https://bugzilla.novell.com/show_bug.cgi?id=464453 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c1 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka@novell.com |bnc-team-screening@forge.provo.novell.com --- Comment #1 from Danny Kukawka 2009-01-08 06:58:17 MST --- I guess it need to be: hal-set-property --udi /org/freedesktop/Hal/devices/computer --key storage.disable_volume_handling --bool true And if this isn't working, it's a problem of the desktop system since it's only a hint for e.g. GNOME or KDE to stop automounting. It has nothing to do with the mount handling in HAL itself. Reassigning back to GNOME. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User puzel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c3 --- Comment #3 from Petr Uzel 2009-01-08 07:06:03 MST --- (In reply to comment #1 from Danny Kukawka)

I guess it need to be:

hal-set-property --udi /org/freedesktop/Hal/devices/computer --key storage.disable_volume_handling --bool true

I will retest this.

And if this isn't working, it's a problem of the desktop system since it's only a hint for e.g. GNOME or KDE to stop automounting. It has nothing to do with the mount handling in HAL itself.

This would explain why it happens only in GNOME live CD (as reported) - I will verify this myself ASAP -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User puzel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c5 Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical --- Comment #5 from Petr Uzel 2009-01-08 07:46:34 MST --- KDE live CD: installation seems to work fine. The real difference is that KDE does not mount any partitions - even the Windows partition is not mounted. This confirms that the issue is GNOME specific. Increasing severity to critical as this breaks GNOME live installer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User puzel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c8 Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |aschnell@novell.com Info Provider|puzel@novell.com | --- Comment #8 from Petr Uzel 2009-01-15 09:02:20 MST --- (In reply to comment #7)

As well, swap should not be automounted at all - was the partition changed from an existing type?

IIRC there were two primary (ntfs & fat) partitions and one extended, but without any logical partitions. The installer tried to create / and swap as a logical partitions. Just after it has created any partition (with parted, which involves informing the kernel about new partition via ioctl), the automounter fired up. Not sure whether the swap partition was created directly with 0x82 type, but I guess it was. I don't have the logs anymore, but I could verify if you need. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c11 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|vuntz@novell.com | --- Comment #11 from Vincent Untz 2009-01-19 07:53:29 MST --- Jiri: there are two things in the upstream bug: + the fact that hal-lock should be run as root (not a bug according to upstream, see comment #7 in the upstream bug) + the fact that locks are not respected for devices which are in /etc/fstab. The patch is available upstream and that's what I proposed to backport if it's needed (see the end of comment #9 here) Now, you can handle that another way and temporary disable automounting by nautilus -- it's a gconf key (/apps/nautilus/preferences/media_automount). You can set it with gconftool-2, but that's merely a workaround (which is actually not easy to get right, since it involves setting the value for the user and resetting it afterwards to its previous value). Note that you can replicate hal-lock functionality elsewhere: see the code at http://cgit.freedesktop.org/hal/tree/tools/hal-lock.c. The important call seems to be libhal_acquire_global_interface_lock(). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c13 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|vuntz@novell.com | --- Comment #13 from Vincent Untz 2009-01-19 08:43:16 MST --- (In reply to comment #12)

yast2-live-installer is run as root; the devices are not in fstab at all (resp. they are written to fstab in chrooted environment, hope that is not a problem).

It shouldn't be an issue, but I don't really know gnome-mount -- I just guess from what I can see from upstream comments.

Since I'm not a hal or GNOME expert (and AFAIK neither is Arvin), could you, please, provide us with a list of commands to disable and reenable the automounter which we can run from bash while the live installer is already running? I can imagine that very same problem can occurre also in other cases than the live installation.

I really think you should not play with gconf and use the hal stuff (either via hal-lock or via a mini app which would be based on hal-lock). I can't really help with the hal part. However, if you want to go the gconf way, here's what to do: gconftool-2 --get /apps/nautilus/preferences/media_automount => this gets the current value of the pref gconftool-2 --set /apps/nautilus/preferences/media_automount --type boolean false => this disables the automounter (and then you can set it back to the old value you saved) Note that is a hack and this is broken in many ways: + the user can reenable the pref manually + you're playing with a user pref and what I wrote here won't exactly restore the pref (ie, it will restore the value, but it will lose the information of whether this is the default value or not). This is probably fine for the live installer, though. Give me 20 minutes to look if I can write a small helper based on hal-lock for you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |vuntz@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c16 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsrain@novell.com --- Comment #16 from Thomas Göttlicher 2009-01-20 03:17:58 MST --- Jiri, I think this is yast2-live-installer specific. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c18 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |vuntz@novell.com --- Comment #18 from Arvin Schnell 2009-01-20 13:16:55 MST --- I cannot add the utility to yast2-storage without introducing new dependencies. Add it somewhere where it is always available when hal is installed, e.g. hal itself. After all I cannot understand why a working solution was removed without even informing the maintainer of yast2-storage. After all the solution was added esp. for this usecase, see bug #153241. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User jimomura@pathcom.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c20 Jim Omura changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimomura@pathcom.com --- Comment #20 from Jim Omura 2009-01-20 20:37:32 MST --- (In reply to comment #19)

(In reply to comment #18)

...

I cannot add the utility to yast2-storage without introducing new dependencies. Add it somewhere where it is always available when hal is installed, e.g. hal itself.

I don't maintain hal. I can only put this small helper in some GNOME package, and I don't think it belongs there, especially since you'd want to use it even when GNOME is not available.

. . If KDE does not have this problem (and possibly not QT either for that matter) it would appear that it might be GNOME specific. In fact, since it is not upstream it might be OpenSuSE GNOME specific. Although this whole situation surprises me. I would have expect that this whole area of Auto-mounting would have been fairly standardized by now. If you guys get this solved, see if you can get a test "11.1 GNOME LiveCD" iso put together and I will try to install it on one of my computers. Whether or not you update anything else in the ISO is not that important, though I guess it would be more stable with the latest packages. The point is that there were some other apparent bugs related to partitioning and GRUB installation. It would be good to see if they were partly/wholly byproducts of this one bug. I have already suggested elsewhere that the current 11.1 GNOME LiveCD iso's should be replaced. This is not something that should be put off till 11.2. I hope whomever makes such decisions is considering this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c22 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |dkukawka@novell.com --- Comment #22 from Arvin Schnell 2009-01-21 03:38:19 MST --- Yes, glib is the culprit. I already get blamed for the dependencies of yast2-storage so I won't add more. Danny, please add the tool to hal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c24 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|aschnell@novell.com | --- Comment #24 from Arvin Schnell 2009-01-21 04:36:30 MST --- The only attachment, see comment #14. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c26 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #26 from Arvin Schnell 2009-01-21 04:58:06 MST --- Then I see now way how I can fix this now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c28 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |vuntz@novell.com --- Comment #28 from Arvin Schnell 2009-01-21 05:18:19 MST ---

From YCP I don't have access to libhal_acquire_global_interface_lock().

Why do I have to hack something in the last minute? Just as well the former solution can be hacked back. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c30 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|vuntz@novell.com |aschnell@novell.com --- Comment #30 from Vincent Untz 2009-01-22 05:03:12 MST --- (In reply to comment #22)

Yes, glib is the culprit. I already get blamed for the dependencies of yast2-storage so I won't add more.

How can glib be an issue if hal is not? vuntz@lyon ~/>rpm -q --requires hal | grep glib dbus-1-glib >= 0.61-1 libdbus-glib-1.so.2 libglib-2.0.so.0 (In reply to comment #28)

Why do I have to hack something in the last minute? Just as well the former solution can be hacked back.

The former solution is not upstream and it will not be accepted upstream. I'm proposing a solution that works as well (if not better because this mechanism is used by more people) and that doesn't require patching all applications that can automatically mount devices. And as far as I can tell, the only reason to not use this solution is a packaging issue. This just sounds wrong, I'm sorry. And I'd really like to avoid putting this in a GNOME-specific package because we certainly want the solution to be valid for non-GNOME stuff. So here's another proposal, to solve it the right way: + to lock: hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run "sh -c 'while true; do sleep 60; done'" + to unlock: kill the previously launched hal-lock No new dependency. How does that sound? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c32 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|vuntz@novell.com |dkukawka@novell.com --- Comment #32 from Vincent Untz 2009-01-22 08:45:33 MST --- I have no idea. Danny might know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c34 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |thoenig@novell.com --- Comment #34 from Arvin Schnell 2009-01-22 09:58:28 MST --- Maybe our dbus maintainer knows the syntax for locking using dbus-send. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c36 Timo Hoenig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |thoenig@novell.com Info Provider|thoenig@novell.com | --- Comment #36 from Timo Hoenig 2009-01-22 10:41:42 MST --- Vincent, you've got everything right. Just --print-reply is missing. Terminal 1: $ lshal -m Terminal 2: dbus-send --print-reply --system --dest=org.freedesktop.Hal /org/freedesktop/Hal/Manager org.freedesktop.Hal.Manager.AcquireGlobalInterfaceLock "string:org.freedesktop.Hal.Device.Storage" boolean:true Terminal 1: 18:40:50.961: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.exclusive = true (new) 18:40:50.962: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.dbus_name = {':1.288'} (new) Unknown type 0='' 18:40:50.964: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.locked = (new) Unknown type 0='' 18:40:50.970: computer property info.named_locks = (new) 18:40:50.971: global_interface_lock_acquired org.freedesktop.Hal.Device.Storage by :1.288 (1 lockers) 18:40:50.971: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.exclusive removed 18:40:50.971: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.locked removed 18:40:50.971: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.dbus_name removed 18:40:50.971: computer property info.named_locks removed 18:40:50.971: global_interface_lock_released org.freedesktop.Hal.Device.Storage by :1.288 (0 lockers) Terminal 2: dbus-send --print-reply --system --dest=org.freedesktop.Hal /org/freedesktop/Hal/Manager org.freedesktop.Hal.Manager.AcquireGlobalInterfaceLock "string:org.freedesktop.Hal.Device.Storage" boolean:true Terminal 1: 18:41:24.900: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.exclusive = false (new) Unknown type 0='' 18:41:24.911: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.dbus_name = (new) Unknown type 0='' 18:41:24.912: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.locked = (new) Unknown type 0='' 18:41:24.913: computer property info.named_locks = (new) 18:41:24.913: global_interface_lock_acquired org.freedesktop.Hal.Device.Storage by :1.289 (1 lockers) 18:41:24.913: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.exclusive removed 18:41:24.913: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.locked removed 18:41:24.913: computer property info.named_locks.Global.org.freedesktop.Hal.Device.Storage.dbus_name removed 18:41:24.913: computer property info.named_locks removed 18:41:24.913: global_interface_lock_released org.freedesktop.Hal.Device.Storage by :1.289 (0 lockers) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c38 --- Comment #38 from Timo Hoenig 2009-01-23 03:31:44 MST --- Yes, I think (I didn't look at the code) how HAL has is designed this functionality. If you don't want to use libhal -- why don't you just use libdbus (or any other D-Bus bindings) to call the method(s) within your application? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c40 --- Comment #40 from Timo Hoenig 2009-01-23 03:43:01 MST --- Hm, it's been a while but I'm pretty sure that I already helped others with YCP/hal issues. Unfortunately I can not recall what part of YaST it was. Maybe Danny's memory is better (it was about error handling IIRC). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c42 --- Comment #42 from Martin Vidner 2009-01-23 10:00:28 MST --- Created an attachment (id=267328) --> (https://bugzilla.novell.com/attachment.cgi?id=267328) dbus-hal.c using libdbus only As one of the complaining, I feel sorry for your wasting of effort, so I hope this code is a suitable replacement. I only needs libdbus-1, not libhal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c44 --- Comment #44 from Arvin Schnell 2009-01-27 07:11:25 MST --- Created an attachment (id=267920) --> (https://bugzilla.novell.com/attachment.cgi?id=267920) prototype patch for yast2-core (trunk) adding dbus-client agent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c46 --- Comment #46 from Arvin Schnell 2009-01-27 08:44:30 MST --- Yes. But it's just a prototype. Calling exit is also not an option. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User aschnell@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c48 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #48 from Arvin Schnell 2009-01-29 09:13:13 MST --- Fixed for openSUSE 11.2 and SLE11. Only checked by looking at 'lshal -m' since I'm not using GNOME. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=464453 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464453#c50 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gato303co@aim.com --- Comment #50 from Jiri Srain 2009-02-18 04:22:24 MST --- *** Bug 474599 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=474599 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.