Please attach dmesg when it works and when it doesn't work.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1816947
Title:
[Dell XPS L321X] Touchpad not working after last apt-get upgrade
Bug-1818885- In my case after booting the iso there was no GUI. Only
after installing the intel driver was i able to login into the desktop.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Project changed: ubuntustudio => wacom-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wacom-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1637605
Title:
Wacom driver crash on wake
To manage notifications about this bug
You have been subscribed to a public bug:
Issue: Wacom drivers crash on Wacom pen enabled laptops/tablets.
Crash Occurs: When the PC is woken from sleep mode. The screen will become
inert to the pen.
How to reproduce: Select "suspend" then press power button to wake.
Work around: Log out
There are two nouveau commits which landed in v4.18-rc6 get backport to
Ubuntu's kernel.
Can you test mainline kernel v4.18-rc6 and see if the issue also happens there?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau
What are you using to add/remove apps? Can you please attach a photo?
** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu)
** Summary changed:
- system problem
+ unable to remove or add apps
** Changed in: gnome-software (Ubuntu)
Status: New => Incomplete
--
You received this
Public bug reported:
unable to remove or add apps.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.5
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
[nouveau] After
Judging by linux-image-4.15.0-46-generic.259292.crash, it appears a
kernel crash in the nouveau driver is the problem here.
If you are able and willing to disable the Nvidia GPU in your system
BIOS then you might find that also works around the problem.
A different solution would likely to be to
Are you suggesting anything in Xorg needs fixing, or is the Xorg task
just an FYI because it's related?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
This doesn't sound like a bug to me. If you manually place your only
connected display at a position that's not 0x0 then I would expect that
invisible space.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Opinion
--
You
As already stated above, the correct workaround, for now, is to
configure a drirc (probably in a conf.d directory, so it doesn't clash
with other settings files) so as to disable 10 bit per channel support
for Totem. The same had to be done with Chromium-vaapi, as it also
happens with that
We're getting down to just a few bugs blocking 19.0, so I'm pinging
those bugs to see what the progress is?
--
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/1815889
Title:
qemu-system-x86_64
I installed an older kernel, and was able to boot and log in. But the
external display (HDMI) still didn't work. In desperation I went to
Settings -> Users -> Automatic Login.
And now everything works. Apart from the fact that my computer can be
used by anyone. So it was a mistake on my part to
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244153/+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/1818899
Title:
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244152/+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/1818899
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244154/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244166/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244161/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244165/+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/1818899
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244164/+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/1818899
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244163/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244162/+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/1818899
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244159/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244158/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244160/+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/1818899
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244155/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244156/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244157/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244149/+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/1818899
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244150/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244151/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
I can boot to login, but if I input correct information it freezes. If I
boot in recovery mode and choose to resume boot, I can login. But my
external display doesn't register. If I choose the failsafeX version
there is an error text related to xorg.
I have not had any
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
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 1813897 ***
https://bugs.launchpad.net/bugs/1813897
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1813897, so is being marked as such.
; - Alpha amd64 (20190306)
MachineType: OEM OEM
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed
boot=casper iso-scan/file
Adding a test for xorg for their consideration.
--
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/1818879
Title:
pull cirrus.ko into main kernel package
To manage notifications about this bug go
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1818879
and then change the status of the bug to 'Confirmed'.
If, due to the
Another alternative would be to have vesa specify a working bpp value,
if that is the only problem there.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
When can we expect a release of the proposed xkb-data?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
To manage notifications
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for
me on bionic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$
Public bug reported:
I add a custom mode for my monitor using xrandr at boot. It looks like
this:
xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481
+hsync -vsync
xrandr --addmode HDMI-1 "2560x1440R"
xrandr --output HDMI-1 --mode "2560x1440R"
xrandr --output HDMI-1
for original report (live qa-test system on dc7700); I forgot to upload
this file...
** Attachment added: "journalctl -a >journalctl.txt (i forget if it was sudo)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1818777/+attachment/5243937/+files/journalctl-a.txt
--
You received
Note that all Xorg crashes get turned into SIGABRT as part of its
internal crash handling. Even if the cause of the crash starts out as
SIGSEGV.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 1568546 ***
https://bugs.launchpad.net/bugs/1568546
** Summary changed:
- Launching any electron app crashes Xorg
+ Launching any electron app crashes Xorg in ?? from ProcVidModeGetModeLine
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** This
It appears the kernel recognizes your Intel GPU with the 'i915' driver,
but has failed to create a device for it. So your CPU is too new for
this old Ubuntu release.
Please try the latest releases and tell us if the problem still occurs:
16.04.6: http://releases.ubuntu.com/16.04/
18.04.2:
** Summary changed:
- system freeze after update
+ system freeze after update (compiz at 100% CPU)
** Package changed: xorg (Ubuntu) => compiz (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Package changed: xorg (Ubuntu) => unity (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/1755544
Title:
Launcher and window butttons disappeared
To manage notifications about this
It appears the kernel knows about the camera:
P: /devices/pci:00/:00:13.1/usb3/3-3/3-3:1.0/video4linux/video1
N: video1
S:
v4l/by-id/usb-Sunplus_Technology_Co.__Ltd._Generic_Digital_camera-video-index0
S: v4l/by-path/pci-:00:13.1-usb-0:3:1.0-video-index0
E: COLORD_DEVICE=1
E:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Dal,
Please run these commands:
lspci -k > lspcik.txt
lscpu > lscpu.txt
and then send us the resulting files 'lspcik.txt' and 'lscpu.txt'.
---
Everyone else, please log your own new bugs.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
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/1756663
Title:
blank X after boot (Dell Latitude 3540 - intel VGA)
To manage
Please open a terminal and run this command:
ls -l /dev/video*
What result do you get?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is
This looks suspicious:
Mar 19 13:55:02 username-desktop systemd[1]:
dev-disk-by\x2duuid-78656203\x2d39f2\x2d486d\x2dba2c\x2d8f981cafa2c5.device:
Job
dev-disk-by\x2duuid-78656203\x2d39f2\x2d486d\x2dba2c\x2d8f981cafa2c5.device/start
timed out.
Mar 19 13:55:02 username-desktop systemd[1]:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
The LightdmDisplayLog.txt looks suspicious:
pci id for fd 14: 80ee:beef, driver (null)
EGL_MESA_drm_image required.
Does the problem still occur in the final/latest release of 18.04?
http://releases.ubuntu.com/18.04/
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed
Sorry for the slow response, but does this problem still occur? If so
then please run this command on the problematic machine:
apport-collect 1756511
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: bionic
--
Maybe it shouldn't be included in 19.04 until it's fixed?
--
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/1767312
Title:
[radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
removing gstreamer1.0-vaapi did the trick but I don't think a user
should be expected to do that on every new installation.
--
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/1767312
Title:
Are you still experiencing this problem in 16.04 after updating the
system?
It sounds like the Synaptics Xorg driver knows about your touchpad but
might be ignoring it:
[44.044] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[44.045] (II) config/udev: Adding input device
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Next time the problem happens, please reboot and then run:
journalctl -b-1 > prevboot.txt
and send us the file 'prevboot.txt'.
Please also follow these instructions in case something has crashed:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
**
Can you please provide a photo of the problem you are seeing?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
*** This bug is a duplicate of bug 1700085 ***
https://bugs.launchpad.net/bugs/1700085
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** This bug has been marked a duplicate of bug 1700085
Mouse cursor is tiny on HiDPI screens
--
You received this bug notification because you
You have been subscribed to a public bug:
My Ubtuntu Studio freeze after one or two hours of use, not giving me time to
save my works.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-lowlatency 4.13.13
Uname: Linux
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849
Thanks, that sounds the same as bug #1760849
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 1760849
Login screen appears on only one monitor
Public bug reported:
I have laptop connected to external display. I do not use the laptop
display. I find it strange that login screen is only shown on laptop
display. Ideally the login screen should be mirrored to all displays.
What happens after login can remain as is.
Right now, even though I
72 matches
Mail list logo
