| Summary: | Segfault after updating KDE to 4.10 | ||
|---|---|---|---|
| Product: | [Applications] apper | Reporter: | Peter Huyoff <peter.huyoff> |
| Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | jnelson-kde, peter.huyoff, rdieter |
| Priority: | NOR | ||
| Version: | 0.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
.xsession-errors after first login
.xsessio-errors after second login New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Peter Huyoff
2013-02-12 18:01:20 UTC
Created attachment 77336 [details]
.xsession-errors after first login
Created attachment 77338 [details]
.xsessio-errors after second login
Created attachment 77411 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- Unusual behavior I noticed:
Same effect, on every login. I've created a new testuser from scratch - same segfault after login.
-- Backtrace (Reduced):
#7 0x00007faab263d5e8 in PackageKit::Transaction::error (this=0x0) at /usr/src/debug/PackageKit-Qt-0.8.7/src/transaction.cpp:203
#8 0x00007faab287080c in Updater::checkForUpdates (this=0x248c450, systemReady=<optimized out>) at /usr/src/debug/apper-0.8.0/apperd/Updater.cpp:100
#9 0x00007faab287238d in ApperdThread::updatesChanged (this=0x2895150) at /usr/src/debug/apper-0.8.0/apperd/ApperdThread.cpp:263
[...]
#11 0x00007faad77a9f8f in QSingleShotTimer::timerEvent (this=0x28b4b60) at kernel/qtimer.cpp:317
#12 0x00007faad77a140c in QObject::event (this=0x28b4b60, e=<optimized out>) at kernel/qobject.cpp:1165
Created attachment 77464 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.10.00 "release 546" using Qt 4.8.4
- Unusual behavior I noticed:
System booted with "nomodeset", same thing happens...
-- Backtrace (Reduced):
#7 0x00007f319ae2a5e8 in PackageKit::Transaction::error (this=0x0) at /usr/src/debug/PackageKit-Qt-0.8.7/src/transaction.cpp:203
#8 0x00007f319b0a280c in Updater::checkForUpdates (this=0xe152d0, systemReady=<optimized out>) at /usr/src/debug/apper-0.8.0/apperd/Updater.cpp:100
#9 0x00007f319b0a438d in ApperdThread::updatesChanged (this=0xe51f80) at /usr/src/debug/apper-0.8.0/apperd/ApperdThread.cpp:263
[...]
#11 0x00007f31c815cf8f in QSingleShotTimer::timerEvent (this=0xcd7bb0) at kernel/qtimer.cpp:317
#12 0x00007f31c815440c in QObject::event (this=0xcd7bb0, e=<optimized out>) at kernel/qobject.cpp:1165
This backtrace is really nonsense... It crashes because of a null pointer but that pointer was just created so I don't see why it's null, do you have this bahavior at every login? if you kill kded4 and start it from konsole does it crash too? Thanks > This backtrace is really nonsense... It crashes because of a null pointer but that pointer was just > created so I don't see why it's null, do you have this bahavior at every login? Yes, this crash happens every time, i logging into my account. I've created a new test-account, with the same effect happening on every boot! The crash happens ca. 30secs to 2mins after KDE4 is fully up. Autostart of jbidwatcher fails, since this failure is present. Maybe, this triggers the bug? > if you kill kded4 and start it from konsole does it crash too? Yes, this happens on every login. I've witched runmode on tty1 from 5 to 3 and back with no change. Same thing if i apply <ctrl>+<alt>+2*<backspace>. Another thing, happening rarely from time to time: Everything works fine, when changing from one applicatin to another fails partially. Mouseclicks are focussed to the last App, clicks outside the old window are withot effect. Keyboard works without quirks, i can use all shortcuts within the "new" App. But i can't switch to another app, using <alt>+<Tab>. The only way out of this is mess, is killing kde4 and login again. Peter can you pkill kded4 and launch it from konsole and wait to see if the same happens? is it a new F18 install? > can you pkill kded4 and launch it from konsole and wait to see if the same happens? Yes, i've done so and the following happens: ----snipp------------------------------------------ pehy@dell670:~> pkill kded4 pehy@dell670:~> kded4 Object::connect: No such signal QDBusAbstractInterface::StateChanged(uint) QDBusConnection for control created "/Mixers/PulseAudio__Playback_Devices_1/alsa_output_pci_0000_07_00_1_hdmi_stereo" QDBusConnection for control created "/Mixers/PulseAudio__Playback_Devices_1/alsa_output_pci_0000_00_1b_0_analog_stereo" QDBusConnection for control created "/Mixers/PulseAudio__Capture_Devices_1/alsa_input_pci_0000_00_1b_0_analog_stereo" Agent registered pehy@dell670:~> kded(5122) PowerDevil::PolicyAgent::setupSystemdInhibition: failed to inhibit systemd powersave handling QDBusConnection: name 'org.kde.Solid.PowerManagement' had owner '' but we thought it was ':1.278' QDBusConnection for control created "/Mixers/PulseAudio__Playback_Streams_1/restore_sink_input_by_media_role_event" pehy@dell670:~> -----------------snipp----------------------------------------- After this, all icons on desktop, except the trashcan, dissapeard! The USB-Notifier pops repeatedly up with "the following device cannot mounted: win-partition>" (translated from german) > is it a new F18 install? No, it's a relative fresh openSUSE 12.2. I've updated KDE from 4.8.5 to 4.10 to fix the problems around KDE4. It became unstable last december. At this time, my machine runs openSUSE 11.4. The problems started after one of the regular online-updates. In january, i Installed openSUSE (no upgrade, fresh install). This is my system: Prozessor (CPU): Intel(R) Xeon(R) CPU 5160 @ 3.00GHz Geschwindigkeit: 2 992,35 MHz Kerne: 4 Arbeitsspeicher Gesamter Arbeitsspeicher: 9,8 GiB Freier Arbeitsspeicher: 5,9 GiB (+ 1,8 GiB Zwischenspeicher) Freier Auslagerungsspeicher (Swap): 4,0 GiB Betriebssystem Kernel: Linux 3.4.28-2.20-desktop x86_64 Aktueller Benutzer: pehy@dell670 Distribution: openSUSE 12.2 (x86_64) KDE: 4.10.00 "release 546" Grafikkarte Hersteller: nVidia Corporation Modell: 2D-Treiber: nvidia 3D-Treiber: NVIDIA 304.64 Peter I've also been having lots of problems with segfaults after upgrading to 4.10
Invariably, they happen when the network is refreshing or right after unlocking the screen.
My tracebacks (konsole crashing) look like this:
#0 sprintf (__fmt=0x7fa10708eec0 "_NET_WM_CM_S%d", __s=<optimized out>)
at /usr/include/bits/stdio2.h:35
#1 create_atoms (dpy=0x0)
at /usr/src/debug/kdelibs-4.10.0/kdeui/windowmanagement/kwindowsystem_x11.cpp:331
#2 0x00007fa1070350aa in KWindowSystem::compositingActive ()
at /usr/src/debug/kdelibs-4.10.0/kdeui/windowmanagement/kwindowsystem_x11.cpp:806
#3 0x00007fa107583e09 in __static_initialization_and_destruction_0 (
__initialize_p=<optimized out>, __priority=<optimized out>)
at /usr/src/debug/konsole-4.10.0/src/WindowSystemInfo.cpp:29
#4 _GLOBAL__sub_I_WindowSystemInfo.cpp(void) ()
at /usr/src/debug/konsole-4.10.0/src/WindowSystemInfo.cpp:29
#5 0x00007fa107e107b6 in call_init (env=0x7fffb17ea468, argv=0x7fffb17ea458,
argc=1, l=<optimized out>) at dl-init.c:85
#6 call_init (l=<optimized out>, argc=1, argv=0x7fffb17ea458,
env=0x7fffb17ea468) at dl-init.c:35
#7 0x00007fa107e1089a in _dl_init (main_map=0x7fa108025188, argc=1,
argv=0x7fffb17ea458, env=0x7fffb17ea468) at dl-init.c:134
#8 0x00007fa107e0351a in _dl_start_user () from /lib64/ld-2.15.so
#9 0x0000000000000001 in ?? ()
#10 0x00007fffb17eb179 in ?? ()
#11 0x0000000000000000 in ?? ()
hmm looking at you xsession erros file actually showed that your packagekit installation might not be working well, does apper opens and work? and your last comment is due which application? the tracebacke doesn't seem to be from apper. Ok, I think I might have fixed the issue (tho if doesn't explain the this=0x0 on the backtrace it might fix the issue: http://gitorious.org/packagekit/packagekit-qt/commit/da41de0e4a98eed232eb05a14e903666dbb21838 I'll ask fedora ppl to push the patch ask and ye shall receive, http://admin.fedoraproject.org/updates/PackageKit-Qt-0.8.7-3.fc18 Yesterday i've updated KDE to version 4.10.1 "release 552". It seems the bug is resolved, no segfault, no lost focus anymore! (Distribution: openSUSE 12.2 (x86_64)) TIA, peter Huyoff This doesn't make sense, first because I thought the bug was with a Fedora user so the update is only in fedora repos and not in openSUSE ones... Your update probably fixed your PackageKit installation which was actually what was triggering the bug but doesn't explain much the crash... either way the code is a bit better now... |