Public bug reported:
The 'w' command is not showing most logged in users, output of 'w':
17:10:59 up 6 days, 15:02, 3 users, load average: 2.56, 2.44, 2.20
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
nanook50.251.249.4917:102:50 0.00s 0.02s sshd:
Public bug reported:
This used to work but stopped working with a recent update of `systemd`
in noble:
podman run --privileged -it quay.io/podman/stable sh '-c' "echo -e 'FROM
docker.io/amd64/ubuntu:noble\\nENV DEBIAN_FRONTEND=noninteractive\\nRUN
apt-get -yqq update && apt-get -yqq upgrade && ap
I was able to fix this, or at least I think I fixed it.
when installing sudo apt install gamemode steam
got hit with
dpkg error processing archive
/var/cache/apt/archives/libtheoraenc1_1.2.0~aplha1+dfsg-5_i386.deb (unpack):
trying to overwrite shared ‘/usr/share/doc/libtheoranenc1/changelog.De
** Also affects: firefox-3.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0
*** This bug is a duplicate of bug 445333 ***
https://bugs.launchpad.net/bugs/445333
** This bug has been marked a duplicate of bug 445333
remember password on printing to windows printers does not work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug is back.
When printing and check "remember password" box the password is not stored.
Tested with chromium and firefox. Could be a problem with snap package.
(see https://issues.chromium.org/issues/348206835)
** Bug watch added: issues.chromium.org/issues #348206835
https://issues.chro
This issues is caused by iBus.
So if I use XIM instead of iBus, it eliminate the latency.
** No longer affects: ibus (Ubuntu)
** Project changed: mutter => ibus
** Tags added: ibus
** Changed in: ibus
Importance: Unknown => Undecided
** Changed in: ibus
Status: Unknown => New
** Ch
Public bug reported:
The w command does not calculate idle time properly.
03:23:30 up 25 min, 4 users, load average: 1.07, 0.83, 0.73
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
lightdm -02:59 24:29 0.00s 0.04s lightdm --sessi
nanook
Hello hurelhuyag (hurelhuyag),
If you want to downgrade ibus, first you need to install Ubuntu 24.04 or
older on a virtual machine because you have to use them to download an
older version of ibus and then send it to Ubuntu 24.10 and install and
older ibus version using this command.
sudo dpkg -i
Hello everyone, this bug report post is no longer expired.
Because I found the reason why I'm having keyboard latency every time I
use Ubuntu 24.10 to play games, the answer was ibus version 1.5.30 so
when I downgrade it to 1.5.29 from Ubuntu 24.04 LTS, it just eliminated
the latency.
I hope you
** Package changed: mutter (Ubuntu) => ibus (Ubuntu)
** Changed in: ibus (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2077670
Title:
Thanks for 99-hp-lt4129-test.rules, it works fine on kubuntu 24.04.1!
--
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/1574582
Title:
HP lt4120 Snapdragon X5 LTE USB
Reassigning to xdg-desktop-portal, which is the service you are
contacting via D-Bus. However, there are different backends for this
portal, e.g. xdg-desktop-portal-gtk, xdg-desktop-portal-gnome, xdg-
desktop-portal-kde and I suspect the issue is in the backend you are
using in that it doesn't matc
** Attachment added: "Screenshot from 2024-10-04 14-35-19.png"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+attachment/5824735/+files/Screenshot%20from%202024-10-04%2014-35-19.png
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You rece
Reverifying using the new method:
Installed `sudo apt install libgtk-3-0t64 -t noble-proposed`.
Got source using `apt source gtk+3.0 -t noble-proposed`
Confirmed GTK 3 version installed is 3.24.41-4ubuntu1.2.
Ran test case listed in bug description, confirmed rendering correctly
(see attached sc
Couldn't work out why they aren't updating automatically but manually
installing the .debs shows the issue fixed, thanks!
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Attempted to verify this today but 3.24.41-4ubuntu1.2 is not downloading
from proposed - is it held due to the autopkgtest results above?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpa
Public bug reported:
In Noble a GtkGlArea widget with transparency doesn't show the GTK
widgets beneath it correctly. This was a regression fixed in
https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e
(released in 3.24.42).
Test Case:
Run gdkgears:
$ apt source g
Bug driver 470, Nvidia GTX 650
W dniu 26.02.2024 o 04:06, Craig pisze:
> (In reply to Michael Catanzaro from comment #62)
>> Hi Craig and Thomas (and Emil if you're still around): if you're still
>> encountering problems with NVIDIA graphics, please report new a bug and
>> leave a comment here lin
I didn't see the problem in kubuntu 23.04 either. Bit of experimentation
last night and I see that the audio usually sorts itself out after you
move to another workspace and then return to the one running zoom.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I tested version 23.12.0: same problem.
Thanks in advance for analyzing the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/2037907
Title:
No package 'nss' found
same problem when trying to compile version 24.01.0.
No package 'nss' found
Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS) (Required is at
least version "3.68")
But
sudo apt-get install libnss3
-> libnss3 is already the newest version (2:3.68.2-0ubuntu1.2).
--
You received this b
I also observed this issue on my laptop with 20.04.
I created a patched version in this PPA[1] and it seems the issue is resolved
with the patch mentioned in comment #5.
If anyone can confirm the patched version does help, I'll submit the patch for
SRU.
[1] https://launchpad.net/~robertliu/+arc
Tested 249.11-0ubuntu3.11 on Ubuntu 22.04 (jammy) and system still wait
for network to be configured
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 3
Found link 2
Found link 1
enp2s0: link is not managed by networkd (yet?).
wlp3s0: link is not managed b
Hi Andreas,
Regarding output,
non-human-readable output of uptime is not modified.
I had to modify code flow a little bit to not change upminutes and uphours
after initial calculation in case of "-p", thus I hid it under
if(!human_readable).
Code flow for !human_readable should stay exactly as be
** Description changed:
- [IMPACT]
+ [ Impact ]
- uptime will provide incorrect data after 52 weeks. This is at least confusing
for users utilizing this tool.
- Issue is already fixed in upstream
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
+ uptime -
Added new debdiffs, updated bug description.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2035061
Title:
uptime -p reports incorrect output after 52 weeks
Status in proc
** Patch added: "focal debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5701220/+files/uptime_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.l
History is a little bit tricky, patch
hhttps://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749
(applied in current debdiff) was merged to the master branch but probably was
lost while repository was moving to a "newlib".
Last released version https://gitlab.com/proc
** Description changed:
[IMPACT]
uptime will provide incorrect data after 52 weeks. This is at least confusing
for users utilizing this tool.
Issue is already fixed in upstream
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
Latest procps release
Thanks Paride for feedback.
1.
Old calculation is a little bit wrong.
It assumes that we have 52 weeks in the year - which is 60*60*24*7*52 ->
31449600 seconds
(31449600 - 1) will result in 51 weeks, 31449600 will result in 0 weeks (it is
assuming year has passed).
However year calculation is dif
debdiff with backport for focal
** Patch added: "uptime_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5699853/+files/uptime_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
debdiff with backport for jammy
** Patch added: "uptime_jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5699852/+files/uptime_jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
** Changed in: procps (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: procps (Ubuntu Fo
Public bug reported:
[IMPACT]
uptime will provide incorrect data after 52 weeks. This is at least confusing
for users utilizing this tool.
Issue is already fixed in upstream
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
Latest procps releases already inc
FYI, if a user has a 22.04 install where they have explicitly removed
snapd/firefox this will add them back. Not sure if this was a
consideration in the fix/testing.
Also, the apt resolver is pulling in snapd while holding ubuntu-desktop
back during staging which made finding the cause of the sna
Public bug reported:
There is either "dummy" output or it claims the headphones are plugged
in and it is unable to output to the speakers, randomly when rebooting
or walking up from suspend. Usually there is no sound, but maybe once
in several tries it works.
The sound worked fine in the previou
Frequent error message for years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1743029
Title:
glib-pacrunner assert failure: *** Error in `/usr/lib/glib-
netwo
I am affected by this bug for a Xerox B230, I'd the printer is shut off
and restart. Deleting the certificate fixes it.
--
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/1973441
T
Should be this change: Fixed default color settings for CMYK printers as
well (Issue #500)
--
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/1971242
Title:
printing PDF appears
It is not fixed with cups 2.4.1
(https://github.com/OpenPrinting/cups/issues/421).
But should be fixed with cups 2.4.3
(https://github.com/OpenPrinting/cups/pull/500).
Ubuntu 22.04 LTS has cups 2.4.1 (cups-config --version)
--
You received this bug notification because you are a member of Ubun
Correct, this fix is valuable for core22, so kinetic was skipped. There
should be no issues for anyone updating from jammy to kinetic. Though
this will affect core20, we expect most snaps to be using core22 so no
plan to backport it to focal.
--
You received this bug notification because you are
Yes, these specific steps performed in a core desktop VM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not aware of snap confinement
Status in glib2
Public bug reported:
Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1
ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: wl
Public bug reported:
After upgrade from 22.10 to 23.04, adding network printer to cups does
not work until disabling avahi-daemon
Network printer is detected, the name can be entered, but instead of the driver
list an error message that the driver list cannot be loaded appears. The cups
error_l
I tested a standard jammy desktop in a VM by running various apps
including calculator to confirm they were still working (i.e. looking
for regressions).
I tested the core desktop behaviour by building the core22-desktop snap
from https://github.com/canonical/core-base-desktop/ (locally modified
t
I've looked at the autopkgtests and the failures don't seem to be
related to this change.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not aware of s
Tested glib2.0 2.72.4-0ubuntu2 in a jammy VM and working.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu
Hi Oliver,
Thanks for the explanation and the PR.
--
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/2012563
Title:
unsupported mount options: 'nofail', 'nostrictatime', 'la
You're welcome!
On Wed, Apr 12, 2023 at 7:47 AM Rishab raju <2007...@bugs.launchpad.net>
wrote:
> Robert Pearson,
> Man it worked after i did as you said.Thanks for the assist. Truely
> thankful.
>
> --
> You received this bug notification because you are subscribed
Hi Oliver,
Could you please add the options listed in comment #1 as well? They are
used by FunctionFS. Thank you.
--
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/2012563
Ti
Rishabraju,
Boot into your BIOS screen (DEL or F2). Select your drive. When the GRUB menu
opens, select Advanced Features. You should then see a list of available
kernels. Select 5.19.0-32-generic (the later kernels are broken.
After you sign in, open the Audio setting, select HDMI hardware, and
Interesting. That indicates that the code is "fragile", not robust. I'm
glad you finally got your systems to recognize the speakers. Do they work?
In my system, it recognized the HDMI audio output, it just does not work.
Testing the speakers gives the sound of silence. I'm back to
5.19.0-32-generic
** Changed in: glib2.0 (Ubuntu Kinetic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1998267
Title:
glib not aware of snap confinement
S
** Description changed:
[ Impact]
glib is not aware of snap confinement and this causes the internal logic
to decide when to use portals to not work as designed. One important
case is the gsettings backend, which should use a keyfile when confined
rather than using dconf. When using a
Will Ubuntu fix kernel 5.19.0-35 or just do another update with a
working kernel?
--
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/2007913
Title:
HDMI Output sound has d
first time that I have gotten a work-around for defective code
since I started using Ubuntu MATE.
Robert Pearson
On Tue, Mar 7, 2023 at 4:20 PM William <2007...@bugs.launchpad.net>
wrote:
> You select your kernel in the grub boot menu. There is an option for
> alternative boot configuratio
"Booting with linux-image-5.19.0-21-generic lists the audio
devices again."
So how do I do that?
On Tue, Mar 7, 2023 at 5:20 AM William <2007...@bugs.launchpad.net>
wrote:
> Booting with linux-image-5.19.0-35-generic appears to be the problem in
> 22.10. Booting with linux-image-5.19.0-21-generi
This leaves those of us with AMD processors out in the cold. Should I
roll back to Ubuntu MATE 18.04 for a working system until you fix your
update bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
ht
When I run lspci it lists
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP
Audio Controller.
The latest update to Ubuntu MATE 22.04 just ignores it.
In the control center/sound/output it only sees the IEC958 built-in
audio digital stereo.
--
You received this bug not
My system is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Video and audio
output are via HDMI.
As soon as I installed the latest update to Ubuntu MATE 22.04 the audio
broke. When I went to the control center, the entry for HDMI audio
wasn't there.
Apparently, the coder assumed everybody was using
I installed the updated version on the platform which needs this patch.
After updating the packages, the platform can scan and connect to a WiFi
network correctly.
I also tried other amd64, armhf and arm64 platforms which don't require
the patch originally and their wifi device still work after up
Public bug reported:
The version of libglib2.0-dev that is currently included in the
repositories for Ubuntu is 2.72.1-1, which is outdated and missing
important features and bug fixes. In particular, the
G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is not
available in this ver
** Description changed:
- When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
- an AP.
+ [ Impact ]
+ When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not
able connect to an AP.
- I tried a different libnl3 from BSP and found that WCN3980 can work
This package fixes the bug for me, thank you very much :)
Tested version:
libsasl2-modules:amd642.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ub
this issue was discovered in an OEM project.
** Package changed: libnl3 (Ubuntu) => oem-priority
** Changed in: oem-priority
Assignee: (unassigned) => Robert Liu (robertliu)
** Also affects: libnl3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
** Tags added: orignate-from-lp1998578
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1998765
Title:
libnl3 3.4.0 doesn't work with WCN3980
Status in libnl3 package in Ubu
I made a test build (debdiff attached) and tried it on the target
device. This version works correctly.
** Patch added: "libnl3_3.4.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1998765/+attachment/5634558/+files/libnl3_3.4.0-1ubuntu1.debdiff
--
You received this
Public bug reported:
When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
an AP.
I tried a different libnl3 from BSP and found that WCN3980 can work
correctly. The version used in BSP is 3.5.0.
I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root
c
Public bug reported:
Did not install
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnih-dbus1 1.0.3-6ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90
ApportVersion: 2.20.1
Public bug reported:
Did not install
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnih-dbus1 1.0.3-6ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_15_0_48_54_generic_90
ApportVersion: 2.20.1
.
[ Where problems could occur ]
- New bug introduced in glib causing a crash.
- Security issue introduced in glib due to accessing snapctl.
- Unexpected behaviour change when running snaps with updated glib.
** Affects: glib2.0 (Ubuntu)
Importance: High
Assignee: Robert Ancell (rob
rtance: Undecided => High
** Changed in: glib2.0 (Ubuntu Jammy)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: glib2.0 (Ubuntu Kinetic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: glib2.0 (Ubuntu Lunar)
Assignee: (unassi
Investigated this, it is due to the theming code failing to get a
settings object, probably due to the shell not running at the time. The
GTK functions that return the settings object are allowed to return
NULL, and this case was not being handled in GTK. The attached patch
contains three fixes in
Here's a quick-and-dirty temporary workaround:
It uses a post-up hook to remove DOMAINS=DOMAINS from the systemd-
resolved state files if it ends up there. Put it in /etc/network/if-
up.d/zzz-fix-domains
```
#!/bin/sh
statedir=/run/systemd/resolve/netif
grep -rl DOMAINS $statedir | xargs -r perl
Thanks for fixing this - 1.10-4ubuntu4.1 works!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1966849
Title:
gzip exec format error under WSL1
Status in gzip:
New
Status
This bug is a bit of a placeholder at the moment - we'll get this landed
into kinetic first and then update this to SRU the change back to the
older releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties
** Also affects: software-properties (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1990448
Title:
Public bug reported:
Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of
just Livepatch.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Affects: software-properties (Ubuntu Bionic)
Importance: Undecided
Status: New
Same here, recent upgrade message appears.
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in syst
Installed systemd 249.11-0ubuntu3.6 on a jammy VM and confirmed
everything working as expected, thanks!
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
For people having this is issue on AKS clusters with custom DNS...
We have done this on all affected nodepools:
$ VMSS=XXX-vmss
$ nodeResourceGroup=XXX-worker
$ az vmss list-instances -g $nodeResourceGroup -n $VMSS --query "[].id"
--output tsv | az vmss run-command invoke --scripts "systemd-reso
Solved by executing amixer -q -D pulse sset Master toggle
https://askubuntu.com/a/1341471
--
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/1888598
Title:
Pulseaudio break
Public bug reported:
I have a 5 monitor setup. Below is the xrandr account of the monitors:
xrandr --listmonitors
Monitors: 5
0: +*DisplayPort-0 1920/509x1080/286+0+1124 DisplayPort-0
1: +HDMI-0 1920/477x1080/268+1920+1080 HDMI-0
2: +DVI-1 1920/519x1200/324+3840+1110 DVI-1
3: +DVI-I-1-1 16
** Description changed:
- When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink
- to /etc/writable/localtime (which in itself if a symlink). Systemd
- doesn't handle this correctly when doing firstboot or using inotify to
- watch for changed to localtime.
+ [Impact]
+ When using
Public bug reported:
When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink
to /etc/writable/localtime (which in itself if a symlink). Systemd
doesn't handle this correctly when doing firstboot or using inotify to
watch for changed to localtime.
** Affects: systemd (Ubuntu)
Nvidia 3090 on an Alienware R10: boots normally, but the desktop appears as
shades of bright green.
It was corrected when I followed Andrii's solution in comment #28.
Thank you Andrii, you just saved me a bunch of time.
I had already tried the Live USB and installed 22.04 on my Gigabyte
Aorus X
Ugh, turns out I don't need to SRU these back to focal - we will be
using Ubuntu Core 22 which already includes these changes. Sorry for the
noise.
** Changed in: shadow (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: adduser (Ubuntu Focal)
Status: In Progress => Won'
** Description changed:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group us
I realized after generating the debdiffs that I didn't have the bug
number in the changelog - this is fixed in the version uploaded to
focal.
** Changed in: adduser (Ubuntu Focal)
Status: New => In Progress
** Changed in: shadow (Ubuntu Focal)
Status: New => In Progress
** Descript
** Patch added: "adduser.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595790/+files/adduser.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://b
** Patch added: "shadow.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595787/+files/shadow.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bug
LP: #195375 adds extrausers groups support to the usermod command, this
SRU adds support to gpasswd (which is used by useradd).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
[Impact]
When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:
$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user
[Test Plan]
1.
Promotion from -proposed sure would be nice. I see verification has
been done but a update excuses shows an netplan.io regression[1]. I'm
not sure if the test is flaky but I see that seb retried it a few
times[2] last week and it failed consistently, so maybe not.
I'm just curious if there's any
Thank you Seb, I had the issue reported in this bug in a WeWork today
(first time connecting since updating to Jammy) and the package in
-proposed resolved the issue for me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Chiming in that it'd be great if this (gzip-1.10-4ubuntu4) continued to
work in WSL1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1966849
Title:
gzip exec format error und
This is affecting me as well after an upgrade to 22.04 (Ubuntu Mate.)
Previous install, fully-patched 20.04, was rock solid. Now I am lucky if
I get 90seconds of internet access without a disconnection. My whole
house runs on wifi -- sadly, no hardwired options. All other
computers/phones have no i
Public bug reported:
My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB
2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7
Bluetooth "keyboard".
The Bluetooth manager finds the K480 but pairing always fails. The
keyboard flashes blue but dongle steady blue.
Note to self to update the PPA with this change re-enabled once this
lands.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965993
Title:
Remove Ubuntu Pro set
1 - 100 of 1016 matches
Mail list logo
