[Bug 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
Important context from https://lists.debian.org/debian-security- announce/2024/msg00057.html : Andres Freund discovered that the upstream source tarballs for xz-utils, the XZ-format compression utilities, are compromised and inject malicious code, at build time, into the resulting liblzma5 library. Right now no Debian stable versions are known to be affected. Compromised packages were part of the Debian testing, unstable and experimental distributions, with versions ranging from 5.5.1alpha-0.1 (uploaded on 2024-02-01), up to and including 5.6.1-1. The package has been reverted to use the upstream 5.4.5 code, which we have versioned 5.6.1+really5.4.5-1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059417 Title: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874938] Re: SyntaxWarning at install
I'm seeing much more than that, installing on noble:
Setting up onboard (1.4.1-5ubuntu2) ...
/usr/lib/python3/dist-packages/Onboard/Appearance.py:924: SyntaxWarning:
invalid escape sequence '\w'
_key_ids_pattern = re.compile('[\w-]+(?:[.][\w-]+)?', re.UNICODE)
/usr/lib/python3/dist-packages/Onboard/Appearance.py:1066: SyntaxWarning:
invalid escape sequence '\w'
key_ids = [x for x in re.findall('\w+(?:[.][\w-]+)?', text) if x]
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:98: SyntaxWarning:
invalid escape sequence '\('
self._layout_regex = re.compile("([^\(]+) (?: \( ([^\)]*) \) )?",
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
/usr/lib/python3/dist-packages/Onboard/SpellChecker.py:324: SyntaxWarning:
invalid escape sequence '\s'
SPLITWORDS = re.compile("[^-_\s]+", re.UNICODE|re.DOTALL)
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:144: SyntaxWarning:
invalid escape sequence '\s'
strings = re.split('(\s+)', context)
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:161: SyntaxWarning:
invalid escape sequence '\s'
"""
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:291: SyntaxWarning:
invalid escape sequence '\s'
_growth_sections_pattern = re.compile("[^\s?#@]+", re.DOTALL)
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:447: SyntaxWarning:
invalid escape sequence '\['
"^In \[[0-9]*\]: ", # ipython
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:450: SyntaxWarning:
invalid escape sequence '\?'
"^\?",# vi reverse search
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:451: SyntaxWarning:
invalid escape sequence '\$'
"\$ ",# generic prompt
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:459: SyntaxWarning:
invalid escape sequence '\('
"^\(.*\)`.*': ", # bash incremental search
/usr/lib/python3/dist-packages/Onboard/TextDomain.py:739: SyntaxWarning:
invalid escape sequence '\w'
_url_pattern = re.compile("([\w-]+)|(\W+)", re.UNICODE)
/usr/lib/python3/dist-packages/Onboard/WordSuggestions.py:1253: SyntaxWarning:
invalid escape sequence '\S'
_section_begin_pattern = re.compile("\S*\s*$")
/usr/lib/python3/dist-packages/Onboard/WordSuggestions.py:1254: SyntaxWarning:
invalid escape sequence '\S'
_section_end_pattern = re.compile("\S*(?=\s*)")
/usr/lib/python3/dist-packages/Onboard/pypredict/lm_wrapper.py:302:
SyntaxWarning: invalid escape sequence '\s'
""" .*?
/usr/lib/python3/dist-packages/Onboard/pypredict/lm_wrapper.py:368:
SyntaxWarning: invalid escape sequence '\s'
tokenize_pattern = """
/usr/lib/python3/dist-packages/Onboard/pypredict/lm_wrapper.py:467:
SyntaxWarning: invalid escape sequence '\w'
if not re.match("""
/usr/lib/python3/dist-packages/Onboard/pypredict/lm_wrapper.py:504:
SyntaxWarning: invalid escape sequence '\d'
result = re.search("ngram (\d+)=\d+", line)
/usr/lib/python3/dist-packages/Onboard/pypredict/lm_wrapper.py:624:
SyntaxWarning: invalid escape sequence '\w'
target_word = re.search("^([\w]|[-'])*", prefix_to_end, re.UNICODE).group()
/usr/lib/python3/dist-packages/Onboard/utils.py:151: SyntaxWarning: invalid
escape sequence '\d'
"""
/usr/lib/python3/dist-packages/Onboard/utils.py:220: SyntaxWarning: invalid
escape sequence '\s'
pattern = re.compile('>\n\s+([^<>\s].*?)\n\s+\g<1>https://bugs.launchpad.net/bugs/1874938
Title:
SyntaxWarning at install
To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1874938/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056595] Re: Lot of SyntaxWarning messages for rhythmbox
Same here:
Setting up rhythmbox-plugins (3.4.7-2ubuntu2) ...
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
[...]
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056595
Title:
Lot of SyntaxWarning messages for rhythmbox
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2056595/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059059] [NEW] Problem with -fno-stack-clash-protection flag on armhf
Public bug reported:
This concerns libdpkg-perl 1.22.4ubuntu5 in Ubuntu noble.
In /usr/share/perl5/Dpkg/Vendor/Ubuntu.pm, there is this bit:
# Debian enables -fstack-clash-protection but it causes troubles on armhf
# (which are not fully analyzed as of writing this); disable it there in
# order to have time to investigate
if ($arch eq 'armhf') {
# Stack clash protector only available on amd64 and arm.
$flags->set_feature('hardening', 'stackclash', 0);
}
Then in /usr/share/perl5/Dpkg/Vendor/Debian.pm, this logic:
# Stack clash
if ($flags->use_feature('hardening', 'stackclash')) {
my $flag = '-fstack-clash-protection';
$flags->append($_, $flag) foreach @compile_flags;
} else {
my $flag = '-fno-stack-clash-protection';
$flags->append($_, $flag) foreach @compile_flags;
}
Which causes -fno-stack-clash-protection to be added to the package
build flags.
Unfortunately, in building Chromium for armhf on noble, I see this
(build log excerpt):
[27780/60083] CXX
obj/net/third_party/quiche/quiche/qpack_decoder_stream_receiver.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27781/60083] CXX
obj/net/third_party/quiche/quiche/qpack_encoder_stream_receiver.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27782/60083] CXX
obj/net/third_party/quiche/quiche/qpack_decoder_stream_sender.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27783/60083] CXX
obj/net/third_party/quiche/quiche/qpack_index_conversions.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27784/60083] CXX
obj/net/third_party/quiche/quiche/qpack_encoder_stream_sender.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27785/60083] CXX obj/net/third_party/quiche/quiche/qpack_encoder.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27786/60083] CXX
obj/net/third_party/quiche/quiche/qpack_instruction_decoder.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27787/60083] CXX obj/net/third_party/quiche/quiche/qpack_header_table.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27788/60083] CXX
obj/net/third_party/quiche/quiche/qpack_instruction_encoder.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
[27789/60083] CXX obj/net/third_party/quiche/quiche/qpack_instructions.o
clang++-16: warning: argument unused during compilation:
'-fno-stack-clash-protection' [-Wunused-command-line-argument]
Basically, *every* invocation of the C or C++ compiler gives this
warning.
I think the flag needs to be dropped altogether for armhf, not just
negated.
** Affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Tags: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059059
Title:
Problem with -fno-stack-clash-protection flag on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2059059/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056302] Re: tar(1) on noble gives EPERM [Operation not permitted] errors when extracting symlinks
Tracked down the cause to the Docker host, which runs on jammy, not knowing about fchmodat2(). The syscall should normally return ENOTSUP when called with AT_SYMLINK_NOFOLLOW on Linux, but the Docker seccomp profile causes it to return EPERM, which confuses tar(1). Closing. ** Changed in: tar (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056302 Title: tar(1) on noble gives EPERM [Operation not permitted] errors when extracting symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2056302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056302] [NEW] tar(1) on noble gives EPERM [Operation not permitted] errors when extracting symlinks
Public bug reported:
This concerns tar 1.35+dfsg-3 in Ubuntu noble. This does NOT affect tar
1.34+dfsg-1.2ubuntu1.1 in mantic.
I'm seeing errors like this:
$ tar xvJf /extern/source/chromium_122.0.6261.111.orig.tar.xz --wildcards
chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca\*
chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca
tar: chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca: Cannot
change mode to rwxr-xr-x: Operation not permitted
(I am running this in a noble Docker container environment, and the
command is extracting into normal user file space.)
This is what strace shows:
23symlinkat("utils/cca.py", AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca") = 0
23utimensat(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca", [UTIME_OMIT,
{tv_sec=1709684076, tv_nsec=0} /* 2024-03-06T00:14:36+ */],
AT_SYMLINK_NOFOLLOW) = 0
23newfstatat(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca",
{st_mode=S_IFLNK|0777, st_size=12, ...}, AT_SYMLINK_NOFOLLOW) = 0
23fchmodat2(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca", 0755,
AT_SYMLINK_NOFOLLOW) = -1 EPERM (Operation not permitted)
The fchmodat(2) man page has the following verbiage:
AT_SYMLINK_NOFOLLOW
If pathname is a symbolic link, do not dereference it: instead
operate on the link itself. This flag is not currently imple‐
mented.
For comparison, this is what happens on mantic:
24symlinkat("utils/cca.py", AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca") = 0
24utimensat(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca", [UTIME_OMIT,
{tv_sec=1709684076, tv_nsec=0} /* 2024-03-06T00:14:36+ */],
AT_SYMLINK_NOFOLLOW) = 0
24newfstatat(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca",
{st_mode=S_IFLNK|0777, st_size=12, ...}, AT_SYMLINK_NOFOLLOW) = 0
24openat(AT_FDCWD,
"chromium-122.0.6261.111/ash/webui/camera_app_ui/resources/cca",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = 3
24newfstatat(3, "", {st_mode=S_IFLNK|0777, st_size=12, ...}, AT_EMPTY_PATH)
= 0
24close(3) = 0
** Affects: tar (Ubuntu)
Importance: Undecided
Status: New
** Tags: noble
** Summary changed:
- tar(1) gives EPERM errors when extracting symlinks
+ tar(1) on noble gives EPERM [Operation not permitted] errors when extracting
symlinks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056302
Title:
tar(1) on noble gives EPERM [Operation not permitted] errors when
extracting symlinks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2056302/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056231] Re: Error when installing nvidia-utils-535: "Invalid cross-device link"
Seeing some strange "Device or resource busy" errors on the /usr/bin/nvidia-debugdump file, seemingly due to Nvidia lossage. Closing as likely unrelated to the packaging. ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056231 Title: Error when installing nvidia-utils-535: "Invalid cross-device link" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2056231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056231] [NEW] Error when installing nvidia-utils-535: "Invalid cross-device link"
Public bug reported: This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble. I had already installed nvidia-cuda-toolkit, and then... # apt-get install nvidia-utils-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: nvidia-driver-535 The following NEW packages will be installed: nvidia-utils-535 0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 405 kB of archives. After this operation, 1157 kB of additional disk space will be used. Get:1 http://apt.example.com/ubuntu noble/restricted amd64 nvidia-utils-535 amd64 535.161.07-0ubuntu3 [405 kB] Fetched 405 kB in 0s (2693 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package nvidia-utils-535. (Reading database ... 51672 files and directories currently installed.) Preparing to unpack .../nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb ... Unpacking nvidia-utils-535 (535.161.07-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb (--unpack): unable to make backup link of './usr/bin/nvidia-debugdump' before installing new version: Invalid cross-device link dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056231 Title: Error when installing nvidia-utils-535: "Invalid cross-device link" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2056231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966162] Re: Display still powers down after screensaver and power management are disabled
On an installed system, with both the aforementioned settings disabled, the display still blanks (black screen) but does not power down. "xset -q" run on the system via ssh shows "DPMS is Disabled". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966162 Title: Display still powers down after screensaver and power management are disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1966162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973298] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973298/+attachment/5589672/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973298 Title: Does not terminate at end of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-application/+bug/1973298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973298] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973298/+attachment/5589673/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973298 Title: Does not terminate at end of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-application/+bug/1973298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973298] Re: Does not terminate at end of session
apport information ** Tags added: apport-collected ** Description changed: This concerns ayatana-indicator-application 22.2.0-1 in Ubuntu jammy. When I am logged into an Xfce session, I see this: # loginctl list-sessions SESSION UID USER SEAT TTY 40 root c2 1000 skunk seat0 2 sessions listed. # loginctl session-status c2 c2 - skunk (1000) Since: Fri 2022-05-13 05:38:18 EDT; 51s ago Leader: 1172 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: active Unit: session-c2.scope ├─1172 lightdm --session-child 12 19 ├─1197 xfce4-session ├─1367 /usr/bin/VBoxClient --seamless ├─1368 /usr/bin/VBoxClient --seamless ├─1472 /usr/bin/ssh-agent -s ├─1482 xfwm4 --replace ├─1491 xfsettingsd ├─1500 xfce4-panel ├─1504 Thunar --daemon ├─1513 xfdesktop ├─1516 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1517 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1519 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1521 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1522 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1544 xcape -e Super_L Control_L Escape ├─1562 xfce4-power-manager ├─1565 /usr/lib/policykit-1-gnome/polkit-gnome-authentication> ├─1576 /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd ├─1579 /usr/libexec/ayatana-indicator-application/ayatana-ind> ├─1587 nm-applet ├─1596 update-notifier └─1597 xiccd After I log out, and wait ten minutes, I see this: # loginctl list-sessions SESSION UID USERSEAT TTY 40 root c2 1000 skunk seat0 c3 117 lightdm seat0 3 sessions listed. # loginctl session-status c2 | cat c2 - skunk (1000) Since: Fri 2022-05-13 05:38:18 EDT; 12min ago Leader: 1172 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─1579 /usr/libexec/ayatana-indicator-application/ayatana-indicator-application-service - The ayatana-indicator-application program is refusing to exit for some - reason. If I "kill -INT 1579", then the session finally closes. + The ayatana-indicator-application program is refusing to exit for some reason. If I "kill -INT 1579", then the session finally closes. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + Package: ayatana-indicator-application 22.2.0-1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1973298/+attachment/5589671/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973298 Title: Does not terminate at end of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-application/+bug/1973298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973302] [NEW] "/usr/bin/VBoxClient --vmsvga" causes black screen inside VirtualBox host
Public bug reported: This concerns virtualbox-guest-x11 6.1.32-dfsg-1build1 in Ubuntu jammy. I am running the Xubuntu (Xfce) desktop inside of a VirtualBox host (5.2.42-dfsg-0~ubuntu1.18.04.1) on Ubuntu bionic. The system boots fine, and I get to the lightdm login prompt without issue. Shortly after logging in, however, the entire (guest) screen turns black. The desktop appears to be running normally, I can start X applications from a virtual terminal, I can even confirm with xev(1) that mouse movements are being recognized within the black screen. However, nothing I do gets anything to display, other than killing the session from a VT and returning to lightdm. I have tracked down the issue to the invocation of "/usr/bin/VBoxClient --vmsvga" in /etc/X11/Xsession.d/98vboxadd-xclient . If I comment out that line, then the session appears normally. If I re-enable it, the black screen returns. Heck, if I run that in a terminal in a working session, the black screen returns. Killing the VBoxClient process at fault does not restore normal video. ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973302 Title: "/usr/bin/VBoxClient --vmsvga" causes black screen inside VirtualBox host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973298] [NEW] Does not terminate at end of session
Public bug reported: This concerns ayatana-indicator-application 22.2.0-1 in Ubuntu jammy. When I am logged into an Xfce session, I see this: # loginctl list-sessions SESSION UID USER SEAT TTY 40 root c2 1000 skunk seat0 2 sessions listed. # loginctl session-status c2 c2 - skunk (1000) Since: Fri 2022-05-13 05:38:18 EDT; 51s ago Leader: 1172 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: active Unit: session-c2.scope ├─1172 lightdm --session-child 12 19 ├─1197 xfce4-session ├─1367 /usr/bin/VBoxClient --seamless ├─1368 /usr/bin/VBoxClient --seamless ├─1472 /usr/bin/ssh-agent -s ├─1482 xfwm4 --replace ├─1491 xfsettingsd ├─1500 xfce4-panel ├─1504 Thunar --daemon ├─1513 xfdesktop ├─1516 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1517 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1519 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1521 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1522 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─1544 xcape -e Super_L Control_L Escape ├─1562 xfce4-power-manager ├─1565 /usr/lib/policykit-1-gnome/polkit-gnome-authentication> ├─1576 /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd ├─1579 /usr/libexec/ayatana-indicator-application/ayatana-ind> ├─1587 nm-applet ├─1596 update-notifier └─1597 xiccd After I log out, and wait ten minutes, I see this: # loginctl list-sessions SESSION UID USERSEAT TTY 40 root c2 1000 skunk seat0 c3 117 lightdm seat0 3 sessions listed. # loginctl session-status c2 | cat c2 - skunk (1000) Since: Fri 2022-05-13 05:38:18 EDT; 12min ago Leader: 1172 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─1579 /usr/libexec/ayatana-indicator-application/ayatana-indicator-application-service The ayatana-indicator-application program is refusing to exit for some reason. If I "kill -INT 1579", then the session finally closes. ** Affects: ayatana-indicator-application (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973298 Title: Does not terminate at end of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-application/+bug/1973298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973291] [NEW] "VBoxClient --draganddrop" does not terminate at end of session
Public bug reported: This concerns virtualbox-guest-x11 6.1.32-dfsg-1build1 in Ubuntu jammy. When I am logged in to an Xfce session, the view from loginctl(1) is as follows: # loginctl list-sessions SESSION UID USER SEAT TTY 40 root c24 1000 skunk seat0 2 sessions listed. # loginctl session-status c24 c24 - skunk (1000) Since: Fri 2022-05-13 04:53:43 EDT; 41s ago Leader: 8502 (lightdm) Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xfce State: active Unit: session-c24.scope ├─8502 lightdm --session-child 12 19 ├─8527 xfce4-session ├─8698 /usr/bin/VBoxClient --seamless ├─8699 /usr/bin/VBoxClient --seamless ├─8705 /usr/bin/VBoxClient --draganddrop ├─8706 /usr/bin/VBoxClient --draganddrop ├─8806 /usr/bin/ssh-agent -s ├─8815 xfwm4 ├─8824 xfsettingsd ├─8827 xfce4-panel ├─8831 Thunar --daemon ├─8836 xfdesktop ├─8839 /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd ├─8840 update-notifier ├─8843 xiccd ├─8847 nm-applet ├─8887 xfce4-power-manager ├─8899 /usr/lib/policykit-1-gnome/polkit-gnome-authentication> ├─8927 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─8928 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> ├─8929 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> └─8949 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr> After I log out, and wait ten minutes, I see this: # loginctl list-sessions SESSION UID USERSEAT TTY 40 root c24 1000 skunk seat0 c25 117 lightdm seat0 3 sessions listed. # loginctl session-status c24 c24 - skunk (1000) Since: Fri 2022-05-13 04:53:43 EDT; 13min ago Leader: 8502 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xfce State: closing Unit: session-c24.scope ├─8705 /usr/bin/VBoxClient --draganddrop └─8706 /usr/bin/VBoxClient --draganddrop The "VBoxClient --draganddrop" program, for some reason, is refusing to exit so that the session can be closed. If I do "kill -INT 8706", then I see # loginctl list-sessions SESSION UID USERSEAT TTY 4 0 root c25 117 lightdm seat0 2 sessions listed. which is what should have happened without intervention. ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973291 Title: "VBoxClient --draganddrop" does not terminate at end of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1973291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970017] [NEW] Warning from certificate file with non-ASCII characters
Public bug reported: This concerns ca-certificates-java 20190909 in Ubuntu jammy. Seen during installation of Java packages: [...] Setting up libatk-wrapper-java (0.38.0-5build1) ... Setting up default-jdk-doc (2:1.11-72build2) ... Setting up libatk-wrapper-java-jni:amd64 (0.38.0-5build1) ... Setting up ca-certificates-java (20190909) ... head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory Adding debian:DigiCert_Assured_ID_Root_G3.pem Warning: there was a problem reading the certificate file /etc/ssl/certs/NetLock_Arany_=Class_Gold=_F?tan?s?tv?ny.pem. Message: /etc/ssl/certs/NetLock_Arany_=Class_Gold=_F?tan?s?tv?ny.pem (No such file or directory) Adding debian:E-Tugra_Certification_Authority.pem Adding debian:Entrust_Root_Certification_Authority_-_G2.pem Adding debian:SecureTrust_CA.pem [...] The "cannot open" error also seems in need of attention. ** Affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970017 Title: Warning from certificate file with non-ASCII characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1970017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
*** This bug is a duplicate of bug 1949970 *** https://bugs.launchpad.net/bugs/1949970 This appears to have been addressed in bug #1949970 by making use of a feature of the PAM config. In /etc/pam.d/lightdm, I see e.g. -authoptionalpam_gnome_keyring.so -authoptionalpam_kwallet.so -authoptionalpam_kwallet5.so From the pam.conf(5) man page: If the *type* value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session. I'll mark this issue as a duplicate of the newer one, even though it should be the other way around. ** This bug has been marked a duplicate of bug 1949970 attempt to dlopen nonexistent pam_kwallet.so spams log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966048] Re: xrdp fails to bind to localhost
On further digging, I've found that this issue is due to an AppArmor rule, which for some reason was treating localhost differently (as IPv6) than a regular network address (IPv4). Closing. ** Changed in: xrdp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966048 Title: xrdp fails to bind to localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1966048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918410] Re: isc-dhcp-client denied by apparmor
Note to everyone watching this bug: The file that John modified above is in the "extra profiles" section of the upstream AppArmor source repository. It may be found on an Ubuntu system at /usr/share/apparmor/extra-profiles/sbin.dhclient and in jammy, it has his fix. However, the isc-dhcp-client package provides its own separate profile, which is installed at /etc/apparmor.d/sbin.dhclient and is quite different. Most people are likely going to be using this latter one, as it is enabled by default. So they will not receive the benefit of John's fix. I've confirmed that the original "DENIED" messages still occur on jammy. ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918410 Title: isc-dhcp-client denied by apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934933] Re: cloud-init dhclient apparmor denied with noexec on /var/tmp
This message...
type=AVC msg=audit(1625678140.496:1898): apparmor="DENIED"
operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/8537/task/8540/comm" pid=8537 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
...is actually for a different issue, discussed at LP: #1918410.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934933
Title:
cloud-init dhclient apparmor denied with noexec on /var/tmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1934933/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961413] Re: [BLUEFIELD] dmesg is flooded with apparmor="DENIED" for dhclient messages
Note that the /proc/XX/task/YY/comm denials are addressed in LP:
#1918410.
That leaves two of this sort:
audit: type=1400 audit(1645193286.560:2012): apparmor="DENIED"
operation="mknod" profile="/{,usr/}sbin/dhclient"
name="/run/NetworkManager/dhclient-oob_net0.pid" pid=103303
comm="dhclient" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961413
Title:
[BLUEFIELD] dmesg is flooded with apparmor="DENIED" for dhclient
messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1961413/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966433] [NEW] Pipewire services start up on remote (ssh) logins
Public bug reported: This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy. I log into an installed system via ssh, and I see skunk@darkstar:~$ ps auxww | grep skunk root 13771 0.5 0.1 19772 12224 ?Ss 07:35 0:00 sshd: skunk [priv] skunk 13774 5.4 0.1 17160 9940 ?Ss 07:35 0:00 /lib/systemd/systemd --user skunk 13775 0.0 0.0 25600 5292 ?S07:35 0:00 (sd-pam) skunk 13782 0.4 0.0 34460 6360 ?Ssl 07:35 0:00 /usr/bin/pipewire skunk 13783 0.4 0.0 18632 6856 ?Ssl 07:35 0:00 /usr/bin/pipewire-media-session skunk 13801 0.0 0.0 8412 4340 ?Ss 07:35 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only skunk 13831 0.0 0.0 19932 8052 ?S07:35 0:00 sshd: skunk@pts/0 skunk 13832 0.0 0.0 5256 4124 pts/0Ss 07:35 0:00 -bash skunk 13854 0.0 0.0 7692 3328 pts/0R+ 07:35 0:00 ps auxww skunk 13855 0.0 0.0 4024 2144 pts/0S+ 07:35 0:00 grep --color=auto skunk Pipewire is a multimedia service. It should not be running in a remote, non-graphical login. ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966433 Title: Pipewire services start up on remote (ssh) logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1966433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965923] Re: rc.apparmor.functions should not mount /sys/kernel/security inside a chroot environment
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965923 Title: rc.apparmor.functions should not mount /sys/kernel/security inside a chroot environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1965923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966034] Re: Request: Add Xubuntu trusty backdrop to xubuntu-wallpapers
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966034 Title: Request: Add Xubuntu trusty backdrop to xubuntu-wallpapers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1966034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966162] [NEW] Display still powers down after screensaver and power management are disabled
Public bug reported: This concerns xubuntu-desktop 2.240 in Ubuntu jammy. (Please redirect this bug to a more suitable package if appropriate.) I am testing the Xubuntu 22.04 live desktop system, running from a daily-build ISO. I do not want the display to blank, nor switch off, when the system is idle. After a normal "Try Xubuntu" startup, in the Settings Manager, I switched off Screensaver -> Screensaver (tab) -> Enable Screensaver Power Manager -> Display (tab) -> Display power management However, the display still powers down after some idle time. ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966162 Title: Display still powers down after screensaver and power management are disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1966162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966048] Re: xrdp fails to bind to localhost
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966048 Title: xrdp fails to bind to localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1966048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966048] [NEW] xrdp fails to bind to localhost
Public bug reported: This concerns xrdp 0.9.17-2ubuntu2 in Ubuntu jammy. I want to have xrdp listen on a localhost port. When I configure the server to use [Globals] ... port=tcp://.:3389 in /etc/xrdp/xrdp.ini, and I attempt to start the server, I get an error: # /etc/init.d/xrdp start Starting xrdp (via systemctl): xrdp.serviceJob for xrdp.service failed because the control process exited with error code. See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for details. failed! In /var/log/xrdp.log, I see [20220323-05:02:00] [INFO ] address [127.0.0.1] port [3389] mode 4 [20220323-05:02:00] [INFO ] listening to port 3389 on 127.0.0.1 [20220323-05:02:00] [ERROR] trans_listen_address failed [20220323-05:02:00] [ERROR] Failed to start xrdp daemon, possibly address already in use. The port is free. Nothing is using it: $ telnet localhost 3389 Trying ::1... Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused I tried building the latest upstream release of xrdp (v0.9.19 as of this writing) with the same build configuration as the Ubuntu package. It starts without error. Please update the package to v0.9.19. ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966048 Title: xrdp fails to bind to localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1966048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966034] [NEW] Request: Add Xubuntu trusty backdrop to xubuntu-wallpapers
Public bug reported: This concerns xubuntu-wallpapers 22.04 in Ubuntu jammy. Please add the Xubuntu backdrop from the trusty release, i.e. https://3.bp.blogspot.com/-pLKk0mvZIQE/U05l_GluNyI/SPM/X6PzqUZhH_s/s1600/xubuntu- trusty.png I miss that mouse. ** Affects: xubuntu-artwork (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966034 Title: Request: Add Xubuntu trusty backdrop to xubuntu-wallpapers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1966034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965923] [NEW] rc.apparmor.functions should not mount /sys/kernel/security inside a chroot environment
Public bug reported: This concerns apparmor 3.0.4-2ubuntu2 in Ubuntu jammy. When I run a command like aa-teardown(8), it will mount securityfs on /sys/kernel/security if this is not already mounted. On bare metal, this is reasonable. But in a chroot environment, the command should probably exit without taking any action, not unlike what systemd does: "Running in chroot, ignoring command 'daemon-reload'". I see that the functions script already has logic addressing AppArmor in container environments, but it appears that the chroot scenario has not been addressed. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965923 Title: rc.apparmor.functions should not mount /sys/kernel/security inside a chroot environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1965923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965255] [NEW] Xubuntu Live ISO does not give (Plymouth) prompt to remove installation medium on reboot
Public bug reported: This concerns plymouth-theme-xubuntu-logo 22.04 in a current daily build of the upcoming Jammy release of the Xubuntu Live ISO. (If this issue belongs to a different package, please redirect accordingly) Normally, when you reboot the system after a live session, you are given the following prompt on the Plymouth logo screen: Please remove the installation medium, then press ENTER: This occurs in an Ubuntu desktop daily build. However, in the Xubuntu daily build, no such prompt appears---the system simply stays on the logo screen, apparently hanged, but hitting Enter will continue as normal. Hitting Esc shows that the usual eject/unmount logic is happening behind the scenes; it appears to be simply not showing the prompt to the user. ** Affects: xubuntu-artwork (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965255 Title: Xubuntu Live ISO does not give (Plymouth) prompt to remove installation medium on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1965255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
FWIW, the fix in focal-proposed looks good on my end as well. I can confirm that the /etc/dhcp/dhclient-enter-hooks.d/resolved script now has the is-enabled check, and while I won't be able to test out resolvconf, I regard the updated conditional as equivalent to my previous known-good workaround (renaming the script to resolved.DISABLED, so it is not sourced by dhclient-script). Greatly appreciate the bug squash! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Yes, it is still an issue in focal. Was there an update since last year that should have addressed this? ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Thank you @ddstreet, I'm happy to see this as well. I'd like to get rid of the workaround I've been using for this issue: # dpkg-divert --divert /etc/dhcp/dhclient-enter- hooks.d/resolved.DISABLED --rename /etc/dhcp/dhclient-enter- hooks.d/resolved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871728] Re: geoclue agent process persists after user logout
KillUserProcesses=yes is a sledgehammer of a solution. I would advise just removing the geoclue package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881357] [NEW] abstractions/X needs new ICEauthority path
Public bug reported: This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal. Saw this during a Firefox test run: May 29 17:25:32 test-ubuntu64 kernel: [ 818.399967] audit: type=1400 audit(1590787532.023:69): apparmor="DENIED" operation="open" profile="firefox" name="/run/user/1000/ICEauthority" pid=1791 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 This comparison was interesting: $ ls -l ~/.ICEauthority /run/user/1000/ICEauthority -rw--- 1 skunk skunk 0 May 29 17:43 /home/skunk/.ICEauthority -rw--- 1 skunk skunk 350 May 29 17:43 /run/user/1000/ICEauthority Is the /run path a new canonical location for the ICEauthority file? The X abstraction would need to know about it. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881357 Title: abstractions/X needs new ICEauthority path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1881357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880841] [NEW] usr.sbin.nscd needs unix socket access to @userdb-*
Public bug reported: This concerns apparmor-profiles 2.13.3-7ubuntu5 in Ubuntu focal. I use the usr.sbin.nscd profile in enforce mode, and am seeing the following messages in /var/log/syslog . I don't know if the SIGABRT is related: May 27 04:39:56 test-ubuntu64 kernel: [ 199.392521] audit: type=1400 audit(1590568796.975:76): apparmor="DENIED" operation="bind" profile="nscd" pid=1679 comm="nscd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-4a5d3fdcfb9afbd7fc75948800519358" May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Main process exited, code=killed, status=6/ABRT May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Failed with result 'signal'. May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Scheduled restart job, restart counter is at 9. The @userdb-* binding looks like a systemd thing. Should a rule for this go into /etc/apparmor.d/abstractions/nameservice ? ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880841 Title: usr.sbin.nscd needs unix socket access to @userdb-* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1880841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783044] Re: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present
I've confirmed that, as of focal, the /boot/efi/EFI/ubuntu/ directory no longer needs to be present in order for the grub-efi-amd64 package to install the bootloader files. Even /boot/efi/EFI/ does not need to be there; it will be created. This issue still appears to exist on the Debian side, however, and Ubuntu now has a related problem (LP: #1879558). Should I file a new bug regarding a concurrent grub-pc + grub-efi-amd64 installation? Is that something that could be reasonably supported? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783044 Title: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1783044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879558] [NEW] grub-efi-amd64 postinst fails to install GRUB if previous GRUB install is not detected
Public bug reported: This concerns grub-efi-amd64 2.04-1ubuntu26 in Ubuntu focal. Currently, when grub-efi-amd64 (or grub-efi-amd64-signed) is installed or reconfigured, the following steps occur: 1. Package postinst script runs 2. postinst checks if /boot/grub/x86_64-efi/core.efi is present, and if so... 3. "/usr/lib/grub/grub-multi-install x86_64-efi" is invoked The check in #2 is accompanied by this comment: # Check /boot/grub to see if we previously installed to an ESP. We don't # want to trigger the install code just by installing the package, # normally the installer installs grub itself first. I very much *want* the package install (or configuration) to do the GRUB install, even if GRUB was not previously installed by the Ubuntu installer. I am specifically concerned with the case of a system with grub-pc being transitioned over to grub-efi-amd64. If a standard system image with the former is installed onto an EFI system, then this conversion is needed. (There is also the case of systems that are themselves converted from BIOS booting to EFI.) I do not know the motivation for the "only install if previously installed" check, but if the goal is to avoid installing GRUB to a plain /boot/efi/ directory (one that is not a separate special EFI partition), then it should be enough to check that /boot/efi/ is a mountpoint. I think it is reasonable to expect the user to set up the EFI partition and mount it prior to installing the package. (Ideally, the package would alert the user if it cannot install GRUB due to /boot/efi/ not being set up correctly.) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879558 Title: grub-efi-amd64 postinst fails to install GRUB if previous GRUB install is not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1879558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879466] [NEW] Purging grub-pc package deletes /etc/default/grub file owned by grub-efi-amd64
Public bug reported: This concerns grub-pc 2.04-1ubuntu26 in Ubuntu focal. I have the following packages installed. Note that grub-pc has been removed but not yet purged: root@xubuntu:/# dpkg -l | grep grub ii grub-common 2.04-1ubuntu26 amd64GRand Unified Bootloader (common files) ii grub-efi-amd642.04-1ubuntu26 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin2.04-1ubuntu26 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 modules) ii grub-efi-amd64-signed 1.142+2.04-1ubuntu26 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) rc grub-pc 2.04-1ubuntu26 amd64GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.04-1ubuntu26 amd64GRand Unified Bootloader, version 2 (PC/BIOS modules) ii grub2-common 2.04-1ubuntu26 amd64GRand Unified Bootloader (common files for version 2) The /etc/default/grub file is owned by grub-efi-amd64, which is correct: root@xubuntu:/# ucfq /etc/default/grub Configuration filePackage Exists Changed /etc/default/grub grub-efi-amd64 YesYes I then purge the grub-pc package, saying no to the "Remove GRUB 2 files?" debconf question: root@xubuntu:/# apt-get purge grub-pc Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: grub-pc* 0 upgraded, 0 newly installed, 1 to remove and 4 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) (Reading database ... 254919 files and directories currently installed.) Purging configuration files for grub-pc (2.04-1ubuntu26) ... ucfr: Association belongs to grub-efi-amd64, not grub-pc ucfr: Aborting ucfr: Association belongs to grub-efi-amd64, not grub-pc ucfr: Aborting And then... root@xubuntu:/# ls -l /etc/default/grub ls: cannot access '/etc/default/grub': No such file or directory The purging of grub-pc deleted a config file belonging to a different package, which is not only incorrect behavior, it could potentially leave the system unbootable after the next update-grub(8) invocation. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879466 Title: Purging grub-pc package deletes /etc/default/grub file owned by grub- efi-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1879466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted
That's why I hedged on having something like "apparmor unload". What you're saying explains why "restart" and "reload" are distinct actions (I'd never been clear on this), so having a new action that is "like 'stop' but actually does stop apparmor, even though that is not usually what you want" makes similar sense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878333 Title: AppArmor cache entries not removed when profile is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted
A related issue: "/etc/init.d/apparmor stop" should invoke aa- teardown(8). Depending on the semantics of the apparmor "service," this could also be "/etc/init.d/apparmor unload" or the like. I was surprised to find that "apparmor stop" was not actually unloading the profiles, as I had assumed. >From the perspective of a sysadmin, I rely on the init scripts to manage daemons/services without having to know the specific technical details of how to interact with each one. A major reason why those scripts exist is to translate a simple start/stop logic into whatever that reasonably means for a particular daemon or service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878333 Title: AppArmor cache entries not removed when profile is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted
Thanks. I am in complete agreement. I don't need (or even want) AppArmor to automagically update the kernel state right after changing something under /etc/apparmor.d/, because having to do a SIGHUP/restart/etc. is already normal practice. But I do expect that a reboot/reload will take care of that for me, as it does for other services. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878333 Title: AppArmor cache entries not removed when profile is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877528] Re: Applet does not terminate at end of X desktop session
Aaaand the upstream has decided they can't/won't fix this issue. One thing that bothers me about this whole situation is that, in order for background services like this one to be cleaned up after logout, they need to behave "correctly." From my point of view, this is backwards. When the system is preparing to reboot, it first sends SIGTERM to all user processes, waits a few seconds, and then sends SIGKILL. Processes that behave correctly are allowed to close down cleanly, and those that don't, are terminated forcibly. If you didn't have that SIGKILL part, then one badly-behaving process could delay the reboot indefinitely. By doing things this way, good behavior is rewarded, but not required. Something like that should be the case for user sessions, although there are exceptions (screen, tmux, nohup), and SIGKILL might be excessive. The upstream bug mentioned a few other processes that remained visible under session-status, and I myself have seen similar behavior from at- spi2-core (haven't determined yet if a bug report is in order for that one). We're going to be fighting a losing battle if every single desktop background service in Ubuntu has to do things correctly in order to avoid keeping the session open after logout. There needs to be a failsafe of some kind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1877528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878333] Re: AppArmor cache entries not removed when profile is deleted
Hello John, I did not take any specific action to unload a profile from the kernel. Instead, I rebooted the system, under the assumption that this would wipe the slate clean, with everything reloading cleanly from /etc/apparmor.d/. The new profile I developed was under a new filename, because I did not want to modify the stock file. Specifically (assuming the profile is "usr.bin.foo"), I created usr.bin.foo.new, and symlinked usr.bin.foo from disable/. It appears to me that aa-remove-unknown (or something like it) should be invoked on startup. The cache is supposed to be an implementation detail (so that the system doesn't spend much time compiling the profiles every time they are loaded), but in this case, it is behaving as a sort of opaque "shadow config" outside of /etc, which is very bad. I can understand that if I edit a file under /etc, the change may not take effect as soon as I save it. Sometimes I have to send a SIGHUP, sometimes I have to restart the daemon, etc. But if I reboot the system, then I think it is reasonable to assume that the entire system config is reloaded (or behaves as if it were reloaded) from /etc. The cache should be properly updated by the system in that situation---it should not require additional action by the user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878333 Title: AppArmor cache entries not removed when profile is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878333] [NEW] AppArmor cache entries not removed when profile is deleted
Public bug reported: This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal. If I delete a profile from /etc/apparmor.d/, reboot the system, and then look in /var/cache/apparmor/.0/, I still see a file for the compiled form of the profile. The same occurs if the profile is "deleted" by other means, such as symlinking it from /etc/apparmor.d/disable/. This behavior caused me some consternation as I was developing an alternate profile for a program that already had one, and I continued to see old behavior even though I had removed the old profile. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878333 Title: AppArmor cache entries not removed when profile is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
Thanks for being on top of this, Sergio. I'm surprised that a LP search for "boot_id" in this project did not turn up this existing bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872564 Title: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878175] [NEW] Abstraction needs access to @{PROC}/sys/kernel/random/boot_id
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
I have AppArmor actively enforcing policy on my system. In
/var/log/syslog, I see a number of the following two sorts of messages:
May 12 04:44:21 image-ubuntu64 kernel: [ 26.667094] audit: type=1400
audit(1589273061.296:63): apparmor="DENIED" operation="open"
profile="nscd" name="/proc/sys/kernel/random/boot_id" pid=655
comm="nscd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
May 12 04:44:26 image-ubuntu64 kernel: [ 32.107018] audit: type=1400
audit(1589273066.730:99): apparmor="DENIED" operation="open"
profile="/usr/sbin/nslcd" name="/proc/sys/kernel/random/boot_id"
pid=1004 comm="nslcd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
The following line is needed in an abstraction somewhere:
@{PROC}/sys/kernel/random/boot_id r,
I've added it locally to /etc/apparmor.d/abstractions/nameservice, and
that took care of the above errors for me. AppArmor upstream has added
it to abstractions/nss-systemd, but this file does not exist in Ubuntu's
apparmor package.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878175
Title:
Abstraction needs access to @{PROC}/sys/kernel/random/boot_id
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878175/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877528] Re: Applet does not terminate at end of X desktop session
This bug was reported three years ago in Debian: https://bugs.debian.org/863227 ** Bug watch added: Debian Bug tracker #863227 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863227 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1877528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877650] Re: Fails to remove /var/lib/command-not-found/ when package is purged
I wouldn't expect dpkg to know about the database files, but they should at least be deleted by a package script (prerm?) when the package is removed/purged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877650 Title: Fails to remove /var/lib/command-not-found/ when package is purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1877650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal. I see the warnings not only for pam_kwallet.so, but also its successor pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have installed). All three of these are referenced in /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter as "optional" modules. I attempted to eliminate the warnings by replacing the "optional" keyword with "[success=ok module_unknown=ignore default=ignore]", but that had no visible effect. The entries referring to these modules need to be removed from LightDM's PAM config files. If libpam-gnome-keyring is installed, it will already make itself known to PAM via a pam-auth-update profile, which is the correct approach. The libpam-kwallet5 package has no pam-auth-update profile, but that is an issue for that package, not this one. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877666] [NEW] Python syntax warning in LayoutLoaderSVG.py
Public bug reported:
This concerns onboard 1.4.1-2ubuntu7 in Ubuntu focal.
Seen during package installation:
[...]
Setting up onboard (1.4.1-2ubuntu7) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
[...]
** Affects: onboard (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877666
Title:
Python syntax warning in LayoutLoaderSVG.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1877666/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877664] [NEW] Python syntax warning in helpers.py script
Public bug reported: This concerns lightdm-gtk-greeter-settings 1.2.2-3 in Ubuntu focal. Seen during package installation: [...] Setting up lightdm-gtk-greeter-settings (1.2.2-3) ... /usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/helpers.py:281: SyntaxWarning: "is" with a literal. Did you mean "=="? if obj._dict[keys[i]] is (): [...] ** Affects: lightdm-gtk-greeter-settings (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877664 Title: Python syntax warning in helpers.py script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter-settings/+bug/1877664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877650] [NEW] Fails to remove /var/lib/command-not-found/ when package is purged
Public bug reported: This concerns command-not-found 20.04.2 in Ubuntu focal. The apt-get invocation largely tells the story: # apt-get --purge --autoremove remove command-not-found Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: command-not-found* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 35.8 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 95222 files and directories currently installed.) Removing command-not-found (20.04.2) ... (Reading database ... 95216 files and directories currently installed.) Purging configuration files for command-not-found (20.04.2) ... dpkg: warning: while removing command-not-found, directory '/var/lib/command-not-found' not empty so not removed # ls -l /var/lib/command-not-found/ total 3020 -rw-r--r-- 1 root root 3084288 May 8 14:54 commands.db -rw-r--r-- 1 root root2442 May 8 14:54 commands.db.metadata I'm purging the package, these files clearly belong to it, that directory should be gone. (Side note: apt-get should be reporting "python3-commandnotfound is no longer needed," since command-not-found is the only package that depends on it, but for some reason this isn't happening. That's why I had specified the --autoremove; I was expecting to remove two packages.) ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877650 Title: Fails to remove /var/lib/command-not-found/ when package is purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1877650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877532] Re: at-spi-bus-launcher does not terminate at end of X session
This bug has LP: 1871726 as a quasi-parent. Those two processes shown in session-status are deceptive; ps(1) shows a much larger number of processes still remaining from the login session. When the two processes go away, however, all the others follow. The impact of this issue, then, is not limited to a mere two lingering processes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877532 Title: at-spi-bus-launcher does not terminate at end of X session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1877532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877528] Re: Applet does not terminate at end of X desktop session
This bug has LP: 1871726 as a quasi-parent. That one system-config-printer process shown in session-status is deceptive; ps(1) shows a much larger number of processes still remaining from the login session. When the s-c-p process goes away, however, all the others follow. The impact of this issue, then, is not limited to a single lingering process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1877528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Also related: LP: #1877532 It's possible that all the lingering processes are due to a couple of misbehaving applications. This isn't a great state of affairs (the cleanup process should not be so fragile that non-cooperative processes can stop it completely), but it might explain what's going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877532] [NEW] at-spi-bus-launcher does not terminate at end of X session
Public bug reported: This concerns at-spi2-core 2.36.0-2 in Ubuntu focal. I log into the Xfce desktop as "skunk" via xrdp, and then logout. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USER SEAT TTY 9 0 root c10 1000 skunk c9 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c10": c10 - skunk (1000) Since: Fri 2020-05-08 04:03:51 EDT; 6min ago Leader: 6009 Display: :11 Service: xrdp-sesman; type x11; class user State: closing Unit: session-c10.scope ├─6184 /usr/libexec/at-spi-bus-launcher --launch-immediately └─6199 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 These two processes stick around forever until I kill them, or their parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of about 20 desktop-related processes. All of them except these two go away on logout. These should too. (Note that this problem does not occur when I log in/out via LightDM on the console.) ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877532 Title: at-spi-bus-launcher does not terminate at end of X session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1877532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Related: LP: #1877528 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877528] [NEW] Applet does not terminate at end of X desktop session
Public bug reported: This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal. I log into the Xfce desktop, and then logout. The screen returns to the LightDM login screen. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USERSEAT TTY 90 root c2 1000 skunk seat0 c3 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c2": c2 - skunk (1000) Since: Fri 2020-05-08 03:09:05 EDT; 9min ago Leader: 2530 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─2856 /usr/bin/python3 /usr/share/system-config-printer/applet.py This process sticks around forever until I kill it, or its parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of nearly 30 desktop-related processes. All of them except this one go away on logout. This one should too. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1877528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870640] Re: Does not register as x-www-browser alternative
Oliver and Łukasz, thank you for following this up. So that I understand, in focal, is the fix part of the transitional package, not in the snap? The former is described as "This is a transitional dummy package. It can safely be removed," but would removing it then remove Chromium as an x -www-browser alternative? (Because that would arguably contradict the "safely") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870640 Title: Does not register as x-www-browser alternative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871882] Re: Default session fails when not started by a login manager
I'm not sure that this new title is accurate, as the error condition is brought about specifically by an unusual (albeit legal) way of starting the X session. My scenario involved xrdp, but I could see this happening with an older display manager (xdm?) that does not recognize XDG xsession files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: Default session fails when not started by a login manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543834] Re: grub-set-default should give a warning when GRUB_DEFAULT != saved
To elaborate on the situation in Ubuntu focal, as there have been some improvements: * grub-reboot(8) now works even when GRUB_DEFAULT != "saved", so that is out of the picture. I've edited the title of this bug accordingly. * Both the man page and --help text for grub-set-default(8) indicate that GRUB_DEFAULT="saved" is required for the command to have the desired effect. * grub-set-default(8) still gives no warning/error when GRUB_DEFAULT != "saved", however, leaving open the possibility of breaking scripts or other scenarios where it is assumed to work. ** Summary changed: - grub-set-default and grub-reboot should give a warning when GRUB_DEFAULT != saved + grub-set-default should give a warning when GRUB_DEFAULT != saved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543834 Title: grub-set-default should give a warning when GRUB_DEFAULT != saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/543834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts
This issue is still present in Ubuntu focal. Here is what I see that needs to happen: systemd: The /etc/dhcp/dhclient-enter-hooks.d/resolved script should be renamed to something like 00resolved or aaa_resolved, so that other packages that install scripts into that directory will have their scripts override whatever definitions are in the "resolved" script. (It is notable that the avahi-autoipd package installs a file named "zzz_avahi-autoipd" into /etc/dhcp/dhclient-exit-hooks.d/, apparently so that it always runs last.) systemd: The "resolved" script itself is obviously a modified version of the one shipped with resolvconf; a comment at the top still even names the original project. There is a conditional at the top that checks for the presence of /lib/systemd/systemd-resolved (exactly where the original checks for /sbin/resolvconf), but this check is pointless---the systemd-resolved file not only belongs to the same package as the script, the package in question is systemd, which for all intents and purposes cannot be removed. Instead, the check should be on whether systemd-resolved is enabled, e.g. if systemctl is-enabled systemd-resolved | fgrep -q enabled ; then systemd: In general, the "resolved" script could use some cleanup, particularly on removing bits related to resolvconf that do not apply to systemd-resolved. resolvconf: It may be worthwhile for this package to disable systemd- resolved upon installation (and re-enable it upon renewal), as that presumably would be the intent of anyone installing it. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782275 Title: Conflict between resolvconf and systemd-resolved dhclient scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543834] Re: grub-set-default and grub-reboot should give a warning when GRUB_DEFAULT != saved
I've confirmed that this issue is still present in Ubuntu focal. ** Changed in: grub2 (Ubuntu) Status: Incomplete => New ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543834 Title: grub-set-default and grub-reboot should give a warning when GRUB_DEFAULT != saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/543834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
Could you try this using lightdm? It's possible that this may be a display-manager issue. I did notice that in a different (customized) configuration of Xubuntu, the user processes still remained after logout, but then killing the "systemd --user" process resulted in the login session ending. Anyway, here is the output you requested, in the original test environment: # LC_ALL=C loginctl user-status skunk | cat skunk (1000) Since: Fri 2020-04-10 18:40:19 EDT; 3min 11s ago State: closing Sessions: *c2 Linger: no Unit: user-1000.slice |-session-c2.scope | |-1288 /usr/libexec/geoclue-2.0/demos/agent | `-1345 /usr/bin/python3 /usr/share/system-config-printer/applet.py `-user@1000.service |-at-spi-dbus-bus.service | |-1131 /usr/libexec/at-spi-bus-launcher | `-1136 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 |-dbus.service | |-1042 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only | |-1140 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd | |-1291 /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd | |-1302 /usr/libexec/dconf-service | |-1391 /usr/libexec/goa-daemon | `-1404 /usr/libexec/goa-identity-service |-evolution-addressbook-factory.service | `-1438 /usr/libexec/evolution-addressbook-factory |-evolution-calendar-factory.service | `-1396 /usr/libexec/evolution-calendar-factory |-evolution-source-registry.service | `-1374 /usr/libexec/evolution-source-registry |-gvfs-afc-volume-monitor.service | `-1501 /usr/libexec/gvfs-afc-volume-monitor |-gvfs-daemon.service | |-1153 /usr/libexec/gvfsd | |-1158 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes | `-1509 /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0 |-gvfs-goa-volume-monitor.service | `-1497 /usr/libexec/gvfs-goa-volume-monitor |-gvfs-gphoto2-volume-monitor.service | `-1493 /usr/libexec/gvfs-gphoto2-volume-monitor |-gvfs-metadata.service | `-1515 /usr/libexec/gvfsd-metadata |-gvfs-mtp-volume-monitor.service | `-1489 /usr/libexec/gvfs-mtp-volume-monitor |-gvfs-udisks2-volume-monitor.service | `-1484 /usr/libexec/gvfs-udisks2-volume-monitor |-init.scope | |-1017 /lib/systemd/systemd --user | `-1018 (sd-pam) `-obex.service `-1464 /usr/lib/bluetooth/obexd Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Application Service. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: indicator-keyboard.service: Succeeded. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Keyboard Backend. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopping Indicator Session Service... Apr 10 18:41:21 test-ubuntu64 systemd[1017]: indicator-session.service: Succeeded. Apr 10 18:41:21 test-ubuntu64 systemd[1017]: Stopped Indicator Session Service. Apr 10 18:41:22 test-ubuntu64 indicator-sound[1250]: g_object_ref: assertion 'old_val > 0' failed Apr 10 18:41:22 test-ubuntu64 systemd[1017]: pulseaudio.service: Succeeded. Apr 10 18:41:22 test-ubuntu64 systemd[1017]: indicator-sound.service: Succeeded. Apr 10 18:41:22 test-ubuntu64 systemd[1017]: Stopped Indicator Sound Service. If I kill the "systemd --user" process, the output slims down to this: # LC_ALL=C loginctl user-status skunk | cat skunk (1000) Since: Fri 2020-04-10 18:40:19 EDT; 5min ago State: closing Sessions: *c2 Linger: no Unit: user-1000.slice `-session-c2.scope `-1288 /usr/libexec/geoclue-2.0/demos/agent Apr 10 18:45:14 test-ubuntu64 systemd[1017]: pk-debconf-helper.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed debconf communication socket. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: pulseaudio.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed Sound System. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: snapd.session-agent.socket: Succeeded. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Closed REST API socket for snapd user session agent. Apr 10 18:45:14 test-ubuntu64 systemd[1017]: Reached target Shutdown. Apr 10 18:45:14 test-ubuntu64
[Bug 1871882] Re: gnome-session-bin package cannot function without gnome-session
Autologin is not in use. The only unusual aspect of this login is that it is via xrdp, and because no argument is passed to the initial /etc/X11/Xsession invocation, it uses the default x-session-manager -> gnome-session . If the user logs in via the console, xfce4-session is used instead, masking the problem. (I tested with an empty user home directory, so there is no user config to confound the problem.) On an Ubuntu desktop system, gnome-session-binary loads /usr/share /gnome-session/sessions/gnome-login.session which is provided by gdm3. So the dependency for gnome-session-bin could be stated as "gnome- session | gdm3". The problem can be reproduced by using /usr/bin/gnome-session as the session manager, with neither the gnome-session nor gdm3 packages installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: gnome-session-bin package cannot function without gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871979] Re: package grub-efi-amd64-signed 1.139+2.04-1ubuntu24 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 2
*** This bug is a duplicate of bug 1871955 *** https://bugs.launchpad.net/bugs/1871955 Looks like a misplaced double-semicolon: --- /var/lib/dpkg/info/grub-efi-amd64-signed.postinst 2020-04-09 07:00:04.0 -0400 +++ /tmp/grub-efi-amd64-signed.postinst 2020-04-09 22:16:11.243539503 -0400 @@ -16,7 +16,7 @@ case $1 in configure) - target=x86_64-efi ;; + target=x86_64-efi # Check /boot/grub to see if we previously installed to an ESP. We don't # want to trigger the install code just by installing the package, # normally the installer installs grub itself first. ** This bug has been marked a duplicate of bug 1871955 package grub-efi-amd64-signed 1.139+2.04-1ubuntu24 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 2 when I ran apt dist-upgrade with pre-release updates enabled in Software Properties -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871979 Title: package grub-efi-amd64-signed 1.139+2.04-1ubuntu24 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1871979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871896] [NEW] Perl warning during package installation
Public bug reported: This concerns update-inetd 4.50 in Ubuntu focal. Observed during package installation: [...] Setting up finger (0.17-17) ... Setting up update-inetd (4.50) ... Setting up fingerd (0.17-17) ... Use of uninitialized value $_ in pattern match (m//) at /usr/share/perl5/DebianNet.pm line 589. Setting up tcpd (7.6.q-30) ... [...] ** Affects: update-inetd (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871896 Title: Perl warning during package installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-inetd/+bug/1871896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871882] [NEW] gnome-session-bin package cannot function without gnome-session
Public bug reported: This concerns gnome-session-bin 3.36.0-2ubuntu1 in Ubuntu focal. When I log into a Xubuntu desktop via xrdp, an error occurs, and the session terminates before the desktop is even drawn on the screen. I looked in syslog, and saw this: Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:12:23 test-ubuntu64 gnome-session[1900]: gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 systemd[1760]: gnome-session-manager@gnome.service: Main process exited, code=exited, status=1/FAILURE I edited /usr/lib/systemd/user/gnome-session-manager@.service to add the --debug option to the gnome-session-binary invocation, and tried again. Now I saw this: Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818#012 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): fill: *** Looking if /home/skunk/.config/gnome-session/sessions/gnome.session is a valid session file Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): fill: *** Looking if /home/skunk/.config/gnome-session/sessions/gnome.session is a valid session file Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Cannot use session '/home/skunk/.config/gnome-session/sessions/gnome.session': non-existing or invalid file. Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Cannot use session '/home/skunk/.config/gnome-session/sessions/gnome.session':
[Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out
This occurs whether the user logs in (through lightdm) on the console, or remotely via xrdp. Running that command, as root, after the user (skunk) has logged in via lightdm: # loginctl list-sessions SESSION UID USER SEAT TTY 20 root c2 1000 skunk seat0 2 sessions listed. After logout: # loginctl list-sessions SESSION UID USERSEAT TTY 20 root c2 1000 skunk seat0 c3 107 lightdm seat0 3 sessions listed. Even after SIGINT to "systemd --user", even after all the user processes go away, the c2 session remains present. The output from loginctl for an xrdp login is similar. After logout: # loginctl list-sessions SESSION UID USERSEAT TTY 20 root c1 107 lightdm seat0 c2 1000 skunk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871593] Re: User receives prompt on login: "Authentication is required to create a color managed device"
Note: My use case involves logging into the desktop remotely, via XRDP. This issue appears to affect other remote-login implementations as well. Related: https://github.com/TurboVNC/turbovnc/issues/47 https://bugzilla.redhat.com/show_bug.cgi?id=1149893 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/273 ** Bug watch added: github.com/TurboVNC/turbovnc/issues #47 https://github.com/TurboVNC/turbovnc/issues/47 ** Bug watch added: Red Hat Bugzilla #1149893 https://bugzilla.redhat.com/show_bug.cgi?id=1149893 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #273 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871593 Title: User receives prompt on login: "Authentication is required to create a color managed device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1871593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871728] [NEW] geoclue agent process persists after user logout
Public bug reported: This concerns geoclue-2.0 2.5.6-0ubuntu1 in Ubuntu focal. I am using the Xfce desktop. When a user logs in, a /usr/libexec/geoclue-2.0/demos/agent process is started. However, when the user logs out, and the associated "systemd --user" instance is killed, the geoclue process remains---apparently because it is running outside of the process group in which all the other session- related processes were in. Not only does this prevent the process from being cleaned up correctly, if the user logs in again, *another* geoclue process starts up. And when they log out, and everything else gets cleaned up... *two* useless geoclue processes remain. Repeat ad infinitum. ** Affects: geoclue-2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871726] [NEW] "systemd --user" and child processes fail to exit when user logs out
Public bug reported: This concerns systemd 245.2-1ubuntu2 in Ubuntu focal. I am using the Xfce desktop. After the user logs out from a desktop session, numerous desktop-related processes are left over. Here is a listing, taken over twenty minutes after logout: skunk853 0.0 0.2 18912 10300 ?Ss 17:55 0:00 /lib/systemd/systemd --user skunk854 0.0 0.0 103304 3496 ?S17:55 0:00 (sd-pam) skunk881 0.0 0.1 8076 5324 ?Ss 17:55 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only skunk970 0.0 0.1 305364 6776 ?Ssl 17:55 0:00 /usr/libexec/at-spi-bus-launcher skunk975 0.0 0.1 7352 4452 ?S17:55 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 skunk979 0.0 0.1 230196 5900 ?Sl 17:55 0:00 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd skunk992 0.0 0.1 239704 7676 ?Ssl 17:55 0:00 /usr/libexec/gvfsd skunk997 0.0 0.1 378332 6444 ?Sl 17:55 0:00 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes skunk 1133 0.0 0.1 156116 5596 ?Sl 17:56 0:00 /usr/libexec/dconf-service skunk 1139 0.0 0.1 236884 4828 ?Sl 17:56 0:00 /usr/libexec/geoclue-2.0/demos/agent skunk 1186 0.0 0.8 59324 34792 ?S17:56 0:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py skunk 1201 0.0 0.6 391676 25688 ?Ssl 17:56 0:00 /usr/libexec/evolution-source-registry skunk 1224 0.0 0.8 616644 35492 ?Sl 17:56 0:00 /usr/libexec/goa-daemon skunk 1235 0.0 0.7 708928 30512 ?Ssl 17:56 0:00 /usr/libexec/evolution-calendar-factory skunk 1243 0.0 0.2 314744 8980 ?Sl 17:56 0:00 /usr/libexec/goa-identity-service skunk 1271 0.0 0.7 681460 29344 ?Ssl 17:56 0:00 /usr/libexec/evolution-addressbook-factory skunk 1302 0.0 0.1 43968 6432 ?Ss 17:56 0:00 /usr/lib/bluetooth/obexd skunk 1322 0.0 0.2 313872 9076 ?Ssl 17:56 0:00 /usr/libexec/gvfs-udisks2-volume-monitor skunk 1327 0.0 0.1 235684 6468 ?Ssl 17:56 0:00 /usr/libexec/gvfs-mtp-volume-monitor skunk 1331 0.0 0.1 237956 6876 ?Ssl 17:56 0:00 /usr/libexec/gvfs-gphoto2-volume-monitor skunk 1335 0.0 0.1 235864 5760 ?Ssl 17:56 0:00 /usr/libexec/gvfs-goa-volume-monitor skunk 1339 0.0 0.2 316716 8800 ?Ssl 17:56 0:00 /usr/libexec/gvfs-afc-volume-monitor skunk 1347 0.0 0.1 313684 7836 ?Sl 17:56 0:00 /usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0 skunk 1353 0.0 0.1 162128 6028 ?Ssl 17:56 0:00 /usr/libexec/gvfsd-metadata When a user logs out of the system, all processes associated with the login session should be terminated (barring the use of nohup(1) or the like). If I sent a SIGINT to the "systemd --user" process above (PID 853), then all the processes promptly go away. This needs to occur on logout. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871593] [NEW] User receives prompt on login: "Authentication is required to create a color managed device"
Public bug reported: This concerns colord 1.4.4-2 in Ubuntu focal. (xiccd 0.3.0-1 may also be relevant.) I log into the Xfce desktop environment, and immediately see an "Authenticate" window pop up: Authentication is required to create a color managed device Password for root: Action: org.freedesktop.color-manager.create-device Vendor: System Color Manager I see this in syslog: Apr 8 05:38:30 test-ubuntu64 dbus-daemon[573]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.35' (uid=1000 pid=1475 comm="xiccd " label="unconfined") This prompt is confusing to ordinary users, and I do not understand why it should even be necessary. ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871593 Title: User receives prompt on login: "Authentication is required to create a color managed device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1871593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871318] [NEW] tumblerd GStreamer plugin crashes on startup, causing desktop session to exit
Public bug reported: This concerns tumbler 0.2.8-1 in Ubuntu focal. Symptom: When I log into the Xubuntu desktop environment, the desktop begins to appear on the screen, but then the X server dies and I am unceremoniously returned to the LightDM login screen. If I uninstall tumbler, then I can log into the desktop environment without issue. I performed further testing, with tumbler installed. I looked at the shared libraries in /usr/lib/x86_64-linux-gnu/tumbler-1/plugins/, and experimented with removing/replacing them. I've confirmed that removing tumbler-gst-thumbnailer.so is enough to make the crash go away. Conversely, leaving it in as the only plugin causes the crash to occur. Because this library is a D-Bus plugin, I do not know how to debug it. There is no crash file for tumbler in /var/crash/ (but I see ones for xfsettingsd and the Xorg X server). ** Affects: tumbler (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871318 Title: tumblerd GStreamer plugin crashes on startup, causing desktop session to exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tumbler/+bug/1871318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870640] [NEW] Does not register as x-www-browser alternative
Public bug reported: This concern chromium 80.0.3987.162 (snap package) in Ubuntu focal. After installing the package, update-alternatives(1) cannot set x-www- browser to point to /usr/bin/chromium-browser: # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting This worked correctly with the previous non-snap chromium-browser package. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870640 Title: Does not register as x-www-browser alternative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870633] [NEW] Python syntax issues in SgtLauncher.py
Public bug reported: This concerns sgt-launcher version 0.2.5-0ubuntu1 in Ubuntu focal. I see the following when installing the package: Setting up sgt-launcher (0.2.5-0ubuntu1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/lib/python3/dist-packages/sgtlauncher/SgtLauncher.py:232: SyntaxWarning: "is" with a literal. Did you mean "=="? if name is "launcher": /usr/lib/python3/dist-packages/sgtlauncher/SgtLauncher.py:235: SyntaxWarning: "is" with a literal. Did you mean "=="? if name is "loading": /usr/lib/python3/dist-packages/sgtlauncher/SgtLauncher.py:238: SyntaxWarning: "is" with a literal. Did you mean "=="? if name is "game": /usr/lib/python3/dist-packages/sgtlauncher/SgtLauncher.py:250: SyntaxWarning: "is not" with a literal. Did you mean "!="? if name is not "launcher" and os.path.isfile(icon_name): /usr/lib/python3/dist-packages/sgtlauncher/SgtLauncher.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="? if name is "game": The "line buffering" warning is a different issue, but the SyntaxWarning messages indicate problems with at least one of this package's Python scripts. ** Affects: sgt-launcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870633 Title: Python syntax issues in SgtLauncher.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgt-launcher/+bug/1870633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels
Thanks Balint. I've installed the bionic-proposed package, and have not observed any silently-failed upgrades as before (but of course verifying it in my use case is tantamount to proving a negative). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853861 Title: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1853861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 507309] Re: Should not re-mount all connected drives on startup
Hi Carolyn, This bug concerns usb-creator specifically, not the general USB 3.0 mounting behavior of Linux. Please do not mark this bug as a duplicate of #792085. ** This bug is no longer a duplicate of bug 792085 Automatic remount of safely removed USB 3.0 drive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/507309 Title: Should not re-mount all connected drives on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/507309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
Could this be SRU'ed into Bionic? 18.04LTS currently has version 1.1, so the "Reading database ..." lines will otherwise afflict it for quite some time to come. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
Scott, thank you for providing the script, and the analysis that led to it. I've run into this issue numerous times but have not been able to suss out exactly what leads to it such that it can be reproduced. I've linked a relevant Debian bug, which appears to address the same issue, and was filed more recently. ** Bug watch added: Debian Bug tracker #812574 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812574 ** Also affects: grub2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812574 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784499] Re: AppArmor treats regular NFS file access as network op
Thanks for looking into this Markus. I'm surprised that the kernel pieces needed to make this work as expected have yet to be fully integrated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784499 Title: AppArmor treats regular NFS file access as network op To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1784499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783044] Re: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present
I think there's a good case to get rid of those Conflicts:, at least for the package combinations that make sense. BIOS+EFI definitely makes sense, IMO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783044 Title: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1783044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783044] Re: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present
My understanding is that grub-pc conflicts with grub-efi-amd64 (and other top-level GRUB packages), so having both installed shouldn't even be possible. (I've filed a bug report on the Debian side to address this, as this situation is not ideal: https://bugs.debian.org/904062) And that if you want the GRUB installation tools, but don't want the bootloader installed automatically on the running system, then this is when you'd install a grub-foo-bin package without the corresponding grub-foo. My point was just that the "Don't install to the EFI removable media path" question is not orthogonal to your hypothetical "Create an EFI subdirectory?" question, so maybe the solution would be to replace the former with some kind of multi-choice question. ** Bug watch added: Debian Bug tracker #904062 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904062 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783044 Title: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1783044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
Arrgh... this is not a great way of working (malware could write to that location and then load in code), but as it is what we've got, I've added the rule to a forthcoming Firefox profile update. Incidentally, Olivier, if you've got a line on who's responsible for the Firefox profile there, it would be very helpful. The profile is no longer maintained by the AppArmor folks, and I'm not sure of a better place to send an update aside from here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777070 Title: firefox plugin libwidevinecdm.so crashes due to apparmor denial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1777070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785548] [NEW] GRUB countdown does not begin until key press
Public bug reported: This concerns grub-pc 2.02-2ubuntu8.2 in Ubuntu 18.04/bionic. I have GRUB configured to do a five-second countdown (no menu) on boot: GRUB_TIMEOUT_STYLE=countdown GRUB_TIMEOUT=5 Strangely enough, on a "Dell Precision Workstation" PC that I have here, the "5" appears on boot but does not begin counting down until I press a key. If I don't do anything, the countdown remains stuck. Other systems I have tested on do not show this behavior. Obviously, this could be a real problem for a system that does not have convenient console access. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785548 Title: GRUB countdown does not begin until key press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557818] Re: cups-client does not create /etc/cups directory, let alone client.conf
Bug persists in Ubuntu 18.04/bionic: # ls /etc/cups ls: cannot access '/etc/cups': No such file or directory # apt-get install cups-client Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: cups-common libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libcupsfilters1 libcupsimage2 libjbig0 libjpeg-turbo8 libjpeg8 libtiff5 Suggested packages: cups xpp cups-bsd smbclient The following NEW packages will be installed: cups-client cups-common libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libcupsfilters1 libcupsimage2 libjbig0 libjpeg-turbo8 libjpeg8 libtiff5 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 1,043 kB of archives. After this operation, 6,575 kB of additional disk space will be used. Do you want to continue? [Y/n] [...] Setting up libcupsfilters1:amd64 (1.20.2-0ubuntu3) ... Setting up libcupsimage2:amd64 (2.2.7-1ubuntu2.1) ... Setting up cups-client (2.2.7-1ubuntu2.1) ... Adding group `lpadmin' (GID 111) ... Done. Processing triggers for libc-bin (2.27-3ubuntu1) ... # ls /etc/cups ls: cannot access '/etc/cups': No such file or directory ** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/557818 Title: cups-client does not create /etc/cups directory, let alone client.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/557818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690858] Re: AppArmor profile blocks access to .config/gtk-3.0/settings.ini
I see that /etc/apparmor.d/abstractions/gnome in Ubuntu 18.04/bionic has
this line...
owner @{HOME}/.config/gtk-3.0/* r,
...which covers the settings.ini file. So this should no longer be an
issue.
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690858
Title:
AppArmor profile blocks access to .config/gtk-3.0/settings.ini
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690858/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
I think we're going to need more information on how this plugin got in there in the first place. Being able to map a library in a user-writable directory doesn't sound terribly safe... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777070 Title: firefox plugin libwidevinecdm.so crashes due to apparmor denial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1777070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575438] Re: usr.sbin.nscd needs r/w access to nslcd socket
An update to the "ldapclient" abstraction has been merged upstream: https://gitlab.com/apparmor/apparmor/merge_requests/153/diffs?commit_id=ac1d0545f458b11728f2bcb4a7de0567538fa94a ** Changed in: apparmor Status: New => Fix Committed ** Changed in: apparmor (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575438 Title: usr.sbin.nscd needs r/w access to nslcd socket To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1575438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783044] Re: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present
Philip, wouldn't such a debconf question be closely related to the existing question on whether to install to the EFI removable media path? Because if you're not putting things into EFI/ubuntu/ (or EFI/debian/), then you'd be putting them into EFI/BOOT/ ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783044 Title: grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1783044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662501] Re: since the apparmor profile is disabled by default, please make the apparmor policy strict with option to make less strict
Hmmm, interesting! I wouldn't hold out too long on giving the friendly tools smarts vis-a-vis conditionals, since that kind of logic isn't necessarily straightforward (i.e. can be hard/time-consuming to implement), it's not necessary for power/paranoid users (we're happy resorting to a text editor), and even low-skill users are better served by a debconf prompt anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662501 Title: since the apparmor profile is disabled by default, please make the apparmor policy strict with option to make less strict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1662501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665535] Re: WebRTC webcam support broken in firefox due to apparmor
/etc/apparmor.d/abstractions/ubuntu-browsers.d/multimedia in Ubuntu 18.04/bionic contains the fix. Marking the Firefox bug as Invalid, since the issue was fixed by updating the AppArmor abstraction. (I.e. no change to the firefox package was/is needed.) ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665535 Title: WebRTC webcam support broken in firefox due to apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1665535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660298] Re: Firefox misses interface org.gtk.vfs.Enumerator
Does this issue still arise with Firefox 60+? I've encountered various DBus VFS-related denials with Firefox under AppArmor, but not this particular one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660298 Title: Firefox misses interface org.gtk.vfs.Enumerator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1660298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784499] [NEW] AppArmor treats regular NFS file access as network op
Public bug reported: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2788 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066437] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066462] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.067504] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.067535] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel:
[Bug 1784499] Re: AppArmor treats regular NFS file access as network op
I have an additional test case that is perhaps more immediate. Attempting to view a roff file in NFS directly: $ man ./zlib.3 man: ./zlib.3: Permission denied No manual entry for ./zlib.3 This fails despite the permissive "/** mrixwlk" rule in the AppArmor profile. Similar output in the log as above; the denials are network- related, not file-access-related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784499 Title: AppArmor treats regular NFS file access as network op To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1784499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553758] Re: usr.bin.firefox apparmor profile blocks access to meminfo
The Firefox AppArmor profile shipped in Ubuntu 18.04/bionic includes this rule, so this should no longer be an issue. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553758 Title: usr.bin.firefox apparmor profile blocks access to meminfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1553758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660086] Re: Apparmor blocks firefox 51.0.1 reading /usr/share/distro-info/debian.csv
The Firefox AppArmor profile shipped in Ubuntu 18.04/bionic includes a rule for /usr/share/distro-info/*.csv, so this should no longer be an issue. ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660086 Title: Apparmor blocks firefox 51.0.1 reading /usr/share/distro- info/debian.csv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1660086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553708] Re: usr.bin.firefox profile blocks access to the AMD GPU
Hello Jean-Philippe, do you still see this issue if those AppArmor permissions are commented out? Are you using the fglrx driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553708 Title: usr.bin.firefox profile blocks access to the AMD GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1553708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553712] Re: usr.bin.firefox apparmor profile blocks access to mounttracker
Has anyone observed any undesirable behavior from Firefox when access to these mount-related DBus services is denied? It's not clear to me why Firefox is even calling these in the first place, and given that mounts can include NFS servers and the like, I'd just as soon deny this access if there's no good reason for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553712 Title: usr.bin.firefox apparmor profile blocks access to mounttracker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1553712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
