*** This bug is a duplicate of bug 1767648 ***
https://bugs.launchpad.net/bugs/1767648
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1767648 ***
https://bugs.launchpad.net/bugs/1767648
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-
Public bug reported:
When I run sauerbraten in fullscreen mode in Ubuntu 18.10, there are
"skips" in the animation of the rotating cubes. Upon further
"evaluation", I noticed the system mouse pointer "popping up" briefly at
the moment of the glitch(near the crosshair) about once a second. When
n
Try triple-clicking instead of double-clicking. Don't ask how I found
this work around but may help others trying to live through this
irritating bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/
*** This bug is a duplicate of bug 1767648 ***
https://bugs.launchpad.net/bugs/1767648
Have the same problem.
--
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/1769299
Title:
universal access
NVIDIA drivers installed through the "Additional Drivers" section in the
Software & Updates program work fine. I can use my monitor now, although
booting takes significantly longer now than before.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I ran perf during the bug to see if I could find out where the high CPU
usage is coming from since it isn't leaving a .crash file. I sampled for
10 seconds starting immediately after plugging in the 4k monitor.
By PID the report looks like:
Samples: 47K of event 'cycles:ppp', Event count (approx.)
Hi,
I went through steps 1 through 3, but even after applying the workaround
from 994921 (commenting out the line of code), rebooting, and
replicating the bug no .crash file was generated. I was lucky enough to
have the screen stay uncorrupted during the lag phase of the bug and I
already had the
@Gunnar: Sure, happy to sacrifice my airport key :)
New bug #1800727 for the XPS.
--
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
Public bug reported:
Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in
order to pass KEY_RFKILL to userspace.
Despite the issue described in bug #1740894, on Dell XPS 15 9575 the
airplane mode key actually worked flawlessly out-of-the-box after
installing Cosmic at beginning of
@Mario: Yeah, history seems to repeat itself.
Personally I think it would help if you could file a bug specifically
about the Dell issue, based on the proposed fix of xkb-data. The xkb-
data fix is probably a step in the right direction, even if it triggers
that regression.
What do you think?
--
A few weeks ago I submitted the similar Bug #1791367 for airplane mode
key not working on Asus ZenBook Flip UX561UD. We did some tests updating
xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on
the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1
where it had
** Tags removed: verification-needed-cosmic
** Tags added: verification-failed-cosmic
--
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 usersp
Added comment to the other bug #1740894: Same issue on the Dell as we
had here, the new update to 2.23-1 from -proposed breaks disabling the
airplane mode on the Dell XPS 15 9575.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config i
Marking as bb-notfixing. This means the bug is not considered a release
blocker, but can still be worked on and fixed.
** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Hi Daniel!
Well, here's what i have atm:
1)Yes, i have crash file there, and using your instructions i can't tell you
the ID of newly-created bug yet :-(
In journal:
Oct 30 10:39:33 pc whoopsie[1635]: [10:39:33] Parsing
/var/crash/_usr_bin_Xwayland.1000.crash.
Oct 30 10:39:33 pc whoopsie[1635]: [
16 matches
Mail list logo
