Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I tested with the nouveau driver and it worked. Maybe there is something between 1.26 and 1.32 that conflicts with nvidia driver. And it is also similar to #996503 which affects sddm and it worked too with nouveau. I tried to fix this by removing some module options from https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 but it had no effect. Maybe forwarding this to nvidia-driver should get some hints about this issue. Regards, Adilson Em qua., 21 de jun. de 2023 às 15:23, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > > These messages are when I stop lightdm. > > Ah ok. > > > > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU > for > > > example?) or software (specific configuration or something). > > > > > > I'm using Nvidia GPU: > > > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > > 1650] (rev a1) > > > > And it is using its official drivers: > > > > dpkg -l xserver-xorg > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-==--- > > = > > ii xserver-xorg 1:7.7+23 amd64X.Org X server > > > > dpkg -l xserver-xorg-video-nvidia > > Desired=Unknown/Install/Remove/Purge/Hold > > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > > pend > > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > > ||/ Nome Versão Arquitectura Descrição > > +++-=--- > > = > > ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary > Xorg > > driver > > Yup, that's likely related. Honestly we (I) don't really support > binary/proprietary drivers. It'd help if you could test with free drivers > (nouveau or something maybe). > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX > RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 > CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU > V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 > 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd > /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 > pNaWlBMeMGI/+bL89SFEQdR52n/uFw== > =tTX8 > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Em qua., 21 de jun. de 2023 às 03:33, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > > I tried to use 1.32 again and it only > > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > > greeter.log and x-0.lo. From the log attached below, one difference is > that > > 1.26 starts seat0 and 1.32 does not start it. I got an X session from > 1.26 > > and X does not even start from 1.32. > > In the log there's definitely a bad sign: > > [+69.14s] DEBUG: Got signal 15 from process 1 > [+69.14s] DEBUG: Caught Terminated signal, shutting down > [+69.14s] DEBUG: Stopping display manager > [+69.14s] DEBUG: Display manager stopped > [+69.14s] DEBUG: Stopping daemon > [+69.14s] DEBUG: Exiting with return value 0 > These messages are when I stop lightdm. > > > Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, > the > journal, dmesg...) so we have more information? > I will send some system logs from journalctl when I start and stop lightdm 1.32 and 1.26. > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > example?) or software (specific configuration or something). > I'm using Nvidia GPU: 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX 1650] (rev a1) And it is using its official drivers: dpkg -l xserver-xorg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-==---= ii xserver-xorg 1:7.7+23 amd64X.Org X server dpkg -l xserver-xorg-video-nvidia Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nome Versão Arquitectura Descrição +++-=---= ii xserver-xorg-video-nvidia 530.41.03-1 amd64NVIDIA binary Xorg driver > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX > RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ > YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy > wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi > NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK > PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 > hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== > =4Egr > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond Using lightdm 1.32 Jun 21 07:49:59 yoda systemd[1]: Starting lightdm.service - Light Display Manager... jun 21 07:49:59 yoda systemd[1]: Started lightdm.service - Light Display Manager. jun 21 07:49:59 yoda audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:49:59 yoda kernel: audit: type=1130 audit(1687344599.571:939): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' jun 21 07:50:15 yoda systemd[50261]: emacs.service: start operation timed out. Terminating. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Failed with result 'timeout'. jun 21 07:50:15 yoda systemd[50261]: Failed to start emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: emacs.service: Scheduled restart job, restart counter is at 8. jun 21 07:50:15 yoda systemd[50261]: Stopped emacs.service - Emacs text editor. jun 21 07:50:15 yoda systemd[50261]: Starting emacs.service - Emacs text editor... jun 21 07:50:15 yoda emacs[56260]: Warning: due to a long standing Gtk+ bug jun 21 07:50:15 yoda emacs[56260]: https://gitlab.gnome.org/GNOME/gtk/issues/221 jun 21 07:50:15 yoda emacs[56260]: Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost. jun 21 07:50:15 yoda emacs[56260]: Using an Emacs configured with --with-x-toolkit=lucid does not have this problem. jun 21 07:50:15 yoda emacs[56260]: Warning (initialization): Unable to create `user-emacs-directory' (~/.emacs.d/). jun 21 07:50:15 yoda emacs[56260]: Any data that would normally be written there may be lost! jun 21 07:50:15 yoda emacs[56260]: If you never want to see this message again, jun 21 07:50:15 yoda emacs[56260]: customize the variable `user-emacs-d
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi Yves-Alexis, I tried to use 1.32 again and it only generates /var/log/lightdm/lightdm.log. It doesn't generate seat0-greeter.log and x-0.lo. From the log attached below, one difference is that 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 and X does not even start from 1.32. Regards, Adilson Em ter., 20 de jun. de 2023 às 18:13, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > > Package: lightdm > > Followup-For: Bug #1038611 > > > > Can't reproduce, starts up just fine for me. > > > > Could you perhaps include the logs from `/var/log/lightdm/´? > > Hi Adilson, > > I'm running 1.32 just fine since it was uploaded to experimental so I can't > reproduce either. Logs would help indeed, and if you can investigate a bit > more on your side (the info about downgrading helps identifying lightdm but > besides that...) > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX > RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF > zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg > D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA > Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 > 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 > PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== > =SArv > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=30230 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) [+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Loading users from org.freedesktop.Accounts [+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1004 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1005 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Package: lightdm Version: 1.32.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading lightdm to the latest upstream version (1.32.0-2) fails to start X session leading only to console mode. Downgrading to 1.26.0-8, from testing, fixes this bug. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.8 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:p t:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.8-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.2-2 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.11-1 ii libpam0g 1.5.2-6 ii libxcb11.15-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-3 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+23 Versions of packages lightdm suggests: ii accountsservice 22.08.8-6 ii upower 0.99.20-2 ii xserver-xephyr 2:21.1.7-3 -- debconf information: * shared/default-x-display-manager: lightdm lightdm/daemon_name: /usr/sbin/lightdm
Bug#1034160: The regression is back to kscreenlocker
I got this bug again after upgrading to qt5 5.15.8+dfsg-6. The same behavior of plasma screen locker freezing and showing the message to use loginctl to unlock. Downgrading to 5.15.8+dfsg-5 solves it. Since it affects this package again, I'm reopening this bug report. -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#1034160: libkscreenlocker5: Screen locker crashes asking for loginctl command
Package: libkscreenlocker5 Version: 5.27.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, After some libraries updates, I cannot lock my plasma session anymore. It shows a black screen with a message asking to go to a virtual terminal and run a 'loginctl unlock-session 2' or similar to unlock the screen. This is happening with my desktop and my notebook. Even with a reboot this problem presists. Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.10 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libkscreenlocker5 depends on: ii kio5.103.0-1 ii kpackagetool5 5.103.0-1 ii libc6 2.36-8 ii libkf5configcore5 5.103.0-2 ii libkf5configgui5 5.103.0-2 ii libkf5configqml5 5.103.0-2 ii libkf5coreaddons5 5.103.0-1 ii libkf5crash5 5.103.0-1 ii libkf5declarative5 5.103.0-1 ii libkf5globalaccel-bin 5.103.0-1 ii libkf5globalaccel5 5.103.0-1 ii libkf5i18n55.103.0-1 ii libkf5idletime55.103.0-2 ii libkf5kiocore5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5package5 5.103.0-1 ii libkf5quickaddons5 5.103.0-1 ii libkf5screendpms8 4:5.27.2-1 ii libkf5waylandclient5 4:5.103.0-1 ii libkf5windowsystem55.103.0-1 ii libkf5xmlgui5 5.103.0-1 ii liblayershellqtinterface5 5.27.2-1 ii libpam0g 1.5.2-6 ii libqt5core5a 5.15.8+dfsg-4 ii libqt5dbus55.15.8+dfsg-4 ii libqt5gui5 5.15.8+dfsg-4 ii libqt5network5 5.15.8+dfsg-4 ii libqt5qml5 5.15.8+dfsg-3 ii libqt5quick5 5.15.8+dfsg-3 ii libqt5widgets5 5.15.8+dfsg-4 ii libqt5x11extras5 5.15.8-2 ii libstdc++6 12.2.0-14 ii libwayland-client0 1.21.0-1 ii libwayland-server0 1.21.0-1 ii libx11-6 2:1.8.4-2 ii libxcb-keysyms10.4.0-1+b2 ii libxcb11.15-1 ii libxi6 2:1.8-1+b1 ii psmisc 23.6-1 Versions of packages libkscreenlocker5 recommends: ii kde-config-screenlocker 5.27.2-1 libkscreenlocker5 suggests no packages. -- no debconf information
Bug#966812: keepass2: Keepass2 crashes at startup after system update
Em seg., 3 de ago. de 2020 às 06:15, Adrian Bunk escreveu: > On Sun, Aug 02, 2020 at 02:15:53PM -0300, Adilson dos Santos Dantas wrote: > > Package: keepass2 > > Version: 2.45+dfsg-1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > After update my system packages, keepas2 stops working. It simply > crashes at > > startup. Maybe is something related to libc6 with mono. I'm attaching > the crash > > report below to check if the problem is with current keepass packages or > it is > > something with mono runtime. > >... > > Versions of packages keepass2 depends on: > >... > > ii libx11-6 2:1.6.10-1 > >... > > Does upgrading libx11-6 to 2:1.6.10-3 fix your problem? > Yes, it does. I tested it with two machines now and it stopped crashing after libx11-6 upgrade. Thank you! > > cu > Adrian > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#966812: keepass2: Keepass2 crashes at startup after system update
Package: keepass2 Version: 2.45+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, After update my system packages, keepas2 stops working. It simply crashes at startup. Maybe is something related to libc6 with mono. I'm attaching the crash report below to check if the problem is with current keepass packages or it is something with mono runtime. Best regards, Adilson adilsond@r2d2:~$ keepass2 free(): double free detected in tcache 2 = Native Crash Reporting = Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = = Native stacktrace: = 0x5609cf35fa15 - /usr/bin/cli : (null) 0x5609cf35fdac - /usr/bin/cli : (null) 0x5609cf30d605 - /usr/bin/cli : (null) 0x5609cf35efef - /usr/bin/cli : (null) 0x7fe6925bc140 - /lib/x86_64-linux-gnu/libpthread.so.0 : (null) 0x7fe692404cb1 - /lib/x86_64-linux-gnu/libc.so.6 : gsignal 0x7fe6923ee537 - /lib/x86_64-linux-gnu/libc.so.6 : abort 0x7fe692447728 - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x7fe69244ea1a - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x7fe692450015 - /lib/x86_64-linux-gnu/libc.so.6 : (null) 0x4179d31e - Unknown = Telemetry Dumper: = Pkilling 0x7fe67a30a700 from 0x7fe6923c4780 Could not exec mono-hang-watchdog, expected on path '/etc/../bin/mono-hang-watchdog' (errno 2) Pkilling 0x7fe679f08700 from 0x7fe6923c4780 Pkilling 0x7fe6794fe700 from 0x7fe6923c4780 Pkilling 0x7fe67a109700 from 0x7fe6923c4780 Pkilling 0x7fe679d07700 from 0x7fe6923c4780 Pkilling 0x7fe6792fd700 from 0x7fe6923c4780 Pkilling 0x7fe682803700 from 0x7fe6923c4780 Entering thread summarizer pause from 0x7fe6923c4780 Finished thread summarizer pause from 0x7fe6923c4780. Waiting for dumping threads to resume = External Debugger Dump: = [New LWP 9824] [New LWP 9825] [New LWP 9831] [New LWP 9832] [New LWP 9833] [New LWP 9834] [New LWP 9836] [New LWP 9837] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe6924941c7 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6 Id Target Id Frame * 1Thread 0x7fe6923c4780 (LWP 9823) "cli" 0x7fe6924941c7 in wait4 () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x7fe684bff700 (LWP 9824) "SGen worker" 0x7fe6925b77b2 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 3Thread 0x7fe682803700 (LWP 9825) "Finalizer" 0x7fe6925ba174 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 4Thread 0x7fe67a30a700 (LWP 9831) "cli" 0x7fe6925bb1bf in accept () from /lib/x86_64-linux-gnu/libpthread.so.0 5Thread 0x7fe67a109700 (LWP 9832) "cli" 0x7fe6925b7ad8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 6Thread 0x7fe679f08700 (LWP 9833) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 7Thread 0x7fe679d07700 (LWP 9834) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 8Thread 0x7fe6794fe700 (LWP 9836) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 9Thread 0x7fe6792fd700 (LWP 9837) "Thread Pool Wor" 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 Thread 9 (Thread 0x7fe6792fd700 (LWP 9837)): #0 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fe6925ba4b3 in __new_sem_wait_slow.constprop.0 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x5609cf564d71 in ?? () #3 0x5609cf5029d6 in ?? () #4 0x7fe6925b0ea7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7fe6924c6daf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7fe6794fe700 (LWP 9836)): #0 0x7fe6925ba388 in do_futex_wait.constprop () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fe6925ba4b3 in __new_sem_wait_slow.constprop.0 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x5609cf564d71 in ?? () #3 0x5609cf5029d6
Bug#902644: upower: Upower breaks power saving settings after upgrade to 0.99.8-1
It worked here. Commenting out this option fixes the bug. Thank you for the solution. Em ter, 3 de jul de 2018 às 11:49, Michael Biebl escreveu: > Hi > > On Thu, 28 Jun 2018 21:55:01 -0300 Adilson dos Santos Dantas > wrote: > > Package: upower > > Version: 0.99.8-1 > > Severity: important > > > > Dear Maintainer, > > > > After upgrading upower to 0.99.8-1, my KDE power saving settings stops > working. > > There is no reaction when I unplug and plug back my notebook AC power. > > Only the battery charge status changes after a few minutes. > > > > The only workaround found, for this problem, is a downgrade back to > 0.99.7-2. > > Could you please test 0.99.8-1 again and comment out (or remove) the > following line in /lib/systemd/system/upower.service: > > PrivateNetwork=true > > After that run (as root) > systemctl daemon-reload; systemctl restart upower > > Please report back if that fixes your problem. > > Regards, > Michael > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#871629: why is the fixed version not available in Sid
I upgraded to the fixed package this morning. And it is still listed in Sid. yoda:~# apt-cache policy thunderbird thunderbird: Instalado: 1:52.2.1-5 Candidato: 1:52.2.1-5 Tabela de versão: *** 1:52.2.1-5 500 500 http://ftp.br.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status Try 'apt-get update' and 'apt-get -s install thunderbird' to check if it will download the latest version. If not try another mirror. 2017-08-12 17:18 GMT-03:00 Gary Dale <garyd...@torfree.net>: > The bug report web page claims that this bug is fixed in unstable but the > Thunderbird package listed in Sid is the same one that causes problems in > Buster. There is no package listed in Experimental. > > Moreover, the problem isn't just with xfce. I'm having the identical > problem with Plasma. > > I can barely use Thunderbird right now. > > -- > To unsubscribe, send mail to 871629-unsubscr...@bugs.debian.org. > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#871629: same here
2017-08-11 14:32:27 -0400 Daniel Kahn Gillmor <d...@fifthhorseman.net> >I used the snapshots service to get the old version. > >I put the following line in /etc/apt/sources.list.d/snapshots.list : > >deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] > http://snapshot.debian.org/archive/debian/20170806/ sid main > >then i did: > >apt update >apt install thunderbird=1:52.2.1-4 > >This will stop working smoothly once the (now old) signature on the >snapshotted apt archive expires. > >Please remember to remove the snapshot archive from your list of sources >when you're done! And also remember to run this command: apt-mark hold thunderbird This prevents installing the bugged package again. When they fix it, just run apt-get install thunderbird to upgrade it. > >Regards, > >--dkg -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#871629: Add me too here
Same here on Debian Sid with KDE. The only solution, for now, is downgrade Thunderbird to the previous version. -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#857029: thunderbird: tries to migrate nonexistent ~/.icedove due to unintended meaning of "\ #" syntax
Adding my "Me too!" here. Since I rebuild thunderbird from Ubuntu, it always used ~/.thunderbird folder. So, after this second debian-based package it breaks with the dialog about "An existing profile.." Creating a symlink to ~/.icedove shows the same message. But removing the "\ #" comments fixes it. -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond
Bug#799840: libpam-smbpass: installed libpam-smbpass break all local login
It happens with me too. When I upgraded my home computer, it installs this libpam-smbpass version and I cannot log in anymore. Even with ssh it cuts the connection when the authentication suceeded. And the error messages are all the same 'double free or corruption' The problem was fixed after booting with a live system, do a chroot and downgrade samba.
Bug#394139: kdebase misses most of keyboard layouts after upgrading
Package: kdebase Version: 4:3.5.5a-2 Severity: critical Tags: l10n Justification: breaks unrelated software After upgrading kdebase I cant use my keyboards dead keys (brazilian abnt2) with kde and qt applications. Other applications (gtk, motif, etc) are still working fine. So I checked the keyboard layout at kcontrol and there was a few layouts: af, al, ad, ara, am az, bd, by, be, ba, in and us. There's no Brazilian Layout and no deadkeys for use here(exept for non qt and non kde software). This bug is similar to #382988 but all workarounds has been failed. Please fix this bug. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1 Locale: LANG=pt_BR, LC_CTYPE=ISO-8859-1 (charmap=ISO-8859-1) (ignored: LC_ALL set to pt_BR) Versions of packages kdebase depends on: ii hal 0.5.8.1-1.yoda.1 Hardware Abstraction Layer ii kappfinder 4:3.5.5a-2 non-KDE application finder for KDE ii kate4:3.5.5a-2 advanced text editor for KDE ii kcontrol4:3.5.5a-2 control center for KDE ii kdebase-bin 4:3.5.5a-2 core binaries for the KDE base mod ii kdebase-data4:3.5.5a-2 shared data files for the KDE base ii kdebase-kio-plugins 4:3.5.5a-2 core I/O slaves for KDE ii kdepasswd 4:3.5.5a-2 password changer for KDE ii kdeprint4:3.5.5a-2 print system for KDE ii kdesktop4:3.5.5a-2 miscellaneous binaries and files f ii kfind 4:3.5.5a-2 file-find utility for KDE ii khelpcenter 4:3.5.5a-2 help center for KDE ii kicker 4:3.5.5a-2 desktop panel for KDE ii klipper 4:3.5.5a-2 clipboard utility for KDE ii kmenuedit 4:3.5.5a-2 menu editor for KDE ii konqueror 4:3.5.5a-2 KDE's advanced file manager, web b ii konqueror-nsplugins 4:3.5.5a-2 Netscape plugin support for Konque ii konsole 4:3.5.5a-2 X terminal emulator for KDE ii kpager 4:3.5.5a-2 desktop pager for KDE ii kpersonalizer 4:3.5.5a-2 installation personalizer for KDE ii ksmserver 4:3.5.5a-2 session manager for KDE ii ksplash 4:3.5.5a-2 the KDE splash screen ii ksysguard 4:3.5.5a-2 system guard for KDE ii ktip4:3.5.5a-2 useful tips for KDE ii kwin4:3.5.5a-2 the KDE window manager ii libkonq44:3.5.5a-2 core libraries for Konqueror ii pmount 0.9.13-1 mount removable devices as normal Versions of packages kdebase recommends: ii kdm 4:3.5.5a-2 X display manager for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
