Daniel
I am Brian's wife, Jane
I am devastated to let you know that Brian succumbed to his prostate
cancer and died a few weeks ago
Please let everyone know
Thanks
Jane Burch
On 7/8/20 7:50 pm, Daniel van Vugt wrote:
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 19.10 (eoan) reached
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
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
On 24/2/20 3:12 pm, Daniel van Vugt wrote:
> Actually I should have just continued from comment #27. To do that
> please run:
>
>mv ~/.local/share/gnome-shell/extensions ~/old-extensions
Oops! I had already run the "dconf reset"!
Never mind, I was not aware of having changed the settings fro
Also, if you have upgraded to 19.10 then please run this again to send
us fresh system information:
apport-collect 1838919
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lo
Actually I should have just continued from comment #27. To do that
please run:
mv ~/.local/share/gnome-shell/extensions ~/old-extensions
and then reboot. Any improvement?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: mutter (Ubuntu)
Status: New =>
The conversation above is no longer fresh in my memory, but I can see a
couple of problems worth mentioning:
* The bug description at the top doesn't clearly describe the problem.
If the issue is "Slow and lost keyboard and mouse events" then please
explain how you experience that issue in more de
** Tags removed: disco
** Tags added: eoan
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => New
** Changed in: mutter (Ubuntu)
Status: Won't Fix => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Sorry for the delay. The problem still exists under 19.10 desktop, but
does not occur quite as often. However, it is slightly harder to escape
from... I either need to wait 20+ seconds uselessly pressing keys I will
have to subsequently delete, or tab to another command prompt, type
something in ea
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
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.
It sounds like the affected system is uniquely broken. The simple answer
would be to do a backup and then wipe/reinstall it from scratch.
The complex answer would be to check for gnome-shell extensions,
uninstall any non-Ubuntu ones. And to remove the relevant gtk-2
libraries and see what else the
I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan
(with gnome mostly at 3.34). The symptoms have not changed... my desktop
still hangs, loses keyboard events, and the log fills with the GTK 2/3
conflict messages. Meanwhile my Studio system behaves perfectly!
The log messages
I didn't see any problems logging on with gnome on xorg, or starting the
first terminal session.
However, as soon as I started the second terminal, the GTK2/GTK3 error
messages poured out. Opening a new tab on the same window does not
generate the messages.
This sounds like your gnome bug report
On 14/8/19 8:22 pm, Traumflug wrote:
> Installed packages don't matter if their content isn't in use. It does
> matter whether you run an X11 or a Wayland session.
>
> To switch between both, log out to get to the login screen. There is a
> gears icon right above the password entry field, click on
Installed packages don't matter if their content isn't in use. It does
matter whether you run an X11 or a Wayland session.
To switch between both, log out to get to the login screen. There is a
gears icon right above the password entry field, click on it. This
should open a menu allowing to choose
Thank you very much for your suggestion #21, Traumflug. I read the issue
you quoted and to be honest, I was quite disappointed in the responses
so far.
The symptoms sound very similar to those I reported here. I compared the
wayland packages on my desktop (slow or lost mouse and keyboard events)
w
If you're running on Wayland it might be related to this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you experienc
I had a bit of a brainwave this morning - or perhaps just awoke from my
stupidity!
I also have a laptop which runs ubuntu studio 19.04 amd64. At the
moment, my desktop which is suffering has the 5.0.0-23-generic kernel.
The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all
these pro
dpkg list next...
** Attachment added: "dpkg list"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Hi Daniel, thanks for not giving up! First, here is snap list:-
Name Version Rev Tracking Publisher
Notes
core 16-2.39.3 7270 stablecanonical✓
core
core18201907231074 stable
top on 4 second intervals rotates the same 5 or 6 threads, so I set the
interval to 20 seconds and copied the output to a file, which I have
attached. I have also attached the dpkg list.
** Attachment added: "top interval 20 seconds"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1
Please also run:
dpkg -l > allpackages.txt
and attach the file 'allpackages.txt'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
To manage
Just a couple of ideas:
* Please run 'top' and tell us if any process is using high CPU while
the problem occurs.
* Please run 'snap list' and paste the output here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
What can I do to help you diagnose the problem further, Daniel?
I think something changed recently, and that must have been an update. I
do not believe I have installed any new packages that might have called
for GTK2, so my guess is that it has been there since the clean 18.10
install and not bee
Thanks again. Life is rarely simple enough to reveal the cause of a
shell bug in the log. If it was though, then the canberra errors are the
only ones I think could be relevant.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Inco
Also, I will attach journalctl -xb log taken as soon as I booted the
system and logged on this morning. It seems to me that as soon as
systemd started the gnome terminal server unit, related error messages
began to be generated.
Chrome/chromium had not been started at the time - it was autostarted
Thanks for explaining Daniel #5. You will see I ran the command again.
However... It is interesting to see that even the apport-collect command
from a new terminal session triggered the canberra error.
brian@schizo:~$ apport-collect 1838919
(apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+
apport information
** Tags added: apport-collected
** Description changed:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last few
weeks and is now so bad I can hardly type an email (or this bug report!)
Because this bug was reported against the wrong project (comment #1) it
has the wrong attachments. To correct that please run:
apport-collect 1838919
Thanks for using 'ubuntu-bug' already. That's just a standard response
which was not entirely appropriate in this case.
I know, Chrome/Chromium'
Daniel post #2. That was exactly how I opened this bug report, so what
exactly are you missing?
Daniel post #3. I don't use Chromium, by preferred browser is stock
vanilla Chrome from their own repository. I did not think Chrome was
delivered as a snap - are you sure your comment is relevant?
--
The GL errors appear to be from Chrome/Chromium. Not Gnome Shell at all.
Although it does sound like they're related to snaps too:
https://wiki.ubuntu.com/DesktopTeam/GNOMESnapStartup
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1838919
When reporting bugs in the future please use apport by using 'ubuntu-
bu
** Package changed: gnome-software (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse events
To manage notifications abou
32 matches
Mail list logo
