[Bug 619663] Re: [maverick] Non-mirrored dual-screen gives narrow display on secondary monitor

2010-11-01 Thread Cliff Dyer
Flickering is a different issue. File a new ticket (or find another one which matches your problem). This is about not rendering widths 2048 pixels. -- [maverick] Non-mirrored dual-screen gives narrow display on secondary monitor https://bugs.launchpad.net/bugs/619663 You received this bug

[Bug 654619] Re: [945gme] Failed to allocate framebuffer with width 2048 with intel 2.12 drivers.

2010-10-08 Thread Cliff Dyer
*** This bug is a duplicate of bug 619663 *** https://bugs.launchpad.net/bugs/619663 I can confirm that it did indeed fix my problem, with the xorg.conf back in place. Thanks so much! -- [945gme] Failed to allocate framebuffer with width 2048 with intel 2.12 drivers.

[Bug 619663] Re: [maverick] Non-mirrored dual-screen gives narrow display on secondary monitor

2010-10-08 Thread Cliff Dyer
It also fixed my problem, reported over on #654619, where I couldn't get X to start at all. Thanks! -- [maverick] Non-mirrored dual-screen gives narrow display on secondary monitor https://bugs.launchpad.net/bugs/619663 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-07 Thread Cliff Dyer
Moving my xorg.conf out of the way allows me to get into X. See attached file. ** Attachment added: xorg.conf https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/654619/+attachment/1676929/+files/xorg.conf -- X will not start on Acer Aspire One (intel drivers)

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
** Attachment added: Xorg log displaying the relevant errors. https://bugs.launchpad.net/ubuntu/+bug/654619/+attachment/1671549/+files/Xorg.0.log -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
Running X or xinit or startx from the command line, I also get: Fatal server error: AddScreen/ScreenInit failed for driver 0 -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are a member of

[Bug 654619] [NEW] X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
Public bug reported: I just updated my Acer Aspire One to Maverick pre-release (aptitude safe-upgraded as of ~10:00 AM EDT 2010/10/04), and when it loads up, I get dropped into the console, instead of GDM. My Xorg.0.log file shows the following errors: (EE) intel(0): Failed to allocate

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
Just tried it, and had no change in my error messages. -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
I'm not sure if you meant something special by run a live session, but I'm attaching the requested files from the failing system. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+bug/654619/+attachment/1671582/+files/dmesg -- X will not start on Acer Aspire One (intel drivers)

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
** Attachment added: kern.log https://bugs.launchpad.net/ubuntu/+bug/654619/+attachment/1671583/+files/kern.log -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+bug/654619/+attachment/1671584/+files/syslog -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 654619] Re: X will not start on Acer Aspire One (intel drivers)

2010-10-04 Thread Cliff Dyer
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+bug/654619/+attachment/1671585/+files/Xorg.0.log -- X will not start on Acer Aspire One (intel drivers) https://bugs.launchpad.net/bugs/654619 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 453179] Re: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/rc80211_minstrel.c:69 minstrel_tx_status+0x66/0xd0 [mac80211]()

2009-10-16 Thread Cliff Dyer
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/33787855/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/33787856/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt

[Bug 453179] [NEW] WARNING: at /build/buildd/linux-2.6.31/net/mac80211/rc80211_minstrel.c:69 minstrel_tx_status+0x66/0xd0 [mac80211]()

2009-10-16 Thread Cliff Dyer
Public bug reported: Problem started when I was trying to install a package (ERIC, I think), using the Ubuntu Software Center. Finally got crash report after adding user switcher to panel, while doing basic web browsing (Firefox) and checking email (Evolution). ProblemType: KernelOops

[Bug 395540] Re: evolution recieves, but won't send

2009-09-29 Thread Cliff Dyer
I've got a similar problem. I'm not sure if it's the same bug, though. If I should file a separate bug report, please let me know. When evolution is trying to send a message, it never completes. The message gets sent (not sure if multiple messages get sent or not. It might hang on the first

[Bug 395540] Re: evolution recieves, but won't send

2009-09-29 Thread Cliff Dyer
This log contains the output from trying to send a message, followed by trying to change folders (to Lists or Lists/Something, I can't remember which), trying to close Evolution, and then issuing a `killall evolution`. ** Attachment added: jcd-evo.log