giplet crashed with GError in readFromGConf()

[elcanux]

Just after updating 9.04 this morning. (it was working fine yesterday & last week).

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/giplet/giplet
InterpreterPath: /usr/bin/python2.6
Package: giplet 0.2.0-1
PackageArchitecture: all
ProcCmdline: python /usr/lib/giplet/giplet --oaf-activate-iid=OAFIID:GNOME_GipletApplet_Factory --oaf-ior-fd=28
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/giplet/giplet', '--oaf-activate-iid=OAFIID:GNOME_GipletApplet_Factory', '--oaf-ior-fd=28']
SourcePackage: giplet
Title: giplet crashed with GError in readFromGConf()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Salvatore Bonaccorso (carnil)]

Architecture: i386
DistroRelease: Ubuntu 9.04
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Alpha i386 (20090225.1)
Package: giplet 0.2.0-1
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups:

[Salvatore Bonaccorso (carnil)]

Hi

I tried to reproduce your crash, but cannot on a up to date jaunty. Could you still reproduce the crash? Does it also appear after updating jaunty? As you see from dependency list, python2.6 is the same you have (2.6.2~rc1-0ubuntu1).

Bests
Salvatore

[elcanux (elcanux)]

Hi,
This crash appear on each reboot sytem, at startup.
It's not appear after updating... but after 2 weeks updating jaunty.

Thanks,
Laurent

[Salvatore Bonaccorso (carnil)]

Hi

Sorry for the late reply, had some problems with my laptop.

On Sat, Apr 11, 2009 at 08:42:48PM -0000, masterlolo wrote:
> This crash appear on each reboot sytem, at startup.
> It's not appear after updating... but after 2 weeks updating jaunty.

I just tried again to reproduce this in a up to date jaunty, but
can't. Can anyone help on this?

@masterlolo: could you try to purge giplet completely, and reinstall
it?

Bests
Salvatore

[elcanux (elcanux)]

I have checked dont't report this next time. I can see if this bug is always on.

Before checked, I have try to deleted, purged giplet & reinstall : same bug on reboot.
After add it on my bar, the address IP was my local address (192.168.x.x). My preferences was : eth0 www.getmyip.org
I have try to change it and I have deleted 'eth0'... then this bug appear again ! (maybe a way)
Then, I have change preferences eth0, by eth1 and add other server to get my IP all is work fine now (I have correct plubic IP Adress). My preferences is now : eth1 www.getmyip.org monip.org

Note, I have only one card, as you can see :
eth0 Link encap:Ethernet HWaddr 00:16:e6:84:30:dd
          inet adr:192.168.1.10 Bcast:192.168.222.255 Masque:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Boucle locale
          inet adr:127.0.0.1 Masque:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1

If you don't see what the real bug, you can close it. For my side, it's ok and in next month I will reinstall Ubuntu

[Salvatore Bonaccorso (carnil)]

Hi!

On Sun, Apr 19, 2009 at 07:29:12AM -0000, masterlolo wrote:
> I have checked dont't report this next time. I can see if this bug is
> always on.
>
> Before checked, I have try to deleted, purged giplet & reinstall : same bug on reboot.
> After add it on my bar, the address IP was my local address (192.168.x.x). My preferences was : eth0 www.getmyip.org
> I have try to change it and I have deleted 'eth0'... then this bug appear again ! (maybe a way)
> Then, I have change preferences eth0, by eth1 and add other server to get my IP all is work fine now (I have correct plubic IP Adress). My preferences is now : eth1 www.getmyip.org monip.org
>
> Note, I have only one card, as you can see :
> eth0 Link encap:Ethernet HWaddr 00:16:e6:84:30:dd
> inet adr:192.168.1.10 Bcast:192.168.222.255 Masque:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> lo Link encap:Boucle locale
> inet adr:127.0.0.1 Masque:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
>
> If you don't see what the real bug, you can close it. For my side, it's
> ok and in next month I will reinstall Ubuntu

I just checked it again, now in a up to date jaunty. I don't think I
should simply ask to close this bug. But I'm still not able to
reproduce the crash. The following, if you have "eth0 www.getmyip.org"
in preferences, then first giplet probes eth0, then www.getmyip.org,
if it get's an ip from eth0, it will show the local ip. If eth0 is
missing in preferences, then it probes only www.getmyip.org, but if
this site is down, then giplet will show only the text "giplet". With
your last preferences "eth1 www.getmyip.org monip.org", if there is no
eth1, then it will probe www.getmyip.org, if from there there is also
neither an ip returned, monip.org is probed.

I can anyway try to ask upstream author about this Bug. On the other
side there was LP#307170. Lyman Li added a "timout functionality" to
giplet in 0.2.1, but this version didn't reach jaunty, since I
submitted the request for sync from Debian to late LP#354139.

If you have a testing environment, you can try to install the giplet
version in my PPA (the one in Debian sid).

Bests
Salvatore

[Salvatore Bonaccorso (carnil)]

Hi Laurent

Could you please try it with the new version now synced from Debian? If you do not use karmic, then I also have uploaded an updated version to my PPA.

Bests
Salvatore

[elcanux (elcanux)]

Hi Salvatore,

Great, It' work fine with your package "giplet_0.2.2-2.jaunty~ppa.1_all.deb"

Thanks for all.
Laurent

[elcanux (elcanux)]

Bug resolv with new version

[Salvatore Bonaccorso (carnil)]

Hi Laurent

But please note, I'm not sure if I can ask for an "backported" version to jaunty for the karmic version, but I will check that if this is possible, with a simplified diff without the change in e.g. build-dependencies (python-support, instead of python-central, ...)

Bests
Salvatore

[dino99 (9d9)]

This version has died long ago; no more supported