--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Segfaults on session start
- From: Didier 'OdyX' Raboud <odyx@debian.org>
- Date: Tue, 14 Jul 2015 00:10:03 +0200
- Message-id: <20150713221003.17602.65557.reportbug@gyllingar>
Package: libkf5screen6
Version: 4:5.3.2-1
Severity: serious
Hi,
I can't open my second session (uid 1001, if that matters), now that my
external screen isn't connected anymore. On session opening, I get multiple
segfaults, starting with kscreen_backend and KSC_XRandR:
Jul 14 00:00:29 gyllingar kernel: [15295.632381] kscreen_backend[17452]: segfault at 10 ip 00007fa54b5acbd0 sp 00007ffff8cd5a68 error 4 in KSC_XRandR.so[7fa54b597000+22000]
Jul 14 00:00:29 gyllingar kernel: [15295.714059] ksplashqml[17403]: segfault at 8 ip 00007f6afd3ca5a0 sp 00007ffea7fbabb8 error 4 in libQt5Gui.so.5.4.2[7f6afd2b8000+52c000]
Jul 14 00:00:29 gyllingar kernel: [15295.714183] kactivitymanage[17446]: segfault at 18 ip 00007fb269e88910 sp 00007fffbdd7bf18 error 4 in libqxcb.so[7fb269e59000+ba000]
I tried to remove some configuration files, but the session still doesn't
start.
Of course, I'm willing to help debugging this, but I don't know where to
start.
Cheers,
OdyX
-- System Information:
Debian Release: stretch/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libkf5screen6 depends on:
ii libc6 2.19-19
ii libqt5core5a 5.4.2+dfsg-4
ii libqt5dbus5 5.4.2+dfsg-4
ii libqt5gui5 5.4.2+dfsg-4
ii libqt5x11extras5 5.4.2-2
ii libstdc++6 5.1.1-14
ii libxcb-randr0 1.10-3+b1
ii libxcb1 1.10-3+b1
libkf5screen6 recommends no packages.
libkf5screen6 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi there,
I can't reproduce this bug; hereby closing then; thanks for the followup !
Le mercredi, 5 avril 2017, 09.29:25 h CEST Lisandro écrit :
> As of version 4:5.8.6-1 (even possibly before) I can't find this issue
> anymore. Is some of you still able to reproduce it?
>
> We do have a workaround for this so maybe this should become important, but
> it would be better if we can close it.
Cheers,
--
OdyX
--- End Message ---