Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
No, not fixed. Comment #15 is an example of the problem still. It's 5
years later. Infiniband IPoIB causes this same problem even with the
"fix". 'rmmod ib_ipoib' allows dhcp to start. Having the module loaded
and the interface configured prevents dhcpd from starting due to
apparmor.
--
You recei
Just upgraded to kernel 5.3.0.29-generic and still no sound.
Found a user who compiled his kernel with ALC294 patch and seems to have
gotten his sound working.
His system is the ASUS UX362FA, running Realtek ALC298 (Device: pci
0x9dc8).
Details can be found here: Kernel.org Bugzilla – Bug 203443
Can you try adding the following to
/etc/apparmor.d/local/usr.sbin.dhcpd:
network packet dgram,
And then running
sudo apparmor_parser -rT /etc/apparmor.d/usr.sbin.dhcpd
And see if restart dhcpd then works?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
# apt-cache policy isc-dhcp-server
isc-dhcp-server:
Installed: 4.4.1-2ubuntu6
Candidate: 4.4.1-2ubuntu6
Version table:
*** 4.4.1-2ubuntu6 500
500 http://archive.ubun
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bu
autopilot upload that drops autopilot-qt usage is in progress
https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu5
** Summary changed:
- Please port your package away from Qt 4
+ RM: Please port your package away from Qt 4
** Changed in: autopilot-qt (Ubuntu)
Statu
Thanks for the bug report. I think this is related to a family of
scaling bugs in gnome-shell I've only discovered recently:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/1004
https://gitlab.gnome.org/GNOME/mutter/issues/849
Those are not this bug, but I think it's related whereby display
There's a slight chance these are both kernel bugs, but I think more
likely the laptop has some real hardware faults. Please try a newer
kernel version:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.2/
or maybe easier; please try booting Ubuntu version 18.04 from USB:
https://ubuntu.co
Thanks for the bug report. I can see two separate problems in the
attached files:
--
(1) Connector 86 (the internal laptop screen) is being detected as
unplugged over and over again. This might be a hardware fault or it
might be a kernel bug:
[ 5631.614] (WW) modeset(0): hotplug event:
** No longer affects: cryptsetup (Ubuntu)
** No longer affects: gcc-10 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1861757
Title:
Missing libgcc_s.so.
** No longer affects: systemd (Ubuntu Cosmic)
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu)
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
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.lau
Good to hear.
The Mesa issue seems to have been resolved 12 hours ago.
The remaining Alt-Tab issue seems to be caused by your system settings:
b'org.gnome.desktop.wm.keybindings' b'switch-windows' b"['disabled']"
b'org.gnome.desktop.wm.keybindings' b'switch-windows-backward' b"['disabled']"
So
Looks like Fix Released about 2 hours after comment #5.
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
--
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
You have been subscribed to a public bug:
I don't have the skills to pick apart this mess, sorry.
If there's anything I can do to help debug it give me a shout.
Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-ge
It seems to be caused by fractional display scaling: The display is
configured to use 150% scaling.
When the scaling is set to 100% (native DPI), mpv and Firefox can play
the video in fullscreen without triggering the bug, everything fine just
like it should be.
When the scaling is set to 200%, t
** Description changed:
When I play a video with mpv (or e.g. Firefox), it works just fine.
When this video is fullscreened (e.g. in mpv by pressing f), the screen
quickly turns off, and switches resolution modes in such a rate the
screen is unusable.
The native resolution of the s
Public bug reported:
When I play a video with mpv (or e.g. Firefox), it works just fine.
When this video is fullscreened (e.g. in mpv by pressing f), the screen
quickly turns off, and switches resolution modes in such a rate the
screen is unusable.
The native resolution of the screen is 1440p, b
Public bug reported:
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
If I use xserver-xorg-video-nouveau/focal,now 1:1.0.16-1 amd64
there is no sound on Display port.
My graphic card is GTX 1650.
Please see bug 1859096. It work with 440 nvidia dri
sorry, the description is not very clear - can you provide specific
steps to reproduce this problem?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Thank you for taking the time to file a bug report.
Unfortunately the collected logs don't indicate what the issue with ldap
is. There don't seem to be other reports of this issue, so it appears
not to be a systemic problem. Best guess, lacking better information,
is that there was a local confi
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
** Package changed: ubuntu => systemd (Ubuntu)
--
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/1862044
Title:
packet loss, extra latency and lower bandwidth on bionic
Stat
You can find it here:
https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd?id=1401429&page=2
-
Version: 237-3ubuntu10.23 2019-06-21 00:06:25 UTC
systemd (237-3ubuntu10.23) bionic; urgency=medium
* d/p/resolved-do-not-hit-CNAME-in-NODATA.patch:
- fix stub re
You have been subscribed to a public bug:
We are investigating migrating our servers from Xenial to Bionic.
We are seeing significant network differences between the 2 LTS versions.
Using the same hardware an machines connected to a single swith on the same
network, we see:
10% less packets throu
hi, Eric:
Could you please confirm that this bug had been fixed on ubuntu bionic
with version 237-3ubuntu10.38?
I am confusing about your comment as I found nothing when go through the
update changes
https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd.
--
You received thi
Eoan vmtests for vlan MTU checks now pass:
(neipa) vlan-mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkVlan/logs/install-serial.log
[ 131.271209] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64 242-7ubuntu3.3 [126 kB]
[ 131.281683] cl
@rael-gc is experiencing this issue still with 18.04 on duplicate bug post...
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubun
*** This bug is a duplicate of bug 1642634 ***
https://bugs.launchpad.net/bugs/1642634
I feel your pain 😐
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/16527
Problem resolved 4 Feb, 2020, DLW/w9dki
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1861890
Title:
package initramfs-tools 0.133ubuntu13 failed to install/upgra
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1862054
Title:
package libssl1.1:arm64 1.1.1-1ubuntu2.1~18.04.5 failed to
install/up
We're marking this issue as "Fix Released" for LXC due to the removal of
all those scripts from the standard LXC distribution, instead relying on
distrobuilder for our users to generate custom LXC images (which can
then be consumed by the lxc-local template).
--
You received this bug notification
Yeah, we were originally considering fixing all of the individual
templates but frankly it was just too much of a mess of bad patterns
from a variety of different authors with no real consistency.
Instead what we came up with is distrobuilder
(https://github.com/lxc/distrobuilder) which has now
Public bug reported:
error
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1:arm64 1.1.1-1ubuntu2.1~18.04.5
Uname: Linux 4.9.108-tegra aarch64
ApportVersion: 2.20.9-0ubuntu7.9
AptOrdering: NULL: ConfigurePending
Architecture: arm64
Date: Wed Feb 5 17:53:40 2020
ErrorMessage: in
** Tags added: sru-20200127
--
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/1783881
Title:
ltp-syscalls: msgstress03 fails because systemd limits number of
processes
Sta
New backport uploaded to the queue
** Summary changed:
- [SRU] Backport 2.62.3-2
+ [SRU] Backport 2.62.4-1
--
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/1850932
Title:
** Attachment added: "curtin vmtest logs for vlan mtu issue"
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5325684/+files/bug-1846232-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
I'm able to easily reproduce this in lxc using the steps provided.
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
It looks like the glib2.0/i386 regressions are actually real. I tried
locally and reproduced them. I then tried 2.62.4 and the tests pass
there. So I think I'll rev this SRU.
** Description changed:
[ Description ]
I'm creating this bug report to have a place to describe the proposed
- bac
This bug was fixed in the package systemd - 237-3ubuntu10.38
---
systemd (237-3ubuntu10.38) bionic-security; urgency=medium
* SECURITY UPDATE: local privilege escalation via DynamicUser
- debian/patches/CVE-2019-384x-1.patch: introduce
seccomp_restrict_suid_sgid() for bloc
Public bug reported:
Screen blinking when i try to log in after log off and system become to
slow and also black screen blinking when i try to change resolution
setting in display.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-18.19
With identical setup and testcase for eoan I have managed to
successfully verify the patch with version 242-7ubuntu3.3:
ubuntu@eoan:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare
ubuntu@eoan:~$
** Tags removed: verification-needed-eoan
** Tags added: verificati
I have just verified bionic. With version 237-3ubuntu10.34 after
replaying test case from the description I see the groups from
/etc/security/group.conf (dialout, users) added:
ubuntu@bionic:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf
** Tags removed: verif
Verified 1.3.1-5ubuntu1.19.10.1 on Eoan.
root@ee-proposed:~# login ubuntu
Password:
Last login: Wed Feb 5 15:40:20 UTC 2020 on UNKNOWN
Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-29-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Sup
An update: testing some more, I can confirm that there were improvements on
volume, now it is definetely louder: if it weren't the buzzing effect on the
sound, I could say it was fixed. On the other hand, the louder it gets the more
noticeable the distortion became.
Oh, and I noticed that both
Curtin vmtest verification for bionic using systemd from -proposed has
run successfully.
(neipa) ipv6_mtu % egrep "237-3ubuntu10.34"
output/BionicTestNetworkMtu/logs/install-serial.log
[ 126.923480] cloud-init[1176]: Get:10 http://archive.ubuntu.com/ubuntu
bionic-proposed/main amd64 libsystemd
Curtin vmtest verification for eoan using systemd from -proposed has run
successfully.
(neipa) ipv6_mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkMtu/logs/install-serial.log
[ 136.520219] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64
** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5325665/+files/bug-1671951-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
This bug has sat incomplete for 6 months. Marking invalid.
** Changed in: libreoffice (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net
The patches on
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/pulseaudio.git/log/?h=jejb-v13
might help with this problem
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
** Tags added: sts
** Description changed:
- In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked
- fine:
+ [Impact]
+ ps -o thcount doesn't print out an error (error: unknown user-defined format
specifier "thcount")
+
+ [Description]
+ The Xenial version of procps has a bug
Agreed. yaztromo identified the frustration well. I've been living
with this in Mint Cinnamon for years, and still can't seem to get used
to it. Thanks for the Alt+N shortcut (works in English/US version).
Maybe that'll help me stop cursing at my computer every time I save a
file.
Returning the
*** This bug is a duplicate of bug 1642634 ***
https://bugs.launchpad.net/bugs/1642634
Happened to me on 18.04 (with Unity). To the point that my system got
frozen with indicator-datetime-service consuming 11.5 GB of 16GB RAM.
--
You received this bug notification because you are a member of
Actually the merge of 1.8.4 and the FTBFS are so different - closing the
iptables tasks to live in a different place if needed.
** No longer affects: iptables (Debian)
** Changed in: iptables (Ubuntu)
Status: New => Invalid
** Also affects: strongswan (Ubuntu)
Importance: Undecided
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/strongswan/+git/strongswan/+merge/378566
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1861
Actually this isn't as bad as I first thought, but it can be. Let me
illustrate how/why.
iptables changed its -dev packaging.
Then strongswan adapted by changing iptables-dev to libip4tc-dev + libip6tc-dev.
If strongswan would have stayed as-is it woul still work. But due to
adapting to the forme
There were two issues:
(1) mesa in focal has lower version than in releases, newer one stuck in
proposed
(2) ubuntu-release-upgrader did not check that the solution it picked at
the end (after re-marking meta packages for upgrades) was actually
valid. It assumed that if mark_upgrade() failed, the
The focal version got updated and the new release includes that fix
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Released
--
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.launch
** Changed in: pygobject (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1859610
Title:
python-gi/arm64 segfaults
> Ubuntu release: 18.04.4 LTS
> Package version: systemd 237-3ubuntu10.33
> journalctl --version gives
> systemd 244 (244)
You mention you're running Ubuntu release 18.04.4, which provides
systemd v237, but you appear to be running journalctl v244. Are you
actually running Ubuntu pre-release 20.
Please run this command and tell us what it says:
gsettings get org.gnome.desktop.interface enable-animations
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Public bug reported:
animations not working
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: communit
Public bug reported:
Dummy Output
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
I sure did, running both new kernels didn't fix it.
--
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/1850702
Title:
[Samsung Notebook 7 Pro, Realtek ALC256, headphone ja
Public bug reported:
Ubuntu release: 18.04.4 LTS
Package version: systemd 237-3ubuntu10.33
A simple journalctl command is now giving me this error
Journal file
/var/log/journal/ad9213e031ec2a16399a4251594e/user-1001@ae426ac82df44a8489f745ad63e8c9ea-215f-0005848bb1ab0334.journal
Thanks for the bug report. This appears to be a kernel problem:
!!Soundcards recognised by ALSA
!!-
--- no soundcards ---
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks. Please also run 'uname -a' each time to verify the new kernel is
running.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubu
Note that 0.27.2-8ubutnu1 dropped the previously applied patch for
CVE-2019-17402 which is still required!
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17402
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Just updated to 5.5.2 and got the same results
--
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/1850702
Title:
[Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] H
Public bug reported:
After I updated my ubuntu kernel to 5.0.0-05 my sound system has
some problems. First it showed Dummy Output and i couldn't find my
solution then i got back to my old kernel(4.18.0 -20) hoping it would
remove the problem but now after i hit some commands it shows no
output
The reason that this regression doesn't affect ubuntu-desktop, might be
that unlike LightDM, GDM doesn't have that Ubuntu-specific patch to use
/usr/share/language-tools/language-options.
So, I subscribed "lightdm (Ubuntu)" to the affected packages, in case we
just want to drop the Ubuntu-specific
Public bug reported:
Hi,
I found this by trying to merge a newer strongswan which was an FTFBS.
I wondered what happened and found:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947176
This is exactly my issue and we might face FTBFS in strongswan, systemd
and probably others as well.
The
73 matches
Mail list logo
