[yast-devel] possible bug report: snapper dumps core
Hey, I'm running snapper on Arch Linux, using lvm thin provisioning for
the snapshots. It seems to be working fine (I can create, mount,
delete,... snapshots). However, after a command completes, some boost
thread seems to die:
[system log excerpt]
Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Activating
service name='org.opensuse.Snapper' (using servicehelper)
Feb 05 06:41:49 mammoth dbus[477]: [system] Activating service
name='org.opensuse.Snapper' (using servicehelper)
Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Successfully
activated service 'org.opensuse.Snapper'
Feb 05 06:41:49 mammoth dbus[477]: [system] Successfully activated service
'org.opensuse.Snapper'
Feb 05 06:41:50 mammoth dbus-daemon[477]: terminate called after throwing
an instance of
'boost::exception_detail::clone_impl
' what(): boost thread: thread not joinable: Invalid argument Aborted (core dumped)
If this is the wrong place for such a report, or, since it's not suse-related, there is no general interest, please tell me. Otherwise, are there other reports that might help identify the problem? Regards, Carsten Bohnens -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, Feb 05, 2013 at 07:09:37AM +0100, carsten@ags.tu-bs.de wrote:
Hey, I'm running snapper on Arch Linux, using lvm thin provisioning for the snapshots. It seems to be working fine (I can create, mount, delete,... snapshots). However, after a command completes, some boost thread seems to die:
what(): boost thread: thread not joinable: Invalid argument Aborted (core dumped)
Thanks for reporting this. I don't have to problem here but I have found a similar bug (https://github.com/lodle/Desurium/issues/348). Apparently the boost thread interface has changed with boost 1.52. Could you try to integrate this patch: diff --git a/server/Background.cc b/server/Background.cc index dfc06e4..eada0e7 100644 --- a/server/Background.cc +++ b/server/Background.cc @@ -42,7 +42,9 @@ Backgrounds::Backgrounds() Backgrounds::~Backgrounds() { thread.interrupt(); - thread.join(); + + if (thread.joinable()) + thread.join(); } Another place to check for thread.joinable() could be Client::~Client().
If this is the wrong place for such a report, or, since it's not suse-related, there is no general interest, please tell me.
If the patch doesn't help could you please open an issue on
github.
Regards,
Arvin
--
Arvin Schnell,
participants (2)
-
Arvin Schnell -
carsten＠ags.tu-bs.de