Correction. I run command of Alain Rouet (alain-rouet):
# sed -i "s/boot_params\['nouveau.runpm'\] = '0'/boot_params\['nouveau.runpm'\]
= '-1'/" /usr/bin/prime-select
And output of the coomand cat /sys/kernel/debug/vgaswitcheroo/switch was
different. Now it's:
0:IGD:+:Pwr::00:02.0
1:DIS:
Maybe also shrink the icon so as to ensure it never touches the bar when
the bar is visible.
--
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/1762910
Title:
The position of audio
To avoid any odd-looking padding I think the solution would be to
enforce the OSD to stay as a square always, and just optionally paint
the bar over the top (possibly with a border to avoid conflicting with
some/future icons).
--
You received this bug notification because you are a member of
Looks like a fix is coming:
https://bugzilla.gnome.org/show_bug.cgi?id=782011
** Bug watch added: GNOME Bug Tracker #782011
https://bugzilla.gnome.org/show_bug.cgi?id=782011
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=782011
Importance: Unknown
We know. There are 830 reports of this crash from 18.04 right now:
https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c
And globally this is the 9th most common gnome-shell crash for 18.04 (or
6th if you look at just the past month).
** Changed in: gnome-shell (Ubuntu)
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136526/+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: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136524/+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: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1759621/+attachment/5136523/+files/Dependencies.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/1759621/+attachment/5136525/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-12-09 (150 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Package: gnome-shell 3.28.1-0ubuntu2
Sadly this is still happening to me on 18.04 as well. Every single time
I resume my machine from suspend. And it's not just that gnome-shell
crashes, but I have to sit for a good 2-3 minutes while apport does its
thing, while the machine is completely frozen from a UI perspective.
This is such a
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/1768653
Title:
chromium 66 FTBFS on armhf
Confirm on Lenovo ideapad 520S-14IKB (Intel i5-7gen, Nvidia 940MX , Intel
620HD).
On Ubuntu 17.10 (Nvidia driver 390.48 from ppa:graphics-drivers/ppa
ppa:graphics-drivers/ppa) prime-select worked fine.
On Ubuntu 18.04 prime-select not turn off nvidia (driver from ppa and driver
from
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for ubuntu-themes (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: ubuntu-themes (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-themes in Ubuntu.
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Changed in: hplip
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1766020
Title:
package python3 3.6.5-3 failed to install/upgrade: installed
Public bug reported:
Please sync transmission 2.94-1 (main) from Debian unstable (main)
The only delta exists for Unity indicator support, and Ayatana support
has been merged into Debian, so this is no longer needed.
Changelog entries since current cosmic version 2.92-3ubuntu2:
transmission
Attached is a debdiff applicable to 5.6-3, which is the current version
in Sid.
** Patch added: "1-5.6-3-to-5.6-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1770059/+attachment/5136511/+files/1-5.6-3-to-5.6-3ubuntu1.debdiff
--
You received this bug notification
Although Ubuntu 14.04 is still supported it is due to reach end-of-life
next year.
https://wiki.ubuntu.com/Releases
I recommend upgrading to a newer version of Ubuntu, not least because
PulseAudio 4.0 is very much out of date now and the developers would be
unlikely to be able to help (the
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
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.
Public bug reported:
Debian Sid contains a new upstream release of brltty. Let's merge it.
Changelog entries since the last Ubuntu upload:
brltty (5.6-3) unstable; urgency=medium
* debian/patches/41-java-bytecode-compat.patch: Bump java compatability to
1.6 and later (Closes:
Please try to only report one issue per bug report.
The first issue you report is in an area that has been bugging me for a
few years too (see bug 1607677). Please reword the bug title and
description to just be about that first issue.
The second issue you report is possibly bug 1759300.
**
See also related bugs:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=unlock
** Tags added: unlock
--
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/1769981
*** This bug is a duplicate of bug 1723615 ***
https://bugs.launchpad.net/bugs/1723615
Thanks. Let's track this in bug 1723615 then.
If you find more crash files then please continue to report them using
'ubuntu-bug' and the robots will hopefully be able to analyse those and
tell you what
No problem. This bug is now closed.
Anyone else who has problems can open a new bug.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
Javier,
If your physical buttons (the ones that move independently of the
touchpad, and not just painted on) are not behaving correctly then
please log a bug with:
ubuntu-bug libinput10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
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/1422253
Title:
gnome-shell crashed with SIGABRT in
I upgraded from Ubuntu 17.10 to 18.04 and all was fine for a couple
weeks. I think an update yesterday (5/7) caused the problem. I have two
accounts on the system. I can initially log into either fine but
switching to the other causes the purple screen with cursor only. It
does not matter if I log
Your bug report appears to be from Ubuntu 17.10. Please consider
upgrading to Ubuntu 18.04 LTS.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
OK, as is the pattern this week, the confusion here is the intersection
of two different bugs. Not one.
My gitlab merge request solves a different problem to this bug.
** Summary changed:
- Prompt the user when the power button is pressed
+ Prompt the user when the power button is pressed on a
There's probably no way GDM could cause this directly. But indirectly if
you are logging into a Wayland session in one case and Xorg in the
other, then that might be the main factor here.
Please try logging into both Xorg and Wayland sessions to see if one
works better.
Also, for Nvidia there
Public bug reported:
i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor with
1GB RAM,500GB HDD,
UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display crashes
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
*** This bug is a duplicate of bug 1767116 ***
https://bugs.launchpad.net/bugs/1767116
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 #1767116, so is being marked as such.
*** This bug is a duplicate of bug 1767116 ***
https://bugs.launchpad.net/bugs/1767116
Public bug reported:
I was changing from 390 to 340 when it happened.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic
I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to
give up on Ubuntu and give that a try. Some word of reassurance from the
Ubuntu team here would be nice. Where they marked this as fixed, I'm not
hopeful of a fix--at least anytime soon. If anyone has found a true and
simple
This occurs in 18.04 because versions 340 and 390 are attempted to be
installed at the same time and they apparently both want to modify
/lib/udev/rules.d/71-nvidia.rules
apt-get install -f was not able to fix the situation.
Workaround: remove all packages mentioning nvidia 340 and 390 (beware
Confirm the issue seems everybody on 18.04 and Nvidia GeForce is
suffering...
Duplicates ?
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363
--
You received this bug notification
In my case it was... complicated.
Turns out that after upgrade to 18.04 wayland was on by default for me.
prime-select intel worked fine
prime-select nvidia gdm would not show
Changing wayland to xorg in gdm (with intel) would not work - login
screen just kept reapearing. Forcing xorg through
Confirming on Dell XPS 15 9560; Nvidia is not power-down when prime
selecting Intel: I am now on 13W with TLP enabled... 17.10 would give me
about half of that.
In addition, I cant suspend properly. Half of the times it will freeze
an I need to force power down...
Together with
No, that 'area' setting doesn't work on my touchpad for some reason. A
alternative i found at https://askubuntu.com/questions/881939/libinput-
how-to-map-different-tappings-to-buttons-tappingbuttonmap-has-no-effe/
does something useful that i'd like to be a setting in the future,
exchange the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
This all might be related to https://bugs.launchpad.net/ubuntu/+source
/nvidia-prime/+bug/1765363 I think...
--
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/1752053
Title:
nvidia-390
Closing as I don't have that hardware anymore, I don't use eog, and will
not be using pre-18.04 OS.
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
After rm...
snap run libreoffice
Traceback (most recent call last):
File "/snap/libreoffice/59/javasettings.py", line 41, in
java_output).group("version")
AttributeError: 'NoneType' object has no attribute 'group'
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed
Not sure what the heck you all are recently taking about.
Most linux users of a ntfs partition are using to store files for use on any Os
or store files without any permission nonsense.
Those that actually place .exe files & want to then execute them from an Ubuntu
session would likely be using
Okay, so it looks like the traceback might have been a one-off.
If you remove the settings file and run libreoffice again, do you get
the traceback again?
rm
$HOME/snap/libreoffice/current/.config/libreoffice/4/user/config/javasettings_Linux_X86_64.xml
snap run libreoffice
--
You
This problem has just arisen, with my Canon Lide 200, on a recently
installed Ubuntu 18.04. The scanner worked fine with Ubuntu 16.04 and
still works under Winblows.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in
Can you observe the issue yourself with a similar setup?
Where are the files being open located? Is it on a USB stick? If so and
if the stick is mounted read-only, that explains why files can't be
edited. Note that in that case libreoffice should display a ribbon that
informs the user that the
I've a proposed fix at
https://gitlab.gnome.org/3v1n0/mutter/commit/993a40c9a4e161e40faa0467f98eadd1ac50dd22
I'm discussing with upstream about it.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because
This bug was fixed in the package cups-pk-helper - 0.2.6-1ubuntu2
---
cups-pk-helper (0.2.6-1ubuntu2) cosmic; urgency=medium
[ Shem Pasamba ]
*
debian/patches/Use_cups-pk-helper_in_org.opensuse.CupsPkHelper.Mechanism.conf.patch
- Use cups-pk-helper in
It could be that fixing this would also fixes lp:1703300
https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
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/1754949
Title:
gnome-shell crashed with
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => In Progress
--
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/1766137
Title:
[regression] Password accepted but login fails
> why it defaults to execute on when the in kernel driver does not.
Well, most users do not define the mapping of their user ids to Windows
ids, so the permissions cannot be stored to the device, and the
permissions have to be the same for all files and all users. If the
default was no-execute,
** Tags added: bionic
--
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/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
Status in gnome-shell
Public bug reported:
In 16.04, it is currently not possible to import OpenVPN configurations.
Specifically, imports fail with the error of:
The file 'filename.ovpn' could not be read or does not contain
recognized VPN connection information.
Error: Key file contains line 'client' which is not a
*** This bug is a duplicate of bug 1723615 ***
https://bugs.launchpad.net/bugs/1723615
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 #1723615, so is being marked as such.
Can confirm on a Dell XPS 9550 - power draw went from ~7W to ~20W after
updating to 18.04, even with prime-select intel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1765363
Udisks specifying a default mask was removed intentionally, leaving the
default to the NTFS driver. ntfs-3g defaults to all executable. People
often do have executable files on their NTFS drives and want to be able
to execute them. This has gone back and forth a few times over the
years and
Public bug reported:
When waking up the PC screen from standby, quite often the screen freezes for
10-20s.
I can't move the mouse or type anything. After a while, it unfreezes.
This is quite annoying because often the freeze is long enough to send the
screen to standby again for absence of
Public bug reported:
jackd2 package don't install in Ubuntu 18.04 LTS.
Broken dependencies, libreadline6 can't be installed anymore.
** Affects: jackd2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages,
I have a lot of computers in my office that needs this drive to work.
Neither Nouveau or VESA works with them.
If this decision persists I will have to move to another distribution (which I
hope to avoid).
--
You received this bug notification because you are a member of Desktop
Packages, which
Sure, here it is.
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+attachment/5136348/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Desktop
Packages, which
Note that there are crashes around the same time in /usr/lib/hidpi-
daemon/hidpi-daemon and /usr/lib/hidpi-daemon/hidpi-notification, which
are provided by System76, but looking at the dumps in /var/crash for
them, it looks like they are crashing _as a result of_ the gnome-shell
crash, as opposed
Public bug reported:
After upgrading my office machines to 18.04, some machines did not start
the GDM3.
After some testing the problem was that the ones that it did not work,
had SDDM installed too (KDE environment in those machines).
The upgrade were from 17.10 and 16.04.
Note that
** Changed in: gdm
Status: Unknown => Confirmed
** Changed in: gdm
Importance: Unknown => Medium
--
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/1766137
Title:
Do you happen to have and could you provide us with the following file
from the system?
/var/log/dist-upgrade/apt-clone_system_state.tar.gz
Thanks in advance.
** Changed in: desktop-file-utils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups-filters (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769982
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
--
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/1663050
Title:
Intel 7265 wireless device disconnect: link is not ready
** Bug watch added: GNOME Bug Tracker #795940
https://bugzilla.gnome.org/show_bug.cgi?id=795940
** Changed in: gdm
Importance: Undecided => Unknown
** Changed in: gdm
Status: New => Unknown
** Changed in: gdm
Remote watch: None => GNOME Bug Tracker #795940
--
You received this
I have the same problem. Does also not work with the nautilus version
from flathub.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1767817
Title:
Full text search does not work
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954
Title:
package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
Public bug reported:
run `sudo do-release-upgrade` on a relativity new 16.04 EC2 instance.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: desktop-file-utils 0.23-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
I'm thinking that Multi-Arch: foreign on the transitional package libp11
-kit-gnome-keyring might help.
If someone wants to verify that, please do, otherwise I'll try tomorrow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Ubuntu 18.04, Firefox 59.02 64 bit has the same problem. Nvidia driver
390.48 in use.
--
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/1730410
Title:
Window full-screen size when
** Also affects: cups-pk-helper (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-pk-helper in Ubuntu.
https://bugs.launchpad.net/bugs/934291
Title:
Deleting or stopping
FWIW, I tried the Position_fix quirking suggestions here:
https://wiki.ubuntu.com/Audio/PositionReporting and didn't see any
improvement.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Anyone affected - were you using any PPAs?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
Title:
package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
This bug was fixed in the package ubiquity - 18.10.1
---
ubiquity (18.10.1) cosmic; urgency=medium
[ Iain Lane ]
* Bump sources to cosmic
* Automatic update of included source packages: bterm-unifont 1.5,
choose-mirror 2.78ubuntu4, preseed 1.71ubuntu8.
[ Andrea Azzarone
Removing amdgpu-pro by running "amdgpu-pro-uninstall" from ubuntu
recovery mode solved this problem for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1762127
Title:
Ubuntu stuck in
Public bug reported:
Happy to do further testing, fresh install of Bionic. Discovered this
when trying to do a video conference using the built in mic and was able
to verify the issue by installing gnome-sound-recorder.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base
For nautilus, neither position nor size works for either user or sudo in
the Ubuntu 18.04 release, nautilus package 1:3.26.3-0ubuntu4.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Pretty sure at least I did at several points in the past. Not sure they
were active at the time of the report, though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
I rebuild the ibus-gtk3 package myself and it seems to work fine so far:
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16.
** Bug watch added: Mozilla Bugzilla #1405634
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634
--
You received this bug notification because you are a member
Should we just ask author of
https://salsa.debian.org/debian/ibus/commit/097e35c350edf76015c637c26ef637d80191052d
commit to know the reason why the ibus-xx-f19-password.patch is removed?
As I see from this comment in ibus' github page:
Public bug reported:
please fix this soon.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture
** Changed in: fonts-liberation2 (Debian)
Status: New => Fix Released
** Changed in: fonts-liberation (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-liberation in Ubuntu.
I closed the Xenial task since deja-dup in Xenial doesn't use ulimit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1751460
Title:
[regression] deja-dup-monitor crashed with
Attaching lsusb -vv of the device.
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1769914/+attachment/5136192/+files/lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
Public bug reported:
PulseAudio thinks that a Fiio E10K can capture audio and tries to
configure that, leading to a ton of:
retire_capture_urb: 2492 callbacks suppressed
messages in dmesg. The device has no capture ability, alsamixer also
only shows one master playback control; no capture one.
Removed the .gladep file; it seems to have crept in by error during the
git migration (also in my cosmic upload) and uploaded bionic. Thanks and
sorry cyphermox if this treads on your toes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
1 - 100 of 150 matches
Mail list logo
