Your message dated Fri, 12 Apr 2024 14:50:31 +0200
with message-id <b4b9651d77775c2c98078dc9bc381f8b2a94610f.ca...@debian.org>
and subject line Re: Bug#1056555: thunar: segfault when ejecting drive
has caused the Debian Bug report #1056555,
regarding thunar: segfault when ejecting drive
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1056555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar
Version: 4.18.4-1
Severity: normal

Hi,
when ejecting a drive, thunar crashes (both with context menu 'eject', and the
eject button)

[18950.426861] Thunar[3027]: segfault at 0 ip 00005615a96c98cc sp
00007ffd2dbd7320 error 4 in thunar[5615a9640000+92000] likely on CPU 7 (core 3,
socket 0)
[18950.426895] Code: f3 48 83 ec 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 48 c7 44 24 20 00 00 00 00 48 85 f6 0f 84 77 02 00 00 48 8b 06 <48> 39 10
0f 84 f1 01 00 00 4c 8b bf 28 01 00 00 4c 39 fe 0f 84 cb


Most of the time this happens when I eject it for the first time in that
session, when I try it a second time it works just fine.


-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunar depends on:
ii desktop-file-utils 0.26-1
ii exo-utils 4.18.0-1
ii libatk1.0-0 2.46.0-5
ii libc6 2.36-9+deb12u3
ii libcairo2 1.16.0-7
ii libexo-2-0 4.18.0-1
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.74.6-2
ii libgtk-3-0 3.24.38-2~deb12u1
ii libgudev-1.0-0 237-2
ii libice6 2:1.0.10-1
ii libnotify4 0.8.1-1
ii libpango-1.0-0 1.50.12+ds-1
ii libsm6 2:1.2.3-1
ii libthunarx-3-0 4.18.4-1
ii libxfce4ui-2-0 4.18.2-2
ii libxfce4util7 4.18.1-2
ii libxfconf-0-3 4.18.0-2
ii shared-mime-info 2.2-1
ii thunar-data 4.18.4-1

Versions of packages thunar recommends:
ii dbus-user-session [default-dbus-session-bus] 1.14.10-1~deb12u1
ii dbus-x11 [dbus-session-bus] 1.14.10-1~deb12u1
ii gvfs 1.50.3-1
ii libxfce4panel-2.0-4 4.18.2-1
ii policykit-1-gnome [polkit-1-auth-agent] 0.105-8
ii thunar-volman 4.18.0-1
ii tumbler 4.18.0-1
ii udisks2 2.9.4-4
ii xdg-user-dirs 0.18-1

Versions of packages thunar suggests:
ii gvfs-backends 1.50.3-1
ii thunar-archive-plugin 0.5.0-1
ii thunar-media-tags-plugin 0.3.0-2+b1

-- no debconf information

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 2024-04-10 at 08:37 -0300, k02 wrote:
> Hi,
> 
> Since this bug was very annoying/frequent, a few weeks ago I decided to 
> format my machine entirely (I've been using debian on this machine for 
> over 4 years without reinstall and using very old config files).
> This bug and other annoyances are gone now,  so if something happens I 
> prefer to open a new bug.

Hi, thanks for the feedback, I'm closing the bug then.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYZLhcACgkQ3rYcyPpX
RFt+Awf/eYQ9fvg+58FKf5pZxZ+Tm3T/CgF4rAwNNRYUiVI/CU8ZWOEprgC0JVoj
sygQQ7BO/ljAQlcLSKEncgsAz1EyyIKeb0PXwFnbDmNLw31En97Wh3itIe48V2lm
akbnOQI7XXUZzGCX7xRwphQ56B+767X8ab4Vi0ayIrlbdxVUe1qUTgk/uJ2svmPE
xtYG4cR9MD79cbEUEDxcmN0kEsj8MiKGjwe7/kRtfSzfvODyXNBEgxQrogbHFMpd
J6HD9oIQ6flokTXL7vLJUBdeWiZe1AAjV4SUaCeHEl2ahF0ds1lwwsJTF3nio3MN
DoZObJe8EB2pJM24UA3HswY+qRgN5w==
=teHV
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to