Actually, now that I've been able to restore the shortcut for showing
desktop (yeah, I could have minimized all the windows manually one by
one), I realize that MY ENTIRE FUCKING DESKTOP is filled with noise.
I attach a screenshot of the whole desktop (I blurred out the icons)
** Attachment
Public bug reported:
The screenshot speaks for itself.
Stuff like this used to happen occasionally up to 16.04, sually after
resuming from suspend, but normally the areas would get redrawn properly
sooner or later.
But since I upgraded to 20.04 I've seen display garbage like this a lot
more
Public bug reported:
This isn't new, this idiocy has annoyed me ever since I've been using
Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that
it still hasn't been fixed.
I use a laptop and I have an external monitor that I keep connected most
of the time.
So, I have it set
Public bug reported:
Sometimes programs open a "popup" or a "secondary", "child" window, I
don't know what the word is.
For example, in Chrome, if I right-click on an image in a web page and
choose "Save As", this will open a new file browser window that allows
me to browse for a directory to
Public bug reported:
On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to
reveal the Desktop by minimizing all windows (it was not exactly the
same as minimizing all windows but whatever).
That shortcut was changed at almost every major release, which was
already irritating
> Note: Please watch your language. They're serious about that here
I know, I wish they were half as serious about handling bugs.
--
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/1887247
Title:
And by the way, this idiocy of having the system bar PLUS the maximized
window's top bar (which used to be one) eats up a significant amount of
vertical space, and gives ZERO extra functionality. There's a lot of
empty space in both, and they contain the exact same elements that were
already
Public bug reported:
I have just upgraded from ubuntu 16.04 to 18.04 (and I would have
upgraded to 20.04 already if the stupid package manager weren't unable
to resolve some conflicts which are "holding back" packages).
An unbelievavly stupid mistake was made in the new design of windows.
When
Public bug reported:
This is 100% reproducible with any window, I'll use a terminal window as
an example.
Steps to reproduce:
- open a terminal window (again, this could be a Gedit, Nautilus window or any
other window)
- make sure the window is not maximized
- Place the mouse cursor at the
Public bug reported:
Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual
console, not entirely sure what that's called, where you can log in into
a shell and run commands.
I use that when some of the tons of bugs in Ubuntu makes the system hang
so badly that I can't even open a
Public bug reported:
I'm not sure I assigned this issue to the correct package.
The bug is either in bash, or in Ubuntu's application terminal, the one
that provides a terminal window to run bash in, which I think is xterm
but I'm not sure.
Also this could be triggered by either an issue in ssh
This is not incomplete.
Just because the reporter has been asked to provide more information the next
time they observe the bug, doesn't mean the report is incomplete.
There is enough information for somebody to look at it. Another thing is that
nobody wants to or they have better things to do,
Public bug reported:
What I did was:
- install LibreCAD (by adding their ppa and then using apt-get)
- open it
- try to open the attached .dwf file
LibreCAD hanged and the whole system stopped responding. The mouse
button stopped moving, the system wouldn't respond to keyboard strokes,
AND not
> Please follow the steps in comment #2 if you would like any help.
> If you don't have time then no problem, just let the bug expire.
The very idea of bugs expiring because the OP doesn't provide any given
piece of information is stupid. I'm always puzzled at how it's such a
common practice in
Just because using Nvidia is "optional" and I don't have time to waste
trying uninstalling it, doesn't mean this bug should expire.
By the way, when you say "using Nvidia on this laptop is optional" do
you mean actually using the Nvidia GPU is (no shit!) or that I can
uninstall the nvidia drivers
Public bug reported:
I booted Ubuntu, and when I started using it, nothing would respond to the
keyboard. Everything was responding normally to the mouse.
It looked like the keystrokes were being "buffered" extremely slowly, I'll
explain:
For example, I opened Chrome and I started typing
Public bug reported:
I have booted the computer about half an hour ago. Since the very
beginning, I noticed the fan spinning at high spin so I launched "top",
and noticed that Xorg was consuming about 50% CPU and another process
called "at-spi2-registr" is consuming another 20%.
Since then, They
Interestingly, killing the "at-spi2-registr" process has made Xorg's CPU
consumption go down to normal.
--
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/1772109
Title:
Xorg consuming 50% CPU for
Public bug reported:
I navigated to a website in Chrome (linledIn.com) and both Chrome and
Xorg started consuming around 100% CPU each (one was actually
significantly above 100% but I can't remember which one).
Then I closed Chrome entirely (and I check there was no Chrome process
left), but
*** This bug is a duplicate of bug 1731294 ***
https://bugs.launchpad.net/bugs/1731294
Oh, I'm afraid this is just a duplicate of the annoying #1731294
** This bug has been marked a duplicate of bug 1731294
Keyboard shortcuts stop working; restarting unity-settings-daemon fixes them
--
Public bug reported:
I often connect an external monitor to my laptop and, when I do, I use it as
the only screen, with the built-in display turned off.
This is the configuration I manually set a long time ago, and there was a time
when, by plugging in the screen, or bootin with the screen
Public bug reported:
I usually connect an external monitor to my laptop. I had it set up
(System Settings->Displays) so that the laptop's built-in monitor is
turned off, and the external monitor is the only active one (of course,
when I unplug the external monitor, the builtin one turns on
Public bug reported:
Steps to reproduce:
- I connected an external monitor to my laptop through the HDMI port
- my display settings are set to use only the external monitor when it is
connected, so the laptop's builtin screen was turned off
- I hibernated
- I brought my laptop home, connected
Public bug reported:
I think the exact same thing happened with the previous upgrade.
I have a laptop and I often connect an external monitor. I had it set up
so that when I connect it, the laptop's builtin display turns off and
the external one works as the only display.
I upgraded from 15.10
> In the Ubuntu Quality mailing list a couple of people suggested this is a
> duplicate
> of https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046
I have disabled intel-powerclamp and intel-rapl entirely and I am not
affected by that issue anymore (no spamming of the kernel log) (btw,
In the Ubuntu Quality mailing list a couple of people suggested this is
a duplicate of
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046
- Can anybody explain how that is supposed to be related?
- that one is marked as fix released for wily, and my system is up to date, so
either
Yes I am still experiencing it.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Public bug reported:
At first I thought this was a regression in Google Chrome (and I
reported it here:
https://bugs.chromium.org/p/chromium/issues/detail?id=617452) but now I
realize it affects Firefox as well.
Since recently, it has become practically impossible to watch videos on
the Web.
(I meant, medium - however, even high would be ridiculous)
--
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/1565541
Title:
Focused window is not always brought to front
To manage notifications
But the likelihood of doing something harmful, such as deleting a file
or an item of any kind, or performing any kind of irreversible action
(or even reversible action but unknowingly) is far from negligible and
is enough to mark the importance as CRITICAL.
I can't believe you set it to high.
--
Public bug reported:
The following steps will systematically reproduce the issue. Terminal is
only an example, you can do the same with any other application that can
open multiple windows.
- open three terminal windows
- hit Ctrl+Super+D to show the Desktop. All windows disappear as expected
-
The usual bullshit again, I'm sick of it.
Did you miss the part where i said this used to work on 15.04? Just in case i
was not clear about it, that was on the same computer with the same bios.
So, it's not a bug in the bios, or in the extremely unlikely event that it is,
it can and hence must
I'm not wasting my time doing all that stuff.
I reported this bug using the ubuntu-bug tool. If a crash report is
needed or useful and it was not included, the tool is broken, and you
need to fix it so that the next time i use ubuntu-bug or apport,
everything you need to investigate the bug is
Public bug reported:
Look at this:
https://code.google.com/p/chromium/issues/detail?id=529097
I'm almost sure that it's a bug in Ubuntu, not in Chrome, and that I
observe it in Chrome just because it's the only application I ever use
that goes fullscreen.
Note that it's not systematically
It may not ve very powerful but it's definitely more powerful than that.
Look at this:
http://www.notebookcheck.net/Intel-HD-Graphics-4000-Benchmarked.73567.0.html
On Windows, they get around 30-40 fps with several videogames which
render much complex scenes than the ones that yield me 18 or
but the distro driver still is hardware accelerated
That's what I doubt. How can I test and make sure it's not somehow
falling back to emulating openGL in CPU?
Doesn't the fact that the triangle test consumes 100% of a cpu core
demonstrate that it's using the CPU to perform such a simple task
Public bug reported:
SUMMARY
- laptop with NVidia card and Optimus technology
- xorg configured ages ago to automatically switch between built-in and
external monitor when plugging/unplugging
- clean Ubuntu 15.04 after upgrading from 14.10 from 14.04
- no nvidia-* nor bumblebee-* was installed
Public bug reported:
I don't know whether I am reporting this against the right package.
I have an acer laptop with these GPUs:
- GPU0: Intel HD Graphics 4000 (M)
- GPU1: NVIDIA GeForce GT 710M
with Optimus technology. I know getting the NVidia card to work is as
complicated as hell, so I gave
When this happens, any of these may happen:
A) I force-power-off the computer, try to boot again in the exact same
conditions (not plugging/unplugging AC power nor mouse nor external
screen), and at the next attempt most of the times it boots normally
B) I do the same as A, but retry for
/var/log/Xorg.0.log.old is empty
/var/log/gpu-manager.log doesn't exist
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: Incomplete = Confirmed
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
I can't tell for sure, but the files you asked me to attach don't seem
to contain the same error messages that I saw in the black screen during
the boot.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Yeah, right, that was certainly caused by a bug in the BIOS.
--
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/1470248
Title:
whole system froze
To manage notifications about this bug go to:
Public bug reported:
I had several programs open and I simply opened a new tab in Google
Chrome.
First the mouse and keyboard stopped responding
Then the Chrome window became grey
Then I couldn't do anything: the system wouldn't respond to either mouse or
keyboard, and even Ctrl+Alt+F1 wouldn't
@36 I observed another crash so i thought apport-collect would include
relevant information about the crash (which I'm not sure was included in
the original report because I don't remember for sure if I reported it
just after the crash or not)
I know you don't give a shit about fixing the bug in
apport information
** Tags added: apport-collected
** Description changed:
- I suspended
- I pressed a key to resume
- the screen turned on and I was prompted for the password as usual
- I entered the password
= my previous session was lost, every application I had left open prior
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407452/+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/1453742
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407470/+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/1453742
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407454/+files/Dependencies.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: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407453/+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: DpkgLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407456/+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/1453742
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407458/+files/LightdmDisplayLog.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: DkmsStatus.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407455/+files/DkmsStatus.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/1453742
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407457/+files/GconfCompiz.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: Lspci.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407462/+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/1453742
Title:
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407461/+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/1453742
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407460/+files/LightdmGreeterLogOld.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: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407459/+files/LightdmGreeterLog.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: ProcModules.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407468/+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: UdevDb.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407469/+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/1453742
Title:
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407474/+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/1453742
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407475/+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/1453742
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407473/+files/XorgLogOld.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/1453742
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407465/+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: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407464/+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: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407467/+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: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407466/+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: Lsusb.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407463/+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/1453742
Title:
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407476/+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/1453742/+attachment/4407471/+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: XorgLog.txt
https://bugs.launchpad.net/bugs/1453742/+attachment/4407472/+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/1453742
Yeah, and that's precisely what's ridiculous: discouraging dual boot.
It's like not recommendiung the use of laptops, or that of an external
keyboard, or some given screen resolutions.
Ubuntu should struggle to better support all normal use scenarios,
rather than picking those where it doesn't
versus take the hour out of your time to do
as previously requested (which in itself is quite simple)
It's not just the time, it's the risk of breaking everything.
When I first installed Ubuntu, in dual boot with Windows by following Ubuntu's
official documentation and the onscreen
Please don't be ridiculous.
This has started happening recently (by the way, I have rebooted several times
and it keeps happening, not systematically at every suspend/resume but very
often).
This didn't happen before, and the bios I'm using is the same, so it is clearly
a REGRESSION in some
Regarding using UEFI, it's strongly advised not using it unless you
absolutely must, as noted in
https://help.ubuntu.com/community/UEFI
I'm not sure what exactly I did with BIOS settings but perhaps it was
disabling UEFI.
Regarding dual-booting, also strongly advised not to do it.
Public bug reported:
- I suspended
- I pressed a key to resume
- the screen turned on and I was prompted for the password as usual
- I entered the password
= my previous session was lost, every application I had left open prior
to suspend was closed, all unsaved data was lost and everything was
Public bug reported:
I was just watching a youtube video fullscreen in Google Chrome.
I exited fullscreen with the Esc key: starting from that moment, the whole
Google Chrome window's content was replaced by a frozen frame of the video (I
could still hear the audio streaming). I couldn't see
Two more findings:
1) This doesn't only happen when the external screen is connected and
then disconnected. Random from-time-to-time system freezes happen
systematically whenever no external monitor is connected (no matter
whether it has been connected and disconnected, or it has never been
Is there any way, other than in BIOS (which apparently is not available
in my bios ), to disable the onboard Intel GPU and leave only the NVidia
enabled?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Two more findings:
1) This doesn't only happen when the external screen is connected and
then disconnected. Random from-time-to-time system freezes happen
systematically whenever no external monitor is connected (no matter
whether it has been connected and disconnected, or it has never been
And again, and again, and again.
And once more, re-plugging the external monitor caused an unrecoverable
freeze (meaning that neither ctrl+alt+f1 nor unplugging and replugging
the monitor would fix the issue) forcing me to a hard power off.
For god's sake when is this going to be looked at, at
The freezes seem to always occur at a mouse click.
No they don't. I've just experienced a freeze that happened while not
clicking.
--
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/1353620
This keeps happening (after several reboots). The freezes seem to always
occur at a mouse click.
How often the freezes happen seems to be apparently random. I have
experienced three freezes within very few minutes, and have also been
more than half an hour without freezes.
This is huge and has
82 matches
Mail list logo
