Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?))

[Ben Caradoc-Davies]

I can confirm that udisks2 2.7.2-2 fixes the thunar problems that I 
reported above: I see only the "usual" filesystems and can mount and 
unmount removable devices as expected.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Ben Caradoc-Davies]

udisks2 is now uninstallable on sid because of #873748:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Michał Milanowski]

This solves issue for me as well. aprropriate libblockdev-* libs
should be added as
required by udisks2

On Wed, 30 Aug 2017 07:37:00 +0200 Daniel Schaal  wrote:
> I'm experiencing the same issue. I attached the log output and the
> backtrace of the coredump.
>
> After installing the missing plugins (libblockdev-* packages) it
> complains about, I don't get this issue anymore.
>
> syslog output:
> -
> Starting Disk Manager...
> udisks daemon version 2.7.2 starting
> failed to load module mdraid: libbd_mdraid.so.2: cannot open shared
> object file: No such file or directory
> Cannot load the part plugin: The 'sgdisk' utility is not available
> failed to load module fs: libbd_fs.so.2: cannot open shared object file:
> No such file or directory
> Error initializing libblockdev library: Failed to load plugins
> (g-bd-init-error-quark, 0)
> traps: udisksd[2390] trap int3 ip:7f77dd711921 sp:7ffce682cbd0 error:0
> in libglib-2.0.so.0.5306.0[7f77dd6c1000+111000]
> Started Process Core Dump (PID 2395/UID 0).
> udisks2.service: Main process exited, code=dumped, status=5/TRAP
> Failed to start Disk Manager.
> udisks2.service: Unit entered failed state.
> udisks2.service: Failed with result 'core-dump'.
> --
>
> Backtrace:
> -
> #0  _g_log_abort (breakpoint=breakpoint@entry=1) at
> ../../../../glib/gmessages.c:554
> #1  0x7fd1ff261f41 in g_log_writer_default (log_level=6,
> log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7ffc32a375a0,
> n_fields=n_fields@entry=3, user_data=user_data@entry=0x0)
>  at ../../../../glib/gmessages.c:2628
> #2  0x7fd1ff2604be in g_log_structured_array
> (log_level=G_LOG_LEVEL_ERROR, fields=0x7ffc32a375a0, n_fields=3) at
> ../../../../glib/gmessages.c:1941
> #3  0x7fd1ff2607b7 in g_log_structured (log_domain=0x55ea532e0c08
> "udisks", log_level=G_LOG_LEVEL_ERROR) at ../../../../glib/gmessages.c:1768
> #4  0x55ea532d8e9b in udisks_log ()
> #5  0x55ea532ad74f in ?? ()
> #6  0x7fd1ff538510 in g_object_new_internal
> (class=class@entry=0x55ea53e38c00, params=params@entry=0x7ffc32a38060,
> n_params=n_params@entry=4) at ../../../../gobject/gobject.c:1821
> #7  0x7fd1ff53a4e0 in g_object_new_valist
> (object_type=94464918131104, first_property_name=,
> var_args=var_args@entry=0x7ffc32a381b0) at
> ../../../../gobject/gobject.c:2104
> #8  0x7fd1ff53a859 in g_object_new (object_type=,
> first_property_name=) at ../../../../gobject/gobject.c:1624
> #9  0x55ea532add55 in udisks_daemon_new ()
> #10 0x55ea532aceab in ?? ()
> #11 0x7fd1ff83de74 in connection_get_cb (source_object= out>, res=0x55ea53e41030, user_data=0x55ea53e34e70) at
> ../../../../gio/gdbusnameowning.c:487
> #12 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41030) at
> ../../../../gio/gtask.c:1145
> #13 0x7fd1ff8029f6 in g_task_return (task=0x55ea53e41030,
> type=) at ../../../../gio/gtask.c:1203
> #14 0x7fd1ff830b92 in bus_get_async_initable_cb

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Michał Milanowski]

Exactly the same issue on Cinnamon. Cinnamon starts very long and I
can see following in xsession log:

Error creating proxy: Error calling StartServiceByName
org.gtk.vfs.UDisks2VolumeMonitor Timeout was reached

However, Cinnamon finally boots after timeout. But, as somebody
mentioned above, all unneceassary devices like systemd are visible in
file manager. Please make this bug serious. For now, need to downgrade
udisks2 to Testing version.

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Daniel Schaal]

I'm experiencing the same issue. I attached the log output and the 
backtrace of the coredump.


After installing the missing plugins (libblockdev-* packages) it 
complains about, I don't get this issue anymore.


syslog output:
-
Starting Disk Manager...
udisks daemon version 2.7.2 starting
failed to load module mdraid: libbd_mdraid.so.2: cannot open shared 
object file: No such file or directory

Cannot load the part plugin: The 'sgdisk' utility is not available
failed to load module fs: libbd_fs.so.2: cannot open shared object file: 
No such file or directory
Error initializing libblockdev library: Failed to load plugins 
(g-bd-init-error-quark, 0)
traps: udisksd[2390] trap int3 ip:7f77dd711921 sp:7ffce682cbd0 error:0 
in libglib-2.0.so.0.5306.0[7f77dd6c1000+111000]

Started Process Core Dump (PID 2395/UID 0).
udisks2.service: Main process exited, code=dumped, status=5/TRAP
Failed to start Disk Manager.
udisks2.service: Unit entered failed state.
udisks2.service: Failed with result 'core-dump'.
--

Backtrace:
-
#0  _g_log_abort (breakpoint=breakpoint@entry=1) at 
../../../../glib/gmessages.c:554
#1  0x7fd1ff261f41 in g_log_writer_default (log_level=6, 
log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7ffc32a375a0, 
n_fields=n_fields@entry=3, user_data=user_data@entry=0x0)

at ../../../../glib/gmessages.c:2628
#2  0x7fd1ff2604be in g_log_structured_array 
(log_level=G_LOG_LEVEL_ERROR, fields=0x7ffc32a375a0, n_fields=3) at 
../../../../glib/gmessages.c:1941
#3  0x7fd1ff2607b7 in g_log_structured (log_domain=0x55ea532e0c08 
"udisks", log_level=G_LOG_LEVEL_ERROR) at ../../../../glib/gmessages.c:1768

#4  0x55ea532d8e9b in udisks_log ()
#5  0x55ea532ad74f in ?? ()
#6  0x7fd1ff538510 in g_object_new_internal 
(class=class@entry=0x55ea53e38c00, params=params@entry=0x7ffc32a38060, 
n_params=n_params@entry=4) at ../../../../gobject/gobject.c:1821
#7  0x7fd1ff53a4e0 in g_object_new_valist 
(object_type=94464918131104, first_property_name=, 
var_args=var_args@entry=0x7ffc32a381b0) at 
../../../../gobject/gobject.c:2104
#8  0x7fd1ff53a859 in g_object_new (object_type=, 
first_property_name=) at ../../../../gobject/gobject.c:1624

#9  0x55ea532add55 in udisks_daemon_new ()
#10 0x55ea532aceab in ?? ()
#11 0x7fd1ff83de74 in connection_get_cb (source_object=out>, res=0x55ea53e41030, user_data=0x55ea53e34e70) at 
../../../../gio/gdbusnameowning.c:487
#12 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41030) at 
../../../../gio/gtask.c:1145
#13 0x7fd1ff8029f6 in g_task_return (task=0x55ea53e41030, 
type=) at ../../../../gio/gtask.c:1203
#14 0x7fd1ff830b92 in bus_get_async_initable_cb 
(source_object=0x55ea53e42070, res=, 
user_data=0x55ea53e41030) at ../../../../gio/gdbusconnection.c:7302
#15 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41100) at 
../../../../gio/gtask.c:1145
#16 0x7fd1ff802009 in complete_in_idle_cb (task=0x55ea53e41100) at 
../../../../gio/gtask.c:1159
#17 0x7fd1ff259dd5 in g_main_dispatch (context=0x55ea53e34200) at 
../../../../glib/gmain.c:3148
#18 g_main_context_dispatch (context=context@entry=0x55ea53e34200) at 
../../../../glib/gmain.c:3813
#19 0x7fd1ff25a1a0 in g_main_context_iterate 
(context=0x55ea53e34200, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../../glib/gmain.c:3886
#20 0x7fd1ff25a4b2 in g_main_loop_run (loop=0x55ea53e341d0) at 
../../../../glib/gmain.c:4082

#21 0x55ea532acc21 in main ()
---

Thanks,
Daniel

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Ben Caradoc-Davies]

udisks2 2.7.2-1 also severely impacted the functionality of thunar on 
sid. All filesystems were shown in the sidebar, including things like 
binfmt (about 20-30 or so filsystems). Removable devices were not shown, 
and no eject icon was shown when removable devices were mounted at the 
command line. Workaround was to downgrade to 2.6.5-2. Before filing a 
separate bug report, I will see if the fix for this issue resolves the 
thunar issues.


Downgrade and hold procedure for the benefit of other readers:

I added the following to /etc/apt/source.list:
deb http://snapshot.debian.org/archive/debian/20170827T034402Z/ sid main

Then ran the following to downgrade and hold:

apt-get update
apt-get install udisks2=2.6.5-2 libudisks2-0=2.6.5-2
apt-mark hold udisks2 libudisks2-0

A system restart was required.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Diederik de Haas]

This is essentially a +1 message and downgrading udisks2 + libudisks2-0 to the 
testing version fixed it for me too

signature.asc
Description: This is a digitally signed message part.

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[debianuser]

Package: udisks2
Version: 2.6.5-2
Severity: important

Dear Maintainer,

Upon an upgrade in sid, my computer gave a message, something like "disk 
manager failed" or something like that, and also "see systemctl status 
udisks2.service". When trying to boot into KDE Plasma I had no taskbar and 
could not open programs with alt+f2 that I was aware of. I appear to have fixed 
the problem by downgrading udisks2 to testing, in that I now have a functioning 
GUI again. 


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages udisks2 depends on:
ii  dbus   1.11.16+really1.10.22-1
ii  init-system-helpers1.49
ii  libacl12.2.52-3+b1
ii  libatasmart4   0.19-4+b1
ii  libc6  2.24-17
ii  libglib2.0-0   2.53.6-1
ii  libgudev-1.0-0 230-3
ii  libpam-systemd 234-2.3
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  libsystemd0234-2.3
ii  libudisks2-0   2.7.2-1
ii  parted 3.2-17
ii  udev   234-2.3

Versions of packages udisks2 recommends:
ii  dosfstools   4.1-1
ii  eject2.1.5+deb1+cvs20081104-13.2
ii  exfat-utils  1.2.7-1
ii  gdisk1.0.1-1
ii  ntfs-3g  1:2016.2.22AR.2-2
ii  policykit-1  0.105-18

Versions of packages udisks2 suggests:
pn  btrfs-progs | btrfs-tools  
pn  cryptsetup-bin 
pn  mdadm  
pn  reiserfsprogs  
pn  xfsprogs   

-- no debconf information