Vlad, honestly, I don't see this getting fixed anytime soon, this has
been an issue since a late revision of 18.10/19.04 (~2018).
Pinning is a time-tested solution for regressions but it does come with
overhead, especially when the issue is actually a dependency of a core
system component (naut
Hi Daniel,
Unfortunately, it would have taken too long to upload identical sets of
apport files and both of these bugs are related to using a physical
DisplayPort 1.2 cable. Both issues disappear when switching cables.
I erred on the side of reporting the issue so it could be addressed but
I don'
Public bug reported:
Currently I'm using a 4K AOC monitor on 20.04 LTS with a DisplayPort
cable.
Normally, there is a gear widget in the lower right corner of the screen
that allows me to select between XServer and Wayland. This gear is
missing. Switching to an HDMI cable corrects the issue but d
After a bit more troubleshooting, working with xrandr and the xorg.conf
doesn't seem to have any effect when on the tty, and xrandr throws a
cannot connect to display error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 1813441 ***
https://bugs.launchpad.net/bugs/1813441
@Sebastien, thank you for pointing out the bug was a duplicate. I've
posted my workaround in the linked bug since the workaround I found is
better than the current workaround.
Additionally, I really don't h
I didn't realize my bug was a duplicate
(https://bugs.launchpad.net/bugs/1875125).
This is a big issue for desktop users, I almost rolled back immediately.
I'll still be rolling back due to other bugs I've found since Friday, but in
the meantime I did find a slightly better way of working around
It looks like this may be an issue with the 5.4 kernel.
Same issue reported at the link below 3 months ago.
https://www.reddit.com/r/Fedora/comments/est6xt/kernel_54x_trackpack_stopped_working_and_usb_3/
** Summary changed:
- 20.04 xhci_hcd cannot read most usb drives
+ 20.04 - 5.4 kernel cannot
Public bug reported:
Upgraded to 20.04 LTS and began testing.
The USB subsystem is unable to read most of the USB 3/2 drives I have
on-hand.
I attempted to read from the devices they all result in the same error.
The manufacturers include:
Lexar USB 3.0 32G
Patriot Glade (Brand) 16G x2
SanDisk
After grokking the gnome documentation and poking around the filesystem
some more, there appears to be an undocumented way to disable the
desktop-icons extension to fix the workaround.
In /usr/share/gnome-shell/modes/ there is a json file ubuntu.json. It
has a list of enabled extensions one of whi
In addition to this bug, as an FYI to save time; the previous workaround
many people follow is installing nemo and setting it as the default for
desktop icons. This no longer works.
"gsettings set org.gnome.desktop.background show-desktop-icons false",
is ignored.
The desktop icon functionality s
Public bug reported:
Ubuntu 20.04 LTS
Dragging files from the desktop to a nautilus window folder doesn't
move, copy or perform any action. The animation upon releasing the click
goes back to the files original location.
Drag and Drop is broken.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Pack
hotkeys that would normally trigger a prompt such as the delete button
when a file is selected are also not working for files located on the
desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18751
Public bug reported:
Running the newest release of ubuntu (20.04LTS).
I entered my password to log in after the lock screen had engaged
automatically and it accepted my password (greying out the buttons) but
didn't log in.
Five minutes later it still hadn't changed so I went to another TTY and
k
[ 1051.565097] gnome-terminal-[3670]: segfault at 90 ip 7feaf3716a3b sp
7fff11fb7e10 error 4 in libgdk-3.so.0.2404.14[7feaf36db000+81000]
[ 1051.565128] Code: ab 9a fc ff 4c 89 ef 48 89 c6 48 89 c3 e8 6d 89 fd ff 4c
8b 44 24 08 4c 89 c7 e8 30 0d fd ff 4c 89 ef 48 89 c6 e8 75 95 fd ff <48>
Apologies for the delayed response, things have been pretty crazy.
I've attached the journal.txt you requested.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1867405/+attachment/5341946/+files/journal.txt
--
You received this bug notification because you are a me
I tested the kernels. Unfortunately none of them seemed to correct the
issue, 4.18-13 was a few seconds faster loading but not by much.
I updated the kernel at the same time as the software so its possible this
is related to one of the packages being updated.
I reverted back to my previous kernel
I've attached the requested fresh dmesg.txt.
I'll be reverting the kernel to see if anything improves and will post
back with the details.
As a side note, and its probably not related, I'm also seeing sporadic
temporary lockups which seem to correspond with the CE: hpet3 warning in
dmesg but even
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1867405/+attachment/5336724/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867405
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1867405/+attachment/5336725/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1867405/+attachment/5336723/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
After updating to the latest kernel (5.3 general/lowlatency) my W510
Thinkpad is taking forever to load gdm3. After some reading I installed
haveged as some issues indicated this as a possible fix. No dice, still
have the issue, no improvement.
On average it takes about 40 se
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1867405/+attachment/5336722/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867405
ping
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846153
Title:
gpg generate-key fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1846153/
ping
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846155
Title:
gpg --generate-key --batch prompt with SIGINT breaks shell
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Upon closer inspection of the ~/.gnupg folder it appears that at some
point a directory is created with the label private-keys-v1.d, the
generation process does not recreate the directory if its missing and
running the batch command returns a very un-useful "file not found"
error if the directory d
I've verified that adding %no-protection to the batch file does allow
the key generation to proceed past the error to completion but there are
other issues.
GPG generates the public key and exports to a file successfully. The
public keyfile contains data, but its untestable.
The private key is no
Reset cannot be typed into the terminal, it doesn't appear to be a
functioning bash shell.
I've included an OBS recording of the prompt as an attachment showing
the problem.
Its necessary to forcibly close and restart the shell.
I haven't tested it in a true tty, I'm used a stander pts pseudo sh
Public bug reported:
Description:
An unusual password prompt appears when passing --batch during key generation.
Using control+c to break to the shell, breaks the shell environment completely.
Steps to replicate:
As a root user:
#> gpg --batch --gen-key temp.batch
Please enter the pass phrase
Additionally, the workaround that many people suggest for similar errors
(via google) as described at https://d.sb/2016/11/gpg-inappropriate-
ioctl-for-device-errors does not work.
The output with proposed changes from the above link:
#> gpg --generate-key --batch < temp.batch
gpg: Generating a s
Public bug reported:
Description:
Generating a gpg key unattended fails on Ubuntu 18.04.3 LTS.
Standard User
> gpg --generate-key --batch < temp.batch
gpg: Generating a standard key
gpg: can't create '(null)': Permission denied
gpg: done
Root Superuser
#> gpg --generate-key --batch < temp.batch
The bugfix was merged upstream:
https://github.com/Icinga/icingaweb2/pull/3315
Ubuntu repo packages just need to be updated to include the fix, I can
confirm this is an outstanding issue with Ubuntu 18.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm receiving this error on 18.04.2 LTS. Will the fix for this will be
backported for the LTS releases?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668641
Title:
Error message: pam_systemd(su:ses
Looking over everything I have the only visible differences between the
day where I was having the issue and today was a kernel error related to
AER/ASPM. This appears to occur whenever docker setup networking for a
new container.
Today host error logs included a device of ID0008 not found which w
You can go ahead and close this bug as I can no longer reproduce it.
I had this issue replicated in a dockerfile environment and had been
debugging the issue all weekend long (new instance each step).
For whatever reason now reverting back to the exact same configuration
(using git checkout) it i
Public bug reported:
Dovecot authentication over IMAP fails when mysql driver configuration
"connect= host=127.0.0.1 ..." where dovecot and mysql are on the same
workstation.
Dovecot appears to work without issue when connecting over a socket, or using
the driver where connect= host=IP where
35 matches
Mail list logo
