Bug 6492 - draksnapshot-config crashed
Summary: draksnapshot-config crashed
Status: RESOLVED DUPLICATE of bug 3032
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-17 19:23 CEST by Tim Vels
Modified: 2012-06-18 16:27 CEST (History)
1 user (show)

See Also:
Source RPM: draksnapshot-0.20.3-3.mga2
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Tim Vels 2012-06-17 19:23:23 CEST 
The "draksnapshot-config" program crashed. Drakbug-14.21 caught it.

just installed and ran, upon opening it it just stopped. nothing came on.

org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.14.1/x86_64-linux-thread-multi/Net/DBus/Binding/Connection.pm:209
Net::DBus::Binding::Connection::send_with_reply_and_block() called from /usr/lib/perl5/vendor_perl/5.14.1/x86_64-linux-thread-multi/Net/DBus/RemoteObject.pm:442
Net::DBus::RemoteObject::_call_method() called from /usr/lib/perl5/vendor_perl/5.14.1/x86_64-linux-thread-multi/Net/DBus/RemoteObject.pm:358
Net::DBus::RemoteObject::AUTOLOAD() called from /usr/lib/perl5/vendor_perl/5.14.1/x86_64-linux-thread-multi/Net/DBus.pm:315
Net::DBus::get_service() called from /usr/lib/perl5/vendor_perl/5.14.2/MDV/Snapshot/Hal.pm:54
MDV::Snapshot::Hal::find_removable_volumes() called from /usr/sbin/draksnapshot-config:111

Theme name: oxygen-gtk
Kernel version = 3.3.6-desktop-2.mga2
Distribution=Mageia release 2 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
Comment 1 Manuel Hiebel 2012-06-18 16:27:12 CEST 
you need hal

*** This bug has been marked as a duplicate of bug 3032 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.