Registered Member
|
plasma crashes at session start on my hardware with the new stable drivers from nvidia, 180.22: everything is working with 177.82 but kde 4.2 is much smoother with 180.22.
I'm on Slackware 12.2 with kde 4.1.96 packages from slackware current, but it's doing the same with 4.1.3. tried rebuilding kdebase-workspace with nvidia 180.22 drivers installed but with no effect. if i change "startkde" (in .xinitrc) with "xterm & startkde" I can relaunch plasma in the xterm but khotkeys don't work (no use restarting it). before that, I generated the attached bug report nvidia-bug-report.log.gz and the redirected x output as x.log.gz. I have done logs also of working situation with 177.82. trying to get a strace of plasma process I: - renamed /usr/bin/plasma to /usr/bin/plasma-real - created an executable script named /usr/bin/plasma with the line strace plasma-real > /tmp/plasma.log 2>&1 - launched X - plasma don't die at start but I still got the khotkey problem. I got plasma logs of the two drivers. tried to use gdb (first time) but I wasn't able to apply at this particular situation, valgrind output is here
this are the logs http://omploader.org/vMTV1cA/logs.tar I'm posting here to ask for suggestions on how to debug it and if you think I should post a bug report on this... tnx in advance
Last edited by ponce on Mon Jan 26, 2009 8:45 am, edited 1 time in total.
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Registered Member
|
another interesting thing (maybe for me only cause, as you can see, I'm learning things while reporting):
tried to follow these instructions http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to get a backtrace to gdb so I recompiled kdebase-workspace with -g flag and disabled stripping. if I quit plasma and relaunch in gdb with 177.82 i can run it, pause it, and I got this backtrace
if I do the same thing with 180.22 program exits with code 01 and this is the output
I think I'm missing something?
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Administrator
|
dlsym is used to access symbols in a library, therefore this means a needed symbol cannot be found ( vsnprintf is provided by glibc I think )
Can you use gdb on other applications ( such as KMix, XTerm, etc ) You may also want to ensure that you have debugging symbols installed for Qt, and KDElibs as well.
Last edited by bcooksley on Sun Jan 25, 2009 8:57 am, edited 1 time in total.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I'm rebuilding qt and kdelibs without stripping (slackbuilds usually execute this two strings, that I commented out)
and I'll post back.
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Registered Member
|
now I got qt, kdelibs and kdebase-workspace rebuilt.
with 177.82 I can kquitapp plasma and then
but with 180.22 is still
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Administrator
|
I do not have any ideas on why this may be happening. NVidia are likely the only ones who can provide insight.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
with my little experience in this matter, I supposed that too, but thnx for confirming it and for your help trying to guess out what is happening
changed post tag: if you think is not appropriated just let me know
Last edited by ponce on Mon Jan 26, 2009 8:46 am, edited 1 time in total.
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Registered Member
|
news on the matter: seems like libsafe (preloaded in slack) is blocking certain nasty functions of driver 180.xx, as disabling make everything (other than plasma, I experienced problem trying to launch google earth) works.
if you disable it, be sure to use PAE for kernel (as explained in the thread linked).
Last edited by ponce on Tue Feb 03, 2009 6:20 am, edited 1 time in total.
ponce, proud to be a member of KDE forums since 2008-Dec.
|
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]