[Bug 675857] [NEW] totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0
Public bug reported: Binary package hint: libglib2.0-0 This bug was encountered on Ubuntu 10.10 First noticed this problem with Totem but it extends to it seems any program using glib. Affected programs will not start up at all and just outputs an error about memory allocation onto stdout/err. (See attachment) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: totem 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Mon Nov 15 23:25:09 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release Candidate amd64 (20100928) ProcEnviron: PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: totem ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0 https://bugs.launchpad.net/bugs/675857 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 675857] Re: totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0
** Attachment added: Result when trying to start totem via commandline. https://bugs.launchpad.net/bugs/675857/+attachment/1734974/+files/startup.log -- totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0 https://bugs.launchpad.net/bugs/675857 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 675857] Re: totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0
Well it seems it was a problem with gstreamer. Deleting the .gstreamer directory in my home folder seems to have fixed the problem. I guess this bug can be considered invalid/closed. -- totem won't start. GLib-ERROR**: /build/buildd/glib2.0-2.26.0 https://bugs.launchpad.net/bugs/675857 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 112840] Re: GNOME freezes after log-in for 70/80 seconds then defreezes
Solved, it was a network related issue. After the upgrade to Feisty, the configuation of /etc/network/interfaces had been altered. Fixing this file made GNOMe boot normally. I found another bug here saying the same thing, but I don't seem to find it anymore, sorry. So mine is a duplicated bug afterall. -- GNOME freezes after log-in for 70/80 seconds then defreezes https://bugs.launchpad.net/bugs/112840 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 112840] GNOME freezes after log-in for 70/80 seconds then defreezes
Public bug reported: I upgraded from Edgy to Feisty and the process was OK. Now GDM starts, I log-in, appears the light orange backgound of ubuntu and the process freezes, the mouse can be moved, and in the upper left corner of the screen a white rectangle is visibile. The system stays like this for 70/80 seconds. Then I can hear the session start music and the white rectangle becomes a window with the following message: There has been an error starting the gnome settings daemon. Some aspects, such as themes, sound or backgroung settings may not work correctly. The last error message has been: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GNOME will try to start the setting daemon again at the next login. Or that's a translation by me, since I use the Italian version. What I tryed to solve this: 1) disable every starting application, such as network manager, battery monitor, evolution, ecc. 2) deleting every setting of gnome and letting it create the new setting files. 3) creating a new user andtrying loggin in with that new user None of this worked, as you can read in my ubuntu forum thread about this damned problem: http://ubuntuforums.org/showthread.php?p=2602229#post2602229 There you'll find some more informations about my problem. How can I solve this, please? ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: Unconfirmed -- GNOME freezes after log-in for 70/80 seconds then defreezes https://bugs.launchpad.net/bugs/112840 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
