[Bug 2061245] Re: Ubuntu 24.04 - GNOME on Xorg session crashes on launch
I'm having the same xorg crash problem on Xubuntu 24.04 beta, see #2061246 (dup'ed to here.) I can reproduce the problem with a Ubuntu 24.04 beta install, but there xorg always crashes, unlike the Xubuntu/xfce4 flavor where the first login after booting fails but trying again immediately will succeed. There's some crash info left in Xorg.0.log, I'll attach it. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061245/+attachment/5764900/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061245 Title: Ubuntu 24.04 - GNOME on Xorg session crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow
*** This bug is a duplicate of bug 1869629 *** https://bugs.launchpad.net/bugs/1869629 ** This bug has been marked a duplicate of bug 1869629 please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869632 Title: AppArmor profile denied access to /etc/mdns.allow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
This problem is indeed somewhat pervasive, I also filed bug 1869632 on cups-browsed doing the same thing, for the same reason. I suspect more will pop up. I don't think libnss_mdns is too widely used, most people would use libnss_mdns_minimal. I only have to use libnss_mdns because my ISP is insane. If this bug were fixed by adding /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns bug 1869632 would be fixed as well (I've verified this by patching it on my system.) Not sure why /etc/apparmor.d/abstractions/mdns contains /etc/nss_mdns.conf, though: libnss_mdns.so.2 doesn't refer to that file (it appears to be used in the NetBSD implementation?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869632] Re: AppArmor profile denied access to /etc/mdns.allow
Bug also exists in package version 1.27.3-1 (current version in focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869632 Title: AppArmor profile denied access to /etc/mdns.allow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869632] [NEW] AppArmor profile denied access to /etc/mdns.allow
Public bug reported: Many messages in syslog audit: type=1400 audit(1585521672.468:40): apparmor="DENIED" operation="open" profile="/usr/sbin/cups-browsed" name="/etc/mdns.allow" pid=1323 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is caused by configuring libnss-mdns to resolve local names, with /etc/nsswitch.conf containing hosts: files mdns [NOTFOUND=return] dns myhostname libnss-mnds reads /etc/mdns.allow to find which domains to resolve, but /etc/apparmor.d/usr.sbin.cups-browsed does not allow access. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups-browsed 1.25.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CupsErrorLog: CurrentDesktop: XFCE Date: Sun Mar 29 15:48:11 2020 InstallationDate: Installed on 2019-10-24 (157 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_c53lph@/vmlinuz-5.3.0-42-generic root=ZFS=rpool/ROOT/ubuntu_c53lph ro quiet splash SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869632 Title: AppArmor profile denied access to /etc/mdns.allow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869629] Re: AppArmor denied access to /etc/mdns.allow to cronyd
As a workaround, hanging /etc/apparmor.d/local/usr.sbin.chronyd to include /etc/mdns.allow r, and reloading with sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.chronyd made it shut up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: AppArmor denied access to /etc/mdns.allow to cronyd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1869629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869629] [NEW] AppArmor denied access to /etc/mdns.allow to cronyd
Public bug reported: Many repetitions of audit: type=1400 audit(1585517168.705:63): apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow" pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r" fsuid=123 ouid=0 in log. I use libnss-mdns for .local name resolution, so /etc/nsswitch.conf contains hosts: files mdns [NOTFOUND=return] myhostname dns and /etc/mnds.allow contains the domains to resolve with mDNS (in may case, "local." and "local"; see /usr/share/doc/libnss-mdns/README.html.) Presumably cronyd calls a gethostbyX() somewhere, thus eventually trickling down through the name service switch and opening /etc/mdns.allow, which the AppArmor profile in the chrony package does not allow. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chrony 3.5-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Sun Mar 29 15:02:39 2020 InstallationDate: Installed on 2020-03-26 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chrony UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - AppArmor denied accss to /etc/mdns.allow to cronyd + AppArmor denied access to /etc/mdns.allow to cronyd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: AppArmor denied access to /etc/mdns.allow to cronyd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1869629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867036] Re: Focal Fossa : chronyd unable to sync system clock
Looking into this, it seems the problem is that /usr/lib/systemd/scripts /chronyd-starter.sh expects to be able to check for the cap_sys_time capability by grepping the output of "capsh --print" for "^Current.*cap_sys_time". However, in Focal the output of "capsh --print" for a root process is just "Current: =ep". I suspect this is a linux kernel tools change, as on an eoan system with linux 5.3.0, "sudo capsh --print" has all the capabilities listed in Current:, which is what the starter script expects. andol's dropin makes capsh output "Current: =ep cap_sys_time+i" which the grep matches so all is fine. Not sure that's the right fix, though. (It would help if I knew what "Current: =ep" is supposed to mean. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867036 Title: Focal Fossa : chronyd unable to sync system clock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1867036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
ExecStart twice is what I meant (this is the way to replace the command from the base definition instead of adding another command to the list, see the systemd.unit man page for details.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
No, ExecStart twice is correct. This is the way systemd overrides work; normally a value for a keyword adds to the list of values from the base .service definition. I don't want that, I want to replace it. The special ExecStart= with no value tells systemd to reset the base value to empty, then the second one starts a new list thus replacing the old command. (This is all explained in the systemd.unit man page.) I should tell you that I no longer use this workaround, since after a fair amount of working with and investigating ureadahead (I thought I might actually contribute a permanent fix) I decided that ureadahead is useless in my configuration, since I only reboot after a kernel update anyway, and ureadahead only can ever help on the second and subsequent boots of the same config (most any changes to /etc will cause ureadahead to rescan at the the next boot.) So I have just purged ureadahead on all my systems. On Sat, Sep 29, 2018 at 5:39 AM midenok <1579...@bugs.launchpad.net> wrote: > > Why it contains ExecStart 2 times? > > [Service] > ExecStart= > ExecStart=/sbin/ureadahead -q > > Did you mean ExecStop? > > [Service] > ExecStop= > ExecStart=/sbin/ureadahead -q > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1579580 > > Title: > ureadahead reports relative path errors in journalctl output > > Status in ureadahead package in Ubuntu: > Confirmed > > Bug description: > ureadahead reports relative path errors in my journalctl output. > > This is currently 4368 lines of useless annoyances in my logs. > > To see if you have this problem, run: journalctl -b | grep ureadahead > | grep relative | wc -l > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ureadahead 0.100.0-19 > ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > Date: Sun May 8 15:55:18 2016 > InstallationDate: Installed on 2016-04-04 (34 days ago) > InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 > (20160325) > ProcEnviron: >TERM=linux >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: ureadahead > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Be aware the messages will come back next time you boot after upgrading a package that touches something in /etc, which will trigger another scan by ureadahead. Better is the workaround I gave back in #9, but really what I recommend is just purge ureadahead. ureadahead only ever can help the second (and subsequent) time one boots after updating the system, and these days I never reboot unless I have updated, since suspend works for desktops/laptops and who reboots servers if you don't have to? Rich On Sat, Sep 22, 2018 at 8:54 AM Anders Hall wrote: > > Thanks, workaround in #19 seem to have removed (thousands of) these > messages. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1579580 > > Title: > ureadahead reports relative path errors in journalctl output > > Status in ureadahead package in Ubuntu: > Confirmed > > Bug description: > ureadahead reports relative path errors in my journalctl output. > > This is currently 4368 lines of useless annoyances in my logs. > > To see if you have this problem, run: journalctl -b | grep ureadahead > | grep relative | wc -l > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ureadahead 0.100.0-19 > ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > Date: Sun May 8 15:55:18 2016 > InstallationDate: Installed on 2016-04-04 (34 days ago) > InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 > (20160325) > ProcEnviron: >TERM=linux >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: ureadahead > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587204] Re: Spams motd with "proxy ... looks invalid"
Similarly, I have set in apt.conf.d Acquire::https::Proxy "DIRECT"; (because apt-cacher-ng can't cache https) and I get proxy 'DIRECT' looks invalid The regexp definitely needs to be broadened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587204 Title: Spams motd with "proxy ... looks invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1587204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 605300] Re: ureadahead man page does not include exit status
** Tags added: manpage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605300 Title: ureadahead man page does not include exit status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/605300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
/sbin/ureadahead is writing out warnings every time it gets a relative path from debugfs. This seems excessively wordy, but putting a -q on the ExecStart in ureadahead.service would shut it up. I did a systemd drop-in as a workaround by creating /etc/systemd/system/ureadahead.service.d/quiet.conf containing [Service] ExecStart= ExecStart=/sbin/ureadahead -q -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984474] Re: initctl crashed with SIGABRT in nih_error_clear()
I had what appears to be a variant of this problem on a machine upgraded from Lucid; selecting logoff/restart from the unity bar resulted in no restart, and after manual restart an initctl crash was reported. Installing the proposed change seems to have fixed it, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984474 Title: initctl crashed with SIGABRT in nih_error_clear() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/984474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
