The bug does not happen in Oneiric. Don't know if it's fixed or just a
different hardware combination that's working better - I have a new
laptop with Oneiric and the same old bluetooth dongle is recognized and
working.
--
You received this bug notification because you are a member of Ubuntu
Desk
I'm experiencing this problem when opening a folder on an SD card with some
photos (about 100-200) at about 10 mpx. The creation of thumbnails eats almost
all the cpu power (centrino 2 duo @2ghz), making even Rhythmbox song lag every
5-10 seconds for a couple of seconds.
Needless to say, this is
** Changed in: ejecter
Status: Fix Committed => Fix Released
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchpad.net/bugs/424256
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
des
Committed working version in "karmic-gdu" branch
(https://code.launchpad.net/~fredp/ejecter/karmic-gdu), now it's using
gnome-disk-utility to know device type. Depends on: libgdu, libgdu-dev. Does
not depend (at least directly) anymore on: hal, dbus.
Please let me know if it's working for you to
Ok, sorry for the close reply - I managed to create the .vapi file modifying
the headers. Things needed for that are here:
https://code.launchpad.net/~fredp/+junk/libgdu-vala
Now I'll try to get something from this.
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchp
I'm using Vala, so I don't directly pass a DBusGProxy - I think Vala handles
this, then I can't fix that warning.
Also, GDU still hasn't Vala bindings and I can't generate the .vapi file
(following the tutorial over at live.gnome.org/Vala) because the include file
requires to define GDU_API_IS_S
I get them too, but I could not understand what causes them.
I would like to avoid using Dbus/Hal/DeviceKit at all, I'm investigating this
in karmic-hal branch but with Gio methods I can't determine well if the device
is internal. If somebody that knows something about Gio could help me it'd be
Actually I'm trying to port it to DeviceKit-disks, but I'm facing some problem
recognizing whether a device is removable, it always tell me the drive is
internal.
I created a new branch to work on this (
https://code.launchpad.net/~fredp/ejecter/karmic ) - leaving out any
backwards-compatibilit
t; In Progress
** Changed in: ejecter
Assignee: (unassigned) => Federico Pelloni (fredp)
** Changed in: ejecter
Importance: Wishlist => Critical
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchpad.net/bugs/424256
You received this bug notification be
I'm sorry I couldn't fix this, but it's not very straightforward.. it
involves switching away from Hal to go for... !?
Here I have to move a little criticism (to whom I don't really know anyway).
What the hell should we use to manage devices? What's going on with Gio, Hal,
devicekit-disks, gudev
10 matches
Mail list logo
