Bug 10306 - draksnapshot-config crashed
Summary: draksnapshot-config crashed
Status: RESOLVED DUPLICATE of bug 7633
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-27 03:04 CEST by padula
Modified: 2013-05-27 10:42 CEST (History)
1 user (show)

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


Attachments

Description padula 2013-05-27 03:04:54 CEST
The "draksnapshot-config" program crashed. Drakbug-14.22.3 caught it.

So foi abrir o programa, já apareceu esse bug...

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/i386-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/i386-linux-thread-multi/Net/DBus/RemoteObject.pm:442
Net::DBus::RemoteObject::_call_method() called from /usr/lib/perl5/vendor_perl/5.14.1/i386-linux-thread-multi/Net/DBus/RemoteObject.pm:358
Net::DBus::RemoteObject::AUTOLOAD() called from /usr/lib/perl5/vendor_perl/5.14.1/i386-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.4.45-desktop586-1.mga2
Distribution=Mageia release 2 (Official) for i586
CPU=AMD Sempron(tm)   2800+
Comment 1 padula 2013-05-27 03:06:10 CEST
I could not open the backup program, the bug has already
Comment 2 Sander Lepik 2013-05-27 10:42:19 CEST
Duplicate.

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

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.