The "draksnapshot-config" program crashed. Drakbug-13.63 caught it. nothing Backtrace was: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files 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.1/MDV/Snapshot/Hal.pm:54 MDV::Snapshot::Hal::find_removable_volumes() called from /usr/sbin/draksnapshot-config:111 Kernel version = 3.1.0-desktop586-0.rc9.1.mga2 Distribution=Mageia release 2 (Cauldron) for i586 CPU=AMD Athlon(tm) II X4 640 Processor
Bug assigned to the package maintainer
Assignee: bugsquad => thierry.vignaud
*** Bug 3204 has been marked as a duplicate of this bug. ***
CC: (none) => pietrotux88
*** Bug 3853 has been marked as a duplicate of this bug. ***
CC: (none) => marja11
*** Bug 4463 has been marked as a duplicate of this bug. ***
CC: (none) => bigdavesr
*** Bug 4987 has been marked as a duplicate of this bug. ***
CC: (none) => baiteche.kamel
*** Bug 5447 has been marked as a duplicate of this bug. ***
CC: (none) => matcle
seems it require hal, maybe we should drop completly from the distro ?
*** Bug 5490 has been marked as a duplicate of this bug. ***
CC: (none) => ab.kde
*** Bug 2187 has been marked as a duplicate of this bug. ***
CC: (none) => jeffrobinsSAE
*** Bug 5635 has been marked as a duplicate of this bug. ***
CC: (none) => nrcefe
*** Bug 5762 has been marked as a duplicate of this bug. ***
*** Bug 5868 has been marked as a duplicate of this bug. ***
CC: (none) => atlee
*** Bug 5896 has been marked as a duplicate of this bug. ***
CC: (none) => it
Depends on: (none) => 5901
It wouldn't be such a big job to port from hal to udisks
Keywords: (none) => Junior_job
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
H, Same as bug 6095 and bug 6099 ? If yes better to keep this one and marking duplicates for bug 6095 and bug 6099 ? Rmk: I confirm the problem with the Mageia 2
CC: (none) => mailinglistsduraph
*** Bug 6099 has been marked as a duplicate of this bug. ***
CC: (none) => seadx6
*** Bug 6095 has been marked as a duplicate of this bug. ***
CC: (none) => rfsrossi
Hi, 1. I add here the content of the drakbug screen 2. I add the content (as explain in drakbug) of the lspcidrake -v command Question: I also add the drakxtools-debug package but ... I don't see something special in drakbug to add information about this so i forgot something ?
Created attachment 2383 [details] Bug 3032 - content of drakbug window
Created attachment 2384 [details] Bug 3032 - result of command lspcidrake -v
we don't need info, draksnapshot, is only still using hal, which is now deprecated
Keywords: NEEDINFO => (none)
Ok so if no more draksnapshot (I just saw the bug 5901) nothing else in draktools ?
you mean backup tools make by mdv/mga ? no :) but there is a lot of alternative, and this one is only a gui for rsnapshot.
Oki doki Just to be sure and so i must to replace what i used till now ;) thx
*** Bug 6127 has been marked as a duplicate of this bug. ***
CC: (none) => jansen.eric
*** Bug 6158 has been marked as a duplicate of this bug. ***
CC: (none) => tomkolp
*** Bug 6177 has been marked as a duplicate of this bug. ***
CC: (none) => epilip
hal is deprecated, but IS present/installable/working for Mageia 2. Draksnapshot works fine if hal is installed, and the annoying/confusing dbus messages go away. Consider installing hal as a temporary fix until draksnapshot or its successor becomes available. (I just tend to use rsync for partials and partclone for full images, the FC16+ partclone RPMs work fine, as do binaries extracted from debian/Ubuntu debs) Just a user, YMMV.
CC: (none) => gjmcgee
It would probably be ~easy to add an rsync backup option in the mc F2 menu... will play with that. It IS a GUI ;-)
*** Bug 6320 has been marked as a duplicate of this bug. ***
CC: (none) => ajv
*** Bug 6324 has been marked as a duplicate of this bug. ***
CC: (none) => mageia
*** Bug 6325 has been marked as a duplicate of this bug. ***
CC: (none) => jlbryenton
Hardware: i586 => AllWhiteboard: (none) => MGA2TOO
*** Bug 6339 has been marked as a duplicate of this bug. ***
CC: (none) => djmathos
*** Bug 6393 has been marked as a duplicate of this bug. ***
CC: (none) => gwen.lohezic
CC: (none) => struggtown
*** Bug 6366 has been marked as a duplicate of this bug. ***
CC: (none) => jall.vigo
*** Bug 6399 has been marked as a duplicate of this bug. ***
CC: (none) => claude.perrot
*** Bug 6492 has been marked as a duplicate of this bug. ***
CC: (none) => tommylee567
*** Bug 6499 has been marked as a duplicate of this bug. ***
CC: (none) => alain.guirauton
*** Bug 6555 has been marked as a duplicate of this bug. ***
CC: (none) => chrisdersch
*** Bug 6638 has been marked as a duplicate of this bug. ***
CC: (none) => mark.tamkun
Why don't we reintroduce HAL as a dependency for draksnapshot until we have a better fix? This is probably confusing a lot of folks, ending this is simple...
*** Bug 6654 has been marked as a duplicate of this bug. ***
CC: (none) => raphgro
I think this is a release blocker due to the crash that makes this module unusable.
Priority: Normal => release_blocker
*** Bug 6658 has been marked as a duplicate of this bug. ***
CC: (none) => simplew8
draksnapshot-0.20.3-3.1.mga2 was just submitted to updates_testing. Please test.
Status: NEW => ASSIGNEDCC: (none) => lists.jjorgeAssignee: thierry.vignaud => qa-bugs
for cauldron the real fix would be to port the code to udisk instead of hal
CC: (none) => dmorganec
Many thanks José, QA please don't worry about all other bugs. Suggested advisory: Updates draksnapshot add a required for hal which was missing previously. srpm: draksnapshot-0.20.3-3.1.mga2.src.rpm thanks
Priority: release_blocker => NormalVersion: Cauldron => 2Whiteboard: MGA2TOO => (none)Severity: normal => major
*** Bug 6696 has been marked as a duplicate of this bug. ***
CC: (none) => danb
*** Bug 6698 has been marked as a duplicate of this bug. ***
CC: (none) => mikeumo
I tried draksnapshot-0.20.3-3.1.mga2.src.rpm It installed OK, and I could set up the directories for backup, but it did not start any backups and the draksnapshot-applet does not appear in the system tray even though it is running and haldaemon is running. Nor is there anything defined in the "Backup Intervals" section of /etc/rsnapshot.conf and /var/log/rsnapshot puts out this message once an hour. /usr/bin/rsnapshot hourly: ERROR: At least one backup level must be set. rsnapshot can not continue.
CC: (none) => derekjenn
Please again, we know that there is a lot a bug against draksnapshot. So the idea is to valid only this one (drakbug coming after the install/launch), no to fix the other bugs (already filled for most of them if you search in the bugzilla).
CC: derekjenn => (none)
*** Bug 6721 has been marked as a duplicate of this bug. ***
CC: (none) => cromaric
Ok, this one is a bit uncomfortable to validate given all the bugs there are, but seeing the amount of duplicates users are creating, there's a need to validate it quickly. After installing the update candidate and starting the haldaemon service, draksnapshot doesn't crash anymore. Testing complete x86_64
CC: (none) => stormi
Whiteboard: (none) => MGA2-64-OK
Just one question though, can the addition of hal to a user's system have bad consequences?
(In reply to comment #55) > Just one question though, can the addition of hal to a user's system have bad > consequences? I have no ideas for that, tmb asked the same on the ml, sorry
Comment #54 is a work around for users that need a quick fix, but it's not a general solution. There has to be a vaild reason why hal was removed from the standard installation. (In reply to comment #55) > Just one question though, can the addition of hal to a user's system have bad > consequences? AFAIK, hal development is dead due to systemd, udev and other newer projects that have merged the hal logic. Please keep this bug open.
The following packages will require linking if this is pushed. hal-0.5.14-6.mga1 (Core Release (distrib1)) hal-info-0.0-5.20091130.3.mga1 (Core Release (distrib1)) libhal1-0.5.14-6.mga1 (Core Release (distrib1)) libpolkit2-0.9-8.mga1 (Core Release (distrib1)) policykit-0.9-8.mga1 (Core Release (distrib1)) usbutils-005-1.mga2 (Core Release (distrib1))
CC: (none) => davidwhodgins
Reproduced mga2 i586 and confirmed the update fixes it once the haldaemon service is started. I found I already had hal installed so I guess it doesn't do any harm. Confirmed the links in comment 58 I think we should validate this one. Any objections?
(In reply to comment #59) > Reproduced mga2 i586 and confirmed the update fixes it once the haldaemon > service is started. > > I found I already had hal installed so I guess it doesn't do any harm. > > Confirmed the links in comment 58 > > I think we should validate this one. > > Any objections? I hope it is not going to be pushed. Until Bug 5121 is fixed draksnapshot remains broken. If we push it we will be replacing one broken package with a new broken package, but one which has an additional service running and sends the root user an email every hour announcing it is broken.
hmm perhaps not such a good idea then! Adding a depends. Is anybody working on bug 5121?
Depends on: (none) => 5121
Adding depends for bug 2317 too for the linking.
Depends on: (none) => 2317
(In reply to comment #61) > hmm perhaps not such a good idea then! > > Adding a depends. Is anybody working on bug 5121? I just took a look at 5121 and could see why backups are failing. I submitted a patch.
This is not only draksnapshot-config to have be fixed ... $ grep -r "MDV::Snapshot::Hal" . ./lib/MDV/Snapshot/Hal.pm:package MDV::Snapshot::Hal; ./draksnapshot-config:use MDV::Snapshot::Hal; ./draksnapshot-applet:use MDV::Snapshot::Hal;
The so called Gnome trend breaks a lot of stuff. I can see that there is still udisks 1.0.4 in Cauldron, but we would get a similiar issue with udisks2 cause of an API change again. https://igurublog.wordpress.com/2012/03/11/udisks2-another-loss-for-linux/
*** Bug 6837 has been marked as a duplicate of this bug. ***
CC: (none) => tsuzuki_asato_ynm
Please not validate this update until packagers decide whether pushing hal to most mga2 systems is OK or not.
Whiteboard: MGA2-64-OK => MGA2-64-OK?
Whiteboard: MGA2-64-OK? => MGA2-64-OK? feedback
According to packager comments from Mageia devel mailing list, this fix is not an acceptable one. Quoting Thierry Vignaud: "That's not the fix. The proper fix is to adapt to udisks. Shouldn't be hard. See eg:http://svnweb.mageia.org/soft/perl-Hal-Cdroms/trunk/lib/Hal/Cdroms.pm?view=log" Anyone wants to try to fix it? Since it can't stay assigned to QA, I'm assigning it to current maintainer (tv), but of course anyone else could try and fix it.
Assignee: qa-bugs => thierry.vignaud
Advertisement: Backintime has all features that draksnapshot has and even a lot more. It's python based and has no direct dependency to udisks. There's GUI for both Gnome/Xfce and KDE. http://backintime.le-web.org/
"Raphael Groner 2012-08-08 12:54:22 CEST Advertisement: Backintime has all features that draksnapshot has and even a lot more. It's python based and has no direct dependency to udisks. There's GUI for both Gnome/Xfce and KDE. http://backintime.le-web.org/" Thanks for the tip, will be trying it ASAP. It would be a better perm. solution if it works well.
backintime-kde4 builds (deleting gnome entry at least on MY system) /looks/appears to work nice, uses rsync as the gods intended.. Needs packaged as an RPM, but very promising.
(In reply to comment #71) > backintime-kde4 builds (deleting gnome entry at least on MY system) > /looks/appears to work nice, uses rsync as the gods intended.. > > Needs packaged as an RPM, but very promising. It is packaged already: http://mageia.madb.org/package/list/t_search/backintime
No need to build anything: # urpmi backintime-kde ⦠or ⦠# urpmi backintime-gnome ⦠done :) Well, we should concentrate this bug on draksnapshot, shouldn't we?
Well, the "fix" of simply using backintime as a direct replacement for draksnapshot appears a more viable alternative than actually fixing draksnapshot, and could possibly be accomplished with a symlink with no deps.(or along those lines) The feature set is equivalent (better actually) and it seems very easy to use. Backintime or something very much like it should be considered as a drop in replacement.
Didn't think to look, thanks. Note that installing backintime-kde4 from urpmi is pulling in 44 packages that I did not need to compile/run it compiling from source directly, it's running fine. ...the requires may need a little pruning.
(In reply to comment #74) > Backintime or something very much like it should be considered as a drop in > replacement. That's exactly my opinion. At least, that solution sounds fair for Mga3/Cauldron. +1 (In reply to comment #75) > Note that installing backintime-kde4 from urpmi is pulling in 44 packages that > I did not need to compile/run it compiling from source directly, it's running > fine. Sorry, I did not try the KDE GUI. Only Xfce (=Gnome GUI) here. > > ...the requires may need a little pruning. You should report that to the maintainer as a new bug.
*** Bug 7028 has been marked as a duplicate of this bug. ***
CC: (none) => jmvanham
*** Bug 7027 has been marked as a duplicate of this bug. ***
CC: (none) => michel.kikkine
*** Bug 7044 has been marked as a duplicate of this bug. ***
CC: (none) => msdobrescu
*** Bug 7079 has been marked as a duplicate of this bug. ***
CC: (none) => markb
*** Bug 7138 has been marked as a duplicate of this bug. ***
CC: (none) => philippe.l
Source RPM: draksnapshot-0.20.3-3.mga2 => draksnapshot-0.20.3-3.1.mga2.src.rpm
*** Bug 7284 has been marked as a duplicate of this bug. ***
CC: (none) => tnthunt
this bug is still in cauldron, too, with draksnapshot-0.20.3-4.mga3
Version: 2 => CauldronSource RPM: draksnapshot-0.20.3-3.1.mga2.src.rpm => draksnapshot-0.20.3-3.1.mga2.src.rpm draksnapshot-0.20.3-4.mga3.src.rpmWhiteboard: MGA2-64-OK? feedback => MGA2TOO MGA2-64-OK? feedback
*** Bug 7404 has been marked as a duplicate of this bug. ***
CC: (none) => defcon-linux
*** Bug 7408 has been marked as a duplicate of this bug. ***
CC: (none) => manu
*** Bug 7432 has been marked as a duplicate of this bug. ***
CC: (none) => bert.mooreii
CC: lists.jjorge => (none)
*** Bug 7431 has been marked as a duplicate of this bug. ***
CC: (none) => franckcas
CC: raphgro => (none)
*** Bug 7468 has been marked as a duplicate of this bug. ***
CC: (none) => gerard.calas
*** Bug 7542 has been marked as a duplicate of this bug. ***
CC: (none) => mauriciopachecom
I have fixed the crash in draksnapshot-0.20.3-5.mga3.noarch for the case where HAL is not running. I have also removed the HAL dependency, since it is really time we get rid of it. draksnapshot should work without it, the only downside is that the user has to manually enter the mountpoint. I have opened a separate bug report about the migration to udisks2 (since this is a separate issue from the "draksnapshot-config crashed when hal is not running" bug): Bug 7565 - draksnapshot should use udisks2 instead of HAL to detect removable devices
Status: ASSIGNED => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED
Nice, and what about the package in mag2? :)
This bug is opened against cauldron, please clone it for the Mageia 2 update process.
Blocks: (none) => 7633
(In reply to comment #91) > Nice, and what about the package in mag2? :) (In reply to comment #92) > This bug is opened against cauldron, please clone it for the Mageia 2 update > process. OK, I cloned it because this one is already 92 comments long. Short reports don't need to be cloned, but can just be reopened and have the version changed. The clone is bug #7633
> OK, I cloned it because this one is already 92 comments long. Short reports > don't need to be cloned, but can just be reopened and have the version changed. I don't really agree about that, it is useful to have per-version bug status. Even if it is cumbersome to clone the bug for each affected version, it gives a clear view of which version is still affected, and where the update progress is.
(In reply to comment #94) > > OK, I cloned it because this one is already 92 comments long. Short reports > > don't need to be cloned, but can just be reopened and have the version changed. > > I don't really agree about that, it is useful to have per-version bug status. > Even if it is cumbersome to clone the bug for each affected version, it gives a > clear view of which version is still affected, and where the update progress > is. I agree with you Olivier, but it's hard to enforce such rules to packagers, especially when such rules could appear as coming from QA team :)
(In reply to comment #95) > (In reply to comment #94) > > > OK, I cloned it because this one is already 92 comments long. Short reports > > > don't need to be cloned, but can just be reopened and have the version changed. > > > > I don't really agree about that, it is useful to have per-version bug status. > > Even if it is cumbersome to clone the bug for each affected version, it gives a > > clear view of which version is still affected, and where the update progress > > is. > > I agree with you Olivier, but it's hard to enforce such rules to packagers, > especially when such rules could appear as coming from QA team :) bugsquad used to enforce it, or do the cloning themselves, but when Mageia 2 was born, and many bugs were valid for cauldron and Mageia 2, we would have had to clone many more bugs than we possibly could, so we decided to set the bug to the highest version (cauldron) and put MGA2TOO on the whiteboard, to indicate it is valid for Mageia 2, too. We use MGA1TOO when it is valid for 1, too. if you want us to revert to how we did it before, then please help find new bug squad members who'll be active (preferably a lot more active on bug reports than I'm nowadays)
@ blino btw, you could have done the cloning yourself, too ;)
this bug was closed, because it lives on as bug 7633
Resolution: FIXED => MOVED