** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1637598
Title:
Screen corruption on docking station
Public bug reported:
bottom and right side of external monitor is corrupted when Lenovo T450s
laptop is connected to docking station.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic
I haven't seen this bug in a week or two. When it existed, the x would
crash continuously. Closing bug, will reopen if I notice it again.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
x crashes randomly throughout the day. At first I thought it was bug
#1041790, but the workaround does not work.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname:
No crashes in 4 days from the package in precise-proposed, looks good so
far.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/956071
Title:
Xorg crashed with SIGSEGV in
Upgrading to critical:
This is a bug that meets all of the following:
A bug which has a severe impact on a large portion of Ubuntu users
Causes data corruption
Crashes the entire operating system
Renders the system temporarily or permanently unusable
Severely affects applications
Look around the internet, I may have found what appears to be upstream
reports:
Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681796
Xorg:
http://patchwork.freedesktop.org/patch/11531/
Debian is showing this SIGSEV:
XIChangeDeviceProperty (dev=dev@entry=0x7f4bac237fa0,
Follow up, here's the xorg bug that debian is referring to:
https://bugs.freedesktop.org/show_bug.cgi?id=52496
I linked both to the tracker here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I am not too familiar with this bug, but I can across a recent patch
[1] to x.org to fix a memory leak in XICreateDeviceProperty(), around
the same lines where this crash is happening.
Error: Memory leak (CWE 401)
Memory leak of pointer 'prop' allocated with XICreateDeviceProperty(property)
unknown fix in the last week of maverick testing. It works again in
maverick, just doesn't work in lucid
** Changed in: linux (Ubuntu)
Status: Triaged = Invalid
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Triaged = Invalid
--
[R350] Transient screen
Fixed with updates last night, it may be a G-D-M, gnome-settings-daemon
issue... Setting to Invalid since we don't exactly know what fixed it.
If the problem persists for the others, please reset this bug to
confirmed.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Invalid
--
** Summary changed:
- [R350] Wrong monitor resolution chosen after upgrading from maverick alpha to
beta
+ Wrong monitor resolution chosen after upgrading from maverick alpha to beta
** Package changed: xserver-xorg-video-ati (Ubuntu) = xorg (Ubuntu)
--
Wrong monitor resolution chosen after
Public bug reported:
Binary package hint: xorg
My monitor is natively 1440x900, and this was properly detected in all
previous releases and the alphas for 10.10. The most recent updates,
however, cause my monitor to default to 1280x1024. I changed the monitor
setting in the gnome control panel
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/642831/+attachment/1608669/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/642831/+attachment/1608670/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
Here's a you-tube video of the symptoms, taken from a different bug report:
http://www.youtube.com/watch?v=8Ky9Yk3pNuI
bug 541501
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you
while the symptoms are identical to bug 541501, the upgraded kernel does
not fix my bug. I also have a desktop, not a thinkpad.
Loading without KMS is working as a work around for now.
uname -r
2.6.35-020635rc1-generic
** This bug is no longer a duplicate of bug 541501
[RV515] [LENOVO T60]
It didn't go away with updates, but I refrained from adding more
comments until I debugged it. I have tested it with KMS off, and the
screen is perfect. I've been toggling the setting over the course of the
past week to ensure that is the problem. I've tried the xorg-edgers ppa
and the newest
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/47791368/WifiSyslog.txt
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [R350] Transient screen tearing/corruption/waviness in lucid
+ [R350] Transient
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/47791367/UdevLog.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/47791366/UdevDb.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/47791363/ProcModules.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/47791362/ProcInterrupts.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/47791361/ProcCpuinfo.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/47791357/PciMultimedia.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/47791355/Lsusb.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/47791354/Lspci.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/47791352/Card0.Amixer.values.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47791353/CurrentDmesg.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/47791325/ArecordDevices.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/47791351/BootDmesg.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member of
apport information
** Description changed:
Binary package hint: xserver-xorg-video-ati
[see attached photo]
I see extensive screen tearing and constant waviness. The amount of
tearing increases with increased video action (i.e. running glxgears,
editing a photo in GIMP).
-
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/47791324/AplayDevices.txt
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug notification because you are a member
also tested with the xorg-edgers ppa:
xserver-xorg-video-ati 1:6.13.99~git20100422.1ad41054-0ubuntu0tormod
** Tags removed: needs-upstream-testing
--
[R350] Transient screen tearing/corruption/waviness in lucid when using KMS
https://bugs.launchpad.net/bugs/557814
You received this bug
*** This bug is a duplicate of bug 541501 ***
https://bugs.launchpad.net/bugs/541501
** This bug has been marked a duplicate of bug 541501
[RV515] [LENOVO T60] external screen display shows shivering, horizontal
refresh offset
--
[R350] Transient screen tearing/corruption/waviness in
I have this bug, reported as duplicate bug #557814.
I have found that the screen shivering is still present in:
$ uname -a
Linux s-desktop 2.6.34-020634rc6-generic #020634rc6 SMP Fri Apr 30 09:08:46 UTC
2010 x86_64 GNU/Linux
with an r350 -ati driver (more info is at the linked bug report).
--
The bug went away with updates, can't tell exactly what - but I think it
had something to do with plymouth (I was have lots of crashes with
plymouth that also stopped the same time)
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed = Invalid
--
[R350] Transient screen
Public bug reported:
Binary package hint: xserver-xorg-video-ati
[see attached photo]
I see extensive screen tearing and constant waviness. The amount of
tearing increases with increased video action (i.e. running glxgears,
editing a photo in GIMP).
I've tried the following:
Compix off
Kernel
** Attachment added: screen shot of corruption
http://launchpadlibrarian.net/43406646/DSCN3045.JPG
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/43406338/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/43406339/CurrentDmesg.txt
**
I loaded as far back as:
Linux 2.6.32-15-generic #22-Ubuntu SMP x86_64 GNU/Linux
and the tearing is still present, although there was no tearing back
when -15 was the newest kernel.
--
[R350] Transient screen tearing/corruption/waviness in lucid
https://bugs.launchpad.net/bugs/557814
You
Thanks for the report, please see:
http://www.rvdavid.net/how-to-get-the-use-of-your-number-pad-back-in-ubuntu/
--
Numpad does not work (HP Pavilion dv6 2140ed)
https://bugs.launchpad.net/bugs/540474
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 197589 ***
https://bugs.launchpad.net/bugs/197589
http://eric.biven.us/2009/02/03/ubuntu-and-the-number-pad-that-wont-work/
http://tuxtraining.com/2009/10/27/fix-number-pad-will-not-work-in-ubuntu
I believe this is also a duplicate of bug #197589, and am
Hi Markus, could you make it crash and submit the apport crash report
[1] to this bug? We'd like to see the stack trace for your segfault.
Thanks.
https://wiki.ubuntu.com/Apport [1]
--
Stelaium crashes on startup due to fragmentation fault
https://bugs.launchpad.net/bugs/481669
You received
Just saw you are using 0.10.4, apport won't work. Could you use gdb [1]?
Thanks.
[1] https://wiki.ubuntu.com/Backtrace
--
Stelaium crashes on startup due to fragmentation fault
https://bugs.launchpad.net/bugs/481669
You received this bug notification because you are a member of Ubuntu-X,
which
Thanks. I'm adding the xorg intel drivers to this bug since both
reporters have Intel chipsets.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Monitor does not turn back on and computer hangs when laptop lid is closed
+
This is an important bug, are we sure it is fix released? So far all comments
have been from people testing the PPA. From Loic's comments:
Closing the GPM task as things work for me with the patched xorg-server which
I just uploaded; needs to be reviewed by release team still
I don't think it
** Changed in: xorg-server (Ubuntu)
Status: Fix Released = Triaged
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
I think multiple bugs are getting mixed together.
See bug 397839.
According to Bryce at that bug report, xorg has been properly patched
with both patches that Richard Hughes requests.
gnome-power-manager is at a version where its fix is included.
So xorg says the bug is invalid since they have
@mac: that warning was placed in to see if the conditions causing the
idle were still occuring in x. The author of GPM believes that the three
patches should have fixed it (and ubuntu has the three patches), but if
you are seeing the warnings, that means the bugs still remains in x
somewhere.
I
...@gmail.com wrote:
On 09/10/2009 10:02 AM, mac_v wrote:
The thing is that the patches described in Richard's blog have been applied
but none of them seem to have fixed this issue... :(
Seems like no one really knows where the problem really is !
Scott Howard , you might wanna consider re
From comment #22, we needed 3 patches: 2 for xorg and 1 for GPM. GPM's
patch was applied with 2.7.91-0ubuntu1 (that's why I put GPM to fixed
released). One of xorg's was applied with 2:1.6.3-1ubuntu2.
xorg-server still needs this patch:
The upload of GPM 2.27.91 included the patch. I no longer have screen
blanking problems, can anyone else confirm this? Thank you.
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Fix Released
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You
We still need these patches:
http://cgit.freedesktop.org/xorg/xserver/patch/?id=6b5978dcf1f7ac3ecc2f22df06f7000f360e2066
http://git.gnome.org/cgit/gnome-power-manager/patch/?id=b6ea044d3b67087ef2fd73f4647d7c5b2d17f8c8
182_negative_sync_transitions.patch only applies:
Sorry, I should have been more clear!
According to richard hughes, we need 3 patches. Two in xserver and one in GPM.
the patch 182_negative_sync_transitions.patch, which is in Ubuntu's xorg-server
package now applies one of the two x patches. That leaves the following x patch:
status triaged
On Thu, Aug 13, 2009 at 11:57 AM, Scott Howardshoward...@gmail.com wrote:
status triaged
On Thu, Aug 13, 2009 at 11:39 AM, TualatriXtualat...@gmail.com wrote:
Oh, I'm very sorry, I just made a wrong click.
** Changed in: xorg-server (Ubuntu)
Status: Triaged =
status triaged
On Thu, Aug 13, 2009 at 11:39 AM, TualatriXtualat...@gmail.com wrote:
Oh, I'm very sorry, I just made a wrong click.
** Changed in: xorg-server (Ubuntu)
Status: Triaged = Incomplete
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You
I'm going to be away, but I want to make sure the information is here on LP on
this bug:
From the author of gnome-power-manager, Richard Hughes:
There's no bug in gnome-power-manager, and I suspect gnome-session
somehow triggers this bug. There's a full writeup in
Thanks for debugging this. I'm also adding xorg to this bugreport since
it appears something in X is intercepting the keyevent and blanking the
screen. Could you do the following:
Paste in output of: lspci -nn | grep VGA
Attach /var/log/Xorg.0.log
To triagers/developers:
1) xev is showing
Thanks for the information. I'm marking as confirmed since the needed
logs are here.
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)
** Summary changed:
- Pressing Suspend key turns off display instead of suspending
+ [GM965/GL960] Pressing Suspend key turns off display
I killed GPM and the bug did not show up (I tested for an hour).
Usually it shows up after ~10 minutes and sometimes multiple times an
hour.
On Fri, Aug 7, 2009 at 8:03 AM, Oded Arbelo...@geek.co.il wrote:
I have the same issue with a Thinkpad T61 with intel 945 card.
--
Screen randomly goes
Thanks for the report. Could you kill GPM right after loading into
gnome and see if the screen blanking happens later on in the session?
command in terminal:
killall gnome-power-manager
I'm experiencing the same bug and wanted to see if it is related to:
** Package changed: ubuntu = xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New = Incomplete
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
Xorg does not load in karmic using Zotac ion board A series
https://bugs.launchpad.net/bugs/404577
You
Thanks for your help finding the logs! Assigning to xorg-server, confirmed
since logs are in comment #2. Just so you know, this section of Launchpad is
primarily used to help diagnose and correct programming errors in the
development release of Ubuntu, and is nearly entirely maintained by
Thanks for your debugging work. I'm assigning this to the nvidia driver
package and confirming. Hopefully they will start including the 185
drivers soon in Karmic so this work around won't be needed.
** Also affects: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided
Status: New
Thanks - I'm marking as confirmed.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided = Low
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: Incomplete = Confirmed
--
[nvidia C51] Second monitor (DVI) doesn't wake up after power save mode
Great - could you also attach the file: ~/.xsession-errors after the
second monitor fails to wake up?
That would be helpful as well.
Thanks
** Summary changed:
- Second monitor (DVI) doesn't wake up after power save mode
+ [C51] Second monitor (DVI) doesn't wake up after power save mode
**
Thank you for the detective work. Please attach your X server log file
(/var/log/Xorg.0.log) to the bug report as individual uncompressed file
attachments using the Attachment: box below after recreating the bug
you described here. Also, can you post the output of lspci -vvnn?
Thanks in advance.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided = Medium
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed = Triaged
--
Some games using 3D-acceleration don't work on Jaunty with ATI chipsets
https://bugs.launchpad.net/bugs/374590
You received this
*** This bug is a duplicate of bug 271138 ***
https://bugs.launchpad.net/bugs/271138
** This bug has been marked a duplicate of bug 271138
mouse and keyboard unresponsive when gdm first runs
--
recent upgrade to 8.10, cannot log in, mouse and keyboard don't respond
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Incomplete
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
[i965, Jaunty] Hung screensaver after resume from suspend (LiveCD only)
https://bugs.launchpad.net/bugs/311362
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thanks for following up. Since this bug is hardware based (from an old
monitor with non standard DDC) with a known workaround for older
hardware [1], I'm marking this bug closed. Thanks for your report, and
please report any additional bugs that you find!
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = Medium
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = Medium
--
[HD 4870] Power-off and power-on of monitors in multiheaded fglrx xorg
configuration causes X to become unresponsive/freeze in Jaunty
Hi again, thanks for your additional information.
xkeyboard-config is the package for the part of the x.org server that
handles keyboard configuration in general, including multiple
localization layout.
Please see Bug #295990 and check if that is a duplicate of your bug. If
it is, please add any
** Tags added: bitesize
--
Some games using 3D-acceleration don't work on Jaunty with ATI chipsets
https://bugs.launchpad.net/bugs/374590
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
Thank you for providing the requested logs. I am also listing xserver-
xorg-video-intel (Ubuntu) as affected, since bugs like these are
commonly an xorg issue.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-power-manager
** Changed in: fglrx
Importance: Undecided = Unknown
** Changed in: fglrx
Status: Confirmed = Unknown
** Changed in: fglrx
Remote watch: None = ATi Linux Platform Bugs #1568
--
[ATI driver specific] Ubuntu Jaunty hangs after usplash with fglrx 8.600 or
8.6002
If you are interested in patching (or fixing this bug), check out this link:
https://wiki.ubuntu.com/Bugs/HowToFix
Also, join #ubuntu-bugs or #ubuntu-motu on IRC (freenode), and ask any
questions you have.
Ubuntu's IRC channels (and instructions on how to use IRC) are found at
Thanks for finding that, I'm going to make this new and update the
title/description. Someone more familiar with SIS can pick this up if it
continues or more users sees this problem.
** Changed in: xserver-xorg-video-sis (Ubuntu)
Status: Incomplete = New
** Summary changed:
- Video
Hello again,
Doing some research [1, 2], I found that Amilo laptops do not actually
pass events through X and ACPI. Unfortunately, upstream has already
determined that this won't be fixed. I'm linking the upstream bug in
case something else comes up again. Thank you for the report and please
Thanks for the update.
For troubleshooting hotkeys, see:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting
As a first step, do the following steps:
1) From a terminal, enter:
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode
\2 = \3, state = \1/p'
2) press the
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
WARNING: __call_bad_lock_func
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
** Package changed: gnome-control-center (Ubuntu) = xkeyboard-config
(Ubuntu)
--
Keyboard layout switching does not work
https://bugs.launchpad.net/bugs/372611
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in ubuntu.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please attach your X server configuration file
(/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the
bug report as individual uncompressed file attachments using the
Attachment: box below.
87 matches
Mail list logo
