It seems that brltty is now installed by default for Ubuntu 22.04 and
this bug prevents USB to serial adapters from working correctly out of
the box. Don't give nay-sayers a reason to no upgrade/use Ubuntu 22.04.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bug
I can reliably reproduce this bug:
1) Boot into Ubuntu 20.04 Beta
- But will not trigger if you are signed into Ubuntu One already
- I am booting the ISO using grml-liveboot
2) Open Settings
3) Click About (bottom of left pane)
4) Click Software Updates (bottom of right pane)
5) In the Softw
Attached is the output of `journalctl -b 0` as requested.
I had a terminal open and ran `logger [LP1871519] ...` as I interacted
with the settings dialog to help you track down what is going wrong. I
will answer your other questions in another comment as I cant see them
when attaching files
** At
> Could you add a screenshot to the bug showing the control UI?
image is attached.
> What monitors config do you use?
I have one monitor, a Viewsonic 23" VS14880
(https://www.viewsonic.com/us/vx2370smh-led.html)
** Attachment added: "display control ui"
https://bugs.launchpad.net/ubuntu/+s
A very similar thing happens if you keep changing the Adjust for TV
slider after each time you click the green "Apply" button so that code
path should be tested as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Public bug reported:
## Version tested:
Ubuntu 20.04 Beta
## Reproduction steps:
Boot Ubuntu 20.04 Beta ISO
Launch Settings window
Open the Display settings
Click the button to set scale to 200%
Push green apply button at top right of window
(screen resize)
Push Keep Changes button
Click the b
I would like to also mention that Ubuntu 20.04 Daily (not MATE) crashes
on Virtualbox and KVM and that, as mentioned previously, running `sudo
apt-get purge gstreamer1.0-vaapi` fixes the crash to login issue.
Another workaround is to use Ubuntu on Wayland but in Virtualbox no
mouse pointer is visib
Hi Marco,
Both 19.04 and 19.10 have the same Disco Dingo background so I used the
wrong VM without noticing.
Non fixed gnome-shell (19.04) has package version 3.32.0+git20190410-1ubuntu1
Fixed gnome-shell (19.10 daily build) has package version gnome-shell
3.32.2-2ubuntu1
--
You received this
I booted the wrong iso. 19.10 daily is indeed fixed. Sorry for the
confusion.
** Attachment added: "Screenshot from 2019-07-29 20-07-17.png"
https://bugs.launchpad.net/gnome-shell/+bug/1809788/+attachment/5279944/+files/Screenshot%20from%202019-07-29%2020-07-17.png
--
You received this bug
I don't think "the bug" is fixed (It looks that way because the dialog
shows only a single line)
bolt ctl doesn't provide a long enough dialog, try my bug at
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721908
** Attachment added: "bug not fixed 19.04 daily 30-Jul-2019"
https:
This issue can be closed. This system was modified at some point with no
notice in the configuration file.
I pulled the deb package from /var/cache/apt, extracted the data.tar.gz
and inspected my.cnf
---
Additional debugging used to verify:
user@hostname:~$ apt-cache policy mysql-server*
mysql
I tried to reproduce this from an upgrade of Ubuntu Server 14.04.6 ->
16.04 and it did not reproduce. I can get more information on the
problematic system via VMWare snaphots I have saved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the package of
http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-5.7/mysql-5.7_5.7.25.orig.tar.gz
file
./packaging/deb-in/extra/apparmor-profile
The following pids are listed but not mysql.pid
# Allow pid, socket, socket lock file access
/var/run/mysqld/mysqld.pid rw,
/var/run/mysqld/my
Public bug reported:
On Ubuntu 16.04.6 LTS, after apt purge mysql-server* then apt install
mysql-server the intallation fails because the AppArmor profile is
incomplete. Booting with kernel command line parameter apparmor=0 allows
successful install.
Running aa-logprof shows that the pid file is
*** This bug is a duplicate of bug 1378095 ***
https://bugs.launchpad.net/bugs/1378095
sss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304134
Title:
aa-enforce crashed with apparmor.common.A
*** This bug is a duplicate of bug 1378095 ***
https://bugs.launchpad.net/bugs/1378095
I just came from
https://help.ubuntu.com/lts/serverguide/apparmor.html.en which links to
this bug. It appears that the real bug report already has a fix
released. I believe the Ubuntu help documentation need
I have the same issue with Linux Mint 19 (Ubuntu 18.04 based) using
kernel 4.15 but for QCA9377 chipset.
I compiled the 4.18 kernel using `make localmodconfig` and have the same
problem.
I had sources for kernel version 4.9.24 and it exhibits the same behavior
(failed to wake target for write32
This has also bugged me for some number of months but the work around is really
easy -- just use
apt purge snapd
instead of
apt remove snapd
What happens is that upon removal of the snapd package, dpkg sees that
/var/lib/snapd/apparmor/snap-confine is empty and removes it which later
breaks ap
** Description changed:
After installing apparmor, apparmor-utils, and libapache2-mod-apparmor
and enabling a virtual host that uses the changehat feature, it is
impossible to "(A)dd Requested Hat" or "(U)se Default Hat" because there
isinconsistent use of q.promptUser() call in the " elif
Public bug reported:
After installing apparmor, apparmor-utils, and libapache2-mod-apparmor
and enabling a virtual host that uses the changehat feature, it is
impossible to "(A)dd Requested Hat" or "(U)se Default Hat" because there
isinconsistent use of q.promptUser() call in the " elif type ==
'u
It appears this bug is not specific to the keyring package. Someone has
already change to gnome-shell (thank you)
---
other dialogs are affected by the same issue.
https://bugzilla.gnome.org/show_bug.cgi?id=786331
** Bug watch added: GNOME Bug Tracker #786331
https://bugzilla.gnome.org/show_b
Gnome bug reported at https://bugzilla.gnome.org/show_bug.cgi?id=790212
** Bug watch added: GNOME Bug Tracker #790212
https://bugzilla.gnome.org/show_bug.cgi?id=790212
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Changing from "keychain" to "keyring" I got a better look at the dialog
again.
** Package changed: keychain (Ubuntu) => ubuntu-keyring (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721908
T
Public bug reported:
I hope this bug is in keychain package. This is only a best guess.
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.13.0-12-generic #13-Ubuntu SMP Sat Sep 23 03:40:16 U
I have had the overlapping buttons happen to me as well. Very difficult
to recover from less a CPU reset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260948
Title:
dead end when changing user
To
Public bug reported:
Coming from Windows to Kubuntu, user switching is counter-intuitive when
switching between multiple users. The problem is two fold
1) The "switch user" window does not close after selecting a user to switch to
2) The "switch user" window does not do anything if trying to acti
26 matches
Mail list logo
