[Touch-packages] [Bug 2064363] Re: thunderbird snap on live systems "already running" but not responsive

[Douglas Lucas]

@u-jjohansen,

You ask:

```
what kind of configuration have you done? 
```

I just:

```
sudo apt update
sudo apt install thunderbird
cp -R /media/lubuntu/drive/startup/thunderbird 
/home/lubuntu/snap/thunderbird/common/.thunderbird
cp /media/lubuntu/drive/startup/lubuntu_thunder/profiles.ini 
/home/lubuntu/snap/thunderbird/common/.thunderbird/
```

None of these are symlinked as far as I know. That profiles.ini has a
few profiles in it that tell Thunderbird to look for the PATH on the
local hard drive as opposed to the RAMdisk, e.g.

```
Path=/media/lubuntu/drive/hq/email/thunderbird/certainprofilegoeshere
```

Beyond the above, I haven't really done any config.

I'm no expert, but your #2 and #3 solutions seem too complicated for my
enduser use cases. Maybe #1 would be the easiest? #4 also might be a
longterm solution. #5 seems too risky. So yeah, I'm thinking either #1
or #4 ... but not sure :\

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2064363

Title:
  thunderbird snap on live systems "already running" but not responsive

Status in apparmor package in Ubuntu:
  New

Bug description:
  Moving this here from
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

  snap policy on an overlay system is preventing thunderbird from
  running. This is related to the snapcraft form report
  https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
  but-is-not-responding-message/39990

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2064363] Re: thunderbird snap on live systems "already running" but not responsive

[Douglas Lucas]

@u-jjohansen

```
$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=7984072k,nr_inodes=1996018,mode=755,inode64)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=1605152k,mode=755,inode64)
/dev/sdb1 on /cdrom type vfat 
(ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on /rofs type squashfs (ro,noatime,errors=continue,threads=single)
/cow on / type overlay 
(rw,relatime,lowerdir=/filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work,uuid=on,xino=off,nouserxattr)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1466)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs 
(rw,nosuid,nodev,relatime,pagesize=2M)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
/var/lib/snapd/snaps/bare_5.snap on /snap/bare/5 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/firmware-updater_127.snap on /snap/firmware-updater/127 
type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/firefox_4173.snap on /snap/firefox/4173 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core22_1380.snap on /snap/core22/1380 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gnome-42-2204_176.snap on /snap/gnome-42-2204/176 type 
squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,inode64)
/var/lib/snapd/snaps/gtk-common-themes_1535.snap on 
/snap/gtk-common-themes/1535 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_21465.snap on /snap/snapd/21465 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1605148k,nr_inodes=401287,mode=700,uid=1000,gid=1000,inode64)
tmpfs on /run/snapd/ns type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=1605152k,mode=755,inode64)
nsfs on /run/snapd/ns/firefox.mnt type nsfs (rw)
/cow on /var/snap/firefox/common/host-hunspell type overlay 
(ro,noexec,noatime,lowerdir=/filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work,uuid=on,xino=off,nouserxattr)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
nsfs on /run/snapd/ns/firmware-updater.mnt type nsfs (rw)
/dev/mapper/luks-a2e355f4-be9b-4894-a5c5-32b52e33067a on /media/lubuntu/drive 
type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/var/lib/snapd/snaps/thunderbird_470.snap on /snap/thunderbird/470 type 
squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
nsfs on /run/snapd/ns/thunderbird.mnt type nsfs (rw)
portal on /run/user/1000/doc type fuse.portal 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/var/lib/snapd/snaps/cups_1044.snap on /snap/cups/1044 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
nsfs on /run/snapd/ns/cups.mnt type nsfs (rw)
/var/lib/snapd/snaps/chromium_2828.snap on /snap/chromium/2828 type squashfs 
(ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
nsfs on /run/snapd/ns/chromium.mnt type nsfs (rw)
```

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2064363

Title:
  thunderbird snap on live systems "already running" but not responsive

Status in apparmor package in Ubuntu:
  New

Bug description:
  Moving this here from
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

  snap policy on an overlay 

[Touch-packages] [Bug 2064363] Re: thunderbird snap on live systems "already running" but not responsive

[Douglas Lucas]

Oh also, by using

```
~/.thunderbird/p0dln6zn.default$ ls -A
```

I just noticed there's a .parentlock right now in that directory ... in
case it's relevant

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2064363

Title:
  thunderbird snap on live systems "already running" but not responsive

Status in apparmor package in Ubuntu:
  New

Bug description:
  Moving this here from
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

  snap policy on an overlay system is preventing thunderbird from
  running. This is related to the snapcraft form report
  https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
  but-is-not-responding-message/39990

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2064363] Re: thunderbird snap on live systems "already running" but not responsive

[Douglas Lucas]

@u-jjohansen:

```
$ mount | grep overlay
/cow on / type overlay 
(rw,relatime,lowerdir=/filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work,uuid=on,xino=off,nouserxattr)
/cow on /var/snap/firefox/common/host-hunspell type overlay 
(ro,noexec,noatime,lowerdir=/filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work,uuid=on,xino=off,nouserxattr)
```

Also, in case it helps, I run this script upon booting the live cd image:
```
$ cat thunder2.sh
cp -R /media/lubuntu/drive/startup/thunderbird 
/home/lubuntu/snap/thunderbird/common/.thunderbird
cp /media/lubuntu/drive/startup/lubuntu_thunder/profiles.ini 
/home/lubuntu/snap/thunderbird/common/.thunderbird/
```

Previously I was running thunder.sh (this below worked in all prior
Lubuntu versions):

```
$ cat thunder.sh
cp -R /media/lubuntu/drive/startup/thunderbird /home/lubuntu/.thunderbird
cp /media/lubuntu/drive/startup/lubuntu_thunder/profiles.ini 
/home/lubuntu/.thunderbird/
```

But with the conversion of thunderbird into snap only, I had to change
the directories.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2064363

Title:
  thunderbird snap on live systems "already running" but not responsive

Status in apparmor package in Ubuntu:
  New

Bug description:
  Moving this here from
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

  snap policy on an overlay system is preventing thunderbird from
  running. This is related to the snapcraft form report
  https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
  but-is-not-responding-message/39990

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Douglas Lucas]

@u-jjohansen:

```
$ sudo dmesg | grep DENIED
[   20.729222] audit: type=1400 audit(1714359674.872:42): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" 
name="/usr/local/share/" pid=2002 comm="6" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
[   20.743227] audit: type=1400 audit(1714359674.886:43): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743368] audit: type=1400 audit(1714359674.886:44): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743817] audit: type=1400 audit(1714359674.886:45): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   20.743821] audit: type=1400 audit(1714359674.886:46): apparmor="DENIED" 
operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" 
pid=2002 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[  496.181770] audit: type=1400 audit(1714360150.324:49): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=2609 comm="(python3)"
[  526.667987] audit: type=1400 audit(1714360181.273:50): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=2767 comm="(python3)"
[  554.736942] audit: type=1400 audit(1714360209.342:51): apparmor="DENIED" 
operation="change_onexec" class="file" info="label not found" error=-2 
profile="unconfined" name="ubuntu_pro_apt_news" pid=3216 comm="(python3)"
[ 2204.153512] audit: type=1400 audit(1714361858.768:60): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 
comm="snap-confine" capability=12  capname="net_admin"
[ 2204.153520] audit: type=1400 audit(1714361858.768:61): apparmor="DENIED" 
operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=8056 
comm="snap-confine" capability=38  capname="perfmon"
[ 2205.965365] audit: type=1107 audit(1714361860.578:62): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.2" pid=8056 label="snap.firefox.firefox" peer_pid=1382 
peer_label="unconfined"
[ 2206.032369] audit: type=1107 audit(1714361860.647:63): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 
peer_label="unconfined"
[ 2206.032740] audit: type=1107 audit(1714361860.647:64): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.83" pid=8056 label="snap.firefox.firefox" peer_pid=8746 
peer_label="unconfined"
[ 2206.331239] audit: type=1400 audit(1714361860.946:65): apparmor="DENIED" 
operation="open" class="file" profile="snap.firefox.firefox" 
name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=8056 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2990.682061] audit: type=1400 audit(1714362645.300:66): apparmor="DENIED" 
operation="open" class="file" profile="snap.firefox.firefox" 
name="/etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini" pid=12989 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2991.168924] audit: type=1107 audit(1714362645.787:67): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.2" pid=12989 label="snap.firefox.firefox" peer_pid=1382 
peer_label="unconfined"
[ 2991.217994] audit: type=1107 audit(1714362645.836:68): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.107" pid=12989 label="snap.firefox.firefox" peer_pid=13639 
peer_label="unconfined"
[ 2991.218729] audit: type=1107 audit(1714362645.837:69): pid=1389 uid=101 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/timedate1" 

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Douglas Lucas]

@u-jjohansen:

Also, I'm having this Thunderbird problem going on simultaneously --
https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
but-is-not-responding-message/39990 -- which might be related to the
issues from my Chrome comments?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Douglas Lucas]

@u-jjohansen:

Yes, live environment only. Sorry, I thought I'd included that in my
first comment but now I see that I neglected to do so. I added an EDIT:
to my first comment to make it clear.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Douglas Lucas]

@jjohansen:


```
$ sudo aa-status
apparmor module is loaded.
56 profiles are loaded.
54 profiles are in enforce mode.
   /snap/snapd/21465/usr/lib/snapd/snap-confine
   /snap/snapd/21465/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   libreoffice-senddocists=!/rofs/etc/apparmor.d).
   libreoffice-soffice//gpg
   libreoffice-xpdfimport
   rsyslogd
   snap-update-ns.chromium
   snap-update-ns.cups
   snap-update-ns.firefox
   snap-update-ns.firmware-updater
   snap-update-ns.thunderbird
   snap.chromium.chromedriver
   snap.chromium.chromium
   snap.chromium.hook.configure
   snap.cups.accept
   snap.cups.cancel
   snap.cups.cups-browsed
   snap.cups.cupsaccept
   snap.cups.cupsctl
   snap.cups.cupsd
   snap.cups.cupsdisable
   snap.cups.cupsenable
   snap.cups.cupsfilter
   snap.cups.cupsreject
   snap.cups.cupstestppd
   snap.cups.driverless
   snap.cups.gs
   snap.cups.ippeveprinter
   snap.cups.ippfind
   snap.cups.ipptool
   snap.cups.lp
   snap.cups.lpadmin
   snap.cups.lpc
   snap.cups.lpinfo
   snap.cups.lpoptions
   snap.cups.lpq
   snap.cups.lpr
   snap.cups.lprm
   snap.cups.lpstat
   snap.cups.reject
   snap.firefox.firefox
   snap.firefox.geckodriver
   snap.firefox.hook.configure
   snap.firefox.hook.connect-plug-host-hunspell
   snap.firefox.hook.disconnect-plug-host-hunspell
   snap.firefox.hook.post-refresh
   snap.firmware-updater.firmware-notifier
   snap.firmware-updater.firmware-updater
   snap.firmware-updater.firmware-updater-app
   snap.firmware-updater.hook.configure
   snap.thunderbird.hook.configure
   snap.thunderbird.thunderbird
2 profiles are in complain mode.
   libreoffice-oosplash
   libreoffice-soffice
0 profiles are in prompt mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
31 processes have profiles defined.
31 processes are in enforce mode.
   /usr/sbin/rsyslogd (1472) rsyslogd
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77339) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77395) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome_crashpad_handler (77397) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77401) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77402) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77404) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77433) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77441) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (77443) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (78308) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (78968) 
snap.chromium.chromium
   /snap/chromium/2828/usr/lib/chromium-browser/chrome (79729) 
snap.chromium.chromium
   /usr/bin/dash (18605) snap.cups.cups-browsed
   /usr/bin/dash (18912) snap.cups.cups-browsed
   /usr/bin/sleep (92417) snap.cups.cups-browsed
   /usr/bin/dash (18607) snap.cups.cupsd
   /snap/cups/1044/sbin/cupsd (18745) snap.cups.cupsd
   /snap/firefox/4173/usr/lib/firefox/firefox (50912) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (51554) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (51573) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52145) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52713) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (52829) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (57517) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (59890) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (84921) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (85070) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (87511) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (93200) snap.firefox.firefox
   /snap/firefox/4173/usr/lib/firefox/firefox (93235) snap.firefox.firefox
0 processes are in complain mode.
0 processes are in prompt mode.
0 processes are in kill mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
```

```
$ sudo systemctl status apparmor
Warning: The unit file, source configuration file or drop-ins of 
apparmor.service changed on disk. Run 'systemctl daemon-reload' to reload units.
○ apparmor.service - Load AppArmor profiles
 Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: 
enabled)
 Active: inactive (dead)
  Condition: start condition unmet at Sun 2024-04-28 20:01:04 PDT; 1 day 12h ago
   Docs: man:apparmor(7)
 https://gitlab.com/apparmor/apparmor/wikis/home/

Apr 28 20:01:02 lubuntu 

[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Douglas Lucas]

I seem to have the same apparmor problem with Chrome under Lubuntu
24.04. From "$ journalctl | grep apparmor | grep chrome" I got
info="Userns create restricted - failed to find unprivileged_userns
profile" (among other things). And it's been reproduced by another as
the following relates.

Can anyone help? Much more detail below. And you can email me:
d...@riseup.net.

Prior Lubuntu versions, I wget'd the latest Chrome deb from Google and
installed it via sudo dpkg -i. Usually it worked quite well. Now with
Lubuntu 24.04, I downloaded the latest Chrome deb the same way on Apr.
28, 2024, but Chrome's not working.

If I run /usr/bin/google-chrome or /usr/bin/google-chrome-stable:

```
$ google-chrome
[55151:55151:0428/224255.271437:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
Trace/breakpoint trap (core dumped)
```

or

```
$ google-chrome-stable
[55166:55166:0428/224300.689874:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
Trace/breakpoint trap (core dumped)
```

Meanwhile, $ sudo netstat -antvp shows active connections to multiple
IPs associated with Google, presumably because I tried multiple times to
get Chrome to launch.

Then,

```
$ ls /etc/apparmor.d
1password   firefox lxc-stop rootlesskit   
scide  usr.bin.redshift
Discord flatpak lxc-unshare  rpm   
signal-desktop usr.bin.tcpdump
MongoDB_Compass force-complain  lxc-usernsexec   rssguard  
slack  usr.lib.libreoffice.program.oosplash
QtWebEngineProcess  geary   mmdebstrap   rsyslog.d 
slirp4netnsusr.lib.libreoffice.program.senddoc
abi github-desktop  msedge   runc  
steam  usr.lib.libreoffice.program.soffice.bin
abstractionsgoldendict  nautilus sbuild
stress-ng  usr.lib.libreoffice.program.xpdfimport
brave   ipa_verify  notepadqqsbuild-abort  
surfshark  usr.lib.snapd.snap-confine.real
buildah kchmviewer  nvidia_modprobe  sbuild-adduser
systemd-coredump   usr.sbin.cups-browsed
busybox keybase obsidian sbuild-apt
thunderbirdusr.sbin.cupsd
cam lc-compliance   opam sbuild-checkpackages  
toybox usr.sbin.rsyslogd
ch-checkns  libcamerify operasbuild-clean  
trinityuwsgi-core
ch-run  linux-sandbox   pageedit sbuild-createchroot   
tunables   vdens
chrome  local   plasmashell  sbuild-destroychroot  tup  
  virtiofsd
codeloupe   podman   sbuild-distupgrade
tuxedo-control-center  vivaldi-bin
crunlsb_release polypane sbuild-hold   
ubuntu_pro_apt_newsvpnns
devhelp lxc-attach  privacybrowser   sbuild-shell  
unix-chkpwdwpcom
element-desktop lxc-create  qcam sbuild-unhold 
unprivileged_userns
epiphanylxc-destroy qmapshacksbuild-update 
userbindmount
evolution   lxc-execute qutebrowser  sbuild-upgrade
usr.bin.man
```

and

```
$ cat /etc/apparmor.d/chrome
# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"

abi ,
include 

profile chrome /opt/google/chrome/chrome flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}
```

This didn't work either:

```
$ /opt/google/chrome/chrome
[0429/105700.793962:WARNING:chrome_main_linux.cc(80)] Read channel stable from 
/opt/google/chrome/CHROME_VERSION_EXTRA
[66808:66808:0429/105700.802212:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
Trace/breakpoint trap (core dumped)
```

Note that I also ran this:

```
$ journalctl | grep apparmor | grep chrome
Apr 28 21:22:42 lubuntu kernel: audit: type=1400 audit(1714364562.824:140): 
apparmor="STATUS" operation="profile_replace" profile="unconfined" 
name="snap.chromium.chromedriver" pid=19182 comm="apparmor_parser"
Apr 28 22:04:11 lubuntu kernel: audit: type=1400 audit(1714367051.521:200): 
apparmor="DENIED" operation="userns_create" class="namespace" info="Userns 
create restricted - failed to find unprivileged_userns profile" error=-13 
profile="unconfined" pid=46114 comm="chrome" requested="userns_create" 
denied="userns_create" target="unprivileged_userns"
```

Someone else reproduced this, following these steps:
```
1. figured out what version of apparmor contained the fix
2. booted the live image
3. checked that the version of apparmor on the live image was greater than 
or equal to the version with the fix
4. 

[Touch-packages] [Bug 1700756] Re: HDMI not working

[Ian Douglas]

Still exists in Ubuntu 22.04 with NVidia driver 390.157  DP works HDMI
shows as connected, but no output to monitor.  HDMI cable works with Mac
Monterey but DP does not.

Nouveau driver works with both ports but the external display speed is
very slow and choppy even if I add PiP and use both ports at 60Hz to
drive half the screen each.  So watching Netflix or any other stream is
impossible to enjoy.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1700756

Title:
  HDMI not working

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Ever since updating nvidia driver to nvidia-381 the external HDMI connectors 
stopped working.
  Neither the native HDMI port nor HDMI over Thunderbolt works.

  The driver recognizes the external monitor (existence and resolution)
  but does not provide a picture. Thunderbolt #1 never worked before but
  Thunderbolt #2 and the HDMI port worked in 16.10.

  The ports are fine (I can boot into MacOS and find all three
  combinations working).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Jun 27 14:18:06 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2017-05-25 (32 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  LightdmLog:
   [+21747.08s] DEBUG: Seat seat0 changes active session to 
   [+21750.55s] DEBUG: Seat seat0 changes active session to c2
   [+21750.55s] DEBUG: Session c2 is already active
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Mon Jun 26 07:46:39 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1978108] [NEW] totem doesn't detect newly installed gstreamer plugin

[Douglas Silva]

Public bug reported:

So you just installed Ubuntu 22.04 and you try to play an mp4 video.
Totem will complain about missing an H.264 decoder, as you can see in
the command line output:

Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main
Profile)|decoder-video/x-h264, level=(string)3, profile=(string)main
(decodificador H.264 (Main Profile))

You will now install gstreamer1.0-libav and try again, but it will still
fail with the same complaint.

The solution, as others have found
(https://askubuntu.com/a/407595/818746), is:

$ rm -rf ~/.cache/gstreamer-1.0/

I suppose that is a bug.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgstreamer1.0-0 1.20.1-1
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  9 08:06:35 2022
InstallationDate: Installed on 2022-06-09 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug jammy wayland-session

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1978108

Title:
  totem doesn't detect newly installed gstreamer plugin

Status in gstreamer1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  So you just installed Ubuntu 22.04 and you try to play an mp4 video.
  Totem will complain about missing an H.264 decoder, as you can see in
  the command line output:

  Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main
  Profile)|decoder-video/x-h264, level=(string)3, profile=(string)main
  (decodificador H.264 (Main Profile))

  You will now install gstreamer1.0-libav and try again, but it will
  still fail with the same complaint.

  The solution, as others have found
  (https://askubuntu.com/a/407595/818746), is:

  $ rm -rf ~/.cache/gstreamer-1.0/

  I suppose that is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 08:06:35 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978108/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1970068] Re: L2TP+IPSec not working after upgrade to 22.04 LTS

[Douglas Kosovic]

I think this is a duplicate of the following, although the xl2tpd errors 
manifest slightly differently :
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1968336

But as others have confirmed, Ubuntu 22.05's xl2tpd-1.3.16-1 is broken,
so the most likely culprit.


network-manager-l2tp uses kl2tpd as its default L2TP daemon and falls back to 
xl2tpd if it can't find kl2tpd. To confirm it is only xl2tpd that is broken for 
you, try installing kl2tpd with the following :

sudo apt install golang-go

go install "github.com/katalix/go-l2tp/...@latest"
sudo mkdir /usr/local/sbin
sudo cp go/bin/kl2tpd /usr/local/sbin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1970068

Title:
  L2TP+IPSec not working after upgrade to 22.04 LTS

Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in ppp package in Ubuntu:
  New
Status in xl2tpd package in Ubuntu:
  New

Bug description:
  In 20.04LTS i was able to connect to my work over the L2TP tunel. Now
  it seems like this in journald:

  kwi 24 01:00:37 nm-l2tp-service[11368]: xl2tpd started with pid 11433
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Not looking for kernel 
SAref support.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Using l2tp kernel 
support.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: xl2tpd version 
xl2tpd-1.3.16 started on crushXnitro PID:11433
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Written by Mark 
Spencer, Copyright (C) 1998, Adtran, Inc.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked by Scott Balmos 
and David Stipp, (C) 2001
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Inherited by Jeff 
McAdams, (C) 2002
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked again by 
Xelerance (www.xelerance.com) (C) 2006-2016
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Listening on IP address 
0.0.0.0, port 49636
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connecting to host 
X.X.X.X, port 1701
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connection established 
to X.X.X.X, 1701.  Local: 19994, Remote: 201 (ref=0/0).
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Calling on tunnel 19994
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Call established with 
X.X.X.X, Local: 65441, Remote: 142, Serial: 1 (ref=0/0)
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: start_pppd: I'm running:
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "/usr/sbin/pppd"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "plugin"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp.so"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "7"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "passive"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "nodetach"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: ":"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "file"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: 
"/run/nm-l2tp-bd8ac49b-a2e9-4094-91dc-17a13ce61ec8/ppp-options"
  kwi 24 01:00:37 pppd[11434]: Plugin pppol2tp.so loaded.
  kwi 24 01:00:37 pppd[11434]: Plugin 
/usr/lib/pppd/2.4.9/nm-l2tp-pppd-plugin.so loaded.
  kwi 24 01:00:37 pppd[11434]: pppd 2.4.9 started by root, uid 0
  kwi 24 01:00:37 pppd[11434]: Using interface ppp0
  kwi 24 01:00:37 pppd[11434]: Connect: ppp0 <-->
  kwi 24 01:00:37 pppd[11434]: Overriding mtu 1500 to 1400
  kwi 24 01:00:37 pppd[11434]: Overriding mru 1500 to mtu value 1400
  kwi 24 01:00:37 NetworkManager[1017]:   [1650754837.9839] manager: 
(ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/6)
  kwi 24 01:00:38 pppd[11434]: CHAP authentication succeeded
  kwi 24 01:00:38 charon[11397]: 10[KNL] interface ppp0 activated
  kwi 24 01:00:38 charon[11397]: 13[KNL] fe80::81ee:6717:6637:2084 appeared on 
ppp0
  kwi 24 01:00:38 charon[11397]: 14[KNL] flags changed for 
fe80::81ee:6717:6637:2084 on ppp0
  kwi 24 01:00:38 pppd[11434]: local  LL address fe80::81ee:6717:6637:2084
  kwi 24 01:00:38 pppd[11434]: remote LL address fe80::::00f0:0c0e
  kwi 24 01:00:38 charon[11397]: 16[KNL] 192.168.57.181 appeared on ppp0
  kwi 24 01:00:38 NetworkManager[1017]:   [1650754838.0741] device 
(ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', 
sys-iface-state: 'external')
  kwi 24 01:00:38 charon[11397]: 08[KNL] 192.168.57.181 disappeared from ppp0
  kwi 24 01:00:38 charon[11397]: 10[KNL] 192.168.57.181 appeared on ppp0
  kwi 24 01:00:38 NetworkManager[1017]:   [1650754838.0751] device 
(ppp0): state change: unavailable -> disconnected (reason 'none', 
sys-iface-state: 'external')
  kwi 24 

[Touch-packages] [Bug 1956062] Re: vim mis-manages modifyOtherKeys on xterms

[Douglas Miller]

What version of vim is planned for 22.04? Will these fixes be included?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1956062

Title:
  vim mis-manages modifyOtherKeys on xterms

Status in vim package in Ubuntu:
  New

Bug description:
  This began as question #76. I've observed odd behavior in vim
  since my upgrade from 18.04 to 20.04. One in particular is when I use
  the "r" command to replace a single character, shifted letters fail to
  work correctly and vim sputters and changes the case of letters in the
  line, instead of replace a single character. Another place is in
  search strings where I want to use the carriage-return character and
  type Ctrl-V Ctrl-M, the Ctrl-M appears as an ESC sequence instead of
  "^M" and the search fails to do what I intended.

  Analyzing the problem in question #76 revealed this:

  When vim initializes (the xterm), it sends "^[[>4;2m" which sets the
  modifyOtherKeys=2 parameter. This appears to send *any* keys that use
  modifiers (Shift, Ctrl, Alt) as ESC sequences, as we've seen. This
  explains why the un-shifted keys "r" and "s" appear normally. But, it
  appears that there are certain cases where vim is not properly
  interpreting the sequences that it requested.

  In the case of the "s" command, vim sends an "^[[>4;m"
  (modifyOtherKeys=0) before I can type the "A", so the "A" comes in as
  a normal ASCII character. It appears that vim should also be doing the
  same thing for "r" but does not. There are probably other contexts
  where vim is failing to properly manage the modifyOtherKeys setting,
  such as when I try ^V^M in search commands.

  In the case of the "r" command, vim sends no ESC sequences after the
  "r" so the "A" comes in as the ESC sequence "^[[27;2;65~" and confuses
  vim.

  In the case of search commands, vim is also failing to reset the
  modifyOtherKeys setting, so the ^V and ^M are sent as ESC sequences -
  although it appears that vim recognizes the ^V "^[[27;5;118~" and then
  (correctly) ignores the ESC in the ^M sequence "^[[27;5;109~". FYI, I
  understand that vim can now recognize "\r" in search strings, but that
  still leaves the problem of all the other control characters I must
  often manipulate in search commands.

  It is looking now as though there is actually a bug in vim, where it
  does not properly manage the modifyOtherKeys setting even though it
  explicitly requests that setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim 2:8.1.2269-1ubuntu5.4
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 30 15:49:03 2021
  InstallationDate: Installed on 2017-02-22 (1772 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to focal on 2020-10-04 (451 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1956062] Re: vim mis-manages modifyOtherKeys on xterms

[Douglas Miller]

Examining the raw I/O between this new vim and my xterm, I see that the
'r' command is now turning off modifyOtherKeys (and then back on after
the replacement character is typed). So, it would appear that there is a
fix to this upstream, and Ubuntu vim is just lacking that fix.

As far as use of ^V in a ":s/" search command, it appears that vim is
simply properly interpreting "^[[27;5;109~" now, rather than inserting
the whole sequence literally.

So, it appears that the version of vim currently in 20.04 is lacking
some fixes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1956062

Title:
  vim mis-manages modifyOtherKeys on xterms

Status in vim package in Ubuntu:
  New

Bug description:
  This began as question #76. I've observed odd behavior in vim
  since my upgrade from 18.04 to 20.04. One in particular is when I use
  the "r" command to replace a single character, shifted letters fail to
  work correctly and vim sputters and changes the case of letters in the
  line, instead of replace a single character. Another place is in
  search strings where I want to use the carriage-return character and
  type Ctrl-V Ctrl-M, the Ctrl-M appears as an ESC sequence instead of
  "^M" and the search fails to do what I intended.

  Analyzing the problem in question #76 revealed this:

  When vim initializes (the xterm), it sends "^[[>4;2m" which sets the
  modifyOtherKeys=2 parameter. This appears to send *any* keys that use
  modifiers (Shift, Ctrl, Alt) as ESC sequences, as we've seen. This
  explains why the un-shifted keys "r" and "s" appear normally. But, it
  appears that there are certain cases where vim is not properly
  interpreting the sequences that it requested.

  In the case of the "s" command, vim sends an "^[[>4;m"
  (modifyOtherKeys=0) before I can type the "A", so the "A" comes in as
  a normal ASCII character. It appears that vim should also be doing the
  same thing for "r" but does not. There are probably other contexts
  where vim is failing to properly manage the modifyOtherKeys setting,
  such as when I try ^V^M in search commands.

  In the case of the "r" command, vim sends no ESC sequences after the
  "r" so the "A" comes in as the ESC sequence "^[[27;2;65~" and confuses
  vim.

  In the case of search commands, vim is also failing to reset the
  modifyOtherKeys setting, so the ^V and ^M are sent as ESC sequences -
  although it appears that vim recognizes the ^V "^[[27;5;118~" and then
  (correctly) ignores the ESC in the ^M sequence "^[[27;5;109~". FYI, I
  understand that vim can now recognize "\r" in search strings, but that
  still leaves the problem of all the other control characters I must
  often manipulate in search commands.

  It is looking now as though there is actually a bug in vim, where it
  does not properly manage the modifyOtherKeys setting even though it
  explicitly requests that setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim 2:8.1.2269-1ubuntu5.4
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 30 15:49:03 2021
  InstallationDate: Installed on 2017-02-22 (1772 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to focal on 2020-10-04 (451 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1956062] Re: vim mis-manages modifyOtherKeys on xterms

[Douglas Miller]

I cloned the vim github repo and did a default build (version 8.2.4014),
that version of vim does not exhibit any of this odd behavior. Seems
likely that either something has fixed this upstream or else Ubuntu
20.04 vim build enables some feature that causes this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1956062

Title:
  vim mis-manages modifyOtherKeys on xterms

Status in vim package in Ubuntu:
  New

Bug description:
  This began as question #76. I've observed odd behavior in vim
  since my upgrade from 18.04 to 20.04. One in particular is when I use
  the "r" command to replace a single character, shifted letters fail to
  work correctly and vim sputters and changes the case of letters in the
  line, instead of replace a single character. Another place is in
  search strings where I want to use the carriage-return character and
  type Ctrl-V Ctrl-M, the Ctrl-M appears as an ESC sequence instead of
  "^M" and the search fails to do what I intended.

  Analyzing the problem in question #76 revealed this:

  When vim initializes (the xterm), it sends "^[[>4;2m" which sets the
  modifyOtherKeys=2 parameter. This appears to send *any* keys that use
  modifiers (Shift, Ctrl, Alt) as ESC sequences, as we've seen. This
  explains why the un-shifted keys "r" and "s" appear normally. But, it
  appears that there are certain cases where vim is not properly
  interpreting the sequences that it requested.

  In the case of the "s" command, vim sends an "^[[>4;m"
  (modifyOtherKeys=0) before I can type the "A", so the "A" comes in as
  a normal ASCII character. It appears that vim should also be doing the
  same thing for "r" but does not. There are probably other contexts
  where vim is failing to properly manage the modifyOtherKeys setting,
  such as when I try ^V^M in search commands.

  In the case of the "r" command, vim sends no ESC sequences after the
  "r" so the "A" comes in as the ESC sequence "^[[27;2;65~" and confuses
  vim.

  In the case of search commands, vim is also failing to reset the
  modifyOtherKeys setting, so the ^V and ^M are sent as ESC sequences -
  although it appears that vim recognizes the ^V "^[[27;5;118~" and then
  (correctly) ignores the ESC in the ^M sequence "^[[27;5;109~". FYI, I
  understand that vim can now recognize "\r" in search strings, but that
  still leaves the problem of all the other control characters I must
  often manipulate in search commands.

  It is looking now as though there is actually a bug in vim, where it
  does not properly manage the modifyOtherKeys setting even though it
  explicitly requests that setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim 2:8.1.2269-1ubuntu5.4
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 30 15:49:03 2021
  InstallationDate: Installed on 2017-02-22 (1772 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to focal on 2020-10-04 (451 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1956062] [NEW] vim mis-manages modifyOtherKeys on xterms

[Douglas Miller]

Public bug reported:

This began as question #76. I've observed odd behavior in vim since
my upgrade from 18.04 to 20.04. One in particular is when I use the "r"
command to replace a single character, shifted letters fail to work
correctly and vim sputters and changes the case of letters in the line,
instead of replace a single character. Another place is in search
strings where I want to use the carriage-return character and type
Ctrl-V Ctrl-M, the Ctrl-M appears as an ESC sequence instead of "^M" and
the search fails to do what I intended.

Analyzing the problem in question #76 revealed this:

When vim initializes (the xterm), it sends "^[[>4;2m" which sets the
modifyOtherKeys=2 parameter. This appears to send *any* keys that use
modifiers (Shift, Ctrl, Alt) as ESC sequences, as we've seen. This
explains why the un-shifted keys "r" and "s" appear normally. But, it
appears that there are certain cases where vim is not properly
interpreting the sequences that it requested.

In the case of the "s" command, vim sends an "^[[>4;m"
(modifyOtherKeys=0) before I can type the "A", so the "A" comes in as a
normal ASCII character. It appears that vim should also be doing the
same thing for "r" but does not. There are probably other contexts where
vim is failing to properly manage the modifyOtherKeys setting, such as
when I try ^V^M in search commands.

In the case of the "r" command, vim sends no ESC sequences after the "r"
so the "A" comes in as the ESC sequence "^[[27;2;65~" and confuses vim.

In the case of search commands, vim is also failing to reset the
modifyOtherKeys setting, so the ^V and ^M are sent as ESC sequences -
although it appears that vim recognizes the ^V "^[[27;5;118~" and then
(correctly) ignores the ESC in the ^M sequence "^[[27;5;109~". FYI, I
understand that vim can now recognize "\r" in search strings, but that
still leaves the problem of all the other control characters I must
often manipulate in search commands.

It is looking now as though there is actually a bug in vim, where it
does not properly manage the modifyOtherKeys setting even though it
explicitly requests that setting.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vim 2:8.1.2269-1ubuntu5.4
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 30 15:49:03 2021
InstallationDate: Installed on 2017-02-22 (1772 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: vim
UpgradeStatus: Upgraded to focal on 2020-10-04 (451 days ago)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1956062

Title:
  vim mis-manages modifyOtherKeys on xterms

Status in vim package in Ubuntu:
  New

Bug description:
  This began as question #76. I've observed odd behavior in vim
  since my upgrade from 18.04 to 20.04. One in particular is when I use
  the "r" command to replace a single character, shifted letters fail to
  work correctly and vim sputters and changes the case of letters in the
  line, instead of replace a single character. Another place is in
  search strings where I want to use the carriage-return character and
  type Ctrl-V Ctrl-M, the Ctrl-M appears as an ESC sequence instead of
  "^M" and the search fails to do what I intended.

  Analyzing the problem in question #76 revealed this:

  When vim initializes (the xterm), it sends "^[[>4;2m" which sets the
  modifyOtherKeys=2 parameter. This appears to send *any* keys that use
  modifiers (Shift, Ctrl, Alt) as ESC sequences, as we've seen. This
  explains why the un-shifted keys "r" and "s" appear normally. But, it
  appears that there are certain cases where vim is not properly
  interpreting the sequences that it requested.

  In the case of the "s" command, vim sends an "^[[>4;m"
  (modifyOtherKeys=0) before I can type the "A", so the "A" comes in as
  a normal ASCII character. It appears that vim should also be doing the
  same thing for "r" but does not. There are probably other contexts
  where vim is failing to properly manage the modifyOtherKeys setting,
  such as when I try ^V^M in search commands.

  In the case of the "r" command, vim sends no ESC sequences after the
  "r" so the "A" comes in as the ESC sequence "^[[27;2;65~" and confuses
  vim.

  In the case of search commands, vim is also failing to reset the
  modifyOtherKeys setting, so the ^V and ^M are sent as ESC sequences -
  although it appears that vim recognizes the ^V "^[[27;5;118~" and then
  (correctly) ignores the ESC in the ^M sequence 

[Touch-packages] [Bug 1938959] [NEW] package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

[Douglas R Duarte]

Public bug reported:



ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Aug  4 19:47:44 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DpkgTerminalLog:
 dpkg: error processing package mesa-va-drivers:amd64 (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
 dpkg: too many errors, stopping
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
ExtraDebuggingInterest: Yes, including running git bisection searches
InstallationDate: Installed on 2020-04-01 (490 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
 Bus 001 Device 003: ID 045e:0752 Microsoft Corp. Wired Keyboard 400
 Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical 
Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 5: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=d7a0cf22-bba9-4c79-89f5-0d805b99da00 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: mesa
Title: package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1208
dmi.board.asset.tag: Default string
dmi.board.name: B250 MINING EXPERT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd09/24/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB250MININGEXPERT:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1938959

Title:
  package mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in mesa package in Ubuntu:
  New

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mesa-va-drivers:amd64 21.0.3-0ubuntu0.2~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Aug  4 19:47:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgTerminalLog:
   dpkg: error processing package mesa-va-drivers:amd64 (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
   dpkg: too many errors, stopping
  ErrorMessage: package is in a very bad inconsistent state; you 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Douglas Purdy]

This was a reinstall after Ubuntu 20.04 boot crashes after a recent
update. The same install options were selected for this reinstall.
Ubuntu had worked for months but after an update a month n or so ago it
always crashed at boot between the ubuntu logo and rotating circle's
shutoff and the login screen. This did not appear to have any relation
to the Invidia card boot fixes on the web. The disk has 3 areas rated
prefail like my other Ubuntu computer which has no problems.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1871268

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 

[Touch-packages] [Bug 1907496] [NEW] python-apt-common 2.1.3ubuntu1.1 Ubuntu.info doesn't have 'groovy'

[Ian Douglas Scott]

Public bug reported:

http://archive.ubuntu.com/ubuntu/pool/main/p/python-apt/python-apt-
common_2.1.3ubuntu1.1_all.deb lacks `Suite: groovy` in `Ubuntu.info`,
which is present in http://archive.ubuntu.com/ubuntu/pool/main/p/python-
apt/python-apt-common_2.1.3ubuntu1_all.deb.

I assume this is unintentional?

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1907496

Title:
  python-apt-common 2.1.3ubuntu1.1 Ubuntu.info doesn't have 'groovy'

Status in python-apt package in Ubuntu:
  New

Bug description:
  http://archive.ubuntu.com/ubuntu/pool/main/p/python-apt/python-apt-
  common_2.1.3ubuntu1.1_all.deb lacks `Suite: groovy` in `Ubuntu.info`,
  which is present in http://archive.ubuntu.com/ubuntu/pool/main/p
  /python-apt/python-apt-common_2.1.3ubuntu1_all.deb.

  I assume this is unintentional?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] Re: Sound doesn't switch to headphones automatically when plugged in

[Douglas Santos]

It seems to be very similar to bug 1881659, indeed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] Dependencies.txt

[Douglas Santos]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407106/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] ProcCpuinfoMinimal.txt

[Douglas Santos]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407107/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] PulseList.txt

[Douglas Santos]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407109/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] ProcEnviron.txt

[Douglas Santos]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407108/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] CurrentDmesg.txt

[Douglas Santos]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407105/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1893846] Re: Sound doesn't switch to headphones automatically when plugged in

[Douglas Santos]

apport information

** Tags added: apport-collected

** Description changed:

  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  douglas1859 F pulseaudio
+  /dev/snd/controlC1:  douglas1859 F pulseaudio
+  /dev/snd/controlC3:  douglas1859 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-25 (129 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio 1:13.99.1-1ubuntu3.6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
+ Tags:  focal
+ Uname: Linux 5.4.0-45-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/20/2012
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F10
+ dmi.board.name: Z68XP-UD3
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: Z68XP-UD3
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1893846/+attachment/5407104/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1893846

Title:
  Sound doesn't switch to headphones automatically when plugged in

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 20.04.1 LTS
  2) gnome-control-center 1:3.36.4-0ubuntu1
  3) What you expected to happen:I expected to connect my headphone and listen 
to any sound automatically.
  4) What happened instead: In order to make the headset work, I must go to the 
Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my 
Output Device, since the default is "Analog Output-Built-in Audio" (getting no 
sound from my headset).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1859 F pulseaudio
   /dev/snd/controlC1:  douglas1859 F pulseaudio
   /dev/snd/controlC3:  douglas1859 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (129 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Tags:  focal
  Uname: Linux 5.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: Z68XP-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68XP-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1849859] Re: smb printing fails

[Bruce Douglas]

This bug seems to still be active in Ubuntu 20.4
The   "AuthInfoRequired username,password" workarround  did NOT work on my 
system, as when I restarted cups, it rewrote the printers.conf file without the 
password and user.

However what did work for me was adding the printer and adding my
credentials at the same time in the SMB printer box! The format that
worked was username:password@host_computer/printername.  In the dialog,
it deletes the username and password on the smb: line but adds them in
the password and username boxes and this time writes them in the file.

This seems very strange to me but it works for me!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1849859

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

I forgot to tell you that I never see any dialog when I plug the
earphone. It's a feature of some desktop environments, right? I have
never seen it in Xfce.

The capture source changes to "headphone" every time I plug the
earphone, and when that happens, there is no sound output. Changing it
to any other source makes the sound work.

I don't remember how it worked in previous versions of Ubuntu. It just
worked. I never had to worry about switching the capture source in order
to have sound. If you think that's important to know, I can try a live
ISO of 18.04 and report back what I find.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

Oh, I can finally hear sound through the earphones by changing the
capture source. Too bad the change doesn't persist after I remove and
reinsert the connector. Every time that happens, I must change it to
Headset Mic, otherwise there will be no sound output.

It also works when I do it through the Pulseaudio GUI mixer that comes
with Xubuntu. Now I just wish the default selection could be one that
works out of the box, as it was in previous Ubuntu versions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

I have attached a screenshot of that screen, because I couldn't find any
Capture Source or Input Source there. Maybe it has a different name or
is missing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

** Attachment added: "screenshot alsamixer capture"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+attachment/5361512/+files/Captura%20de%20tela_2020-04-27_06-51-37.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

Running amixer sset 'Capture Source' 'Internal Mic' returns error:

amixer: Unable to find simple control 'Capture Source',0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1875249] [NEW] [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Douglas Silva]

Public bug reported:

Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no
sound output when you plug an earphone/headset. The built-in speakers,
on the other hand, are working properly. This is a laptop, Dell Inspiron
11 3162.

I checked volume levels with alsamixer, I played with the device
selection in the Pulseaudio mixer application, but nothing worked. I
also tested Firefox (playing a YouTube video) and system sounds. None of
them worked. The audio test made by apport-bug played no sound through
the earphone.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 3990 F pulseaudio
  dsilva 4791 F alsamixer
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Apr 26 18:12:06 2020
InstallationDate: Installed on 2020-04-24 (2 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 3990 F pulseaudio
  dsilva 4791 F alsamixer
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0NM68T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.sku: 0725
dmi.product.version: 2.4.0
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Summary changed:

- No sound output from earphones
+ [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound 
output from earphones

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875249

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

I think I can't reproduce this anymore on Xubuntu 20.04. I left the
laptop idle and after 30 minutes it was suspended as expected, without
making any fixes (clean install).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is
  unable to suspend the system when the user is inactive. A PK user-
  agent dialog is presented for the user to authenticate first - and as
  this action occurs specifically when the user is idle and away the PC
  can end up having an unplanned loss of power when the battery is
  exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Douglas]

I have Acer Aspire E5-573G-72UF, i have tested in Linux Mint 19.3 and
Ubuntu 20.04, and headset mic not woking.

Internal mic is ok, but i need headset for better talk.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1523100

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1851661] [NEW] AppArmor denied operation open to snap pick-colour-picker

[Douglas Silva]

Public bug reported:

I've written an issue here:
https://github.com/stuartlangridge/ColourPicker/issues/63

Pick (a color picker distributed as a snap) will not launch. The creator
of the application believes this to be a problem with my system, not
with their app. Apparently, AppArmor is preventing it from starting. I'm
not familiar with this MAC implementation, but the logs suggest that
this is the problem. See the attachment.

```
nov 07 11:18:29 alq22 audit[27542]: AVC apparmor="DENIED" operation="open" 
profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" 
pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
nov 07 11:18:29 alq22 kernel: audit: type=1400 audit(1573136309.796:304): 
apparmor="DENIED" operation="open" 
profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" 
pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
```

This is a fresh installation of Ubuntu 18.04.3. I take great care not to
mess with system components such as snapd. Other snaps are working
properly.

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

** Attachment added: "Journalctl output - see last lines"
   
https://bugs.launchpad.net/bugs/1851661/+attachment/5303495/+files/journalctl.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1851661

Title:
  AppArmor denied operation open to snap pick-colour-picker

Status in apparmor package in Ubuntu:
  New

Bug description:
  I've written an issue here:
  https://github.com/stuartlangridge/ColourPicker/issues/63

  Pick (a color picker distributed as a snap) will not launch. The
  creator of the application believes this to be a problem with my
  system, not with their app. Apparently, AppArmor is preventing it from
  starting. I'm not familiar with this MAC implementation, but the logs
  suggest that this is the problem. See the attachment.

  ```
  nov 07 11:18:29 alq22 audit[27542]: AVC apparmor="DENIED" operation="open" 
profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" 
pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  nov 07 11:18:29 alq22 kernel: audit: type=1400 audit(1573136309.796:304): 
apparmor="DENIED" operation="open" 
profile="snap.pick-colour-picker.pick-colour-picker" name="/proc/27542/mounts" 
pid=27542 comm="python3" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  ```

  This is a fresh installation of Ubuntu 18.04.3. I take great care not
  to mess with system components such as snapd. Other snaps are working
  properly.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1849324] [NEW] Xorg logs spammed with failed page flip messages

[Douglas Silva]

Public bug reported:

Please read this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1645553

I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
messages are still being spammed into my Xorg logs.

```
[  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable
[  6794.424] (EE) AMDGPU(0): present flip failed
[  6794.457] Failed to get FB for flip
```

A potential fix has already been merged here:
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193

Fedora users already have it. I haven't tested Fedora to see if that
fixes my problem.

If that fix is already in Ubuntu, I believe we're talking about a new
bug.

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

** Attachment added: "The Xorg log file, currently 15 MB large"
   https://bugs.launchpad.net/bugs/1849324/+attachment/5299212/+files/Xorg.0.log

** Description changed:

- This bug has already been discussed here:
+ Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553
  
  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.
  
  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```
  
  A fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193
  
  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.
  
  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

** Description changed:

  Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553
  
  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.
  
  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```
  
- A fix has already been merged here:
+ A potential fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193
  
  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.
  
  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1849324

Title:
  Xorg logs spammed with failed page flip messages

Status in xorg package in Ubuntu:
  New

Bug description:
  Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553

  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.

  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```

  A potential fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193

  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.

  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1848616] [NEW] LightDM crashes and logs me out when resuming from suspend

[Douglas Silva]

Public bug reported:

I close the laptop lid and let it suspend. On resume, the whole desktop
is frozen for a while. Nothing works during this time, no CAPS LOCK
indicator LED, neither TTY switching. Then the screen goes dark and I
see the LightDM login screen. I was logged out.

This is a regression, since it wasn't reproducible on Ubuntu 19.04.

How reproducible?
100% of the time.

I am not totally sure it was LightDM's fault. It is my best guess based
on the behavior I witnessed.

See logs.

Potentially relevant specs:
- Intel HD Graphics 400 (Braswell)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: lightdm 1.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 17 21:52:19 2019
InstallationDate: Installed on 2019-10-17 (0 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Journalctl output from right after the problem"
   
https://bugs.launchpad.net/bugs/1848616/+attachment/5298012/+files/journalctl.txt

** Description changed:

  I close the laptop lid and let it suspend. On resume, the whole desktop
  is frozen for a while. Nothing works during this time, no CAPS LOCK
  indicator LED, neither TTY switching. Then the screen goes dark and I
  see the LightDM login screen. I was logged out.
  
  This is a regression, since it wasn't reproducible on Ubuntu 19.04.
+ 
+ How reproducible?
+ 100% of the time.
  
  I am not totally sure it was LightDM's fault. It is my best guess based
  on the behavior I witnessed.
  
  See logs.
  
  Potentially relevant specs:
  - Intel HD Graphics 400 (Braswell)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 21:52:19 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1848616

Title:
  LightDM crashes and logs me out when resuming from suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  I close the laptop lid and let it suspend. On resume, the whole
  desktop is frozen for a while. Nothing works during this time, no CAPS
  LOCK indicator LED, neither TTY switching. Then the screen goes dark
  and I see the LightDM login screen. I was logged out.

  This is a regression, since it wasn't reproducible on Ubuntu 19.04.

  How reproducible?
  100% of the time.

  I am not totally sure it was LightDM's fault. It is my best guess
  based on the behavior I witnessed.

  See logs.

  Potentially relevant specs:
  - Intel HD Graphics 400 (Braswell)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 17 21:52:19 2019
  InstallationDate: Installed on 2019-10-17 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

** Description changed:

- On 16.04 (XFCE session and others) and possibly later the power-manager
- is unable to suspend the system when the user is inactive. A PK user-
- agent dialog is presented for the user to authenticate first - and as
- this action occurs specifically when the user is idle and away the PC
- can end up having an unplanned loss of power when the battery is
- exhausted.
+ On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is
+ unable to suspend the system when the user is inactive. A PK user-agent
+ dialog is presented for the user to authenticate first - and as this
+ action occurs specifically when the user is idle and away the PC can end
+ up having an unplanned loss of power when the battery is exhausted.
  
  /var/log/auth.log shows:
  
  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-f7631ecd0b46]
  (owned by unix-user:tj)
  
  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to
  allow Suspend. Currently it only has an entry for hibernate.
  
  Adding the following stanza solves the issue:
  
  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is
  unable to suspend the system when the user is inactive. A PK user-
  agent dialog is presented for the user to authenticate first - and as
  this action occurs specifically when the user is idle and away the PC
  can end up having an unplanned loss of power when the battery is
  exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

I can also reproduce this on both of my computers running Xubuntu 19.04,
a desktop and a laptop.

Just to be extra clear on what the issue is:

If the computer is left idle for 10 minutes, the screen locks. When 15
minutes have passed, it should suspend, but it never does. I unlock the
screen to investigate why, and find that there is a prompt window asking
my password in order to allow the system to suspend.

What usually happens as a consequence:

I fall asleep with the laptop still running, and on the next day the
thing is powered off with only 1% of battery power. It stayed ON all
night.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

Thanks for the response. Sorry for the delay, I didn't get a
notification about this.

If by admin you mean one that has sudo privileges or a member of group
`adm`, then yes. It's the default user created by the installer.

I could reproduce this on Arch Linux and other distros IIRC. The
workaround works on them too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1839900] [NEW] Power button action not working

[Douglas Silva]

Public bug reported:

I've configured it so that the system would suspend after pressing the
power button. This does not happen.

How is it reproducible?
It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new 
kernel, new bug. On Ubuntu 19.04, this has been reproducible since its release. 
This is also reproducible on other distributions with the GNOME desktop.

This is exclusive to the GNOME desktop. No other desktop I've tried has
issues with the power button action.

Ubuntu 18.04.3
Kernel 5.0.0-23-generic
GNOME 3.28.2

See attached logs. Near the end of it I attempted to make the system
suspend by repeatedly pressing the power button, as configured in GNOME
Settings > Power > When the power button is pressed.

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "journalctl output"
   
https://bugs.launchpad.net/bugs/1839900/+attachment/5282269/+files/journalctl.txt

** Package changed: systemd (Ubuntu) => gnome-settings-daemon (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1839900

Title:
  Power button action not working

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I've configured it so that the system would suspend after pressing the
  power button. This does not happen.

  How is it reproducible?
  It started after updating from Ubuntu 18.04.2 to 18.04.3. New packages, new 
kernel, new bug. On Ubuntu 19.04, this has been reproducible since its release. 
This is also reproducible on other distributions with the GNOME desktop.

  This is exclusive to the GNOME desktop. No other desktop I've tried
  has issues with the power button action.

  Ubuntu 18.04.3
  Kernel 5.0.0-23-generic
  GNOME 3.28.2

  See attached logs. Near the end of it I attempted to make the system
  suspend by repeatedly pressing the power button, as configured in
  GNOME Settings > Power > When the power button is pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1839900/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1836881] [NEW] Xorg freeze

[Douglas Rodrigues Alves]

Public bug reported:

My gnome session freezes, mouse works fine but cannot start
applications. I am able to enter one of the tty terminals and kill the
session. This happens a few times a day and started a week ago probably.

Douglas

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 17 12:29:38 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.15.0-52-generic, x86_64: installed
 nvidia, 418.56, 4.15.0-54-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1208]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] 
[1025:1207]
InstallationDate: Installed on 2018-01-13 (550 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
 Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Predator PH317-51
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Sienna_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
dmi.product.family: Predator Helios 300
dmi.product.name: Predator PH317-51
dmi.product.version: V1.05
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1836881

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  My gnome session freezes, mouse works fine but cannot start
  applications. I am able to enter one of the tty terminals and kill the
  session. This happens a few times a day and started a week ago
  probably.

  Douglas

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 17 12:29:38 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 4.15.0-52-generic, x86_64: installed
   nvidia, 418.56, 4.15.0-54-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1208]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] 
[1025:1207]
  InstallationDate: Installed on 2018-01-13 (55

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

The solution is right here, so simple to apply. Why is this ignored? No
one else suspends their machines? Merge the necessary polkit rule,
please.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1825785] [NEW] lightdm: screen does not wake up on mouse/keyboard events

[Douglas Silva]

Public bug reported:

Description: When session is locked either using dm-tool or light-
locker, lightdm greeter is functional (you can type your password and
press Enter to unlock the session) but screen is not turned on, and
remains turned off even when you move the mouse or press any key.

Although, it doesn't occur when you close your session instead locking
it.

Additional info:
* xorg: 1:7.7+19ubuntu12
* lightdm 1.28.0-0ubuntu1
* xfce4-session: 4.12.1-6ubuntu1

>From lsb_release:
Description:Ubuntu 19.04
Release:19.04

* Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
* Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

Steps to reproduce:
* Lock the running session using lightdm
* Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
* You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

Note: switching out and then switching back to tty7 restores visibility
of the lock screen.

On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
screen behave as expected.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Apr 22 02:06:42 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
InstallationDate: Installed on 2019-04-22 (0 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
 Bus 001 Device 002: ID 8087:07dc Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 11-3162
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0NM68T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.sku: 0725
dmi.product.version: 2.4.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

** Description changed:

  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.
  
  Although, it doesn't occur when you close your session instead locking
  it.
  
  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1
  
  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04
  
- * Reproducible on other distributions as well.
+ * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.
  
  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.
  
  Note: switching out and then switching back to tty7 restores visibility
  of the lock 

[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas Silva]

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

** This bug has been marked a duplicate of bug 1795135
   XFCE window buttons are not clickable at the top of the screen

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1690671

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity
  are not affected. Any DE still using gtk2 works fine. I tested 3
  different computers with Intel Graphics and they were all displaying
  the same glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

No change in Disco. Still missing the entry at
"com.ubuntu.desktop.pkla".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Douglas Silva]

Your workaround worked for me too. I'm running Xubuntu 18.04. Now I can
suspend the machine.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1757375

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1823503] [NEW] systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04

[Douglas Moyes]

Public bug reported:

dns-nameservers entry in /etc/network/interfaces is ignored by systemd-
resolved-- all of the other settings work, which adds quite a bit of
confusion and frustration since Ubuntu recently switched to using
netplan.


It would be a **VERY** good idea to add a comment at the top of 
/etc/network/interfaces that this file is now deprecated, and provide 
information about the new netplan utility. Something similar was done to 
/etc/resolv.conf years back.

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

** Package changed: guessnet (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1823503

Title:
  systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  dns-nameservers entry in /etc/network/interfaces is ignored by
  systemd-resolved-- all of the other settings work, which adds quite a
  bit of confusion and frustration since Ubuntu recently switched to
  using netplan.

  
  It would be a **VERY** good idea to add a comment at the top of 
/etc/network/interfaces that this file is now deprecated, and provide 
information about the new netplan utility. Something similar was done to 
/etc/resolv.conf years back.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1823217] [NEW] Portrait display cuts off below primary monitor

[Douglas Hitchcock]

Public bug reported:

Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

Two monitors, place one Portrait right.  Any part of that screen that
extends below the primary monitor is cut off.  The mouse cursor will go
in there, but any window you drag in there disappears.  If you take a
screen shot, the screenshot tool thinks that area does not exist.
Screenshots attached.

I've used this same monitor layout for years, this issue did not exist
in Cosmic.  I was able to reproduce it in a clean install in Virtualbox,
so it's not limited to my hardware or any extensions/apps I'm using.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 14:02:45 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
 virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 
08) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller 
[1558:7410]
InstallationDate: Installed on 2019-03-26 (8 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
MachineType: System76, Inc. Galago UltraPro
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=6429a565-4509-46ef-9be8-1558a2b094e4 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Galago UltraPro
dmi.board.vendor: System76, Inc.
dmi.board.version: galu1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: System76, Inc,
dmi.chassis.version: galu1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
dmi.product.family: Not Applicable
dmi.product.name: Galago UltraPro
dmi.product.sku: Not Applicable
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

** Attachment added: "Picture of screen, since screenshot doesn't capture the 
blackness"
   
https://bugs.launchpad.net/bugs/1823217/+attachment/5252896/+files/IMG_20190404_121441.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1823217

Title:
  Portrait display cuts off below primary monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Using beta of Disco Dingo, so gnome-shell 3.32.0-1ubuntu1.

  Two monitors, place one Portrait right.  Any part of that screen that
  extends below the primary monitor is cut off.  The mouse cursor will
  go in there, but any window you drag in there disappears.  If you take
  a screen shot, the screenshot tool thinks that area does not exist.
  Screenshots attached.

  I've used this same monitor layout for years, this issue did not exist
  in Cosmic.  I was able to reproduce it in a clean install in
  Virtualbox, so it's not limited to my hardware or any extensions/apps
  I'm using.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 14:02:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.4, 5.0.0-7-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics 

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Douglas Kosovic]

Comment 6 and 7 in the upstream GNOME NetworkManager-pptp bug report :
https://bugzilla.gnome.org/show_bug.cgi?id=785771#c6
are relevant to this bug (but not the 'cp -a' issue).

As mentioned, the following exit in /etc/ppp/ip-up.d/000resolvconf when
the interface is managed by NM, seems the right solution.

case "$6" in
  nm-pptp-service-*|nm-l2tp-service-*|/org/freedesktop/NetworkManager/PPP/*)
# NetworkManager handles it
exit 0
;;
esac

Perhaps the exit should be added to /etc/ppp/ip-up.d/usepeerdns for
instances when resolvconf package isn't installed?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Douglas Kosovic]

I wasn't able to redirect the stderr from the following line in /etc/ppp
/ip-up.d/usepeerdns (probably because of something pppd is doing) :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

So I modified the cp.c source from the coreutils package and redirected
stderr to a file.

The error message I now see is :


cp: failed to preserve ownership for 
'/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0': Operation not 
permitted


cp.c is using the lchown() function which is failing with that message.

Looks like only preserving ownership is failing as I tried the following
and it works:

cp --preserve=mode,timestamps "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-
backup.$PPP_IFACE"

The way /run is mounted might be the reason why 'cp -a' and lchown() is failing.
 

Ignore what I said able $? being 0 after the cp -a line. Doing the
following line confirms $? is 1 :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" || echo
ERROR $? >> /tmp/usepeerdns-up.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Douglas Kosovic]

Sorry ignore comment #16 as the following line in /etc/ppp/ip-
up.d/usepeerdns will exit because of the '#!/bin/sh -e' shebang
line:

cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"


So my original suggestion of replacing the following line:

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

was correct and won't prematurely exit.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Douglas Kosovic]

I can confirm the issue is the following line in /etc/ppp/ip-
up.d/usepeerdns as previously mentioned :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

The variable expansion of that line is :
cp -a /run/systemd/resolve/stub-resolv.conf 
/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0

I had to modify the shebang line of that script from :
  #!/bin/sh -e
to :
  #!/bin/sh
to get past that line and output debugging output I inserted, which included :

ls -l /run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 720 Jan 17 21:47 
/run/systemd/resolve/stub-resolv.conf

ls -l /run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0
-rw--- 1 root root 720 Jan 17 21:47 
/run/systemd/resolve/stub-resolv.conf.pppd-backup.ppp0

So 'cp -a' isn't copying the permissions. Oddly, $? is 0 after running
that 'cp -a' line, therefor seems correct, also umask is 0022, so I'm
not sure what is going wrong.


Anyway a fix seems to be to change the following line in 
/etc/ppp/ip-up.d/usepeerdns from :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"


For Ubuntu 18.04 setups that have the pppconfig package installed, the
following lines in /etc/ppp/ip-up.d/0dns-up probably should be changed
from :

/bin/cp -Lp "$RESOLVCONF" "$RESOLVBAK" || exit 1
/bin/cp -Lp "$TEMPRESOLV" "$RESOLVCONF" || exit 1
chmod 644 "$RESOLVCONF" || exit 1

to:

/bin/cp -Lp "$RESOLVCONF" "$RESOLVBAK" || exit 1
chmod 644 "$RESOLVBAK" || exit 1
/bin/cp -Lp "$TEMPRESOLV" "$RESOLVCONF" || exit 1
chmod 644 "$RESOLVCONF" || exit 1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Douglas Kosovic]

Correction the following line in /etc/ppp/ip-up.d/usepeerdns
probably should be changed from :

cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

to:

cp -Lp "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"
chmod 644 "$REALRESOLVCONF.pppd-backup.$PPP_IFACE"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1778946

Title:
  No dns resolution after closing a vpn/pptp connection

Status in network-manager package in Ubuntu:
  Confirmed
Status in ppp package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Douglas Hammond]

This issue also affected Linux Mint 19.2, and Brian's workaround and fix
in #36 work for that distribution as well.

I used the workaround steps to resume the broken boot, then followed the
fix steps and rebuilt the initramfs using:

# rebuild initramfs
/usr/sbin/update-initramfs.distrib -u 

then copied the resulting .img to my netboot server.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1755863

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1804317] [NEW] nVidia video problem

[Douglas Hart]

Public bug reported:

After upgrade from 16.04 to 18.04 I no longer have video on my monitor.
I can get video using NoMachine, however.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.57  Tue Sep 18 23:25:09 
CDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 20 14:17:01 2018
DistUpgraded: 2018-11-20 14:00:29,184 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 410.57, 4.15.0-39-generic, x86_64: installed
 nvidia, 410.57, 4.4.0-139-generic, x86_64: installed
 system76, 1.0.0~1540923431~18.04~33e9d57~dev, 4.15.0-39-generic, x86_64: 
installed
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:3975]
InstallationDate: Installed on 2016-04-11 (952 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
MachineType: System76, Inc. Wild Dog Pro
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=6994e1a0-8931-4a0b-be62-d7db3f360890 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-11-20 (0 days ago)
dmi.bios.date: 10/19/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H170-D3HP-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: wilp12
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd10/19/2015:svnSystem76,Inc.:pnWildDogPro:pvrwilp12:rvnGigabyteTechnologyCo.,Ltd.:rnH170-D3HP-CF:rvrx.x:cvnSystem76,Inc.:ct3:cvrwilp12:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Wild Dog Pro
dmi.product.version: wilp12
dmi.sys.vendor: System76, Inc.
nvidia-settings:
 ERROR: Error querying enabled displays on GPU 0 (Missing Extension).
 
 
 ERROR: Error querying connected displays on GPU 0 (Missing Extension).
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Nov 20 14:12:55 2018
xserver.configfile: default
xserver.errors:
 Error systemd-logind returned paused fd for drm node
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Error systemd-logind returned paused fd for drm node
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1804317

Title:
  nVidia video problem

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade from 16.04 to 18.04 I no longer have video on my
  monitor.  I can get video using NoMachine, however.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  

[Touch-packages] [Bug 1783928] Re: package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be

[Douglas Karoub]

Thank you for being there

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1783928

Title:
  package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in packagekit package in Ubuntu:
  New

Bug description:
  Reporting issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jul 26 20:37:33 2018
  DuplicateSignature:
   package:gir1.2-packagekitglib-1.0:0.8.17-4ubuntu6~gcc5.4ubuntu1.2
   Unpacking linux-headers-generic-hwe-16.04 (4.15.0.29.51) over (4.13.0.45.64) 
...
   dpkg: error processing package gir1.2-packagekitglib-1.0 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-29 (239 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: packagekit
  Title: package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1783928] [NEW] package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it

[Douglas Karoub]

Public bug reported:

Reporting issue

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Jul 26 20:37:33 2018
DuplicateSignature:
 package:gir1.2-packagekitglib-1.0:0.8.17-4ubuntu6~gcc5.4ubuntu1.2
 Unpacking linux-headers-generic-hwe-16.04 (4.15.0.29.51) over (4.13.0.45.64) 
...
 dpkg: error processing package gir1.2-packagekitglib-1.0 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-11-29 (239 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: packagekit
Title: package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1783928

Title:
  package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in packagekit package in Ubuntu:
  New

Bug description:
  Reporting issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jul 26 20:37:33 2018
  DuplicateSignature:
   package:gir1.2-packagekitglib-1.0:0.8.17-4ubuntu6~gcc5.4ubuntu1.2
   Unpacking linux-headers-generic-hwe-16.04 (4.15.0.29.51) over (4.13.0.45.64) 
...
   dpkg: error processing package gir1.2-packagekitglib-1.0 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-29 (239 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: packagekit
  Title: package gir1.2-packagekitglib-1.0 0.8.17-4ubuntu6~gcc5.4ubuntu1.2 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1783624] [NEW] Some programs do not work

[Douglas L. Turnbull]

Public bug reported:

Cannot access software through Ubuntu Software
VLC does not play DVD movies

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jul 26 04:07:02 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
InstallationDate: Installed on 2018-07-13 (12 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP-Pavilion VT563AA-ABG HPE-170a
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic 
root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro splash quiet plymouth:debug=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.07
dmi.board.name: IONA
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: VT563AA-ABG HPE-170a
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Jul 26 04:05:37 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 0b38:0010KEYBOARD, id 8
 inputHID 0b38:0010KEYBOARD, id 9
 inputHID 413c:3010MOUSE, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1783624

Title:
  Some programs do not work

Status in xorg package in Ubuntu:
  New

Bug description:
  Cannot access software through Ubuntu Software
  VLC does not play DVD movies

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 26 04:07:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2018-07-13 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP-Pavilion VT563AA-ABG HPE-170a
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic 
root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro splash quiet plymouth:debug=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1782972] [NEW] O/S not functioning correctly

[Douglas L. Turnbull]

Public bug reported:

O/S not functioning properly.
Ubuntu Software does not function correctly.
I prefer to use Graphics Interface please, not Terminal mode.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jul 22 18:16:39 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
InstallationDate: Installed on 2018-07-13 (8 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP-Pavilion VT563AA-ABG HPE-170a
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.07
dmi.board.name: IONA
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: VT563AA-ABG HPE-170a
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jul 22 18:10:55 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 0b38:0010KEYBOARD, id 8
 inputHID 0b38:0010KEYBOARD, id 9
 inputHID 413c:3010MOUSE, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1782972

Title:
  O/S not functioning correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  O/S not functioning properly.
  Ubuntu Software does not function correctly.
  I prefer to use Graphics Interface please, not Terminal mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 22 18:16:39 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2018-07-13 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP-Pavilion VT563AA-ABG HPE-170a
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1782972] Re: O/S not functioning correctly

[Douglas L. Turnbull]

My email address is:- turnbul...@gmx.com

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1782972

Title:
  O/S not functioning correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  O/S not functioning properly.
  Ubuntu Software does not function correctly.
  I prefer to use Graphics Interface please, not Terminal mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 22 18:16:39 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2018-07-13 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP-Pavilion VT563AA-ABG HPE-170a
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.07
  dmi.board.name: IONA
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: VT563AA-ABG HPE-170a
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jul 22 18:10:55 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 0b38:0010KEYBOARD, id 8
   inputHID 0b38:0010KEYBOARD, id 9
   inputHID 413c:3010MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1780415] Re: I replaced U/S system 500 GB HDD with 120GB SSD

[Douglas L. Turnbull]

My email address is:- turnbul...@gmx.com

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1780415

Title:
  I replaced U/S system 500 GB HDD with 120GB SSD

Status in xorg package in Ubuntu:
  New

Bug description:
  I then loaded my latest Ubuntu O/S 16.04.1, which I knew required updating.
  But when connected to internet and checked update status, the response is the
  O/S is up to date, but it is some two years old!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul  6 19:52:08 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2018-07-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP-Pavilion VT563AA-ABG HPE-170a
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=5ddb6a75-6511-492d-ada2-10da6ee2886f ro drm.debug=0xe 
vesafb.invalid=1 plymouth:debug=1=1 nopat plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.07
  dmi.board.name: IONA
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: VT563AA-ABG HPE-170a
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul  6 19:50:22 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 0b38:0010KEYBOARD, id 8
   inputHID 0b38:0010KEYBOARD, id 9
   inputHID 413c:3010MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1780415] [NEW] I replaced U/S system 500 GB HDD with 120GB SSD

[Douglas L. Turnbull]

Public bug reported:

I then loaded my latest Ubuntu O/S 16.04.1, which I knew required updating.
But when connected to internet and checked update status, the response is the
O/S is up to date, but it is some two years old!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jul  6 19:52:08 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
InstallationDate: Installed on 2018-07-04 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP-Pavilion VT563AA-ABG HPE-170a
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=5ddb6a75-6511-492d-ada2-10da6ee2886f ro drm.debug=0xe 
vesafb.invalid=1 plymouth:debug=1=1 nopat plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.07
dmi.board.name: IONA
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: VT563AA-ABG HPE-170a
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul  6 19:50:22 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 0b38:0010KEYBOARD, id 8
 inputHID 0b38:0010KEYBOARD, id 9
 inputHID 413c:3010MOUSE, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1780415

Title:
  I replaced U/S system 500 GB HDD with 120GB SSD

Status in xorg package in Ubuntu:
  New

Bug description:
  I then loaded my latest Ubuntu O/S 16.04.1, which I knew required updating.
  But when connected to internet and checked update status, the response is the
  O/S is up to date, but it is some two years old!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul  6 19:52:08 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
  InstallationDate: Installed on 2018-07-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP-Pavilion VT563AA-ABG HPE-170a
  ProcEnviron:
   LANGUAGE=en_AU:en
   

[Touch-packages] [Bug 677743]

[Douglas Greenstein]

http://wow.honeyrum.com

Doug Greenstein

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/677743

Title:
  [Realtek ALC662 rev1] Playback problem Rhythm box will not play. there
  is no sound. I may have erased some necessary sub programs while I was
  trying to get real player to work.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I'm a novice to computers and Linux. Have the latest version of Ubuntu
  which I down-loaded a few days ago. The Rhythm box player was working
  fine when I first used it. As I said I added some GStreamer components
  which than caused the Rhythm box not to work and then I undid them.
  The real player still doesn't work. I really didn't know what I was
  doing!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
  Uname: Linux 2.6.35-22-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1641 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,103c2a99,00100101'
 Controls  : 18
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbfec000 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Nov 19 23:25:32 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 NVidia HDA-Intel - HDA NVidia
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC662 rev1] Playback problem
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.15
  dmi.board.name: Narra6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 6.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.15:bd11/06/2009:svnHP-Pavilion:pnAY643AA-ABAs5310f:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: AY643AA-ABA s5310f
  dmi.sys.vendor: HP-Pavilion

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 677743]

[Douglas Greenstein]

http://favourite.neovolo.org
Doug Greenstein

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/677743

Title:
  [Realtek ALC662 rev1] Playback problem Rhythm box will not play. there
  is no sound. I may have erased some necessary sub programs while I was
  trying to get real player to work.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I'm a novice to computers and Linux. Have the latest version of Ubuntu
  which I down-loaded a few days ago. The Rhythm box player was working
  fine when I first used it. As I said I added some GStreamer components
  which than caused the Rhythm box not to work and then I undid them.
  The real player still doesn't work. I really didn't know what I was
  doing!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
  Uname: Linux 2.6.35-22-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  douglas1641 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,103c2a99,00100101'
 Controls  : 18
 Simple ctrls  : 11
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbfec000 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Fri Nov 19 23:25:32 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 NVidia HDA-Intel - HDA NVidia
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC662 rev1] Playback problem
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.15
  dmi.board.name: Narra6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 6.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.15:bd11/06/2009:svnHP-Pavilion:pnAY643AA-ABAs5310f:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: AY643AA-ABA s5310f
  dmi.sys.vendor: HP-Pavilion

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1751293] Re: libfreetype6 2.8.1 cause nasty font glitches in atom editor

[Douglas Gaskell]

This also effects other electron apps such as Discord. The fix for users
is to downgrade from freetype 2.8.1 to freetype 2.8.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to freetype in Ubuntu.
https://bugs.launchpad.net/bugs/1751293

Title:
  libfreetype6 2.8.1 cause nasty font glitches in atom editor

Status in freetype package in Ubuntu:
  Invalid

Bug description:
  Main bugreport: https://github.com/atom/atom/issues/15737

  Problem can be reproduced with 2.8.1-0.1ubuntu2, but it disappears on
  libfreetype6=2.8-0.2ubuntu2.1.

  I don't know about root cause, but may be holding back on 2.8-0 in
  bionic may be a great idea?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libfreetype6 2.8-0.2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Fri Feb 23 16:42:14 2018
  Dependencies:
   gcc-8-base 8-20180208-0ubuntu1
   libc6 2.26-0ubuntu2.1
   libgcc1 1:8-20180208-0ubuntu1
   libpng16-16 1.6.34-1
   zlib1g 1:1.2.11.dfsg-0ubuntu2
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-22 (246 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737524] [NEW] DVD R/W ODD is not being recognised by dvd decrypter

[Douglas L. Turnbull]

Public bug reported:

Have tried reloading dvd decrypter and wine, but did not cure problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Dec 11 20:55:33 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-101-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104M [GeForce GTX 880M] [10de:1198] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK104M [GeForce GTX 880M] [1028:05ae]
InstallationDate: Installed on 2017-08-20 (113 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Alienware Alienware 17
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=5d561490-ed57-4448-9388-c0aa28db7add ro 
plymouth:debug=1=1=1=1=1=1=1=1=1 vesafb.invalid=1 plymouth:debug 
plymouth:debug=1=1=1=1=1=1=1 nopat drm.debug=0xe plymouth:debug=1=1=1=1 
plymouth:debug=1=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2014
dmi.bios.vendor: Alienware
dmi.bios.version: A14
dmi.board.name: 04WT2G
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A14
dmi.modalias: 
dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA14:
dmi.product.name: Alienware 17
dmi.product.version: A14
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1737524

Title:
  DVD R/W ODD is not being recognised by dvd decrypter

Status in xorg package in Ubuntu:
  New

Bug description:
  Have tried reloading dvd decrypter and wine, but did not cure problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec 11 20:55:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-101-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104M [GeForce GTX 880M] [10de:1198] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GK104M [GeForce GTX 880M] [1028:05ae]
  InstallationDate: Installed on 2017-08-20 (113 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 17
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=5d561490-ed57-4448-9388-c0aa28db7add ro 
plymouth:debug=1=1=1=1=1=1=1=1=1 vesafb.invalid=1 plymouth:debug 
plymouth:debug=1=1=1=1=1=1=1 nopat drm.debug=0xe plymouth:debug=1=1=1=1 
plymouth:debug=1=1
  SourcePackage: xorg
  UpgradeStatus: 

[Touch-packages] [Bug 1692066] Re: [Request] Libreswan plugin for Network Manager

[Douglas Kosovic]

I suggest you file a Debian Request for Package (RFP) for 
network-manager-libreswan :
   https://wiki.debian.org/RFP

Once the package is in Debian Sid, it will automatically make its way to
Ubuntu.

Or if you are able to provide a package, an Intent to Package (ITP) :
   https://wiki.debian.org/ITP

libreswan was added to Debian Sid earlier in the year and it made its
way to Ubuntu 17.04.

Upstream in the GNOME Projects network-manager-libreswan GIT repository in the 
NEWS file, you'll notice network-manager-libreswan was renamed from 
network-manager-openswan at version 1.2
  https://git.gnome.org/browse/network-manager-libreswan/tree/

Debian/Ubuntu used to include network-manager-openswan, so that package
might be a good starting point for updating to network-manager-
libreswan.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1692066

Title:
  [Request] Libreswan plugin for Network Manager

Status in libreswan package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello!

  I have the need to use Libreswan instead of strongswan to connect to
  an IPSec IKEv1 XAuth VPN in main mode without a group. Thing is
  strongswan doesn't support this configuration, so I explicitally need
  it. Nonetheless, libreswan is as developed as strongswan and it's
  widely used.

  using config files in /etc (ipsec.conf and .secrets) it's possible to
  correctly configure ipsec/libreswan, but needlessly to say, having the
  possibility to manage it via a GUI is 100 times better (and easier for
  "normal" users).

  In the current repositories (Zesty) I only found the libreswan's ipsec
  binaries (package libreswan), but not the network manager plugin
  (sources are available on github).

  I've tried to compile them, but I'm afraid they use a different path
  pattern than Ubuntu, so without making changes it's not possible to
  succesfully install it from sources.

  Thanks

  LibreSwan NetworkManager plugin sources:
  https://github.com/NetworkManager/network-manager-libreswan

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1718863] [NEW] VLC malfunction

[Douglas L. Turnbull]

Public bug reported:

VLC will no longer function.
When attempting to play a DVD movie, the screen goes white with black speckled 
effect.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Sep 22 17:23:34 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104M [GeForce GTX 880M] [10de:1198] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK104M [GeForce GTX 880M] [1028:05ae]
InstallationDate: Installed on 2017-08-20 (33 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Alienware Alienware 17
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=5d561490-ed57-4448-9388-c0aa28db7add ro drm.debug=0xe plymouth:debug 
vesafb.invalid=1 nopat
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2014
dmi.bios.vendor: Alienware
dmi.bios.version: A14
dmi.board.name: 04WT2G
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A14
dmi.modalias: 
dmi:bvnAlienware:bvrA14:bd09/24/2014:svnAlienware:pnAlienware17:pvrA14:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA14:
dmi.product.name: Alienware 17
dmi.product.version: A14
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1718863

Title:
  VLC malfunction

Status in xorg package in Ubuntu:
  New

Bug description:
  VLC will no longer function.
  When attempting to play a DVD movie, the screen goes white with black 
speckled effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep 22 17:23:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-92-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-96-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104M [GeForce GTX 880M] [10de:1198] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GK104M [GeForce GTX 880M] [1028:05ae]
  InstallationDate: Installed on 2017-08-20 (33 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 17
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=5d561490-ed57-4448-9388-c0aa28db7add ro drm.debug=0xe plymouth:debug 
vesafb.invalid=1 nopat
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A14
  dmi.board.name: 04WT2G
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  

[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Douglas H. Silva]

Unable to reproduce this in Ubuntu MATE 17.04. I use full-disk
encryption too and enabled auto-login as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in ubuntu-mate:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1712510] [NEW] Slow bootup

[Douglas L. Turnbull]

Public bug reported:

Could be a grub problem

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Aug 23 18:51:55 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:0708]
   Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
InstallationDate: Installed on 2017-08-16 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 187c:0528 Alienware Corporation 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Alienware Alienware 15 R2
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=8e3659b0-7baf-41fc-af8b-0f93a2fac71a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2015
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.5
dmi.board.name: Alienware 15 R2
dmi.board.vendor: Alienware
dmi.board.version: X01
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 15 R2
dmi.product.version: 1.1.5
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Aug 23 18:49:52 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV124
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19528 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1712510

Title:
  Slow bootup

Status in xorg package in Ubuntu:
  New

Bug description:
  Could be a grub problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 23 18:51:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-08-16 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 

[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas H. Silva]

** Description changed:

  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
  
  This affects any desktop environment made with gtk+3, such as MATE,
- Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
- affected. Any DE still using gtk2 works fine. I tested 3 different
+ Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity are
+ not affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1690671

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity
  are not affected. Any DE still using gtk2 works fine. I tested 3
  different computers with Intel Graphics and they were all displaying
  the same glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Douglas H. Silva]

Using ath9k driver: no issues

My netbook running iwlwifi driver still has this bug. It's in Ubuntu,
because I'm running Debian Stretch just fine there.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

[Douglas Kosovic]

network-manager-l2tp 1.2.6-2 was accepted into Debian sid :

   https://tracker.debian.org/pkg/network-manager-l2tp

The Debian package was automatically added to Ubuntu artful (17.10).

I've requested an Ubuntu backport of network-manager-l2tp from artful to
xenial (16.04) which includes intermediate zesty (17.04) and yakkety
(16:10) releases :

   https://bugs.launchpad.net/xenial-backports/+bug/1697934

Please vote for the backport by clicking the "this bug affects me" link
in the backport request.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/264691

Title:
  Please add NM option for connecting to L2TP IPSEC VPN

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Invalid

Bug description:
  Binary package hint: network-manager

  Missing feature:

  You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network
  Manager.

  The server I want to connect to expects a login / password and a PSK.

  When you do a connection in XP you can see the following details on a
  connection:

  Device name: L2TP
  Server type: PPP
  Authentication: MS CHAP v2
  IPSEC Encryption: IPSEC ESP 3DES
  Compression: MPPC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1697223] Re: Nil

[Douglas L. Turnbull]

If a bug is found, can it be remedied?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1697223

Title:
  Nil

Status in xorg package in Ubuntu:
  New

Bug description:
  Suspect virus in external hard drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun 11 08:52:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-02-18 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.5
  dmi.board.name: Alienware 15 R2
  dmi.board.vendor: Alienware
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.1.5
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jun 11 08:51:22 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV124
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19528 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1697223] [NEW] Nil

[Douglas L. Turnbull]

Public bug reported:

Suspect virus in external hard drives.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jun 11 08:52:58 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:0708]
   Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
InstallationDate: Installed on 2017-02-18 (112 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Alienware Alienware 15 R2
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2015
dmi.bios.vendor: Alienware
dmi.bios.version: 1.1.5
dmi.board.name: Alienware 15 R2
dmi.board.vendor: Alienware
dmi.board.version: X01
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 15 R2
dmi.product.version: 1.1.5
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jun 11 08:51:22 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 Unknown chipset: NV124
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   19528 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1697223

Title:
  Nil

Status in xorg package in Ubuntu:
  New

Bug description:
  Suspect virus in external hard drives.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jun 11 08:52:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-02-18 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=b4c1ed82-d9b3-438b-8f25-73a383ef28a5 ro plymouth:debug=1=1=1=1 
plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas H. Silva]

** Description changed:

+ THE ISSUE:
+ The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
+ 
  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
- THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
- 
  It can always be reproduced. I can record a video of the issue if
  needed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1690671

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1692273] [NEW] bug notification

[Douglas Robson]

Public bug reported:

This was found when I ran a diagnostic.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat May 20 19:15:24 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694]
InstallationDate: Installed on 2017-04-13 (37 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=ce8e6a6f-8c36-4bf0-b23c-1a1e71deefcf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2003
dmi.board.asset.tag: Default string
dmi.board.name: H110M-A/M.2
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat May 20 09:42:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9412 
 vendor ACI
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1692273

Title:
  bug notification

Status in xorg package in Ubuntu:
  New

Bug description:
  This was found when I ran a diagnostic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat May 20 19:15:24 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:8694]
  InstallationDate: Installed on 2017-04-13 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=ce8e6a6f-8c36-4bf0-b23c-1a1e71deefcf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  

[Touch-packages] [Bug 1690671] [NEW] Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas H. Silva]

Public bug reported:

This affects any desktop environment made with gtk+3, such as MATE,
Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
affected. Any DE still using gtk2 works fine. I tested 3 different
computers with Intel Graphics and they were all displaying the same
glitch.

THE ISSUE:
The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

It can always be reproduced. I can record a video of the issue if
needed.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested with 3 different
- computers and they were all displaying the same glitch.
+ computers with Intel Graphics and they were all displaying the same
+ glitch.
  
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
- affected. Any DE still using gtk2 works fine. I tested with 3 different
+ affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Summary changed:

- Pointer clicks and hovering fail to have effect at the very left and top 
edges of screen
+ Pointer clicks and hovering fail to have effect at the very left and top 
borders of screen

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
+ The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below (away from border) restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or 

[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)

[Douglas H. Silva]

I fixed it with `sudo systemctl enable bluetooth` followed by a reboot.
It will print something to the terminal when you enable. Something else
must have disabled bluetooth.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1607390

Title:
  serious bug on bluetooth (Ubuntu 16.04 LTS)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed ubuntu 16.04 LTS twice -and i discovered that
  the problem was from the tool katoolin so i didn't install it- after i
  installed ubuntu the bluetooth didn't work for me.

  P.S:the bluetooth was working when my laptop was ubuntu 15.04

  when i turn bluetooth on to connect my mouse the switch was on but it
  said that

  Bluetooth is disabled

  i entered the command

  sudo rfkill unblock bluetooth

  it worked but didn't connect to the mouse even after the next restart
  i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock 
bluetooth before last line and restarting)

  and i've tried **sudo hciconfig hci0 reset** with output

  > Can't init device hci0: Connection timed out (110)

  my lsusb; rfkill list output:

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  0: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
   1: asus-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
   11: hci0: Bluetooth
    Soft blocked: no
   Hard blocked: no

  and output of **dmesg | grep -Ei 'ath3k|blue'**

  [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   34.157120] Bluetooth: Core ver 2.21
  [   34.157135] Bluetooth: HCI device and connection manager initialized
  [   34.157138] Bluetooth: HCI socket layer initialized
  [   34.157140] Bluetooth: L2CAP socket layer initialized
  [   34.157145] Bluetooth: SCO socket layer initialized
  [   35.604410] usbcore: registered new interface driver ath3k
  [   51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   53.810045] Bluetooth: hci0 command 0x0c25 tx timeout
  [   55.814079] Bluetooth: hci0 command 0x0c38 tx timeout
  [   57.818111] Bluetooth: hci0 command 0x0c39 tx timeout
  [   59.822149] Bluetooth: hci0 command 0x0c05 tx timeout
  [   66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   66.997552] Bluetooth: BNEP filters: protocol multicast
  [   66.997556] Bluetooth: BNEP socket layer initialized
  [  195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  195.328480] Bluetooth: RFCOMM TTY layer initialized
  [  195.328488] Bluetooth: RFCOMM socket layer initialized
  [  195.328495] Bluetooth: RFCOMM ver 1.11
  [  199.131870] Bluetooth: hci0 command 0x1009 tx timeout
  [  276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  294.258992] Bluetooth: hci0 command 0x1005 tx timeout
  [  296.263065] Bluetooth: hci0 command 0x0c23 tx timeout
  [  298.267076] Bluetooth: hci0 command 0x0c14 tx timeout
  [  306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  346.417970] Bluetooth: hci0 command 0x0c56 tx timeout
  [  348.421916] Bluetooth: hci0 command 0x0c45 tx timeout
  [  350.425782] Bluetooth: hci0 command 0x0c58 tx timeout
  [  352.429744] Bluetooth: hci0 command 0x1004 tx timeout
  [  366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  368.145218] Bluetooth: hci0 command 0x1001 tx timeout
  [  370.149130] Bluetooth: hci0 command 0x1009 tx timeout
  [  410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  421.612041] Bluetooth: hci0 command 0x0c23 tx timeout
  [  423.616060] Bluetooth: hci0 command 0x0c14 tx timeout
  [  425.620018] Bluetooth: hci0 command 0x0c25 tx timeout
  [  427.623984] Bluetooth: hci0 command 0x0c38 tx timeout
  [  442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  444.727752] Bluetooth: hci0 command 0x0c52 tx timeout
  [  446.731800] Bluetooth: hci0 command 0x0c45 tx timeout
  [  448.735743] Bluetooth: hci0 command 0x0c58 tx timeout
  [  450.739762] Bluetooth: hci0 command 0x1004 tx timeout
  [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller
  [ 4011.801141] 

[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

[Douglas Kosovic]

There is now a new PPA, network-manager-l2tp 1.2.4 for 17.04 (zesty), 16.10 
(yakkety) and 16.04 (xenial) packages can be found here:
https://launchpad.net/~nm-l2tp/+archive/ubuntu/network-manager-l2tp

strongswan stable release updates for yakkety and xenial which fix the
aforementioned AppArmor name space issue were released in the last
couple of weeks. So I've decided to release PPA packages as Debian
strongswan doesn't have the fix yet. The network-manager-l2tp 1.2.4 PPA
packages on yakkety and xenial have explicit dependencies for the
versions of the strongswan packages with the fix.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/264691

Title:
  Please add NM option for connecting to L2TP IPSEC VPN

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Invalid

Bug description:
  Binary package hint: network-manager

  Missing feature:

  You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network
  Manager.

  The server I want to connect to expects a login / password and a PSK.

  When you do a connection in XP you can see the following details on a
  connection:

  Device name: L2TP
  Server type: PPP
  Authentication: MS CHAP v2
  IPSEC Encryption: IPSEC ESP 3DES
  Compression: MPPC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Douglas H. Silva]

The applet started functioning properly after 16.04.2. If the problem
was Intel drivers, it solved it. Intel Wireless 3160 + Ubuntu MATE with
kernel 4.8.0-39-generic. Confirm this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Douglas H. Silva]

Any change after 16.04.2? New kernel 4.8...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1641867] [NEW] GtkMenu: Submenu navigation triangle doesn't work

[Sam Douglas]

Public bug reported:

The navigation triangle code for keeping a submenu open when the mouse
is moving diagonally toward it is broken due to incorrect rounding.

This was reported upstream at:
https://bugzilla.gnome.org/show_bug.cgi?id=710388

The attached patch (also submitted upstream) rounds the cursor location
when calculating the navigation triangle bounds.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Fix for navigation triangle bug"
   
https://bugs.launchpad.net/bugs/1641867/+attachment/4777560/+files/submenu_navigation_region_fix.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1641867

Title:
  GtkMenu: Submenu navigation triangle doesn't work

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The navigation triangle code for keeping a submenu open when the mouse
  is moving diagonally toward it is broken due to incorrect rounding.

  This was reported upstream at:
  https://bugzilla.gnome.org/show_bug.cgi?id=710388

  The attached patch (also submitted upstream) rounds the cursor
  location when calculating the navigation triangle bounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1641867/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Henry J. Douglas]

I'm running Ubuntu 14.04.5 for now. It's unaffected by this. The .5
release added the support I needed. None of the workarounds for 16.04
worked in this hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Henry J. Douglas]

The arrows are not gone. I just made a clean install and update.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1579319] Re: Text missing in GTK+ applications after suspend

[Henry J. Douglas]

I thought disabling Slight Hinting would solve it permanently, but then
I had to change the "SubPixel thing" to something else for it to stop
corrupting characters after screen lock/suspend. Then it happened again
anyway! I'm out of workarounds and I got tired of Ubuntu's bugs. Not
installed right now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1579319

Title:
  Text missing in GTK+ applications after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Occasionally when resuming from suspend, text is randomly missing in
  GTK+ applications. Chrome and QT apps are unaffected. In my case it
  doesn't occur very frequently, perhaps once a week at most. I
  typically suspend my system every day and only reboot once or twice a
  month.

  It's not clear what is causing the problem. Based on the symptoms and
  similar bug reports, it seems most likely a problem with xorg and/or
  xserver-xorg-video-intel. It appears to be a new bug with 16.04 as I
  never experienced this in 15.10.

  I've noticed that the amount of missing text seems to vary depending
  on the font and font size. Some fonts/sizes seem to be okay, while
  with others there is no text on screen at all.

  Font rendering settings also appear have an effect. The problem is
  only visible with slight hinting and RGB sub pixel order. Disabling
  anti-aliasing or changing either the hinting or sub pixel order to
  anything else immediately renders all characters normally.

  Switching to a virtual terminal and back again fixes the problem
  (Ctrl+Alt+F1 then Ctrl+Alt+F7), as does restarting Xorg or logging
  out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat May  7 12:39:24 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:013c]
  InstallationDate: Installed on 2016-04-23 (13 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Extensa 5230
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=ba619ff4-ea0b-4b58-aa61-e79a3e7e7c1b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.28
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5230
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 02:12:16 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15105 
   vendor LPL
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system

[Henry J. Douglas]

There's also a message in the upper corner saying, "Power Manager:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Method call timed out."

Using Xubuntu 16.04

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1605189

Title:
  Authentication is required for suspending the system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspend from the xfce power manager does not work, as a
  window opens and asks for my password. Well, if it wants to suspend
  the system after a given timeout, I cannot enter my password as I'm
  not in front of my system then. Once I'm able to enter my password it
  is too late to run the suspend action.

  The window asking for my password prints:

  Password: 

  Details

  Action: org.freedesktop.login1.suspend
  Vendor: The systemd project

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 13:13:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-17 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4236ML1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236ML1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236ML1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Douglas Santos]

Aravind, are you using Gutenprint + CUPS ? Didn't you try the official
Epson drivers? Your printer uses  the same driver I use here "201207w"
for the printer and the "iscan 1.0.1" for the scanner.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

Aravind Gopal, I think you should try a fresh install. I have a Epson
L355 working fine and Google Earth x64 working with a small issue
(sometimes it closes right after launching, but on the 2nd time it
works...).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

Before epson's driver installation I had to install the LSB package (32
packages/dependencies), and that worked perfectly. I've also installed
Google Earth x64 with minor issues, but its ok. The scanner worked even
when this Bug wasn't fixed!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN

[Douglas Kosovic]

I've posted a summary of current NetworkManager-l2tp known issues and 
workarounds for Ubuntu and Debian here :
  https://github.com/nm-l2tp/network-manager-l2tp/issues/12

I haven't created a new network-manager-l2tp PPA because because of the
strongSwan AppArmor name space issue involving NetworkManager and also
some Ubuntu 16.04 users have had an issues with the system xl2tpd, but
not with a locally built copy. Unfortunately I haven't been able to
reproduce the xl2tpd issue since I changed computers a couple of months
ago.

I hope to submit a network-manager-l2tp package to Debian once the
strongSwan AppArmor issue has been resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/264691

Title:
  Please add NM option for connecting to L2TP IPSEC VPN

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Invalid

Bug description:
  Binary package hint: network-manager

  Missing feature:

  You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network
  Manager.

  The server I want to connect to expects a login / password and a PSK.

  When you do a connection in XP you can see the following details on a
  connection:

  Device name: L2TP
  Server type: PPP
  Authentication: MS CHAP v2
  IPSEC Encryption: IPSEC ESP 3DES
  Compression: MPPC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

I was using LSB from Trusty's repo, and right now I've received the
update for this packages:   libappstream-glib8 lsb lsb-base lsb-core
lsb-invalid-mta lsb-printing lsb-release lsb-security

Also this packages was deleted with "autoremove":   libpod-plainer-perl
libqt4-opengl libqt4-svg lsb-cxx lsb-desktop  lsb-graphics lsb-languages
lsb-multimedia

The printer is still working perfectly. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Henry J. Douglas]

One more thing I forgot to mention. Ubuntu (Unity) works perfectly. Any
other official flavour or distribution launched before 2016 (as this is
a new laptop) will have this issue. I couldn't find what makes Ubuntu's
network-manager work as it should yet.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1380480

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1380480/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Henry J. Douglas]

Intel Wireless 3160 (iwlwifi driver), Ubuntu MATE 16.04 is still being
affected. The connection is reestablished but no wireless Access Points
are displayed (up/down arrow ethernet icon instead of wireless). It
seems that this same bug has been reported several times here and
upstream, with no relevant updates :(

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1380480

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1380480/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1592607] [NEW] package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: a tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, que é diferente de outras instânci

[Douglas da Silva]

Public bug reported:

the crash ocurred during packettracert62 installation

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Jun 14 21:33:39 2016
ErrorMessage: a tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, que 
é diferente de outras instâncias do pacote libqtcore4:i386
InstallationDate: Installed on 2016-06-13 (1 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: a 
tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, que é diferente de 
outras instâncias do pacote libqtcore4:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1592607

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: a
  tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, que é
  diferente de outras instâncias do pacote libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  the crash ocurred during packettracert62 installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jun 14 21:33:39 2016
  ErrorMessage: a tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, 
que é diferente de outras instâncias do pacote libqtcore4:i386
  InstallationDate: Installed on 2016-06-13 (1 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: a 
tentar sobreescrever '/etc/xdg/Trolltech.conf' partilhado, que é diferente de 
outras instâncias do pacote libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Douglas Santos]

@Arup this installation doesn't have security issues, as the package
cannot be updated once the repo isn't there?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1536353

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Henry J. Douglas]

Sorry, false alarm. My very last attempt failed. Up/down arrows are
back.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Henry J. Douglas]

It's now working, I think. Downloaded and installed latest linux kernel
updates (listed below), restarted and performed several suspends without
losing connection or list of APs. Please confirm.

Start-Date: 2016-06-09  23:06:05
Commandline: apt upgrade
Requested-By: cyberdoug (1000)
Install: linux-signed-image-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), 
linux-image-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), 
linux-headers-4.4.0-24:amd64 (4.4.0-24.43, automatic), 
linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic), 
linux-headers-4.4.0-24-generic:amd64 (4.4.0-24.43, automatic)
Upgrade: linux-headers-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), 
linux-libc-dev:amd64 (4.4.0-22.40, 4.4.0-24.43), linux-image-generic:amd64 
(4.4.0.22.23, 4.4.0.24.25), linux-signed-image-generic:amd64 (4.4.0.22.23, 
4.4.0.24.25), linux-signed-generic:amd64 (4.4.0.22.23, 4.4.0.24.25), 
linux-generic:amd64 (4.4.0.22.23, 4.4.0.24.25)
End-Date: 2016-06-09  23:07:58

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp