Public bug reported:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
Public bug reported:
I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor
I know it can't be the problem with the other monitor as
** Patch added: "001-vaes_gcm_avx512.patch"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+attachment/5754726/+files/001-vaes_gcm_avx512.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in
Hello @adrien-n,
I had Dan Zimmerman take a look at this issue and found a solution.
This is what he shared:
Steps to reproduce:
---
Get Source and apply patch:
git clone https://git.launchpad.net/ubuntu/+source/openssl ubuntu_openssl
cd ubuntu_openssl
git checkout
This says fix commited though it seems to be neither available in
mantic-updates nor in noble? This is annoying as we have to resort to
installing 253.5-1ubuntu4 manually from the old repository archives and
prevent updates of it
--
You received this bug notification because you are a member of
Public bug reported:
I have my system set up to rely on GPT auto generator together with
Discoverable Partitions Specification (DPS). After upgrading my system
the gpt generator is no longer included resulting in boot failure.
I have been able to workaround this by setting up the mounts in fstab
Hi @schopin,
Recommended way to test the relevant code paths would be to use OpenSSL’s
Capability Bits Environment variable. Notes below:
Ubuntu - OpenSSL OPENSSL_ia32cap Environment Variable
OpenSSL Environment variable processor feature bit disable combos for testing.
Running `sudo dhclient -6 ` appears to work, the problem
seems to be with the systemd-networkd DHCPv6 client.
--
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/2025382
Title:
Public bug reported:
Ubuntu 22.04.2 LTS
kernel 5.15.0-1038-oracle
systemd 249.11-0ubuntu3.9
After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6
via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also
other similar reports, e.g.
I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected
by default.
I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe
it's related to the blueman update from 2.3.4 to 2.3.5 on
IIRC I tried to install it from source back then, but had missing build
dependencies (or versions) which were not in the package repositories. I
could be wrong, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Hmm, currently when connecting it via blueman it automatically connects with
the last used profile.
I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it
seems to have A2DP there.
But as soon as I change my Mic Input Device to my headphones it changes to
"Headset Head
Hey @vanvugt, is there maybe any ETA?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1988364
Title:
Missing the A2DP profile and defaults to low quality
Status in Bluez
my 5 cents:
```
# apt list --upgradable
Listing... Done
ubuntu-wallpapers-kinetic/kinetic-updates,kinetic-updates
22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1]
ubuntu-wallpapers/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all
[upgradable from: 22.10.2-0ubuntu1]
```
Thanks, good to know :) At least you are listening :P
Do you know about any updates on this topic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1988364
Title:
Missing
Public bug reported:
Recently updated to Ubuntu 22.10 from 22.04 LTS. (kernel - 5.19.0-23)
There is no sound output unless pulseaudio is started manually. No
output devices except dummy output, until pulseaudio is started.
pulseaudio is enabled but is inactive(dead) until it is started using
** Description changed:
- Black areas appear in all gtk2 apps. For example in text fields. After a few
mouse clicks, they may disappear, then reappear. You can see if you open any
app based on gtk2. For example, darksnow.
- I have Ubuntu 22.04.1 LTS.libgtk2.0-0 version: 2.24.33-2ubuntu2
+ Black
Public bug reported:
Black areas appear in all gtk2 apps. For example in text fields. After a
few mouse clicks, they may disappear, then reappear. You can see if you
open any app based on gtk2. For example, darksnow.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgtk2.0-0
The empty blacklist.conf seems to have caused all this.
- CLOSE -
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking
Might i have emptied or removed
/etc/modprobe.d/blacklist.conf
by mistake? It was awfully empty!?
--- pre ---
# https://askubuntu.com/a/67028/289138
$ dpkg -S /etc/modprobe.d/blacklist.conf
kmod: /etc/modprobe.d/blacklist.conf
$ sudo apt install --reinstall -o
Might it be the case that I somehow removed or emptied
/etc/modprobe.d/blacklist.conf ?
--- pre ---
# https://askubuntu.com/a/67028/289138
$ dpkg -S /etc/modprobe.d/blacklist.conf
dpkg -S /etc/modprobe.d/blacklist.conf
$ sudo apt install --reinstall -o
$ journalctl --disk-usage
Archived and active journals take up 624.0M in the file system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at
https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/240553
$ sudo rmmod evbug
[sudo] password for hannu:
$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Another attempt:
$ cat /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf
# https://askubuntu.com/a/1289997
blacklist i2c_nvidia_gpu
Didn't make any difference.
My judgment is that this is NOT a hardware issue, a plain software one
indicated by:
As the flow of dmesg items ends; if I start tapping
Sadly, that wasn't it... still does the same (Only at start from "cold"?
is it?)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black
Current status:
$ grep hda /etc/modprobe.d/blacklist.conf
blacklist snd_hda_codec_realtek
Seems to stop the problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Oh, I DO have sound in the speakers, BT high def (A2DP) audio too...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking
$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller
(rev a1)
*** Is there REALLY Realtek audio hardware in here too?
*** or just a partly initialized driver due to the
$ cat /sys/class/sound/hwC0D0/vendor_name
Realtek
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking cursor in top left
Hmm...
$ cat /sys/class/sound/hwC0D0/chip_name
ALC294
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking cursor in top
--- audio in the output of lshw ---
*-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@:01:00.1
--- seen in dmesg ---
[5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[5.881465] NET: Registered protocol family 38
[9.328954] wlo1: authenticate with 94:18:65:08:59:ae
[9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3)
[9.382307] wlo1:
Thanks for clarifying, that makes sense now.
Actually I just wanted to thank you, if there would be reactions to
comments that would be great for that. But as I'm writing this comment
now I got one other question: In the sidebar I see many people being
listed under "May be notified". And I'm very
But now it looks like a fix is released, no? Sorry, I'm still new to
launchpad and not everything is obvious to me yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1988364
@vanvugt Thank you very much for opening this bug and everyone else for
the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1988364
Title:
Missing the A2DP
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+attachment/5393623/+files/Dependencies.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
Public bug reported:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
Will this also be released for jammy soon?
I'm running into this issue which should be fixed with 5.65:
https://github.com/bluez/bluez/issues/313
** Bug watch added: github.com/bluez/bluez/issues #313
https://github.com/bluez/bluez/issues/313
--
You received this bug notification because
Please close the ticket. I have not seen the issue in later versions of
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1477584
Title:
package rsyslog
Unfortunately that didn't made any change. My
/etc/apparmor.d/usr.bin.redshift now looks like follows.
/usr/bin/redshift {
dbus send bus="system"
path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",
dbus
Which would be?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1948752
Title:
apparmor is logging too many messages
Status in Redshift:
New
Status in apparmor package
Public bug reported:
Whenever I boot up my PC, I turn on the monitor as well. When this
happens, the Intel Mesa graphics loads, and my screen ends up being
small with large pixelated icons. The resolution was capped at 1024x768.
Only after I reboot my PC multiple times without changing the
Hi,
upower 0.99.18 version contains the fix for this. Are there plans to
integrate this version to Ubuntu 20.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1967565
Just realized that my 22.04 installation was still running in WSL1... No
more error after switching to WSL2.
** Summary changed:
- gzip exec format error under WSL
+ gzip exec format error under WSL1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Corrected output:
$ echo $(( 3600 + $(date +%s -d'1970-01-01 00:02:18') ))
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1970105
Title:
Date gives back wrong second
Public bug reported:
In my opinion, the required '1970-01-01 **01**:02:18' below is wrong.
The answer should be 3600 more seconds.
Note: **02:18 is 138 seconds.**
$ man date
...
%s seconds since 1970-01-01 00:00:00 UTC
...
$ date +%s -d'1970-01-01 01:02:18'
138
$ date --version
date (GNU
Thank you for your suggestion. I have reported the issue upstream here:
https://gitlab.freedesktop.org/upower/upower/-/issues/179
** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #179
https://gitlab.freedesktop.org/upower/upower/-/issues/179
--
You received this bug
Public bug reported:
upower takes a really long time (around 1-2 minutes) to detect when an AC
charger is plugged-in.
'upower -d' shows battery state as discharging after AC charger is plugged-in.
'systemctl restart upower.service' would update the status immediately as
charging. Otherwise, it
** Information type changed from Public to Private
** Attachment removed: "Image of printing error"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312547/+files/Screenshot%20from%202019-12-15%2015-07-59.png
** Attachment removed: "CupsErrorLog.txt"
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1958019/+attachment/5554768/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 5091 F pulseaudio
/dev/snd/pcmC1D0p: ubuntu 5091 F...m pulseaudio
/dev/snd/controlC0: ubuntu 5091 F pulseaudio
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1958019/+attachment/5554766/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1958019/+attachment/5554767/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1958019/+attachment/5554764/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1958019/+attachment/5554765/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Alsa-info output saved to a file
** Attachment added: "alsa-info-legion7.txt"
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+attachment/5554763/+files/alsa-info-legion7.txt
** Tags added: apport-collected impish
--
You received this bug notification because you are a member of Ubuntu
Alsa-info output: http://alsa-
project.org/db/?f=ae148d86e41375195a7e401ef0af5d533218f275
--
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/1958019
Title:
[Lenovo
This might be another case of
https://bugzilla.kernel.org/show_bug.cgi?id=208555
** Also affects: sound-2.6 via
https://bugzilla.kernel.org/show_bug.cgi?id=208555
Importance: Unknown
Status: Unknown
** Summary changed:
- [82N6, Realtek ALC287, Speaker, Internal] No sound at all
+
I have the same issue.
I have a Legion 7 16ACHg6 which I'm testing under Ubuntu 20.04.3 LTS and 21.10
LiveUSB, and in both of them there is no sound out of the built-in speakers.
Headphones are working fine though.
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
Hi Daniel,
In my understanding, the crash is not reproducible after my workaround
(switching to the nvidia driver), because the nvidia-resume.service is not
masked (my theory).
Therefore, I switched back to the Nouveau driver, and I reproduced the
problem and collected the system logs as you
Created attachment 143424
New crash information added by DrKonqi
gwenview (20.12.3) using Qt 5.15.2
- What I was doing when the application crashed:
This is a little bizarre. I encountered this while rapidly scrolling
through thumbnails in a directory. One particular image reliably crashes
Interesting update
Given the "Unit nvidia-resume.service is masked" complain by systemd-
logind in my previous comment, I thought it could be related with the
switching on and off the proprietary nvidia driver: after turning it on,
I turned it off (switching to Nouveau)
If I grep for `systemd`, after the first meaningful message:
Nov 10 00:20:06 lenovo systemd-logind[11553]: Power key pressed.
The first error is:
Nov 10 00:20:11 lenovo systemd-logind[11553]: Error during inhibitor-
delayed operation (already returned success to client): Unit nvidia-
Public bug reported:
Unfortunately, this bug does not seem to be fixed yet.
My syslog is flooded with ALLOWED messages regarding redshift.
My system is a Kubuntu 21.04.
AppArmor is V. 3.0.0-0ubuntu7.1
Attached you'll find an excerpt from /var/log/syslog for the last 5
minutes.
** Affects:
Public bug reported:
My Canon MP499 printer is recognized, but if i try to use it in
LibreOffice Writer, a message appears (see above). Using translate, it
shows this message:
Printer cannot be started. Check your printer's configuration
fred@fred-Latitude-E6430:~$ lpstat
** Information type changed from Private to Public
--
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/1856480
Title:
"Could not start printer" message appears when I attempt to
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361003/+files/WifiSyslog.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360989/+files/CRDA.txt
**
** Attachment removed: "ping.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313410/+files/ping.txt
** Attachment removed: "Screenshot of configuring screen and terminal"
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt
** Attachment removed: "NetDevice.enp4s0.txt"
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350596/+files/CRDA.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310884/+files/CRDA.txt
**
** Attachment removed: "my initrd.img"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345796/+files/initrd.img
** Attachment removed: "ProcCpuinfoMinimal.txt"
** Attachment removed: "WifiSyslog.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt
** Attachment removed: "IpAddr.txt"
/rules binary subprocess returned exit
status 2
Expected output:
Should compile successfully
Thanks,
Vijai Kumar K
** Affects: base-files (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Still an issue in 20.04 LTS
--
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/1726124
Title:
DNS domain search paths not updated when VPN started
Status in network-manager
Same problem here (Ubuntu 20.04, i915 driver, Skylake Intel(R) Core(TM)
i7-6500U CPU @ 2.50GHz
) :
- glxgears and vlc both give a black window
- /usr/bin/kcmshell5 kcm_networkmanagementreturns a segfault.
'export MESA_LOADER_DRIVER_OVERRIDE=i965' seems to solve all this. Many
thanks to
On the Debian bug site it shows that adding wifi.hidden yes via "nmcli
connection modify wifi.hidden yes" does seem to produce a solution
but it only works one time. When I did this and restarted network
manager service I had hidden wifi connect once successfully but it
wouldn't do it again
I'm confirming this bug 6 years later is real and unfixed still! The
solution worked for me. Can this be patched ASAP?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
i have no audio from speakers in my laptop but i have audio output on hdmi. i
have another harddrive with windows 7 on it and the speakers work correctly on
that. they used to work on this distro
Description:Ubuntu 20.04 LTS
Release:20.04
ProblemType: Bug
Public bug reported:
tried to reinstall ubuntu-desktop for some mutter problems; some keys
cannot be typed/copied; but it has worsened
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libasound2-plugins 1.2.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux
Sorry for all, "Fix Released" information for status isn't true, it's my
mistake.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1874851
Title:
Unable to remove file
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1874851
Title:
Unable to remove file or
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1874851
Title:
Unable to remove file or
By the way : user.lastnamelastnamelastn...@domain.fr does not trigger
the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865517
Title:
cannot log in with long username
Just retried with fresh download of this file :
http://cdimage.ubuntu.com/daily-live/current/focal-desktop-amd64.iso
I confirm that entering on tty3
username.lastnamelastnamelastn...@domain.fr
(not just "user.")
does trigger the bug.
--
You received this bug notification because you are a
Nothing but i misexplained, bug isn't related to the fact that account exists
or not.
Please try to enter in a tty that exact login :
'username.lastnamelastnamelastn...@domain.fr'
It reset without asking for password, and the error line is added to
auth.log
Then try :
All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let
me reproduce this.
Its more clear on tty, as you see username field resets, but it's the
same from ligthdm
So should i open a bug for agetty package instead ?
--
You received this
Public bug reported:
We use ldap authentication with mail addresses as usernames.
So usernames are not posix and some are > 32 chars but are working.
Some of them fire a bug :
When trying to log, it doesn't asks for password, it just wait some seconds
then reset to ask username.
I can't
** Bug watch added: Red Hat Bugzilla #1763702
https://bugzilla.redhat.com/show_bug.cgi?id=1763702
** Also affects: wget (CentOS) via
https://bugzilla.redhat.com/show_bug.cgi?id=1763702
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Just another data point. I searched Debian packages and there is not an
associated release impacted by this issue.
Debian oldstable (stretch) ships wget 1.18 (pre-regression release). See
https://packages.debian.org/stretch/wget
Debian stable (buster) ships wget 1.20 (regression fixed release).
Public bug reported:
Traditionally (AFAIK for at least the last decade), tools that support
the no_proxy environment variable support specifying an entire subdomain
by prefixing it with a "dot". For example, to exclude any website under
example.com from using the proxy, you would set no_proxy to
Do you know when 1:11.1-1ubuntu7.5 will be re-released?
My update Ubuntu installation has the last version installed on Nov 22, 2019.
Also, my apt package manager doesn't seem to know about "withdrawals" so the
rest of my pulseaudio files remain from 1:11.1-1ubuntu7.5
BTW, I was able to install
Public bug reported:
Running: apt-get install pulseaudio-esound-compat
I get the following error:
The following packages have unmet dependencies:
pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but
1:11.1-1ubuntu7.5 is to be installed
Depends:
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1597840
Title:
package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade:
18.04.3 LTS !, still reproduced, which makes me sad.
As a workaround: `sudo apt-get install resolvconf-admin`
--
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/1688018
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
Thanks Miroslav for opening this bug, two weeks after me opening bug #1846557.
Unfortunately, it took proving that gdb couldn't debug properly _any_ 32-bit
program, not just kernels running on QEMU, in
A fix was released after bug #1848200, reporting the same problem, was
opened.
** Changed in: gdb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
** This bug has been marked a duplicate of bug 1846557
Unable to debug any kernel on i386 qemu machine
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi guys,
any update on this?
Just to be sure, I tried to the Linux kernel 4.19.16 in the same
scenario and I got the same result. I built the kernel with buildroot
and I launched QEMU with:
qemu-system-i386 -kernel bzImage -S -s -append 'nokaslr'
I know it needs an initrd and a hdd img in order
Public bug reported:
Hi,
On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM
(qemu-system-i386) by just doing the following:
> target remote localhost:1234
> b term.c:694
and then, when the
s/closed to/close to/ .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1836328
Title:
unattended-upgrades should not be enabled by default
Status in
1 - 100 of 204 matches
Mail list logo
