[Kernel-packages] [Bug 1197902] Re: Display corruption on 29 2560x1080 monitor

2013-11-03 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197902

Title:
  Display corruption on 29 2560x1080 monitor

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  I have a 29 monitor that supports a native resolution of 2560x1080.
  Using the nouveau driver with kernel mode setting correctly set the
  resolution of the display, as indicated in the gnome-control-center -
  display configuration utility, but the display appears to running at a
  much lower apparent resolution.  Text is almost unreadable, everything
  appears incredibly fuzzy.  I attempted to use the proprietary nvidia
  drivers, and after using the nvidia-xconfig utility to generate a
  xorg.conf file and restarting the machine it is indeed using the
  proprietary driver and hardware acceleration is working, but the fuzzy
  condition persists.

  I am using Ubuntu 13.04, I have updated all the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1197902] Re: Display corruption on 29 2560x1080 monitor

2013-09-04 Thread Christopher M. Penalver
Anthony Brennan, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal (Applications-Accessories-Terminal), as it will
automatically gather and attach updated debug information to this
report:

apport-collect -p linux replace-with-bug-number

Andreas Raster, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug 
Control team, and Ubuntu Bug Squad would like you to please file a new report 
by executing the following in a terminal while booted into a Ubuntu repository 
kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being
addressed as quickly as possible.

No need exists to comment here at this time. After reading the above
documention in it's entirety, if you have further questions, you are
welcome to redirect them to the appropriate mailing list or forum via
http://www.ubuntu.com/support/community/mailinglists , or you may
contact me directly.

Thank you for your understanding.

** Tags added: needs-kernel-logs needs-upstream-testing regression-
potential

** Tags removed: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197902

Title:
  Display corruption on 29 2560x1080 monitor

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have a 29 monitor that supports a native resolution of 2560x1080.
  Using the nouveau driver with kernel mode setting correctly set the
  resolution of the display, as indicated in the gnome-control-center -
  display configuration utility, but the display appears to running at a
  much lower apparent resolution.  Text is almost unreadable, everything
  appears incredibly fuzzy.  I attempted to use the proprietary nvidia
  drivers, and after using the nvidia-xconfig utility to generate a
  xorg.conf file and restarting the machine it is indeed using the
  proprietary driver and hardware acceleration is working, but the fuzzy
  condition persists.

  I am using Ubuntu 13.04, I have updated all the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1197902] Re: Display corruption on 29 2560x1080 monitor

2013-09-03 Thread Andreas Raster
I have the same problem and just tested with the latest mainline kernel
[0]. The problem wasn't fixed.

I also tried different propietary driver versions (I am using fglrx) and
the open source radeon driver, both of which showed the same wrong
behaviour. I think I should be able to fix the problem by just forcing a
mode with a manually written xorg.conf and will try that later.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc7-saucy/

** Tags added: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197902

Title:
  Display corruption on 29 2560x1080 monitor

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I have a 29 monitor that supports a native resolution of 2560x1080.
  Using the nouveau driver with kernel mode setting correctly set the
  resolution of the display, as indicated in the gnome-control-center -
  display configuration utility, but the display appears to running at a
  much lower apparent resolution.  Text is almost unreadable, everything
  appears incredibly fuzzy.  I attempted to use the proprietary nvidia
  drivers, and after using the nvidia-xconfig utility to generate a
  xorg.conf file and restarting the machine it is indeed using the
  proprietary driver and hardware acceleration is working, but the fuzzy
  condition persists.

  I am using Ubuntu 13.04, I have updated all the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1197902] Re: Display corruption on 29 2560x1080 monitor

2013-07-23 Thread madbiologist
** Package changed: initramfs-tools (Ubuntu) = linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197902

Title:
  Display corruption on 29 2560x1080 monitor

Status in “linux” package in Ubuntu:
  New

Bug description:
  I have a 29 monitor that supports a native resolution of 2560x1080.
  Using the nouveau driver with kernel mode setting correctly set the
  resolution of the display, as indicated in the gnome-control-center -
  display configuration utility, but the display appears to running at a
  much lower apparent resolution.  Text is almost unreadable, everything
  appears incredibly fuzzy.  I attempted to use the proprietary nvidia
  drivers, and after using the nvidia-xconfig utility to generate a
  xorg.conf file and restarting the machine it is indeed using the
  proprietary driver and hardware acceleration is working, but the fuzzy
  condition persists.

  I am using Ubuntu 13.04, I have updated all the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1197902] Re: Display corruption on 29 2560x1080 monitor

2013-07-23 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc2-saucy/

** Changed in: linux (Ubuntu)
   Importance: Undecided = Medium

** Tags added: raring

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197902

Title:
  Display corruption on 29 2560x1080 monitor

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have a 29 monitor that supports a native resolution of 2560x1080.
  Using the nouveau driver with kernel mode setting correctly set the
  resolution of the display, as indicated in the gnome-control-center -
  display configuration utility, but the display appears to running at a
  much lower apparent resolution.  Text is almost unreadable, everything
  appears incredibly fuzzy.  I attempted to use the proprietary nvidia
  drivers, and after using the nvidia-xconfig utility to generate a
  xorg.conf file and restarting the machine it is indeed using the
  proprietary driver and hardware acceleration is working, but the fuzzy
  condition persists.

  I am using Ubuntu 13.04, I have updated all the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197902/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp