[Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2021-07-10 Thread Daniel Richard G.
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

2021-07-01 Thread Daniel Richard G.
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

2021-06-30 Thread Daniel Richard G.
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

2021-04-09 Thread Daniel Richard G.
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

2020-05-29 Thread Daniel Richard G.
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-*

2020-05-27 Thread Daniel Richard G.
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

2020-05-19 Thread Daniel Richard G.
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

2020-05-19 Thread Daniel Richard G.
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

2020-05-19 Thread Daniel Richard G.
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

2020-05-13 Thread Daniel Richard G.
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

2020-05-13 Thread Daniel Richard G.
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

2020-05-13 Thread Daniel Richard G.
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

2020-05-13 Thread Daniel Richard G.
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

2020-05-13 Thread Daniel Richard G.
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

2020-05-12 Thread Daniel Richard G.
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

2020-05-12 Thread Daniel Richard G.
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

2020-05-12 Thread Daniel Richard G.
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

2020-05-10 Thread Daniel Richard G.
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

2020-05-10 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-08 Thread Daniel Richard G.
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

2020-05-07 Thread Daniel Richard G.
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

2020-04-14 Thread Daniel Richard G.
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

2020-04-14 Thread Daniel Richard G.
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

2020-04-13 Thread Daniel Richard G.
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

2020-04-13 Thread Daniel Richard G.
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

2020-04-10 Thread Daniel Richard G.
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

2020-04-10 Thread Daniel Richard G.
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

2020-04-09 Thread Daniel Richard G.
*** 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

2020-04-09 Thread Daniel Richard G.
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

2020-04-09 Thread Daniel Richard G.
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

2020-04-09 Thread Daniel Richard G.
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"

2020-04-08 Thread Daniel Richard G.
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

2020-04-08 Thread Daniel Richard G.
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

2020-04-08 Thread Daniel Richard G.
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"

2020-04-08 Thread Daniel Richard G.
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

2020-04-07 Thread Daniel Richard G.
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

2020-04-03 Thread Daniel Richard G.
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

2020-04-03 Thread Daniel Richard G.
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

2019-12-03 Thread Daniel Richard G.
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

2019-03-19 Thread Daniel Richard G.
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

2019-01-12 Thread Daniel Richard G.
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

2018-11-30 Thread Daniel Richard G.
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

2018-10-12 Thread Daniel Richard G.
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

2018-08-15 Thread Daniel Richard G.
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

2018-08-14 Thread Daniel Richard G.
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

2018-08-09 Thread Daniel Richard G.
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

2018-08-05 Thread Daniel Richard G.
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

2018-08-05 Thread Daniel Richard G.
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

2018-08-03 Thread Daniel Richard G.
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

2018-08-03 Thread Daniel Richard G.
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

2018-08-03 Thread Daniel Richard G.
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

2018-08-03 Thread Daniel Richard G.
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

2018-07-30 Thread Daniel Richard G.
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

2018-07-30 Thread Daniel Richard G.
/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

2018-07-30 Thread Daniel Richard G.
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

2018-07-30 Thread Daniel Richard G.
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

2018-07-30 Thread Daniel Richard G.
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

2018-07-29 Thread Daniel Richard G.
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

2018-07-29 Thread Daniel Richard G.
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

2018-07-29 Thread Daniel Richard G.
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

2018-07-29 Thread Daniel Richard G.
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

[Bug 1372113] Re: flashplayer does not work due missing apparmor rule

2018-07-29 Thread Daniel Richard G.
The current Firefox AppArmor profile includes the "openssl" abstraction,
which allows access to /etc/ssl/openssl.cnf. This bug should no longer
be present in Ubuntu.

** 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/1372113

Title:
  flashplayer does not work due missing apparmor rule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1372113/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 885211] Re: firefox generates apparmor violations

2018-07-29 Thread Daniel Richard G.
Does this issue still occur with Firefox 60 or later? I am unable to
reproduce it on 18.04/bionic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885211

Title:
  firefox generates apparmor violations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/885211/+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

2018-07-29 Thread Daniel Richard G.
I think we could really use some kind of conditional construct (IF ...
THEN ...) in AppArmor syntax. Everything being talking about here
should, ideally, be adjustable using tunables. With a debconf
configuration option, even.

Between users who want strict access control to user files, and users
who don't know "how to computer," there's no way we're going to get
agreement on a default configuration that satisfies the former. The best
outcome, then, is to make tightening up the access easy, and editing
lines in the guts of profile and abstraction files IMO does not measure
up to that.

-- 
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 911540] Re: about:memory displays a weird error due to lacking access to /proc/self/smaps

2018-07-29 Thread Daniel Richard G.
For the record, Firefox 61 very much does continue to make use of
/proc//smaps (and /proc//statm) when using the about:memory
page.

I confirmed this by experimentally commenting out the AppArmor rules for
those two /proc files (motivated by comment #3 above), and subsequently
observed AppArmor denials. However, the about:memory page still
displayed the memory summary, and no error message came up at all.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911540

Title:
  about:memory displays a weird error due to lacking access to
  /proc/self/smaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/911540/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783057] [NEW] Allow support of Secure Boot without touching NVRAM

2018-07-22 Thread Daniel Richard G.
Public bug reported:

This concerns shim 13-0ubuntu2 in Ubuntu 18.04/bionic.

(Note: I am not entirely clear on whether this issue belongs to shim, or
to grub2; please redirect as appropriate.)

I am installing Ubuntu with EFI support with the following two
prerequisites:

  1. No changes are made to NVRAM (the system boots via e.g. "ATA HDD0"
instead of a dedicated boot option);

  2. The EFI removable media path (BOOT/BOOTX64.EFI) is used. (This is
kind of required by #1)

I have confirmed that this arrangement can be booted in Secure Boot mode
if the following two changes are made:

  1. BOOT/fbx64.efi is removed, to eliminate boot-loop behavior (same
issue as in https://launchpad.net/bugs/1750351, only unlocking the boot
order is not an option), and

  2. grubx64.efi and grub.cfg are copied from ubuntu/ into BOOT/ (as
BOOTX64!shim otherwise complains about not being able to find grubx64).

I would like for it to be possible to install Ubuntu in Secure Boot mode
in this manner, as the current approach effectively negates the intent
of the update_nvram=false debconf selection.

** Affects: shim (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/1783057

Title:
  Allow support of Secure Boot without touching NVRAM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1783057/+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

2018-07-22 Thread Daniel Richard G.
I should point out that on the Debian side, the same conditional exists
in the postinst script, so this same issue occurs there as well. (Only
with the /boot/efi/EFI/debian/ directory, of course.)

-- 
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] [NEW] grub-efi-amd64 postinst fails to install GRUB if /boot/efi/EFI/ubuntu/ is not present

2018-07-22 Thread Daniel Richard G.
Public bug reported:

This concerns grub-efi-amd64 2.02-2ubuntu8.1 in Ubuntu 18.04/bionic.

When the grub-efi-amd64 package is initially installed on a system that
has not previously booted via the Ubuntu EFI bootloader (so /boot/efi/
is either empty, or at least does not have a /boot/efi/EFI/ubuntu/
directory), the package postinst script fails to install anything into
/boot/efi/.

The postinst script, in fact, contains this conditional around the grub-
install invocation:

if [ "$bootloader_id" ] && [ -d "/boot/efi/EFI/$bootloader_id" ];
then

It's not clear why this is here. There might be a reason why you would
not want to install/update the bootloader if the directory for it isn't
already there. In my case, however, I am running the postinst script
(via dpkg-reconfigure) precisely to populate an EFI partition from
scratch.

I can work around this issue with a simple

# mkdir -p /boot/efi/EFI/ubuntu

before running dpkg-reconfigure, but this is far from obvious.

An additional problem with the conditional is that if it fails, no
message is given to the user that the postinst is omitting the GRUB
install, let alone the reason why. If the user misses the absence of the
grub-install message, they'll only find out something went wrong when
they attempt to boot using the newly-installed bootloader and it doesn't
work.

** 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/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 425979] Re: [UEFI boot only] Holding shift fails to display grub2 menu

2018-07-22 Thread Daniel Richard G.
Hello everyone,

There is a bug report similar to this one on the Debian side:

https://bugs.debian.org/902928

There, Colin Watson made an interesting comment:

> When I last looked into this, this wasn't possible with UEFI: the
> firmware doesn't tell us about held modifier keys.  You'll probably need
> to use a short but non-zero timeout and press Escape instead.
>
> (It's possible that more recent versions of the UEFI spec have improved
> this; but if so then somebody would need to implement that in GRUB, and
> it would still only work if you had new enough firmware.)

So it would seem that the old way of bringing up the GRUB menu by
holding down the Shift key just doesn't work in this brave new UEFI
world anymore.

It would be interesting to hear if anyone is aware of a system that
boots in UEFI mode and *does* respond to the held Shift key. Currently,
I don't believe it's clear as to whether this is an architectural
limitation of UEFI (i.e. it can't be fixed), or if newer UEFI firmware
versions could potentially make held modifier keys usable.

** Bug watch added: Debian Bug tracker #902928
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902928

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/425979

Title:
  [UEFI boot only] Holding shift fails to display grub2 menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/425979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782843] [NEW] Error spam when pulseaudio is not active

2018-07-20 Thread Daniel Richard G.
Public bug reported:

This concerns xfce4-pulseaudio-plugin 0.4.1-0ubuntu1 in Ubuntu
18.04/bionic.

In an Xfce desktop session, when this package is installed, and
Pulseaudio is not active, I see a steady procession of these messages in
~/.xsession-errors:


(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:20.688: Disconected 
from the PulseAudio server. Attempting to reconnect in 5 seconds.

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:20.689:
pa_context_connect() failed: Access denied

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:25.688:
Disconected from the PulseAudio server. Attempting to reconnect in 5
seconds.

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:25.689:
pa_context_connect() failed: Access denied

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:30.687:
Disconected from the PulseAudio server. Attempting to reconnect in 5
seconds.

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:30.688:
pa_context_connect() failed: Access denied

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:35.687:
Disconected from the PulseAudio server. Attempting to reconnect in 5
seconds.

(wrapper-2.0:2036): pulseaudio-plugin-WARNING **: 17:00:35.688: 
pa_context_connect() failed: Access denied


If the plugin is going to poll for Pulseaudio, it should print a warning
at most once. An alternative reasonable behavior could be to exit
altogether (since a PA volume control is useless without PA).

** Affects: xfce4-pulseaudio-plugin (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/1782843

Title:
  Error spam when pulseaudio is not active

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1782843/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782641] Re: Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian

2018-07-20 Thread Daniel Richard G.
Dimitri, thank you for laying out the rationale behind the package name.

Since there is good reason for things to be the way they are here, I've
opened a bug on the Debian side for them to address the naming
inconsistency:

https://bugs.debian.org/904152

** Bug watch added: Debian Bug tracker #904152
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904152

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782641

Title:
  Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring"
  for consistency with Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1782641/+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

2018-07-20 Thread Daniel Richard G.
This issue can be addressed with a manual action, but first you have to
dig into the scripts to diagnose the problem, and really if resolvconf
is installed then it should just work.

Part of this setup involves disabling systemd-resolved, in favor of a
"direct" /etc/resolv.conf, to match the network configuration of other
systems at my site. We've also found resolvconf to be a good solution to
allow flexibility in how the dynamic resolv.conf file is assembled.

There are at least two issues that I can see here:

1. When there is more than one script in /etc/dhcp/dhclient-enter-
hooks.d/ that defines the make_resolv_conf() shell function, the last
definition is the one that "wins." If the "resolvconf" script is renamed
to e.g. "zz-resolvconf", then it works correctly. This may be a case for
renaming systemd's "resolved" script to something like "00resolved"
(borrowing an idea from /etc/X11/Xsession.d/), since it is always
present in an out-of-the-box install.

2. The "resolved" script takes effect if the /lib/systemd/systemd-
resolved executable is present, when it should probably also check that
systemd-resolved is enabled. Currently, the script runs even if systemd-
resolved is not active, effectively turning into a no-op (albeit a no-op
that clobbers resolvconf's functionality).

   That would also fix another use case, where systemd-resolved is
disabled and resolvconf is absent. In that scenario, the default
make_resolv_conf() function from /sbin/dhclient-script should be used.

-- 
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 1782641] [NEW] Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian

2018-07-19 Thread Daniel Richard G.
Public bug reported:

The package that Ubuntu calls "ubuntu-keyring" is present in Debian as
"ubuntu-archive-keyring".

Debian has separate "debian-keyring" and "debian-archive-keyring"
packages, described as follows:

d-k: GnuPG keys of Debian Developers and Maintainers
d-a-k: GnuPG archive keys of the Debian archive

IMO this is a reasonable distinction, as the keys of
developers/maintainers are rarely needed by end users, and the d-k
package is significantly larger (on the order of 30 MB).

Thus, the current "ubuntu-keyring" package would be better named
"ubuntu-archive-keyring", not only so that the equivalent package has
the same name in both distros, but also to maintain the same distinction
between developer keys and archive keys. (Ubuntu could potentially
decide to ship a package containing Ubuntu developer keys in the future,
and it would be awkward if this needed to be named e.g. "ubuntu-devel-
keyring" or the like.)

** Affects: ubuntu-keyring (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/1782641

Title:
  Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring"
  for consistency with Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1782641/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782275] [NEW] Conflict between resolvconf and systemd-resolved dhclient scripts

2018-07-17 Thread Daniel Richard G.
Public bug reported:

I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead of
netplan, as the latter does not meet my needs. I am using resolvconf to
update /etc/resolv.conf from DHCP, as in earlier releases.

Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to
/run/resolvconf/resolv.conf) being updated; it is only the boilerplate
from /etc/resolvconf/resolv.conf.d/head with no server information
appended. (My "base" and "tail" files are empty.)

I poked around the scripts in /etc, and believe I have found the
problem.

When resolvconf is installed, the following two files are present:

/etc/dhcp/dhclient-enter-hooks.d/resolvconf
/etc/dhcp/dhclient-enter-hooks.d/resolved

Both of these scripts define the make_resolv_conf() shell function. What
I am seeing is that dhclient runs these two scripts in the
(alphabetical) order shown, and as the resolved script runs second, it
overwrites the resolvconf version of the shell function with its own. As
a result, dhclient does not invoke the appropriate update command for
resolvconf, even though the hook script was installed correctly.

Normally, I would remove the package that is providing the "resolved"
script, but this package is systemd, which cannot be removed. I am not
sure which of the two packages (resolvconf or systemd) needs to make an
accommodation for the other, but it is clear that the current approach
does not work.

** Affects: resolvconf (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: systemd (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/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 1782274] [NEW] resolvconf package needs dependency on ifupdown

2018-07-17 Thread Daniel Richard G.
Public bug reported:

When I install resolvconf on a minimal install of Ubuntu 18.04 (bionic),
I see this:

# apt-get install resolvconf
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  resolvconf
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/48.2 kB of archives.
After this operation, 187 kB of additional disk space will be used.
Preconfiguring packages ...
/tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: not 
found
/tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: not 
found
Selecting previously unselected package resolvconf.
(Reading database ... 90542 files and directories currently installed.)
Preparing to unpack .../resolvconf_1.79ubuntu10_all.deb ...
Unpacking resolvconf (1.79ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up resolvconf (1.79ubuntu10) ...
/var/lib/dpkg/info/resolvconf.config: 13: /var/lib/dpkg/info/resolvconf.config: 
ifquery: not found
/var/lib/dpkg/info/resolvconf.config: 13: /var/lib/dpkg/info/resolvconf.config: 
ifquery: not found
Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service → 
/lib/systemd/system/resolvconf.service.
Created symlink 
/etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path
 → /lib/systemd/system/resolvconf-pull-resolved.path.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting 
it.
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for resolvconf (1.79ubuntu10) ...


The "ifquery" program is provided by the ifupdown package. Therefore, 
resolvconf needs to include ifupdown in its Depends: clause. (Currently, 
ifupdown is mentioned in Enhances:)

** Affects: resolvconf (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/1782274

Title:
  resolvconf package needs dependency on ifupdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782274/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 684280] Re: casper toram forgets to disconnect loop device

2018-07-02 Thread Daniel Richard G.
Philip Susi: Confirmed with the Bionic live CD:

root@xubuntu:~# cat /proc/cmdline 
BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper 
iso-scan/filename=/linux/xubuntu-18.04-desktop-amd64.iso toram

root@xubuntu:~# umount /isodevice 
umount: /isodevice: target is busy.

root@xubuntu:~# losetup -d /dev/loop0

root@xubuntu:~# umount /isodevice 
(succeeds)

However, I did not observe the issue as originally reported; Ubiquity
was able to install the system even with /isodevice mounted and unable
to be unmounted. (In my case, the ISO file was on a USB thumbdrive, and
I installed to a hard drive.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280

Title:
  casper toram forgets to disconnect loop device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/684280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766317] Re: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

2018-04-25 Thread Daniel Richard G.
This bug appears to have been fixed in 8.32.0-1ubuntu4. Looks like this
was an issue with the Apparmor profile.

rsyslog (8.32.0-1ubuntu4) bionic; urgency=medium

  [ Jamie Strandboge ]
  * debian/usr.sbin.rsyslogd: updates for bionic (LP: #1766600)
- allow rsyslog modules in multiarch directories
- allow writing temporary pidfile

  [ Dimitri John Ledkov ]
  * Tolerate installing rsyslog, on systems without systemd installed. LP:
#1766574

 -- Dimitri John Ledkov   Tue, 24 Apr 2018 15:47:41
+0100

If anyone is still seeing this issue, please re-open.

** Changed in: rsyslog (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/1766317

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766317] Re: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

2018-04-24 Thread Daniel Richard G.
Hi Brian,

This is actually the same issue.

I am seeing the same error message quoted by the original reporter, but
that message is filtered through systemd---it is not direct output from
rsyslogd. What I provided was the direct output, that actually shows
what's going on.

I think this needs to be bumped up to at least High, as it breaks
logging.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766317

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766317] Re: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1

2018-04-23 Thread Daniel Richard G.
I am seeing this same error in Bionic. Some further telemetry:

# /usr/sbin/rsyslogd -n
rsyslog internal message (3,-2066): could not load module 
'/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so', dlopen: 
/usr/lib/x86_64-linux-gnu/rsyslog/lmnet.so: failed to map segment from shared 
object
 [v8.32.0 try http://www.rsyslog.com/e/2066 ]
Error during class init for object 'conf' - failing...
rsyslogd initializiation failed - global classes could not be initialized.
Did you do a "make install"?
Suggested action: run rsyslogd with -d -n options to see what exactly fails.
rsyslogd: run failed with error -2066 (see rsyslog.h or try 
http://www.rsyslog.com/e/2066 to learn what that number means)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766317

Title:
  package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766317/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

2018-04-05 Thread Daniel Richard G.
Thanks Dimitri, greatly appreciated. I haven't found many problems in my
testing of Bionic, but this is the juiciest one so far.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1731522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

2018-04-05 Thread Daniel Richard G.
Steve, Bionic still has the default (commented-out)

#DNSStubListener=udp

in /etc/systemd/resolved.conf .

I've noticed that this breaks Kerberos KDC lookup at a large site,
because the reply is quite large:

# host -t SRV _kerberos._udp.xxx.example.com
;; Connection to 127.0.0.53#53(127.0.0.53) for 
_kerberos._udp.xxx.example.com failed: connection refused.

# kinit u...@xxx.example.com
kinit: Cannot find KDC for realm "XXX.EXAMPLE.COM" while getting initial 
credentials

After setting DNSStubListener=yes:

# host -t srv _kerberos._udp.xxx.example.com
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx01.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx02.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx03.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx04.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx05.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx06.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx07.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx08.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx09.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx10.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx11.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx12.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx13.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx14.xxx.example.com.
_kerberos._udp.xxx.example.com has SRV record 0 100 88 
xxx15.xxx.example.com.

# kinit u...@xxx.example.com
Password for u...@xxx.example.com:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731522

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1731522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1722027] [NEW] Removing kernel packages leads to initrd regens, reboot-required

2017-10-07 Thread Daniel Richard G.
Public bug reported:

This concerns linux-base 4.0ubuntu1 in Ubuntu Xenial.

Removing Linux kernel packages from the system leads to initrd
generation and causes /var/run/reboot-required to appear. Neither of
these side effects should occur if only kernel packages older than the
running one are removed, a common operation in system maintenance.

Below is a terminal session illustrating the problem. Note the update-
initramfs lines indicating that an initrd is being (re)generated. The
removal process paused for a few seconds at these lines, because
generating an initrd is somewhat disk- and CPU-intensive. (Look closely
at the versions of the initrd that are generated---the system is
refreshing initrd files for the kernel versions that are being removed!)

 Terminal log begins 

# ls /var/run/reboot-required
ls: cannot access '/var/run/reboot-required': No such file or directory

# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  linux-headers-4.4.0-83* linux-headers-4.4.0-83-generic*
  linux-headers-4.4.0-87* linux-headers-4.4.0-87-generic*
  linux-headers-4.4.0-89* linux-headers-4.4.0-89-generic*
  linux-headers-4.4.0-91* linux-headers-4.4.0-91-generic*
  linux-image-4.4.0-83-generic* linux-image-4.4.0-87-generic*
  linux-image-4.4.0-89-generic* linux-image-4.4.0-91-generic*
  linux-image-extra-4.4.0-83-generic* linux-image-extra-4.4.0-87-generic*
  linux-image-extra-4.4.0-89-generic* linux-image-extra-4.4.0-91-generic*
0 upgraded, 0 newly installed, 16 to remove and 0 not upgraded.
After this operation, 1,188 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 353048 files and directories currently installed.)
Removing linux-headers-4.4.0-83-generic (4.4.0-83.106) ...
Removing linux-headers-4.4.0-83 (4.4.0-83.106) ...
Removing linux-headers-4.4.0-87-generic (4.4.0-87.110) ...
Removing linux-headers-4.4.0-87 (4.4.0-87.110) ...
Removing linux-headers-4.4.0-89-generic (4.4.0-89.112) ...
Removing linux-headers-4.4.0-89 (4.4.0-89.112) ...
Removing linux-headers-4.4.0-91-generic (4.4.0-91.114) ...
Removing linux-headers-4.4.0-91 (4.4.0-91.114) ...
Removing linux-image-extra-4.4.0-83-generic (4.4.0-83.106) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-96-generic
Found initrd image: /boot/initrd.img-4.4.0-96-generic
Found linux image: /boot/vmlinuz-4.4.0-93-generic
Found initrd image: /boot/initrd.img-4.4.0-93-generic
Found linux image: /boot/vmlinuz-4.4.0-92-generic
Found initrd image: /boot/initrd.img-4.4.0-92-generic
Found linux image: /boot/vmlinuz-4.4.0-91-generic
Found initrd image: /boot/initrd.img-4.4.0-91-generic
Found linux image: /boot/vmlinuz-4.4.0-89-generic
Found initrd image: /boot/initrd.img-4.4.0-89-generic
Found linux image: /boot/vmlinuz-4.4.0-87-generic
Found initrd image: /boot/initrd.img-4.4.0-87-generic
Found linux image: /boot/vmlinuz-4.4.0-83-generic
Found initrd image: /boot/initrd.img-4.4.0-83-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
Purging configuration files for linux-image-extra-4.4.0-83-generic 
(4.4.0-83.106) ...
Removing linux-image-4.4.0-83-generic (4.4.0-83.106) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
update-initramfs: Deleting /boot/initrd.img-4.4.0-83-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-96-generic
Found initrd image: /boot/initrd.img-4.4.0-96-generic
Found linux image: /boot/vmlinuz-4.4.0-93-generic
Found initrd image: /boot/initrd.img-4.4.0-93-generic
Found linux image: /boot/vmlinuz-4.4.0-92-generic
Found initrd image: /boot/initrd.img-4.4.0-92-generic
Found linux image: /boot/vmlinuz-4.4.0-91-generic
Found initrd image: /boot/initrd.img-4.4.0-91-generic
Found 

[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-07-07 Thread Daniel Richard G.
Confirmed that this fixes the segfault for me when applied to version
3.20.0. Thanks :)

(Figured this would be easy to reproduce...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-07-06 Thread Daniel Richard G.
Er...

$ klist -v
klist: invalid option -- 'v'
Usage: klist [-e] [-V] [[-c] [-l] [-A] [-d] [-f] [-s] [-a [-n]]] [-k [-t] 
[-K]] [name]
[...]

Remember, the segfault occurs with a user that is local-only. Kerberos
infrastructure is installed on the system, but the user has no Kerberos
tickets, no Kerberos envvars set, no cache file, nothing at all.

$ klist
klist: Credentials cache file '/tmp/krb5cc_1000' not found

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-07-05 Thread Daniel Richard G.
Hi Guido, I think you mean "klist -V" (uppercase) :-)

On the system in question, that returns

$ klist -V
Kerberos 5 version 1.13.2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-06-29 Thread Daniel Richard G.
Attached is a Valgrind log file produced from a debug build of k-a-d
version 3.20.0.

All the errors appear to be accesses within freed memory...

** Attachment added: "kad-valgrind-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+attachment/4906188/+files/kad-valgrind-log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-06-27 Thread Daniel Richard G.
Hunh. How odd... I can't imagine that there would be something
particular to this system that is causing the crash. As you requested:

skunk@darkstar:/tmp/krb5-auth-dialog-3.20.0/_build/src$ G_MESSAGES_DEBUG=all 
./krb5-auth-dialog -a
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
principal: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pk-userid: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pk-anchors: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pw-prompt-mins: 30
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-forwardable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-proxiable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-renewable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
conf-tickets: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
principal: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pk-userid: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pk-anchors: 
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
pw-prompt-mins: 30
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-forwardable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-proxiable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
tgt-renewable: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_set_property: 
conf-tickets: False
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_local_command_line: 
Parsing local command line
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_startup: Primary 
application
(krb5-auth-dialog:16500): Gtk-DEBUG: Connecting to session manager
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_nm_client_state_changed_cb: 
Network connected
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: monitor_ccache: Monitoring 
/tmp/krb5cc_1000
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: ka_applet_command_line: 
Evaluating command line
(krb5-auth-dialog:16500): KrbAuthDialog-DEBUG: credentials_expiring: Checking 
expiry <1800s
Segmentation fault (core dumped)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 643623] Re: Should ubuntu-keyring include the debug archive key?

2017-06-26 Thread Daniel Richard G.
Thank you Dimitry, that is a helpful link.

I've removed the key-file attachment from comment #5, but am unable to
otherwise edit/remove the text.

** Attachment removed: "dbgsym-release-key.asc"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+attachment/4903350/+files/dbgsym-release-key.asc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643623

Title:
  Should ubuntu-keyring include the debug archive key?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] Re: "krb5-auth-dialog --auto" segfaults on startup

2017-06-26 Thread Daniel Richard G.
I'm afraid I see the same failure mode with 3.20. The GDB session is
below.

(You're not able to reproduce this? This is a system with all the
Kerberos infrastructure, but a local-only user---no KRB* envvars set)


$ gdb --args /tmp/krb5-auth-dialog-3.20.0/_build/src/krb5-auth-dialog --auto
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/tmp/krb5-auth-dialog-3.20.0/_build/src/krb5-auth-dialog...done.
(gdb) r
Starting program: /tmp/krb5-auth-dialog-3.20.0/_build/src/krb5-auth-dialog 
--auto
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe9bf6700 (LWP 5105)]
[New Thread 0x7fffe93f5700 (LWP 5106)]
[New Thread 0x7fffe895a700 (LWP 5107)]
[New Thread 0x7fffdbdb9700 (LWP 5108)]

Thread 1 "krb5-auth-dialo" received signal SIGSEGV, Segmentation fault.
0x77928b8f in krb5_cc_resolve (context=0x99df40, 
name=0x95a130 "Broadway", id=0x7fffda90) at cache.c:270
270 cache.c: No such file or directory.
(gdb) bt
#0  0x77928b8f in krb5_cc_resolve (context=0x99df40, 
name=0x95a130 "Broadway", id=0x7fffda90) at cache.c:270
#1  0x00409aae in ka_get_tgt_from_ccache (context=0x99df40, 
creds=0x7fffdb90) at ../../src/ka-kerberos.c:897
#2  0x0040804c in credentials_expiring_real (applet=0x6c7190)
at ../../src/ka-kerberos.c:227
#3  0x00408c2e in credentials_expiring (data=0x6c7190)
at ../../src/ka-kerberos.c:531
#4  0x00408cc7 in credentials_expiring_once (data=0x6c7190)
at ../../src/ka-kerberos.c:547
#5  0x7604e04a in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7604e3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7604e49c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x76615e30 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x0040cd28 in main (argc=2, argv=0x7fffdf18)
at ../../src/ka-applet.c:1252
(gdb) up
#1  0x00409aae in ka_get_tgt_from_ccache (context=0x99df40, 
creds=0x7fffdb90) at ../../src/ka-kerberos.c:897
897 if (krb5_cc_default (context, ))
(gdb) p kcontext_valid
$1 = 0
(gdb)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1700468] [NEW] "krb5-auth-dialog --auto" segfaults on startup

2017-06-26 Thread Daniel Richard G.
Public bug reported:

This concerns krb5-auth-dialog 3.12.0-2 in Ubuntu Xenial.

When the program is invoked with the --auto option, it briefly maps the
systray icon, and then segfaults.

Here is a GDB session running on a debug build of the original package
source:

$ gdb --args 
/tmp/krb5-auth-dialog-3.12.0/debian/krb5-auth-dialog/usr/bin/krb5-auth-dialog 
--auto
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/tmp/krb5-auth-dialog-3.12.0/debian/krb5-auth-dialog/usr/bin/krb5-auth-dialog...done.
(gdb) r
Starting program: 
/tmp/krb5-auth-dialog-3.12.0/debian/krb5-auth-dialog/usr/bin/krb5-auth-dialog 
--auto
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe9bf6700 (LWP 28626)]
[New Thread 0x7fffe93f5700 (LWP 28627)]
[New Thread 0x7fffe3fff700 (LWP 28630)]
[New Thread 0x7fffe37fe700 (LWP 28631)]

Thread 1 "krb5-auth-dialo" received signal SIGSEGV, Segmentation fault.
0x77928b8f in krb5_cc_resolve (context=0x9f58a0, name=0x96f600 "am", 
id=0x7fffda60) at cache.c:270
270 cache.c: No such file or directory.
(gdb) bt
#0  0x77928b8f in krb5_cc_resolve (context=0x9f58a0, 
name=0x96f600 "am", id=0x7fffda60) at cache.c:270
#1  0x004095b2 in ka_get_tgt_from_ccache (context=0x9f58a0, 
creds=0x7fffdb60)
at /tmp/krb5-auth-dialog-3.12.0/./src/ka-kerberos.c:886
#2  0x00407d4b in credentials_expiring_real (applet=0x6be190)
at /tmp/krb5-auth-dialog-3.12.0/./src/ka-kerberos.c:216
#3  0x00408895 in credentials_expiring (data=0x6be190)
at /tmp/krb5-auth-dialog-3.12.0/./src/ka-kerberos.c:520
#4  0x004088e4 in credentials_expiring_once (data=0x6be190)
at /tmp/krb5-auth-dialog-3.12.0/./src/ka-kerberos.c:536
#5  0x7604e04a in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7604e3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7604e49c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x76615e30 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x0040c4b9 in main (argc=2, argv=0x7fffdee8)
at /tmp/krb5-auth-dialog-3.12.0/./src/ka-applet.c:1235
(gdb) p context
$1 = (krb5_context) 0x9f58a0
(gdb) p *context
$2 = {etypes = 0x80101026c, etypes_des = 0x3502b8, 
  as_etypes = 0x500730106, tgs_etypes = 0x33312e313a, 
  permitted_enctypes = 0x700750105, default_realms = 0x7328610500670108, 
  max_skew = 10611, kdc_timeout = 17187406087, host_timeout = 825110842, 
  max_retries = 7536896, kdc_sec_offset = 23, kdc_usec_offset = 778531439, 
  cf = 0x522e69707374612e, et_list = 0x79727473696765, 
  warn_dest = 0x2400730102, debug_dest = 0x793131612e67726f, 
  cc_ops = 0x442e69707374612e, num_cc_ops = 1667855973, 
  http_proxy = 0x6f72746e6f43746e , 
  time_fmt = 0x72656c6c , 
  log_utc = 7536899, 
  default_keytab = 0x6369766544746547 , 
  default_keytab_modify = 0x694c746e65764565 , use_admin_kdc = 1852142707, 
  extra_addresses = 0x1000100, scan_interfaces = 1, srv_lookup = 1, 
  srv_try_txt = 0, fcache_vno = 0, num_kt_types = 6, kt_types = 0x96ff70, 
  date_fmt = 0x7796b758 "%Y-%m-%d", error_string = 0x0, error_code = 0, 
  ignore_addresses = 0x0, default_cc_name = 0x96f600 "am", 
  default_cc_name_env = 0x0, default_cc_name_set = 0, mutex = 0x9f4720, 
  large_msg_size = 1400, max_msg_size = 1024000, tgs_negative_timeout = 0, 
  flags = 39, send_to_kdc = 0x0, hx509ctx = 0x0, num_kdc_requests = 0, 
  name_canon_rules = 0x0}


As you can see, the Kerberos context object appears not to have been properly 
initialized.

** Affects: krb5-auth-dialog (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/1700468

Title:
  "krb5-auth-dialog --auto" segfaults on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5-auth-dialog/+bug/1700468/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 643623] Re: Should ubuntu-keyring include the debug archive key?

2017-06-26 Thread Daniel Richard G.
I agree on this key needing to be available in the/an official Ubuntu
keyring package.

For now, because the original key file is not even accessible via HTTPS,
I am attaching a copy of it here. The file is dated 2016-07-04 16:10,
and has the following SHA{256,512} hashes:

4a54623d5ec01d098441a42413d5d176c3292113aed9d274ac18ddaec50b76ce  
dbgsym-release-key.asc
728caec72fa2062f6d931a2c231433ee7dd0181d10d59ac6ec2afe90abc4cf17e3c9a7a4e82430ffdbd850eb68557bd33c1882e7de1dd93bc9b8dbbc61119f82
  dbgsym-release-key.asc

Original location: http://ddebs.ubuntu.com/dbgsym-release-key.asc

If anyone sees a difference with the original, please speak up.

** Attachment added: "dbgsym-release-key.asc"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+attachment/4903350/+files/dbgsym-release-key.asc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643623

Title:
  Should ubuntu-keyring include the debug archive key?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/643623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


  1   2   3   4   5   6   7   8   9   >