Bug#979343: sddm: general protection fault in libQt5Qml.so.5.15.2
Hello Bernhard, On Sun, Mar 21, 2021 at 01:59:34AM +0100, Bernhard Übelacker wrote: > Am 20.03.21 um 21:44 schrieb Helge Kreutzmann: > > If I should install a -dbg version or something else please > > inform me. > > Thank you for the additional information. > There might really be something more. If you have not, is it possible > to install the package "systemd-coredump". > > If then a crash happens again and it gets recorded it should > be mentioned in journalctl and this command should list them: > coredumpctl list > And a core should be stored. (But maybe just for the current boot) > > There should be already a slight backtrace in journalctl > that might be helpful, but with 'coredumpctl gdb' and at the gdb > prompt with 'bt' it might reveal some more information. > Even better when sddm-dbgsym is installed, and if sufficiently RAM is > available, libqt5qml5-dbgsym. (and some more not yet known in between ...) I installed those three packages and report the core dump back. > There might be more pointer in: > https://wiki.debian.org/HowToGetABacktrace Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#979343: sddm: general protection fault in libQt5Qml.so.5.15.2
Am 20.03.21 um 21:44 schrieb Helge Kreutzmann: If I should install a -dbg version or something else please inform me. Thank you for the additional information. There might really be something more. If you have not, is it possible to install the package "systemd-coredump". If then a crash happens again and it gets recorded it should be mentioned in journalctl and this command should list them: coredumpctl list And a core should be stored. (But maybe just for the current boot) There should be already a slight backtrace in journalctl that might be helpful, but with 'coredumpctl gdb' and at the gdb prompt with 'bt' it might reveal some more information. Even better when sddm-dbgsym is installed, and if sufficiently RAM is available, libqt5qml5-dbgsym. (and some more not yet known in between ...) There might be more pointer in: https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard
Bug#979343: sddm: general protection fault in libQt5Qml.so.5.15.2
Hello Lisandro, On Wed, Mar 17, 2021 at 02:28:30PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Control: tag -1 unreproducible moreinfo > > On Wed, 17 Mar 2021 at 13:54, Helge Kreutzmann wrote: > > > > On Wed, Mar 17, 2021 at 02:25:12PM +0100, Bernhard Übelacker wrote: > > > do you still see these messages in your logging? > > > > Yes. > > > > > If yes could you maybe add the surrounding logging > > > of one such fault? E.g. by something like this: > > > journalctl | grep "traps:" -C20 > > > > As soon as it appears (last time was yesterday). > > The weird things here are that it does not always happens and so far > we have only seen your bug report. May I suggest you to check the Well, since it is not causing any visible problems, other users probably don't even notice it, least they report it. I monitor my logs with logcheck, so I notice unusual log messages and report them. > binary with debsums? > > debsums libqt5qml5 root@samd:~# debsums libqt5qml5 /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.15.2 OK /usr/lib/x86_64-linux-gnu/qt5/qml/builtins.qmltypes OK /usr/share/doc/libqt5qml5/changelog.Debian.gz OK /usr/share/doc/libqt5qml5/copyright OK > If that is ok then I would run memtest to check the RAM. I can probably do this some time, but this looks like search in the dark. Since December 4th, when this started, this was the only programm crashing on my machine, and in 2020 I only had one additional crash in vlc. Also (several years back) I had a faulty RAM module, and the experience was quite different - under heavy load memory corruption, including disc corruption. Nothing I've seen since (and definitely not in 2020/2021). Again, if there is some debug version helpful and if I could get the core (currently I don't know how to create it in this case), I could provide it to you. Best greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#979343: sddm: general protection fault in libQt5Qml.so.5.15.2
Hello Bernhard, On Wed, Mar 17, 2021 at 02:25:12PM +0100, Bernhard Übelacker wrote: > do you still see these messages in your logging? For example today. > If yes could you maybe add the surrounding logging > of one such fault? E.g. by something like this: > journalctl | grep "traps:" -C20 Here you are: Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:103: TypeError: Cannot read property 'largeSpacing' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:44: TypeError: Cannot read property 'gridUnit' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:78: TypeError: Cannot read property 'largeSpacing' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:69: TypeError: Cannot read property 'largeSpacing' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:95: TypeError: Cannot read property 'gridUnit' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/TextField.qml:152: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/private/TextFieldFocus.qml:80: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:50: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:75: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:50: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:75: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:50: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:75: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:50: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:75: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:50: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/share/sddm/themes/debian-theme/components/UserDelegate.qml:75: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/TextField.qml:128: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd sddm-greeter[2001]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/TextField.qml:128: TypeError: Cannot read property 'longDuration' of null Mär 20 16:13:35 samd systemd[2378]: gpgconf: Fehler bei Ausführung von `/usr/lib/gnupg/scdaemon': wahrscheinlich nicht installiert Mär 20 16:13:35 samd kernel: traps: sddm-greeter[2001] general protection fault ip:7fd51dfe3ec7 sp:7ffccf696ee0 error:0 in libQt5Qml.so.5.15.2[7fd51ddb+2cd000] Mär 20 16:13:35 samd sddm-helper[1975]: [PAM] Closing session Mär 20 16:13:35 samd sddm-helper[1975]: pam_unix(sddm-greeter:session): session closed for user sddm Mär 20 16:13:35 samd sddm-helper[1975]: [PAM] Ended. Mär 20 16:13:35 samd sddm[1923]: Auth: sddm-helper exited with 11 Mär 20 16:13:35 samd sddm[1923]: Greeter stopped. Mär 20 16:13:35 samd systemd[1]: session-2.scope: Succeeded. Mär 20 16:13:35 samd systemd[1]: session-2.scope: Consumed 1.357s CPU time. Mär 20 16:13:35 samd systemd-logind[669]: Session 2 logged out. Waiting for processes to exit. Mär 20 16:13:35 samd systemd-logind[669]: Removed session 2. Mär 20 16:13:35 samd systemd[1977]: pulseaudio.service: Succeeded. Mär 20 16:13:35 samd systemd[2373]: Queued start job for default target Main User Target. Mär 20 16:13:35 samd systemd[2373]: Created slice User Application Slice. Mär 20 16:13:35 samd systemd[2373]: Reached target Paths. Mär 20 16:13:35 samd systemd[2373]: Reached target Timers. Mär 20 16:13:35 samd systemd[2373]: Starting D-Bus User Message Bus
Processed: Re: Bug#983025: libqt5widgets5: Segfault with QGLWidget class. Fixed Upstream
Processing control commands: > severity -1 important Bug #983025 [libqt5widgets5] libqt5widgets5: Segfault with QGLWidget class. Fixed Upstream Severity set to 'important' from 'critical' > tags -1 - newcomer Bug #983025 [libqt5widgets5] libqt5widgets5: Segfault with QGLWidget class. Fixed Upstream Removed tag(s) newcomer. > forwarded -1 https://bugreports.qt.io/browse/QTBUG-86582 Bug #983025 [libqt5widgets5] libqt5widgets5: Segfault with QGLWidget class. Fixed Upstream Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-86582'. -- 983025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983025: libqt5widgets5: Segfault with QGLWidget class. Fixed Upstream
Control: severity -1 important Control: tags -1 - newcomer Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-86582 ¡Hola Alejandro! On Thu, Feb 18, 2021 at 11:59:56AM +0100, Alejandro Lorenzo wrote: > Package: libqt5widgets5 > Version: 5.15.2+dfsg-4 > Severity: critical > Tags: upstream newcomer > Justification: breaks unrelated software > > Dear Maintainer, > > Recently i found a bug in QGLWidget (one of the widgets included in > libqt5widgets5) that creates a segfault. This bug was accepted as upstream > bug 86582 > > (https://bugreports.qt.io/browse/QTBUG-86582) > > It was confirmed and fixed by the Qt people, unfortunately, it has been > committed to the 5.15 LTS branch of their development which is no longer > accessible to the OpenSource licensees > > QGLWidget has been a deprecated Widget for some time now, and many software > changed to QOpenGLWidget alternative, which does not exhibit this problem, > but other pieces of the debian system (e.g. libqtgstreamer; also deprecated > but still in debian repos) uses it. Can you please tell if any applications in Debian repos are affected by this bug? You mentioned libqtgstreamer but it's a library — do you know if there is a concrete application that can be used to reproduce that crash? It is unlikely that we will be able to fix it, provided that upstream patch is not publicly available. So I am downgrading severity to make this bug not block the release of Debian Bullseye. This bug does not satisfy the criteria for critical anyway, because not the whole libqt5widgets5 library is broken, but only a specific use-case of it (which is also a deprecated one). Also I am removing the newcomer tag — newcomers won't have enough knowledge to be able to fix it. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: Screen randomly wakes up from standby / energy saving mode
On Saturday, March 20, 2021 12:46:00 PM CET Daniel Schröter wrote: > inkbottle schrieb am Mittwoch, 26. Februar 2020 um 17:20:03 UTC+1: > > My screen randomly wakes up from standby > > I have the same problem. It seems to happen since one oft the last upgrades. > I'm running KDE from unstable (5.20.5). > > One monitor went to sleep (and stands there) fine. The other monitor wakes > up every minute. No logs in journalctl or dbus-monitor. > > I also tried it with a new profile (other user). I already replaced the > displayport cable. > > In sddm it works fine. But if I start "real" KDE it wakes up every minute > randomly. > > If I do > xrandr --output DP-1 --off > the monitor went to sleep and stays in sleep mode. After KDE(?) sends sleep > to the monitor (after 10 minutes inactivity) the problematic monitor wakes > up from sleep again :-( > > Any ideas to debug this? Your analysis of KDE waking up the monitor by sending a sleep signal is interesting. (I don't know how you figured that out.) At one point I understood that `dpms` was buggy. That `kwin` had difficulties communicating with `dmps` for intrinsic reasons, and that it will never be fixed anyway, nor even investigated, because `xorg` isn't developed any longer. I don't remember what exactly made me believe that in the first place. Consequently I endeavored to see what could be done with `wayland`. I found out that a command that shows how the kernel see the monitor, `drm_info`, invariably returns correct information, unless `kwin` is running, in which case those data became preposterous, wrong. Just as if it is the whole `kwin` stake that might have issues. Again it is the layman view, I'm probably completely mistaken. However it does work quite all right with gnome/ wayland if I remember correctly. Here, what I found about that at the time: https://bugs.kde.org/show_bug.cgi?id=404092 (I'm not sure nobody ever read what I wrote. They must have a lot on their plate.) At one point I did use that sort of command: `while true; do xset dpms 10 10 10; sleep 10; xset dpms force off; sleep 600; done` But it wasn't working very well neither, as if something was messing around with it in the background, and even though it did seem bullet proof, the monitor always manage to wake up now and then, only for a short time, which was resulting in a sort of very slow flickering, not sure it's good for the monitor. Sooo, what I do now: I turn the computer off! Oh, yes, turning the monitor off wouldn't do it, it would put such a mess, it'd take me like 30 min, to fix it when turning it back on. > > Bye
Re: Screen randomly wakes up from standby / energy saving mode
Hello Norbert, Norbert Preining schrieb am Samstag, 20. März 2021 um 13:30:03 UTC+1: > Which GPU are you using? It's not an AMD GPU. Old onboard Intel # inxi -G Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Display: server: X.org 1.20.10 driver: loaded: modesetting tty: 103x55 Message: Advanced graphics data unavailable in console for root. # lsgpu sys:/sys/devices/pci:00/:00:02.0/drm/card0 subsystem : drm drm card: /dev/dri/card0 parent : sys:/sys/devices/pci:00/:00:02.0 sys:/sys/devices/pci:00/:00:02.0/drm/renderD128 subsystem : drm drm render : /dev/dri/renderD128 parent : sys:/sys/devices/pci:00/:00:02.0 sys:/sys/devices/pci:00/:00:02.0 subsystem : pci drm card: /dev/dri/card0 drm render : /dev/dri/renderD128 vendor : 8086 device : 0412 # lscpu |grep "Model name" Model name: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz As mentioned already it has been working in the past and just occurs if KDE has been loaded. Bye
Re: Screen randomly wakes up from standby / energy saving mode
Hi Daniel, Which GPU are you using? With AMDs this is a known problem and ignored since years by upstream developers. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA ProGuide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 Mar 20, 2021 21:06:15 Daniel Schröter : > inkbottle schrieb am Mittwoch, 26. Februar 2020 um 17:20:03 UTC+1: >> My screen randomly wakes up from standby > > I have the same problem. It seems to happen since one oft the last upgrades. > I'm running KDE from unstable (5.20.5). > > One monitor went to sleep (and stands there) fine. The other monitor wakes up > every minute. No logs in journalctl or dbus-monitor. > > I also tried it with a new profile (other user). I already replaced the > displayport cable. > > In sddm it works fine. But if I start "real" KDE it wakes up every minute > randomly. > > If I do > xrandr --output DP-1 --off > the monitor went to sleep and stays in sleep mode. After KDE(?) sends sleep > to the monitor (after 10 minutes inactivity) the problematic monitor wakes up > from sleep again :-( > > Any ideas to debug this? > > Bye
Re: Screen randomly wakes up from standby / energy saving mode
inkbottle schrieb am Mittwoch, 26. Februar 2020 um 17:20:03 UTC+1: > My screen randomly wakes up from standby I have the same problem. It seems to happen since one oft the last upgrades. I'm running KDE from unstable (5.20.5). One monitor went to sleep (and stands there) fine. The other monitor wakes up every minute. No logs in journalctl or dbus-monitor. I also tried it with a new profile (other user). I already replaced the displayport cable. In sddm it works fine. But if I start "real" KDE it wakes up every minute randomly. If I do xrandr --output DP-1 --off the monitor went to sleep and stays in sleep mode. After KDE(?) sends sleep to the monitor (after 10 minutes inactivity) the problematic monitor wakes up from sleep again :-( Any ideas to debug this? Bye
Frameworks 5.80
Hi, I just pulled KDE-Frameworks: 5.80.0 from Experimental. Thanks for all hard work and keeping us in sync with up-stream!! -- Luc Castermans mailto:luc.casterm...@gmail.com
