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"
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 Desktop
Packages, which is subscribed to
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
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Please also run:
dpkg -l > allpackages.txt
and attach the file 'allpackages.txt'.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838919
Title:
Slow and lost keyboard and
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 Desktop
Packages, which is subscribed to gnome-shell in
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
It appears you are using the unsupported 'oibaf' PPA on this machine:
version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908031930.2dd598~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908031930.2dd598~oibaf~b
Please remove
If possible, please also take a video of the problem with a phone and
then attach the video here.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- display flickering in perpetual loop while starting ubuntu 18.04.2
+ [i915] display flickering in perpetual loop while
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
**
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:
** 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
*** 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
Your system is still using the unsupported 'oidbaf' PPA:
version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b
Please try using 'ppa-purge'
Hi Lukasz,
We are in luck, after some very helpful debugging done by the customer, I have
been able to reliably reproduce this issue myself.
Firstly, this issue only affects users of Ubuntu inside a VMware Horizon VDI,
and only occurs after you install the VMware Horizon Agent for Linux.
The
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 Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1767536
Title:
Accessing the
Chelmite, change it to 2 and see if it works better
sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/*
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1838836
Title:
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
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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!)
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Also affects: webkit-open-source
Importance: Undecided
Status: New
** No longer affects: webkit-open-source
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: webkit (Ubuntu)
** No longer affects: webkit (Fedora)
** Also
Reopening mesa for bionic, because the revert needs to be dropped once
the kernel is fixed, otherwise Ice Lake is broken because it needs
softpin for the DRI driver to work.
** Changed in: mesa (Ubuntu Bionic)
Status: Fix Released => In Progress
--
You received this bug notification
I am not sure that the update fixed the problem. I am running 19.04 that
is up to date and I am still having the problem with installing a
network printer.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Public bug reported:
Details here: https://photos.app.goo.gl/ummEcpamq3yYA7p38
Device: Ubuntu 19.10 on Wayland (last build for 5 August 2019), HP 250 G6
Notebook, Celeron N3350 (Apollo Lake), Intel HD 500.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
Public bug reported:
gnome 3.28.2
Laptop needs to be re-started
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
@yparitcher is it possible for you verify with disco using a live cd?
https://tutorials.ubuntu.com/tutorial/try-ubuntu-before-you-install
Typically, we want to see srus verified by testing the specific
code/release, if possible. Even with simple patches, sometimes things
can go wrong.
--
You
> is it possible for you verify with disco using a live cd?
to clarify, actually installing disco to test/verify is preferred, but I
suggested the live cd as that will let you reproduce the problem and
verify the fix, without having to actually install disco to your hard
drive - the live cd runs
** Changed in: jackd2 (Ubuntu)
Status: New => Confirmed
** Changed in: jackd2 (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
** 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:
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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
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
** Tags added: disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1838963
Title:
Firefox on Wayland opens with black screen
Status in firefox package in Ubuntu:
Confirmed
Bug
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I get:
wifi.powersave = 3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1838836
Title:
network-manager needs to be restarted frequently
Status in network-manager package in
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.
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 Desktop
Packages, which is subscribed to
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
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 Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
Public bug reported:
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 restart the computer
This bug was fixed in the package libinput - 1.10.4-1ubuntu0.18.04.1
---
libinput (1.10.4-1ubuntu0.18.04.1) bionic; urgency=medium
* dont-disable-tapping-on-mt-tool-palm.diff: Don't disable tapping if
tool-based palm is detected. (LP: #1837962)
-- Timo Aaltonen Mon, 29 Jul
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
Confirming per duplicate bug #1707354.
** Changed in: webbrowser-app (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is
** 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:
To clarify, it resolved the issue for me. I was previously unable to
connect because NTLMv1 was turned off where I work. Now I can connect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
I tested the proposed package and it worked for me. I connected via
NTLM.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1817537
Title:
libsoup should support ntlmv2
Status in
Yes, it was likely a font caching issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1838944
Title:
[snap] title bar shows text, all letters are squares
Status in
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1838890
Title:
Suspected memory leak in
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1838944
Title:
[snap] title bar shows text, all
I've run into the same problem, using Kubuntu 18.04 (about 10 years
after this was reported).
The machine is used by multiple people, and they should not mess up each
other's printer settings. So I removed them from the lpadmin group.
However, now the only way to set (local) printer defaults is
looks like a patch to disable softpin on mesa (to fix bug #1836721)
actually regressed ICL which needs softpin... so now softpin needs to be
backported to bionic kernel (4.15) so that the mesa revert can be
dropped
** Changed in: mesa (Ubuntu Bionic)
Status: Fix Committed => In Progress
eoan has 5.2
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1825940
Title:
[graphics] Enable ICL
Status in
tested the update on bionic/disco on Intel (Whiskey Lake) and AMD
(HAINAN), works fine
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1831700
Title:
Mesa 19.0.8 stable release
Status
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Disco)
--
You received this bug notification because you are a member of Desktop
Packages, which is
Same problem here. Ubuntu 19.04 and WH-1000XM3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1724919
Title:
Bluetooth headphones only use A2DP when connected manually
Status
I know what the problem was, I had title fonts set to be fonts-league-
spartan, in gnome-tweaks (0.1 of it installed), after the upgrade to
19.10 i have (0.3 of the font installed) and for some reason the fonts
were set to "None", however already running gui applications had the
text still
Oh, and I don't have apport installed anymore. And don't plan to re-
install it again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1838944
Title:
[snap] title bar shows
** Also affects: sound-2.6
Importance: Undecided
Status: New
** No longer affects: sound-2.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1793410
Title:
[Acer Swift
This bug was fixed in the package gst-plugins-good1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-plugins-good1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream release (LP: #1832123)
* Updated references from 1.14.4 to 1.14.5
-- Iain Lane Wed, 03 Jul 2019 17:54:41
This bug was fixed in the package gst-plugins-ugly1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-plugins-ugly1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul 2019 11:42:40 +0100
**
I still can't reproduce the problem in a fully up-to-date bionic VM, using the
instructions in bug #1795169, which is a duplicate of the original bug report.
I've tested both X (default) and Wayland sessions.
To anyone affected, can you please point to the particular website
you're using to
This bug was originally reported against Cosmic, which is now end of
life.
@Coenraad, what do you mean by "from further upstream"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1814551
This bug was fixed in the package gst-plugins-base1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-plugins-base1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream release (LP: #1832123)
- debian/patches/CVE-2019-9928.patch: drop - it's in this release
-- Iain Lane Wed,
This bug was fixed in the package gstreamer1.0 - 1.14.5-0ubuntu1~18.04.1
---
gstreamer1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
-- Iain Lane Wed, 03 Jul 2019 15:34:47 +0100
** Changed in: gstreamer1.0 (Ubuntu Bionic)
The verification of the Stable Release Update for gstreamer1.0 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
This bug was fixed in the package gst-python1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-python1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul 2019 13:30:17 +0100
** Changed in:
This bug was fixed in the package gst-rtsp-server1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-rtsp-server1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5*
-- Iain Lane Thu, 04 Jul 2019 13:32:16 +0100
**
This bug was fixed in the package gstreamer-editing-services1.0 -
1.14.5-0ubuntu1~18.04.1
---
gstreamer-editing-services1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul
This bug was fixed in the package gstreamer-vaapi -
1.14.5-0ubuntu1~ubuntu18.04.1
---
gstreamer-vaapi (1.14.5-0ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul 2019 13:35:50 +0100
This bug was fixed in the package gst-libav1.0 - 1.14.5-0ubuntu1~18.04.1
---
gst-libav1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul 2019 12:04:24 +0100
--
You received
This bug was fixed in the package gst-plugins-bad1.0 -
1.14.5-0ubuntu1~18.04.1
---
gst-plugins-bad1.0 (1.14.5-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1832123)
* Update references to 1.14.5
-- Iain Lane Thu, 04 Jul 2019 10:16:29 +0100
**
Thanks for the suggestion.
The chromium-browser package is becoming a transitional package, for all
intents and purposes, so it's meant to be eventually removed. Adding
more new transitional packages that just switch the snap store channel
in use doesn't seem very useful, and goes against the
The issue seems quite serious, although the downside of it is that it
only affects certain users on certain environments. Before accepting
this into -proposed I'd like to know a bit more: you mentioned in the
impact field that the bug is impacting users (or one user?) on VMware
Horizon VDI, but
** 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
Can you please run the following command to attach more detailed
information to the bug report?
apport-collect 1838944
Additionally, the output of the following commands would be useful:
snap info core core18 chromium gtk-common-themes
And a screenshot of the problem.
Thanks!
**
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
Public bug reported:
Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 68.0.1+build1-0ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Public bug reported:
Details here: https://photos.app.goo.gl/2CjpJGB1wEWU8qJw6
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 68.0.1+build1-0ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
Status: Confirmed => Incomplete
** No longer affects: ubuntu-drivers-common (Ubuntu)
** No longer affects: ubuntu-drivers-common (Ubuntu
Public bug reported:
3rd party PPA Mesaremoved, and problem stil persist in dmesg:
[ 52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen
encoder in use 0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.2.0-050200-generic x86_64
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825544
Title:
Switch User menu item gone after
This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.18.04.3
---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.18.04.3) bionic; urgency=medium
* debian/templates/dkms_nvidia.conf.in:
debian/patches/buildfix_kernel_5.0.patch,
The verification of the Stable Release Update for nvidia-graphics-
drivers-340 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
Ouch, it go truncated locally, not during upload :( The local copy of
that file is truncated too.
Since you got the one without segmentation, you only got the logs from
the one that is currently working.
I re-did the experiment, and using the `--since` option of journalctl
I've cut the logs to
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1837834
The shorter one ends at Jul 1, long before I asked you for the tests, and also
its last line looks broken. It is mot probably incomplete, somehow a part of it
got lost during upload.
In the longer one I have found one of your two tests. I have cut it at the
beginning of that test and uploaded
NM 1.18.0-1ubuntu6 with the above-mentioned merge request merged has
been uploaded and in the -proposed -> -release migration the
autopkgtests have all passed now. Closing as fixed.
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug
*** 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.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1837962
Title:
Tap-to-Click of SYNA8005 touchpad (06CB:CD8C)
It appears you are using the unsupported 'oibaf' PPA for your Mesa
files. Please remove the PPA from your system and retest.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
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,
Thanks Daniel; I've removed the buggy version from proposed, let's wait
for the next one to be in Debian
** Changed in: libraw (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libraw in
Public bug reported:
Description:Ubuntu 18.04.2 LTS
Release:18.04
How to solve this dmesg:
[ 50.990513] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen
encoder in use 0
I use dual port(DVI/HDMI) AGP Radeon HD4650 with DVI port connected to
LCD.
ProblemType: Bug
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.
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.
1 - 100 of 122 matches
Mail list logo
