[opensuse-kde3] automount of USB disk in openSUSE 12.3 / KDE3
Hello: openSUSE 12.3 with KDE3 hal-enabled kdebase3 packages. When I plug in an USB stick, nothing happenes on the desktop, no notifier, no automounting. dmesg indicates the medium is recognized: [ 728.028033] usb 1-1: new high-speed USB device number 2 using ehci_hcd .. [ 728.209966] Initializing USB Mass Storage driver... [ 728.215480] scsi4 : usb-storage 1-1:1.0 [ 728.215800] usbcore: registered new interface driver usb-storage [ 728.215804] USB Mass Storage support registered. .. [ 729.255197] sd 4:0:0:0: Attached scsi generic sg4 type 0 [ 729.627164] sd 4:0:0:0: [sde] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB) [ 729.627650] sd 4:0:0:0: [sde] Write Protect is off [ 729.627656] sd 4:0:0:0: [sde] Mode Sense: 23 00 00 00 [ 729.628161] sd 4:0:0:0: [sde] No Caching mode page present [ 729.628165] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.632704] sd 4:0:0:0: [sde] No Caching mode page present [ 729.632717] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.661277] sde: sde1 [ 729.663675] sd 4:0:0:0: [sde] No Caching mode page present [ 729.663683] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.663690] sd 4:0:0:0: [sde] Attached SCSI removable disk How can I fix it? Thanks, Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Le samedi 16 novembre 2013, Istvan Gabor a écrit :
729.632717
Hi All, hi Istvan, Sorry to disturb, but I would like to know if Istvan knows why his system needs so much time to start (more than 12 minutes, then). Thanks Patrick -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Saturday 16 November 2013 20:02:18 Patrick Serru wrote:
Le samedi 16 novembre 2013, Istvan Gabor a écrit :
729.632717
Hi All, hi Istvan,
Sorry to disturb, but I would like to know if Istvan knows why his system needs so much time to start (more than 12 minutes, then).
I think he plugs in USB drive some time after booting up. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Istvan, Is udevd running? Does ps aux | grep udev return something? Sorry, I have an unrelated question. How did you manage to get hal to run? Are there special "hal-enabled kdebase3" packages? Thanks, Gianluca On Sat, 16 Nov 2013, Istvan Gabor wrote:
Hello:
openSUSE 12.3 with KDE3 hal-enabled kdebase3 packages.
When I plug in an USB stick, nothing happenes on the desktop, no notifier, no automounting.
dmesg indicates the medium is recognized:
[ 728.028033] usb 1-1: new high-speed USB device number 2 using ehci_hcd .. [ 728.209966] Initializing USB Mass Storage driver... [ 728.215480] scsi4 : usb-storage 1-1:1.0 [ 728.215800] usbcore: registered new interface driver usb-storage [ 728.215804] USB Mass Storage support registered. .. [ 729.255197] sd 4:0:0:0: Attached scsi generic sg4 type 0 [ 729.627164] sd 4:0:0:0: [sde] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB) [ 729.627650] sd 4:0:0:0: [sde] Write Protect is off [ 729.627656] sd 4:0:0:0: [sde] Mode Sense: 23 00 00 00 [ 729.628161] sd 4:0:0:0: [sde] No Caching mode page present [ 729.628165] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.632704] sd 4:0:0:0: [sde] No Caching mode page present [ 729.632717] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.661277] sde: sde1 [ 729.663675] sd 4:0:0:0: [sde] No Caching mode page present [ 729.663683] sd 4:0:0:0: [sde] Assuming drive cache: write through [ 729.663690] sd 4:0:0:0: [sde] Attached SCSI removable disk
How can I fix it?
Thanks,
Istvan
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Istvan,
Is udevd running?
Does
ps aux | grep udev
return something?
Sorry, I have an unrelated question. How did you manage to get hal to run? Are there special "hal-enabled kdebase3" packages?
Hello: There are hal-enabled packages for openSUSE 12.3 KDE3, here: http://download.opensuse.org/repositories/KDE:/KDE3:/HAL-enabled/openSUSE_12... Previously the hal enabled packages worked for me in oS 12.1 and 12.2. Media automount and "safely remove" also worked. Now in openSUSE 12.3 with hal-enabled KDE3 automount does not work, after plugin/inserting media nothing happens, no popup window/media notifier is shown. The system recognizes the inserted medium (dmesg shows it, see my original post). When hal-enabled KDE is installed, ps aux | grep udev shows: :~> ps -aux |grep udevd root 281 0.0 0.0 38752 2008 ? Ss 17:59 0:00 /usr/lib/systemd/systemd-udevd user 28650 0.0 0.0 8312 860 pts/2 S+ 18:18 0:00 grep --color=auto udevd I have deinstalled hal-enabled kdebase3 and installed normal (not hal-enabled) kdebase3 packages from http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_12.3/ repo. With these packages automounting of inserted media works, media notifier popup shows, and I the medium is mounted in /media. But unfortunately I can not use safely-remove. When I try to use safely-remove, an error message is shown. The error window is titled "Error - kio_media_mounthelper", and the error text is: 'Unable to unmount "/dev/sdd1". Reason: not authorized to perform operation" And, when I right click on the mounted device icon and select properties, the tab, where mount properties can be edited, is missing. In that tab I could edit different mount options (for example vfat filesystem characterset). I could find another message describing the same problem, here on opensuse-kde3 list: http://lists.opensuse.org/opensuse-kde3/2012-10/msg00010.html No answer to that question either. No one knows how to fix this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi On Mon, Nov 18, 2013 at 8:10 PM, Istvan Gabor <suseuser04@freemail.hu> wrote:
... But unfortunately I can not use safely-remove. When I try to use safely-remove, an error message is shown. The error window is titled "Error - kio_media_mounthelper", and the error text is:
'Unable to unmount "/dev/sdd1". Reason: not authorized to perform operation"
And, when I right click on the mounted device icon and select properties, the tab, where mount properties can be edited, is missing. In that tab I could edit different mount options (for example vfat filesystem characterset).
I could find another message describing the same problem, here on opensuse-kde3 list:
http://lists.opensuse.org/opensuse-kde3/2012-10/msg00010.html
No answer to that question either.
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
2013. november 18. 19:24 napon Mark Goldstein <goldstein.mark@gmail.com> írta: [snip]
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
It not only unmounting media. Through that deskto media icon different mount optons could be set. Now the corresponfing tab with these options is missing. Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tuesday 19 November 2013 13:52:41 Istvan Gabor wrote:
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
It not only unmounting media. Through that deskto media icon different mount optons could be set. Now the corresponfing tab with these options is missing.
In that case I think it is now impossible. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
2013. november 19. 18:29 napon Ilya Chernykh <anixxsus@gmail.com> írta:
On Tuesday 19 November 2013 13:52:41 Istvan Gabor wrote:
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
It not only unmounting media. Through that deskto media icon different mount optons could be set. Now the corresponfing tab with these options is missing.
In that case I think it is now impossible.
Then, if I would like to mount my USB vfat disk with option -o shortname=winnt, how or where can I do it? Or do I have to unmount the drive and remount it manually with the specified options? (Would be very inconvenient.) Thanks, Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 20 November 2013 03:35:42 Istvan Gabor wrote:
It not only unmounting media. Through that deskto media icon different mount optons could be set. Now the corresponfing tab with these options is missing.
In that case I think it is now impossible.
Then, if I would like to mount my USB vfat disk with option -o shortname=winnt, how or where can I do it?
I do not know, but most likely not with KDE3 means. By the way, what is shortname? Did you try to label the USB drive? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I guess that from the command line as root you could use remount: mount -o remount,shortname=winnt /dev/<device> /media/<mountdir> You have to replace <device> and <mountdir> (you might get them from `df`). A bit of a hack. According to the mount man page, this is what shortname is: shortname={lower|win95|winnt|mixed} Defines the behaviour for creation and display of filenames which fit into 8.3 characters. If a long name for a file exists, it will always be preferred display. winnt Display the shortname as is; store a long name when the short name is not all lower case or all upper case. On Wed, 20 Nov 2013, Ilya Chernykh wrote:
On Wednesday 20 November 2013 03:35:42 Istvan Gabor wrote:
It not only unmounting media. Through that deskto media icon different mount optons could be set. Now the corresponfing tab with these options is missing.
In that case I think it is now impossible.
Then, if I would like to mount my USB vfat disk with option -o shortname=winnt, how or where can I do it?
I do not know, but most likely not with KDE3 means.
By the way, what is shortname? Did you try to label the USB drive?
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Monday 18 November 2013 22:24:10 Mark Goldstein wrote:
Hi
On Mon, Nov 18, 2013 at 8:10 PM, Istvan Gabor <suseuser04@freemail.hu> wrote:
... But unfortunately I can not use safely-remove. When I try to use safely-remove, an error message is shown. The error window is titled "Error - kio_media_mounthelper", and the error text is:
'Unable to unmount "/dev/sdd1". Reason: not authorized to perform operation"
And, when I right click on the mounted device icon and select properties, the tab, where mount properties can be edited, is missing. In that tab I could edit different mount options (for example vfat filesystem characterset).
I could find another message describing the same problem, here on opensuse-kde3 list:
http://lists.opensuse.org/opensuse-kde3/2012-10/msg00010.html
No answer to that question either.
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
As a workaround you can use the 17th advice from here: http://linuxforum.ru/viewtopic.php?id=26412 -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wed, Dec 4, 2013 at 1:58 AM, Ilya Chernykh <anixxsus@gmail.com> wrote:
On Monday 18 November 2013 22:24:10 Mark Goldstein wrote:
Hi
On Mon, Nov 18, 2013 at 8:10 PM, Istvan Gabor <suseuser04@freemail.hu> wrote:
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
As a workaround you can use the 17th advice from here:
Thanks a lot, I'll try. Interesting thought that automounting works. Only unmounting requires root permission... -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wed, Dec 4, 2013 at 8:00 AM, Mark Goldstein <goldstein.mark@gmail.com> wrote:
On Wed, Dec 4, 2013 at 1:58 AM, Ilya Chernykh <anixxsus@gmail.com> wrote:
On Monday 18 November 2013 22:24:10 Mark Goldstein wrote:
Hi
On Mon, Nov 18, 2013 at 8:10 PM, Istvan Gabor <suseuser04@freemail.hu> wrote:
Same here. I am just using "umount..." in root shell or sudo as workaround. Maybe there is some group one need to add him/herself.
As a workaround you can use the 17th advice from here:
Thanks a lot, I'll try. Interesting thought that automounting works. Only unmounting requires root permission...
Yep, it works. Now I can unmount removable media as normal user. Thanks again. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I thought that all removable media are handled now by udev and dbus and hal is almost not needed. Is the dbus daemon running? ps aux | grep dbus Are removable media in HAL-enabled kde3 handled by hal or udev? Sorry, I'm not helping you much. I have never used the "safely remove" feature. I always type "sync" in a terminal before I unplug a USB device but I don't know whether this takes care of everything. Gianluca On Mon, 18 Nov 2013, Istvan Gabor wrote:
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Istvan,
Is udevd running?
Does
ps aux | grep udev
return something?
Sorry, I have an unrelated question. How did you manage to get hal to run? Are there special "hal-enabled kdebase3" packages?
Hello:
There are hal-enabled packages for openSUSE 12.3 KDE3, here:
http://download.opensuse.org/repositories/KDE:/KDE3:/HAL-enabled/openSUSE_12...
Previously the hal enabled packages worked for me in oS 12.1 and 12.2. Media automount and "safely remove" also worked.
Now in openSUSE 12.3 with hal-enabled KDE3 automount does not work, after plugin/inserting media nothing happens, no popup window/media notifier is shown.
The system recognizes the inserted medium (dmesg shows it, see my original post).
When hal-enabled KDE is installed, ps aux | grep udev shows:
:~> ps -aux |grep udevd root 281 0.0 0.0 38752 2008 ? Ss 17:59 0:00 /usr/lib/systemd/systemd-udevd user 28650 0.0 0.0 8312 860 pts/2 S+ 18:18 0:00 grep --color=auto udevd
I have deinstalled hal-enabled kdebase3 and installed normal (not hal-enabled) kdebase3 packages from http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_12.3/ repo.
With these packages automounting of inserted media works, media notifier popup shows, and I the medium is mounted in /media.
But unfortunately I can not use safely-remove. When I try to use safely-remove, an error message is shown. The error window is titled "Error - kio_media_mounthelper", and the error text is:
'Unable to unmount "/dev/sdd1". Reason: not authorized to perform operation"
And, when I right click on the mounted device icon and select properties, the tab, where mount properties can be edited, is missing. In that tab I could edit different mount options (for example vfat filesystem characterset).
I could find another message describing the same problem, here on opensuse-kde3 list:
http://lists.opensuse.org/opensuse-kde3/2012-10/msg00010.html
No answer to that question either.
No one knows how to fix this?
Thanks,
Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
On Monday 18 November 2013 22:10:19 Istvan Gabor wrote:
No one knows how to fix this?
Actually Serghei already developed a fix that should work, but it needs porting because Serghei uses cmake (the fix is not just a patch a a policy kit client for kde3). in the meanwhile, did you try do uncheck the use of Udisks backend in the Control Center? Does it help? Note also that because of this inconvinience, I made all USB drives to mount in sync mode. This means you can safely remove them physically once the writing operation is over. The writing is not cashed. Upon removal the drive is unmounted. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
2013. november 18. 22:52 napon Ilya Chernykh <anixxsus@gmail.com> írta:
On Monday 18 November 2013 22:10:19 Istvan Gabor wrote:
No one knows how to fix this?
Actually Serghei already developed a fix that should work, but it needs porting because Serghei uses cmake (the fix is not just a patch a a policy kit client for kde3).
in the meanwhile, did you try do uncheck the use of Udisks backend in the Control Center? Does it help?
I did not try it? Where can I find this in the control center? I looked in KDE Components / Service Manager but did not see Udisks.
Note also that because of this inconvinience, I made all USB drives to mount in sync mode. This means you can safely remove them physically once the writing operation is over. The writing is not cashed. Upon removal the drive is unmounted.
It is good to know. Where I these setting configured? I'd like to learn. Thanks, Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 20 November 2013 03:30:11 you wrote:
On Monday 18 November 2013 22:10:19 Istvan Gabor wrote:
No one knows how to fix this?
Actually Serghei already developed a fix that should work, but it needs porting because Serghei uses cmake (the fix is not just a patch a a policy kit client for kde3).
in the meanwhile, did you try do uncheck the use of Udisks backend in the Control Center? Does it help?
I did not try it? Where can I find this in the control center? I looked in KDE Components / Service Manager but did not see Udisks.
I think in Peripherals/System Storage. Once you uncheck the safe removal should work, but all USB drives will look like hard drives. That is you have two options: * Use the Udisks2 backend - no safe removal - sync mounting - correct device type recognition * Do not use Udisks2 backend - safe removal - inaccurate device type recognition (only hard drive/DVD)
Note also that because of this inconvinience, I made all USB drives to mount in sync mode. This means you can safely remove them physically once the writing operation is over. The writing is not cashed. Upon removal the drive is unmounted.
It is good to know. Where I these setting configured? I'd like to learn.
It is already configured in the package. You do not need to do anything. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
* Use the Udisks2 backend
- no safe removal - sync mounting
Does "sync mounting" significantly slow down USB data transfer? Gianluca
- correct device type recognition
* Do not use Udisks2 backend
- safe removal - inaccurate device type recognition (only hard drive/DVD)
Note also that because of this inconvinience, I made all USB drives to mount in sync mode. This means you can safely remove them physically once the writing operation is over. The writing is not cashed. Upon removal the drive is unmounted.
It is good to know. Where I these setting configured? I'd like to learn.
It is already configured in the package. You do not need to do anything. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Just my 2c. Are you using systemd or sysv? It seems that udev is somehow related to systemd: http://phoronix.com/forums/showthread.php?73574-OpenSUSE-Not-Everyone-Likes-... It might be worth it trying it out with both and see if it fixes things. But I might be completely wrong. Gianluca On Mon, 18 Nov 2013, Istvan Gabor wrote:
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Istvan,
Is udevd running?
Does
ps aux | grep udev
return something?
Sorry, I have an unrelated question. How did you manage to get hal to run? Are there special "hal-enabled kdebase3" packages?
Hello:
There are hal-enabled packages for openSUSE 12.3 KDE3, here:
http://download.opensuse.org/repositories/KDE:/KDE3:/HAL-enabled/openSUSE_12...
Previously the hal enabled packages worked for me in oS 12.1 and 12.2. Media automount and "safely remove" also worked.
Now in openSUSE 12.3 with hal-enabled KDE3 automount does not work, after plugin/inserting media nothing happens, no popup window/media notifier is shown.
The system recognizes the inserted medium (dmesg shows it, see my original post).
When hal-enabled KDE is installed, ps aux | grep udev shows:
:~> ps -aux |grep udevd root 281 0.0 0.0 38752 2008 ? Ss 17:59 0:00 /usr/lib/systemd/systemd-udevd user 28650 0.0 0.0 8312 860 pts/2 S+ 18:18 0:00 grep --color=auto udevd
I have deinstalled hal-enabled kdebase3 and installed normal (not hal-enabled) kdebase3 packages from http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_12.3/ repo.
With these packages automounting of inserted media works, media notifier popup shows, and I the medium is mounted in /media.
But unfortunately I can not use safely-remove. When I try to use safely-remove, an error message is shown. The error window is titled "Error - kio_media_mounthelper", and the error text is:
'Unable to unmount "/dev/sdd1". Reason: not authorized to perform operation"
And, when I right click on the mounted device icon and select properties, the tab, where mount properties can be edited, is missing. In that tab I could edit different mount options (for example vfat filesystem characterset).
I could find another message describing the same problem, here on opensuse-kde3 list:
http://lists.opensuse.org/opensuse-kde3/2012-10/msg00010.html
No answer to that question either.
No one knows how to fix this?
Thanks,
Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Just my 2c. Are you using systemd or sysv? It seems that udev is somehow related to systemd:
If I know correctly there is no sysv in openSUSE 12.3. oS 12.2 was the last openSUSE release where it was an option. And there is another thing I just noticed: Despite of that you can install hal from the KDE repo, it is not running, and can not be started, at least no on my system. ~> ps -e|grep -i hal ~> # systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 10:40:12 CET; 9h ago Process: 1529 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 1465 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service Nov 19 10:40:11 linux.site systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... Nov 19 10:40:11 linux.site haldaemon[1465]: chown: invalid user: 'haldaemon:haldaemon' Nov 19 10:40:11 linux.site haldaemon[1465]: Starting HAL daemon..done Nov 19 10:40:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 10:40:12 linux.site haldaemon[1529]: Shutting down HAL daemon..done # systemctl start haldaemon.service # # systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 20:30:12 CET; 7s ago Process: 24740 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 24727 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service Nov 19 20:30:12 linux.site haldaemon[24727]: Starting HAL daemon..done Nov 19 20:30:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 20:30:12 linux.site haldaemon[24740]: Shutting down HAL daemon..done # This is the output from /var/log/messages: # cat /var/log/messages |grep -i hal 2013-11-19T20:17:08.620060+01:00 linux systemd-udevd[24127]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.035565+01:00 linux systemd-udevd[24360]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.125681+01:00 linux systemd-udevd[24366]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.170657+01:00 linux systemd-udevd[24368]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.188653+01:00 linux systemd-udevd[24370]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:28:51.115023+01:00 linux dbus-daemon[1464]: dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:28:51.115086+01:00 linux dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:30:12.535197+01:00 linux systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... 2013-11-19T20:30:12.862989+01:00 linux haldaemon[24727]: Starting HAL daemon..done 2013-11-19T20:30:12.871227+01:00 linux systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. 2013-11-19T20:30:12.939199+01:00 linux haldaemon[24740]: Shutting down HAL daemon..done Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I tried to install hal in openSUSE 12.3 regular KDE3 (not hal-enabled) with no luck. I have been able to get it to run under 12.2 by fixing some aliases. See here: http://lists.opensuse.org/opensuse-kde3/2013-02/msg00021.html When I do the same in openSUSE 12.3 I am able to start hal (status displays "Active: active (running)") but it crashes after a few minutes. You can try it out, maybe you will have better luck. Is there a way how I can debug why the haldaemon crashes? When I look at the log file, I see a line printed right before it crashes: haldaemon[9781]: Starting HAL daemon It looks like it's trying to re-start itself but can't. I would like to understand what the difference is between hal-enabled KDE3 and non hal-enabled KDE3. If I had another box with exaclty the same installation but with the hal-enabled KDE3, maybe I could compare them side to side and learn what is missing in the non hal-enabled one. Gianluca On Tue, 19 Nov 2013, Istvan Gabor wrote:
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Just my 2c. Are you using systemd or sysv? It seems that udev is somehow related to systemd:
If I know correctly there is no sysv in openSUSE 12.3. oS 12.2 was the last openSUSE release where it was an option.
And there is another thing I just noticed:
Despite of that you can install hal from the KDE repo, it is not running, and can not be started, at least no on my system.
~> ps -e|grep -i hal ~>
# systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 10:40:12 CET; 9h ago Process: 1529 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 1465 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 10:40:11 linux.site systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... Nov 19 10:40:11 linux.site haldaemon[1465]: chown: invalid user: 'haldaemon:haldaemon' Nov 19 10:40:11 linux.site haldaemon[1465]: Starting HAL daemon..done Nov 19 10:40:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 10:40:12 linux.site haldaemon[1529]: Shutting down HAL daemon..done
# systemctl start haldaemon.service # # systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 20:30:12 CET; 7s ago Process: 24740 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 24727 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 20:30:12 linux.site haldaemon[24727]: Starting HAL daemon..done Nov 19 20:30:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 20:30:12 linux.site haldaemon[24740]: Shutting down HAL daemon..done #
This is the output from /var/log/messages:
# cat /var/log/messages |grep -i hal 2013-11-19T20:17:08.620060+01:00 linux systemd-udevd[24127]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.035565+01:00 linux systemd-udevd[24360]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.125681+01:00 linux systemd-udevd[24366]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.170657+01:00 linux systemd-udevd[24368]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.188653+01:00 linux systemd-udevd[24370]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:28:51.115023+01:00 linux dbus-daemon[1464]: dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:28:51.115086+01:00 linux dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:30:12.535197+01:00 linux systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... 2013-11-19T20:30:12.862989+01:00 linux haldaemon[24727]: Starting HAL daemon..done 2013-11-19T20:30:12.871227+01:00 linux systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. 2013-11-19T20:30:12.939199+01:00 linux haldaemon[24740]: Shutting down HAL daemon..done
Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
I have an update. If I run `hald --verbose=yes --daemon=no` for debugging purposes, I get the following error messages: [11923]: 21:22:42.392 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory Any ideas? Gianluca On Tue, 19 Nov 2013, Gianluca Interlandi wrote:
I tried to install hal in openSUSE 12.3 regular KDE3 (not hal-enabled) with no luck. I have been able to get it to run under 12.2 by fixing some aliases. See here:
http://lists.opensuse.org/opensuse-kde3/2013-02/msg00021.html
When I do the same in openSUSE 12.3 I am able to start hal (status displays "Active: active (running)") but it crashes after a few minutes. You can try it out, maybe you will have better luck.
Is there a way how I can debug why the haldaemon crashes? When I look at the log file, I see a line printed right before it crashes:
haldaemon[9781]: Starting HAL daemon
It looks like it's trying to re-start itself but can't.
I would like to understand what the difference is between hal-enabled KDE3 and non hal-enabled KDE3. If I had another box with exaclty the same installation but with the hal-enabled KDE3, maybe I could compare them side to side and learn what is missing in the non hal-enabled one.
Gianluca
On Tue, 19 Nov 2013, Istvan Gabor wrote:
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Just my 2c. Are you using systemd or sysv? It seems that udev is somehow related to systemd:
If I know correctly there is no sysv in openSUSE 12.3. oS 12.2 was the last openSUSE release where it was an option.
And there is another thing I just noticed:
Despite of that you can install hal from the KDE repo, it is not running, and can not be started, at least no on my system.
~> ps -e|grep -i hal ~>
# systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 10:40:12 CET; 9h ago Process: 1529 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 1465 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 10:40:11 linux.site systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... Nov 19 10:40:11 linux.site haldaemon[1465]: chown: invalid user: 'haldaemon:haldaemon' Nov 19 10:40:11 linux.site haldaemon[1465]: Starting HAL daemon..done Nov 19 10:40:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 10:40:12 linux.site haldaemon[1529]: Shutting down HAL daemon..done
# systemctl start haldaemon.service # # systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 20:30:12 CET; 7s ago Process: 24740 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 24727 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 20:30:12 linux.site haldaemon[24727]: Starting HAL daemon..done Nov 19 20:30:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 20:30:12 linux.site haldaemon[24740]: Shutting down HAL daemon..done #
This is the output from /var/log/messages:
# cat /var/log/messages |grep -i hal 2013-11-19T20:17:08.620060+01:00 linux systemd-udevd[24127]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.035565+01:00 linux systemd-udevd[24360]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.125681+01:00 linux systemd-udevd[24366]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.170657+01:00 linux systemd-udevd[24368]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.188653+01:00 linux systemd-udevd[24370]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:28:51.115023+01:00 linux dbus-daemon[1464]: dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:28:51.115086+01:00 linux dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:30:12.535197+01:00 linux systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... 2013-11-19T20:30:12.862989+01:00 linux haldaemon[24727]: Starting HAL daemon..done 2013-11-19T20:30:12.871227+01:00 linux systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. 2013-11-19T20:30:12.939199+01:00 linux haldaemon[24740]: Shutting down HAL daemon..done
Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/
Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
On 20/11/2013 05:30, Gianluca Interlandi wrote:
I have an update. If I run `hald --verbose=yes --daemon=no` for debugging purposes, I get the following error messages:
[11923]: 21:22:42.392 [E] addon-acpi.c:83: Cannot connect to acpid socket: No such file or directory
Any ideas?
Gianluca
<snip> I noticed this while I was on the road this morning. I had a similar experience with KDE3 when I was first porting to openSUSE 12.2 on a new system and later similarly on openSUSE 12.3 in a VirtualBox. With a bit of jiggery-pokery, I managed to get both of them to work properly when mounting and, more importantly, dismount USB devices since the 12.2 system is used a lot for SD card reads and clearances. I did put a lot of what I went through up on my LiveJournal which you can get to at http://mistie710.livejournal.com but you'll probably end up wading through a load of other stuff I wrote so here's a rough idea behind what I did. (Note that I had already installed the HAL-enabled 3.5.10 and that all of the stuff below is done from a root konsole). As already mentioned in this thread, one good idea is to manually try starting haldaemon to see what it is up to. One of the first things I did, though I was never sure if this was effective, was to make sure that dbus had an associated user account created. The command used went something like groupadd -g 81 dbus; useradd -c 'System message bus' -u 81 -g dbus dbus; usermod -s /bin/false dbus; usermod -d '/' dbus Having done that, I noticed that hald was dying off because a number of files were missing, notably the fdi cache. To sort that out, I did the following: mkdir /etc/hal/fdi/preprobe mkdir /etc/hal/fdi/information mkdir /etc/hal/fdi/policy /usr/lib/hal/hald-generate-fdi-cache Once rebooted, all seemed well. Some days later, openSUSE 12.3 was released with a similar problem. I did the above but found that hald still seemed to fail until I checked the user list and found that the haldaemon user was missing this time. The command... useradd -g haldaemon -u 109 -s /bin/false -c 'User for haldaemon' -d /var/run/hald haldaemon ...and a change of runlevel for haldaemon fixed all that. Even got sysinfo back, though that also takes a little bit of a frob to get it to work. Don't know if the above fixes your problem but it worked for me. I suspect that something like this will crop up in openSUSE 13.1... oh well! -- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 20 November 2013 22:07:17 Chika wrote:
Once rebooted, all seemed well. Some days later, openSUSE 12.3 was released with a similar problem. I did the above but found that hald still seemed to fail until I checked the user list and found that the haldaemon user was missing this time. The command...
useradd -g haldaemon -u 109 -s /bin/false -c 'User for haldaemon' -d /var/run/hald haldaemon
...and a change of runlevel for haldaemon fixed all that. Even got sysinfo back, though that also takes a little bit of a frob to get it to work.
Currently the following code is designed for this: if getent passwd haldaemon >/dev/null then : OK haldaemon user already present else /usr/sbin/useradd -r -g haldaemon -c "User for haldaemon" \ -d /var/run/hald -o haldaemon 2>/dev/null || : fi Does not it work properly? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 20/11/2013 18:28, Ilya Chernykh wrote:
On Wednesday 20 November 2013 22:07:17 Chika wrote:
Once rebooted, all seemed well. Some days later, openSUSE 12.3 was released with a similar problem. I did the above but found that hald still seemed to fail until I checked the user list and found that the haldaemon user was missing this time. The command...
useradd -g haldaemon -u 109 -s /bin/false -c 'User for haldaemon' -d /var/run/hald haldaemon
...and a change of runlevel for haldaemon fixed all that. Even got sysinfo back, though that also takes a little bit of a frob to get it to work.
Currently the following code is designed for this:
if getent passwd haldaemon >/dev/null then : OK haldaemon user already present else /usr/sbin/useradd -r -g haldaemon -c "User for haldaemon" \ -d /var/run/hald -o haldaemon 2>/dev/null || : fi
Does not it work properly?
This was some time ago that I did this (shortly after 12.3 was released) so I'd say that, if the code was there at the time, it didn't work for me then. I'll be setting up a new 13.1 box in the next couple of weeks so I suspect that I'll get a chance to try it again then. I'll certainly get the practice as I'm due to rebuild three different systems of various sizes and configurations so I'll keep you posted if anything odd turns up. -- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Wednesday 20 November 2013 23:42:39 Chika wrote:
This was some time ago that I did this (shortly after 12.3 was released) so I'd say that, if the code was there at the time, it didn't work for me then. I'll be setting up a new 13.1 box in the next couple of weeks so I suspect that I'll get a chance to try it again then.
I'll certainly get the practice as I'm due to rebuild three different systems of various sizes and configurations so I'll keep you posted if anything odd turns up.
If you find some useful hacks please share them so I could fix the packages and all people use the improvement. I would be also very glad if you tell what you did with the runlevel. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 20/11/2013 20:07, Ilya Chernykh wrote:
On Wednesday 20 November 2013 23:42:39 Chika wrote:
This was some time ago that I did this (shortly after 12.3 was released) so I'd say that, if the code was there at the time, it didn't work for me then. I'll be setting up a new 13.1 box in the next couple of weeks so I suspect that I'll get a chance to try it again then.
I'll certainly get the practice as I'm due to rebuild three different systems of various sizes and configurations so I'll keep you posted if anything odd turns up.
If you find some useful hacks please share them so I could fix the packages and all people use the improvement.
I would be also very glad if you tell what you did with the runlevel.
That was no biggie. I just went into YaST --> System services (Runlevel) and set haldaemon to be active at levels 2, 3 and 5. One reboot later, all was well. It can be done from the command line too but I had YaST open for some reason anyway when I noticed that I'd forgotten to set this up. -- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Chika, I went through your journal and found under "openSUSE 12.3 - Slight second thoughts": Oh, and for the record, the user for dbus should have read: useradd -c 'System message bus' -u 81 -g dbus dbus; usermod -s /bin/false dbus; usermod -d '/' dbus My dbus service is running but I do not have a dbus user. What do you get when you type grep dbus /etc/passwd; grep dbus /etc/group Also, another thing is that you don't necessarily need to create the directories and cache in /etc/hal/, they are already present in /usr/share/hal. So I just linked them and it worked in openSUSE 12.2. Thanks for you help, Gianluca On Wed, 20 Nov 2013, Chika wrote:
On 20/11/2013 20:07, Ilya Chernykh wrote:
On Wednesday 20 November 2013 23:42:39 Chika wrote:
This was some time ago that I did this (shortly after 12.3 was released) so I'd say that, if the code was there at the time, it didn't work for me then. I'll be setting up a new 13.1 box in the next couple of weeks so I suspect that I'll get a chance to try it again then.
I'll certainly get the practice as I'm due to rebuild three different systems of various sizes and configurations so I'll keep you posted if anything odd turns up.
If you find some useful hacks please share them so I could fix the packages and all people use the improvement.
I would be also very glad if you tell what you did with the runlevel.
That was no biggie. I just went into YaST --> System services (Runlevel) and set haldaemon to be active at levels 2, 3 and 5. One reboot later, all was well. It can be done from the command line too but I had YaST open for some reason anyway when I noticed that I'd forgotten to set this up.
-- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 21/11/2013 00:20, Gianluca Interlandi wrote:
Hi Chika,
I went through your journal and found under "openSUSE 12.3 - Slight second thoughts":
Oh, and for the record, the user for dbus should have read:
useradd -c 'System message bus' -u 81 -g dbus dbus; usermod -s /bin/false dbus; usermod -d '/' dbus
My dbus service is running but I do not have a dbus user. What do you get when you type
grep dbus /etc/passwd; grep dbus /etc/group
messagebus:x:101:101:User for D-Bus:/var/run/dbus:/bin/false dbus:x:81:81:System message bus:/:/bin/false dbus:!:81: video:x:33:daria,dbus
Also, another thing is that you don't necessarily need to create the directories and cache in /etc/hal/, they are already present in /usr/share/hal. So I just linked them and it worked in openSUSE 12.2.
So they are. I suppose I simply went for where the system expected to find them rather than go look for them elsewhere. I'll bear that in mind when I start the next system.
Thanks for you help,
Thanks for the advice too. -- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hmmm, it's quite interesting though that you have two users: messagebus and dbus. On my other installations (11.3 and 11.4) where hal is running correctly I have only messagebus as user. However, I will try that out later. One thing that I am confused about: you say that you used yast to change the runlevels where the haldaemon is started. However, my runlevel editor in yast shows only "B" as a runlevel option (all others, e.g., 2,3,5 are not shown). This is a common issue with openSUSE 12.3 and it is due to the switch from sysv to systemd: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/... Could it be that it worked for you because it was an early download of openSUSE 12.3? In any case, if yast does not work you should use: systemctl enable haldeamon.service (to activate it at bootup) systemctl start haldeamon.service (to start it right away without reboot) In the future, hopefully, the runlevel editor of yast will be replaced with a systemd compatible GUI. Gianluca On Thu, 21 Nov 2013, Chika wrote:
On 21/11/2013 00:20, Gianluca Interlandi wrote:
Hi Chika,
I went through your journal and found under "openSUSE 12.3 - Slight second thoughts":
Oh, and for the record, the user for dbus should have read:
useradd -c 'System message bus' -u 81 -g dbus dbus; usermod -s /bin/false dbus; usermod -d '/' dbus
My dbus service is running but I do not have a dbus user. What do you get when you type
grep dbus /etc/passwd; grep dbus /etc/group
messagebus:x:101:101:User for D-Bus:/var/run/dbus:/bin/false dbus:x:81:81:System message bus:/:/bin/false dbus:!:81: video:x:33:daria,dbus
Also, another thing is that you don't necessarily need to create the directories and cache in /etc/hal/, they are already present in /usr/share/hal. So I just linked them and it worked in openSUSE 12.2.
So they are. I suppose I simply went for where the system expected to find them rather than go look for them elsewhere. I'll bear that in mind when I start the next system.
Thanks for you help,
Thanks for the advice too.
-- Chris "Chika" Johnson MMW Crashnet
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 21/11/2013 20:36, Gianluca Interlandi wrote:
One thing that I am confused about: you say that you used yast to change the runlevels where the haldaemon is started. However, my runlevel editor in yast shows only "B" as a runlevel option (all others, e.g., 2,3,5 are not shown). This is a common issue with openSUSE 12.3 and it is due to the switch from sysv to systemd:
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/...
I suspect that I have mixed up the two systems. The 12.2 system was quite certainly changed using YaST as I described. I just fired up my 12.3 VB and YaST shows only that the service is running, even under expert mode, though chkconfig (OK, so I still tend to use the pre-systemd commands!) shows 2, 3 and 5 are set for it. It was some time ago now, and I know that I did experiment around that time with the systemctl commands but I don't recall using it to set haldaemon's service levels. I must be getting old... -- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Ilya, Currently, haldaemon is not working in my openSUSE 12.3 installation, but I am not using the HAL-enabled KDE3 pacakges. The haldaemon user and group were not present and I created them manually, but it still does not run. I have the following line in /etc/group: haldaemon:x:482: and in /etc/passwd I have: haldaemon:x:485:482:User for haldaemon:/var/run/hald:/bin/false The code that you mention, where is it inserted? Gianluca On Wed, 20 Nov 2013, Ilya Chernykh wrote:
On Wednesday 20 November 2013 22:07:17 Chika wrote:
Once rebooted, all seemed well. Some days later, openSUSE 12.3 was released with a similar problem. I did the above but found that hald still seemed to fail until I checked the user list and found that the haldaemon user was missing this time. The command...
useradd -g haldaemon -u 109 -s /bin/false -c 'User for haldaemon' -d /var/run/hald haldaemon
...and a change of runlevel for haldaemon fixed all that. Even got sysinfo back, though that also takes a little bit of a frob to get it to work.
Currently the following code is designed for this:
if getent passwd haldaemon >/dev/null then : OK haldaemon user already present else /usr/sbin/useradd -r -g haldaemon -c "User for haldaemon" \ -d /var/run/hald -o haldaemon 2>/dev/null || : fi
Does not it work properly? -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
useradd -g haldaemon -u 109 -s /bin/false -c 'User for haldaemon' -d /var/run/hald haldaemon
...and a change of runlevel for haldaemon fixed all that. Even got sysinfo back, though that also takes a little bit of a frob to get it to work.
What do you mean by "a change of runlevel for haldaemon"? How do you change the runlevel for haldaemon? Another question: do you have acpid running? Is it necessary for hald to run properly? Gianluca
Don't know if the above fixes your problem but it worked for me. I suspect that something like this will crop up in openSUSE 13.1... oh well!
-- Chris "Chika" Johnson MMW Crashnet -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On Tue, 19 Nov 2013, Istvan Gabor wrote:
Gianluca Interlandi <gianluca@u.washington.edu> írta:
Just my 2c. Are you using systemd or sysv? It seems that udev is somehow related to systemd:
If I know correctly there is no sysv in openSUSE 12.3. oS 12.2 was the last openSUSE release where it was an option.
I think that sysv-init is available in the openSUSE 12.3 standard repositories. However, according to this thread: http://opensuse.14.x6.nabble.com/problem-with-switch-to-sysvinit-init-td4989... it will break your system. I wonder how come they haven't removed the package from the standard repository if it is known that it creates damage. Perhaps people who are in charge of the repositories haven't caught up with development. Gianluca
And there is another thing I just noticed:
Despite of that you can install hal from the KDE repo, it is not running, and can not be started, at least no on my system.
~> ps -e|grep -i hal ~>
# systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 10:40:12 CET; 9h ago Process: 1529 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 1465 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 10:40:11 linux.site systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... Nov 19 10:40:11 linux.site haldaemon[1465]: chown: invalid user: 'haldaemon:haldaemon' Nov 19 10:40:11 linux.site haldaemon[1465]: Starting HAL daemon..done Nov 19 10:40:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 10:40:12 linux.site haldaemon[1529]: Shutting down HAL daemon..done
# systemctl start haldaemon.service # # systemctl status haldaemon.service haldaemon.service - LSB: HAL is a daemon for managing information about the hardware on the system Loaded: loaded (/etc/init.d/haldaemon) Active: inactive (dead) since Tue, 2013-11-19 20:30:12 CET; 7s ago Process: 24740 ExecStop=/etc/init.d/haldaemon stop (code=exited, status=0/SUCCESS) Process: 24727 ExecStart=/etc/init.d/haldaemon start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/haldaemon.service
Nov 19 20:30:12 linux.site haldaemon[24727]: Starting HAL daemon..done Nov 19 20:30:12 linux.site systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. Nov 19 20:30:12 linux.site haldaemon[24740]: Shutting down HAL daemon..done #
This is the output from /var/log/messages:
# cat /var/log/messages |grep -i hal 2013-11-19T20:17:08.620060+01:00 linux systemd-udevd[24127]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.035565+01:00 linux systemd-udevd[24360]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.125681+01:00 linux systemd-udevd[24366]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.170657+01:00 linux systemd-udevd[24368]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:17:56.188653+01:00 linux systemd-udevd[24370]: failed to execute '/usr/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory 2013-11-19T20:28:51.115023+01:00 linux dbus-daemon[1464]: dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:28:51.115086+01:00 linux dbus[1464]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.124" (uid=1001 pid=24664 comm="systemctl start haldaemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ") 2013-11-19T20:30:12.535197+01:00 linux systemd[1]: Starting LSB: HAL is a daemon for managing information about the hardware on the system... 2013-11-19T20:30:12.862989+01:00 linux haldaemon[24727]: Starting HAL daemon..done 2013-11-19T20:30:12.871227+01:00 linux systemd[1]: Started LSB: HAL is a daemon for managing information about the hardware on the system. 2013-11-19T20:30:12.939199+01:00 linux haldaemon[24740]: Shutting down HAL daemon..done
Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Scientist at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. http://healthynaturalbaby.org -----------------------------------------------------
participants (7)
-
Chika -
Gianluca Interlandi -
Ilya Chernykh -
Istvan Gabor -
Istvan Gabor -
Mark Goldstein -
Patrick Serru