Problem present on Dell Latitude X300 in Lucid RC (20100419.1).
The system boots with xforcevesa.
HOWEVER the problem was NOT present in Lucid Beta1 !!!
--
[i855] Xserver freezing on Toshiba Satellite A10 (Intel 82852/855GM)
https://bugs.launchpad.net/bugs/477256
You received this bug notificati
Will the xserver-xorg-video-intel packages from
https://edge.launchpad.net/~raof/+archive/aubergine make any difference
if the bug was from having KMS disabled (and my current fix is looking
like "options i915 modeset=1" under /etc/modprobe.d) ???
--
[i855] Xserver freezing on Toshiba Satellite A
I did install the new version but it seems that it does not fix the
problems when needing i915.modeset=1
The installation was a little strange but in the end it seems that I
have:
xserver-xorg-video-intel
2:2.12.0+legacy20100802-0~raof1~lucid
but the output from Xorg -version looks like
X.Org X
In the past two years, the WPE renderer has itself also been removed.
This bug is surely not relevant to anybody in 2024. You're hitting some
other bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
No issue on Ubuntu 13.10
--
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/1069901
Title:
Low Graphics Mode Using Mini DisplayPort On Dell XPS L502x
To manage notifications about this bug g
ith status 1
[ 77.307819] init: failsafe-x main process (1742) terminated with status 1
[ 85.354772] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 87.303490] init: plymouth-stop pre-start process (3097) terminated with
status 1
Date: Thu May 3 00:20:06 2012
DistUpgraded: Fre
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/993611
Title:
/usr/bin/X segfaults during boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/99
Will give this patch a try on Xubuntu 12.04 when I have a chance.
Currently, am using Mint 9 Xfce on my Lenovo S10 netbook, as the version
of xrandr does not have this problem on that distro. Would love to
upgrade though...
--
You received this bug notification because you are a member of Ubuntu-
Will give this patch a try on Xubuntu 12.04 when I have a chance.
Currently, am using Mint 9 Xfce on my Lenovo S10 netbook, as the version
of xrandr does not have this problem on that distro. Would love to
upgrade though...
--
You received this bug notification because you are a member of Ubuntu-
Before booting, disconnecting the wireless USB mouse and keyboard (comes with
Packard Bell OneTwo), X boots up without problems.
When I connect the Chicony USB Wireless HID receiver X crashes immediately.
This is consistently reproducible.
Check the Xorg.log for:
(II) XINPUT: Adding extended in
I installed the 290.10 using the x86_64 package downloaded off the NVIDIA
website. I had no crash ever since.
I stressed my system by playing multiple YouTube and Vimeo Flash HD clips
in parallel (that used to crash everytime), no problem!
If you don't need the latest changes in the drivers, this i
n (display_name=0xbfeedf1a ":0") at
/build/buildd/gtk+2.0-2.24.10/gdk/x11/gdkdisplay-x11.c:173
?? ()
?? ()
?? ()
?? ()
Title: amdcccle crashed with SIGSEGV in gdk_display_open()
UnitySupportTest:
Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1015930
Title:
amdcccle crashed with SIGSEGV in IA__gdk_display_open()
To manage notifications about this bug go to:
https://bugs.launch
I see very similar crashes since upgrading from 15.10 to 16.04. I'm on a
Lenovo ideapad 300 with Skylake graphics
Xorg.log backtrace:
[ 167.216] (EE) Backtrace:
[ 167.237] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55cd120e95ce]
[ 167.237] (EE) 1: /usr/lib/xorg/Xorg (0x55cd11f37000
Public bug reported:
I use an external monitor connected to my Dell XPS L502x laptop via the
Mini DisplayPort. 99% of the time this results in:-
The System is running in low-graphics mode
This Error is appearing at boot-up before login screen I then get a set
of options to select such as reconfi
The exact same things happens for me. Let's hope they fix it soon, this
is really frustrating :(
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1741447
Title:
Unity / Compiz in a crash loop afte
I think something is hosed with the radeon driver in mesa 17.2.8, but I
can't find the 17.2.4 pkgs to roll back and test the theory. The 17.2.4
was pulled from updates and proposed lines. I'm hesitant to rollback to
11.2.
I can get you anything you need (logs, etc...) look at the issue. I'm a
l
The warning string in the Xorg.0.log, "flip queue failed", is found in the
following driver:
/usr/lib/xorg/modules/drivers/radeon_drv.so
found in package: xserver-xorg-video-radeon-hwe-16.04
This module is loaded in Xorg on my machine. I'll download the source
and start looking through the code.
Source of warning message from radeon_drv.so:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip
queue failed: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue
failed in %s: %s\n",
./src/radeon_kms.c: xf86DrvMsg(scrn->scrnIndex, X_WAR
Specifically, the source file:
./src/drmmode_display.c:xf86DrvMsg(scrn->scrnIndex, X_WARNING,
"flip queue failed: %s\n",
Line 3093 in the source code of `drmmode_display.c`:
flip_error:
xf86DrvMsg(scrn->scrnIndex, X_WARNING, "flip queue failed: %s\n",
I'll "gdb attach" the Xorg process next and see if I can't get some
runtime data.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati-hwe-16.04 in Ubuntu.
https://bugs.launchpad.net/bugs/1750393
Title:
Blank screen with only
Okay, a little code inspection leads to one of these two function calls
failing at line 3062:
if (crtc == ref_crtc) {
if (drmmode_page_flip_target_absolute(pRADEONEnt,
drmmode_crtc,
Line 3039 in the source can also cause the message:
if (flip_sync == FLIP_ASYNC) {
if (!drmmode_wait_vblank(crtc,
DRM_VBLANK_RELATIVE |
This issue has a workaround:
Download 7.9 radeon driver Ubuntu package (xserver-xorg-video-radeon-
hwe-16.04_7.9.0-0ubuntu1~16.04.1_amd64.deb) from:
https://launchpad.net/ubuntu/xenial/amd64/xserver-xorg-video-radeon-
hwe-16.04/1:7.9.0-0ubuntu1~16.04.1
Execute the following on the downloaded .de
** Summary changed:
- Blank screen with only mouse pointer after mesa driver update; display does
not switch to tty7 upon lightdm start; Xorg.0.log quickly grows
+ Blank screen with only mouse pointer after 7.10 radeon driver update; display
does not switch to tty7 upon lightdm start; Xorg.0.log
Public bug reported:
I dont know anything else
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
BootLog:
fsck from util-linux 2.19.1
/de
--
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/841382
Title:
[i915gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
render.IPEHR: 0x0100
To manage notification
Public bug reported:
System booted OK with Nouveau driver. I used Driver Manager to apply
change of "Using NVIDIA driver metapackage from nvidia-
driver-390(proprietary,tested)". After the NVIDIA proprietary driver
installation, system failed to boot. All i get was a blank screen,
with a bli
2 of 5
** Attachment added: "boot-2.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331177/+files/boot-2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
1st attachment of 5(1 of 5)
** Attachment added: "boot-1.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331176/+files/boot-1.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-gr
3 of 5
** Attachment added: "boot-3.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331178/+files/boot-3.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
4 of 5
** Attachment added: "boot-4.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331179/+files/boot-4.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
5 of 5
** Attachment added: "boot-5.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331180/+files/boot-5.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in
** Attachment added: "boot-2.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331430/+files/boot-2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Thanks Daniel... i did what you requested. Following is a recap of the
process, FYI:
1. System running Nouveau driver. All OK.
2. Open terminal, input "sudo apt install nvidia-driver-390".
3. After installation complete, input "systemctl reboot" to reboot.
4. Screen went blank on reboot, curs
** Attachment added: "boot-4.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331432/+files/boot-4.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
** Attachment added: "boot-3.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331431/+files/boot-3.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
** Attachment added: "boot-5.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331433/+files/boot-5.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
thanks in advance
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1864781
Title:
System with GeForce GT 520 failed to boot when nvidia-390 was
installed
To manage notifi
1. Added to /etc/X11/Xwrapper.config : needs_root_rights = yes (as instructed
in bug 1716857.
2. Open terminal, input "sudo apt install nvidia-driver-390".
3. After installation complete, input "systemctl reboot" to reboot.
4. Screen went blank on reboot, cursor blinking at around the top left co
to add, after step 4:
4a. i waited a little longer and noticed a jagged dialogue window
popped up (attached). i tried to input my password, but neither mouse
nor keyboard was functional. i waited again, and later proceeded to
resume at step 5.
** Attachment added: "dialogue box.jpeg"
http
Daniel.. anything else i should try to equip you with more info to debug
this?
Thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1864781
Title:
System with GeForce G
I can confirm this. This morning after upgrading I found myself with a
US keyboard layout without realizing why, and with no way to get back to
my own, not from dpkg/reconfigure keyboard/configuration nor from
localectl. (those are supposed to be hyphens, yeah)
The funny thing is that in gnome/ter
Ubuntu 18, Intel(R) UHD Graphics 620
$ sudo intel_gpu_top
(intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:832) intel-mmio-CRIT
Public bug reported:
Elan Synaptics touchpad is not detected on my Lenovo s21e-20 notebook computer
with a fresh install of Ubuntu 15.04.
Followed the guide on this page
(https://wiki.ubuntu.com/DebuggingTouchpadDetection) to debug.
Thanks for the help in advance.
** Affects: xserver-xorg-input
Public bug reported:
resolved (maybe) :
sudo apt-get purge fglrx*
install fglrx 15.200 via "additional drivers" in software update
everything seems to work including OpenCL.
but fglrxinfo reports :
ad@Antec-Ubuntu:~$ fglrxinfo
display: :0 screen: 0
OpenGL vendor string: Advanced Micro Devices, In
** Package changed: ubuntu => nvidia-graphics-drivers-304-updates
(Ubuntu)
** Package changed: nvidia-graphics-drivers-304-updates (Ubuntu) =>
nvidia-graphics-drivers-340 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-d
This bug might be a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848
--
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/1449560
I have tried Aaron's patches myself and they do make the "Failed to
claim DRM device." error messages in /var/log/Xorg.0.log disappear and
the log looks like the NVIDIA driver is working fine, but I still boot
to a black screen.
So there is either another problem, or those patches don't quite fix
Public bug reported:
Laptop model: Clevo P650RS-G
Touchpad make: Synaptics
lsb_release: 20.04.1 LTS
libinput version: 0.29.0-1
The touchpad refuses to work even in Ubuntu Live boot, but it is operational in
Windows 10.
In previous releases, I've been able to add "i8042.reset" to the grub
confi
t. This
might be caused by the object having been destroyed from C code using something
such as destroy(), dispose(), or remove() vfuncs.
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: == Stack trace for
context 0x55656e024200 ==
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[261
Guys, the problem still happens on various linux distros in 2016. Is
there anybody looking into this? It's so annoying for anybody using more
than one keyboard layout.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https:/
*** This bug is a duplicate of bug 1826125 ***
https://bugs.launchpad.net/bugs/1826125
I agree with mactyr that this should not be a duplicate of that bug. The
flaw that I see is not what is shown in those videos. There is no
glitching, it is the whole screen flashing brighter, and is why I us
On the basis of 3 of us deeming that the symptoms of the other bug are
different to the ones described in this bug, I have removed the
duplicate link. I hope that's OK.
If it helps narrow it down, it seems that we all have the non-touch
1080p version, and all notice it much more when Night Light i
Public bug reported:
I found this in my logfile:
possible it can help to make xorg/driver better
[ 509.209] [mi] EQ overflowing. The server is probably stuck in an infinite
loop.
[ 509.224]
Backtrace:
[ 510.673] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80a66f7]
[ 510.673] 1: /usr/bin/X (
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/08
Title:
EQ overflowing. The server is probably stuck in an infinite loop.
To manage notifications about this bug go to:
https://bugs.launchpa
Public bug reported:
I have a new installation of Ubuntu 11.10 on a Dell Inspiron 17r Laptop, and the
FN+F3 key combination does not work.
Expected: pressing Fn+f3 should disable the touchpad
Outcome: Although a transparent pop-up shows up on the top right hand corner
notifying user that the touc
Public bug reported:
Hello,
I have 2 screens and there is a 2 pixels shift to the right on the
display on my second screen (see attached picture).
This bug is clearly the same that the one reported here :
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1253885
I opened a clone, as suggested
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982170/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982176/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982178/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Title:
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982177/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/128069
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982172/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/12
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982174/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Tit
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982173/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/12
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982171/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Tit
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982175/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982179/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982180/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982190/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982191/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982189/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
T
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982185/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Tit
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982183/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982184/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982188/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982186/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982187/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280690
Tit
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982181/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1280
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1280690/+attachment/3982182/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
I had the same problem on my Thinpad T60 using Xubuntu 13.10, here is
how I solved it:
sudo cp /sys/devices/platform/thinkpad_acpi/hotkey_all_mask
/sys/devices/platform/thinkpad_acpi/hotkey_mask
This change only remains during your active session, so test it out
first and if it works add the abov
Sorry add the above line to /etc/rc.local to make it permanent*
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1242259
Title:
Thinkpad x1 Volume up down and mute keys stopped working after upgra
Have had no problems so far using the new Ubuntu 13.04, what version
ninsky are you using?
--
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/1069901
Title:
Low Graphics Mode Using Mini Displ
Upstream: https://bugs.freedesktop.org/show_bug.cgi?id=66534
** Bug watch added: freedesktop.org Bugzilla #66534
https://bugs.freedesktop.org/show_bug.cgi?id=66534
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics i
Public bug reported:
I have ubuntu 12.04.2 installed from a cd image. Now I would like to
upgrade to the 12.04.3 HWE stack and this package seems to cause a
problem:
silviu@pangolin:~$ sudo apt-get install linux-generic-lts-raring
xserver-xorg-lts-raring
[sudo] password for silviu:
Reading pack
Public bug reported:
For some days, I cannot use any more the scroll function from my touch pad (on
the right side of the touch pad is a line painted where it was possible to
sroll up and down).
It cannot be so long, but I seen it for ~2-3 days before it was ok.
ProblemType: Bug
DistroRelea
ok, now I found the problem. Default setting got replaced: now I had to
scroll with two fingers... but the option is also there to scoll on the
sides :)
Thanks
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
Thanks for the test case, that's much appreciated. Just a few comments:
- We might as well extend the existing trap-crasher test instead of
adding a new one that is a near duplicate.
- The test should ideally be added in its own commit before the fix so
that it's easy to verify that the fix actua
Thanks for the patch. Do you mind sending it to
pix...@lists.freedesktop.org for review?
--
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/1197921
Title:
LibreOffice spreadsheet causes full
Also, if you have a test that demonstrates the issue, it would be
valuable to add to the test suite in the pixman/test directory.
--
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/1197921
Titl
Public bug reported:
This is an authomatc redirect from x Diagnose
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.9.2-0ubuntu8.3
Ar
Same problem here, freezes were infrequent on 12.04, only occasional.
Since some updates were installed on 14-01-2013, freezes happen at least
once a day to my work PC, both when idle and loaded.
Symptoms that vary:
- Black screen (latest) OR oops dump screen OR corrupt memory graphics on
entir
@slucas1979 : I will try Kernel 3.8. Thanks for the tip.
fglrx radeon driver is more stable more often but has it's own issues and
crashes. Overall is no better. Back to open source driver.
trying 3.8 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ as there is
ment
Woohoo! For 12.04.1 LTS users with constant crash problems as described here
and on-board ATI/AMD/Radeon graphics cards, this looks promising:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
If you want the 3.5 kernel and xorg packages from 12.04.2 made available in LTS
for 'hardware enable
I notice that this is filed under package “xserver-xorg-video-intel” yet
people report issues on various graphics cards. Mine is AMD chipset with
VGA controller Radeon "AMD nee ATI RS880 [Radeon HD 4200].
Will this reduce visibility to those concerned with the radeon driver?
--
You received thi
Re. #713 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/993187/comments/713
I have ran for 24 hours on 12.04.1 with LTS Enablement stack from
Quantal installed (with kernel 3.5.0-23-generic and X.Org X Server
1.13.0 / 2:1.13.0-0ubuntu6.1~precise2).
Although the OS and gr
A 3.8 kernel did not appear to be compatible with 12.04.1... Although it booted
to the login screen there was:
(1) No grub menu, (2) No boot screen just purple, (3) When plugging in a USB
keyboard (none connected initially), nothing happens, (4) No network. I had to
boot into rescue media and
This diatribe of information was useful getting my 8" Xenarc 800TSV screen
working with the evdev driver on Ubuntu 10.04 LTS but the volume of info was
such that it was hard to figure out what was the right thing to do vs the wrong
thing to do.
So I wanted to summarize what I did so others cou
Confirming same problem ("desktop" machine, Asus MB minimal system,
nvidia card). Resume from suspend powers up (fans, disk, backlight) but
just get black screen, kernel appears wedged, hard reset required. This
is 14.04, both new install and upgrade from 13.04 same problem. Nvidia
proprietary driv
@chaas
Re Mint, that might make sense - I was running Mint Debian w/ MATE, which is
based on Debian testing, which I found also has the problem. Are you running
Mint 16? I don't know it lineage (I don't know much about Mint), but assume
it's not based on Debian testing.
--
You received this bu
1 - 100 of 300 matches
Mail list logo
