[Bug 1113300] Re: gnome-control-center crashed with SIGSEGV in empathy_account_widget_apply_and_log_in() -> lookup_type_node_I()
Same problem here. I did a fresh install of Ubuntu 13.04 AMD64 and used my old Ubuntu 12.10 AMD64 home partition (located on another HDD). The problem occurs when attempting to create an AIM, ICQ or Yahoo! account. I've already tried to remove the .mission-control .config/signond .config/libaccounts-glib directories with no effect. My previously configured Facebook and Google accounts were gone afterwards however. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1113300 Title: gnome-control-center crashed with SIGSEGV in empathy_account_widget_apply_and_log_in() -> lookup_type_node_I() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1113300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 179552] Re: [Hardy] gnome-session hangs on log in
*** This bug is a duplicate of bug 136529 *** https://bugs.launchpad.net/bugs/136529 I've got the same problem on my laptop. The strange thing is that logging in to the GNOME session works fine with the previous 2.6.22 kernel but won't work with the new 2.6.24 kernel. I should probably mention that I'm not able to boot the new kernel at all without partially disabling ACPI before - by providing "acpi=ht" in the boot options. After doing this the system boots up fine - but hangs at the described point above (with exactly the same error messages in .xsession-errors). I'm using running Hardy on a Samsung R60Plus Notebook - Core 2 Duo T5450 (@1.66GHz) - 2048 MB RAM - ATI Mobility Radeon X2300 If you need further logfiles etc. then please let me know. -- [Hardy] gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
Okay, as I was so stupid to post in a report that was marked as a duplicate of this one, I'll post my problem here (thanks for the hint Pär ;-)). I've got the same problem as all people do here - when I try to login to a GNOME session the screen just freezes at the brown Ubuntu background. I can still move my mouse pointer though and switch to the console via Ctrl-Alt-F1 (or any other function key). The only really weird thing is that this only happens with the new 2.6.24 kernel. As with kernel 2.6.24-2 I couldn't even boot my system without providing the "acpi=off" or "acpi="ht" boot-option. However, this problem is now gone (or it has been solved) when I dist-upgraded to kernel 2.6.24-3 this morning - but I still can't login to any gnome session. This also goes for the GNOME failsafe session and the problem isn't solved by disabling the dual core functionality in the BIOS or by providing the "acpi=off" boot-option. As I said before, everything works fine with the old gutsy kernel 2.6.22 and other versions before, so it might have something to do with the kernel itself (but don't take my word for it, I don't know what exactly causes the problem). I'm using the latest Hardy version, with all the upgrades and dist-upgrades so far - and apart from a self-compiled ndiswrapper (latest SVN) every package on my system is in its original state. I should also mention that I didn't compile ndiswrapper for the 2.6.24 kernel so far, so it shouldn't be the cause of this problem. I don't know if it's related to this specific bug, but the avahi daemon won't start with the 2.6.24 kernel (it just tells me that the start failed at boot time) and when I'm trying to use the command "sudo" on the console the system also hangs (I can still type things via keyboard and switch to another console, but I can't kill nor abort the process). Well, that seems to be it for now. I'll attach a few logfiles (tell me if you need more). Here are my system specs: - Samsung R60Plus Notebook with a - Core2Duo T5450 (@1.66GHz) CPU - 2048 MB RAM - ATI Mobility Radeon X2300 - and nothing attached but a small mouse Cheers, Bernhard ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/11206361/dmesg.log -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
** Attachment added: "varlogmessages.log" http://launchpadlibrarian.net/11206369/varlogmessages.log -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/11206374/Xorg.0.log -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
Thanks for the hint. But unfortunately this doesn't work for me either. I did like you told me and removed the gdm autostart links with "update-rc.d -f gdm remove". Then I created a .xinitrc file with "exec gnome-session" in it and rebooted my machine. After logging in via terminal I then executed the "startx" script and my machine stops at exactly the same point as before - only that now I don't see the brown Ubuntu background but the grey background of the X server (along with its mouse pointer). I then switched back to the console and listed all running processes and it seems that gnome-session, gnome-settings-manager, metacity, pulseaudio, etc. have actually been started. But at some unknown point the system still just stops loading my GNOME session. So it seems that this has actually nothing to do with gdm - after booting the old 2.6.22 kernel again it works fine (that's how I'm writing here). What am I supposed to do now? Any suggestions? I'm thinking about opening a new bugreport now, but I don't know wether this is a good idea or not. -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
First of all, thanks for all the help here! I just wanted to add that just using "startx&" without creating a .xinitrc ends with the same results: my GNOME session won't start. After a few seconds of harddisk activity the PC just stops loading and does nothing anymore (at least as far as I can see). I have indeed upgraded my machine from Feisty to Gutsy and from there to Hardy via the dist-upgrade option (meaning via network). I tried to do a fresh install yesterday with the daily live CD of 2008-01-08, but as this CD still seems to use the 2.6.24-2 kernel it didn't even boot at first. I then used the boot option "acpi=off" and the kernel seemed to boot at first - but then just stopped while trying to start the X session and fell back to the console. I tried to get it to run manually, but that didn't work either. I've had the same problems with the Alpha 2 live CD. I'll now try to kill gnome-keyring after boot and report back with the results. Bernhard -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
Oh well, it seems my problem regarding the not-starting GNOME session is only the tip of the iceberg. Remember you told me to remove gdm from being automatically started at boot time jtholmes? Well, I did this yesterday and after it didn't work out the way it should, I restored the settings with "update-rc.d gdm defaults". Afterwards I didn't boot the kernel 2.6.24-3 anymore - until now. It seems that the running order of the programs at boot time has changed now (which isn't a problem at all) and now cupsys gets loaded before gdm. That shouldn't be a problem, only that now my systems stops booting when trying to load cupsys and GDM doesn't show up anymore. So I switched to a console, only to find out that the cups daemons are obviously running, but so is also the S20cupsys script (which should have long exited by now). Okay, I thought that maybe it's all the fault of the printer service and deactivated it (via "update-rc.d -f cupsys remove") and rebooted my machine. GDM started up then, I logged in - and still the GNOME session just stops loading after a few seconds. So I switched to a console, did "ps -e" - only to see that now the NFS autostart script (S20nfs-kernel-service) stopped responding. The nfsd daemons were loaded, but the script didn't exit. So I also deactivated nfs, only to see that after a reboot it showed the same behaviour with the Samba daemons. And now I'm really at a loss here. To me it seems that the system just doesn't boot completely and maybe that's exactly the problem with my not-starting GNOME session. I don't know for sure though - for that I'm just too unexperienced. -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 136529] Re: Can't log in after upgrading
I just wanted to inform you that I've solved the problem with my system not booting properly and the not starting gnome session. In my case it was a problem with the previously (and manually) installed ndiswrapper - I removed it and built it against the new kernel and everythings is working fine now. Sorry for the possible trouble I've caused here and thanks for your help ;-). -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185641] Re: [hardy] Stretch icon feature doesn't work
Oh, and I should also add that, just like mlind wrote before, everything worked fine until the nautilus upgrade. -- [hardy] Stretch icon feature doesn't work https://bugs.launchpad.net/bugs/185641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185641] Re: [hardy] Stretch icon feature doesn't work
I've got exactly the same problem here. The default GNOME icons are stretching fine, while some icons of custom-made desktop launchers won't stretch at all. Other icons (like e.g. ScummVM's or Thunderbird's) are even replaced by default ones. -- [hardy] Stretch icon feature doesn't work https://bugs.launchpad.net/bugs/185641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
