Is there actually something to do here for xorg?
--
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/2009145
Title:
Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored
To manage notifications
** Tags added: jammy
--
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/2032910
Title:
60x11-common_xdg_path sets wrong XDG_DATA_DIRS on Plasma
To manage notifications about this bug go to:
** Tags removed: ubuntu
--
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/1922414
Title:
Xorg scripts fail with "has_option: command not found"
To manage notifications about this bug go to:
You need to provide /var/lib/dkms/nvidia/390.141/build/make.log
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
"Fix:
sudo apt install -y --reinstall gcc g++ gcc-7 g++-7"
How on Earth is that a fix? Does an updated package do this for you? I'm
doubting it very much.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
All good here too with 390.116-0ubuntu0.18.04.3
--
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/1851162
Title:
nvidia-drivers-390 fail to build with kernel 5.3
To manage
Updated Bionic with all the latest packages before adding -proposed.
Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES=''
KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/5.3.0-26-generic/build
Did you build a custom kernel?
--
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/1846995
Title:
package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade:
Probably the same as Bug #1851162
--
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/1843385
Title:
package nvidia-dkms-390 (not installed) failed to install/upgrade:
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
--
You received this bug notification because you are a member of Ubuntu-X,
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
--
You received this bug notification because you are a member of Ubuntu-X,
Or don't.
https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The HWE package now force-upgrades to 5.3.0, rendering that entire
package useless.
--
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/1851162
Title:
nvidia-drivers-390 fail
Build log attached.
** Attachment added: "DKMS build log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5302550/+files/make.log
** Description changed:
- With linux-image-5.0.0-23 I had no problems. Following an update 5.3.0
- was installed,
Public bug reported:
With linux-image-5.0.0-23 I had no problems. Following an update linux-
image-5.3.0-19 was installed, the DKMS build failed, and the system
became unusable.
Removing 5.3.0 brings the system back.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390
I've marked this as affecting me but I've just realised that I'm using a
different kernel. In my case 5.0.x works fine, 5.3.0 fails in
(apparently) the same way:
DKMS make.log for nvidia-390.116 for kernel 5.3.0-19-generic (x86_64)
Sun 3 Nov 19:50:42 GMT 2019
make[1]: Entering directory
*** This bug is a duplicate of bug 961202 ***
https://bugs.launchpad.net/bugs/961202
** This bug is no longer a duplicate of bug 1163099
compiz generates ~200 wakeups per second when the screen is locked
** This bug has been marked a duplicate of bug 961202
A locked screen (blank
This isn't a duplicate at all. The other bug is asking for MORE log
files, not for them to be rotated.
** This bug is no longer a duplicate of bug 274870
Xorg should keep more rotated logs
** Description changed:
- Wishlist item!
-
- Sometimes, especially when crashes/reboots are involved,
** Information type changed from Public to Public Security
--
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/1271166
Title:
Gómez Peer under Wine appears on the lock screen
To manage
** Tags removed: mesa ubuntu unhandled wine
** Tags removed: 3-d 3d exception
--
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/371750
Title:
Wine d3d9 test causes unhandled exception
To manage
*** This bug is a security vulnerability ***
Public security bug reported:
When running the Gómez Peer under Wine (including upstream), the
application is still visible on top of the lock screen.
Nothing running should be visible on top of the lock screen and this is
a security concern.
To
DKMS make.log for fglrx-8.960 for kernel 3.8.0-34-generic (x86_64)
Wed Dec 25 21:47:07 GMT 2013
AMD kernel module generator version 2.1
kernel includes at /lib/modules/3.8.0-34-generic/build/include not found or
incomplete
file: /lib/modules/3.8.0-34-generic/build/include/linux/version.h
**
I'm on Precise. I installed fglrx-updates which, for some reason, has
had this broken version backported to Precise's fglrx-updates, but you
would expect that from fglrx-updates I guess.
fglrx itself has problems and I described my workaround to that at
As I have clearly stated it is not an error with Wine: it affects Wine.
--
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/1114520
Title:
Graphical Wine applications fail to load
To
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = New
--
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/1114520
Title:
Graphical Wine applications fail to load
To
..otherwise this is yet another LTS release completely broken less than
one year after its release.
--
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/1114520
Title:
Graphical Wine
*** This bug is a duplicate of bug 1058040 ***
https://bugs.launchpad.net/bugs/1058040
https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer/+bug/1058040/comments/61
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
That's fine, but I'm not the one that keeps marking my bug as a duplicate of
this one.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1113331
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Public bug reported:
Graphical applications that run under Wine, such as the SlingPlayer 1.5 will
fail to load with the fglrx package installed.
http://appdb.winehq.org/objectManager.php?sClass=versioniId=11492
Using fglrx-updates used to allow everything to run correctly, and with
a
Public bug reported:
Ran a dist-upgrade and now my screen resolution is all wrong. AMD's CCC
tells me that driver isn't loaded. No idea how to resolve this.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname:
The workaround is no use to those of us using the LTS Precise.
--
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/1058040
Title:
fglrx-installer not working with AMD Radeon/Mobility
Precise: Remove any and all fglrx*-updates and fglrx*-experimental
packages THEN install fglrx. Trying to do both together gives your
computer a fit.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
No, I'm in Precise and had fglrx-updates installed. Ran a dist-upgrade and now
it doesn't work.
Purged that and installed fglrx and the problem has gone away.
The older version of fglrx-updates added... I don't know but it reported
my graphics card correctly when using glxinfo, fglrx doesn't.
$
Thanks Robert, can this be backported to Precise?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1064772
Title:
Please upgrade libxcb to 1.9
To manage notifications about this bug go to:
Public bug reported:
As explained here: http://bugs.winehq.org/show_bug.cgi?id=31882
There is a bug in libxcb affecting multithreaded GUI applications which has
been fixed upstream by
http://cgit.freedesktop.org/xcb/libxcb/commit/?id=23911a707b8845bff52cd7853fc5d59fb0823cef
As X is started for each user, control can be returned to the actual
machine by killing that particular X session via SSH once the user has
attempted to log out.
ALL input via the keyboard and mouse is completely ignored until X is
killed. Even the CAPS LOCK button doesn't work.
I cannot find
I now cannot shutdown. Presumably because logging out is the first step.
SSH in and sudo halt gives me a garbled screen and the laptop fails to
power off.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I only had one user logged in this time, and it still crashed when I
logged out.
** Summary changed:
- Xorg freeze when logging out user
+ Xorg freeze when logging out
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
--
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/1047610
Title:
Xorg freeze when logging out user
To manage notifications about this bug go to:
Public bug reported:
I use two accounts on my computer.
1000 - My main, useful account.
1001 - For testing without messing up my settings on 1000.
I always log in 1000 first and log in a second time with 1001.
When I first start the computer I can log in and out multiple times
without any
Public bug reported:
While trying to upload some videos to Google+ my hard drive went insane,
Unity crashed, then X and now X won't start!
I can find no logical reason why this happened, nor do I have any idea
how to fix it.
I have ran fsck on all the partitions and tried setting X to the
** Description changed:
- While trying to upload some video to Google+ my hard drive went insane,
+ While trying to upload some videos to Google+ my hard drive went insane,
Unity crashed, then X and now X won't start!
I can find no logical reason why this happened, nor do I have any idea
I got my system working again by:
1. Loading failsafe X
2. Downloading and installing the latest fglrx
3. Rebooted (but then Wine wouldn't start - this is usually a sign that fglrx
is NOT installed)
4. Installed the fglrx-updates packages
5. Rebooted
I'm back to normal for now AFAICT. This
Well I updated fglrx and the problem remains. Still on Natty though.
--
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/864648
Title:
Screen brightness resets to full when switching
Possibly the most ignorant comment I have ever seen added.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
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/878235
Title:
Well I had an updated version of fglrx installed (not from the repos)
which worked fine before this update.
I tried to install from the repos but there were all kinds of errors, it
also would not reinstall. I have finally managed to force uninstall the
latest driver and reinstall the driver from
Apparently not:
Start-Date: 2011-10-19 14:35:26
Upgrade: libkrb5-3:amd64 (1.8.3+dfsg-5ubuntu2.1, 1.8.3+dfsg-5ubuntu2.2),
libk5crypto3:amd64 (1.8.3+dfsg-5ubuntu2.1, 1.8.3+dfsg-5ubuntu2.2),
wine1.3:amd64 (1.3.29-0ubuntu1~ppa1~natty1, 1.3.30-0ubuntu1~ppa1~natty1),
libimobiledevice2:amd64
Public bug reported:
I have JUST ran an update. Now, once the system has booted I am
presented with nothing but a blank screen. I cannot change consoles or
do ANYTHING with the machine unless running X in failsafe mode (which I
am doing now).
There were three xserver updates, so I have no idea
--
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/878235
Title:
System unusable after update
To manage notifications about this bug go to:
I have downgraded xserver-xorg-core and xserver-common but the problem
persists. I have also managed to downgrade libimobiledevice2 and
libdvdread4 but all the kerberos stuff is blocked for downgrade by Bug
878263.
The logs mean nothing to me. Isn't there anything in the Xorg logs?
Whatever is
I have purged xserver-xorg-video-intel as it is useless on my system.
I know the packages *should* be unrelated, but downgrading the suspected
packages didn't work either.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are
*** This bug is a duplicate of bug 877905 ***
https://bugs.launchpad.net/bugs/877905
Are we sure this is a duplicate of bug 877905?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Bug 878235 has been marked a duplicate of this and it is a on a fresh
Natty install.
--
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/877905
Title:
After upgrading Xserver video does not
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/874694/+attachment/2554425/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/874694/+attachment/2554397/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Attachment added: xrandr
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/874694/+attachment/2554437/+files/xrandr.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thanks for that, BJB, that works!
Not sure if the bug lies in the graphics drivers then?
--
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/874694
Title:
Resolution cannot be
apport information
** Tags added: apport-collected
** Description changed:
In Lubuntu 11.10 I cannot set the resolution higher than 640x480. The
screen clearly doesn't like this and doesn't fit the desktop. See
attached photo.
-PCI Devices-
Host bridge : Intel
It doesn't seem to have added a great deal of information.
--
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/874694
Title:
Resolution cannot be set higher than 640x480 and
** Attachment added: Photo of screen
https://bugs.launchpad.net/bugs/874694/+attachment/2545700/+files/2011-10-15%2000.59.24.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Public bug reported:
In Lubuntu 11.10 I cannot set the resolution higher than 640x480. The
screen clearly doesn't like this and doesn't fit the desktop. See
attached photo.
-PCI Devices-
Host bridge : Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM
Controller/Host-Hub
The affected computer is dead. Can't do much with this bug really.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in
Public bug reported:
I've logged this against fglrx, but there is nothing remotely helpful in
any of the logs to tell me what is actually causing the problem.
When attempting to install the Windows version of Skype 5.3 in Wine the
entire system locks up. A system tray icon loads then everything
** Attachment added: Wine 1.3.17 log
https://bugs.launchpad.net/bugs/760636/+attachment/2034192/+files/skype53-wine1.3.17.log
--
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/760636
http://www.skype.com/go/getskype-msi
--
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/760636
Title:
Installing Skype 5.3 in Wine causes system lock-up
The crash does indeed still occur with Lucid.
I have attached an updated backtrace with the latest Wine git. I added
the -dbg package for the graphics drivers too but they don't seem to
have made any difference.
** Attachment added: wine-1.2-rc2-251-ge533ec4 console output
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/50058236/RelatedPackageVersions.txt
--
Wine d3d9 test causes unhandled exception
https://bugs.launchpad.net/bugs/371750
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: XorgConf.txt
http://launchpadlibrarian.net/50058245/XorgConf.txt
--
Wine d3d9 test causes unhandled exception
https://bugs.launchpad.net/bugs/371750
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
apport information
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/50058273/XorgLog.txt
--
Wine d3d9 test causes unhandled exception
https://bugs.launchpad.net/bugs/371750
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
apport information
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/50058329/XorgLogOld.txt
** Changed in: mesa (Ubuntu)
Status: Incomplete = New
** Tags removed: needs-retested-on-lucid-by-june
--
Wine d3d9 test causes unhandled exception
Hard to tell if this is fixed or not.
Tested using the Lucid live CD as I don't feel like risking my system
with a full upgrade yet (will do this in the next month).
The test throws up a load of screen garbage over and over again and
eventually stops. Because the screen is garbage it is
apport-collect apparently doesn't show up until Jaunty, I'm using Intrepid.
Is there another way to collect this data?
apport-cli or apport-gtk seem to be my options.
The unhandled exception no longer occurs, but that could simply mean
that Wine handles the exception, the test still fails in
Scrub that last error, my apologies, that's a different problem.
The original problem remains.
--
Wine d3d9 test causes unhandled exception
https://bugs.launchpad.net/bugs/371750
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
Video driver for the ATI Radeon and FireGL graphics accelerators.
This version of the ATI driver officially supports:
* RADEON X1300, X1600, X1800, X1900
* RADEON 8500, 9000, 9100, 9200, 9500, 9550, 9600, 9700, 9800
http://packages.ubuntu.com/intrepid-updates/xorg-driver-fglrx
According to
Public bug reported:
Binary package hint: xorg-driver-fglrx
$ sudo aticonfig --initial
Uninitialised file found, configuring.
Segmentation fault
fglrx doesn't work at all, this is presumably the way to get it to work,
but I get a segmentation fault.
Not sure what else would help other than
** Attachment added: dmesg
http://launchpadlibrarian.net/27279298/dmesg.log
--
aticonfig --initial segfaults on Radeon 9200 under Intrepid
https://bugs.launchpad.net/bugs/381755
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
76 matches
Mail list logo
