Chris, is there a possibility to backport the fix to Quantal? It really
makes the computer difficult to use as it hangs every few minutes, in
particular when scrolling. This has been happening to me since the
kernel update on Wednesday 20th March (when this bug was first
reported).
What info is re
Just in case that's useful, here's my i915_error_state too. I understand
that it's fixed in Raring but Raring has not been released yet so for
all users who do not fancy upgrading to a pre-release version, is there
a way to backport the fix? The reason I ask is because the bug is really
debilitatin
Chris, I can't find the TLB Invalidate bug. Can you link to it from this
bug please? I would like to help contribute to that one if that's the
root cause.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https:/
I got this crash on Raring x86_64 after a dist-upgrade today.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1134112
Title:
Xorg crashed with SIGABRT in OsAbort()
To manage notifications
I also have the same symptoms as Lorenzo (comment #8) regarding "low
graphics mode", especially during a warm reboot: cold boot seems not to
show the issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
Public bug reported:
I'm not sure this is the correct package nor whether it's a single bug
but I'm happy to analyse further if someone can help me do so. I just
did an apt-get dist-upgrade on my machine and here's what happened:
1. Ran sudo apt-get update && sudo apt-get dist-upgrade;
2. At the
** Package changed: linux (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)
** Also affects: gnome-control-center
Importance: Undecided
Status: New
--
touchpad tap-to-click doesn't works after update to karmic from jaunty
https://bugs.launchpad.net/bugs/379203
You received this bug not
Max, I can confirm that the commands above re-enable tap-to-click on my
T42.
--
touchpad tap-to-click doesn't works after update to karmic from jaunty
https://bugs.launchpad.net/bugs/379203
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Note that the gnome-control-center task exists to represent the need to
assess whether gnome-mouse-properties needs changes to integrate nicely
with the synaptics change mentionned above.
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
touchpad tap-
*** This bug is a duplicate of bug 217908 ***
https://bugs.launchpad.net/bugs/217908
** This bug has been marked a duplicate of bug 217908
Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD
implementation in several video drivers
--
poor image quality rescaling
https://bugs.l
** Package changed: ubuntu => xserver-xorg-input-synaptics (Ubuntu)
--
unstoppable scrolling synaptics touchpad
https://bugs.launchpad.net/bugs/355372
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
_
** Package changed: ubuntu => xorg-server (Ubuntu)
--
My 22" Monitor is not detected upon startup when plugged into my laptop.
https://bugs.launchpad.net/bugs/355165
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
*** This bug is a duplicate of bug 378391 ***
https://bugs.launchpad.net/bugs/378391
Note that this is a duplicate of bug #378391 that has been confirmed
solved in the final release of Karmic that uses kernel
2.6.31-14-generic. If you wish to comment further, please do so on bug
#378391.
--
Geir, would there be any way to backport this fix to Karmic? Should I
open a new bug against karmic-backports for this?
--
blender-bin crashed with SIGSEGV in GPU_state_init()
https://bugs.launchpad.net/bugs/446632
You received this bug notification because you are a member of Ubuntu-X,
which is
I can confirm that it works perfectly well in release Karmic: tap to
click is enabled by default and works as expected (typed from a newly
Karmic Eee PC).
--
Source rename clobbered local changes (so tapping not working in Karmic)
https://bugs.launchpad.net/bugs/378391
You received this bug notif
** Changed in: xkeyboard-config (Ubuntu)
Status: New => Confirmed
--
Variant keyboard layouts are numbered with a subscript instead of something
more descriptive
https://bugs.launchpad.net/bugs/475280
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
I can confirm that with the United Kingdom layouts too. Steps to
reproduce:
1. Go to System -> Preferences -> Keyboard
2. Select the Layout tab
3. Click Add...
4. Select the same country as your primary layout but a different variant.
5. Click Add
6. Click Close
Expected behaviour:
The keyboard l
@dzidzitop: I'm happy to report it upstream but before I do that, I
would like to make sure I fully understand the issue and it looks to me
like there are 2 distinct sets of problems: for Latin keymaps on the one
hand and for Cyrillic keymaps on the other. So my understanding is that:
On Latin Bel
@Simos: I agree that you do see the subscript with the current version
of Lucid so the issue in comment #2 seems to have been resolved. I also
agree that the area in the panel is limited. This is still a valid
usability issue though, especially for users who use several keyboard
layouts on a regula
Public bug reported:
Binary package hint: xserver-xorg-video-ati
When attaching an external monitor to the VGA port of my IBM ThinkPad
T42, the output is corrupted if I attempt to extend the desktop to the
external monitor. It works as expected when I set the external monitor
as a mirror of the L
A photo taken of the laptop's LCD showing the corruption.
** Attachment added: "L1000899.JPG"
http://launchpadlibrarian.net/51924310/L1000899.JPG
--
Radeon Mobility 7500: corrupted display in dual-monitor, no mirroring
configuration
https://bugs.launchpad.net/bugs/605395
You received this bu
A screenshot taken in the dual-head configuration showing what the
laptop *thinks* it's displaying.
** Attachment added: "Screenshot-multi-screen.png"
http://launchpadlibrarian.net/51924368/Screenshot-multi-screen.png
--
Radeon Mobility 7500: corrupted display in dual-monitor, no mirroring
c
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/51923922/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/51923923/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51923924/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
Following an update a few days ago, my laptop's screen is detected as
having a 16:9 ratio rather than a 4:3 ratio and the display is set to
1360x768 pixels rather than 1024x768. As a result, the GDM login box is
shifted to the right and, once logged
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/641525/+attachment/1599255/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/641525/+attachment/1599256/+files/CurrentDmesg.txt
** Attachment added: "DRM.card0.SVIDEO.1.txt"
Photograph of login screen demonstrating the bug.
** Attachment added: "ubuntu-screen-ratio-bug.JPG"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/641525/+attachment/1599279/+files/ubuntu-screen-ratio-bug.JPG
--
Screen with 4:3 ratio incorrectly detected as having 16:9 ratio
https://bu
26 matches
Mail list logo
