Bug#534420: marked as done (Nepomukserver crashes KDE3 sessions)
Your message dated Fri, 26 Jun 2009 17:25:40 +0300
with message-id <ba4a6e220906260725x1fb22087m77b5b6b196b1f48@mail.gmail.com>
and subject line Re: Bug#534672: System not recoverable
has caused the Debian Bug report #534421,
regarding Nepomukserver crashes KDE3 sessions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
534421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534421
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kdebase-runtime
Version: 4:4.2.2-1
Severity: important
*** Please type your report below this line ***
Please refer to bug 534340.
Here another crash-log from the .xsession-errors
============================
nepomukstorage(4001) Nepomuk::Repository::open: no need to convert "main"
nepomukstorage(4001) Nepomuk::Storage::slotNepomukCoreInitialized:
Successfully initialized nepomuk core
[/usr/bin/nepomukservicestub] "/usr/bin/nepomukservicestub(4002)" Error
in thread 139651718399840 : "org.freedesktop.DBus.Error.UnknownObject -
No such object path '/org/soprano/Server'"
"/usr/bin/nepomukservicestub(4002)" Error in thread 139651718399840 :
"QLocalSocket::connectToServer: Connection refused"
nepomukqueryservice(4002) <unnamed>::GlobalModelContainer::init: Failed
to connect to Nepomuk server via local socket
"/home/anja/.kde/share/apps/nepomuk/socket"
X Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2
Minor opcode: 0
Resource id: 0xa00012
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
*** kdesktop got signal 1 (Exiting)
kicker: sighandler called
klauncher: Exiting on signal 1
kicker: Fatal IO error: client killed
ksmserver: Fatal IO error: client killed
ICE default IO error handler doing an exit(), pid = 3989, errno = 11
kdeinit: sending SIGTERM to children.
kdesktop_lock: Fatal IO error: client killed
kicker: sighandler called
kdeinit: Exit.
ICE default IO error handler doing an exit(), pid = 3904, errno = 4
klauncher: Fatal IO error: client killed
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
Where is the Neopukserver started?
How can i disable it?
I don't need and want it!
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-1)
(ignored: LC_ALL set to de_DE)
Shell: /bin/sh linked to /bin/bash
Versions of packages kdebase-runtime depends on:
ii kde-icons-oxygen 4:4.2.2-1 Oxygen icon theme for KDE 4
ii kdebase-runtime-bin-kde4 4:4.2.2-1 core binaries for the KDE 4
base r
ii kdebase-runtime-data 4:4.2.2-1 shared data files for the
KDE 4 ba
ii kdelibs5 4:4.2.2-2 core libraries for all KDE
4 appli
ii libasound2 1.0.20-2 shared library for ALSA
applicatio
ii libc6 2.9-12 GNU C Library: Shared libraries
ii libclucene0ldbl 0.9.20-3 library for full-featured
text sea
ii libgcc1 1:4.4.0-5 GCC support library
ii libjpeg62 6b-14 The Independent JPEG
Group's JPEG
ii libopenexr6 1.6.1-4 runtime files for the
OpenEXR imag
ii libphonon4 4:4.3.1-1 Phonon multimedia framework
for Qt
ii libpulse0 0.9.15-2 PulseAudio client libraries
ii libqt4-dbus 4.5.1-2 Qt 4 D-Bus module
ii libqt4-qt3support 4.5.1-2 Qt 3 compatibility library
for Qt
ii libqt4-svg 4.5.1-2 Qt 4 SVG module
ii libqt4-xml 4.5.1-2 Qt 4 XML module
ii libqtcore4 4.5.1-2 Qt 4 core module
ii libqtgui4 4.5.1-2 Qt 4 GUI module
ii libsmbclient 2:3.3.4-1 shared library for
communication w
ii libsoprano4 2.2.2+dfsg.1-1 libraries for the Soprano
RDF fram
ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3
ii libstreamanalyzer0 0.6.5-1+b1 streamanalyzer library for
Strigi
ii libstreams0 0.6.5-1+b1 streams library for for
Strigi Des
ii libx11-6 2:1.2.1-1 X11 client-side library
ii libxcursor1 1:1.1.9-1 X cursor management library
ii libxine1 1.1.16.2-1+b1 the xine video/media player
librar
ii p
kdebase-runtime recommends no packages.
Versions of packages kdebase-runtime suggests:
pn djvulibre-bin <none> (no description available)
-- no debconf information
honon-backend-gstreamer 4:4.3.1-1 Phonon GStreamer 0.10.x backend
--- End Message ---
--- Begin Message ---
2009/6/26 <forum+debian@km.mydyn.de>:
> Before i am killing the system i checked some other logs.
> Now i found in the /var/log/Xorg.0.log
>
> (II) Setting vga for screen 0.
> (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
> (==) NVIDIA(0): RGB weight 888
> (==) NVIDIA(0): Default visual is TrueColor
> (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
> (**) NVIDIA(0): Option "MetaModes" "1680x1050 +0+0; 1280x1024 +0+0; 1024x768 +0+0; 800x600 +0+0; 640x480 +0+0"
> (**) NVIDIA(0): Enabling RENDER acceleration
> (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
> (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
> (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
> (EE) NVIDIA(0): you continue to encounter problems, Please try
> (EE) NVIDIA(0): reinstalling the NVIDIA driver.
> (II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 at PCI:1:0:0 (GPU-0)
> (--) NVIDIA(0): Memory: 131072 kBytes
> (--) NVIDIA(0): VideoBIOS: 04.34.20.87.00
> (II) NVIDIA(0): Detected AGP rate: 8X
> (--) NVIDIA(0): Interlaced video modes are supported on this GPU
> (--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:1:0:0:
> (--) NVIDIA(0): NVIDIA TV Encoder (TV-0)
> (--) NVIDIA(0): Hitachi X91D DVI (DFP-0)
> (--) NVIDIA(0): NVIDIA TV Encoder (TV-0): 350.0 MHz maximum pixel clock
> (--) NVIDIA(0): TV encoder: NVIDIA
> (II) NVIDIA(0): Assigned Display Device: DFP-0
> (WW) NVIDIA(0): No valid modes for "1680x1050+0+0"; removing.
> (II) NVIDIA(0): Validated modes:
> (II) NVIDIA(0): "1280x1024+0+0"
> (II) NVIDIA(0): "1024x768+0+0"
> (II) NVIDIA(0): "800x600+0+0"
> (II) NVIDIA(0): "640x480+0+0"
>
> So to run Debian with KDE4 you must have a running GLX?
No, KDE4 does not require GLX. However, the KDE window manager checks
if X is capable of doing GLX stuff and in this process it uses some GL
functions.
The problem in your case is that you have installed the nvidia drivers
from the nvidia installer (downloaded from nvidia.com) and you
installed them without knowing that this installer overwrites files
from Xorg/mesa. Then you installed xfce (as stated in bug 534340) and
that probably also caused an upgrade of Xorg/mesa, which overwrote the
files of the nvidia driver again. This makes the nvidia driver to
crash when some application attempts to use GLX stuff. As a result,
you are kicked out of KDE and GNOME sessions because they both have
compositing-aware window managers and try to find and use
compositing/GLX on login if it is available.
> I tried to reinstall the NVIDIA-driver and that was working.
See? ;) Reinstalling the nvidia drivers overwrites the files again
and it works. So, please switch to using the nvidia-glx package
instead of the nvidia installer or make use of the nvidia installer at
your own risk and taking care to reinstall the driver whenever
something from xorg or mesa is upgraded.
> But now the system does not reboot any more.
> It is hanging at starting NFS
That might be an issue either with NFS or your network connection, but
completely unrelated to the nvidia drivers and/or KDE/GNOME/XFCE.
> I give up now ...
In the future, please refrain from opening bug reports (especially
ones with serious or grave severity) if you don't have enough
knowledge of what is going on. There are user support mailing lists
and forums where you can ask to find a solution to your problem. You
should only file bug reports when you are almost sure that your
problem is a bug in a specific package.
I am closing all three reports that you opened about this "bug":
534672, 534340 and 534421. I hope you didn't file any more bugs about
this in gnome packages... If you did, please close them.
Thanks,
George
--- End Message ---
Reply to: