[Bug 216871] Re: gdm uses incorrect resolution

2008-10-22 Thread Daniel Nelson
This seems to be fixed for me too. I installed the Intrepid beta and GDM showed the correct resolution once I set up my xorg file (my monitor is not detected properly). I'll mark as fixed. -- gdm uses incorrect resolution https://bugs.launchpad.net/bugs/216871 You received this bug notification

[Bug 216871] Re: gdm uses incorrect resolution

2008-10-22 Thread Daniel Nelson
This appears to have been fixed in Intrepid as of the beta. ** Changed in: gdm (Ubuntu) Status: Confirmed => Fix Released -- gdm uses incorrect resolution https://bugs.launchpad.net/bugs/216871 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a

[Bug 442627] Re: evolution crashed with SIGSEGV in comp_subject()

2010-10-20 Thread Daniel Nelson
I can confirm that this still occurs in Evolution 2.30 on Ubuntu 10.10 x86_64. -- evolution crashed with SIGSEGV in comp_subject() https://bugs.launchpad.net/bugs/442627 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs

[Bug 442627] Re: evolution crashed with SIGSEGV in comp_subject()

2010-10-25 Thread Daniel Nelson
Based on the upstream bug report, it looks like a new version of libical must be installed, as well as a patch being applied to Evolution. What are the next steps for getting this fix into current Ubuntu releases? Since it causes a crash, I think it's a good candidate for a release in -updates. -

[Bug 215395] Re: nautilus crashed with SIGSEGV

2008-04-10 Thread Daniel Nelson
** Visibility changed to: Public -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/215395 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com http

[Bug 216871] [NEW] gdm uses incorrect resolution

2008-04-13 Thread Daniel Nelson
Public bug reported: I'm having a similar issue to the one described in #146828, but with Hardy. My monitor's native resolution is 1600x1200. When I installed hardy (console-based net-install), my monitor (Samsung SyncMaster213T) and/or video card (Intel GMA33 onboard) did not get autodetected p

[Bug 216871] Re: gdm uses incorrect resolution

2008-04-13 Thread Daniel Nelson
** Attachment added: "xorg.conf" http://launchpadlibrarian.net/13410322/xorg.conf -- gdm uses incorrect resolution https://bugs.launchpad.net/bugs/216871 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs

[Bug 216871] Re: gdm uses incorrect resolution

2008-04-13 Thread Daniel Nelson
Setting this as affecting GDM, although it might well be an xorg (or some config package) issue, as I figure the GDM people will know if it's really their job. ** Changed in: gdm (Ubuntu) Sourcepackagename: None => gdm -- gdm uses incorrect resolution https://bugs.launchpad.net/bugs/216871 You r

[Bug 215395] Re: nautilus crashed with SIGSEGV

2008-04-21 Thread Daniel Nelson
I can no longer reproduce this bug, and I do not have access to the computer that it happened on (a Vista box), and although I tried to reproduce the environment on another system (a WinXP box), it may have been Vista specific problem or something. I will have access to the system a week from Wedn

[Bug 78201] Re: Network history display incorrect

2008-06-30 Thread Daniel Nelson
This still occurs on Hardy (x86_64) ** Changed in: gnome-system-monitor (Ubuntu) Status: Invalid => Confirmed -- Network history display incorrect https://bugs.launchpad.net/bugs/78201 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assig

[Bug 78201] Re: Network history display incorrect

2008-06-30 Thread Daniel Nelson
I can confirm that this still occurs on Hardy x86_64 ** Attachment added: "1second.png" http://launchpadlibrarian.net/15693269/1second.png -- Network history display incorrect https://bugs.launchpad.net/bugs/78201 You received this bug notification because you are a member of Ubuntu Desktop B