this issue does not appear related to openstack-ansible
** Changed in: openstack-ansible
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Freeze began after a system update
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ite details.
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release:22.04
jonathan@Apollo-Lake-N3450:~$ ntpq -p
remote
of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
jonathan@Apollo-Lake-N3450:~$ ntpq -p
remote refid st t when poll reach de
com/JonathanFerguson/NTP with
the new location of ntp.conf, after restarting I noticed that the resultant
output was missing requisite details.
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N
requisite details.
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
jonathan@Apollo-Lake-N3450:~$ ntpq -p
re
://wiki.ubuntu.com/JonathanFerguson/NTP with
the new location of ntp.conf, after restarting I noticed that the resultant
output was missing requisite details.
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N345
cation of ntp.conf, after restarting I noticed that the resultant
output was missing requisite details.
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
Description:Ub
of ntp.conf, after restarting I noticed that the resultant
output was missing requisite details.
-
Compare the following and the lack of ".MCST." and ".ACST.":
Original ntp on Apollo-Lake-N3150
jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
Description:
Public bug reported:
Because of bug #2033652 I was trying to report a gdb crash from
/var/crash. It spent a long time uploading data, then and then popped up
an error dialog:
Network problem
Cannot connect to crash database, please check your internet connection.
HTTP Error ???: Bad gateway
(I
Public bug reported:
I was debugging gimp when gdb to debug bug #2031907 when gdb crashed on
me and reported a useless backtrace followed by this:
---
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it.
I do not see this issue often enough to be able to reproduce it for
troubleshooting purposes. Can't remember the last time I saw it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This issue is also present on Bionic. Is there a chance that the network
manager would be fixed in Bionic, as part of Ubuntu Pro?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I mean, the bug is three years old and presumably by now the vast
majority of web sites have renewed their certificates and the new ones
are compatible with SECLEVEL=2 since all of the signing authorities
stopped issuing incompatible ones years ago, so it's kind of moot at
this point.
--
You
Public bug reported:
If you suspend from GNOME, wake your machine back up, and then once it's
totally back up, run `shutdown --show` as root, it says "syspend is
scheduled for (null)". It shouldn't say (null) there, which I suppose is
a different bug, but the bug I'm concerned about is that the
** Attachment added: "printers.conf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2007413/+attachment/5647479/+files/printers.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Public bug reported:
When printing to the printer "m479" shown in the attached config files,
specifying the number of copies to print doesn't work, i.e., I always
get one copy. This is true both from GUI print dialogs and from lp on
the command line.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Interestingly, the wifi icon is currently flapping back and forth
between the question mark and the fully connected symbol every few
seconds. If I run nmcli networking connection check in a loop it
switches to "full" when the fully connected symbol is showing and
"portal" when the question mark is
jik@framework1l:~$ nmcli networking connectivity check
portal
jik@framework1l:~$
I'm not using a VPN.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1844897
Given your description, I don't think the upgrade left resolvconf
installed. I think I can my ansible playbook after running the upgrade
and it reinstalled resolvconf which had been uninstalled by the upgrade.
I guess if resolvconf can't be removed yet because of the reverse-
dependencies, then
Public bug reported:
If I create a 5-second video of my desktop with the "Take a Screenshot"
tool (as an aside, is that tool built into gnome-shell now or something?
I couldn't figure out what executable the app icon corresponds to, i.e.,
I couldn't find the desktop file for it :shrug:) and then
See: https://github.com/jikamens/remember-the-yubikey
The relevant part here is that the unit file just starts up a shell
script that checks if my YubiKey is plugged in, and if it isn't it
exits.
I don't keep my YubiKey plugged in when the laptop is closed and idle —
and it certainly wasn't
Two ideas, one of which I've already mentioned above:
1) You could migrate the address and port settings from sshd_config to
listen.conf _before_ installing the new sshd_config, so that they will
be preserved even if the config gets replaced with the vendor version
because of a merge conflict
1) Nobody reads the release notes.
2) I am not "overwriting configuration files with 'known good' ones," I
am making specific changes to the config files with ansible plays.
Specifically, before fixing my playbook for Kinetic, it looked like
this:
- name: enable root ssh public key
Hello,
I am unclear about why you are asking for the contents of my sshd_config
file, given that the problem I described here isn't the merge conflict,
but rather what happens in terms of the migration from ssh service to
socket when the user opts to install the vendor version of sshd_config
as a
It looks like in today's Kinetic update iwd was removed, perhaps because
of this bug?
If so then the removal caused another problem:
/etc/NetworkManager/conf.d/iwd.conf still existed after the iwd package
was removed (I don't understand why, honestly), so even after I unmasked
and re-enabled
Public bug reported:
Setting up network-manager-config-connectivity-ubuntu (1.40.0-1ubuntu2) ...
Failed to restart network-manager.service: Unit network-manager.service not
found.
invoke-rc.d: initscript network-manager, action "force-reload" failed.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
systemctl disable wpa_supplicant wasn't good enough. I had to mask it.
Before I masked it, something started it on reboot even when it was
disabled (I don't know what was starting it).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
ThinkPad X1 Carbon 6th Gen
WiFi was working fine.
Installed today's batch of Kinetic updates.
Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB
dongle and plug into my router to be able to submit this bug report).
ProblemType: Bug
DistroRelease:
Public bug reported:
During upgrade from Jammy to Kinetic, I get asked what to do because my
sshd_config has been modified. I say to do a 3-way merge. It says 3-way
merge fails. I shrug, figure I'll just restore my customizations with
Ansible after the upgrade like I always do, and tell it to use
*shrug* I've had this computer since 2016 and when I first set it up I
used resolvconf to configure it and have continued to do that.
It's no skin off my nose—if it's deprecated I'll find something else to
use—but it seems to me that if you're going to keep the package in the
repository you
Public bug reported:
Setting up resolvconf (1.91ubuntu1) ...
cp: not writing through dangling symlink
'/etc/resolvconf/resolv.conf.d/original'
dpkg: error processing package resolvconf (--configure):
installed resolvconf package post-installation script subprocess returned
error exit status 1
Public bug reported:
Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
after I was idle for 20 minutes, as it is configured to do. The lid was
closed when the laptop went to sleep. I was unable to wake up the
laptop. Opening the lid back up should have caused it to wake up but
Public bug reported:
Same issue as reported before for other versions.
Here 1.187.31
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.31
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules:
Yes, the print job in question works when I print it to the driverless printer.
I would not say that it is therefore reasonable to declare that this issue is
resolved, but *shrug* whatever.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jonathan 8896 F pulseaudio
CasperMD5CheckResult: unkn
>Do you have cups-filter 1.28.15 installed
Yes, and I rebooted after installing it just to make sure. Problem
persists.
>Or did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug?
I _also_ have this setting in my printers.conf. So clearly this
Here's my printers.conf, since it doesn't look like ubuntu-bug attached
it, and there's no sensitive information in it.
** Attachment added: "printers.conf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+attachment/5579950/+files/printers.conf
--
You received this bug
Public bug reported:
I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI socket://m551dn.kamens.brookline.ma.us:9100"
in printers.conf) and the same physical printer configured
The file prints with pdftops-renderer=gs.
I can fix this for me personally, but is there any way to adjust the
default CUPS configuration for the type of printer that I have to make
this setting the default for others with the same printer, so they don't
also run into this issue?
** Changed in:
Public bug reported:
I have an HP LaserJet M551dn printer which usually works just fine with
CUPS. Tonight, however, I discovered that I was completely unable to
print one particular PDF file (unfortunately I can't provide you with
the file because it's a scan of a tax form with PII on it). CUPS
Public bug reported:
While installing full upgrade from terminal - sudo apt full-upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.29
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules:
In case you don't want to wait for aruiz's loader to be packaged in Debian (and
then trickled down to Ubuntu), here's a PPA:
https://code.launchpad.net/~helkaluin/+archive/ubuntu/webp-pixbuf-loader
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
After running "sudo apt upgrade" and approving the listed packages, the
following error occurred after unpacking a number of packages:
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
To expand on the above, have the Firefox and snapd developers figured
out how to incorporate native messaging in a snap-based browser? You
guys are locking out a significant portion of useful extensions if not
figured out.
--
You received this bug notification because you are a member of Ubuntu
This is still a problem but I'm not convinced it's enough of a problem
to warrant reopening the ticket.
I run into this because my `systemd --user` process persists between
logins because I have persistent service units running under it. For
most people `systemd --user` will exit when they log
This appears to no longer be an issue with the current versions of
systemd and udev in 21.04.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: systemd (Ubuntu Groovy)
Status: Incomplete => Fix Released
--
You received this bug notification
Please tell me specifically how to enable debug and afterward capture
the logs that you want to see.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916418
Title:
Custom
For those of you who landed here looking for how to use DisplayLink in
Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19
/update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I performed the splash -> nosplash test described above; it made no
difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1920067
Title:
Xorg with EVDI can't start with
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1920067
Title:
Somehow today's Hirsute updates have
Public bug reported:
As I indicated in a bug report I filed earlier today,
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms
can no longer compile the evdi kernel module with the 5.11 kernel. So,
to work around this, I need to keep using the 5.10 kernel instead.
But I can't,
** Attachment added: "list of packages upgraded today from dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+attachment/5471986/+files/upgraded.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2
Public bug reported:
Note: I'm guessing that lvm2 is the most likely culprit for this issue,
but I don't know for certain.
After today's Hirsute upgrades, my system won't boot. The boot gets to
the point where it asks me for the passphrase for my encrypted root
disk, and I enter it, and then it
Public bug reported:
DisplayLink uses these udev rules to start the displaylink service when
a displaylink device is plugged in:
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTR{idVendor}=="17e9",
IMPORT{builtin}="usb_id", ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
10100727: The recent upgrade of librsvg2-2:i386 and librsvg2-common:i386
(from 2.40.20-2 to (2.40.20-2ubuntu0.1) "broke" the display of card
styles Anglo and Gnomeangelo, in the aisleriot "Klondike" solitaire
game. By "broke", I mean that the card faces displayed only in part --
elements were
The issue seems gone after a reboot. Theming and colors are back to
normal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1888065
Title:
Screen dies/black after changing
Public bug reported:
I upgraded to 20.04 over a month ago and it's been working fine. I have
one monitor (external). I tried turning on fractional scaling in the
display settings and the screen immediately turned black. I waited,
expecting the "confirm changes" prompt to timeout and restore the
This is still occuring in 20.04 along with the notification at bootup.
It has not been fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1869981
Title:
Printer
So, something that is surprising me is that nobody has asked for any
type of report. I would love to share any diagnostic information I have,
just give me a terminal command or path to a text file and I will share
it.
--
You received this bug notification because you are a member of Ubuntu
Touch
It also seems that the notification repeats at midnight as well
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1864558
Title:
Printer adds automatically at boot with
I want to add that it seems rather widespread, as just about every in depth
review I have seen of 20.04 on YouTube brings up this issue.
Also, disabling the notification does not work because of the fact that it
occurs at first login.
Considering how widespread this is, shouldn't it be at a
Same probleme with the modification you suggest.
root@bowser:~# cat /etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network-online.target
[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto
[Install]
WantedBy=multi-user.target
I am not sure how widespread this is, but I can also confirm this happens on my
laptop as well. Ever since updating to 20.04 I always get the "printer added"
notification on bootup regardless of whether it was added already or not.
On previous versions this would only happen on the first bootup
Public bug reported:
I am running a Ubuntu 20.04 server with lxd and kvm/qemu.
I try to connect a nfs share at boot. It is working while I do not configure
any bridge with netplan. I am creating directly a systemd service for the NFS
mount but I have the same problem if I edit the fstab file.
Fixed long ago.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1184178
Title:
[MS-7698,
There is still something wrong here.
The site in question has fixed the issue in response to my query, and
SSL Labs now gives it an A grade:
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com
According to SSL Labs, it supports these two ciphers for TLS 1.2:
Fair enough, I will contact the web site maintainer. However, regarding
this:
>You can override this via command-line, a system config file, or a local
>config file + environment variable pointing to it.
>
>On Ubuntu 20.04 LTS:
>
>man SSL_CTX_get_security_level.3ssl
1) I searched high, low, and
Aha! `curl -v --ciphers 'DEFAULT:@SECLEVEL=1' https://www.toodledo.com/`
works but `curl -v --ciphers 'DEFAULT:@SECLEVEL=2'
https://www.toodledo.com/` fails.
According to
https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_get_security_level.html,
the default security level for the library is 1 if
I may be misunderstanding something, but as far as I can tell this is
not a cipher mismatch problem.
According to
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com, the
site supports TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. According to
"openssl ciphers", openssl supports
Example output:
jik@jik-x1:~$ curl -v https://www.toodledo.com/
* Trying 146.20.52.175:443...
* TCP_NODELAY set
* Connected to www.toodledo.com (146.20.52.175) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile:
Public bug reported:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c
For others with similar problems, I'm keeping my findings up to date
here: https://www.tartley.com/dina-as-otf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340
I succeeded with the process of converting a bitmap font into a vector
format with embedded bitmaps, which Pango will display. It took me hours
to figure out, so for anyone else:
Use fontforge, as described here:
https://gitlab.gnome.org/GNOME/pango/issues/386#note_570411
The gotcha is that once
Thanks for talking me through it Sebastien. Fair enough, I defer to your
experience on that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1861340
Title:
All bitmap
I don't think 'fix released' is the right status.
Could Focal use a slightly older version of Pango, to keep bitmap fonts
working for another 6 months, hoping it becomes clearer how to continue
supporting them going forward?
--
You received this bug notification because you are a member of
So, um, this has been broken since Bionic and still not fixed, despite
the fact that ubuntu-bug is the only supported way for reporting bugs?
This seems highly sub-optimal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'm speculating that pango 1.44 dropping support for bitmap fonts might
be a cause: https://gitlab.gnome.org/GNOME/pango/issues/386
** Package changed: fontconfig (Ubuntu) => pango1.0 (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/pango/issues #386
I semi-guessed at package 'fontconfig' to associate. Advice welcome.
** Package changed: ubuntu => fontconfig (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
I can no longer reproduce it either. *shrug*
P.S. Hi Ted long time no see.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get dist-upgrade -y hangs
Public bug reported:
My recent apt-get dist-upgrade -y hung here:
...
update-initramfs: deferring update (trigger activated)
e2scrub_all.service is a disabled or a static unit not running, not starting it.
I did a pstree on the apt-get process and saw this:
e2scrub_all.timer restarts just fine; it's the e2scrub_reap.service
restart that's hanging.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1860676
Title:
apt-get
Installing ncsd worked well for me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1745664
Title:
[regression] systemd-logind crashed with SIGABRT in
Public bug reported:
On restart it sometimes happens that I get a message to the effect that my
graphics are operating in some kind of limited mode. An Xorg error is
mentioned. On OK I get a few options such as 'try starting in default mode' and
other options involving various possible tests,
Public bug reported:
I imported an openvpn configuration with `nmcli c import type openvpn file
config.ovpn`.
After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
I have
jik@jik5:~$ sudo systemctl is-enabled whoopsie
disabled
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1843630
Title:
ubuntu-bug not opening anything in the browser
** Attachment added: "crashdb.conf"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+attachment/5290988/+files/crashdb.conf
** Changed in: apport (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
After experiencing some "turbulence" in my wifi (I rebooted my primary
wifi router, which caused my laptop to fallback onto a secondary access
point which didn't have full connectivity until the primary router
finished rebooting, then I rebooted the primary router a second
Public bug reported:
Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to
the developers?" with the "Don't send" and "Send" buttons, but when I
click on "Send" nothing happens.
I have the "problem_types" line commented out in
/etc/apport/crashdb.conf, though I don't know if
Public bug reported:
Expected behavior:
Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a
prompt if the original file should be overwritten.
What happened:
After performing an upgrade of package procps IPv4Forwarding was disabled in
/etc/sysctl.conf without asking:
As per http://packaging.ubuntu.com/html/fixing-a-bug.html, I'm directly
including a patch. I've tested this locally and confirmed that these
changes enable debugging RISC-V programs running inside very recent
versions of QEMU. As noted before, it has also already been applied to
the Debian version
Public bug reported:
This issue was recently fixed in Debian, but seems to have not been
pulled into Ubuntu: https://salsa.debian.org/gdb-
team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175
Description:Ubuntu Disco Dingo (development branch)
Release:19.04
gdb-multiarch:
testing on bionic with bionic-proposed enabled
I can successfully install libxcb-xinput-dev and libxcb-xinput0 and they
contain the necessary files. I can install libxcb* and it includes the
same files as before.
** Tags removed: verification-needed-bionic
** Tags added:
So this was caused because I still had "nomodeset" in my grub, which I
had needed for the monitor to work after the initial install. Once I
took it out, everything works fine. Oops.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
I called Lenovo and asked and the support rep I spoke with said that the
X1 Carbon's fingerprint reader isn't supported in Linux yet.
I don't know whether to trust that information as accurate, but that's
what he said.
I don't know whether that's worthy of a separate bug report or not. I
mean,
Public bug reported:
Ubuntu 18.04, Dell Inspiron 14 with Intel graphics. HDMI worked fine
when I had Windows on the machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
As far as I can tell, the BIOS is able to see the fingerprint reader --
I just booted into the BIOS and told it to reset the fingerprint data,
and it said that it had done so successfully -- so this appears to be a
Linux-specific issue.
--
You received this bug notification because you are a
I have a new Thinkpad X1 Carbon 6th generation. I can see the
fingerprint reader right next to the trackpad, and the specs say that it
has one, but I don't see it showing up in the output of lspci or lsusb.
Maybe I'm missing it? Maybe it's not supported? Or maybe there's a
hardware issue? I'm not
So, whether or not I needed to run pam-auth-update, doing so and
enabling fingerprint authentication there should not cause GDM to break,
nor should the other weird behavior I described above be happening.
Having said that, yes, I was trying to enable login with fingerprint. I
googled how to do
Actually, it's even weirder than that.
I went through all this several times while trying to narrow down the
repro steps, and it's all very bizarre. Somehow I managed to get gdm
working again, and then in a logged in gdm session, I enabled
fingerprint, and exited from pam-auth-update, then ran
1 - 100 of 409 matches
Mail list logo
