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
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
Desktop Bugs, which is subscribed to mut
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
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
h
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and mouse
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
I'm not familiar with the code that does suspension so suggest:
1. Verify the bug is still in Ubuntu 19.04/19.10.
2. If so then please report it to the upstream developers at:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
and then tell us the new bug ID.
** Tags added: bionic
** Cha
** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
** Summary changed:
- Mouse cursor left frozen copy of itself
+ [nvidia] Mouse cursor left frozen copy of itself
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
*** This bug is a duplicate of bug 1827428 ***
https://bugs.launchpad.net/bugs/1827428
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 1827428, so it is being marked as such. Please look
You have been subscribed to a public bug:
Inevitably the mouse cursor will become fixated on screen at the
position it was when the screen was unlocked. When I switch TTY and come
back the lock screen will change and I'll be able to move the fixed
mouse cursor to a new location. Only fix is to res
To copy a workaround from the thread linked above: `nm-connection-
editor` still works great.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1767536
Title:
Accessing t
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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://b
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!)
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.
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
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.
** Also affects: gnome-shell
Importance: Undecided
Status: New
** Project changed: gnome-shell => oem-priority
** Changed in: oem-priority
Importance: Undecided => Medium
** Changed in: oem-priority
Importance: Medium => High
** Changed in: oem-priority
Assignee: (unassigne
Public bug reported:
When trying to suspend the system via pressing the power button in the
system tray with ALT key pressed, it is possible to interrupt the system
to enter sleep mode and fall back to screen lock. While trying to unlock
the screen, the system goes to sleep immediately.
Gnome-she
This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu4.4
---
glib2.0 (2.48.2-0ubuntu4.4) xenial-security; urgency=medium
* SECURITY REGRESSION: regression in last security update (LP: #1838890)
- debian/patches/CVE-2019-13012-regression.patch: fix a
memory leak introd
I'm on an iMac, so I want to make use of my Retina (hj-dpi) screen,
while also using external screens that are not hi-dpi.
I can confirm no good X11 support for separate dpis per screen. I was
able to mess around with xrandr, but I got ghosting on my mouse cursor
that I could not resolve. Possibly
Public bug reported:
Fingerprint gui on Asus A407Ma Zorin OS 15 not detect driver, please
solved it
** Affects: libfprint (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfpr
Public bug reported:
I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bug
** Changed in: glib2.0 (Ubuntu)
Status: New => In Progress
** Also affects: glib2.0 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu Trusty)
Importance: Und
Public bug reported:
I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output me
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1838890
Title:
Suspected memory leak i
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #632
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/632
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/632
Importance: Unknown
Status: Unknown
-
Upstream bug was closed "RESOLVED NOTABUG" on 2012-10-09
Changes were made to Gtk and not evince. Old behaviour
of scrolling with left mouse button has been moved to
right mouse button. Change also applied to nautilus.
Checked still the case with evince 3.28.4 in Ubuntu 18.04.
Due to change in f
For me, this bug just started happening when I did a software update
yesterday.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825544
Title:
Switch User menu item gone after u
*** This bug is a duplicate of bug 1671487 ***
https://bugs.launchpad.net/bugs/1671487
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 #1671487, so is being marked as such.
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'
This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1
---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium
* No-change backport from disco to eoan.
mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining
This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1
---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium
* No-change backport from disco to eoan.
mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining
This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1
---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium
* No-change backport from disco to eoan.
mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining
This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1
---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium
* No-change backport from disco to eoan.
mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining
This bug was fixed in the package mutter -
3.32.2+git20190711-2ubuntu1~19.04.1
---
mutter (3.32.2+git20190711-2ubuntu1~19.04.1) disco; urgency=medium
* No-change backport from disco to eoan.
mutter (3.32.2+git20190711-2ubuntu1) eoan; urgency=medium
* Merge with debian. Remaining
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 verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
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
** Tags removed: artful
** Tags added: bionic
** Changed in: gdm3 (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1748036
Title:
.pam_en
Yes, ~/.pam_environment is still not parsed in Ubuntu 19.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1748036
Title:
.pam_environment not applied if home directory is encrypted
** Changed in: gnome-control-center (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1838902
Title:
GNOME Control Center sticks whe
Thanks for the report Simon! Leo, could you have a look?
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1838890
Titl
51 matches
Mail list logo
