Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
This bug is to track all the changes needed to get the new utopia stack into Gentoo. Ebuilds to follow... Reproducible: Always Steps to Reproduce:
One thing we really would like to have is udev 057 (which is why I cc'd gregkh)...
Created an attachment (id=58380) [details] dbus 0.33
Created an attachment (id=58381) [details] hal patch
Created an attachment (id=58382) [details] a merger of Cardoe's and my ebuild for hal 0.5.1
Created an attachment (id=58383) [details] gnome-vfs hal api patch
Created an attachment (id=58384) [details] gnome-vfs (hal 0.5.1 enabled) ebuild
Created an attachment (id=58385) [details] gnome-volume-manager 1.3.1 (hal 0.5.1 enabled)
Created an attachment (id=58386) [details] gnome-utils hal api patch
Created an attachment (id=58387) [details] gnome-utils (hal 0.5 enabled) ebuild
Created an attachment (id=58388) [details] hal-device-manager 0.5.1 ebuild
Created an attachment (id=58389) [details] nautilus-cd-burner hal api patch
Created an attachment (id=58390) [details] nautilus-cd-burner
why do you need udev 057? We really do not want that version yet, it still has real problems that are getting resolved. it also needs a lot of rule re-working to get correct :( right now i'm working with the fedora and debian developers to get it all resolved.
I'm not saying right away... Its just a request. So whenever its ready, it'd be awesome. On a related note, with 056 right now /dev/hda is root:disk but /dev/hda1 is root:root. Is this by design? Can we make /dev/hda1 root:disk as well?
Again, is there anything in 057 that Gentopia needs that is not in 056?
As for the hda1 group issue, that looks like a bug in the ide-devfs.sh script, care to open a new bug for that?
From the hal changelog: * hald/linux2/coldplug.c (hal_util_get_udevinfo_path): Move from osspec.c (hal_util_get_sysfs_to_dev_map): New function (coldplug_synthesize_events): Get the sysfs->dev map in one go using 'udevinfo -d' available in udev since at least version 057.
`udevinfo -d` exists in udev 056
spotted from Doug's email to -dev: If there aren't too many hoops to jump through then this is something that I would be seriously interested in helping out with. Hell, it may even be something I can invest my paid working time into. Where are the (flaming) hoops?
The main issues are getting the new hal/dbus packages up to snuff. see http://dev.gentoo.org/~npmccallum/overlay
Created an attachment (id=59435) [details] Ebuild for liferea-0.9.2 that compiles/runs with dbus > .3 Patch to follow.
Created an attachment (id=59436) [details] patch for liferea 0.9.2 that fixes the DBUS API Patch to use the new dbus > .3 API
I think there is a problem with the pmount patch for gnome-volume-manager. I recompiled it and it tries to use mount (not pmount) to mount my digital camera when I plug it in. Here is an output: manager.c/995: Changed: /dev/sda1 manager.c/792: Added: /dev/sda1 mount: wrong fs type, bad option, bad superblock on /dev/sda1, or too many mounted file systems
Well, mount eventually does get called. Pmount doesn't replace mount, it is a wrapper around mount. Can you mount that same device as root with just regular ole mount? If you can, then there is either a problem with pmount or gvm. If not, then you may have a problem with your hardware. BTW, what kind of hardware is it?
The device is a digital camera. When I just type mount /dev/sda1 I get: mount: can't find /dev/sda1 in /etc/fstab or /etc/mtab But if I create a folder /media/camera and type mount /media/camera the camera is sucessfully mounted. If I type pmount /dev/sda1 the camera is also sucessfully mounted. So I don not get why I get en error when gnome-volume-manager tries to mount it.
I found the problem. I had not compiled support for NLS UTF8 in my kernel. This is needed and is done with: make menuconfig -> File Systems ---> Native Language Support ---> < > NLS UTF8 (last option) Now it automounts again!
Find now that hal does not recognise my dvd player. When I lauch hal-device-manager my dvd player is not in the list. Udev do create the correct node /dev/cdrom and I can mount the device with both pmount /dev/cdrom and mount /dev/cdrom Any ideas?
I don't know how to add a new dependancy, but xfmedia-0.7.0 would not compile with the new dbus. I have commited bug #94331 for this and the fact that the dbus was not there at all as a dependancy for the xfmedia package.
Newer hal using pmount makes it impossible for me to get my PSP to mount with the correct uppercasing. It hardcodes shortname=winnt for vfat in it's code. I've manually hacked that to be shortname=mixed so that the casing works. Using the old fstab-sync method, I've been able to get shortname=mixed as an option, but pmount does it's own thing. I'd really like to see that option in pmount before this all goes into gentoo. Maybe I should submit a seperate bug report, though, but thought since it was an issue wit this whole setup, i should put it here as well.
please submit a bug report upstream regarding PSP/pmount as I don't have have the hardware so it would be useless for me to do so. Upstream is martin pitt from ubuntu/debian.
a new version of dbus has been released (.34) - i haven't yet tested it, a friend is moving and im currently watching 4 pit bulls and a mini-pinscher, so i've had my hands full, and will for a bit, reading through the changelog just now, i think it MIGHT break a few things, but I am not too sure, I know that one of the api's (dbus_connection_disconnect) has changed to dbus_connection_close - thats pretty much the only one that sticks out a lot to me.
according to http://bugs.gentoo.org/show_bug.cgi?id=92573 Daniel says that my problem is with Hal - After updating to the gentoo-sources 2.6.12, my usb hard drive no longer automounts, and when i attempt to mount it manually, i get the following mebius portage-gentopia # pmount /dev/sda1 /media/FIREFLY Error: device /dev/sda1 is not removable I have re-emerged all of gentopia, dbus-0.3.4, hal-0.5.2, pmount, gnome-volume-manager, and gnome-vfs, and I still get the above when trying to mount manually, and it does not auto-mount it. Worked fine under 2.6.11 with removing the inotify patch from gentoo sources and applying the patch from the gamin filesdir in Gentopia's overlay. Any ideas?
Just a quick note to let you know that app-cdr/k3b-0.12.2 works fine with sys-apps/dbus-0.34 and sys-apps/hal-0.5.2 from your Gentopia overlay, despite its deps say =sys-apps/dbus-0.23* and =sys-apps/hal-0.4*. At least, my usb2 DVD burner appears/disappears when i plug/unplug it, with no need to manually refresh the device list or anything like that, and i assume that's what the HAL support is for. Should i open a bugreport for the KDE team, or should i wait since this versions are not in the tree yet anyway?
Hello, The gnome-volume-manager (maybe something else..) stopped working 2-1 week(s) ago. I'm updating my ~x86 gentoo every day, so some update broke things. packages i have installed: suspend2-sources-2.6.12-r1 gamin-0.1.2 gnome-volume-manager-1.3.2 dbus-0.34 hotplug-base-20040401 hal-0.5.2 hotplug-20040923-r1 udev-063 hal-device-manager-0.5.1 Gnome does not automount my usbkey or cdrom and doesn't place an icon on desktop. /etc/fstab: /dev/hdc /mnt/cdrom iso9660 noauto,user,ro,uid=1000,gid=100 0 0 /dev/sda1 /mnt/usbdisk vfat noauto,user,rw,quiet,uid=1000,gid=100,dmask=007,fmask=117,codepage=852 0 0 Here is a log from the gnome-volume-manager: dano@picard:~ $ gnome-volume-manager manager.c/421: setting[0]: bool: autobrowse = 0 manager.c/421: setting[1]: bool: autoburn = 0 manager.c/416: setting[2]: string: autoburn_audio_cd_command = sonance --burn-cd manager.c/416: setting[3]: string: autoburn_photo_cd_command = f-spot --burn-cd manager.c/416: setting[4]: string: autoburn_data_cd_command = nautilus --no-desktop burn: manager.c/421: setting[5]: bool: autoipod = 1 manager.c/416: setting[6]: string: autoipod_command = sonance --ipod-available=%h manager.c/421: setting[7]: bool: automount_drives = 0 manager.c/421: setting[8]: bool: automount_media = 0 manager.c/421: setting[9]: bool: autophoto = 0 manager.c/416: setting[10]: string: autophoto_command = gthumb --import-photos manager.c/421: setting[11]: bool: autoplay_cda = 0 manager.c/416: setting[12]: string: autoplay_cda_command = gnome-cd --unique --play --device %d manager.c/421: setting[13]: bool: autoplay_dvd = 0 manager.c/416: setting[14]: string: autoplay_dvd_command = totem /mnt/cdrom manager.c/421: setting[15]: bool: autoprinter = 1 manager.c/416: setting[16]: string: autoprinter_command = gnome-cups-add manager.c/421: setting[17]: bool: autorun = 0 manager.c/416: setting[18]: string: autorun_path = .autorun:autorun:autorun.sh manager.c/416: setting[19]: string: eject_command = /usr/bin/eject manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_ea0_2168_106C1140DFCC69B5 manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_ea0_2168_106C1140DFCC69B5_if0 manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_ea0_2168_106C1140DFCC69B5_if0_scsi_host manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_ea0_2168_106C1140DFCC69B5_if0_scsi_host_scsi_device_lun0 manager.c/1181: New Device: /org/freedesktop/Hal/devices/storage_model_USB_Flash_Disk manager.c/1187: not a mountable volume: /org/freedesktop/Hal/devices/storage_model_USB_Flash_Disk manager.c/1217: Changed: /dev/sda manager.c/1181: New Device: /org/freedesktop/Hal/devices/volume_part_1_size_130809856 manager.c/1217: Changed: /dev/sda manager.c/1181: New Device: /org/freedesktop/Hal/devices/volume_uuid_42C7_BF86 manager.c/1217: Changed: /dev/sda1 ### After my first install of gentopia stuff it just worked, but now i am really sad :( ### Thanx for help.
For me evolution-2.2.3-r2 compiles fine with dbus despite what its ebuild says.
That is dbus-0.34 I meant (sorry).
WHY NOBODY TAKES THE PATCHES FROM FEDORA4 DEVEL BRANCH ? THERE ARE REAL PATCHES. NOW HERE ALL LIKE FOR KIDS, LOL NOT A SERIOUS GENTOPIA
Well, then make an ebuild for it please. If you have enough time please help instead of crying around in bugs ..
Please create a seperate bug for liferea. This bug will be closing shortly.
(In reply to comment #39) > Please create a seperate bug for liferea. This bug will be closing shortly. The above mentionned dbus API issue has been fixed upstream already. Also, citizen428 should have got an ebuild patch to add optionnal dbus support in his ebuild when >=dbus-0.3 is unmasked (part of bug #100051), so i don't think there is need for a new bug.
Howdy, why are hal-0.5.4 and dbus-0.36.1 in ~x86 when some stuff (such as kdebase-kioslaves and k3b) depend on the older hal and dbus versions? It's causing hal and dbus to be in an upgrade/downgrade cycle on my ~x86 system. Seems to me that the latest versions of hal and dbus should be hard masked until all ebuilds have their dependencies fixed.
KDE people closed out the bugs saying they fixed the dependancies. I believed them. One of the crossed off bugs that this one depended on were those bugs. As far as this is concerned, those problems are seperate bugs.
Here's the problem: When doing emerge -DNuavt world, Portage wants to upgrade hal and dbus to 0.5.4 and 0.36.1 respectively. After those upgrades have completed, on the next run of emerge -DNuavt world, Portage wants to downgrade hal and dbus due to, for example, the =sys-apps/hal-0.4* and =sys-apps/dbus-0.23* dependencies in gnome-vfs-2.10.0-r2. Are we (users) expected to mask the newer versions of hal and dbus in /etc/portage/package.mask? I've never had to do that before. Hence the hard masking until everything works nicely together, right?
The issue you're having is the fact that you emerged an ebuild before the depend was properly fixed. So by looking at the tree (which you should see with the command you're using), you can re-emerge the package that keeps pulling in the new or old hal/dbus. Closing this bug since hal & dbus are in Portage an unmasked. Good job all.
I noticed the if hal starts before the acpid daemon acpid can not start because hald-addon-acpi blocks /proc/acpi/event. Is this a bug?
what happend to net.80203.link and .rate in earlier version of hal it showed me what is ma current coneciot speed and am i connected or not. bu now in 0.5.4 it doesn't. i know it was a matter of patch and i want to ask can it be ported to 0.5.4 too ?!
Since hal is no longer compiled with fstab-sync, my system doesn't (correctly) automatically mount my USB devices anymore. I filed bug #113724 regarding this. Could somebody please have a look?
CC'ed you to bug #107784. It is quite possible that is the issue you are facing.
The gentopia svn repository (and maybe the entire server) has been down for a couple of weeks, it seems. Just FYI. svn: PROPFIND request failed on '/svn/overlay' svn: PROPFIND of '/svn/overlay': SSL negotiation failed: Interrupted system call (https://gentopia.gentooexperimental.org) URL: https://gentopia.gentooexperimental.org/svn/overlay Repository Root: https://gentopia.gentooexperimental.org/svn Repository UUID: 0314abc3-b4f6-0310-a51c-ac2cb2351e82 Revision: 433 Node Kind: directory Schedule: normal Last Changed Author: cardoe Last Changed Rev: 433 Last Changed Date: 2006-01-19 00:54:52 -0500 (Thu, 19 Jan 2006)
