[Bug 1871030]

[Forest]

Alternative workaround step 2, leaving system config files untouched:

Copy /usr/share/dbus-1/services/org.kde.kdeconnect.service to
~/.local/share/dbus-1/services/ and change the Exec= line of the copy to
Exec=/usr/bin/false

When combined with step 1 of my workaround, this prevents kdeconnectd
from launching in that user's sessions. It adds some clutter to the
session log, as dbus-daemon complains that the executable is failing,
but it gives up after several tries and seems to remain quiet after
that.

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

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


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

[Bug 1871030]

[Forest]

I found some (ugly) workarounds for the unwanted kdeconnectd autostart.

The process seems to be launched at session startup time from two
distinct places:

1. /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop

This can be disabled for individual users by copying the file to each
user's ~/.config/autostart/ directory and adding Hidden=true to the
[Desktop Entry] section of the copies.

Alternatively, it can be disabled by default by adding a line like this to the 
file's [Desktop Entry] section:
  X-KDE-autostart-condition=kdeconnectd-autostartrc:General:Autostart:false
Then, to re-enable it for a particular user, create a 
~/.config/kdeconnectd-autostartrc file with Autostart=true in its [General] 
section. (The file name "kdeconnectd-autostartrc" is arbitrary; I chose it in 
hopes of avoiding conflicts with any standard files.)

2. /usr/share/dbus-1/services/org.kde.kdeconnect.service

According to KDE docs*, this file tells every user's dbus session to launch 
kdeconnectd if something tries to contact it over d-bus. With this file in 
place, kdeconnectd is launched by systemd at session start even if a user 
disables the autostart .desktop file. The file can be moved to a backup 
directory to avoid this. However, I think a better fix would be to identify 
whatever is making org.kde.kdeconnect d-bus requests at session startup, and 
prevent that instead.
* https://develop.kde.org/docs/use/d-bus/dbus_autostart_services/

Of course, these workarounds are hackish, and will probably revert to
the normal (unwanted) behavior whenever KDE Connect package updates are
installed. What we really need is for it to be configurable in the first
place. Seems like a good fit for the Background Services panel.

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

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


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

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Forest]

The effectively forced use of Snap is what finally drove me to abandon
Ubuntu. This issue played a part in that.

To be clear, I am in favor of app isolation on desktop linux, and I find
container-based packaging useful in certain situations. However, the
Snap project has demonstrated over and over again that the people
driving it fail to grasp important issues like user agency and open
systems. Like Alex, I find the result intolerable. Being rid of it was
worth the temporary pain of switching distros.

So long, Ubuntu, and thanks for all the fish.

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

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

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


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

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Forest]

Thank you, Ivan. I have add my "affects me" status and a comment there.

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

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

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


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

[Bug 1965535] Re: Stop recommending snap

[Forest]

+1

For the record, Snap being forced upon users for critical packages is
the primary reason why I recently dropped Ubuntu and stopped
recommending the distro to others, after using it for over 15 years.

Container-based packaging has its place. Snap has some interesting
features compared to FlatPak and AppImage. However, none of them are
suitable replacements for deb & apt, and this is really driven home when
they're used for core packages like the web browser. Snap in particular
has multiple fundamental design and implementation problems that make it
intolerable.

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

Title:
  Stop recommending snap

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


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

[Bug 1871030]

[Forest]

> unable to communicate with the first paired instance

The word "paired" should have been in parentheses. I don't know what ate
them. To be clear, only one user has paired KDE Connect with the Android
app, yet the second user's kdeconnectd instance makes the first instance
stop working. Unless there's another way to fix this, I think I need a
way to disable kdeconnectd for the second user.

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

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


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

[Bug 1871030]

[Forest]

+1 for adding the option on a per-user basis. It's not just a matter of
convenience; the lack of this option breaks KDE Connect on my multiuser
system: As soon as a second desktop session is started, the new
kdeconnectd instance seems to steal the Android app's attention, leaving
it unable to communicate with the first paired instance.

I tried copying /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop to
the second user's ~/.config/autostart/ and adding Hidden=true, as
specified in the freedesktop spec. It didn't help.

I tried renaming /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop.
It didn't help.

I searched for a systemd --user unit that I could disable. I didn't find
one.

This really should be a per-user option, listed in Background Services
along with all the others.

In the meantime, I would appreciate a workaround, if somebody knows of
one.

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

Title:
  There's no Option to Disable the Startup of KDEConnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions


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

[Bug 1873922] Re: 20.04 not compatible with virtualbox-guest-x11: Fails changing display

[Forest Darling]

I am running Xubuntu 20.04 as both my host and guest, and I ran into
this same issue. The root cause is that GCC is missing in the guest,
which is required to build the kernel modules. You can install it using
this command:

sudo apt-get install build-essential

Once it's installed, you need to at least attempt rebuilding the kernel
modules:

sudo /sbin/rcvboxadd quicksetup all

NOTE: previous versions of VirtualBox used the following command
instead:

sudo /sbin/vboxconfig

If trying to rebuild the modules doesn't work, try reinstalling
VirtualBox Guest Additions entirely (run these inside of the mounted
Guest Additions ISO directory):

cd /media/*/*/
sudo ./VBoxLinuxAdditions.run

Here are my software versions for reference:

On the host (Xubuntu 20.04):

lsb_release -r
Release:20.04

dpkg -l virtualbox virtualbox-guest-additions-iso
virtualbox  6.1.16-dfsg-6~ubuntu1.20.04.1
virtualbox-guest-additions-iso  6.1.16-1~ubuntu1.20.04.1

VirtualBox version from Help->About Dialog:
6.1.16_Ubuntu r140961

On the guest (Xubuntu 20.04):

lsb_release -r
20.04

VBoxClient --version
6.1.16r140961

gcc --version
9.3.0

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

Title:
  20.04 not compatible with virtualbox-guest-x11: Fails changing display

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

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

[Bug 1547589] Re: rtkit-daemon flooding syslog

[Forest]

** Bug watch added: github.com/heftig/rtkit/issues #22
   https://github.com/heftig/rtkit/issues/22

** Also affects: rtkit via
   https://github.com/heftig/rtkit/issues/22
   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/1547589

Title:
  rtkit-daemon flooding syslog

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

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

[Bug 1895765] Re: conversion to m4a fails

[Forest]

Upstream report:  https://sourceforge.net/p/gtkpod/bugs/334/

(I tried adding it the normal way, but Launchpad doesn't seem to
recognize sourceforge bug reports.)

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

Title:
  conversion to m4a fails

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

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

[Bug 1895765] [NEW] conversion to m4a fails

[Forest]

Public bug reported:

Conversion to .m4a silently fails 100% of the time.

Running the convert-2m4a.sh script manually reveals this error message
in conversion.log:

output file exists, use --overwrite option

Apparently gtkpod's conversion script is running faac on an already-
existing output file, which causes faac to fail since version 1.29.5,
when the --overwrite option was introduced.

Adding --overwrite to ENCODER_OPTS fixes the problem. (This might break
compatibility with faac versions more than three years old.) Patch
attached.

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

** Patch added: "0002-faac_overwrite.patch"
   
https://bugs.launchpad.net/bugs/1895765/+attachment/5411198/+files/0002-faac_overwrite.patch

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

Title:
  conversion to m4a fails

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

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

[Bug 1895408] [NEW] tmpfs man page is missing

[Forest]

Public bug reported:

The filesystems(5) man page refers to a tmpfs(5) man page, but that page
is not packaged on ubuntu focal. Please package
/usr/share/man/man5/filesystems.5.gz

** Affects: manpages (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/1895408

Title:
  tmpfs man page is missing

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

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

[Bug 1892592] [NEW] right click lag: desktop application menu is slow to appear

[Forest]

Public bug reported:

Since upgrading from xubuntu cosmic to disco, desktop right-click is now
laggy: The application menu that used to open instantly now takes around
300ms to appear. The problem is still present in xubuntu focal.

This is slow and annoying, not only because it makes xfce feel like a
bloated heavyweight desktop, but also because it interferes with quick
gesture-like application launches (click, drag, click) that used to be
possible without looking too closely at the mouse area of the screen.

The previous, fast behavior returns if I disable this option in Settings 
Manager:
Desktop: Menus: Desktop Menu: Show application icons in menu
Unfortunately, that also strips the applications menu of its icons.

Meanwhile, the window list menu (desktop middle-click) still opens
instantly, even with icons.

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


** Tags: regression-release

** Description changed:

  Since upgrading from xubuntu cosmic to disco, desktop right-click is now
  laggy: The application menu that used to open instantly now takes around
- 300ms to appear.
+ 300ms to appear. The problem is still present in xubuntu focal.
  
  This is slow and annoying, not only because it makes xfce feel like a
  bloated heavyweight desktop, but also because it interferes with quick
  gesture-like application launches (click, drag, click) that used to be
  possible without looking too closely at the mouse area of the screen.
  
  The previous, fast behavior returns if I disable this option in Settings 
Manager:
  Desktop: Menus: Desktop Menu: Show application icons in menu
  Unfortunately, that also strips the applications menu of its icons.
  
  Meanwhile, the window list menu (desktop middle-click) still opens
  instantly, even with icons.

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

Title:
  right click lag: desktop application menu is slow to appear

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

Patches refreshed for update-notifier 3.192.30, as published in Ubuntu
20.04 (focal).

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

** Patch added: "restore_reboot.patch"
   
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5397271/+files/restore_reboot.patch

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

** Patch removed: "restore_icon.patch"
   
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5038130/+files/restore_icon.patch

** Patch removed: "restore_reboot.patch"
   
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5038131/+files/restore_reboot.patch

** Patch added: "restore_icon.patch"
   
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5397270/+files/restore_icon.patch

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

I hate to say this, folks, but ecryptfs looks like a dead end for us.
It's no longer supported by Ubuntu (the package has been moved to the
Universe repo). Also, the problem at hand is caused by systemd, which is
run by a man famous for releasing poorly-vetted, system-breaking
software, and then refusing to fix the damage he causes.

For a year or so, I maintained a systemd patch to work around this bug.
(It is posted above, but no longer applies to current systemd code.)
There was a time when it looked like the problem was finally fixed
upstream, but then it just broke again.

Anyone who (like me) has been using ecryptfs to encrypt a private directory and 
unlock it only when needed, might consider switching to gocryptfs.  From a 
user's point of view, it works similarly to ecryptfs.  There's also a handy GUI 
called SiriKali that works with it.
https://nuetzlich.net/gocryptfs/
https://mhogomchungu.github.io/sirikali/

Good luck.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1877219] Re: dozens of empty grilo-plugin-cache folders polluting /tmp

[Forest]

** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #70
   https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70

** Also affects: grilo-plugins via
   https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70
   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/1877219

Title:
  dozens of empty grilo-plugin-cache folders polluting /tmp

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1877219/+subscriptions

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

[Bug 1877219] [NEW] dozens of empty grilo-plugin-cache folders polluting /tmp

[Forest]

Public bug reported:

My /tmp folder has dozens of empty folders with names like grilo-plugin-
cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
can do their job without leaving endless garbage directories behind when
they're done?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

$ dpkg-query --show grilo-plugins-0.3-base
grilo-plugins-0.3-base:amd640.3.9-1ubuntu1

** Affects: grilo-plugins (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  My /tmp folder has dozens of empty folders with names like grilo-plugin-
  cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
  can do their job without leaving endless garbage directories behind when
  they're done?
+ 
+ $ lsb_release -a
+ No LSB modules are available.
+ Distributor ID:   Ubuntu
+ Description:  Ubuntu 19.10
+ Release:  19.10
+ Codename: eoan
+ 
+ $ dpkg-query --show grilo-plugins-0.3-base
+ grilo-plugins-0.3-base:amd64  0.3.9-1ubuntu1

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

Title:
  dozens of empty grilo-plugin-cache folders polluting /tmp

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

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

[Bug 1866124] Re: ps -eo lxc no longer shows a task's lxc container

[Forest]

The top command's LXC column (not shown by default, but can be enabled
through the 'f' menu) also shows a - for all processes, including those
that belong to containers.

My containers are unprivileged, in case that matters.

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

Title:
  ps -eo lxc no longer shows a task's lxc container

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

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

[Bug 1866124] [NEW] ps -eo lxc no longer shows a task's lxc container

[Forest]

Public bug reported:

When I use the ps command's "lxc" format specifier, for example:

ps -eo pid,lxc,command

The second output column is supposed to show "the name of the lxc
container within which a task is running.  If a process is not running
inside a container, a dash ('-') will be shown." [1]

This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
brought me from lxc 3.03 to 3.04.  Now, that column always contains a
dash instead of the container name, even for processes that are running
inside a container.  The "lxc" format specifier seems to be broken now.

[1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers

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

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

** Also affects: lxc (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  When I use the ps command's "lxc" format specifier, for example:
  
  ps -eo pid,lxc,command
  
  The second output column is supposed to show "the name of the lxc
  container within which a task is running.  If a process is not running
  inside a container, a dash ('-') will be shown." [1]
  
- This worked fine until I upgraded from ubuntu 19.04 to 19.10.  Now, that
- column always contains a dash instead of the container name, even for
- processes that are running inside a container.  The "lxc" format
- specifier seems to be broken now.
+ This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
+ brought me from lxc 3.03 to 3.04.  Now, that column always contains a
+ dash instead of the container name, even for processes that are running
+ inside a container.  The "lxc" format specifier seems to be broken now.
  
- 
- [1] 
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
+ [1]
+ 
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers

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

Title:
  ps -eo lxc no longer shows a task's lxc container

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

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

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Forest]

P.S.

Dear snap developers,

I do feel some empathy for you.  You're trying to build something good,
and share it with people.  Taking heat while doing that mostly thankless
job is tough.  So, thank you for your efforts.

I chose not to censor my previous comment, though, because I have found
that downplaying the significance of a problem is counterproductive in
the long run.  Things don't get fixed if the people who can fix them
don't understand how problematic they are.

I can't wait another four years.  Looks like I'm going to have to either
find another way to use chromium on ubuntu, or else finally replace
ubuntu.

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

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

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

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

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Forest]

I discovered this today when the ubuntu 19.10 upgrade replaced my
chromium package with a snap, thereby creating this alien directory in
my home dir.  I believe my exact words were, "are you fucking kidding
me?"

> at the end it's pure aesthetics.

Wrong.  It obstructs tab completion in command lines and keyboard
navigation in file managers, which is something that I do thousands of
times per day.  This makes it a rather significant attack on usability.

Even for people who don't use keyboards, the additional clutter adds
cognitive load every time someone looks for a file or navigates to
another directory.  It also contributes to pushing other files off the
edge of file manager windows, thereby either requiring the user to
scroll to find things or to waste desktop space with larger file manager
windows.  You might think these to be minor effects, but that doesn't
excuse it, and they add up quickly.  Especially for the single most
visible directory in the entire system.

> echo snap >> ~/.hidden

That doesn't work my terminal or my Thunar (file manager) windows.

> "me too" is not really bringing anything to the discussion.

I normally agree, but this is a special case.  It would be difficult to
overstate how foolish this design decision was.  The flood of comments
serve as a clear demonstration of that, and will (hopefully) ensure that
the people responsible think more carefully before repeating their
mistake in the future.

Consider also that each "me too" here represents not just the person who
wrote it, but also multiple others who had the same reaction but didn't
bother (or don't know how) to come here and write about it.

While we're at it, not that there wouldn't be so many "me too" comments
if the snap folks hadn't left this problem unaddressed for nearly four
years.

Four. Years.

Okay, so fixing it properly is difficult because of your rigid design.
Okay, that happens; we all make mistakes.  But maybe consider
implementing a temporary fix early, so you don't leave people burdened
with your mistake while you take four freaking years to fix it properly?

I am in disbelief.

Amusingly, I happen to be evaluating container-style packaging systems
this week, with FlatPak and Snap on my short list because of their
sandboxing features.  The fact that this bug exists in the first place,
along with the fact that it has been allowed to persist for nearly four
years, has convinced me:  I'm not building anything with snap.

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

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

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

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

[Bug 913444]

[Forest]

Olivier, thank you. Getting rid of the remove() call looks like it would
fix the annoyance of having My Documents relocated every time I upgrade
wine or dxvk.

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

Title:
  Every wine update re-enables desktop integration links

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

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

[Bug 1797417]

[Forest]

Patch 9050 fixed the problem for me. Tested with volumeicon-alsa on
ubuntu 19.04.

Thanks, Ivan!

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

Title:
  Background of system tray icons not drawn properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-panel/+bug/1797417/+subscriptions

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

[Bug 1844781] [NEW] Thunar fails to scroll to the end of the file list

[Forest]

Public bug reported:

After upgrading from Ubuntu 18.04 to 19.04, Thunar's compact list view
often fails to scroll the last column fully into view.

** Affects: exo
 Importance: Medium
 Status: Confirmed

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


** Tags: disco patch-forwarded-upstream regression-release

** Bug watch added: Xfce Bugzilla #14737
   https://bugzilla.xfce.org/show_bug.cgi?id=14737

** Also affects: exo via
   https://bugzilla.xfce.org/show_bug.cgi?id=14737
   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/1844781

Title:
  Thunar fails to scroll to the end of the file list

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

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

[Bug 1844781] Re: Thunar fails to scroll to the end of the file list

[Forest]

** Patch added: "0003-restore-scroll-to-end.patch"
   
https://bugs.launchpad.net/exo/+bug/1844781/+attachment/5289901/+files/0003-restore-scroll-to-end.patch

** Tags added: disco regression-release

** Tags added: patch-forwarded-upstream

** Description changed:

  After upgrading from Ubuntu 18.04 to 19.04, Thunar's compact list view
- often fails to scroll to the end.
+ often fails to scroll the last column fully into view.

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

Title:
  Thunar fails to scroll to the end of the file list

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

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

[Bug 1844771] Re: Thunar interactive search sometimes stops accepting input after one character

[Forest]

** Tags added: disco patch-accepted-upstream regression-release

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

Title:
  Thunar interactive search sometimes stops accepting input after one
  character

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

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

[Bug 1844771] [NEW] Thunar interactive search sometimes stops accepting input after one character

[Forest]

Public bug reported:

Typing a file name in a thunar window (optionally pressing Ctrl+F first)
normally selects the file whose name matches the entered text. After
upgrading from Ubuntu 18.04 to 19.04, this feature started randomly
breaking after a single character is entered.

To reproduce (sometimes):

1. Open a thunar window to a directory full of files.
2. Before doing anything in that window, Alt+Tab to a different window.
3. Alt+Tab back again.
4. Type the name of a file in the open directory.
5. Notice that, sometimes, the input text box stops accepting input after the 
first letter of the file name.

** Affects: exo
 Importance: Medium
 Status: Fix Released

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

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


** Tags: disco patch-accepted-upstream regression-release

** Bug watch added: Xfce Bugzilla #15100
   https://bugzilla.xfce.org/show_bug.cgi?id=15100

** Also affects: thunar via
   https://bugzilla.xfce.org/show_bug.cgi?id=15100
   Importance: Unknown
   Status: Unknown

** Also affects: exo (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/1844771

Title:
  Thunar interactive search sometimes stops accepting input after one
  character

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

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

[Bug 1844771] Re: Thunar interactive search sometimes stops accepting input after one character

[Forest]

** Patch added: "0002-fix-typeahead.patch"
   
https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1844771/+attachment/5289892/+files/0002-fix-typeahead.patch

** Also affects: exo via
   https://bugzilla.xfce.org/show_bug.cgi?id=15100
   Importance: Unknown
   Status: Unknown

** No longer affects: thunar

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

Title:
  Thunar interactive search sometimes stops accepting input after one
  character

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

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

[Bug 1843490] [NEW] lxc.cgroup.devices.allow prevents unprivileged container from starting

[Forest]

Public bug reported:

Adding lxc.cgroup.devices.allow directives to an unprivileged container
config prevent the container from starting. These lxc-start errors look
relevant:


lxc-start testbox 20190910192712.171 WARN cgfsng - 
cgroups/cgfsng.c:get_hierarchy:204 - There is no useable devices controller
lxc-start testbox 20190910192712.171 ERRORcgfsng - 
cgroups/cgfsng.c:cg_legacy_set_data:2191 - Failed to setup limits for the 
"devices" controller. The controller seems to be unused by "cgfsng" cgroup 
driver or not enabled on the cgroup hierarchy
lxc-start testbox 20190910192712.171 WARN cgfsng - 
cgroups/cgfsng.c:__cg_legacy_setup_limits:2228 - Failed to set "devices.allow" 
to "c 10:57 rwm"


It seems to me that I used lxc.cgroup.devices.allow directives without trouble 
a few years ago. I wonder which system upgrades broke it.


To reproduce:

(Note: subuid, subgid, and lxc-usernet are already configured for this
user.)

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.04
Release:19.04
Codename:   disco

$ dpkg-query --show libpam-cgfs lxc1
libpam-cgfs 3.0.3-0ubuntu1
lxc13.0.3-0ubuntu1

$ lxc-create -t download -n testbox -- -d ubuntu -r bionic -a amd64
The cached copy has expired, re-downloading...
Setting up the GPG keyring
Downloading the image index
Downloading the rootfs
Downloading the metadata
The image cache is now ready
Unpacking the rootfs

---
You just created an Ubuntu bionic amd64 (20190910_07:42) container.

To enable SSH, run: apt install openssh-server
No default root or user password are set by LXC.

$ echo "lxc.cgroup.devices.allow = c 10:57 rwm" >> lxc/testbox/config

$ lxc-start -n testbox -o debug.out -l trace
lxc-start: testbox: lxccontainer.c: wait_on_daemonized_start: 842 Received 
container state "ABORTING" instead of "RUNNING"
lxc-start: testbox: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: testbox: tools/lxc_start.c: main: 333 To get more details, run the 
container in foreground mode
lxc-start: testbox: tools/lxc_start.c: main: 336 Additional information can be 
obtained by setting the --logfile and --logpriority options

$ cat debug.out
lxc-start testbox 20190910192712.380 INFO confile - 
confile.c:set_config_idmaps:1555 - Read uid map: type u nsid 0 hostid 10 
range 65536
lxc-start testbox 20190910192712.380 INFO confile - 
confile.c:set_config_idmaps:1555 - Read uid map: type g nsid 0 hostid 10 
range 65536
lxc-start testbox 20190910192712.382 TRACEcommands - commands.c:lxc_cmd:300 
- Connection refused - Command "get_init_pid" failed to connect command socket
lxc-start testbox 20190910192712.383 TRACEcommands - commands.c:lxc_cmd:300 
- Connection refused - Command "get_state" failed to connect command socket
lxc-start testbox 20190910192712.383 TRACEstart - 
start.c:lxc_init_handler:748 - Created anonymous pair {4,5} of unix sockets
lxc-start testbox 20190910192712.383 TRACEcommands - 
commands.c:lxc_cmd_init:1248 - Creating abstract unix socket 
"/home/ubuntu/lxc/testbox/command"
lxc-start testbox 20190910192712.383 TRACEstart - 
start.c:lxc_init_handler:760 - Unix domain socket 6 for command server is ready
lxc-start testbox 20190910192712.388 INFO lxccontainer - 
lxccontainer.c:do_lxcapi_start:961 - Set process title to [lxc monitor] 
/home/ubuntu/lxc testbox
lxc-start testbox 20190910192712.392 TRACEstart - start.c:lxc_start:2052 - 
Doing lxc_start
lxc-start testbox 20190910192712.393 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM 
security driver AppArmor
lxc-start testbox 20190910192712.393 TRACEstart - start.c:lxc_init:777 - 
Initialized LSM
lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:458 - Added arch 2 to main seccomp context
lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:466 - Removed native arch from main seccomp context
lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:458 - Added arch 3 to main seccomp context
lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:466 - Removed native arch from main seccomp context
lxc-start testbox 20190910192712.395 TRACEseccomp - 
seccomp.c:get_new_ctx:471 - Arch 4 already present in main seccomp context
lxc-start testbox 20190910192712.395 INFO seccomp - 
seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this 
to allow umount -f;  not recommended"
lxc-start testbox 20190910192712.395 INFO seccomp - 
seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start testbox 20190910192712.395 INFO seccomp - 
seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for 
reject_force_umount action 0(kill)
lxc-start testbox 20190910192712.396 INFO seccomp - 
seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start testbox 20190910192712.396 INFO seccomp - 

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

Still broken in disco.

** Tags added: disco

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

The systemd patch I posted earlier no longer works in disco, and the
workarounds posted here only partially fix the problem and only for a
subset of use cases. Looks like we're back to needing a proper fix.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command

[Forest]

At quick glance, I don't see a quick and easy way to test email
notifications. Is there one? Is it documented someplace? I'd hate to be
the one who thought an email would be sent when a problem is detected,
only to find out after it was too late that I was mistaken.

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

Title:
  10mail script should use sendmail command, not the mail command

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

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

[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command

[Forest]

The problem this presents to me personally is that the current packaging
causes (by default) GNU mailutils to be installed, and that
implementation of mailx forcibly overrides and breaks the dma MTA's
MASQUERADE mode, upon which my site depends. (I verified with mailutils'
author that this is the case.) As a result, the smartmontools mail
feature simply does not work on systems like mine, and cannot be made to
work with a mere configuration change.

However, it could be made to work with a fairly minor change to the
10mail script, to invoke sendmail* if available on the system. Since you
seem to be using mailx because of the flexibility it offers in delivery
options, perhaps this change would make sense, as it would buy more
flexibility with relatively little effort, and without losing anything.

As I said, though, I didn't write this bug report just to solve my own
problem. I took the time to write it up because it seems like a general
case that probably affects other people, and I thought you folks would
want to be aware of it.


*When I say sendmail here, I don't mean the traditional implementation. I'm 
using dma, the Dragonfly Mail Agent, on my systems. It is very lightweight, 
works well, and has been proposed as the new default on debian-based 
distributions.
https://wiki.mageia.org/en/Dma_Dragonfly_Mail_Agent
https://wiki.debian.org/Debate/DefaultMTA/DMA

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

Title:
  10mail script should use sendmail command, not the mail command

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

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

[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command

[Forest]

Just for the record, it's also worth noting that mailutils, which is
currently listed in this package's Recommends: field, overrides the dma
(Dragonfly Mail Agent) MASQUERADE setting and causes outgoing messages
to bounce.  In other words, 10mail doesn't work without a /usr/bin/mail,
and in certain configurations, doesn't work with one either.

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

Title:
  10mail script should use sendmail command, not the mail command

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

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

[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command

[Forest]

> (Caution: not tested :-)

Heh... Understood.

I know how to work around the problem on my own system, though. I wrote
up this report because I thought the maintainers might like to know that
10mail doesn't work on systems that have no /usr/bin/mail at all, but
have a perfectly functioning sendmail command.  If you don't care, so be
it.

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

Title:
  10mail script should use sendmail command, not the mail command

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

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

[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command

[Forest]

Okay, thanks for the info, but it doesn't solve the problem.

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

Title:
  10mail script should use sendmail command, not the mail command

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

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

[Bug 1833331] [NEW] 10mail script should use sendmail command, not the mail command

[Forest]

Public bug reported:

The 10mail script is trying to send messages with /usr/bin/mail (aka
mailx), which is a user agent, not intended for automated message
sending. I believe it should be using the /usr/sbin/sendmail or
/usr/lib/sendmail command instead, as that command is meant for non-
interactive message sending.

Accordingly, the package should probably declare Recommends: default-mta
| mail-transport-agent instead of mailx | mailutils.

Use case:

The current script's use of the mail command is causing message delivery
to fail on my systems.  This was at first because no mail user agent was
installed (and there should be no need for one, since there are no local
mail users.) Furthermore, even when I installed gnu mailutils in an
attempt to solve this problem, I discovered that mailutils overrides my
system's MTA configuration to use an invalid MAIL FROM address, causing
the upstream mail host to reject smartmon's outgoing messages. Several
more hours spent experimenting with mailutils configuration options just
led to one form or another of the same type of problem, all rooted in
the fact that mailutils makes assumptions that are just plain wrong on
some installations. I would like my sanity back, please. :)

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

** Description changed:

  The 10mail script is trying to send messages with /usr/bin/mail (aka
  mailx), which is a user agent, not intended for automated message
  sending. I believe it should be using the /usr/sbin/sendmail or
  /usr/lib/sendmail command instead, as that command is meant for non-
  interactive message sending.
  
  Accordingly, the package should probably declare Recommends: default-mta
  | mail-transport-agent instead of mailx | mailutils.
  
  Use case:
  
  The current script's use of the mail command is causing message delivery
- to fail on my systems.  This was at first because there no mail user
- agent was installed (since there are no local mail users), but even when
- I installed one, I discovered that it (gnu mailutils) overrides my
+ to fail on my systems.  This was at first because no mail user agent was
+ installed (since there are no local mail users), but even when I
+ installed one, I discovered that it (gnu mailutils) overrides my
  system's MTA configuration to use an invalid MAIL FROM address, causing
  the upstream mail host to reject smartmon's outgoing messages.

** Description changed:

  The 10mail script is trying to send messages with /usr/bin/mail (aka
  mailx), which is a user agent, not intended for automated message
  sending. I believe it should be using the /usr/sbin/sendmail or
  /usr/lib/sendmail command instead, as that command is meant for non-
  interactive message sending.
  
  Accordingly, the package should probably declare Recommends: default-mta
  | mail-transport-agent instead of mailx | mailutils.
  
  Use case:
  
  The current script's use of the mail command is causing message delivery
  to fail on my systems.  This was at first because no mail user agent was
- installed (since there are no local mail users), but even when I
- installed one, I discovered that it (gnu mailutils) overrides my
+ installed (and there should be no need for one, since there are no local
+ mail users.) Furthermore, even when I installed gnu mailutils in an
+ attempt to solve this problem, I discovered that mailutils overrides my
  system's MTA configuration to use an invalid MAIL FROM address, causing
  the upstream mail host to reject smartmon's outgoing messages.

** Description changed:

  The 10mail script is trying to send messages with /usr/bin/mail (aka
  mailx), which is a user agent, not intended for automated message
  sending. I believe it should be using the /usr/sbin/sendmail or
  /usr/lib/sendmail command instead, as that command is meant for non-
  interactive message sending.
  
  Accordingly, the package should probably declare Recommends: default-mta
  | mail-transport-agent instead of mailx | mailutils.
  
  Use case:
  
  The current script's use of the mail command is causing message delivery
  to fail on my systems.  This was at first because no mail user agent was
  installed (and there should be no need for one, since there are no local
  mail users.) Furthermore, even when I installed gnu mailutils in an
  attempt to solve this problem, I discovered that mailutils overrides my
  system's MTA configuration to use an invalid MAIL FROM address, causing
- the upstream mail host to reject smartmon's outgoing messages.
+ the upstream mail host to reject smartmon's outgoing messages. Several
+ more hours spent experimenting with mailutils configuration options just
+ led to one form or another of the same type of problem, all rooted in
+ the fact that mailutils makes assumptions that are just plain wrong on
+ some installations. I would like my sanity back, please. :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, 

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

My PPA has moved, and has a current package for ubuntu bionic.  New
location:

https://launchpad.net/~foresto/+archive/ubuntu/tweaks/

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist

[Forest]

Another ecryptfs use case that I didn't notice in these comments:

Protecting a directory tree within a user's home directory, to be
unlocked for short term use and then re-locked immediately afterward,
without logging out or requiring root access.  This is appropriate for
limiting the exposure of your sensitive files while using software that
runs as you (and therefore has access to all your files) but you don't
trust to be free of exploits (e.g. web browsers or games).

A common pattern is to exit all programs that don't need access to your
encrypted directory, then unlock it and do your viewing/editing, then
re-lock it before using complex or proprietary software again.  In the
physical world, this is like putting your private papers in a locked
filing cabinet while guests visit, rather than leaving them on your
desk.

LUKS/dm-crypt are not well-suited for this use case, since they require
carving out a fixed-size chunk of disk space (which wastes space until
it is filled and denies additional storage once it is filled), and since
they require root access to set up.

It looks like fscrypt might one day be well-suited for this use case,
but it doesn't appear to be ready yet.

That means that Ubuntu does not yet have a good replacement for
ecryptfs, which was an officially encouraged tool not very long ago. I
hope we'll all keep this in mind before telling people they should not
be using it.

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

Title:
  Buggy, under-maintained, not fit for main anymore; alternatives exist

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

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

Re: [Bug 1299878] Re: ncsw_config.mk missing from linux-lowlatency kernel

[Forest]

Hey, a bug I filed 4 years ago has been marked as "won't fix". This is
precisely why I don't use Linux anymore...

On Wed, Mar 6, 2019, 11:59 PM Erich Eickmeyer 
wrote:

> ** Changed in: ubuntustudio
>Status: New => Invalid
>
> ** Changed in: ubuntustudio
>Status: Invalid => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1299878
>
> Title:
>   ncsw_config.mk missing from linux-lowlatency kernel
>
> Status in Ubuntu Studio:
>   Won't Fix
> Status in linux-lowlatency package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I'm on Ubuntu Studio 14.04 Beta 2 (upgraded through apt-get from Beta
>   1,) and I'm trying to compile my own low-latency kernel with make-
>   kpkg. I just want to remove xhci-hda and ehci-hda from the kernel so
>   my USB Audio Interface will work correctly. I modify the config file
>   via make menuconfig, but then when I run
>
>   sudo make-kpkg clean
>
>   I get the following output:
>
>   exec make kpkg_version=12.036+nmu3 -f /usr/share/kernel-package/ruleset/
> minimal.mk clean
>   == making target minimal_clean [new prereqs: ]==
>   This is kernel package version 12.036+nmu3.
>   test ! -f .config || cp -pf .config config.precious
>   test ! -e stamp-building || rm -f stamp-building
>   test ! -f Makefile || \
>   makeARCH=i386 distclean
>   make[1]: Entering directory `/usr/src/linux-headers-3.13.0-12-lowlatency'
> CLEAN   .
>   /usr/src/linux-headers-3.13.0-12-lowlatency/drivers/net/dpa/Makefile:7:
> /usr/src/linux-headers-3.13.0-12-lowlatency/drivers/net/dpa/NetCommSw/
> ncsw_config.mk: No such file or directory
>   make[4]: *** No rule to make target
> `/usr/src/linux-headers-3.13.0-12-lowlatency/drivers/net/dpa/NetCommSw/
> ncsw_config.mk'.  Stop.
>   make[3]: *** [drivers/net/dpa] Error 2
>   make[2]: *** [drivers/net] Error 2
>   make[1]: *** [_clean_drivers] Error 2
>   make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-12-lowlatency'
>   make: *** [minimal_clean] Error 2
>
>   The same thing happens with 3.13.0-20-lowlatency as well. I have the
>   build-essential package installed as well as linux-headers-lowlatency
>   and linux-headers-generic. I think the device driver is just missing.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntustudio/+bug/1299878/+subscriptions
>

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

Title:
  ncsw_config.mk missing from linux-lowlatency kernel

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

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

[Bug 1816278] Re: lubuntu-desktop requires pulseaudio to be installed

[Forest]

>The solution: install the basic components or simply uninstall pavucontrol-qt. 
>It will remove lubuntu-desktop but that's just a metafile. It won't remove your
>entire installation.

Wouldn't that leave all the remaining lubuntu packages marked as
automatically installed, and therefore slated for removal at the next
apt-get autoremove? If so, that's not very helpful.

Also, don't "recommends" packages get installed by default? If so,
wouldn't setting pavucontrol-qt to "recommends" still give you the
experience you expect, while still allowing non-Pulse installations for
users who need them?

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

Title:
  lubuntu-desktop requires pulseaudio to be installed

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

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

[Bug 1816278] [NEW] lubuntu-desktop requires pulseaudio to be installed

[Forest]

Public bug reported:

The lubuntu-desktop package depends on pavucontrol-qt, which in turn
depends on pulseaudio, meaning that PulseAudio is forced upon anyone who
wants to use Ubuntu's LXQt flavor.  This is problematic for those of us
to whom PulseAudio is intolerable, and for those who simply prefer an
ALSA-only system.  It also seems unnecessary, given that the xubuntu-
desktop package merely "recommends" pavucontrol, and pavucontrol merely
"recommends" pulseaudio.

Please downgrade these dependencies from "depends" to "recommends" or
"suggests".

** Affects: lubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: pavucontrol-qt (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: pavucontrol-qt (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/1816278

Title:
  lubuntu-desktop requires pulseaudio to be installed

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

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

[Bug 1389964] Re: Thunar's Open Terminal Here is missing the SSH_AUTH_SOCK environment variable

[Forest]

Yes, still present in 18.04.


** Changed in: thunar (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/1389964

Title:
  Thunar's Open Terminal Here is missing the SSH_AUTH_SOCK environment
  variable

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

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

[Bug 1796487] [NEW] The i915 driver crashes often on a Dell latitude 630

[forest]

Public bug reported:

Hi,

The i915 driver is crashing very often, for instance typynig 'xrandr -q'
produces a crash, and at startup lightdm also seem to crash because of
that.

Here's a crash log:
[ 2040.136248] [ cut here ]
[ 2040.136254] vblank wait timed out on crtc 1
[ 2040.136389] WARNING: CPU: 1 PID: 6418 at 
/build/linux-39dmni/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x181/0x190 [drm]
[ 2040.136393] Modules linked in: hid_generic usbhid hid gpio_ich dell_rbtn 
dell_laptop dell_smbios_smm dcdbas dell_smm_hwmon wl(POE) coretemp kvm 
irqbypass dell_wmi sparse_keymap snd_hda_codec_hdmi snd_hda_codec_idt 
snd_hda_codec_generic joydev snd_hda_intel snd_hda_codec pcmcia snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event input_leds snd_rawmidi 
serio_raw dell_smbios_wmi dell_smbios wmi_bmof dell_wmi_descriptor snd_seq 
snd_seq_device snd_timer snd yenta_socket pcmcia_rsrc lpc_ich pcmcia_core 
cfg80211 soundcore shpchp mac_hid sch_fq_codel parport_pc ppdev lp parport 
ip_tables x_tables autofs4 psmouse firewire_ohci i915 pata_acpi firewire_core 
crc_itu_t i2c_algo_bit tg3 drm_kms_helper ptp pps_core syscopyarea sysfillrect 
sysimgblt fb_sys_fops drm wmi video
[ 2040.136531] CPU: 1 PID: 6418 Comm: Xorg Tainted: PW  OE
4.15.0-36-generic #39-Ubuntu
[ 2040.136535] Hardware name: Dell Inc. Latitude D630   
/0KU184, BIOS A15 11/24/2008
[ 2040.136573] RIP: 0010:drm_wait_one_vblank+0x181/0x190 [drm]
[ 2040.136576] RSP: 0018:babfc0a27960 EFLAGS: 00010282
[ 2040.136582] RAX:  RBX: 8df7cd118000 RCX: 0006
[ 2040.136586] RDX: 0007 RSI: 0082 RDI: 8df7dfd16490
[ 2040.136590] RBP: babfc0a279b8 R08: 0001 R09: 084b
[ 2040.136594] R10: babfc0a27800 R11:  R12: 0001
[ 2040.136597] R13:  R14: 2d00091e R15: 8df7cd04c968
[ 2040.136603] FS:  7f96a4876600() GS:8df7dfd0() 
knlGS:
[ 2040.136607] CS:  0010 DS:  ES:  CR0: 80050033
[ 2040.136611] CR2: 563c2fc3dce4 CR3: 000110b72000 CR4: 06e0
[ 2040.136614] Call Trace:
[ 2040.136632]  ? wait_woken+0x80/0x80
[ 2040.136740]  intel_get_load_detect_pipe+0x5b7/0x620 [i915]
[ 2040.136830]  intel_tv_detect+0x147/0x510 [i915]
[ 2040.136839]  ? __i2c_transfer+0x123/0x400
[ 2040.136846]  ? _cond_resched+0x19/0x40
[ 2040.136855]  ? __ww_mutex_lock_slowpath+0x16/0x20
[ 2040.136883]  drm_helper_probe_detect+0x50/0x90 [drm_kms_helper]
[ 2040.136902]  ? drm_helper_probe_detect+0x50/0x90 [drm_kms_helper]
[ 2040.136921]  drm_helper_probe_single_connector_modes+0xe2/0x710 
[drm_kms_helper]
[ 2040.136928]  ? __mark_inode_dirty+0x11d/0x3b0
[ 2040.136972]  drm_mode_getconnector+0x15d/0x340 [drm]
[ 2040.136980]  ? lapic_next_event+0x20/0x30
[ 2040.137020]  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
[ 2040.137053]  drm_ioctl_kernel+0x5f/0xb0 [drm]
[ 2040.137086]  drm_ioctl+0x31b/0x3d0 [drm]
[ 2040.137124]  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
[ 2040.137135]  do_vfs_ioctl+0xa8/0x630
[ 2040.137142]  ? handle_mm_fault+0xb1/0x1f0
[ 2040.137150]  ? __do_page_fault+0x270/0x4d0
[ 2040.137156]  SyS_ioctl+0x79/0x90
[ 2040.137163]  do_syscall_64+0x73/0x130
[ 2040.137171]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 2040.137176] RIP: 0033:0x7f96a1c725d7
[ 2040.137180] RSP: 002b:7fffa5922888 EFLAGS: 3246 ORIG_RAX: 
0010
[ 2040.137186] RAX: ffda RBX: 562f090e8280 RCX: 7f96a1c725d7
[ 2040.137190] RDX: 7fffa59228c0 RSI: c05064a7 RDI: 000e
[ 2040.137193] RBP: 7fffa59228c0 R08:  R09: 
[ 2040.137197] R10:  R11: 3246 R12: c05064a7
[ 2040.137201] R13: 000e R14: 000e R15: 7fffa59228c0
[ 2040.137205] Code: ff ff e8 c3 18 d4 f7 48 8d 75 a8 4c 89 ff e8 07 7a d8 f7 
45 85 ed 0f 85 ff fe ff ff 44 89 e6 48 c7 c7 10 a4 36 c0 e8 ff 15 d4 f7 <0f> 0b 
e9 e9 fe ff ff 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 
[ 2040.137320] ---[ end trace 8dac4fb0d7cdb594 ]---
[ 2050.272295] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:41:pipe B] flip_done timed out
[ 2060.512282] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [PLANE:35:plane B] flip_done timed out

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jean   6784 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Oct  6 15:34:32 2018
HibernationDevice: RESUME=UUID=30799a78-4216-4c10-a118-5efd87b1e6bf
InstallationDate: Installed on 

[Bug 1796212] [NEW] xfce4-terminal fails to update utmp; breaks write, wall, who commands

[Forest]

Public bug reported:

Due to a change in vte, xfce4-terminal on ubuntu no longer updates utmp,
which leaves terminal sessions invisible to basic unix commands like
who, wall, and write.  However, it has a build-time option to fix this
problem via libutempter.  It would be nice if this option was enabled on
ubuntu.

Change needed in debian/control:
Build-Depends: libutempter-dev

Change needed in debian/rules:
dh_auto_configure -- --with-utempter

Background:
https://bugzilla.xfce.org/show_bug.cgi?id=13710

** Affects: xfce4-terminal (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/1796212

Title:
  xfce4-terminal fails to update utmp; breaks write, wall, who commands

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

A systemd build with my patch applied is available here:

https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

This is a systemd bug, created by this commit:

https://github.com/systemd/systemd/commit/74dd6b5

It looks like poettering has attempted to address it in more recent
versions of systemd (though that doesn't help us in ubuntu 17.10):

https://github.com/systemd/systemd/pull/6832

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

Here's a simple patch to disable the broken systemd feature, and restore
ecryptfs functionality.

** Patch added: "disable_system_service_session_keyrings.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718658/+attachment/5038578/+files/disable_system_service_session_keyrings.patch

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

The ecryptfs-manager workaround helps the mount to succeed, but (at
least in my case) the system refuses to unmount it afterward. This is a
problem for those of us who open our ecryptfs volumes only for as long
as they're needed.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1726873] Re: mount.ecryptfs_private can't mount in 17.10

[Forest]

*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1718658
   ecryptfs-mount-private fails to initialize ecryptfs keys

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

Title:
  mount.ecryptfs_private can't mount in 17.10

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

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

[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

Refreshed patch for update-notifier-3.186 (artful).

** Tags added: artful

** Patch removed: "restore_icon.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4706739/+files/restore_icon.patch

** Patch removed: "restore_reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4816749/+files/restore_reboot.patch

** Patch added: "restore_icon.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/5038130/+files/restore_icon.patch

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

Sigh... The maintainers don't seem to care about the users.

I have refreshed my patches for ubuntu 17.10.

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

Refreshed patch for update-notifier-3.186 (artful).

** Patch added: "restore_reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/5038131/+files/restore_reboot.patch

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames

[Forest]

No, that won't help either.

You don't seem to understand: Adding a domain search list will not help
because the local machines do not have domains. They only have names,
like "host1" or "beetle", even on the network's DNS servers.

Since systemd's resolver refuses to consult the name servers for names
like these, it completely breaks name resolution on networks like this.

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

Title:
  systemd-resolve breaks resolution of local network hostnames

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

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

[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames

[Forest]

According to the systemd documentation, UseDomains only affects systems
that get their network setup from DHCP, which is not the case at my
site.  Furthermore, it is documented as a way to add a DNS search
domain, which would not help resolve hosts that have no domains.

So far, the only way I have found to fix the breakage is to manually
disable systemd-resolve and configure a resolver that actually works
properly.

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

Title:
  systemd-resolve breaks resolution of local network hostnames

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

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

[Bug 1699660] [NEW] systemd-resolve breaks resolution of local network hostnames

[Forest]

Public bug reported:

After upgrading to Ubuntu 17.04 (zesty), resolution of my local
network's host names is completely broken.  Apparently the upgrade
replaced my existing resolver with systemd-resolve, which deliberately
refuses to pass "single-label" domain names to my domain name server.
That is the server where all my network's host names are kept, so I can
no longer resolve any of them.

Apparently, this is yet another example of Poettering's upstream decisions 
causing denial of service to people who have been saddled with his malware.
https://github.com/systemd/systemd/issues/2514#issuecomment-179203186

Would someone sensible please put a stop to this forced breakage during
upgrade, and advise on how to fix it now that the damage has been done?

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

Title:
  systemd-resolve breaks resolution of local network hostnames

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

Dear maintainers,

Won't you please accept my patch into mainline?

It is well-tested.

It fits the project's code style perfectly.

Most importantly, it gives users a way to fix this regression without
affecting default behavior.

You can see from this bug report that dozens of users have managed to
find their way here, which hints that there are many more impacted users
who don't know how to identify the root cause of the regression and its
bug reporting system, or simply don't have the time to do so.

To underscore that point, my PPA stats show hundreds of downloads of my
patched version, and even those numbers only represent a fraction of
affected users (my PPA builds are only announced in this bug report).

Moreover, I regularly have people contacting me directly, asking for
patched builds for the Ubuntu variants that they run.  I don't want to
be in the business of maintaining a fork of your project.  Please just
fix this problem in the mainline code.

Your users are asking for help, and we have so far been ignored for over
three years.  I have done all the hard work for you.  All you have to do
is accept the patch.  It's easy.  It's safe.  It works.

Love,

Your users

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu and other desktops

[Forest]

** Summary changed:

- regression: update-notifier stopped showing a tray icon in xubuntu
+ regression: update-notifier stopped showing a tray icon in xubuntu and other 
desktops

** Tags added: zesty

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu and
  other desktops

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

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

[Bug 1246364] Re: regression: update-notifier stopped showing a tray icon in xubuntu

[Forest]

** Summary changed:

- update-notifier does not show a tray icon in xubuntu
+ regression: update-notifier stopped showing a tray icon in xubuntu

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

Title:
  regression: update-notifier stopped showing a tray icon in xubuntu

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

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

[Bug 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface

[Forest Bond]

I'm actually a bit confused -- the bug status is "fix released" but it
is not at all clear to me in what Ubuntu release this fix has been
applied.  Can someone clarify this for me?

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

Title:
  org.freedesktop.DBus.Properties.GetAll fails always for
  fi.w1.wpa_supplicant1.Interface interface

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

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

[Bug 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface

[Forest Bond]

This bug completely breaks WiFi support on my system using ConnMan. Took
a bit to hunt down and I also wrote my own patch before finding this bug
report. Can we please get this fix pushed out?

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

Title:
  org.freedesktop.DBus.Properties.GetAll fails always for
  fi.w1.wpa_supplicant1.Interface interface

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

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

[Bug 1583520] Re: Unable to convert to AAC using Ubuntu 16.04 / gstreamer0.10-plugins-bad-multiverse not available

[Forest]

Same problem here in Xubuntu 16.10:  soundconverter's preferences do not
offer aac/m4a among the output format options.  What is necessary to
make the option appear?

$ dpkg-query --show soundconv\* gstreamer1.0-plugins\*
gstreamer1.0-plugins-bad:amd64  1.8.3-1ubuntu1.1
gstreamer1.0-plugins-bad-faad:amd64 1.8.3-1ubuntu1.1
gstreamer1.0-plugins-bad-videoparsers:amd64 1.8.3-1ubuntu1.1
gstreamer1.0-plugins-base:amd64 1.8.3-1ubuntu1
gstreamer1.0-plugins-base:i386  1.8.3-1ubuntu1
gstreamer1.0-plugins-good:amd64 1.8.3-1ubuntu1.2
gstreamer1.0-plugins-ugly:amd64 1.8.3-1ubuntu1
gstreamer1.0-plugins-ugly-amr:amd64 1.8.3-1ubuntu1
soundconverter  3.0.0~alpha1+git20151209-1

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

Title:
  Unable to convert to AAC using Ubuntu 16.04 / gstreamer0.10-plugins-
  bad-multiverse not available

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

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

[Bug 1671273] [NEW] PulseAudio requirement breaks Firefox on ALSA-only systems

[Forest]

Public bug reported:

Upgrading Firefox to version 52 on an ALSA-only system breaks audio on
all websites.

PulseAudio has apparently become a hard requirement in the latest
official build of Firefox, but since PulseAudio is (due to its design)
not viable on some systems, this renders Firefox useless as a general-
purpose browser.

The upstream code still contains ALSA support.  Please re-enable it on
Ubuntu.  I have read that Arch Linux has already done so.

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

** Description changed:

  Upgrading Firefox to version 52 on an ALSA-only system breaks audio on
  all websites.
  
  PulseAudio has apparently become a hard requirement in the latest
- version of Firefox, but since PulseAudio is (due to its design) not
- viable on some systems, this renders Firefox useless as a general-
+ official build of Firefox, but since PulseAudio is (due to its design)
+ not viable on some systems, this renders Firefox useless as a general-
  purpose browser.
  
  The upstream code still contains ALSA support.  Please re-enable it on
  Ubuntu.  I have read that Arch Linux has already done so.

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

Title:
   PulseAudio requirement breaks Firefox on ALSA-only systems

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

Pascal Mons wrote:

> I guess the change was an Ubuntu policy change about the updates as
they like to force them a bit like Microsoft does. I don't expect them
to ever revert to the previous behaviour.

That would be a silly reason not to accept the patch, since it doesn't
change the behavior for Unity users, and it helps people on other
desktops to notice and install updates *sooner* than they do with the
current behavior.

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

** Patch removed: "restore_reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4706740/+files/restore_reboot.patch

** Patch added: "restore_reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4816749/+files/restore_reboot.patch

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

Clarification: I split my changes into two patches. They both still work
on the latest release.

My patches simply restore code that was removed a while back, so it's
pretty safe to consider them already-tested.  They don't change the
default behavior, so applying them shouldn't affect current users unless
they specifically enable the restored functionality.

In other words, these patches should be fairly easy to validate and safe
to apply.

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

The solution here is to convince the package maintainers that WE NEED
THEM TO FIX THIS BUG.

My patch still works on the latest release.  ALL THEY NEED TO DO IS
APPLY IT.

I occasionally update my PPA for the release that I run myself
(currently Xubuntu yakkety), but expecting me to do maintain a parallel
distribution of update-notifier is not a realistic solution.


** Tags added: yakkety

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1661098] Re: NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the ovpn config and causing AUTH_FAILED

[Forest]

Turns out is triggered by NetworkManager-openvpn stripping the "comp-lzo
no" option from the imported .ovpn config file, misrepresenting a
3-value option as a simple check box, and giving the user no way to
enter the correct setting.

Checking the "Use LZO data compression" box in the Advanced... config
dialog *might* work around the problem.  This does not map to the
intended "comp-lzo no" setting in openvpn, but if the server is pushing
the setting to the client, it might work anyway.

More details in the upstream bug report.

** Summary changed:

- auth_failed when attempting openvpn via networkmanager
+ NetworkManager-openvpn mishandles the comp-lzo option, thereby breaking the 
ovpn config and causing AUTH_FAILED

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

Title:
  NetworkManager-openvpn mishandles the comp-lzo option, thereby
  breaking the ovpn config and causing AUTH_FAILED

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1661098/+subscriptions

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

[Bug 1661098] Re: auth_failed when attempting openvpn via networkmanager

[Forest]

NetworkManager 1.2.4
NetworkManager-openvpn 1.2.6 and 1.2.8 (same problem in both)

$ nmcli --version
nmcli tool, version 1.2.4

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

$ openvpn --version
OpenVPN 2.3.11 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] 
[IPv6] built on Jun 22 2016
library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2010 OpenVPN Technologies, Inc. 
Compile time defines: enable_crypto=yes enable_crypto_ofb_cfb=yes 
enable_debug=yes enable_def_auth=yes enable_dependency_tracking=no 
enable_dlopen=unknown enable_dlopen_self=unknown 
enable_dlopen_self_static=unknown enable_fast_install=yes enable_fragment=yes 
enable_http_proxy=yes enable_iproute2=yes enable_libtool_lock=yes 
enable_lzo=yes enable_lzo_stub=no enable_maintainer_mode=no 
enable_management=yes enable_multi=yes enable_multihome=yes 
enable_pam_dlopen=no enable_password_save=yes enable_pedantic=no enable_pf=yes 
enable_pkcs11=yes enable_plugin_auth_pam=yes enable_plugin_down_root=yes 
enable_plugins=yes enable_port_share=yes enable_selinux=no enable_server=yes 
enable_shared=yes enable_shared_with_static_runtimes=no enable_silent_rules=no 
enable_small=no enable_socks=yes enable_ssl=yes enable_static=yes 
enable_strict=no enable_strict_options=no enable_systemd=yes 
enable_win32_dll=yes enable_x509_alt_username=yes with_aix_soname=aix 
with_crypto_library=openssl with_gnu_ld=yes wit
 h_mem_check=no with_plugindir='${prefix}/lib/openvpn' with_sysroot=no

$ tail -f /var/log/syslog
Feb  2 23:49:01 computer NetworkManager[1329]:   [1486108141.0702] audit: 
op="connection-activate" uuid="----" 
name="example" pid=3136 uid=1000 result="success"
Feb  2 23:49:01 computer NetworkManager[1329]:   [1486108141.0741] 
vpn-connection[0x557d295f73c0,----,"example",0]:
 Started the VPN service, PID 5074
Feb  2 23:49:01 computer NetworkManager[1329]:   [1486108141.0828] 
vpn-connection[0x557d295f73c0,----,"example",0]:
 Saw the service appear; activating connection
Feb  2 23:49:01 computer nm-openvpn[5081]: OpenVPN 2.3.11 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2016
Feb  2 23:49:01 computer nm-openvpn[5081]: library versions: OpenSSL 1.0.2g  1 
Mar 2016, LZO 2.08
Feb  2 23:49:01 computer NetworkManager[1329]: nm-openvpn[5074]   
openvpn[5081] started
Feb  2 23:49:01 computer NetworkManager[1329]:   [1486108141.1490] 
vpn-connection[0x557d295f73c0,----,"example",0]:
 VPN plugin: state changed: starting (3)
Feb  2 23:49:01 computer NetworkManager[1329]:   [1486108141.1491] 
vpn-connection[0x557d295f73c0,----,"example",0]:
 VPN connection: (ConnectInteractive) reply received
Feb  2 23:49:01 computer nm-openvpn[5081]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Feb  2 23:49:01 computer nm-openvpn[5081]: Control Channel Authentication: 
using '/home/ubuntu/vpn/ovpn.example.net/networkmanager/example.ovpn.tls-auth' 
as a OpenVPN static key file
Feb  2 23:49:01 computer nm-openvpn[5081]: NOTE: chroot will be delayed because 
of --client, --pull, or --up-delay
Feb  2 23:49:01 computer nm-openvpn[5081]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
Feb  2 23:49:01 computer nm-openvpn[5081]: UDPv4 link local: [undef]
Feb  2 23:49:01 computer nm-openvpn[5081]: UDPv4 link remote: 
[AF_INET]10.10.10.10:1194
Feb  2 23:49:01 computer nm-openvpn[5081]: WARNING: 'link-mtu' is used 
inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
Feb  2 23:49:01 computer nm-openvpn[5081]: WARNING: 'comp-lzo' is present in 
remote config but missing in local config, remote='comp-lzo'
Feb  2 23:49:01 computer nm-openvpn[5081]: [OpenVPN Server] Peer Connection 
Initiated with [AF_INET]10.10.10.10:1194
Feb  2 23:49:04 computer nm-openvpn[5081]: AUTH: Received control message: 
AUTH_FAILED
Feb  2 23:49:04 computer nm-openvpn[5081]: SIGUSR1[soft,auth-failure] received, 
process restarting
Feb  2 23:49:04 computer NetworkManager[1329]: nm-openvpn[5074]   
Password verification failed
Feb  2 23:49:06 computer NetworkManager[1329]:   [1486108146.0884] 
vpn-connection[0x557d295f73c0,----,"example",0]:
 VPN plugin: requested secrets; state connect (4)
Feb  2 23:49:06 computer nm-openvpn[5081]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Feb  2 23:49:06 computer nm-openvpn[5081]: UDPv4 link local: [undef]
Feb  2 23:49:06 computer nm-openvpn[5081]: UDPv4 link remote: 
[AF_INET]10.10.10.10:1194
Feb  2 23:49:06 computer nm-openvpn[5081]: WARNING: 'link-mtu' is used 
inconsistently, local='link-mtu 

[Bug 1661098] [NEW] auth_failed when attempting openvpn via networkmanager

[Forest]

Public bug reported:

Attempting to establish an OpenVPN session via network-manager-openvpn
fails with a password authentication error, even though the username and
password I entered are correct.  The following messages in syslog:

Feb  1 12:44:54 computer nm-openvpn[21582]: NOTE: the current 
--script-security setting may allow this configuration to call user-defined 
scripts
Feb  1 12:44:54 computer nm-openvpn[21582]: UDPv4 link local: [undef]
Feb  1 12:44:54 computer nm-openvpn[21582]: UDPv4 link remote: 
[AF_INET]209.148.113.36:1194
Feb  1 12:44:54 computer nm-openvpn[21582]: WARNING: 'link-mtu' is used 
inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
Feb  1 12:44:54 computer nm-openvpn[21582]: WARNING: 'comp-lzo' is present 
in remote config but missing in local config, remote='comp-lzo'
Feb  1 12:44:54 computer nm-openvpn[21582]: [OpenVPN Server] Peer 
Connection Initiated with [AF_INET]209.148.113.36:1194
Feb  1 12:44:56 computer nm-openvpn[21582]: AUTH: Received control message: 
AUTH_FAILED
Feb  1 12:44:56 computer nm-openvpn[21582]: SIGUSR1[soft,auth-failure] 
received, process restarting
Feb  1 12:44:56 computer NetworkManager[1322]: nm-openvpn[21574]   
Password verification failed

I am able to establish the session by manually running openvpn from the
command line, using the same username, password, and the ovpn file from
which NetworkManager imported the setttings.

I'm running Xubuntu 16.10 (yakkety).
I did not have this problem in Ubuntu 16.04 (xenial).

** Affects: network-manager-openvpn (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/1661098

Title:
  auth_failed when attempting openvpn via networkmanager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1661098/+subscriptions

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

Problem still exists in Ubuntu 16.10.

** Summary changed:

- starting any container with umask 007 breaks lxc-stop and prevents host 
system shutdown
+ starting any container with umask 007 breaks host system shutdown. lxc-stop 
just hangs.

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

Title:
  starting any container with umask 007 breaks host system shutdown.
  lxc-stop just hangs.

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

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

[Bug 1659983] Re: steam package needs a dbus-x11 dependency to fix missing tray icon / indicator

[Forest]

** Description changed:

  Please add Recommends: dbus-x11 (or maybe Suggests:) to the steam
  packaging.
  
  I was trying for months to figure out why steam wouldn't show a
  notification tray icon or application indicator on my new xubuntu
- installation, when it worked fine on my old installation. I learned
+ installation, when it worked fine on my old installation. I discovered
  today that installing the dbus-x11 package fixes it. Perhaps that
  package is usually pulled in by some other dependency in a default
  desktop installation, but on my minimal system, it wasn't.

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

Title:
  steam package needs a dbus-x11 dependency to fix missing tray icon /
  indicator

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

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

[Bug 1659983] [NEW] steam package needs a dbus-x11 dependency to fix missing tray icon / indicator

[Forest]

Public bug reported:

Please add Recommends: dbus-x11 (or maybe Suggests:) to the steam
packaging.

I was trying for months to figure out why steam wouldn't show a
notification tray icon or application indicator on my new xubuntu
installation, when it worked fine on my old installation. I learned
today that installing the dbus-x11 package fixes it. Perhaps that
package is usually pulled in by some other dependency in a default
desktop installation, but on my minimal system, it wasn't.

** Affects: steam (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/1659983

Title:
  steam package needs a dbus-x11 dependency to fix missing tray icon /
  indicator

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

I reproduced it with the latest mainline kernel as well:

Linux xenialbox 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20
22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Here's the slightly different syslog output:

Nov 22 14:36:55 xenialbox kernel: [  484.506570] INFO: task systemd:3086 
blocked for more than 120 seconds.
Nov 22 14:36:55 xenialbox kernel: [  484.506578]   Not tainted 
4.9.0-040900rc6-generic #201611201731
Nov 22 14:36:55 xenialbox kernel: [  484.506579] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 22 14:36:55 xenialbox kernel: [  484.506582] systemd D0  3086   
3076 0x0104
Nov 22 14:36:55 xenialbox kernel: [  484.506589]  8eaa1810bc00 
8eaa58f4d800 8eaa57f59d00 8eaa5fc19340
Nov 22 14:36:55 xenialbox kernel: [  484.506593]  8eaa54bec880 
9bab80f17b78 8bc87183 8c244480
Nov 22 14:36:55 xenialbox kernel: [  484.506596]  00ff8eaa57f59d00 
8eaa5fc19340  8eaa57f59d00
Nov 22 14:36:55 xenialbox kernel: [  484.506600] Call Trace:
Nov 22 14:36:55 xenialbox kernel: [  484.506622]  [] ? 
__schedule+0x233/0x6e0
Nov 22 14:36:55 xenialbox kernel: [  484.506626]  [] 
schedule+0x36/0x80
Nov 22 14:36:55 xenialbox kernel: [  484.506629]  [] 
rwsem_down_write_failed+0x20a/0x380
Nov 22 14:36:55 xenialbox kernel: [  484.506634]  [] ? 
kvm_sched_clock_read+0x1e/0x30
Nov 22 14:36:55 xenialbox kernel: [  484.506643]  [] ? 
kernfs_sop_show_options+0x40/0x40
Nov 22 14:36:55 xenialbox kernel: [  484.506651]  [] 
call_rwsem_down_write_failed+0x17/0x30
Nov 22 14:36:55 xenialbox kernel: [  484.506655]  [] 
down_write+0x2d/0x40
Nov 22 14:36:55 xenialbox kernel: [  484.506658]  [] 
grab_super+0x30/0xa0
Nov 22 14:36:55 xenialbox kernel: [  484.506661]  [] 
sget_userns+0x18f/0x4d0
Nov 22 14:36:55 xenialbox kernel: [  484.506663]  [] ? 
kernfs_sop_show_path+0x50/0x50
Nov 22 14:36:55 xenialbox kernel: [  484.50]  [] 
kernfs_mount_ns+0x7e/0x230
Nov 22 14:36:55 xenialbox kernel: [  484.506674]  [] 
cgroup_mount+0x328/0x840
Nov 22 14:36:55 xenialbox kernel: [  484.506679]  [] ? 
alloc_pages_current+0x95/0x140
Nov 22 14:36:55 xenialbox kernel: [  484.506682]  [] 
mount_fs+0x38/0x150
Nov 22 14:36:55 xenialbox kernel: [  484.506686]  [] 
vfs_kern_mount+0x67/0x110
Nov 22 14:36:55 xenialbox kernel: [  484.506688]  [] 
do_mount+0x1e1/0xcb0
Nov 22 14:36:55 xenialbox kernel: [  484.506691]  [] ? 
__check_object_size+0xff/0x1d6
Nov 22 14:36:55 xenialbox kernel: [  484.506695]  [] ? 
kmem_cache_alloc_trace+0xd7/0x190
Nov 22 14:36:55 xenialbox kernel: [  484.506697]  [] 
SyS_mount+0x83/0xd0
Nov 22 14:36:55 xenialbox kernel: [  484.506700]  [] 
do_syscall_64+0x5b/0xc0
Nov 22 14:36:55 xenialbox kernel: [  484.506702]  [] 
entry_SYSCALL64_slow_path+0x25/0x25

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

Linux xenialbox 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

** Description changed:

- If I run lxc-start with umask 007 (or any other value that masks the
- world-execute bit), my host system enters a state with the following
- problems:
+ If I have umask 007 (or any other value that masks the world-execute
+ bit) when I run lxc-start for the first time after logging in, my host
+ system enters a state with the following problems:
  
  * lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
  * lxc-stop --kill --nolock hangs in the same way.
- * Attempts to reboot or shut down my host system fail, requiring a hard reset 
to recover.
+ * Attempts to reboot or shut down the host system fail, requiring a hard 
reset to recover.
  
  When lxc-stop hangs, messages like these appear in syslog every couple
  of minutes:
  
  Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 
blocked for more than 120 seconds.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE  
 4.4.0-47-generic #68-Ubuntu
  Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
  Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
  Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
  Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
  Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
  Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
  Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
  Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
  Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
  Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
  Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
  Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 
do_mount+0x269/0xde0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091698]  [] 
SyS_mount+0x9f/0x100
  Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  
  When system shutdown hangs, similar messages appear on the console every
  couple of minutes.
  
  I can reproduce this at will with a freshly-installed and fully-updated
  host OS in VirtualBox, and with either an old-ish container or a new
  one.
  
  I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS
  amd64.
  
  My containers are all unprivileged.
  
  My umask at container creation time does not seem to matter.  As far as
  I have seen, my umask only matters the first time I start a container in
  my login session.
  
  I can work around the bug by manually setting my umask to something more
  permissive before I start my first container of the day, and then
  setting it back again, but that's rather a hassle.  (Even worse, it's
  very easy to forget this workaround and be left with containers that
  can't be stopped and a host system that won't shut down cleanly.)

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

** Description changed:

  If I run lxc-start with umask 007 (or any other value that masks the
  world-execute bit), my host system enters a state with the following
  problems:
  
  * lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
  * lxc-stop --kill --nolock hangs in the same way.
  * Attempts to reboot or shut down my host system fail, requiring a hard reset 
to recover.
  
  When lxc-stop hangs, messages like these appear in syslog every couple
  of minutes:
  
  Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 
blocked for more than 120 seconds.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE  
 4.4.0-47-generic #68-Ubuntu
  Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
  Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
  Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
  Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
  Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
  Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
  Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
  Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
  Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
  Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
  Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
  Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 
do_mount+0x269/0xde0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091698]  [] 
SyS_mount+0x9f/0x100
  Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  
  When system shutdown hangs, similar messages appear on the console every
  couple of minutes.
  
+ I can reproduce this at will with a freshly-installed and fully-updated
+ host OS in VirtualBox, and with either an old-ish container or a new
+ one.
+ 
  I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS
  amd64.
  
  My containers are all unprivileged.
- 
- I can reproduce this at will with a freshly installed host OS in
- VirtualBox, and with either an old-ish container or a new one.
  
  My umask at container creation time does not seem to matter.  As far as
  I have seen, my umask only matters the first time I start a container in
  my login session.
  
  I can work around the bug by manually setting my umask to something more
  permissive before I start my first container of the day, and then
  setting it back again, but that's rather a hassle.  (Even worse, it's
  very easy to forget this workaround and be left with containers that
  can't be stopped and a host system that won't shut down cleanly.)

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

** Description changed:

  If I run lxc-start with umask 007 (or any other value that masks the
  world-execute bit), my host system enters a state with the following
  problems:
  
  * lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
  * lxc-stop --kill --nolock hangs in the same way.
  * Attempts to reboot or shut down my host system fail, requiring a hard reset 
to recover.
  
  When lxc-stop hangs, messages like these appear in syslog every couple
  of minutes:
  
  Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 
blocked for more than 120 seconds.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE  
 4.4.0-47-generic #68-Ubuntu
  Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
  Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
  Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
  Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
  Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
  Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
  Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
  Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
  Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
  Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
  Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
  Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
  Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
  Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 
do_mount+0x269/0xde0
  Nov 17 01:22:11 hostbox kernel: [ 3360.091698]  [] 
SyS_mount+0x9f/0x100
  Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  
  When system shutdown hangs, similar messages appear on the console every
  couple of minutes.
  
  I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS
  amd64.
  
  My containers are all unprivileged.
  
- I can reproduce this at will with either an old-ish container or a fresh
- new one.
+ I can reproduce this at will with a freshly installed host OS in
+ VirtualBox, and with either an old-ish container or a new one.
  
  My umask at container creation time does not seem to matter.  As far as
  I have seen, my umask only matters the first time I start a container in
  my login session.
  
  I can work around the bug by manually setting my umask to something more
  permissive before I start my first container of the day, and then
  setting it back again, but that's rather a hassle.  (Even worse, it's
  very easy to forget this workaround and be left with containers that
  can't be stopped and a host system that won't shut down cleanly.)

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] [NEW] starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

Public bug reported:

If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:

* lxc-stop hangs forever instead of stopping any container, even one that 
wasn't started with umask 007.
* lxc-stop --kill --nolock hangs in the same way.
* Attempts to reboot or shut down my host system fail, requiring a hard reset 
to recover.

When lxc-stop hangs, messages like these appear in syslog every couple
of minutes:

Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked 
for more than 120 seconds.
Nov 17 01:22:11 hostbox kernel: [ 3360.091629]   Tainted: P   OE   
4.4.0-47-generic #68-Ubuntu
Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 
8800c6febb58 0 12179  12168 0x0104
Nov 17 01:22:11 hostbox kernel: [ 3360.091638]  8800c6febb58 
8800d318d280 88040c649b80 8800d318d280
Nov 17 01:22:11 hostbox kernel: [ 3360.091641]  8800c6fec000 
8800345bc088 8800345bc070 
Nov 17 01:22:11 hostbox kernel: [ 3360.091644]  fffe0001 
8800c6febb70 81830f15 8800d318d280
Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace:
Nov 17 01:22:11 hostbox kernel: [ 3360.091653]  [] 
schedule+0x35/0x80
Nov 17 01:22:11 hostbox kernel: [ 3360.091657]  [] 
rwsem_down_write_failed+0x202/0x350
Nov 17 01:22:11 hostbox kernel: [ 3360.091662]  [] ? 
kernfs_sop_show_options+0x40/0x40
Nov 17 01:22:11 hostbox kernel: [ 3360.091666]  [] 
call_rwsem_down_write_failed+0x13/0x20
Nov 17 01:22:11 hostbox kernel: [ 3360.091669]  [] ? 
down_write+0x2d/0x40
Nov 17 01:22:11 hostbox kernel: [ 3360.091672]  [] 
grab_super+0x30/0xa0
Nov 17 01:22:11 hostbox kernel: [ 3360.091674]  [] 
sget_userns+0x152/0x450
Nov 17 01:22:11 hostbox kernel: [ 3360.091677]  [] ? 
kernfs_sop_show_path+0x50/0x50
Nov 17 01:22:11 hostbox kernel: [ 3360.091680]  [] 
kernfs_mount_ns+0x7e/0x230
Nov 17 01:22:11 hostbox kernel: [ 3360.091685]  [] 
cgroup_mount+0x2eb/0x7f0
Nov 17 01:22:11 hostbox kernel: [ 3360.091687]  [] 
mount_fs+0x38/0x160
Nov 17 01:22:11 hostbox kernel: [ 3360.091691]  [] 
vfs_kern_mount+0x67/0x110
Nov 17 01:22:11 hostbox kernel: [ 3360.091694]  [] 
do_mount+0x269/0xde0
Nov 17 01:22:11 hostbox kernel: [ 3360.091698]  [] 
SyS_mount+0x9f/0x100
Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] 
entry_SYSCALL_64_fastpath+0x16/0x71

When system shutdown hangs, similar messages appear on the console every
couple of minutes.

I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS
amd64.

My containers are all unprivileged.

I can reproduce this at will with either an old-ish container or a fresh
new one.

My umask at container creation time does not seem to matter.  As far as
I have seen, my umask only matters the first time I start a container in
my login session.

I can work around the bug by manually setting my umask to something more
permissive before I start my first container of the day, and then
setting it back again, but that's rather a hassle.  (Even worse, it's
very easy to forget this workaround and be left with containers that
can't be stopped and a host system that won't shut down cleanly.)

** Affects: lxc (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/1642767

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown

[Forest]

Possibly related: when the problem is triggered, I notice that my guest
instances start with no /etc/resolv.conf and no inet address.

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

Title:
  starting any container with umask 007 breaks lxc-stop and prevents
  host system shutdown

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

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

[Bug 1639524] [NEW] doesn't view images from archives on xenial

[Romik Forest]

Public bug reported:

It was be able to view images from archives in previous versions, but on
Xenial it can't

** Affects: gwenview (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/1639524

Title:
  doesn't view images from archives on xenial

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

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

[Bug 1639523] [NEW] rar5 support on Xenial

[Romik Forest]

Public bug reported:

Krusader from Xenial package stil can't work with rar archives.
The rar5 support is added by developer many time ago

** Affects: krusader (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/1639523

Title:
  rar5 support on Xenial

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

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

[Bug 1639479] Re: Video playback is choppy / stuttering with ALSA audio output

[Forest]

** Patch added: "patch 2/2"
   
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1639479/+attachment/4772993/+files/revert-alsa-large-buffers.patch

** Bug watch added: VLC Trac #10422
   http://trac.videolan.org/vlc/ticket/10422

** Also affects: vlc via
   http://trac.videolan.org/vlc/ticket/10422
   Importance: Unknown
   Status: Unknown

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

** Also affects: vlc (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734100
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Video playback is choppy / stuttering with ALSA audio output
+ Video playback is garbled / choppy / stuttering with ALSA audio output

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

Title:
  Video playback is garbled / choppy / stuttering with ALSA audio output

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

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

[Bug 1639479] [NEW] Video playback is garbled / choppy / stuttering with ALSA audio output

[Forest]

Public bug reported:

VLC 2.x fails to play many videos smoothly when ALSA audio output is
selected.  Every 10-30 seconds, the picture gets badly garbled, as if
there were packet loss in the video stream.  I see the problem most
often with high def content.

The problem has been identified upstream, and reportedly fixed in vlc
3.0, but they are dismissive of users wanting a fix for 2.x.  Given that
this bug exists in the current LTS release and we're likely to be stuck
with vlc 2.x for years to come, this is kind of a problem.

I have a pair of patches that apply to both vlc 2.2.2 and vlc 2.2.4.  I have 
been using them with no problems for the past couple of months.  Anyone else 
who wants to test them is most welcome, of course.  Patched builds are 
available for xenial on my PPA:
https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/

** Affects: vlc
 Importance: Unknown
 Status: Unknown

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

** Affects: vlc (Debian)
 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/1639479

Title:
  Video playback is garbled / choppy / stuttering with ALSA audio output

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

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

[Bug 1639479] Re: Video playback is choppy / stuttering with ALSA audio output

[Forest]

** Patch added: "patch 1/2"
   
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1639479/+attachment/4772992/+files/reduce-decoder-lock-scope.patch

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

Title:
  Video playback is garbled / choppy / stuttering with ALSA audio output

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

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

[Bug 1639474] [NEW] cairo.Error: invalid value from do_draw() when gtk3 theme has scrollbar stepper buttons

[Forest]

Public bug reported:

Meld barfs up a bunch of tracebacks on stderr when the desktop's gtk3
theme has scrollbar stepper buttons.  This is particularly annoying when
working at the command line, since all those traceback messages push
everything else out of my terminal window.

Example traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/meld/diffmap.py", line 138, in do_draw
width, height)
cairo.Error: invalid value (typically too big) for the size of the input 
(surface, pattern, etc.)

It seems that DiffMap.do_draw() subtracts the combined height of the
scrollbar steppers from self._scroll_height (no matter what the height
is, and uses the result as the height argument to
cairo.Surface.create_similar().  When self._scroll_height is only 1,
that argument ends up being a negative number, which chokes cairo.

You won't see the bug unless your gtk3 theme uses scrollbar stepper
buttons.  To reproduce, find a theme with something like this in its
gtk-3.0/gtk-widgets.css:

-GtkScrollbar-has-backward-stepper: true;
-GtkScrollbar-has-forward-stepper: true;
-GtkRange-stepper-size: 15px;

I can reproduce the bug by comparing directories while using any of
these themes:

Greybird-Mod
https://www.gnome-look.org/p/1015000/

Windows 8 Gtk3
https://www.gnome-look.org/p/1013223/

Clearlooks-Phenix v6
https://www.gnome-look.org/p/1013756/

DarkMint
https://www.gnome-look.org/p/1013679/

** Affects: meld
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: GNOME Bug Tracker #773985
   https://bugzilla.gnome.org/show_bug.cgi?id=773985

** Also affects: meld via
   https://bugzilla.gnome.org/show_bug.cgi?id=773985
   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/1639474

Title:
  cairo.Error: invalid value from do_draw() when gtk3 theme has
  scrollbar stepper buttons

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

** Tags added: wily xenial

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

Re: [Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

>Forest: Any chance for a Trusty .deb of this in your PPA?

Not likely.  I don't have a need for a Trusty build, and I suspect making
one myself would be counterproductive to the goal of this bug report:
Getting the maintainers to do it, so everyone can have the fix through
official channels.

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

Launchpad statistics report 300 downloads for my patched Ubuntu 14.04
(trusty) builds.

In order to download those packages, all 300 of those people had to
figure out what package was responsible for the removed functionality,
find their way to this bug report, read through the comments to discover
my PPA builds, and take it upon themselves to either add my PPA to their
systems or manually download and install my package.  For each of those
300 people who had the knowledge and perseverance to overcome all those
obstacles, there are surely more who did not, and simply had their
workflows broken by this bug.

The usability studies that led to this change were obviously flawed.

Dear maintainers, I hope you will reconsider your earlier decision soon,
and fix the problem.  I have already done the hard part for you.  We,
along with those who haven't the time or knowledge to speak up in this
bug report, are depending on you.

For now, I have attached new patches for the version of update-notifier
that is current in Ubuntu 16.04 (xenial):

restore_icon.patch is an update of my earlier patch.

restore_reboot.patch builds upon that work, additionally restoring the
"Reboot Required" UI.

I have also uploaded new builds to my PPA for Ubuntu Xenial.  These
include both of my patches, along with updated debian packaging
(actually just an additional line in debian/update-notifier.install) to
ensure the reboot-dialog.ui file gets installed.

https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

Here's an updated patch, for update-notifier 3.168.1, which is current
on Ubuntu 16.04 (xenial).

** Patch added: "restore_icon.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4706739/+files/restore_icon.patch

** Patch removed: "restore_tray_icon.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4207170/+files/restore_tray_icon.patch

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1246364] Re: update-notifier does not show a tray icon in xubuntu

[Forest]

This additional patch restores the reboot-required icon.  It is intended
to be applied after update_icon.patch.

** Patch added: "restore_reboot.patch"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1246364/+attachment/4706740/+files/restore_reboot.patch

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

Title:
  update-notifier does not show a tray icon in xubuntu

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

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

[Bug 1583310] [NEW] xfce4-panel + compiz window focus and restoring

[Romik Forest]

Public bug reported:

xfce 4.12 + Compiz 0.9.12.2
When I minimize window clicking in window area on the panel I can't then 
restore the same window by clicking again. I need to click some other window 
first. Or, if the window is restoring, it has not focus.

** Affects: xfce4-panel (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/1583310

Title:
  xfce4-panel + compiz window focus and restoring

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

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

[Bug 1583257] [NEW] xfce4-panel pager applet wrong aspect ratio with compiz

[Romik Forest]

Public bug reported:

xfce4 4.12 + compiz 0.9.12.2
standard pager applet has wrong aspect ratio for viewports when they have more 
when 1 row.

** Affects: xfce4-panel (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/1583257

Title:
   xfce4-panel pager applet wrong aspect ratio with compiz

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

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

[Bug 1583164] Re: Panel Indicator uses 25% cpu

[Romik Forest]

** Description changed:

  Ubuntu Studio 16.04 LTS, 4.4.0-22-lowlatency, xfce4 4.12, Compiz
  0.9.12.2
  
  top always shows 18-28% cpu used by panel-6-indicat (immediately after system 
start)
  Reinstalling xfce4-panel and xfce4-indicator-plugin doesn't help.
  Killing the panel-6-indicat by pid doesn't help
  
- Indicators: Sound menu, Messaging Menu, nm-applet, skype, caffeineplus,
- alarm-clock
+ Indicators: Sound menu, Messaging Menu, nm-applet, skype, caffeineplus, 
alarm-clock
+ Killing skype, caffeineplus,alarm-clock doesn't help.
  
  $ top
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
   2183 romik 20 0 446808 35028 26832 S 21,3 0,9 2:21.52 panel-6-indicat
  
  $ ps ax | grep panel
   2183 ? Rl 0:43 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 6 16777271 
indicator Индикаторы Предоставляет место на панели для индикаторов Unity. 
Индикаторы позволяют приложениям и системным сервисам показывать свой статус и 
взаимодействовать с пользователем.
  
  $ dpkg -S /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
  xfce4-indicator-plugin: 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
  
  $ apt-cache show xfce4-indicator-plugin
  Package: xfce4-indicator-plugin
  Priority: optional
  Section: universe/xfce
  Installed-Size: 370
  Maintainer: Xubuntu Developers 
  Original-Maintainer: Debian Xfce Maintainers 

  Architecture: amd64
  Version: 2.3.3-0ubuntu4
  Provides: indicator-renderer
  Depends: libc6 (>= 2.4), libdbus-glib-1-2 (>= 0.78), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.6), libido3-0.1-0 (>= 
13.10.0daily13.06.19), libindicator3-7 (>= 0.4.90), libxfce4panel-2.0-4 (>= 
4.11.0), libxfce4ui-2-0 (>= 4.11.0), libxfce4util7 (>= 4.9.0), libxfconf-0-2 
(>= 4.6.0), upstart
  Filename: 
pool/universe/x/xfce4-indicator-plugin/xfce4-indicator-plugin_2.3.3-0ubuntu4_amd64.deb
  Size: 60824
  MD5sum: ab1d273990915238c7fca0ea67c074f5
  SHA1: ca96db3e21960cf1b36b66a444368e7749c4dc3d
  SHA256: 2c1a4193aa68dfce9bcb4f37ea663d245815ee85457d7eb8f2d16fded72e90fa
  Description-ru: модуль отображения информации от приложений на панели Xfce4
   Небольшое расширение для последовательного отображения информации от
   различных приложений в панели Xfce4 по правилам описанным в спецификации
   Ubuntu MessagingMenu design.
  Description-md5: 9840efa394a05eab71be8c0a6217040f
  Homepage: 
http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin/
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Supported: 3y
  Task: xubuntu-core, xubuntu-desktop, mythbuntu-frontend, mythbuntu-desktop, 
mythbuntu-backend-slave, mythbuntu-backend-master, ubuntustudio-desktop-core, 
ubuntustudio-desktop

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

Title:
  Panel Indicator uses 25% cpu

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

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

[Bug 1583164] Re: Panel Indicator uses 25% cpu

[Romik Forest]

** Description changed:

  Ubuntu Studio 16.04 LTS, 4.4.0-22-lowlatency, xfce4 4.12, Compiz
  0.9.12.2
  
  top always shows 18-28% cpu used by panel-6-indicat (immediately after system 
start)
  Reinstalling xfce4-panel and xfce4-indicator-plugin doesn't help.
  Killing the panel-6-indicat by pid doesn't help
  
+ Indicators: Sound menu, Messaging Menu, nm-applet, skype, caffeineplus,
+ alarm-clock
+ 
  $ top
-   PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
-  2183 romik 20 0 446808 35028 26832 S 21,3 0,9 2:21.52 panel-6-indicat
+   PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+  2183 romik 20 0 446808 35028 26832 S 21,3 0,9 2:21.52 panel-6-indicat
  
  $ ps ax | grep panel
-  2183 ? Rl 0:43 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 6 16777271 
indicator Индикаторы Предоставляет место на панели для индикаторов Unity. 
Индикаторы позволяют приложениям и системным сервисам показывать свой статус и 
взаимодействовать с пользователем.
+  2183 ? Rl 0:43 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 6 16777271 
indicator Индикаторы Предоставляет место на панели для индикаторов Unity. 
Индикаторы позволяют приложениям и системным сервисам показывать свой статус и 
взаимодействовать с пользователем.
  
  $ dpkg -S /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
  xfce4-indicator-plugin: 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
  
  $ apt-cache show xfce4-indicator-plugin
  Package: xfce4-indicator-plugin
  Priority: optional
  Section: universe/xfce
  Installed-Size: 370
  Maintainer: Xubuntu Developers 
  Original-Maintainer: Debian Xfce Maintainers 

  Architecture: amd64
  Version: 2.3.3-0ubuntu4
  Provides: indicator-renderer
  Depends: libc6 (>= 2.4), libdbus-glib-1-2 (>= 0.78), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.6), libido3-0.1-0 (>= 
13.10.0daily13.06.19), libindicator3-7 (>= 0.4.90), libxfce4panel-2.0-4 (>= 
4.11.0), libxfce4ui-2-0 (>= 4.11.0), libxfce4util7 (>= 4.9.0), libxfconf-0-2 
(>= 4.6.0), upstart
  Filename: 
pool/universe/x/xfce4-indicator-plugin/xfce4-indicator-plugin_2.3.3-0ubuntu4_amd64.deb
  Size: 60824
  MD5sum: ab1d273990915238c7fca0ea67c074f5
  SHA1: ca96db3e21960cf1b36b66a444368e7749c4dc3d
  SHA256: 2c1a4193aa68dfce9bcb4f37ea663d245815ee85457d7eb8f2d16fded72e90fa
  Description-ru: модуль отображения информации от приложений на панели Xfce4
-  Небольшое расширение для последовательного отображения информации от
-  различных приложений в панели Xfce4 по правилам описанным в спецификации
-  Ubuntu MessagingMenu design.
+  Небольшое расширение для последовательного отображения информации от
+  различных приложений в панели Xfce4 по правилам описанным в спецификации
+  Ubuntu MessagingMenu design.
  Description-md5: 9840efa394a05eab71be8c0a6217040f
  Homepage: 
http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin/
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Supported: 3y
  Task: xubuntu-core, xubuntu-desktop, mythbuntu-frontend, mythbuntu-desktop, 
mythbuntu-backend-slave, mythbuntu-backend-master, ubuntustudio-desktop-core, 
ubuntustudio-desktop

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

Title:
  Panel Indicator uses 25% cpu

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

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

[Bug 1583164] [NEW] Panel Indicator uses 25% cpu

[Romik Forest]

Public bug reported:

Ubuntu Studio 16.04 LTS, 4.4.0-22-lowlatency, xfce4 4.12, Compiz
0.9.12.2

top always shows 18-28% cpu used by panel-6-indicat (immediately after system 
start)
Reinstalling xfce4-panel and xfce4-indicator-plugin doesn't help.
Killing the panel-6-indicat by pid doesn't help

$ top
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2183 romik 20 0 446808 35028 26832 S 21,3 0,9 2:21.52 panel-6-indicat

$ ps ax | grep panel
 2183 ? Rl 0:43 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 6 16777271 
indicator Индикаторы Предоставляет место на панели для индикаторов Unity. 
Индикаторы позволяют приложениям и системным сервисам показывать свой статус и 
взаимодействовать с пользователем.

$ dpkg -S /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
xfce4-indicator-plugin: 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so

$ apt-cache show xfce4-indicator-plugin
Package: xfce4-indicator-plugin
Priority: optional
Section: universe/xfce
Installed-Size: 370
Maintainer: Xubuntu Developers 
Original-Maintainer: Debian Xfce Maintainers 

Architecture: amd64
Version: 2.3.3-0ubuntu4
Provides: indicator-renderer
Depends: libc6 (>= 2.4), libdbus-glib-1-2 (>= 0.78), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.6), libido3-0.1-0 (>= 
13.10.0daily13.06.19), libindicator3-7 (>= 0.4.90), libxfce4panel-2.0-4 (>= 
4.11.0), libxfce4ui-2-0 (>= 4.11.0), libxfce4util7 (>= 4.9.0), libxfconf-0-2 
(>= 4.6.0), upstart
Filename: 
pool/universe/x/xfce4-indicator-plugin/xfce4-indicator-plugin_2.3.3-0ubuntu4_amd64.deb
Size: 60824
MD5sum: ab1d273990915238c7fca0ea67c074f5
SHA1: ca96db3e21960cf1b36b66a444368e7749c4dc3d
SHA256: 2c1a4193aa68dfce9bcb4f37ea663d245815ee85457d7eb8f2d16fded72e90fa
Description-ru: модуль отображения информации от приложений на панели Xfce4
 Небольшое расширение для последовательного отображения информации от
 различных приложений в панели Xfce4 по правилам описанным в спецификации
 Ubuntu MessagingMenu design.
Description-md5: 9840efa394a05eab71be8c0a6217040f
Homepage: http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 3y
Task: xubuntu-core, xubuntu-desktop, mythbuntu-frontend, mythbuntu-desktop, 
mythbuntu-backend-slave, mythbuntu-backend-master, ubuntustudio-desktop-core, 
ubuntustudio-desktop

** Affects: xfce4-indicator-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/1583164

Title:
  Panel Indicator uses 25% cpu

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

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

[Bug 1582878] Re: panel-6-indicat uses 25% CPU

[Romik Forest]

$ top
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2183 romik 20 0 446808 35028 26832 S 21,3 0,9 2:21.52 panel-6-indicat

$ ps ax | grep panel
 2183 ? Rl 0:43 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 6 16777271 
indicator Индикаторы Предоставляет место на панели для индикаторов Unity. 
Индикаторы позволяют приложениям и системным сервисам показывать свой статус и 
взаимодействовать с пользователем.

$ dpkg -S /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so
xfce4-indicator-plugin: 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so

$ apt-cache show xfce4-indicator-plugin
Package: xfce4-indicator-plugin
Priority: optional
Section: universe/xfce
Installed-Size: 370
Maintainer: Xubuntu Developers 
Original-Maintainer: Debian Xfce Maintainers 

Architecture: amd64
Version: 2.3.3-0ubuntu4
Provides: indicator-renderer
Depends: libc6 (>= 2.4), libdbus-glib-1-2 (>= 0.78), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.6), libido3-0.1-0 (>= 
13.10.0daily13.06.19), libindicator3-7 (>= 0.4.90), libxfce4panel-2.0-4 (>= 
4.11.0), libxfce4ui-2-0 (>= 4.11.0), libxfce4util7 (>= 4.9.0), libxfconf-0-2 
(>= 4.6.0), upstart
Filename: 
pool/universe/x/xfce4-indicator-plugin/xfce4-indicator-plugin_2.3.3-0ubuntu4_amd64.deb
Size: 60824
MD5sum: ab1d273990915238c7fca0ea67c074f5
SHA1: ca96db3e21960cf1b36b66a444368e7749c4dc3d
SHA256: 2c1a4193aa68dfce9bcb4f37ea663d245815ee85457d7eb8f2d16fded72e90fa
Description-ru: модуль отображения информации от приложений на панели Xfce4
 Небольшое расширение для последовательного отображения информации от
 различных приложений в панели Xfce4 по правилам описанным в спецификации
 Ubuntu MessagingMenu design.
Description-md5: 9840efa394a05eab71be8c0a6217040f
Homepage: http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Supported: 3y
Task: xubuntu-core, xubuntu-desktop, mythbuntu-frontend, mythbuntu-desktop, 
mythbuntu-backend-slave, mythbuntu-backend-master, ubuntustudio-desktop-core, 
ubuntustudio-desktop

P.S. I use xfce4 + compiz

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

Title:
  panel-6-indicat uses 25% CPU

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

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