Public bug reported:

I am the lead developer of Pidgin. A user came in reporting that on a
fresh copy of mate 24.04 launching pidgin would kill their X session and
bring them back to the login screen.

The user ended up fixing it somehow. They booted from a USB key I guess
and installed pidgin there, and after returning to their normal install
it was fixed.

However, I installed Mate 24.04 in a virtual machine and am able to
easily reproduce the issue.

I've tried to get a backtrace by running pidgin under gdb in screen, but
all I'm seeing is an X error and nothing else this is also why I have
apport disabled per https://wiki.ubuntu.com/Backtrace.

I've tried a number of things, but nothing has seemed to make a
difference. However, I did just notice a backgrace in Xorg.0.log.old
which I've included below.

If necessary I can provide this libvirt based vm for testing there's
nothing personal or whatever in it.

[   256.027] (EE) Backtrace:
[   256.028] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x14c) [0x594269ec7dbc]
[   256.029] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x70928ac45320]
[   256.030] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x11c) 
[0x70928ac9eb1c]
[   256.031] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x1e) 
[0x70928ac4526e]
[   256.032] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xdf) 
[0x70928ac288ff]
[   256.034] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   256.034] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x70928ac2881b]
[   256.035] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x47) 
[0x70928ac3b507]
[   256.035] (EE) 7: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xbd3) 
[0x594269e7e3c3]
[   256.035] (EE) 8: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa6) [0x594269e806a6]
[   256.036] (EE) 9: /usr/lib/xorg/Xorg (DRI2GetParam+0x6b9) [0x594269e81409]
[   256.036] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x3e4) 
[0x594269d48ab4]
[   256.037] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3b2) [0x594269d4ce52]
[   256.038] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x8a) 
[0x70928ac2a1ca]
[   256.039] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x8b) 
[0x70928ac2a28b]
[   256.040] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x594269d35395]
[   256.040] (EE) 
[   256.040] (EE) 
Fatal server error:
[   256.040] (EE) Caught signal 6 (Aborted). Server aborting
[   256.040] (EE) 
[   256.040] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[   256.040] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[   256.040] (EE) 
[   256.060] (EE) Server terminated with error (1). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pidgin 1:2.14.13-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Apr 29 00:47:08 2024
InstallationDate: Installed on 2024-04-27 (2 days ago)
InstallationMedia: Ubuntu-MATE 24.04 LTS "Noble Numbat" - Release amd64 
(20240424)
SourcePackage: pidgin
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2024-04-26T23:30:36.471843

** Affects: pidgin (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064079

Title:
  starting pidgin on a fresh mate 24.04 kills the x session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/2064079/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to