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

2017-08-29 Thread 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#705334: steam: fresh installation fails to start after initial update

2013-04-13 Thread Daniel Schaal
Package: steam
Version: 1.0.0.33-1
Followup-For: Bug #705334

Hi,

The problem seems to be that newer versions of steam depend on libSDL2
(which is available in debian), but also on the image, mixer, net and ttf
libraries for SDL. I compiled them from the upstream source and after
installing them (and some other i386 libs like libpango, libgtk, ...)
steam starts without problems.

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (103, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9.0-rc6 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- debconf information:
* steam/question: I AGREE
* steam/license:
  steam/purge:


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#755394: base-files: move of os-release to /usr/lib breaks dracut initrd

2014-07-20 Thread Daniel Schaal
Package: base-files
Version: 7.4
Severity: critical
Justification: breaks the whole system

Using a dracut initrd the move of os-release to /usr/lib breaks the boot, as
systemd can't find the os-release file, as it is located under 
/sysroot/usr/lib/os-release,
but the symlink points to /usr/lib/os-release.

The error message is:

"Specified switch root path /sysroot does not seem to be an OS tree. 
/etc/os-release is missing."

Replacing the absolute symlink with a relative symlink /etc/os-release -> 
../usr/lib/os-release
fixes the boot here.

-- Daniel

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (103, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.1.1+dfsg-1
ii  mawk [awk]  1.3.3-17

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org