[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Lucas]

New install of ubuntu 24.04, causes this issue

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions


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

[Desktop-packages] [Bug 2051574] Re: gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

[Lucas]

Issue present on installed today 24.04, during initial boot

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2051574

Title:
  gnome-shell-portal-helper crashed with SIGTRAP in
  waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Same as Summary

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 08:56:29 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-portal-helper
  InstallationDate: Installed on 2024-01-25 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
  ProcCmdline: /usr/libexec/gnome-shell-portal-helper
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
   ?? () from /lib/x86_64-linux-gnu/libwebkitgtk-6.0.so.4
  Title: gnome-shell-portal-helper crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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

[Desktop-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" 

[Desktop-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 Desktop
Packages, which is subscribed to firefox 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 Desktop
Packages, which is subscribed to firefox 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-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 

[Desktop-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. 

[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm

[Lucas Kanashiro]

Hi Helga,

Thanks for taking the time to report this bug and trying to make Ubuntu
better.

>From what I understood this is an issue with the snap package of
Thunderbird, if that's the case you should try to report here (?):

https://snapcraft.io/thunderbird

I am not sure if this bug will reach the snap maintainers here.

And I do not think this is an issue with the sssd package in the Ubuntu
archive, but an integration issue affecting the snap package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056760

Title:
  [snap]Thunderbird doesn't authenticate with sssd-kcm

Status in sssd package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I have Kerberos authentication set up in Thunderbird for my mailbox.

  My environment contains:

  helga@helga-rashomon:~$ env | grep KRB
  KRB5CCNAME=KCM:

  This means that Kerberos authentication should work through the sssd-
  kcm server.

  I initialize Kerberos and verify that it functions correctly:

  helga@helga-rashomon:~$ klist
  Ticket cache: KCM:1000
  Default principal: he...@example.org

  Valid starting  Expires Service principal
  03/11/24 04:14:24   03/12/24 04:14:24   krbtgt/example@example.org
  03/11/24 04:15:24   03/12/24 04:14:24   HTTP/redmine.example.org@
  Ticket server: HTTP/redmine.example@example.org

  (listing redacted to say example.org instead of the real address. the
  redmine listing shows that Firefox works correctly with this address)

  However, when I open the Snap Thunderbird, it does not recognize this
  Kerberos setup, showing me "The Kerberos/GSSAPI ticket was not
  accepted by the IMAP server". klist -A likewise shows no changes.

  The exact same setup works when I specify KRB5CCNAME=DIR:${HOME}/krb5cc in 
.profile instead.
  The sssd-kcm setup also works in Thunderbird native and Flatpak profiles.

  Considering the Flatpak specifically permits access to
  /run/.heim_org.h5l.kcm-socket, could it be that the Thunderbird Snap
  is not allowed to access this socket?

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


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

[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore

[Lucas Kanashiro]

Thanks for the reply Nathan.

Right, so I am targeting all the supported Ubuntu series now.

You are right, it should go to the development release first, before
SRUing the changes. I asked because it was not clear to me what series
are affected.


** Also affects: xdg-desktop-portal-gtk (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Mantic)
   Importance: Undecided
 Assignee: Nathan Teodosio (nteodosio)
   Status: Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2039187

Title:
  Thunderbird doesn't accept URI attachments anymore

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk source package in Focal:
  New
Status in xdg-desktop-portal-gtk source package in Jammy:
  New
Status in xdg-desktop-portal-gtk source package in Lunar:
  New
Status in xdg-desktop-portal-gtk source package in Mantic:
  Confirmed

Bug description:
  The desktop portal constructs an mailto: url with an attachment= but
  thunderbird upstream explicitly decided to not allow adding files from
  an URL for security reasons.

  One can still use the -compose option though, as this patch does.

  Test case
  -

  * Install the proposed package.
  * Log out and back in.
  * Set Thunberbird as default client in Gnome Control Panel.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters.
  * Thunderbird should open with the corresponding files attached.
  * [For regression testing] Set Evolution as the default.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters. It only attaches one 
file, this is however not a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions


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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Lucas Magasweran]

I no longer see the window grouping issue with Slack snap 4.34.121 on
Ubuntu 22.04.3.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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


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

[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore

[Lucas Kanashiro]

Hi Nathan,

Just to understand a bit better, is this bug affecting just Jammy? Any
other Ubuntu series? Please target the correct series in the bug.

Looking at your debdiff, the version string tells me that the target
should be Mantic and Lunar, since they have version 1.14.1-1. However
you mentioned Jammy, if that's the case, you need to apply your changes
on top of version 1.14.0-1build1.

Apart from that, the packaging changes LGTM. I see there is an ongoing
discussion in your upstream PR, maybe it is a good idea to wait a bit to
see if the patch requires some changes.

Another thing is that you need to update your bug description if you
want to SRU the proposed changes. Please, follow the template provided
here:

https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/2039187

Title:
  Thunderbird doesn't accept URI attachments anymore

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  The desktop portal constructs an mailto: url with an attachment= but
  thunderbird upstream explicitly decided to not allow adding files from
  an URL for security reasons.

  One can still use the -compose option though, as this patch does.

  Test case
  -

  * Install the proposed package.
  * Log out and back in.
  * Set Thunberbird as default client in Gnome Control Panel.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters.
  * Thunderbird should open with the corresponding files attached.
  * [For regression testing] Set Evolution as the default.
  * Open Nautilus and try to attach two files to the same email. They can be 
creatively named, it should not break on weird characters. It only attaches one 
file, this is however not a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions


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

[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation

[Lucas Kanashiro]

Anyone willing to provide a debdiff (changes + changelog) to fix this
issue in Jammy, Kinetic and Lunar? As Sebastien mentioned in comment
#29, this bug has ~ubuntu-sponsors subscribed but there is no "ready-to-
upload" debdiff attached.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984

Title:
  pcscd.socket is disabled after installation

Status in pcsc-lite package in Ubuntu:
  Fix Released
Status in pcsc-lite source package in Jammy:
  Triaged
Status in pcsc-lite source package in Kinetic:
  Triaged
Status in pcsc-lite source package in Lunar:
  Triaged
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  The pscc-lite package provides an open source implementation of PC/SC,
  the de-facto standard to interface Personal Computers with Smart
  Cards/Readers.

  This bug is in the upstream debian packaging, and results in the
  pcscd.socket being disabled after installation. This prevents
  automatic startup of the associated pcscd.service, thus preventing
  automatic handling of Smart Cards/Readers w/out manual intervention to
  enable the socket (which doesn't persist across reboots).

  This is especially painful for users that require Smart Authentication
  for login.

  [ Test Plan ]

  Steps to reproduce:

  1. If installed, remove and do a fresh install of the package pcscd
  (the sole version released for jammy is 1.9.5-3).

  2. Verify that the pcscd.socket is disabled:

  $ systemctl status pcscd.socket
  ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket
   Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor 
preset: enabled)
   Active: inactive (dead)
     Triggers: ● pcscd.service
   Listen: /run/pcscd/pcscd.comm (Stream)

  3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or
  Nitrokey) that's known to work on Ubuntu and verify that it fails to
  work.

  Repeating the same steps with a package built with the patch attached
  to comment #27 should ensure that the socket is enabled, and that
  interaction with a Smart Card or Crypto Token should work w/out manual
  intervention.

  [ Where problems could occur ]

  This is a back-ported change from upstream and is a result of a bug in
  dh_installsystemd (see comment #26). As such the risk is minimal.

  The only potential risk of failure I can come up with is a snap that
  stages the old version of the client library, as it would be looking
  in the wrong place for the socket.

  [ Other Info ]

  This bug was originally reported against Ubuntu Mate 22.04, however it
  applies to all derivatives of Ubuntu Desktop 22.04 LTS.

  Note - while there's some disagreement as to whether this bug occurs
  100% of the time across all 22.04 installations, it's pretty clear
  from the upstream Debian bug and subsequent packaging fix that we
  should land this.

  As the upstream fix landed in 1.9.9-2 (which is already released in mantic) 
only the following releases are impacted by this bug:
   - jammy
   - kinetic
   - lunar

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


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

[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock

[Lucas Kanashiro]

I added tasks for Jammy, Lunar and Mantic (devel). I also took a look at
the debdiff and you could also close this bug in the changelog via "LP:
#2014954". Moreover, you could improve the patch DEP-3 headers and add
the Bug-Ubuntu field with a link to this bug.

** Also affects: libmbim (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: libmbim (Ubuntu Lunar)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https://bugs.launchpad.net/bugs/2014954

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
- when the device is first shipped or comes out of the factory,
  it should be protected with a lock till the device reaches
  the end user. This FCC lock feature will ensure the device
  is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


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

[Desktop-packages] [Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

[Lucas Kanashiro]

This is in the general sponsorship queue, do you need help to get those
uploads sponsored? Or is there someone with upload rights working with
you on this? In case you already have someone to sponsor the uploads,
please, unsubscribe ~ubuntu-sponsors.

After a quick look at the latest debdiff proposed by Matthew, I would
suggest to use version 3.3.0-1ubuntu0.1 in Jammy. Right now, we have
version 3.3.0-1 in the release pocket, and using version 3.3.0-1ubuntu1
might make some users think that this delta was introduced during the
development cycle, and using 3.3.0-1ubuntu0.1 makes more explicit the
fact that this was introduced after the release via a SRU. This is just
my 2 cents, what was proposed would work out well, it is more a semantic
thing that I like to follow when adding a delta via SRU to a package
that used to be a sync from Debian.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890

Title:
  gvfsd process does not have the KRB5CCNAME environment set

Status in gvfs package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Invalid
Status in tracker-miners source package in Bionic:
  Won't Fix
Status in gvfs source package in Focal:
  Invalid
Status in tracker-miners source package in Focal:
  In Progress
Status in gvfs source package in Jammy:
  Invalid
Status in tracker-miners source package in Jammy:
  In Progress
Status in gvfs source package in Kinetic:
  Invalid
Status in tracker-miners source package in Kinetic:
  In Progress
Status in gvfs source package in Lunar:
  Invalid
Status in tracker-miners source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  The KRB5CCNAME environment variable points to the Kerberos ticket of
  the current machine and this ticket is used for authentication in
  Active Directory  servers.

  This variable is set by pam_sss when the user authenticates and can be
  used by other processes, such as gio, to skip the credentials input
  when accessing network shares, for example.

  Some services rely on gvfs-daemon in order to properly function, such
  as tracker-extract-3.service and tracker-miner-fs-3.service, which
  means they will ask for the gvfs-daemon to be initialized when they
  are executed by systemd. This creates problems if one service that
  relies on gvfsd is started too early, as it would result in gvfsd
  being started too early as well.

  As of version 3.1 of tracker-miners, the install target of tracker-
  miners-fs-3.service was set to gnome-session.target:
  https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283

  However, the tracker-extract-3.service was not updated and its target
  is still default.target, which is too early for the service to start.

  Starting tracker-extract too early is also starting gvfsd too early,
  before the session environment gets fully updated. Which means that
  gvfsd does not have the KRB5CCNAME variable and can not do any
  operations with it.

  Tracker-extract is supposed to be a helper service managed by tracker-
  miner-fs-3.service. By using a [Install] section, we are actually
  telling systemd that it should manage this service as well, when it
  shouldn't.

  So, by removing the [Install] section and having tracker-miner-
  fs-3.service being tied to gnome-session.target, we fix the issue of
  gvfsd starting too early without the updated session environment.

  [ Test Plan ]

  In order to test this issue, it's required to have an Active Directory server 
running.
  1) Authenticate with an AD user (as this would set the KRB5CCNAME env);
  2) Check gvfsd environment. This can be done by running:
  cat /proc/$(pidof gvfsd)/environ | xargs --null -n1

     You will be able to see that it does not have the variable listed.
  3) Check that the information mentioned above about tracker-miner-fs-
     3.service is true.
  4) Disable tracker-extract-3.service (This is a bit tricky, since its
     target was default.target. The easiest way is to remove the symlink that
     systemd created when enabling the unit, located under
     /etc/systemd/user/default.target.wants/tracker-extract-3.service
  5) Reboot the machine;
  6) Repeat steps 1 and 2.
     This will show that gvfsd is now started with the proper environment.

  Is not enough to look at ptree and the pids of the processes, instead
  it's better to look into the session logs with:

     journalctl --user -b

  And check the order in which the services were started and when they
  were triggered.

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test

  After installing test packages of tracker-miners, KRB5CCNAME should be
  set in gvfs environment upon login to gnome.

  [ Where problems could occur ]

  The tracker project is a search engine that speeds up search
  

[Desktop-packages] [Bug 2017452] [NEW] On run, nautilus opens two windows instead of one

[Douglas Lucas]

Public bug reported:

Narrative: I boot into a live Lubuntu operating system -- either 22.10
or 23.04; bug is the same in both -- and open up the terminal where I
run 'sudo apt update && sudo apt install nautilus' Next I use the
"Superkey + R" keyboard shortcut to open up the dialog to run a program.
I run 'nautilus' and two windows open, both for the Home directory. The
two windows are identical except they are visually separated from one
another slightly on the screen. Expected behavior is to open just one
window to my home folder.

Currently I'm running Lubuntu 23.04 but same bug happens in Lubuntu 22.10
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04

Source package is presumably 'nautilus'

$ apt-cache policy nautilus
nautilus:
  Installed: 1:44.0-1ubuntu2
  Candidate: 1:44.0-1ubuntu2
  Version table:
 *** 1:44.0-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
100 /var/lib/dpkg/status

I expected running nautilus to open up one window to my Home directory
but instead it opens two.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nautilus 1:44.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: LXQt
Date: Sun Apr 23 21:57:33 2023
GsettingsChanges:
 
LiveMediaBuild: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug lunar nautilus

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2017452

Title:
  On run, nautilus opens two windows instead of one

Status in nautilus package in Ubuntu:
  New

Bug description:
  Narrative: I boot into a live Lubuntu operating system -- either 22.10
  or 23.04; bug is the same in both -- and open up the terminal where I
  run 'sudo apt update && sudo apt install nautilus' Next I use the
  "Superkey + R" keyboard shortcut to open up the dialog to run a
  program. I run 'nautilus' and two windows open, both for the Home
  directory. The two windows are identical except they are visually
  separated from one another slightly on the screen. Expected behavior
  is to open just one window to my home folder.

  Currently I'm running Lubuntu 23.04 but same bug happens in Lubuntu 22.10
  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  Source package is presumably 'nautilus'

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:44.0-1ubuntu2
Candidate: 1:44.0-1ubuntu2
Version table:
   *** 1:44.0-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  I expected running nautilus to open up one window to my Home directory
  but instead it opens two.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: LXQt
  Date: Sun Apr 23 21:57:33 2023
  GsettingsChanges:
   
  LiveMediaBuild: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

[Lucas Kanashiro]

The following changes were applied upstream to fix this issue in
network-manager:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1491/diffs

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Invalid

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward

[Lucas Gallindo]

I just got this issue after a clean install of LUbuntu 22.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1872950

Title:
  Nvidia 340.108 fails to install with kernels 5.5 onward

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Groovy:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * Installing the 340 driver will fail when running Linux 5.7 or
  newer.

  [Test Case]

   * Install nvidia-340 from -proposed.

   * Check that the modules was built and installed, using the
     following command:

     dkms status

  [Regression Potential]

   * The driver once built and installed could be not working and lead
  to have the desktop not starting for example. Check that you get a
  desktop loaded and decent performances

  

  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions


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

[Desktop-packages] [Bug 1993356] Re: udisks doesn't make sense from cdrom

[Lucas Kanashiro]

We still have no progress in the upstream issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1993356

Title:
  udisks doesn't make sense from cdrom

Status in udisks:
  Unknown
Status in qemu package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  udisks doesn't make sense from cdrom

  there are journal errors from sending ATA command IDENTIFY, maybe
  incomplete kernel or qemu support?

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


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

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

[Lucas Kanashiro]

** Also affects: oem-priority/focal
   Importance: Undecided
 Assignee: Robert Liu (robertliu)
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1998765

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in libnl3 package in Ubuntu:
  New

Bug description:
  [ Impact ] 
  When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.

  However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.

  After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
  identified as the root cause.

  According to the commit, the "NLA_F_NESTED" flag should be set for
  kernel later than 5.2.

  [ Test Plan ]
  Verify with the updated version, the WIFI module can:
1. scan WIFI networks
2. connect to an available network
3. access to the connected network

  [ Where problems could occur ]
  1. kernel versions without NLA_F_NESTED flag defined
This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.

  2. Drivers don't use the NESTED flag.
According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.

  [ Other Info ]
  22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions


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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Lucas Sandery]

@slalomsk8er, I'm not disagreeing with snap's shortcomings, I'm just providing 
alternatives for anyone who's run into such issues. There is now also the 
option of getting stable builds in .deb form from the MozillaTeam 
(https://wiki.ubuntu.com/MozillaTeam) PPA at
https://launchpad.net/~mozillateam/+archive/ubuntu/ppa
There are many guides about how best to use it and ensure you receive automatic 
updates.

They have been providing ESR builds for some time, but recently added
stable packages. I haven't found any info that verifies their members as
employed by either Canonical or Mozilla, but they seem to have some
trust by the community.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  In Progress
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  In Progress
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed
Status in plasma-browser-integration package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

  [Workaround]
  If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with 
this app.

  sudo apt install gnome-shell-extension-manager

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


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

[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector

[Lucas Sandery]

One can use the builds directly from Mozilla
https://www.mozilla.org/firefox/all/ but the onus is on the
user/sysadmin to keep it updated.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1741074

Title:
  [snap] chrome-gnome-shell extension fails to detect native host
  connector

Status in Mozilla Firefox:
  In Progress
Status in KeePassXC Snap Builds:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  In Progress
Status in goopg package in Ubuntu:
  Confirmed
Status in kdeconnect package in Ubuntu:
  Confirmed
Status in plasma-browser-integration package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chrome-gnome-
  shell-does-not-work-with-chromium-snap/3377)

  See attached screenshot.

  [Workaround]
  If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with 
this app.

  sudo apt install gnome-shell-extension-manager

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


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

[Desktop-packages] [Bug 1978890] Re: FIPS/OEM installation compatibility is unclear to the end-user

[Lucas Albuquerque Medeiros de Moura]

We discussed this on the UA team and we believe we can warn the user of
the potential problems of enabling FIPS we using a OEM kernel, but we
don't think we should block this on the UA side, since users could still
be aware of the risk and follow through with the procedure.

However, before we deliver this through UA, we believe we need to sort
the GRUB_FLAVOUR_ORDER scenario. Otherwise we will warn the user and
even if they want to proceed with FIPS, the will end up in the OEM
kernel regardless.

But let us know if you think we should definitely block enabling FIPS on
a machine running a OEM kernel.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1978890

Title:
  FIPS/OEM installation compatibility is unclear to the end-user

Status in subiquity package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  [Overall Summary]

  Converting to cover all oem/fips compatibility issues with
  ua/installers/update-manager. These projects are mostly silo'd, so
  when they all converge it creates a confusing and frustrating
  experience for the user.

  At it's core, the problem is that both fips and oem us
  GRUB_FLAVOUR_ORDER to select the preferred kernel to boot from,
  disregarding versioning.

  The main issues are:
  1. ubuntu-drivers should not attempt to `oem-ify` a `fipsified` machine
  2. ua tool should not attempt to `fipsify` an oem machine
  3. subiquity should mention that drivers page is potentially making machine 
realtime & fips incompatible

  
  Below are some reproducible examples of issues:

  ---
  (Subiquity installer case)
  [Summary]
  A recent change to the subiquity snap adds support for installing oem drivers 
at time of instance install. If the user installs these packages, then attempts 
to install the fips packages post-install, fips will install as expected, but 
the system will always boot to the oem kernel.

  [Expected Behavior]
  Messaging should clearly indicate that installing the oem packages will make 
the environment incompatible with fips/RT kernel/ etc. 

  [Observed Behavior]
  Subiquity just offers additional drivers, without clarifying the 
compatibility complications.

  [Replication Steps]
  (Using Dell Inc. Precision 7920 Tower/060K5C)
  1. Install from current focal ISO
  2. Confirm driver installation on the oem gui page
  3. Install ua client/fips
  4. Reboot
  5. Observe kernel version (oem)

  ---
  (update-manager case)
  [Summary]
  A feature was added to allow for post-install enablement for oem-enabled 
devices via update manager:
  https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050

  While this works great for some situations, it can lead to users
  unexpectedly installing the oem meta package + associated kernel,
  overwriting an existing fips installation, as the "Improved hardware
  support" bundle may not be noticed when operating update-manager

  [Expected Behavior]
  For non linux-generic running installs, the post-install oem enablement 
functionality should not trigger, nor should it add the additional repositories 
to the client's sources.list.d.

  [Observed Behavior]
  sources.list.d is updated and "Improved hardware support" is allowed as an 
option in update-manager, which leads to clients unexpectedly losing compliance 
in fips environments.

  [Replication Steps]
  (Using Dell Inc. Precision 7920 Tower/060K5C)
  1. Install from current focal ISO
  2. Attach a ua subscription
  3. Enable the fips-updates service
  4. Reboot the system, login the desktop and wait for a while. The 
notification will pop up and it will show "Improved hardware support" on the 
certified machines that has the OEM metapackage support.
  5. Click through the update-manager prompt and install the oem packages
  6. Reboot check fips status

  oem's config in /etc/default/grub.d/* does not have a number prefix,
  and thus will always override 99-ubuntu-fips.cfg when calling update-
  grub.

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


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

[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04

[Lucas Varsky]

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

This also happens to me on my AMD laptop, this is why we use backups!
Can't live without the gestures.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969254

Title:
  wayland session not longer an option after recent update on Ubuntu
  22.04

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After some recent update to Ubuntu 22.04 dev, X11 is selected by
  default and there is no longer the option to select the display
  protocol at login.

  It seems I am not the only affected:
  https://askubuntu.com/questions/1402671/ubuntu-no-gear-for-
  waylaland-x11

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-session 42.0-1ubuntu2
  Uname: Linux 5.17.3-051703-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 22:20:35 2022
  InstallationDate: Installed on 2022-02-02 (72 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago)

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


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

[Desktop-packages] [Bug 1969245] [NEW] scroll on dock shows workspaces OSD with missing information

[Lucas Varsky]

Public bug reported:

Description: 
When I scroll on the dock to change workspaces, it displays the new OSD for 
switching a workspace, but the white circles that display the current workspace 
are shown on a dark gray and the OSD's animation is missing. 

What should happen:
The OSD should display the correct animation you would see if you type 
Super/Win + Alt + Left/Right Arrow
Or no OSD at all. 

Replicate it: 
Scroll on dock. 

Hardware info:
Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta (15/04/2022)

Package version (output of apt-cache policy):

apt-cache policy gnome-shell-extension-ubuntu-dock

gnome-shell-extension-ubuntu-dock:
  Instalados: 72~ubuntu4
  Candidato: 72~ubuntu5
  Tabla de versión:
 72~ubuntu5 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
 *** 72~ubuntu4 100
100 /var/lib/dpkg/status

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 22.04 bug jammy ui

** Tags added: 22.04 bug jammy ui

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1969245

Title:
  scroll on dock shows workspaces OSD with missing information

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Description: 
  When I scroll on the dock to change workspaces, it displays the new OSD for 
switching a workspace, but the white circles that display the current workspace 
are shown on a dark gray and the OSD's animation is missing. 

  What should happen:
  The OSD should display the correct animation you would see if you type 
Super/Win + Alt + Left/Right Arrow
  Or no OSD at all. 

  Replicate it: 
  Scroll on dock. 

  Hardware info:
  Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta 
(15/04/2022)

  Package version (output of apt-cache policy):

  apt-cache policy gnome-shell-extension-ubuntu-dock

  gnome-shell-extension-ubuntu-dock:
Instalados: 72~ubuntu4
Candidato: 72~ubuntu5
Tabla de versión:
   72~ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
   *** 72~ubuntu4 100
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969245/+subscriptions


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

[Desktop-packages] [Bug 1969244] [NEW] ubuntu dock's right click menu switches position when the dock is hidden

[Lucas Varsky]

Public bug reported:

Description: 
When ubuntu-dock is set to autohide and in hidden state (happens on panel and 
dock mode) 
When you go to right-click an icon to access its menu, the dock hides again and 
the menu stays open but when you click it the menu updates its position to be 
closer to the dock, leading to miss clicks and a worse user experience. 

What should happen: 
The dock should stay visible while you interact with the menu. 

Replicate it: 
Set your dock to autohide and then, trigger the autohide (like maximizing a 
window), reach for one of the icons and right-click it.


Hardware info: 
Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta (15/04/2022)


Package version (output of apt-cache policy): 

apt-cache policy gnome-shell-extension-ubuntu-dock

gnome-shell-extension-ubuntu-dock:
  Instalados: 72~ubuntu4
  Candidato:  72~ubuntu5
  Tabla de versión:
 72~ubuntu5 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
 *** 72~ubuntu4 100
100 /var/lib/dpkg/status

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 22.04 bug gnome-shell-extension-ubuntu-dock jammy ui

** Tags added: ui

** Tags added: jammy

** Tags added: 22.04 bug gnome-shell-extension-ubuntu-dock

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1969244

Title:
  ubuntu dock's right click menu switches position when the dock is
  hidden

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Description: 
  When ubuntu-dock is set to autohide and in hidden state (happens on panel and 
dock mode) 
  When you go to right-click an icon to access its menu, the dock hides again 
and the menu stays open but when you click it the menu updates its position to 
be closer to the dock, leading to miss clicks and a worse user experience. 

  What should happen: 
  The dock should stay visible while you interact with the menu. 

  Replicate it: 
  Set your dock to autohide and then, trigger the autohide (like maximizing a 
window), reach for one of the icons and right-click it.

  
  Hardware info: 
  Asus Vivobook 14 Ryzen 5 3500U & Radeon Graphics. Ubuntu 22.04 Beta 
(15/04/2022)

  
  Package version (output of apt-cache policy): 

  apt-cache policy gnome-shell-extension-ubuntu-dock

  gnome-shell-extension-ubuntu-dock:
Instalados: 72~ubuntu4
Candidato:  72~ubuntu5
Tabla de versión:
   72~ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
   *** 72~ubuntu4 100
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969244/+subscriptions


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

[Desktop-packages] [Bug 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

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

** This bug has been marked a duplicate of bug 1967901
   [qxl] Xorg fails to start with "Screen(s) found, but none have a usable 
configuration."

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968063

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

adding Xorg crash dump

** Attachment added: "Xorg crash dump"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968063

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1968063] [NEW] Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

Public bug reported:

Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
Server will not start. Either directly via lightdm or via gdm/wayland
selecting Xubuntu session.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  6 17:59:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash jammy ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968063

Title:
  Jammy: Xorg crash on virtual QXL graphics

Status in xorg package in Ubuntu:
  New

Bug description:
  Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
  Server will not start. Either directly via lightdm or via gdm/wayland
  selecting Xubuntu session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  6 17:59:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-focal
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-focal
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: 

[Desktop-packages] [Bug 1965138] [NEW] Desktop application should check for service available information before listing it

[Lucas Albuquerque Medeiros de Moura]

Public bug reported:

Currently, it seems that software-properties is incorrectly assuming
that both ESM and Livepatch services can be enabled in a Jammy machine.
Those services are not yet available in Jammy and we are attaching an
image showing that the Desktop message is that we had an error enabling
then and that the user should try again.

It seems that software-proporties source `/var/lib/ubuntu-
advantage/status.json` and assumes the services is available if it
appears on the services list and the `entitled` field has the `yes`
value. However, it is perfectly possible for a service to be entitled to
an user, but not available in the user's machine.

We are now suggesting that software-properties also looks at the
`available` field in the services json output to make that assumption,
this will probably solve the issue we are seeing on Jammy.

Another approach would be using the output of `ua status --format json`
directly. However, this command will make a request to the contract's
server if the user is unattached and maybe it is not wise to use it in
that context. However, the output of that command only show services
that are available, so we would not need to apply that extra available
filter to it.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "jammy-desktop-error.png"
   
https://bugs.launchpad.net/bugs/1965138/+attachment/5569662/+files/jammy-desktop-error.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1965138

Title:
  Desktop application should check for service available information
  before listing it

Status in software-properties package in Ubuntu:
  New

Bug description:
  Currently, it seems that software-properties is incorrectly assuming
  that both ESM and Livepatch services can be enabled in a Jammy
  machine. Those services are not yet available in Jammy and we are
  attaching an image showing that the Desktop message is that we had an
  error enabling then and that the user should try again.

  It seems that software-proporties source `/var/lib/ubuntu-
  advantage/status.json` and assumes the services is available if it
  appears on the services list and the `entitled` field has the `yes`
  value. However, it is perfectly possible for a service to be entitled
  to an user, but not available in the user's machine.

  We are now suggesting that software-properties also looks at the
  `available` field in the services json output to make that assumption,
  this will probably solve the issue we are seeing on Jammy.

  Another approach would be using the output of `ua status --format
  json` directly. However, this command will make a request to the
  contract's server if the user is unattached and maybe it is not wise
  to use it in that context. However, the output of that command only
  show services that are available, so we would not need to apply that
  extra available filter to it.

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


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

[Desktop-packages] [Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

[Lucas Kanashiro]

According to the Debian bug, ssl-cert/1.1.1 contains the fix and it is
already available in jammy (release pocket), so I am marking this as fix
released.

** Changed in: ssl-cert (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1945774

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  New
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

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


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

[Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled

[Lucas Kanashiro]

The debdiff to add libvpx to lto-disabled-list package looks good to me,
+1.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

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


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

[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)

[Joao Lucas de Paiva Paulino]

I'm here to say that I'm having the same issue.

Until this evening, I was using Debian 10 with KDE, but I installed
Ubuntu 20.04 a few hours ago.

I use a laptop with a external keyboard connected on it and my laptop
have a numeric keyboard and my external keyboard don't, so I always use
the laptop keyboard to insert numbers. However, each time I swap the
keyboard, my computer frozen.

Also, I have a mouse with several buttons and two of them are configured
as "PgUp" and "PgDn" because I find it more practical over there.
However, unfortunately, I can't use it properly because the computer
crashes every time I press a button. However, I think it's worth
mentioning that mouse buttons that belong to the mouse (like click and
scroll) don't have this problem.

In short, if I switch keyboards, whether it's laptop, external or mouse
buttons, my computer freezes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/108

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions


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

[Desktop-packages] [Bug 1928604] Re: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases

[Lucas Kanashiro]

Thanks for taking the time to file this bug and trying to make Ubuntu
better.

ubuntu-advantage-tools does not provide only a way to enable ESM, it
also provides a bunch of other services (from the project README):

"The Ubuntu Advantage client provides users with a simple mechanism to
view, enable, and disable offerings from Canonical on their system. The
following entitlements are supported:

Common Criteria EAL2 certification artifacts provisioning
Canonical CIS Benchmark Audit Tool
Ubuntu Extended Security Maintenance
FIPS 140-2 Certified Modules
FIPS 140-2 Non-Certified Module Updates
Livepatch Service
"

Those other services might be useful in non-EOL releases. Due to that,
the package is installed by default in all supported releases.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1928604

Title:
  ubuntu-advantage-tools should not be auto-installed on supported
  Ubuntu releases

Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  I understand that Canonical thinks about financial profit. It is
  business and it is good.

  But please do not install ubuntu-advantage-tools to supported releases
  like 18.04 LTS, 20.04 LTS and 21.04. It may confuse users. Users do
  not expect ESM existence on supported systems.

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

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

[Desktop-packages] [Bug 1926346] [NEW] Desktop Action missing translation into Brazilian Portuguese

[Lucas Wilm]

Public bug reported:

Using Xubuntu 20.04 and I have a Firefox (version 88) launcher on the
xfce4-panel. When right-clicking, a context menu with Desktop Actions
like "Open a New Private Window" is opened and it's missing translation
into Brazilian Portuguese for that string.

I reported the bug in bugzilla
(https://bugzilla.mozilla.org/show_bug.cgi?id=1705800) and I was told to
report it in my distribution bug tracker.

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

** Attachment added: "Captura de tela_2021-04-16_15-11-34.png"
   
https://bugs.launchpad.net/bugs/1926346/+attachment/5492893/+files/Captura%20de%20tela_2021-04-16_15-11-34.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1926346

Title:
  Desktop Action missing translation into Brazilian Portuguese

Status in firefox package in Ubuntu:
  New

Bug description:
  Using Xubuntu 20.04 and I have a Firefox (version 88) launcher on the
  xfce4-panel. When right-clicking, a context menu with Desktop Actions
  like "Open a New Private Window" is opened and it's missing
  translation into Brazilian Portuguese for that string.

  I reported the bug in bugzilla
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1705800) and I was told
  to report it in my distribution bug tracker.

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

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

[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop

[Lucas Sandery]

@seb128 I'm not sure it's upstream.
 has been around
forever and was marked as duplicate of the still open
 where it appears
Mozilla doesn't want to do anything about it. The earliest ancestor of
that file I can find in the source is from 2010
.

** Bug watch added: Mozilla Bugzilla #371734
   https://bugzilla.mozilla.org/show_bug.cgi?id=371734

** Bug watch added: Mozilla Bugzilla #296568
   https://bugzilla.mozilla.org/show_bug.cgi?id=296568

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1861262

Title:
  Add message/rfc822 to thunderbird.desktop

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Please add message/rfc822 to thunderbird.desktop:

  -MimeType=x-scheme-handler/mailto;application/x-xpinstall;
  +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822;

  It will allow to open *.eml files. I attach an example eml file.

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

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

[Desktop-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

[Lucas Kanashiro]

Thank you for taking the time to file a bug report.

>From what you described it seems that Network Manager is the one
responsible for adding the unexpected routing rule, so this might not
affect OpenVPN itself. I quickly tried to reproduce your setup but did
not notice the bug there. Could you please share your config files to
see if I missed something?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

** Changed in: openvpn (Ubuntu)
   Status: New => Incomplete

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1914288] Re: Xorg freeze

[André Lucas Moisés Lacerda]

** Information type changed from Private Security to Private

** Information type changed from Private to Public Security

** Information type changed from Public Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1914288

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes randomly during usage and always after recovering from suspend
  mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  2 16:51:10 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
  InstallationDate: Installed on 2020-09-10 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 3583
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0NN4D6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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

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

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

[Desktop-packages] [Bug 1914288] [NEW] Xorg freeze

[André Lucas Moisés Lacerda]

Public bug reported:

Freezes randomly during usage and always after recovering from suspend
mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  2 16:51:10 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
   Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
InstallationDate: Installed on 2020-09-10 (144 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Inspiron 3583
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2020
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0NN4D6
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu

** Information type changed from Public to Private Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1914288

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freezes randomly during usage and always after recovering from suspend
  mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  2 16:51:10 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08ca]
 Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] 
[1028:08ca]
  InstallationDate: Installed on 2020-09-10 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 3583
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=7f3ab5d0-2b6b-4064-81ec-9a66d46303f4 ro quiet splash radeon.modeset=0 
amdgpu.dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0NN4D6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:br1.8:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0NN4D6:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Lucas Lamonds]

Updated to the 460 drivers and it works with modeset=1.  With modeset=1
and 450, it wasn't working.

I have a Quadro K2000 and a 2080 Super dual gpu, single monitor setup.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1870736

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions

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

[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

[lucas grigolon varela]

I can confirm the same problem and the "Scroll Lock" workaround worked
here too. I'm using my system with English language but the keyboard is
the BR-ABNT2. I tried with different drivers of Nvidia and with Noveau,
no difference. I'm using ubuntu 20.04.1 LTS.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1895486

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Fix Committed

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions

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

[Desktop-packages] [Bug 1898747] [NEW] [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No sound at all on hdmi audio output

[Lucas Arroyo Blanco]

Public bug reported:

Recently I reinstalled ubuntu on my laptop and this time I found that
when I connect the laptop to the tv with the hdmi I manage to get the
video working but with no sound, it reproduces from the laptop speakers.

On pulseaudio volume control the digital stereo hdmi output appears as
unplugged and unavailable.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 17:29:42 2020
InstallationDate: Installed on 2020-09-29 (7 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lucas  1634 F pulseaudio
 /dev/snd/controlC0:  lucas  1634 F pulseaudio
 /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
 /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.26
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 84F7
dmi.board.vendor: HP
dmi.board.version: 07.10
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: 4AR14EA#ABE
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No
  sound at all on hdmi audio output

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Recently I reinstalled ubuntu on my laptop and this time I found that
  when I connect the laptop to the tv with the hdmi I manage to get the
  video working but with no sound, it reproduces from the laptop
  speakers.

  On pulseaudio volume control the digital stereo hdmi output appears as
  unplugged and unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 17:29:42 2020
  InstallationDate: Installed on 2020-09-29 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1634 F pulseaudio
   /dev/snd/controlC0:  lucas  1634 F pulseaudio
   /dev/snd/pcmC0D0c:   lucas  1634 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lucas  1634 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP Pavilion Notebook, Nvidia GPU 80 HDMI/DP, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84F7
  dmi.board.vendor: HP
  dmi.board.version: 07.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.26:bd12/13/2019:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn84F7:rvr07.10:cvnHP:ct10:cvrChassisVersion:

[Desktop-packages] [Bug 1878094] Re: Ubuntu 20.04 / Pulseaudio RTP receive broken sound

[Lucas]

This bug has now been fixed upstream. Can we pull this?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1878094

Title:
  Ubuntu 20.04 / Pulseaudio RTP receive broken sound

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  just upgraded some of my computers to Ubuntu 20.04, also tried with
  fresh install, in all case the pulseaudio rtp receive module is giving
  me very poor sound.

  Easily reproducible on a single machine :

  pacmd load-module module-null-sink sink_name=MyNullSink
  pacmd load-module module-rtp-send source=MyNullSink.monitor loop=true
  pacmd load-module module-rtp-recv

  And then play something in the null sink, loopback sound will be bad
  (lags).

  What I noticed : if I open the rtp stream with vlc, it's ok, sound is
  good.

  Ubuntu 20 uses PulseAudio 13.99, aka (I guess) PulseAudio 14 which
  implements RTP through gstreamer, which is new.

  So I tested my rtp stream with gstreamer:

  gst-launch-1.0 udpsrc address=224.0.0.56 port=46586
  caps="application/x-rtp, media=audio, payload=10, clock-rate=44100" !
  .recv_rtp_sink_0 rtpbin ! rtpL16depay ! audioconvert ! audioresample !
  pulsesink

  And it works fine, so I definitively believe there is an issue in the
  new module-rtp-recv.so bundled with PulseAudio and that is now based
  on gstreamer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC2', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 11 22:22:55 2020
  InstallationDate: Installed on 2019-03-31 (407 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-09 (2 days ago)
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1404
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX H370-I GAMING
  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.:bvr1404:bd09/13/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXH370-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [deleted]
  mtime.conffile..etc.pulse.daemon.conf: 2020-05-10T12:17:27.278185
  mtime.conffile..etc.pulse.default.pa: 2020-05-10T12:13:15.278817
  mtime.conffile..etc.pulse.system.pa: 2020-05-11T16:24:47.654012

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

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

[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Lucas Chen Alba]

I was having this issue, didn't gather much info on in, but I was on
Ubuntu 18.x LTS, my Dell Vostro was detecting 3 mics, when I actually
had only 1. I reinstalled Ubuntu, 20.04 now. At first glance it was
detecting the same mics and some buzz noise, same with the 18.x, but
then after the initial update, I restarted my pc and now it's all
working, and it only detects 1 mic

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

[Lucas Trognon]

In this case, I believe that the screenpad upgrade tool is needed. I
only have Pop!Os 20.04, and no Windows available. It might be were the
issue is coming from

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1846090

Title:
  Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:180e]
  InstallationDate: Installed on 2019-09-27 (3 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Lucas Magasweran]

@seb128, yes. It is still in issue on 20.04 (focal).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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

[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

[Lucas Trognon]

@ilya 
Hi, I've heard of people managing to make it work on other models. Are you 
using the UX580gd as well ? Are you using a dual boot with Windows ?

@Taha
Apologies, I forgot to subscribe to the bug. Yes I did and met no success :(

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1846090

Title:
  Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:180e]
  InstallationDate: Installed on 2019-09-27 (3 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

[Lucas Trognon]

Thanks for the insight !

Sadly, it seems like it is not working on xorg for UX580GD independently
of the GPU used.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1846090

Title:
  Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:180e]
  InstallationDate: Installed on 2019-09-27 (3 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

[Lucas Trognon]

Taha, 
Did the screenpad work out of the box or did you have to download/setup 
additional drivers ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1846090

Title:
  Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:180e]
  InstallationDate: Installed on 2019-09-27 (3 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Lucas Magasweran]

Removing the snap version and installing the deb version fixed the issue
for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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

[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)

[Henry Lucas]

Hello, I have this problem on my Ubuntu VMs (since 19.04). However, my Debian 
10 VMs are not affected. I hope this bug will be fixed before the LTS. This 
graphics bug makes my VMs unusable.
Thank you.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1825842

Title:
  [vmware] Background goes white when using scaling (200%, 300% or 400%)

Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  As soon as I set my display to scaled (any percentage) via Settings ->
  Displays -> Scale, the background image disappears and become all
  white. When I choose a different background image via Settings ->
  Background initially nothing happens. As soon as I switch back to 100%
  scaling, the image I choose before now appears.

  This problem started right after updating to 19.04. No such issues
  with either 18.04 or 18.10.

  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:35:49 2019
  DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-03-01 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, 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

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

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

[Desktop-packages] [Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

[Lucas Partridge]

 for mime-support (3.60ubuntu1) ...
Setting up libnss-myhostname:amd64 (237-3ubuntu10.15) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2) ...
Processing triggers for libglib2.0-0:amd64 (2.56.3-0ubuntu0.18.04.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Setting up colord (1.3.3-2build1) ...
colord.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...
Setting up gnome-control-center (1:3.28.2-0ubuntu0.18.04.2) ...

At long last I have my Settings back (and printer!). Than you so much:).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1821809

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

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

[Desktop-packages] [Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

[Lucas Partridge]

Also, shouldn't the user at least see an error message if you click on
the Settings icon but nothing appears to happen?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1821809

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

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

[Desktop-packages] [Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

[Lucas Partridge]

Thanks. Yes, I had installed a ppa for simple-scan a long time ago to
fix a scanner issue but I thought I'd gotten rid of it. I have also just
deleted all the ppas to do with that under /etc/apt/sources.list.d. But
I still can't get gnome-control-center to run or be installed:

The following packages have unmet dependencies.
 gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

Do you have any idea how I can fix this please? I'm at a loss here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1821809

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

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

[Desktop-packages] [Bug 1821809] Re: gnome-control-center won't install: Depends: colord (>= 0.1.30)

[Lucas Partridge]

I don't think this is exactly the same as
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1762256 because when I try installing the tree of
dependencies I get slightly different errors...

$ sudo apt install colord
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 colord : Depends: libsane1 (>= 1.0.24) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

$ sudo apt install libsane1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libsane1 : Depends: libsane-common (= 1.0.27-1~experimental3ubuntu2) but 
1.0.27+git20180317-xenial0 is to be installed
Recommends: sane-utils (>= 1.0.27-1~experimental3ubuntu2)
E: Unable to correct problems, you have held broken packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1821809

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

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

[Desktop-packages] [Bug 1821809] [NEW] gnome-control-center won't install: Depends: colord (>= 0.1.30)

[Lucas Partridge]

Public bug reported:

This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/1762256.

I noticed Settings has gone missing from my ubuntu 18.04. When I click
on the spanner icon under the power icon in the top right nothing
appears to happen. Attempting to install it fails with:

$ sudo apt install gnome-control-center
[sudo] password for lucas: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 gnome-control-center : Depends: colord (>= 0.1.30)
E: Unable to correct problems, you have held broken packages.

This may have come about as a side-effect of trying to install simple-
scan. I raised a question about that at
https://askubuntu.com/q/1108407/103266 but it never got fixed. I
couldn't resolve the error "Unable to correct problems, you have held
broken packages". Any suggestions welcome, please.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 21:15:46 2019
InstallationDate: Installed on 2017-09-03 (569 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1821809

Title:
  gnome-control-center won't install: Depends: colord (>= 0.1.30)

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This bug looks similar to https://bugs.launchpad.net/ubuntu/+source
  /gnome-control-center/+bug/1762256.

  I noticed Settings has gone missing from my ubuntu 18.04. When I click
  on the spanner icon under the power icon in the top right nothing
  appears to happen. Attempting to install it fails with:

  $ sudo apt install gnome-control-center
  [sudo] password for lucas: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   gnome-control-center : Depends: colord (>= 0.1.30)
  E: Unable to correct problems, you have held broken packages.

  This may have come about as a side-effect of trying to install simple-
  scan. I raised a question about that at
  https://askubuntu.com/q/1108407/103266 but it never got fixed. I
  couldn't resolve the error "Unable to correct problems, you have held
  broken packages". Any suggestions welcome, please.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 26 21:15:46 2019
  InstallationDate: Installed on 2017-09-03 (569 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1821809/+subscriptions

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

[Desktop-packages] [Bug 1559739] Re: Systemd service script for daemon doesn't use /etc/default/transmission-daemon

[Lucas Clemente Vella]

How do I submit a patch?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1559739

Title:
  Systemd service script for daemon doesn't use /etc/default
  /transmission-daemon

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  transmission-daemon:
Installed: 2.84-1ubuntu1
Candidate: 2.84-1ubuntu1
Version table:
   *** 2.84-1ubuntu1 0
  500 http://fi.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected:
  Changing CONFIG_DIR in /etc/default/transmission-daemon, causes the daemon to 
use that directory for its configuration and runtime folders.

  What happened instead:
  Whatever value CONFIG_DIR had, transmission-daemon acted as if it was the 
default ('/var/lib/transmission-daemon/info').

  I was finally able to fix this by adding 
'EnvironmentFile=/etc/default/transmission' into the service file and changing 
the name of CONFIG_DIR to TRANSMISSION_HOME in /etc/default/transmission. I 
tried adding $OPTIONS to the command line in the service file instead (as the 
older startup scripts do) but apparently systemd doesn't support substitution 
in the environment file. 
  This enables specifying the configuration directory, and shouldn't break the 
older scripts.

  Btw, having three init scripts is kind of confusing.

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

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

[Desktop-packages] [Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

[Lucas Rizzini da Costa Lima]

Same problem here. I'm using Ubuntu 18.10 LiveCD and from time to time
my Ubuntu just freezes and when it happens my pendrive LED blinks like
crazy. It's hard to recover from it, but yesterday I did. The log it at
the post below.

Here's my post about it: https://unix.stackexchange.com/questions/483898
/my-shell-script-to-periodically-free-some-memory-up-with-ubuntu-18-10
-livecd-wit#_=_

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1588009

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

Status in libinput:
  Invalid
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have just recently looked in my syslog and discovered that the
  following message shows up a lot daily so I thought I should report
  it:

  /usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset
  negative

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libinput10 1.2.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  1 18:39:08 2016
  InstallationDate: Installed on 2016-05-15 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: libinput
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)

[Lucas Czepaniki]

Actually, I forgot to mention one thing that I've noticed:

When I first switched the alert sound it was to 'drip'. Since then if I try to 
set default again, it'll set the drip sound.
But if I set another like bark or glass or whatever, it'll play the default 
sound + the selected one, and if the selected is the default, it plays the 
default sound + the drip.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1753070

Title:
  Cannot restore default alert sound (Ubuntu bell)

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  After changing the default alert sound in Settings > Sound > Sound
  Effects, I cannot restore the alert sound to the Ubuntu 17.10 default.
  Gnome Control Center version: 1:3.26.2-0ubuntu0.2

  There are five options in the Sound Effects tab: Default, Bark, Drip,
  Glass and Sonar. Selecting Default gives the same sound as Drip, which
  is not the default I had before.

  I think the sound options come from
  /usr/share/sounds/gnome/default/alerts where I found Ogg files for the
  Bark, Drip, Glass and Sonar options (but not for Default). The
  /usr/share/sounds/ubuntu/stereo/bell.ogg seems to have been the
  original default alert sound, to which I cannot restore.

  I am not sure if this is related, but when I opened the Sound Effects
  tab for the first time, the Alert Volume slider was at 0% and grayed
  out. The alert sound was working fine, so I guess that default
  settings from elsewhere were in effect until I started adjusting
  things in this tab and thereby overriding those default settings. I
  cannot restore to that grayed out state either in this tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  3 11:17:54 2018
  InstallationDate: Installed on 2018-02-09 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+subscriptions

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

[Desktop-packages] [Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)

[Lucas Czepaniki]

Having the same issue here.


.-/+oooo+/-.   lucas@bionic 
`:+ss+:`    
  -+ssyy+- OS: Ubuntu 18.04.1 LTS x86_64 
.ossdMMMNyo.   Host: Inspiron 7472 
   /ssshdmmNNmmyNhss/  Kernel: 4.15.0-36-generic 
  +shmydMMMNy+ Uptime: 9 hours, 1 min 
 /hNMMMyhhhmNMMMNh/Packages: 2370 
.dMMMNhsshNMMMd.   Shell: bash 4.4.19 
+hhhyNMMNyyNMMMysss+   Resolution: 1920x1080 
ossyNMMMNyMMhsshmmmhssso   DE: GNOME 3.28.3 
ossyNMMMNyMMhsshmmmhssso   WM: GNOME Shell 
+hhhyNMMNyyNMMMysss+   WM Theme: Adwaita 
.dMMMNhsshNMMMd.   Theme: United-Ubuntu-Dark [GTK2/3] 
 /hNMMMyhhhdNMMMNh/Icons: Paper [GTK2/3] 
  +sdmydy+ Terminal: gnome-terminal 
   /ssshdmmyNhss/  CPU: Intel i7-8550U (8) @ 4.000GHz 
.ossdMMMNyo.   GPU: Intel Integrated Graphics 
  -+syyy+- GPU: NVIDIA GeForce MX150 
`:+ss+:`   Memory: 5533MiB / 15937MiB 
.-/+oooo+/-. 


lucas@bionic:~$ lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
CPU(s):  8
Model name:  Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1753070

Title:
  Cannot restore default alert sound (Ubuntu bell)

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  After changing the default alert sound in Settings > Sound > Sound
  Effects, I cannot restore the alert sound to the Ubuntu 17.10 default.
  Gnome Control Center version: 1:3.26.2-0ubuntu0.2

  There are five options in the Sound Effects tab: Default, Bark, Drip,
  Glass and Sonar. Selecting Default gives the same sound as Drip, which
  is not the default I had before.

  I think the sound options come from
  /usr/share/sounds/gnome/default/alerts where I found Ogg files for the
  Bark, Drip, Glass and Sonar options (but not for Default). The
  /usr/share/sounds/ubuntu/stereo/bell.ogg seems to have been the
  original default alert sound, to which I cannot restore.

  I am not sure if this is related, but when I opened the Sound Effects
  tab for the first time, the Alert Volume slider was at 0% and grayed
  out. The alert sound was working fine, so I guess that default
  settings from elsewhere were in effect until I started adjusting
  things in this tab and thereby overriding those default settings. I
  cannot restore to that grayed out state either in this tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  3 11:17:54 2018
  InstallationDate: Installed on 2018-02-09 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+subscriptions

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

[Desktop-packages] [Bug 1777518] Re: LibreOffice Writer closes upon startup

[Lucas Dantas]

** Description changed:

  Steps to reproduce:
  1 - install lubuntu 18.04, default settings
  2 - in a terminal, type 'sudo apt install libreoffice'
  3 - start libreoffice with 'libreoffice --writer'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Jun 18 17:47:38 2018
  InstallationDate: Installed on 2018-06-13 (5 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ ==
+ 
+ WORKAROUND: Install libreoffice-gtk2 
.
+ Remove libreoffice-gnome and libreoffice-gtk3 
 
.

** Description changed:

  Steps to reproduce:
  1 - install lubuntu 18.04, default settings
  2 - in a terminal, type 'sudo apt install libreoffice'
  3 - start libreoffice with 'libreoffice --writer'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Jun 18 17:47:38 2018
  InstallationDate: Installed on 2018-06-13 (5 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)
  
  ==
  
- WORKAROUND: Install libreoffice-gtk2 
.
- Remove libreoffice-gnome and libreoffice-gtk3 
 
.
+ WORKAROUND:
+ 
+ Install libreoffice-gtk2 .
+ 
+ Remove libreoffice-gnome and libreoffice-gtk3
+ 
+ .

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1777518

Title:
  LibreOffice Writer closes upon startup

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1 - install lubuntu 18.04, default settings
  2 - in a terminal, type 'sudo apt install libreoffice'
  3 - start libreoffice with 'libreoffice --writer'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Jun 18 17:47:38 2018
  InstallationDate: Installed on 2018-06-13 (5 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  ==

  WORKAROUND:

  Install libreoffice-gtk2 .

  Remove libreoffice-gnome and libreoffice-gtk3
  
  .

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

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

[Desktop-packages] [Bug 1777518] Re: LibreOffice Writer closes upon startup

[Lucas Dantas]

The cause appears to be related with the packages libreoffice-gtk3 and 
libreoffice-gnome.
Workaround: install libreoffice-gtk2, and only then, remove libreoffice-gtk3 
and libreoffice-gnome.

$ sudo apt install libreoffice-gtk2 && sudo apt remove libreoffice-gtk3
libreoffice-gnome

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1777518

Title:
  LibreOffice Writer closes upon startup

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1 - install lubuntu 18.04, default settings
  2 - in a terminal, type 'sudo apt install libreoffice'
  3 - start libreoffice with 'libreoffice --writer'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Jun 18 17:47:38 2018
  InstallationDate: Installed on 2018-06-13 (5 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1777518] [NEW] LibreOffice Writer closes upon startup

[Lucas Dantas]

Public bug reported:

Steps to reproduce:
1 - install lubuntu 18.04, default settings
2 - in a terminal, type 'sudo apt install libreoffice'
3 - start libreoffice with 'libreoffice --writer'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Mon Jun 18 17:47:38 2018
InstallationDate: Installed on 2018-06-13 (5 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug bionic i386

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1777518

Title:
  LibreOffice Writer closes upon startup

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1 - install lubuntu 18.04, default settings
  2 - in a terminal, type 'sudo apt install libreoffice'
  3 - start libreoffice with 'libreoffice --writer'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Jun 18 17:47:38 2018
  InstallationDate: Installed on 2018-06-13 (5 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1232928] Re: The wifi regulatory domain is ignored

[Lucas Kocia]

This was requested as an option in Network-manager a while ago (see 
https://bugzilla.gnome.org/show_bug.cgi?id=720331). Current work-around appears 
to be to invoke:
"sudo iw region set AU"
or whatever char code other then AU you wish.

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

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

Title:
  The wifi regulatory domain is ignored

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have edited the /etc/defaults/crda file to configure my system
  regulatory domain to AU.

  When network-manager attaches to the wireless network, this value is not 
sourced. The regulatory domain switches back to US.
  This repeats back and forth, from AU to World to US.

  System detail is:
  root@mythtv:/etc/sysctl.d# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="13.04, Raring Ringtail"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 13.04"
  VERSION_ID="13.04"
  ...

  Here is the output from dmesg when this occurs.

  [   15.579701] cfg80211: Calling CRDA for country: AU
  [   15.583170] cfg80211: Regulatory domain changed to country: AU
  [   15.583173] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   15.583174] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [   15.583175] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583176] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [   15.583177] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [   22.265820] wlan0: authenticate with 94:44:52:a7:ed:d3
  [   22.313771] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [   22.315735] wlan0: authenticated
  [   22.319045] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [   22.320563] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [   22.323544] wlan0: associated
  [   22.323571] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   22.323611] cfg80211: Calling CRDA for country: US
  [   22.325924] cfg80211: Regulatory domain changed to country: US
  [   22.325927] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [   22.325928] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2700 mBm)
  [   22.325930] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
1700 mBm)
  [   22.325931] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325932] cfg80211:   (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325933] cfg80211:   (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [   22.325934] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  ...
  [  216.856143] wlan0: deauthenticating from 94:44:52:a7:ed:d3 by local choice 
(reason=3)
  [  216.884265] cfg80211: Calling CRDA to update world regulatory domain
  [  216.890344] cfg80211: World regulatory domain updated:
  [  216.890350] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.890355] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890359] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890362] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  216.890365] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890368] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  216.890390] cfg80211: Calling CRDA for country: AU
  [  216.895900] cfg80211: Regulatory domain changed to country: AU
  [  216.895904] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  216.895907] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
  [  216.895910] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895913] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 
2300 mBm)
  [  216.895915] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
3000 mBm)
  [  217.982078] wlan0: authenticate with 94:44:52:a7:ed:d3
  [  218.005788] wlan0: send auth to 94:44:52:a7:ed:d3 (try 1/3)
  [  218.006865] wlan0: authenticated
  [  218.010870] wlan0: associate with 94:44:52:a7:ed:d3 (try 1/3)
  [  218.012486] wlan0: RX AssocResp from 94:44:52:a7:ed:d3 (capab=0x11 
status=0 aid=4)
  [  218.015591] wlan0: associated
  [  218.015626] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  218.015680] cfg80211: Calling CRDA for country: US
  [  218.022206] cfg80211: Regulatory domain changed to country: US
  [  218.022210] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  218.022213] cfg80211:   

[Desktop-packages] [Bug 1731468] [NEW] package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intenta

[Lucas Lanús]

Public bug reported:

was automatic, i do nathing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxatracker2:amd64 11.2.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-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 Nov 10 06:18:05 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-96-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-97-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-98-generic, x86_64: installed
DpkgHistoryLog:
 Start-Date: 2017-11-10  06:17:32
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: openjdk-8-jre:amd64 (8u131-b11-2ubuntu1.16.04.3, 
8u151-b12-0ubuntu0.16.04.2), openssl:amd64 (1.0.2g-1ubuntu4.8, 
1.0.2g-1ubuntu4.9), chromium-browser:amd64 (62.0.3202.62-0ubuntu0.16.04.1308, 
62.0.3202.75-0ubuntu0.16.04.1313), chromium-codecs-ffmpeg-extra:amd64 
(62.0.3202.62-0ubuntu0.16.04.1308, 62.0.3202.75-0ubuntu0.16.04.1313), 
libssl-dev:amd64 (1.0.2g-1ubuntu4.8, 1.0.2g-1ubuntu4.9), libssl-doc:amd64 
(1.0.2g-1ubuntu4.8, 1.0.2g-1ubuntu4.9), openjdk-8-jre-headless:amd64 
(8u131-b11-2ubuntu1.16.04.3, 8u151-b12-0ubuntu0.16.04.2), 
chromium-browser-l10n:amd64 (62.0.3202.62-0ubuntu0.16.04.1308, 
62.0.3202.75-0ubuntu0.16.04.1313), libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8, 
1.0.2g-1ubuntu4.9), tzdata:amd64 (2016j-0ubuntu0.16.04, 2017c-0ubuntu0.16.04)
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Broadwell-U Integrated Graphics 
[1179:f904]
InstallationDate: Installed on 2017-08-07 (94 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA Satellite E45t-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=a6f583cf-18ee-481e-bd9d-9fc0a70d5f30 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: mesa
Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: CA10CU
dmi.board.vendor: TOSHIBA
dmi.board.version: 2.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.00:bd11/05/2014:svnTOSHIBA:pnSatelliteE45t-B:pvrPSPNCU-004002:rvnTOSHIBA:rnCA10CU:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite E45t-B
dmi.product.version: PSPNCU-004002
dmi.sys.vendor: TOSHIBA
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Nov  9 20:03:47 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1145 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1731468

Title:
  package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade:
  El paquete está en un estado grave de inconsistencia - debe
  reinstalarlo  antes de intentar su configuración.

Status in mesa package in Ubuntu:
  New

Bug description:
  was automatic, i do nathing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  

[Desktop-packages] [Bug 1730149] Re: No option to set a 2nd display as mirrored in Ubuntu 17.10

[Lucas Cofresi]

This turns out not to be a bug, but simply a different (and, it turns
out, a much improved) interface for the same purposes. I apologize for
the haste (also, I could not find a way to simply rescind it).

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

** Converted to question:
   
https://answers.launchpad.net/ubuntu/+source/gnome-control-center/+question/660501

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1730149

Title:
  No option to set a 2nd display as mirrored in Ubuntu 17.10

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Up to rel 17.04, we were able to choose the mode for a second display
  as either "mirrored" or "extended". With rel 17.10, it always defaults
  to "extended".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730149/+subscriptions

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

[Desktop-packages] [Bug 1730149] [NEW] No option to set a 2nd display as mirrored in Ubuntu 17.10

[Lucas Cofresi]

Public bug reported:

Up to rel 17.04, we were able to choose the mode for a second display as
either "mirrored" or "extended". With rel 17.10, it always defaults to
"extended".

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1730149

Title:
  No option to set a 2nd display as mirrored in Ubuntu 17.10

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Up to rel 17.04, we were able to choose the mode for a second display
  as either "mirrored" or "extended". With rel 17.10, it always defaults
  to "extended".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730149/+subscriptions

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

[Desktop-packages] [Bug 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable

[Lucas Magasweran]

This has been fixed and merged upstream in nm-applet/network-manager
1.4.2.

https://bugzilla.gnome.org/show_bug.cgi?id=763937#c14

Ubuntu 17.04 has 1.4.4. Is it possible to backport this to 16.04 LTS?

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

Title:
  DHCP settings for network manager shared connection are hard-coded
  source, should be editable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 10.04, but it's in all versions.
  2) any version of network manager
  3) I want to be able to change the DHCP settings for a shared network 
connection
  4) YOUR OPERATING SYSTEM WON'T LET ME!

  The file nm-device.c contains this line:

  nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /*
  10.42.43.1 */

  hard-coding DHCP settings that should obviously be editable by the
  user is a TERRIBLE IDEA.  PLEASE FIX.

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

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

[Desktop-packages] [Bug 1717272] Re: HiDPI settings reset on logout

[Lucas Czekaj]

Running Ubuntu Budgie 17.10 Beta 1 with Gnome 3.26 and the issue is
still there.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1717272

Title:
  HiDPI settings reset on logout

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  When logging in to my XPS 13 (9360) on 17.10, the only thing that is
  reasonably (200%) scaled is the sidebar. Top bar, windows, and fonts
  are all unscaled and TINY.

  - I'll go to Control Centre, Devices, Displays, and see that scaling is set 
to 200%.
  - I'll then change the scaling to 100%, and hit apply and confirm. At this 
point, windows are scaled to 200%.
  - I need to change the scaling to 100% AGAIN. Now everything is 100%, and 
therefore tiny
  - I then change the scaling to 200%, hit apply and confirm, which does barely 
anything
  - I then need to set scaling to 200% AGAIN, hit apply and confirm, and only 
*then* everything is properly scaled.

  I need to do this every time I log back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 16:33:30 2017
  ExecutablePath: /usr/bin/gnome-control-center
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717272/+subscriptions

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

[Desktop-packages] [Bug 1712715] [NEW] Row filter not working for dates

[Lucas Clemente Vella]

Public bug reported:

Trying to select rows by year in the first column of the attached file
hides all lines, instead of keeping the lines matching the selected
filter criteria.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libreoffice-calc 1:5.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17
Uname: Linux 4.10.0-32-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Aug 23 23:26:09 2017
InstallationDate: Installed on 2015-07-05 (780 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to zesty on 2017-04-30 (115 days ago)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "File triggering the bug"
   
https://bugs.launchpad.net/bugs/1712715/+attachment/4937787/+files/BUG_AUTO_FILTRO.ods

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1712715

Title:
  Row filter not working for dates

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Trying to select rows by year in the first column of the attached file
  hides all lines, instead of keeping the lines matching the selected
  filter criteria.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-calc 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17
  Uname: Linux 4.10.0-32-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug 23 23:26:09 2017
  InstallationDate: Installed on 2015-07-05 (780 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to zesty on 2017-04-30 (115 days ago)

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

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

[Desktop-packages] [Bug 1710319] [NEW] package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: package evince-common is not ready for configuration cannot configure (current status 'half-in

[Michael Lucas]

Public bug reported:

This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @ 2.2GHz.

Not sure what the deal is actually since the update status shows up to
date.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: evince-common 3.18.2-1ubuntu4.1
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Aug 11 21:31:05 2017
DpkgHistoryLog:
 Start-Date: 2017-08-11  21:30:43
 Requested-By: lucastoshi (1000)
 Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), 
update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 
(1:16.04.7, 1:16.04.8)
DuplicateSignature:
 package:evince-common:3.18.2-1ubuntu4.1
 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
 Rebuilding /usr/share/applications/bamf-2.index...
 dpkg: error processing package evince-common (--configure):
  package evince-common is not ready for configuration
ErrorMessage: package evince-common is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-12-10 (244 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: evince
Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: 
package evince-common is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1710319

Title:
  package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade:
  package evince-common is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in evince package in Ubuntu:
  New

Bug description:
  This is in Ubuntu 16.04 LTS on my 64bit Intel Celeron CPU 900 @
  2.2GHz.

  Not sure what the deal is actually since the update status shows up to
  date.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: evince-common 3.18.2-1ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 11 21:31:05 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-11  21:30:43
   Requested-By: lucastoshi (1000)
   Upgrade: update-manager-core:amd64 (1:16.04.7, 1:16.04.8), 
update-manager:amd64 (1:16.04.7, 1:16.04.8), python3-update-manager:amd64 
(1:16.04.7, 1:16.04.8)
  DuplicateSignature:
   package:evince-common:3.18.2-1ubuntu4.1
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package evince-common (--configure):
package evince-common is not ready for configuration
  ErrorMessage: package evince-common is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-12-10 (244 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: evince
  Title: package evince-common 3.18.2-1ubuntu4.1 failed to install/upgrade: 
package evince-common is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1675334] Re: nvidia 375.39 package makes weird screen appearance on resume

[Lucas Partridge]

Reverting to the previous NVidia 340.102 proprietary driver also fixes
it for me - i.e., graphics appear normal after waking from suspend.

I'm also using ubuntu 16.04 with all the latest apt-get updates.

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] 
(rev a1)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1675334

Title:
  nvidia 375.39 package makes weird screen appearance on resume

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed

Bug description:
  I recently received new proprietary nvidia driver package (nvidia 375.39) and 
my computer screen makes very weird apparance, rainbow-like frame around 
windows upon resume. 
  It is very difficult to explain that situation, additional lines on all 
window borders and makes window buttons in upper window frame very invisible, 
attached in this bug report.

  I am using NVIDIA GeForce 560 Ti graphics card and I had not met such 
experience before.
  My system is Ubuntu 16.04 (Xenial) with all latest patches applied.

  Here's summary of my graphics environment:

  lspci | grep VGA
  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  sudo lshw -C video
*-display   
 description: VGA compatible controller
 product: GF114 [GeForce GTX 560 Ti]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nvidia latency=0
 resources: irq:32 memory:f800-f9ff memory:d000-d7ff 
memory:dc00-dfff ioport:af00(size=128) memory:fa00-fa07

  I temporarily reverted my driver to older 340.102 proprietary and it
  is no problem for sleep / resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1675334/+subscriptions

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

[Desktop-packages] [Bug 1675334] Re: nvidia 375.39 package makes weird screen appearance on resume

[Lucas Partridge]

This might be a duplicate of https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-375/+bug/1667158 ...?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1675334

Title:
  nvidia 375.39 package makes weird screen appearance on resume

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed

Bug description:
  I recently received new proprietary nvidia driver package (nvidia 375.39) and 
my computer screen makes very weird apparance, rainbow-like frame around 
windows upon resume. 
  It is very difficult to explain that situation, additional lines on all 
window borders and makes window buttons in upper window frame very invisible, 
attached in this bug report.

  I am using NVIDIA GeForce 560 Ti graphics card and I had not met such 
experience before.
  My system is Ubuntu 16.04 (Xenial) with all latest patches applied.

  Here's summary of my graphics environment:

  lspci | grep VGA
  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  sudo lshw -C video
*-display   
 description: VGA compatible controller
 product: GF114 [GeForce GTX 560 Ti]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nvidia latency=0
 resources: irq:32 memory:f800-f9ff memory:d000-d7ff 
memory:dc00-dfff ioport:af00(size=128) memory:fa00-fa07

  I temporarily reverted my driver to older 340.102 proprietary and it
  is no problem for sleep / resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1675334/+subscriptions

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

[Desktop-packages] [Bug 1675334] Re: nvidia 375.39 package makes weird screen appearance on resume

[Lucas Partridge]

I've had a similar problem since upgrading to NVidia 375.39, albeit
slightly different appearance after waking from suspend. See screenshot.

** Attachment added: "Screenshot from 2017-03-23 21-26-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1675334/+attachment/4843784/+files/Screenshot%20from%202017-03-23%2021-26-42.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1675334

Title:
  nvidia 375.39 package makes weird screen appearance on resume

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed

Bug description:
  I recently received new proprietary nvidia driver package (nvidia 375.39) and 
my computer screen makes very weird apparance, rainbow-like frame around 
windows upon resume. 
  It is very difficult to explain that situation, additional lines on all 
window borders and makes window buttons in upper window frame very invisible, 
attached in this bug report.

  I am using NVIDIA GeForce 560 Ti graphics card and I had not met such 
experience before.
  My system is Ubuntu 16.04 (Xenial) with all latest patches applied.

  Here's summary of my graphics environment:

  lspci | grep VGA
  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  sudo lshw -C video
*-display   
 description: VGA compatible controller
 product: GF114 [GeForce GTX 560 Ti]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:01:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nvidia latency=0
 resources: irq:32 memory:f800-f9ff memory:d000-d7ff 
memory:dc00-dfff ioport:af00(size=128) memory:fa00-fa07

  I temporarily reverted my driver to older 340.102 proprietary and it
  is no problem for sleep / resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1675334/+subscriptions

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

Re: [Desktop-packages] [Bug 1662440] Re: Unable to import FNMT certificates in chromium or chrome

[Alvaro de Lucas]

Thank you very much. That has a lot of sense...Kind regards

El Viernes 10 de febrero de 2017 16:45, Alberto Salvia Novella 
 escribió:
 

 Bottom-line is this importance is relative to the overall Ubuntu, not
specifically to Chromium. The Chromium project could have a different
importance, set in the report you have filled upstream.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to import FNMT certificates in chromium or chrome

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Hi,
  there's an "unknown error" when you try to import certificates from the FNMT 
on Chrome or derivatives.
  There's an error when you try to import the personal certificate, but also 
when you try to import the CA certificates from the FNMT.

  Here you can download the AC certificates: 
https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish)
  Direct links:
  
https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer
  2nd class: 
https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
  Uname: Linux 4.8.8-040808-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-HDMI-A-1:
  enabled: enabled
  dpms: On
  status: connected
  edid-base64: 
AP///wA4o0pnAQEBAQ0TAQOgLx54Kg61qlE3qyUUUFS/74CBwIFAgYCLwJUAkECzAHFPITmQMGIaJ0AYsDZA2igRAAAc/QA4Sx9TEQAKICAgICAg/ABQMjIxVwogICAgICAg/wA5MzEwMDk0NE5CCiAgASECAxtiIwl/B4MBAABnAwwAIACALUMBEATiAA8AADYAQOhjAAAaGh0AgFHQHCBAgDUAQIRjAAAclQ==
  modes: 1680x1050 1920x1080 1920x1080 1400x1050 1280x1024 1280x1024 1440x900 
1280x960 1360x768 1152x864 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
  enabled: disabled
  dpms: Off
  status: connected
  edid-base64: 
AP///wAGr50hAAAVAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYuCSAwHA4IEAwZDYAfdYQAAAYAgAMM/kKPGQfFCJuICAgAMs=
  modes: 1920x1080 1920x1080
  Date: Tue Feb  7 08:12:37 2017
  Desktop-Session:
  'ubuntu'
  '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
  
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
  
  Env:
  'None'
  'None'
  InstallationDate: Installed on 2016-08-01 (189 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Load-Avg-1min: 1.07
  Load-Processes-Running-Percent:  0.1%
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1966
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.49
  dmi.chassis.asset.tag: 5CG35023TQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd10/03/2013:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088410305B0620100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088410305B0620100
  dmi.sys.vendor: Hewlett-Packard
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to import FNMT certificates in chromium or chrome

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Hi,
  there's an "unknown error" when you try to import certificates from the FNMT 
on Chrome or derivatives.
  There's an error when you try to import the personal certificate, but also 
when you try to import the CA certificates from the 

Re: [Desktop-packages] [Bug 1662440] Re: Unable to import FNMT certificates in chromium or chrome

[Alvaro de Lucas]

You're right. You have another browsers... and certificates work on
firefox. I ment is not low priority for Chromium developers...Several
spanish institutional pages have outdated certificates. Mayte that's
also the problem in this page...Kind regards

El Jueves 9 de febrero de 2017 18:50, Alberto Salvia Novella 
 escribió:
 

 When I click on the link it says "you do not have permission to view the
requested page". Any idea why is that?

And the importance is low because Chromium isn't core software, and
certificates aren't a core functionality of it
(https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Importance).

** Changed in: chromium-browser (Ubuntu)
      Status: Incomplete => Triaged

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to import FNMT certificates in chromium or chrome

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Hi,
  there's an "unknown error" when you try to import certificates from the FNMT 
on Chrome or derivatives.
  There's an error when you try to import the personal certificate, but also 
when you try to import the CA certificates from the FNMT.

  Here you can download the AC certificates: 
https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish)
  Direct links:
  
https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer
  2nd class: 
https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
  Uname: Linux 4.8.8-040808-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-HDMI-A-1:
  enabled: enabled
  dpms: On
  status: connected
  edid-base64: 
AP///wA4o0pnAQEBAQ0TAQOgLx54Kg61qlE3qyUUUFS/74CBwIFAgYCLwJUAkECzAHFPITmQMGIaJ0AYsDZA2igRAAAc/QA4Sx9TEQAKICAgICAg/ABQMjIxVwogICAgICAg/wA5MzEwMDk0NE5CCiAgASECAxtiIwl/B4MBAABnAwwAIACALUMBEATiAA8AADYAQOhjAAAaGh0AgFHQHCBAgDUAQIRjAAAclQ==
  modes: 1680x1050 1920x1080 1920x1080 1400x1050 1280x1024 1280x1024 1440x900 
1280x960 1360x768 1152x864 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
  enabled: disabled
  dpms: Off
  status: connected
  edid-base64: 
AP///wAGr50hAAAVAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYuCSAwHA4IEAwZDYAfdYQAAAYAgAMM/kKPGQfFCJuICAgAMs=
  modes: 1920x1080 1920x1080
  Date: Tue Feb  7 08:12:37 2017
  Desktop-Session:
  'ubuntu'
  '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
  
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
  
  Env:
  'None'
  'None'
  InstallationDate: Installed on 2016-08-01 (189 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Load-Avg-1min: 1.07
  Load-Processes-Running-Percent:  0.1%
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1966
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.49
  dmi.chassis.asset.tag: 5CG35023TQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd10/03/2013:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088410305B0620100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088410305B0620100
  dmi.sys.vendor: Hewlett-Packard
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to 

[Desktop-packages] [Bug 1663316] [NEW] package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Lucas Kenji]

Public bug reported:

failed to install/upgrade: subprocess installed post-installation script
returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libglib2.0-cil 2.12.10-5
ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
Date: Wed Feb  1 22:51:35 2017
DpkgHistoryLog:
 Start-Date: 2017-02-01  22:49:30
 Commandline: aptdaemon role='role-remove-packages' sender=':1.189'
 Remove: libjcommon-java:i386 (1.0.16-3), libfreehep-graphicsio-pdf-java:i386 
(2.1.1+dfsg-1), geogebra:i386 (4.0.34.0+dfsg1-2), libjas-java:i386 
(2.5.4408-1), mathpiper:i386 (0.81f+svn4469+dfsg3-3), libjfreechart-java:i386 
(1.0.13-5), libcommons-math-java:i386 (2.2-3), libhamcrest-java:i386 (1.3-4), 
libcollections15-java:i386 (4.01+ds1-1), libjfugue-java:i386 (4.0.3-3), 
libfreehep-graphicsio-svg-java:i386 (2.1.1-3), libfreehep-xml-java:i386 
(2.1.2+dfsg1-3), junit4:i386 (4.11-2)
DuplicateSignature: package:libglib2.0-cil:2.12.10-5:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-04-13 (1397 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.14
SourcePackage: gtk-sharp2
Title: package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-04-23 (1022 days ago)

** Affects: gtk-sharp2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk-sharp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1663316

Title:
  package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in gtk-sharp2 package in Ubuntu:
  New

Bug description:
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-cil 2.12.10-5
  ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Wed Feb  1 22:51:35 2017
  DpkgHistoryLog:
   Start-Date: 2017-02-01  22:49:30
   Commandline: aptdaemon role='role-remove-packages' sender=':1.189'
   Remove: libjcommon-java:i386 (1.0.16-3), libfreehep-graphicsio-pdf-java:i386 
(2.1.1+dfsg-1), geogebra:i386 (4.0.34.0+dfsg1-2), libjas-java:i386 
(2.5.4408-1), mathpiper:i386 (0.81f+svn4469+dfsg3-3), libjfreechart-java:i386 
(1.0.13-5), libcommons-math-java:i386 (2.2-3), libhamcrest-java:i386 (1.3-4), 
libcollections15-java:i386 (4.01+ds1-1), libjfugue-java:i386 (4.0.3-3), 
libfreehep-graphicsio-svg-java:i386 (2.1.1-3), libfreehep-xml-java:i386 
(2.1.2+dfsg1-3), junit4:i386 (4.11-2)
  DuplicateSignature: package:libglib2.0-cil:2.12.10-5:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-13 (1397 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (1022 days ago)

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

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

[Desktop-packages] [Bug 1662440] Re: Unable to import FNMT certificates in chromium or chrome

[Alvaro de Lucas]

Reported here:
https://bugs.chromium.org/p/chromium/issues/detail?id=690340

I think importance shouldn't be low: you can't use the browser if you require 
your certificates.
Thank you very much in advance
Kind regards

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to import FNMT certificates in chromium or chrome

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  there's an "unknown error" when you try to import certificates from the FNMT 
on Chrome or derivatives.
  There's an error when you try to import the personal certificate, but also 
when you try to import the CA certificates from the FNMT.

  Here you can download the AC certificates: 
https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish)
  Direct links:
  
https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer
  2nd class: 
https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
  Uname: Linux 4.8.8-040808-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wA4o0pnAQEBAQ0TAQOgLx54Kg61qlE3qyUUUFS/74CBwIFAgYCLwJUAkECzAHFPITmQMGIaJ0AYsDZA2igRAAAc/QA4Sx9TEQAKICAgICAg/ABQMjIxVwogICAgICAg/wA5MzEwMDk0NE5CCiAgASECAxtiIwl/B4MBAABnAwwAIACALUMBEATiAA8AADYAQOhjAAAaGh0AgFHQHCBAgDUAQIRjAAAclQ==
   modes: 1680x1050 1920x1080 1920x1080 1400x1050 1280x1024 1280x1024 1440x900 
1280x960 1360x768 1152x864 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
   enabled: disabled
   dpms: Off
   status: connected
   edid-base64: 
AP///wAGr50hAAAVAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYuCSAwHA4IEAwZDYAfdYQAAAYAgAMM/kKPGQfFCJuICAgAMs=
   modes: 1920x1080 1920x1080
  Date: Tue Feb  7 08:12:37 2017
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-08-01 (189 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Load-Avg-1min: 1.07
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1966
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.49
  dmi.chassis.asset.tag: 5CG35023TQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd10/03/2013:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088410305B0620100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088410305B0620100
  dmi.sys.vendor: Hewlett-Packard
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1662440] [NEW] Unable to import FNMT certificates in chromium or chrome

[Alvaro de Lucas]

Public bug reported:

Hi,
there's an "unknown error" when you try to import certificates from the FNMT on 
Chrome or derivatives.
There's an error when you try to import the personal certificate, but also when 
you try to import the CA certificates from the FNMT.

Here you can download the AC certificates: 
https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish)
Direct links:
https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer
2nd class: 
https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer
...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
Uname: Linux 4.8.8-040808-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
DRM.card0-HDMI-A-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wA4o0pnAQEBAQ0TAQOgLx54Kg61qlE3qyUUUFS/74CBwIFAgYCLwJUAkECzAHFPITmQMGIaJ0AYsDZA2igRAAAc/QA4Sx9TEQAKICAgICAg/ABQMjIxVwogICAgICAg/wA5MzEwMDk0NE5CCiAgASECAxtiIwl/B4MBAABnAwwAIACALUMBEATiAA8AADYAQOhjAAAaGh0AgFHQHCBAgDUAQIRjAAAclQ==
 modes: 1680x1050 1920x1080 1920x1080 1400x1050 1280x1024 1280x1024 1440x900 
1280x960 1360x768 1152x864 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-eDP-1:
 enabled: disabled
 dpms: Off
 status: connected
 edid-base64: 
AP///wAGr50hAAAVAQSQJhV4AsiVnldUkiYPUFQBAQEBAQEBAQEBAQEBAQEBFDeAwHA4IEAwZDYAfdYQAAAYuCSAwHA4IEAwZDYAfdYQAAAYAgAMM/kKPGQfFCJuICAgAMs=
 modes: 1920x1080 1920x1080
Date: Tue Feb  7 08:12:37 2017
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2016-08-01 (189 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Load-Avg-1min: 1.07
Load-Processes-Running-Percent:   0.1%
MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1966
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 93.49
dmi.chassis.asset.tag: 5CG35023TQ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd10/03/2013:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088410305B0620100:rvnHewlett-Packard:rn1966:rvrKBCVersion93.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 088410305B0620100
dmi.sys.vendor: Hewlett-Packard
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1662440

Title:
  Unable to import FNMT certificates in chromium or chrome

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,
  there's an "unknown error" when you try to import certificates from the FNMT 
on Chrome or derivatives.
  There's an error when you try to import the personal certificate, but also 
when you try to import the CA certificates from the FNMT.

  Here you can download the AC certificates: 
https://www.sede.fnmt.gob.es/descargas/certificados-raiz-de-la-fnmt (spanish)
  Direct links:
  
https://www.sede.fnmt.gob.es/documents/10445900/10526749/AC_Raiz_FNMT-RCM_SHA256.cer
  2nd class: 
https://www.sede.fnmt.gob.es/documents/10445900/10526749/FNMTClase2CA.cer
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 55.0.2883.87-0ubuntu0.16.04.1263
  Uname: Linux 4.8.8-040808-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 

[Desktop-packages] [Bug 1661994] [NEW] Xdiagnistics

[LUCAS]

Public bug reported:

Report sent

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Feb  5 18:34:32 2017
DistUpgraded: 2016-08-01 11:52:39,263 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type))
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
   Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
MachineType: Hewlett-Packard HP Compaq dc5750 Microtower
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=5c6c0f08-be2e-4bbf-8e22-05238972f64e ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-01 (188 days ago)
dmi.bios.date: 01/25/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786E3 v02.10
dmi.board.name: 0A64h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC72544ZW
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:svnHewlett-Packard:pnHPCompaqdc5750Microtower:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq dc5750 Microtower
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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: Mon Aug  1 02:46:56 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
 inputHP WMI hotkeys   KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1661994

Title:
   Xdiagnistics

Status in xorg package in Ubuntu:
  New

Bug description:
  Report sent

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Feb  5 18:34:32 2017
  DistUpgraded: 2016-08-01 11:52:39,263 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
 Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) 
[103c:280b]
  MachineType: Hewlett-Packard HP Compaq dc5750 Microtower
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=5c6c0f08-be2e-4bbf-8e22-05238972f64e ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (188 days ago)
  dmi.bios.date: 01/25/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.10
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 

[Desktop-packages] [Bug 1659300] [NEW] File Conflict dialogue resizes depending on thumbnail size

[Lucas Czech]

Public bug reported:

(wishlist)

When copying/moving files and there is a name conflict, the dialogue
shows some information about the two conflicting files, e.g., name,
size, modification time, and an icon (for most file types) or thumbnail
(for images or videos).

This thumbnail uses the aspect ratio of the images/video, which might be
different for different files in the directory. Thus, when there are
multiple conflicting files in one copy/move operation, the size of the
File Conflict dialogue can change for each conflict. This means that the
buttons (e.g., "Cancel", "Skip", "Replace") change their position.

Users that resolve conflicts by clicking those buttons then have to
constantly move the mouse cursor even if they want to hit e.g. "Skip"
for some files in a row.

This problem can be solved by fixing the space taken up by the
thumbnails, that is, always use the maximum size. Of course, the
displayed thumbnail does not need to change (it should still use the
correct aspect ratio) - it just needs to be embedded in a background-
coloured box of fixed size.

Ubuntu 14.04 and 16.04

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1659300

Title:
  File Conflict dialogue resizes depending on thumbnail size

Status in nautilus package in Ubuntu:
  New

Bug description:
  (wishlist)

  When copying/moving files and there is a name conflict, the dialogue
  shows some information about the two conflicting files, e.g., name,
  size, modification time, and an icon (for most file types) or
  thumbnail (for images or videos).

  This thumbnail uses the aspect ratio of the images/video, which might
  be different for different files in the directory. Thus, when there
  are multiple conflicting files in one copy/move operation, the size of
  the File Conflict dialogue can change for each conflict. This means
  that the buttons (e.g., "Cancel", "Skip", "Replace") change their
  position.

  Users that resolve conflicts by clicking those buttons then have to
  constantly move the mouse cursor even if they want to hit e.g. "Skip"
  for some files in a row.

  This problem can be solved by fixing the space taken up by the
  thumbnails, that is, always use the maximum size. Of course, the
  displayed thumbnail does not need to change (it should still use the
  correct aspect ratio) - it just needs to be embedded in a background-
  coloured box of fixed size.

  Ubuntu 14.04 and 16.04

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

Please find attached the the log file. Remember to start cups-browsed
again via sudo systemctl start cups-browsed so that you are connected to
the cups server once more.

The delayed shutdown always happens when I am connected to the network
that has cups printers. When I am not connected to any cups server it is
fine.


** Attachment added: "cups-browsed.log"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778984/+files/cups-browsed.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

** Attachment added: "lpstat"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778778/+files/lpstat

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

** Attachment added: "cups-browsed.service"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778776/+files/cups-browsed.service

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

** Attachment added: "cups-browsed.config"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778775/+files/cups-browsed.config

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

Sorry for the spam. I couldn't figure out how to attach multiple files.

** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778777/+files/error_log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

** Attachment added: "cups.service"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778774/+files/cups.service

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

Hello,

please find attached the desired files. Unfortunately, there is no
/var/log/cups/cups-browsed_log, but only a access_log. I attached this
one instead in case it helps.

I never restarted cups, only the computer itself to test it.


** Attachment added: "access_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+attachment/4778773/+files/access_log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

Hi,

thank you very much for the update. Unfortunately, it doesn't work for
me either. I just tested it an hour ago.

cups-filters:
  Installed: 1.8.3-2ubuntu3.2
  Candidate: 1.8.3-2ubuntu3.2
  Version table:
 *** 1.8.3-2ubuntu3.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1.8.3-2ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 1.8.3-2ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


Please let me know if you need any more information. 

Best, 
Lucas

** Tags removed: verification-needed
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
    Installed: 1.8.3-2ubuntu3.1
    Candidate: 1.8.3-2ubuntu3.1
    Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

  [Impact]

  On many machines the shutdown will take unusually long, typically the
  90-second timeout after which a hanging process gets killed. One case
  where this easily happens is if you have a remote CUPS server sharing
  printers which your local cups-browsed picks up and your local CUPS is
  not listening on localhost:631 (usually when it does not share
  printers). cups-browsed also tries to access the local cupsd on
  localhost:631 and hangs.

  [Testcase]

  Take two machines in one local network (can also be VMs), one being a
  CUPS server with at least one print queue being shared, another a
  client with CUPS and cups-browsed running but not sharing local queues
  and not listening on localhost:631. It picks up the server's queues
  but when trying to shut down cups-browsed, cups-browsed hangs. The
  fixed package (cups-filters 1.8.3-2ubuntu3.2) solves this problem as
  its cups-browsed shuts down correctly.

  [Regression Potential]

  The patch is not small, but it does only small and simple changes, not
  replacing big bunches of code by other big bunches of code, so the
  regression potential is rather low. The changes in the patch are also
  all backported from the working upstream code of cups-filters.

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

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

[Desktop-packages] [Bug 1638986] [NEW] cups/cups-browsed causing delay in shutdown (16.04)

[Lucas Liebenwein]

Public bug reported:

Description:Ubuntu 16.04.1 LTS
Release:16.04

cups-filters:
  Installed: 1.8.3-2ubuntu3.1
  Candidate: 1.8.3-2ubuntu3.1
  Version table:
 *** 1.8.3-2ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.8.3-2ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Bug description:

I have updated to the latest cups-filters version to fix the bug as
described by bug report #1579905 but I still get that Ubuntu takes very
long to shutdown.

For now, I have simply disabled cups-browser and I manually start it up
every time I need to print something.

It is probably related to

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

as Till has described in #1579905. I tried to download and compile the
upstream version at BZR as suggested for Debian but I ended up not being
able to print anymore and instead went back to the current version in
the package distribution.

Hopefully, there is an easy fix for Ubuntu 16.04 as well.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1638986

Title:
  cups/cups-browsed causing delay in shutdown (16.04)

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  cups-filters:
Installed: 1.8.3-2ubuntu3.1
Candidate: 1.8.3-2ubuntu3.1
Version table:
   *** 1.8.3-2ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.3-2ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Bug description:

  I have updated to the latest cups-filters version to fix the bug as
  described by bug report #1579905 but I still get that Ubuntu takes
  very long to shutdown.

  For now, I have simply disabled cups-browser and I manually start it
  up every time I need to print something.

  It is probably related to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637

  as Till has described in #1579905. I tried to download and compile the
  upstream version at BZR as suggested for Debian but I ended up not
  being able to print anymore and instead went back to the current
  version in the package distribution.

  Hopefully, there is an easy fix for Ubuntu 16.04 as well.

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

Totally my fault! Now I remember, when I first installed 16.04 I removed
it as it was chewing up CPU time and battery and it was not clear to me
for what it is needed. Now I know what I need it for! Sorry to have
burdened you. It is well behaved now though.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1617107/+attachment/4728445/+files/dpkg.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

yup! that did it, after reboot. you are the best!

Strange that this was not installed by default with 16.04. As I said, I
did a clean install. At any rate. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

by the way, thanks for your help on this! just in case, some more data
points:

sudo gvfs-mount  ftp://ftp.debian.net
Error mounting location: volume doesn't implement mount

nad in case it matters:

mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

just in case

sudo gvfs-mount  ftp://ftp.debian.net
Error mounting location: volume doesn't implement mount

in case it matters:

mount | grep gvfs
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

gvfs-mount ftp://ftp.debian.net
Error mounting location: Location is not mountable

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] Re: nautilus does not recognize any server type

[lucas]

That is what I was afraid of.

dmesg -w does not report anything new when I get the error message. Any
other way of reporting syslog that would be helpful?


dpkg -l |grep gvfs
ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1 
amd64userspace virtual filesystem - GIO 
module
ii  gvfs-bin1.28.2-1ubuntu1~16.04.1 
amd64userspace virtual filesystem - binaries
ii  gvfs-common 1.28.2-1ubuntu1~16.04.1 
all  userspace virtual filesystem - common 
data files
ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1 
amd64userspace virtual filesystem - servers
ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1 
amd64userspace virtual filesystem - fuse 
server
ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1 
amd64userspace virtual filesystem - private 
libraries

PS: I did install sshfs after the new install to no avail. Not sure that
matters. Also tested if this is a permission issue by running the same
as guest user. Same problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1617107] [NEW] nautilus does not recognize any server type

[lucas]

Public bug reported:

Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
with ssh, sftp, nsf, dav, really anything I can think of gives "This
file server type is not recognized." Error message appears as soon as :
is entered, e.g. "ssh:".

ssh and sftp work just fine from the command line.

using nautilus version "Files 3.14.3"

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1617107

Title:
  nautilus does not recognize any server type

Status in nautilus package in Ubuntu:
  New

Bug description:
  Have a fresh Ubuntu 16.04 LTS install. "Connect to Server" in nautilus
  with ssh, sftp, nsf, dav, really anything I can think of gives "This
  file server type is not recognized." Error message appears as soon as
  : is entered, e.g. "ssh:".

  ssh and sftp work just fine from the command line.

  using nautilus version "Files 3.14.3"

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Andrew Lucas]

Hi all,

I've been running Xubuntu 16.04 since about Feb 2016, and this has been
an issue for ages.

Prior to seeing the fix for Ctrl+Alt+F1 -> Ctrl+Alt+F7 (which works),
the fix for me was navigating to Chrome web browser, logging into
Netflix, and playing a video. I've no idea why, and I'm not proposing
this as a fix for anyone (clearly the above combination is
quicker/easier), but I'm hoping it might help pin down the cause.

I don't have the technical skills to contribute a patch myself, but I
was prompted to comment because I'm a bit worried that we're over a
month past a release and seeing this bug - which has been around for 2/3
months before release - on an LTS, and still we don't even have it
assigned.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in X.Org X server:
  Confirmed
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Cursor is visible at unlock screen either after returning from suspend
  or just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1568604/+subscriptions

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

[Desktop-packages] [Bug 1584848] [NEW] package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package libglib2.0-cil is not ready for configuration cannot configure (current status `half-installe

[Lucas Kenji]

Public bug reported:

package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package
libglib2.0-cil is not ready for configuration  cannot configure (current
status `half-installed')

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libglib2.0-cil 2.12.10-5
ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
Uname: Linux 3.13.0-85-generic i686
ApportVersion: 2.14.1-0ubuntu3.20
Architecture: i386
Date: Mon May 23 12:36:31 2016
DuplicateSignature: package:libglib2.0-cil:2.12.10-5:package libglib2.0-cil is 
not ready for configuration  cannot configure (current status `half-installed')
ErrorMessage: package libglib2.0-cil is not ready for configuration  cannot 
configure (current status `half-installed')
InstallationDate: Installed on 2013-04-13 (1135 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.13
SourcePackage: gtk-sharp2
Title: package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package 
libglib2.0-cil is not ready for configuration  cannot configure (current status 
`half-installed')
UpgradeStatus: Upgraded to trusty on 2014-04-23 (760 days ago)

** Affects: gtk-sharp2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk-sharp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1584848

Title:
  package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package
  libglib2.0-cil is not ready for configuration  cannot configure
  (current status `half-installed')

Status in gtk-sharp2 package in Ubuntu:
  New

Bug description:
  package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package
  libglib2.0-cil is not ready for configuration  cannot configure
  (current status `half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-cil 2.12.10-5
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic i686
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: i386
  Date: Mon May 23 12:36:31 2016
  DuplicateSignature: package:libglib2.0-cil:2.12.10-5:package libglib2.0-cil 
is not ready for configuration  cannot configure (current status 
`half-installed')
  ErrorMessage: package libglib2.0-cil is not ready for configuration  cannot 
configure (current status `half-installed')
  InstallationDate: Installed on 2013-04-13 (1135 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: gtk-sharp2
  Title: package libglib2.0-cil 2.12.10-5 failed to install/upgrade: package 
libglib2.0-cil is not ready for configuration  cannot configure (current status 
`half-installed')
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (760 days ago)

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

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

[Desktop-packages] [Bug 1574617] Re: External monitor keeps going blank

[Lucas Corte Real Saldanha]

I found a way to reproduce it. It happens when the mouse pointer jumps
between the two displayport monitors. If I keep moving the mouse between
the two monitors it happens each couple of seconds.

If I disable the vga monitor. The problem is gone...

I have no idea of what is happening but at least know that disabling the
vga monitor solves the issue for me.

Hopefully someone will find out what is happening.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1574617

Title:
  External monitor keeps going blank

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have an external monitor connected to my Thinkpad as an extended desktop. 
On Ubuntu 15.10 it worked fine but in 16.04 it 'crashes' under certain 
conditions.
  When you move mouse from the external monitor across and hover over the 
laptop screen the external monitor blanks out. It sometimes 'comes back to 
life' after a few seconds. The monitor also sometimes drops out of it's own 
accord and appears to be random.
  The laptop isn't disconnecting from the monitor as if you take a screenshot 
you'll still see your extended desktop with windows open but the monitor is no 
longer detecting a signal from the laptop.
  To 'fix' either:
  1. Run startx
  2. Change something in the display menu (ie. the resolution), basically 
anything to force the laptop to 'update' the desktop and rescale
  3. log out/shutdown/restart
  4. Turn the monitor off and on, disconnect the cable (DisplayPort) 

  To be clear/Tldr; - this is not an issue with the monitor or cable, it
  still works fine with other laptops and had been fine up until the
  upgrade to 16.04. (When it initially started happening I assumed it
  was a cable issue so I have swapped out the cable a couple of times)
  and the monitor does not 'disconnect': just blanks out.

  Hardware - Thinkpad T410 (Intel Ironlake)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  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
  CurrentDesktop: Unity
  Date: Mon Apr 25 13:26:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-21 (216 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago)

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

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