** Changed in: vala (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/424256
Title:
Ejecter crashes due to missing gvfs hal volume monitor.
To manage
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Branch linked: lp:ubuntu/ejecter
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package ejecter - 0.2.1+karmic-gdu-
bzr68-0ubuntu1
---
ejecter (0.2.1+karmic-gdu-bzr68-0ubuntu1) karmic; urgency=low
* New upstream bzr revision 68 from karmic-gdu branch (LP: #427312, #424256,
#403143).
* Drop quilt support.
* debian/control:
It works ok.. no warnings at all :)
thanks Federico!
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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.
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
I'm trying the new brach on Karmic and seems to work ok.
I get some warning when launched:
** (ejecter:4286): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY
(proxy)' failed
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchpad.net/bugs/424256
You received
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
The critical message is because you're passing an invalid DBusGProxy to
dbus_g_proxy_call.
If you want to do disk management stuff outside of the capabilities of
GIO, then the library you want really is GDU
--
Ejecter crashes due to missing gvfs hal volume monitor.
Today I upgraded to Karmic and I'm trying to work on this.. But I'm
having serious trouble, it doesn't compile because of missing Dbus
headers. Vala's fault as usual?
** Changed in: ejecter
Importance: Undecided = Wishlist
** Changed in: ejecter
Status: New = In Progress
** Changed
@Federico: I think you can easily fix this using C code. Just call
libhal_manger_find_device_string_match in order to get the udi of the
device.
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchpad.net/bugs/424256
You received this bug notification because you are a
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
I'm trying to fix this, if I won't be able to do it, I will ask to
remove ejecter package from Ubuntu.
** Changed in: ejecter (Ubuntu)
Status: New = In Progress
--
Ejecter crashes due to missing gvfs hal volume monitor.
https://bugs.launchpad.net/bugs/424256
You received this bug
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,
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Low
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
the issue is not a gvfs one
** Changed in: gvfs (Ubuntu)
Status: New = Invalid
--
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
Bugs, which is subscribed to Ubuntu.
--
Really don't think it's a Vala bug either. The problem is 'ejecter'
needs to be ported to DeviceKit-Disks and stop using HAL altogether.
--
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
19 matches
Mail list logo
