[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I'm using a vanilla ubuntu:GNOME session.
--
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/1822515
Title:
Touchscreen input doesn't rotate with the screen
To manage notifications about
apport information
** Tags added: apport-collected
** Description changed:
When a touch screen is rotated, touch input is not mapped correctly.
I'm testing 19.04 on an Acer-One S1003 where the default orientation is
portrait.
Ubuntu 19.04 support automatic screen rotation out of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1822515/+attachment/5258394/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1822515/+attachment/5258393/+files/ProcCpuinfoMinimal.txt
--
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 1809407 ***
https://bugs.launchpad.net/bugs/1809407
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1809407, so it is being marked as such. Please
Yes, sorry. I am trying to track hundreds of bugs in my head and I don't
always remember (or reread) the context of each one every day.
I have now modified the task list for this bug so it tracks both Nvidia
and AMD drivers.
** No longer affects: mutter
** Also affects:
This looks like a low level problem. So either in the kernel, or in the
Xorg driver.
Since you are using the old Xorg driver 'xserver-xorg-video-intel', I
first recommend removing that package or changing your Xorg config to
NOT use the 'intel' driver. Your system is easily new enough to use the
Thanks for the video...
https://drive.google.com/file/d/1ePqj5TCcUje1zcnjIyglkSqFW7qp2cW8/view
** Summary changed:
- There is a constant screen flickereing.
+ There is regular screen flickering/flashing (when the mouse isn't moving)
** Changed in: xorg-server (Ubuntu)
Status: Expired =>
** Package changed: xorg (Ubuntu) => gnome-shell (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/1826025
Title:
gnome-shell trap int3 no desktop
To manage notifications about this bug
UPDATE:
After blacklisting nuoveau and installing nvidia driver, there was no overheat
shutdown, but the cpu is on full speed all the time. and the tempetature is 87
celsius constantly.
I tried disabling pstate, using tlp, neither worked so far.
Here is a usual frame from top:
top - 21:19:30 up
Public bug reported:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the same trap.
This bug was fixed in the package console-setup - 1.191ubuntu3
---
console-setup (1.191ubuntu3) eoan; urgency=medium
* No change rebuild to include all previous changes
console-setup (1.191ubuntu2) eoan; urgency=medium
* Call setupcon --force only when debian-installer is
But scripts changing between scancode and ascii/unicode (such as for
some terminal emulation, dosbox, etc.) would break. I'm not saying they
are widespread, but I have seen this kind of use, and requiring such
flag will suddenly break them.
--
You received this bug notification because you are a
@samuel-thibault kbd_mode would check current state and only allow safe
mode switches without -f, i.e. between unicode and ascii. Scripts
changing between those modes would not have to be changed.
I fixed postinst to not pass -f to setupcon, it is in eoan-proposed.
--
You received this bug
** Changed in: xorg-server (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1792932
Title:
Desktop fails to boot in
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
I read the description of bug 1809407 and I don't think this is the same
bug. With my problem, I can fix everything by refreshing the screen
(alt+f2 'r') but in the other bug, you have to sleep and wake
** Description changed:
+
+ (console-setup)
+ [Impact]
+
+ * keyboard-configuration's postinst changes keyboard mode breaking X
+ keys.
+
+ [Test Case]
+
+ * Ssh to a system or open a terminal and unset DISPLAY
+
+ $ echo $DISPLAY
+
+ $
+
+ * Check kbd mode, should be raw
How will kbd_mode know whether it's safe or not?
Adding a -f option to kbd_mode will at best break some *other* existing
scripts, while this very script should really definitely *NOT* pass -f
to setupcon. That is the nonsense which needs to be fixed.
--
You received this bug notification
Public bug reported:
As a user, after I open my laptop to resume using it after it suspended
by closing it, the background and some parts of some windows have this
"white noice" instead.
I can get rid of it if I restart gnome (alt+f2 / r / enter) but it's
still very annoying.
I'm using the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (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.
https://bugs.launchpad.net/bugs/520546
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
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/1637032
Title:
Regression: The screen keeps flashing (even in text terminal mode)
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
For me, updating drivers solved the issue. I have got Intel controller:
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620
(rev 02)
This is how to update drivers:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get install
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Tags removed: yakkety
--
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/1541082
Title:
[PowerMac3,1] Blotchy GUI graphics for images
To manage notifications about this bug go to:
** Tags removed: yakkety
--
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/1636473
Title:
random cursor jumps when clicking on dell xps 13
To manage notifications about this bug go to:
I also added kbd because I plan patching kbd_mode to perform only safe
mode switches unless a new -f (force) option is passed.
** Also affects: kbd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
That is when updating the console-setup package, yes. As mentioned on
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that's because its config script passes
--force to setupcon, it really shouldn't, as mentioned there
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Does anyone have a workaround?
--
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/1809737
Title:
Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks)
To manage
This affects me too, after updating the following packages:
libreoffice-style-breeze:amd64 (1:6.0.7-0ubuntu0.18.04.2,
1:6.0.7-0ubuntu0.18.04.5),
libreoffice-math:amd64 (1:6.0.7-0ubuntu0.18.04.2, 1:6.0.7-0ubuntu0.18.04.5),
update-manager-core:amd64 (1:18.04.11.9, 1:18.04.11.10),
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
64 matches
Mail list logo
