[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

[Daniel van Vugt]

Sorry. Confirmed on artful. You just have to log in using the GNOME
session (not GNOME on Wayland). So this is a Xorg-specific bug, which
still exists.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: artful

** Summary changed:

- cursor not following the theme while hovering the desktop and the windows 
decorations
+ Gnome (on Xorg) randomly ignores customized cursor theme

** Summary changed:

- Gnome (on Xorg) randomly ignores customized cursor theme
+ Gnome (on Xorg) dishonours customized cursor theme while hovering the desktop 
and the windows decorations

** Tags added: cursor

** Changed in: lightdm (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1696019

Title:
  Gnome (on Xorg) dishonours customized cursor theme while hovering the
  desktop and the windows decorations

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

[Daniel van Vugt]

It appears the bug does not exist in 17.10. So this is either Fix
Released post-16.04, or some problem specific to your custom theme.
Please help us to figure out which by:

1. Testing Ubuntu 17.10 or 17.04; and
2. Testing the standard Ambiance/Radiance themes.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

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

-- 
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/1696019

Title:
  Gnome (on Xorg) dishonours customized cursor theme while hovering the
  desktop and the windows decorations

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1693693] Re: Stuck on a black screen after logging out of Gnome Shell

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

** Changed in: unity-greeter (Ubuntu)
   Status: Incomplete => New

** Description changed:

  Stuck on a black screen after logging out of Gnome Shell.
  
  Logging in via ssh shows gnome-shell is no longer running. But if I
- press Ctrl+Alt+F7 then the login screen (unity-greeter) comes up (and
- the login sound plays).
+ press Alt+F7 then the login screen (unity-greeter) comes up (and the
+ login sound plays).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri May 26 14:34:05 2017
  DisplayManager: lightdm
  GsettingsChanges:
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Stuck on a black screen after logging out of Gnome Shell
+ Stuck on a black screen (wrong VT) after logging out of Gnome Shell

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

Title:
  Stuck on a black screen (wrong VT) after logging out of Gnome Shell

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Stuck on a black screen after logging out of Gnome Shell.

  Logging in via ssh shows gnome-shell is no longer running. But if I
  press Alt+F7 then the login screen (unity-greeter) comes up (and the
  login sound plays).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri May 26 14:34:05 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693693/+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 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

[Daniel van Vugt]

** Changed in: canonical-devices-system-image
   Status: Incomplete => Invalid

-- 
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/1627311

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Invalid
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627311/+subscriptions

-- 
Mailing list: 

[Desktop-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Ubuntu Foundations Team Bug Bot]

The attachment "patch for network-manager source" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
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/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

[Launchpad Bug Tracker]

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

-- 
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/1627311

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627311/+subscriptions

-- 

[Desktop-packages] [Bug 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

[Launchpad Bug Tracker]

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1627311

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

[Launchpad Bug Tracker]

[Expired for mir (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mir (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1627311

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

[fcole90]

After making the screencast something fixed this behaviour, at least for
this session..

-- 
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/1696019

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

[fcole90]

I made a screencast of this behaviour. I rescaled it to keep it in a
limited size

** Attachment added: "untitled.mpg"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1696019/+attachment/4889756/+files/untitled.mpg

-- 
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/1696019

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Daniel van Vugt]

Done.

Also note we are working to release at least one significant update soon
for Ubuntu 16.04 Bluetooth audio support. So the PPA fixes will go
mainstream...

-- 
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/1582213

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

** Patch added: "patch for network-manager source"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch

-- 
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/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

The actual patch is attached above and can be applied to the source code
which you can build yourself. But for your convenience, I have attached
the .deb file below:

** Attachment added: "patched network manager .deb for easy fix installation on 
Ubuntu 17.04"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889755/+files/network-manager_1.4.4-1ubuntu3_amd64.deb

-- 
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/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Please note that this patch and fix only works for Ubuntu 17.04 which relies on
systemd-resolved as a DNS/DNSSEC stub resolver, as well as an LLMNR resolver.

You also need to be using a network-manager plugin like 
network-manager-openvpn-gnome.
Install and configure an openvpn connection after going 'sudo apt-get install 
network-manager-
openvpn-gnome', importing a config file, connecting (if possible), and 
observing the fact that
there are DNS leaks (queries WILL be routed to your ISP) with online tools like 
those at
https://dnsleaktest.com. Otherwise, just know that systemd-resolved naturally 
leaks DNS queries
over all configured domains on all interfaces by design unless a specific 
system bus call is made.
In this case, the SetLinkDomains(in  i ifindex, in  a(sb) domains) method, if 
passed
the interface index followed by an array containing the "routing-only" domain 
"~." 
(see https://manpages.debian.org/testing/systemd/systemd.network.5.en.html) and 
the boolean true.
But enough with the technical details, lets move on to the fix!

First, make sure you have all necessary packages to build the network
manager, install with:

sudo apt update
sudo apt-get build-dep network-manager

cd ~/Documents
mkdir nm && cd nm
apt-get source network-manager
cd network-manager-1.4.4/

Copy the patch file into the network-manager-1.4.4 directory:

cp ~/Downloads/resolved-vpn-dns-leak-fix.patch .

Apply the patch with:

patch -p1 < resolved-vpn-dns-leak-fix.patch

Remove patch from source directory before compilation:

rm resolved-vpn-dns-leak-fix.patch

Compile and build .deb package for installation (this will take a
while):

dpkg-buildpackage -us -uc -b

The compiled .debs should be in the parent directory you created nm:

cd ../

First, stop all network services:

sudo service network-manager stop
sudo service networking stop

Install just the patched network manager (the other .debs are not
necessary):

sudo dpkg -i network-manager_1.4.4-1ubuntu3_amd64.deb

Bring network services back up:

sudo service networking start
sudo service network-manager start

Connect to standard openvpn via network-manager-openvpn GUI (or other plugin)
Search the syslog for something like:

NetworkManager[876]:   [1496716774.9849] 
systemd-resolved[0x55b0132ec2b0]: Link type is VPN
TUN or TAP, fixing DNS leak...

and verify that the VPN link (for example tun0) includes the descriptor:
DNS Domain: ~.

using the command:

systemd-resolve --status

When compiling network manager, several bogus links are created and will show 
up when
you type 'systemd-resolve --status', don't worry they will disappear once you 
reboot.

Then open your browser, navigate to https://dnsleaktest.com and select Extended 
test
You should only see your VPN provider's DNS servers. For example, with PIA you 
should see
something like:

Test complete

Query round Progress... Servers found
  1  ..  1
  2  ..  1
  3  ..  1
  4  ..  1
  5  ..  1
  6  ..  1

IP  HostnameISP Country
173.239.220.5   ip-5-220-239-173.east.us.northamericancoax.com  GoLightSpeed
United States

Now, to prevent Ubuntu apt from replacing your patched, VPN-DNS-leak-
free version of network manager that relies on systemd-resolved, use the
command:

sudo apt-mark hold network-manager

Thats all, you're done. Congrats, no DNS leaks on Ubuntu 17.04!
I hope that I was able to make your life easier and more secure using openvpn 
or other
vpn services through the built-in GUI for the Gnome NetworkManager on Ubuntu 
17.04 :)

(Side note: I am a college student and C/C++ dev who loves Ubuntu <3 Also, this 
took quite a bit
of research on the GLib API, systemd-resolved API, and much much tracing using 
our good friend
'grep -r' for built in functions and enums of the Gnome network manager itself. 
No additional
compiler warnings are generated, the patch conforms to the C90 standard, and 
the syntax style 
used throughout the network manager source code was maintained.)

I will attach the small text patch generated using 'diff -u' along with the 
patched generated 
.deb file for your convenience. Cheers, and I hope this helps you all!

-- 
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/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS 

[Desktop-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

[fcole90]

** Summary changed:

- cursor not following the theme while hovering the desktop
+ cursor not following the theme while hovering the desktop and the windows 
decorations

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[fcole90]

I receive the following warning:
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
No journal files were opened due to insufficient permissions.

Retrying as superuser I didn't receive the warning but the log was
empty..

** Attachment added: "gnome-shell.log"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+attachment/4889746/+files/gnome-shell.log

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Doug Morse]

@Daniel van Vugt (vanvugt):  Thanks for your assistance!

I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.

I didn't subscribe to this bug, I didn't even know about it.  I report
bug 1691556 and you marked it a duplicate of this one.

As I have already requested, kindly re-open my bug 1691556, as I don't
believe I can re-open it myself.

Finally, I'd like to see this fixed in 16.04.  It's LTS, and that's
important to me (and a lot of users).  If that means I have to help with
backport, I'm happy to do so.  In addition, if I can be helpful with
debugging, I'd be happy to do so, and have tried.  It's just not clear
to me at this point how to get better / more detailed debugging info.
What I did try per https://wiki.ubuntu.com/DebuggingBluetooth didn't
reveal anything helpful.  For me, I believe the key issue is figuring
out the "Device or resource busy" error (as I've mentioned here and in
my original bug report).

-- 
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/1582213

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  

[Desktop-packages] [Bug 619403] Re: [KDE] no option for mouse wheel acceleration

[Austin]

** Changed in: xorg-server (Ubuntu)
   Status: Opinion => Confirmed

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

Status in X.Org X server:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I am very used to mouse wheel acceleration but I haven't found any
  setting for it in the KDE settings.

  Also, the maximum possible value you can fill there (strangely it
  counts per lines) still is very slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: kdebase (not installed)
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic-pae 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Aug 17 20:50:50 2010
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-kde

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+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 1695567] Re: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR *** in g_free() from gweather_location_unref()

[Jeremy Bicha]

** Description changed:

  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions
  
  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.
+ 
+ This error has been reported over 700 times on errors.ubuntu.com for
+ Ubuntu GNOME 17.04.
  
  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash
  
  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
  
   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Description changed:

  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions
  
  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.
  
  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.
  
  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash
  
  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
  
+ [Other Info]
+ This updates libgweather from 3.24.0 to 3.24.1
+ https://git.gnome.org/browse/libgweather/log
+ 
+ The guard_against_segfault commit was already present in Ubuntu 17.04.
+ 
   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Changed in: libgweather (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: libgweather (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  [Other Info]
  This updates libgweather from 3.24.0 to 3.24.1
  https://git.gnome.org/browse/libgweather/log

  The guard_against_segfault commit was already present in Ubuntu 17.04.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of 

[Desktop-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Daniel van Vugt]

OK, could you please:

1. Start a separate VT login: Ctrl+Alt+F4, and log in.
2. Return to lightdm (Ctrl+Alt+F7) and attempt a Gnome login.
3. After it fails return to Ctrl+Alt+F4 and take a copy of the log using this 
command:
   journalctl /usr/bin/gnome-shell > gnome-shell.log
4. Attach gnome-shell.log to this bug.

I hope in future bug reports will do this automatically for users, but
they don't yet.

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1688208] Re: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city()

[Jeremy Bicha]

** Description changed:

+ Impact
+ ==
+ Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.
+ 
+ (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)
+ 
+ This particular error has been reported over 1000 times to
+ errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
+ blocker bug.
+ 
+ Test Case
+ =
+ The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.
+ 
+ Because e.u.com links this issue with gnome-shell, this is difficult to
+ verify except that if you run gnome-shell, it shouldn't crash so often
+ especially when first logging in.
+ 
+ Regression Potential
+ 
+ The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

Title:
  gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city()
  from foreach_city() from foreach_city() from foreach_city()

Status in libgweather:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  Impact
  ==
  Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.

  (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)

  This particular error has been reported over 1000 times to
  errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
  blocker bug.

  Test Case
  =
  The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.

  Because e.u.com links this issue with gnome-shell, this is difficult
  to verify except that if you run gnome-shell, it shouldn't crash so
  often especially when first logging in.

  Regression Potential
  
  The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1688208/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[fcole90]

I have an nvidia/intel hybrid GPU (GTX-850M), with nvidia proprietary
drivers (nvidia-375) from the supported drivers PPA. The attempt failed
when using the intel GPU, so the nvidia part is not involved. Using GDM
I could load a fully functional Wayland session.

I'm using also the most updated Linux/X/Mesa HWE stack from main
repository (I think it's based on the 16.10 stack).

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Daniel van Vugt]

All,

I have spent some time looking at the major Bluetooth/audio pain points
recently. And a common problem is simply that some bugs are
oversubscribed. Everyone experiences bugs slightly differently and it
clouds the issue to the point of us not being able to ever close it.

But the answer is simple: If your name is not Mary Sherman and you
continue to experience problems even with the PPA (and after rebooting)
then please log a separate bug of your own.

P.S. Also generally speaking Bluetooth audio support is still maturing
so my advice is if you rely on Bluetooth audio then you should be using
the latest (17.04+) Ubuntu release. It certainly was not ready for
general usage in 16.04.

-- 
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/1582213

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 941928] Re: Firefox starts and crashes

[spm2011]

** Changed in: ubufox (Ubuntu)
   Status: New => Invalid

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

Title:
  Firefox starts and crashes

Status in ubufox package in Ubuntu:
  Invalid

Bug description:

Application Basics

  Name
  Firefox

  Version
  11.0

  User Agent
  Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:11.0) Gecko/20100101 
Firefox/11.0

  Profile Directory

Open Containing Folder

  Enabled Plugins

about:plugins

  Build Configuration

about:buildconfig

  Crash Reports

about:crashes

  Memory Use

about:memory

Extensions

  Name

  Version

  Enabled

  ID

  NoScript
  2.3
  true
  {73a6fe31-595d-460b-a920-fcc0f8843232}

  Test Pilot
  1.2
  true
  testpi...@labs.mozilla.com

  TinyURL Generator
  2.5.1
  true
  tinyurl.ad...@fast-chat.co.uk

  Ubuntu Firefox Modifications
  0.9.3
  true
  ubu...@ubuntu.com

  Firebug
  1.9.1
  false
  fire...@software.joehewitt.com

  Mozilla Firefox hotfix
  1.0
  false
  firefox-hot...@mozilla.org

Modified Preferences

Name

Value

  accessibility.typeaheadfind.flashBar
  0

  browser.history_expire_days.mirror
  180

  browser.places.importBookmarksHTML
  false

  browser.places.smartBookmarksVersion
  2

  browser.startup.homepage
  http://www.google.com/

  browser.startup.homepage_override.buildID
  20120225025349

  browser.startup.homepage_override.mstone
  rv:11.0

  browser.tabs.warnOnClose
  false

  extensions.lastAppVersion
  11.0

  gfx.blacklist.suggested-driver-version
  

  network.cookie.prefsMigrated
  true

  places.database.lastMaintenance
  1330350623

  places.history.expiration.transient_current_max_pages
  104858

  places.history.expiration.transient_optimal_database_size
  167772160

  places.last_vacuum
  1303735866

  plugin.disable_full_page_plugin_for_types

  print.print_bgcolor
  false

  print.print_bgimages
  false

  print.print_colorspace
  default

  print.print_downloadfonts
  false

  print.print_evenpages
  true

  print.print_in_color
  true

  print.print_margin_bottom
  0.50012107193

  print.print_margin_left
  0.50012107193

  print.print_margin_right
  0.50012107193

  print.print_margin_top
  0.50012107193

  print.print_oddpages
  true

  print.print_orientation
  0

  print.print_pagedelay
  500

  print.print_paper_data
  0

  print.print_paper_height
  279.40

  print.print_paper_name
  na_letter

  print.print_paper_size_type
  1

  print.print_paper_size_unit
  1

  print.print_paper_width
  215.90

  print.print_plex_name
  default

  print.print_printer
  IT_OKI_C610

  print.print_resolution_name
  default

  print.print_scaling
  1.00

  print.print_shrink_to_fit
  true

  print.print_to_file
  false

  print.print_unwriteable_margin_bottom
  56

  print.print_unwriteable_margin_left
  25

  print.print_unwriteable_margin_right
  25

  print.print_unwriteable_margin_top
  25

  print.printer_CupsPDF.print_bgcolor
  false

  print.printer_CupsPDF.print_bgimages
  false

  print.printer_CupsPDF.print_colorspace
  default

  print.printer_CupsPDF.print_command
  lpr ${MOZ_PRINTER_NAME:+-P"$MOZ_PRINTER_NAME"}

  print.printer_CupsPDF.print_downloadfonts
  false

  print.printer_CupsPDF.print_edge_bottom
  0

  print.printer_CupsPDF.print_edge_left
  0

  print.printer_CupsPDF.print_edge_right
  0

  print.printer_CupsPDF.print_edge_top
  0

  print.printer_CupsPDF.print_evenpages
  true

  print.printer_CupsPDF.print_footercenter

  print.printer_CupsPDF.print_footerleft
  

  print.printer_CupsPDF.print_footerright
  

  print.printer_CupsPDF.print_headercenter

   

[Desktop-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR *** in g_free() from gweather_location_unref()

[Daniel van Vugt]

** Summary changed:

- /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or 
corruption (out): ADDR ***
+ /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or 
corruption (out): ADDR *** in g_free() from gweather_location_unref()

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+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 1672037] Re: package network-manager-gnome 1.2.6-0ubuntu0.16.04.2 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package network-manager-gnome 1.2.6-0ubuntu0.16.04.2 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

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

Bug description:
  error persist

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Mar  9 13:21:14 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (223 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.16  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: network-manager-applet
  Title: package network-manager-gnome 1.2.6-0ubuntu0.16.04.2 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1672037/+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 1574347] Re: WiFi networks list disappears (device type not reloaded)

[Daniel van Vugt]

All: Commenting on a closed bug will generally be ignored (even if it
was closed erroneously).

If you have continuing issues then please log a new bug.

** Changed in: network-manager (Ubuntu)
 Assignee: Marzenco Alexandru Ionuț (thors-hand) => (unassigned)

-- 
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/1574347

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Daniel van Vugt]

That might be true, but NVIDIA isn't mentioned anywhere in this bug.

fcole90: What GPU/drivers are you using?

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1292398] Re: Second screen position isn't saved from one session to another

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Importance: Low => Medium

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Unknown
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1491787] Re: System language isn't applied to gnome-control-center in Gnome-Shell

[Daniel van Vugt]

Note that 'Settings' is two different apps depending on which shell
you're using:

Unity7: unity-control-center
Gnome Shell: gnome-control-center

** Package changed: gnome-shell (Ubuntu) => gnome-control-center
(Ubuntu)

-- 
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/1491787

Title:
  System language isn't applied to gnome-control-center in Gnome-Shell

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

Bug description:
  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1491787/+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 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

[Christopher M. Penalver]

Namey Herey, it will help immensely if you use the computer the problem is 
reproducible with, work around the issue as you noted, and file a new report 
with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

-- 
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/1638990

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic.

  WORKAROUND: Use nouveau.

  WORKAROUND: Boot with already installed kernel 4.4.0-31-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+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 281985] Re: [upstream] background image zoomed in exporting .odp to .ppt

[Christopher M. Penalver]

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [upstream] background image zoomed in exporting .odp to .ppt

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Impress via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/281985/+attachment/380358/+files/demo.odp
  && loimpress -nologo demo.odp

  save the file in .ppt, close and open the .ppt and it looks the same
  as it did in demo.odp.

  4) What happens instead is the background is zoomed in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/281985/+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 1491787] [NEW] System language isn't applied to gnome-control-center in Gnome-Shell

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hey,

I'm referring to this issue on AskUbuntu:
http://askubuntu.com/questions/600656/change-language-of-the-gnome-
shell-overview

On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
center are shown in English in the Gnome-Shell overview (see screenshot
in the above mentioned link), even though my system language is German.
The entries in the gnome-control-center itself are however in German.

Is this due to a bug or missing translations?

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: gnome-control-center gnome-shell xenial yakkety zesty
-- 
System language isn't applied to gnome-control-center in Gnome-Shell
https://bugs.launchpad.net/bugs/1491787
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-control-center in Ubuntu.

-- 
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 1696022] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  something not right

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 18:50:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-04-11 (420 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1696022/+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 1696022] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Alex Telnyi]

Public bug reported:

something not right

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
Uname: Linux 3.13.0-96-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Mon Jun  5 18:50:23 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2016-04-11 (420 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  something not right

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 18:50:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-04-11 (420 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1696022/+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 1695876] Re: German Documentation file displays incorrect CUPS version

[Bug Watch Updater]

** Changed in: cups
   Status: Unknown => New

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1695876/+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 1696019] [NEW] cursor not following the theme while hovering the desktop

[fcole90]

Public bug reported:

If I use lightdm to load GNOME Shell, I encounter a very weird bug: if I
move the cursor to hover the desktop, the cursor theme becomes DMZ
White, but if I move the cursor over the GNOME panel or over any open
window, it returns back to the custom theme set by me.

I can experience this bug only when using lightdm, if I use gdm3 I
always have the same cursor.

Note that I'm not on Wayland and that I have nautilus folders on my
desktop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun  6 02:14:12 2017
InstallationDate: Installed on 2016-09-09 (269 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Summary changed:

- cursor does not following the theme while hovering the desktop
+ cursor not following the theme while hovering the desktop

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

Title:
  cursor not following the theme while hovering the desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1696019/+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 1695876] Re: German Documentation file displays incorrect CUPS version

[Till Kamppeter]

Reported upstream as

https://github.com/apple/cups/issues/5019

** Bug watch added: github.com/apple/cups/issues #5019
   https://github.com/apple/cups/issues/5019

** Also affects: cups via
   https://github.com/apple/cups/issues/5019
   Importance: Unknown
   Status: Unknown

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1695876/+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 1660353] Re: thumbnails disappear when scrolling in thumbnails pane

[Bug Watch Updater]

** Changed in: evince
   Status: Confirmed => Fix Released

-- 
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/1660353

Title:
  thumbnails disappear when scrolling in thumbnails pane

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Triaged

Bug description:
  1. open a many-page (at least 15 pages) document
  2. open the thumbnails pane
  3. click on a thumbnail
  4. scroll up and down until the thumbnails (including outlines disappear)

  Obviously, we expect for the thumbnails to stay visible.  To make then
  visible again, move the pointer to the main document window, and then
  back to the thumbnails. Each one will reappear as you move the pointer
  over it.

  This is not the same as bug 1369028 as evince does not hang.
  This is not the same as bug 1629633, as there is still a thumbnail border for 
that document, and under no circumstances will the thumbnail appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 30 15:36:40 2017
  InstallationDate: Installed on 2014-10-13 (840 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (108 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1660353/+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 1611037] Re: Geolocation in firefox doesn't work anymore

[Pierre Rudloff]

Debian switched to MLS by default and I guess Ubuntu could do the same.
This would help avoid quota issues.

-- 
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/1611037

Title:
  Geolocation in firefox doesn't work anymore

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since a couple of days (around beginning of August 2016) the
  geolocation in Firefox doesn't work anymore. I _think_ (but not
  entirely sure) this happened already with Firefox 47.

  That seems to affect all the website using the W3C geolocation, but to test, 
go for example to:
  http://benwerd.com/lab/geo.php

  In the popup, accept to share the location, and the text displayed in the 
location is:
  "The page could not get your location."

  My computer is running Ubuntu 16.04, with Firefox
  48.0+build2-0ubuntu0.16.04.1 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1611037/+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 1617129] Re: "Startup Applications" not saving after reboot. Also program added does not run at reboot.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-session (Ubuntu)
   Status: New => Confirmed

-- 
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/1617129

Title:
  "Startup Applications" not saving after reboot.  Also program added
  does not run at reboot.

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  When using Startup Applications in a fresh install of 16.04 I select "Add" 
and place my information for the program in the proper lines.
  An example is a terminal package called Guake.
  In 14.04 when using the Startup Applications and adding this package it would 
run at startup, reboot or re-logging in.  in 14.04 in general I have not 
encountered this issue.
  There is a item that is always there and that is "NVIDIA X Server Settings" 
(this may be the cause of my other issue Bug 1615864), but I will leave that to 
the other report.
  I also noticed after adding the program to autostart at boot up that there 
was nothing added to the .config/autostart folder. Maybe this is not related?  
Again, pointing to Bug 1615864 for the reason the script is not autostarting.
  Could this be an issue with autostart not reading the added items from the 
GUI or even the manually added script I placed in the autostart folder for my 
graphics issue?

  I must have added Guake a dozen times along with some test items to
  start.  Each and every time the items fall out of the GUI and have to
  be re-added and they did not run after boot.

  Thanks
  GEE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1617129/+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 1695987] [NEW] "Unknown option: proto udp6" error on openvpn import in KDE network manager

[linex83]

Public bug reported:

I created an openvpn config file, which I could successfully run on
command line. However, as I tried importing the file with the KDE
network manager, I got the following error message:

"Unknown option: proto udp6"

Since the openvpn command could process the config file without
problems, I think the network manager should be able to do that, too.

Here's my openvpn client config file:
client
dev tun
proto udp6
remote ::...:ccc 7002
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert my.crt
key my.key
remote-cert-tls server
tls-auth ta.key 1
cipher AES-256-CBC
auth SHA512
comp-lzo
verb 3
key-direction 1

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jun  5 22:08:08 2017
InstallationDate: Installed on 2017-06-04 (0 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu zesty

-- 
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/1695987

Title:
  "Unknown option: proto udp6" error on openvpn import in KDE network
  manager

Status in xorg package in Ubuntu:
  New

Bug description:
  I created an openvpn config file, which I could successfully run on
  command line. However, as I tried importing the file with the KDE
  network manager, I got the following error message:

  "Unknown option: proto udp6"

  Since the openvpn command could process the config file without
  problems, I think the network manager should be able to do that, too.

  Here's my openvpn client config file:
  client
  dev tun
  proto udp6
  remote ::...:ccc 7002
  resolv-retry infinite
  nobind
  persist-key
  persist-tun
  ca ca.crt
  cert my.crt
  key my.key
  remote-cert-tls server
  tls-auth ta.key 1
  cipher AES-256-CBC
  auth SHA512
  comp-lzo
  verb 3
  key-direction 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun  5 22:08:08 2017
  InstallationDate: Installed on 2017-06-04 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695987/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

[Chris]

I found the bug described and confirmed on redhat, where I also found the 
solution. (although they have the goa-demon in the /usr/libexec/ folder)
https://bugzilla.redhat.com/show_bug.cgi?id=1340203

As a work-around, for each user account I created a new file in
~/.config/autostart/ called goa-replace.desktop, and in a text-editor
entered the following:

[Desktop Entry]
Name=GOA Replace
Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace
NoDisplay=true
Terminal=false
Type=Application

The problem seems to be that dbus is spawning goa-daemon, but then not
killing the process when the user logs out. gnome-keyring IS killed, and
this breaks the link between the two.

Not sure what the *real* solution is, seems to be a big debate about how
systemd leaves 'lingering' processes from users after log out. I see 28
processes left running after a user logs out. Surely this needs to be
cleaned up??? Is there a better way to force systemd to properly close a
users session?

** Bug watch added: Red Hat Bugzilla #1340203
   https://bugzilla.redhat.com/show_bug.cgi?id=1340203

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1695983] [NEW] Removing an imported openvpn connection doesn't clean up copied certificates

[linex83]

Public bug reported:

I imported an openvpn connection with the KDE network manager, which
worked fine. On import I was asked whether I want my certificates to be
copied to .local/share/networkmanagement, which I confirmed. Them I
removed my connection and reimported it again, this time receiving the
following error message:

"Error copying certificate to
/home/user/.local/share/networkmanagement/certificates/myopenvpn.key:
Destination file exists"

Seems like copied certificates aren't cleaned up when an openvpn
connection is removed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jun  5 21:56:31 2017
InstallationDate: Installed on 2017-06-04 (0 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu zesty

-- 
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/1695983

Title:
  Removing an imported openvpn connection doesn't clean up copied
  certificates

Status in xorg package in Ubuntu:
  New

Bug description:
  I imported an openvpn connection with the KDE network manager, which
  worked fine. On import I was asked whether I want my certificates to
  be copied to .local/share/networkmanagement, which I confirmed. Them I
  removed my connection and reimported it again, this time receiving the
  following error message:

  "Error copying certificate to
  /home/user/.local/share/networkmanagement/certificates/myopenvpn.key:
  Destination file exists"

  Seems like copied certificates aren't cleaned up when an openvpn
  connection is removed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun  5 21:56:31 2017
  InstallationDate: Installed on 2017-06-04 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+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 1695973] Re: nautilus crashed with SIGSEGV

[Cristian Aravena Romero]

** Information type changed from Private to Public

-- 
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/1695973

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Started Ubuntu GNOME, and open apport.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Jun  4 18:26:57 2017
  Disassembly: No hay registros.
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1494016476
  InstallationDate: Installed on 2015-07-26 (679 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcCwd: /home/caravena
  Registers: El programa no tiene registros ahora.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'programa'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-05-15 (20 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1695973/+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 1695971] Re: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured because

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
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/1695971

Title:
  package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to
  install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  cannot be configured because libgl1-mesa-glx:i386 is at a different
  version (13.1~git1701031930.c4b87f~gd~x)

Status in mesa package in Ubuntu:
  New

Bug description:
  I tried to install Qt5 by
  ```
  $ sudo apt-get install qt5-default
  ```
  what gave me a `you have held broken packages' error`-message so I tried
  ```
  $ sudo aptitude install qt5-default
  ```
  what proposed some solutions. I think, the chosen solution downgraded the 
given package in the summary.

  Additional information:
  ```
  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  
  $ apt-cache policy libgl1-mesa-glx:amd64
  libgl1-mesa-glx:
Installed: 12.0.6-0ubuntu0.16.10.1
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   *** 12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  
  $ apt-cache policy libgl1-mesa-glx:i386
  libgl1-mesa-glx:i386:
Installed: (none)
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  5 20:33:05 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   vhba, 20161009, 4.8.0-49-generic, x86_64: installed
   vhba, 20161009, 4.8.0-52-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-49-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-52-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-glx:amd64:12.0.6-0ubuntu0.16.10.1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1.1) ...
   dpkg: error processing package libglapi-mesa:amd64 (--configure):
package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured 
because libglapi-mesa:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be 
configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7007]
  InstallationDate: Installed on 2016-06-04 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 2740p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=45931ea1-c5bd-4b7e-ae5d-28d50c0d8e97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot 
be configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68COU Ver. F.04
  dmi.board.name: 7007
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 39.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68COUVer.F.04:bd03/08/2011:svnHewlett-Packard:pnHPEliteBook2740p:pvr:rvnHewlett-Packard:rn7007:rvrKBCVersion39.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2740p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.74+git1612241830.eebefa~gd~x
  

[Desktop-packages] [Bug 1695971] [NEW] package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured becau

[Michael Banucu]

Public bug reported:

I tried to install Qt5 by
```
$ sudo apt-get install qt5-default
```
what gave me a `you have held broken packages' error`-message so I tried
```
$ sudo aptitude install qt5-default
```
what proposed some solutions. I think, the chosen solution downgraded the given 
package in the summary.

Additional information:
```
$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10


$ apt-cache policy libgl1-mesa-glx:amd64
libgl1-mesa-glx:
  Installed: 12.0.6-0ubuntu0.16.10.1
  Candidate: 12.0.6-0ubuntu0.16.10.1
  Version table:
 *** 12.0.6-0ubuntu0.16.10.1 500
500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 12.0.3-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages


$ apt-cache policy libgl1-mesa-glx:i386
libgl1-mesa-glx:i386:
  Installed: (none)
  Candidate: 12.0.6-0ubuntu0.16.10.1
  Version table:
 12.0.6-0ubuntu0.16.10.1 500
500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
 12.0.3-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
```

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jun  5 20:33:05 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 vhba, 20161009, 4.8.0-49-generic, x86_64: installed
 vhba, 20161009, 4.8.0-52-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-49-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-52-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-glx:amd64:12.0.6-0ubuntu0.16.10.1
 Processing triggers for desktop-file-utils (0.23-1ubuntu1.1) ...
 dpkg: error processing package libglapi-mesa:amd64 (--configure):
  package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured 
because libglapi-mesa:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be 
configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7007]
InstallationDate: Installed on 2016-06-04 (366 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 2740p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=45931ea1-c5bd-4b7e-ae5d-28d50c0d8e97 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: mesa
Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot 
be configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68COU Ver. F.04
dmi.board.name: 7007
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 39.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68COUVer.F.04:bd03/08/2011:svnHewlett-Packard:pnHPEliteBook2740p:pvr:rvnHewlett-Packard:rn7007:rvrKBCVersion39.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2740p
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74+git1612241830.eebefa~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git1612191933.720dd0~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1701040733.028c94~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git1610280732.1516d3~gd~x
xserver.bootTime: Mon Jun  5 20:51:28 2017
xserver.configfile: 

[Desktop-packages] [Bug 1297790] Re: "Unknown audio device" dialog pops up every time I plug in headphones

[spm2011]

** Tags added: zesty

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

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I've got a combined headphone/headset socket on my Laptop. Every time
  I plug in my headphones, an "unknown audio device" dialog pops up
  asking whether I've plugged in headphones or a headset.  This is isn't
  a great user experience as my phone can auto-detect the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1949 F pulseaudio
   /dev/snd/controlC0:  mark   1949 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 26 11:03:29 2014
  InstallationDate: Installed on 2014-03-24 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Latitude E7440, Realtek ALC292, Green Headphone Out, Front] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: DE004505
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: DE004505
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1297790/+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 1695948] [NEW] Nothing

[Severin Scheuerer]

Public bug reported:

Nothing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun  5 20:05:15 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:81d2]
InstallationDate: Installed on 2017-06-04 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-54-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81D2
dmi.board.vendor: HP
dmi.board.version: KBC Version 87.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 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

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

Title:
  Nothing

Status in xorg package in Ubuntu:
  New

Bug description:
  Nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun  5 20:05:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81d2]
  InstallationDate: Installed on 2017-06-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-54-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81D2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 87.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive
  
+ 
+ ubuntu-system-settings-online-accounts
+ online-accounts-api
+ storage-framework
+ keeper
+ mcloud
+ Note: ubuntu-system-settings recommends u-s-s-online-accounts. My 
understanding is that we'll be dropping unity8 from Ubuntu 17.10 so I'm not 
sure it's worthwhile to drop that recommends.
+ 
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
  Kubuntu still uses signon-ui

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

Title:
  Please remove obsolete UOA packages

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

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive

  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  Note: ubuntu-system-settings recommends u-s-s-online-accounts. My 
understanding is that we'll be dropping unity8 from Ubuntu 17.10 so I'm not 
sure it's worthwhile to drop that recommends.

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1677198] Re: OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

[Jan-Åke Larsson]

I understand this is an upstream bug. I'll just write this here anyway,
will post bug upstream later if nobody beats me to it.

Affects me too. The imported config said aes-256-cbc. That was read in
as BF-something-or-other. Blowfish, not AES. After setting that to
AES-256-CBC, the thing connects.

After some time, the following happens:

nm-openvpn[3577]: [integrity] Inactivity timeout (--ping-restart), restarting
nm-openvpn[3577]: SIGUSR1[soft,ping-restart] received, process restarting
nm-openvpn[3577]: NOTE: the current --script-security setting may allow this 
configuration to call user-defined scripts
nm-openvpn[3577]: TCP/UDP: Preserving recently used remote address: 
[AF_INET]:
nm-openvpn[3577]: UDP link local: (not bound)
nm-openvpn[3577]: UDP link remote: [AF_INET]:
nm-openvpn[3577]: [integrity] Peer Connection Initiated with [AF_INET]:
nm-openvpn[3577]: Preserving previous TUN/TAP instance: tun0
nm-openvpn[3577]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper 
--debug 0 3573 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_8 
--tun -- tun0 1500 1558   restart
nm-openvpn[3577]: WARNING: Failed running command (--up/--down): could not 
execute external program
nm-openvpn[3577]: Exiting due to fatal error
NetworkManager[667]:  [1496682880.1314] platform-linux: 
do-add-ip4-route[8: 0.0.0.0/0 50]: failure 101 (Nätverket kan inte nås)

It seems that nm-openvpn fails. Ideas on what to do?

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

Title:
  OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

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

Bug description:
  I can definitely confirm that Network Manager's OpenVPN is not working
  yet in Ubuntu 17.04.

  I set up my configuration via import:
  http://neartalk.com/ss/2017-03-29_001_633x332.png

  On all earlier versions of Ubuntu, after importing the configuration,
  I'm able to connect to the VPN. However, in 17.04, connection attempts
  always give this error immediately:

  "The VPN Connection disconnected because the VPN Service has stopped"

  Clearly the VPN Service has NOT stopped. I've confirmed that this
  error is false by taking the exact same import-file and I imported it
  into an Ubuntu 16.04 computer and then the VPN connected without
  issue. Also, with this same import-file I've had no issues in Ubuntu
  16.10.

  So I've thoroughly confirmed that there is no issue with the VPN
  service. The issue is with the client in Ubuntu 17.04.

  I cannot upgrade to 17.04 until this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 05:25:14 2017
  InstallationDate: Installed on 2017-01-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

[Till Kamppeter]

As the backends do not filter data but simply pass the data through it
is not clear whether the "usb" CUPS backend really causes the problem.
Especially in this case the CUPS backend still lets go data to the
printer and the printer prints something.

So before modifying the backend behavior I would like to know what kind
of data you feed to the printer and what does CUPS exactly do.

Did you create a CUPS queue with a driver/PPD file? Which driver or PPD
file (please attach your print queue's PPD file from /etc/cups/ppd/)? Or
did you create a raw (unfiltered) queue? How do you send jobs to CUPS?
Do you simply send them or do you use the "-o raw" option (unfiltered
by-job)? Are you sending jobs as plain text or as PDF, PostScript, ...?

If you add the quirk rule to blacklist your printer the "usb" CUPS
backend would ignore the printer preventing the backend to discover the
printer. How are you using the printer then? Another CUPS backend? Which
one? No use of CUPS at all (like "cat file > /dev/usb/lp0")? Are you
using a driver/filter then?

Please also follow the instructions of the sections "CUPS error_log",
"USB printer", "Capturing print job data", and "Getting the data which
would go to the printer" for the case when you are using the "usb" CUPS
backend without changes in the quirk rules and also when using CUPS with
the change. also run

sudo lsusb -vvv > lsusb-out.txt

and attach the resulting file.

Please do not compress any of the files you get and do not package them
together. Attach them to this bug report one by one.

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

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

[Namey Herey]

Linux 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
Ubuntu 17.04
NVIDIA binary driver 375.66 from nvidia-375
Nvidia GTX 770
Using disk encryption

I cannot believe this is still an issue after a year! During this time I
have had to manually fix and purge the Nvidia drivers multiple times (at
various different installs onto my PC where I was hoping this issue had
been resolved). There is no way any normal person would have been able
to recover their device.

It was difficult enough to even find this bug report.

Someone reported "Also wanted to mention that the initial symptom of
this problem in the presence of full-disk encryption is that the boot
fails very early, before it even asks for your FDE passphrase.". However
that is not the case for me, in this case I enter the passphrase but the
next stage is a black screen with a single "_" character in the top-left
corner, with nothing happening.

-- 
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/1638990

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic.

  WORKAROUND: Use nouveau.

  WORKAROUND: Boot with already installed kernel 4.4.0-31-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

[Ubuntu Foundations Team Bug Bot]

The attachment "cups_2.2.3-1ubuntu1.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1695928] [NEW] Please remove obsolete UOA packages

[Jeremy Bicha]

Public bug reported:

Ubuntu Online Accounts is no longer maintained. There is an alternative,
GNOME Online Accounts for the GNOME desktop.

Also, Unity's Online Accounts settings panel does not currently work
without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

Please remove these source packages and their binaries:
-
gnome-control-center-signon
account-plugins
account-plugin-fitbit
account-polld
pay-service
qt-purchasing-opensource-src
storage-provider-webdav
sync-monitor
ubuntuone-credentials
ubuntu-push
unity-scope-gdrive

Other Notes
---
The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

Kubuntu still uses signon-ui

** Affects: gnome-control-center-signon (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-signon in Ubuntu.
https://bugs.launchpad.net/bugs/1695928

Title:
  Please remove obsolete UOA packages

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

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1695917] [NEW] 0.26.2 has been released

[Nikita Yerenkov-Scott]

Public bug reported:

A new maintenance release for Shotwell which is 0.26.2 is now available
for download. Please upgrade the version the the repositories. The
changelog is:

Shotwell 0.26.2 - 1 Jun 2017
  * Fix issue when minimizing publishing UI on Unity
  * Fix browsing on GVFS-mounted file systems
  * Fix missing linebreaks in comments when writing back meta-data
  * Fix crash when no import plugin is selected
  * Translation updates

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


** Tags: upgrade-software-version

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

Title:
  0.26.2 has been released

Status in shotwell package in Ubuntu:
  New

Bug description:
  A new maintenance release for Shotwell which is 0.26.2 is now
  available for download. Please upgrade the version the the
  repositories. The changelog is:

  Shotwell 0.26.2 - 1 Jun 2017
* Fix issue when minimizing publishing UI on Unity
* Fix browsing on GVFS-mounted file systems
* Fix missing linebreaks in comments when writing back meta-data
* Fix crash when no import plugin is selected
* Translation updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1695917/+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 1176510] Re: gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

[Chow Loong Jin]

** Package changed: banshee (Ubuntu) => rhythmbox (Ubuntu)

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

Title:
  gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  If I start rhytmbox on the new ubuntu 13.04 raring ringtail (amd64)
  then i get the following message:

  ERROR: Caught a segmentation fault while loading plugin file:
  /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so

  Please either:
  - remove it and restart.
  - run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

  
  The installed version of gstreamer1.0-plugins-base is 1.0.6-1.

  The error occurs, when I try to play any mp3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1176510/+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 1351772] Re: "disable touchpad while typing" doesn't work

[Christopher Barrington-Leigh]

Thank you! It looks like this:

Thinkpad T450s:

$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen  id=9[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=12   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint id=13   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 4x5 Pen stylus   id=16   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 4x5 Pen eraser   id=17   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 4x5 Pad pad  id=18   [slave  pointer  (2)]
⎜   ↳ Wacom Bamboo 2FG 4x5 Finger touch id=19   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Sleep Button  id=8[slave  keyboard (3)]
↳ Integrated Camera id=10   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=11   [slave  keyboard (3)]
↳ ThinkPad Extra Buttonsid=14   [slave  keyboard (3)]
↳ HD Webcam C525id=15   [slave  keyboard (3)]

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

Title:
  "disable touchpad while typing" doesn't work

Status in OEM Priority Project:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  When selecting "disable while typing" under the touchpad section of
  the "Mouse & Touchpad" preferences, nothing changes, the touchpad
  stays active while typing. I can rapidly type multiple characters with
  my left hand and continue to move the cursor with the touchpad with my
  right hand.

  I can see from my processlist that syndaemon is running with the
  following options:

   2185 ?S  1:31  |   \_ syndaemon -i 1.0 -t -K -R

  First, the -t option isn't what's expected with this setting, it
  should disable the touchpad entirely. Also, it doesn't seem to even do
  that correctly, as I can definitely click the touchpad while typing as
  well as moving the cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  Uname: Linux 3.14.0-997-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug  2 17:20:22 2014
  InstallationDate: Installed on 2014-04-22 (102 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1351772/+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 1691693] Re: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitt

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

-- 
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/1691693

Title:
  package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade:
  unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new':
  Operation not permitted

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I was trying to upgrade to 17.04 and the error plus loads of others
  came up. Even after partial upgrade again.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu May 18 10:27:56 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.2.2-0ubuntu2
   Unpacking libreoffice-common (1:5.3.1-0ubuntu2) over (1:5.2.2-0ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-lHfAqY/17-libreoffice-common_1%3a5.3.1-0ubuntu2_all.deb 
(--unpack):
unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2016-02-19 (453 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: 
unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1691693/+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 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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/1393578

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

-- 
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/1663062

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 393585] Re: Focused/unfocused selection colors are confusingly similar

[Matthew Paul Thomas]

ubuntu-ux was a dummy project for the purpose of getting the opinion of
Canonical’s platform design team. That team no longer exists. My view on
this, however, is the same as it was when I commented in April 2010.

-- 
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/393585

Title:
  Focused/unfocused selection colors are confusingly similar

Status in One Hundred Papercuts:
  Invalid
Status in community-themes package in Ubuntu:
  Opinion
Status in nautilus package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Opinion

Bug description:
  Problem occurs with: Ambiance, Radiance, Clearlooks, DarkRoom,  Dust, 
Elementary, Glossy, Human, Human-Clearlooks
  Does not occur with: New Wave

  For example, open a Nautilus window and select an icon.  Switch focus
  to the desktop by clicking on it.  The window is not active but the
  icon in it retains the "selected items" color.  It appears as though
  it is still selected and that it can be modified by keyboard
  shortcuts.  By clicking on an icon on the desktop it changes color to
  be selected an now it appears that two items are selected.

  Several times I've deleted things by accident due to this, especially
  when I was new to GNOME.  I would have several windows open with items
  selected.  I would see the item I want selected and hit the delete key
  to remove it, only to realize that I had some other window focused
  where I had deleted something else.

  In Windows selected items in unfocused windows turn gray.  I think it
  also adds another visual clue as to what window is focused besides
  just the title bar.

  Firefox and Thunderbird deliver the behavior I expect (probably
  because they are only faux GTK apps).  Select some text in Firefox and
  then focus to another window and you will see that the selected text
  turns gray, indicating it is not active.  Try that in gedit or evince
  and the text will remain blue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/393585/+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 1176510] Re: gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: banshee (Ubuntu)
   Status: New => Confirmed

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

Title:
  gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault

Status in banshee package in Ubuntu:
  Confirmed

Bug description:
  If I start rhytmbox on the new ubuntu 13.04 raring ringtail (amd64)
  then i get the following message:

  ERROR: Caught a segmentation fault while loading plugin file:
  /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttypefindfunctions.so

  Please either:
  - remove it and restart.
  - run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

  
  The installed version of gstreamer1.0-plugins-base is 1.0.6-1.

  The error occurs, when I try to play any mp3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1176510/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

[Dariusz Gadomski]

Patch proposal for Artful.

** Patch added: "cups_2.2.3-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+attachment/4889375/+files/cups_2.2.3-1ubuntu1.debdiff

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[Jeremy Bicha]

I don't think the open source NVIDIA graphics drivers support GNOME on
Wayland in Ubuntu 16.04 LTS.

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[fcole90]

Ok, mine is 1695872

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[fcole90]

** This bug is no longer a duplicate of bug 1632772
   Login option 'GNOME on Wayland' does not start from LightDM

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1695889] Re: package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in packa

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade:
  trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README',
  which is also in package texlive-xetex 2009-15

Status in texlive-lang package in Ubuntu:
  New

Bug description:
  I've just upgraded my 12.04 Ubuntu to 14.04 version.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-lang-arabic 2013.20140215-1
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Mon Jun  5 00:18:23 2017
  DuplicateSignature: package:texlive-lang-arabic:2013.20140215-1:trying to 
overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in 
package texlive-xetex 2009-15
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in package 
texlive-xetex 2009-15
  InstallationDate: Installed on 2012-10-05 (1703 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: texlive-lang
  Title: package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade: 
trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is 
also in package texlive-xetex 2009-15
  UpgradeStatus: Upgraded to trusty on 2017-06-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1695889/+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 1695889] [NEW] package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in pac

[brenodee]

Public bug reported:

I've just upgraded my 12.04 Ubuntu to 14.04 version.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: texlive-lang-arabic 2013.20140215-1
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic i686
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: i386
Date: Mon Jun  5 00:18:23 2017
DuplicateSignature: package:texlive-lang-arabic:2013.20140215-1:trying to 
overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in 
package texlive-xetex 2009-15
ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in package 
texlive-xetex 2009-15
InstallationDate: Installed on 2012-10-05 (1703 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: texlive-lang
Title: package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade: 
trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is 
also in package texlive-xetex 2009-15
UpgradeStatus: Upgraded to trusty on 2017-06-05 (0 days ago)

** Affects: texlive-lang (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 package-conflict third-party-packages trusty

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

Title:
  package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade:
  trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README',
  which is also in package texlive-xetex 2009-15

Status in texlive-lang package in Ubuntu:
  New

Bug description:
  I've just upgraded my 12.04 Ubuntu to 14.04 version.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-lang-arabic 2013.20140215-1
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Mon Jun  5 00:18:23 2017
  DuplicateSignature: package:texlive-lang-arabic:2013.20140215-1:trying to 
overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in 
package texlive-xetex 2009-15
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/xelatex/bidi/README', which is also in package 
texlive-xetex 2009-15
  InstallationDate: Installed on 2012-10-05 (1703 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: texlive-lang
  Title: package texlive-lang-arabic 2013.20140215-1 failed to install/upgrade: 
trying to overwrite '/usr/share/doc/texlive-doc/xelatex/bidi/README', which is 
also in package texlive-xetex 2009-15
  UpgradeStatus: Upgraded to trusty on 2017-06-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1695889/+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 1695884] [NEW] usb probing malforms Epson TM-T70 label printer output

[Dariusz Gadomski]

Public bug reported:

CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
0x0202) which is used outside CUPS (via usblp driver).

No matter whether the printer is set up as a CUPS raw printer or it's
not used via CUPS (but rather via a device node under usblp control) the
formatting is broken on the printed out labels: the orientation is
different from what had been set, the fonts differ.

After blacklisting the printer in the quirks file all the problems were
gone.

My assumption is that this printer should be blacklisted by default.

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

** Summary changed:

- usb probing malforms TM-T70 output
+ usb probing malforms Epson TM-T70 output

** Summary changed:

- usb probing malforms Epson TM-T70 output
+ usb probing malforms Epson TM-T70 label printer output

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1689862] Re: gnome-shell crashed with SIGSEGV in _int_free() from __GI___libc_free() from g_free() from gweather_location_unref() from gweather_info_set_location_internal()

[Bug Watch Updater]

** Changed in: libgweather
   Status: Confirmed => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in _int_free() from
  __GI___libc_free() from g_free() from gweather_location_unref() from
  gweather_info_set_location_internal()

Status in libgweather:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/054a8a52f0b22f6ab00604d7bf8049ab48578d6d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1689862/+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 1695880] Re: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  Could not install 'gstreamer1.0-alsa'

  59.1549:package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 20:15:16 2017
  DuplicateSignature:
   package:gstreamer1.0-alsa:i386:1.8.3-1ubuntu0.2
   Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
   dpkg: error processing package gstreamer1.0-alsa:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1695880/+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 1695880] [NEW] package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Rossi Ivanova]

Public bug reported:

Could not install 'gstreamer1.0-alsa'

59.1549:package is in a very bad inconsistent state; you should
reinstall it before attempting configuration

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Mon Jun  5 20:15:16 2017
DuplicateSignature:
 package:gstreamer1.0-alsa:i386:1.8.3-1ubuntu0.2
 Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
 dpkg: error processing package gstreamer1.0-alsa:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-06-05 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gst-plugins-base1.0
Title: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  Could not install 'gstreamer1.0-alsa'

  59.1549:package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 20:15:16 2017
  DuplicateSignature:
   package:gstreamer1.0-alsa:i386:1.8.3-1ubuntu0.2
   Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
   dpkg: error processing package gstreamer1.0-alsa:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-alsa:i386 1.8.3-1ubuntu0.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1695880/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[Jeremy Bicha]

fcole90, please file a new bug for your issue.

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1393578] Re: Subpixel order not included in Mir display information

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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/1393578

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

-- 
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/1590099

Title:
  Need to support pointer confinement in Mir and toolkits using Mir

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Released
Status in MirAL:
  Fix Released
Status in libsdl2 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1

-- 
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/1663062

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 1695876] [NEW] German Documentation file displays incorrect CUPS version

[Ivy Alexander]

Public bug reported:

The /doc/de/index.html.in file in the package source has an incorrect
version number written into a header instead of using '@CUPS_VERSION@'
to populate this file as in the other languages' version of the same
file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
having the wrong version once CUPS is installed:

...

  
CUPS 2.0.2
...

instead of:

...

  
CUPS @CUPS_VERSION@
...

resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

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

Title:
  German Documentation file displays incorrect CUPS version

Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695876/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[fcole90]

Using 16.04 I can still reproduce the bug. I don't have any trace of
unity8 as well.

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

[fcole90]

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

** This bug has been marked a duplicate of bug 1632772
   Login option 'GNOME on Wayland' does not start from LightDM

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1615549] Re: Don't restrict jump list actions to Unity

[Launchpad Bug Tracker]

** Branch linked: lp:~xintx-ua/firefox/fix-1615549

-- 
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/1615549

Title:
  Don't restrict jump list actions to Unity

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox in its application .desktop file provides a couple of Desktop
  Actions ("jump list actions"), for opening a new tab or a new
  incognito tab. Since Plasma 5.6 those actions are also supported by
  KDE Plasma and there's no reason these actions should be restricted to
  Unity (OnlyShowIn=Unity).

  They are currently shown in Plasma and work just fine as I did not
  implement support for OnlyShowIn/NotShowIn in Desktop Actions (which I
  didn't see explicitly mentioned in the spec though). For Plasma 5.8
  which will have MPRIS controls in the context menu I want to add
  support for this to avoid double entries in media players (many abuse
  static Desktop Actions for player controls).

  However, I don't want to break users relying on the ability to open
  new (incognito) tabs through the task bar in Plasma, hence I request
  the OnlyShowIn for Firefox desktop actions to be dropped.
  (Alternatively "KDE" could be added, but I don't see any reason for
  not enabling them globally).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1615549/+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 1695872] [NEW] GNOME on Wayland session could not be started from lightdm

[fcole90]

Public bug reported:

GNOME on Wayland session could not be started from lightdm

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun  5 11:23:22 2017
InstallationDate: Installed on 2016-09-09 (268 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

hi Daniel,

Fantastic! I is a really good news for me.

thanks,
Mao


On Mon, Jun 5, 2017 at 12:46 PM, Daniel Axtens 
wrote:

> Hi,
>
> I can get xorg working if I do these 2 things:
>
> 1) Edit memory with gdb to add "pci:" to bus id. This is what the kernel
> patch should do. I will test the patch soon, I am just waiting for the
> kernel to build.
>
> 2) Install this /etc/X11/xorg.conf:
>
> Section "ServerFlags"
> Option "AutoAddGPU" "off"
> EndSection
>
> Section "Device"
> Identifier "dja"
> Driver "modesetting"
> BusID "pci:0007:161:0:0"
> EndSection
>
>
> This does 2 things:
>  - AutoAddGPU prevents the card from falsely being marked as GPU. I am not
> yet fully sure why that is required.
>
>  - The Device section then specifies the busid and driver specifically.
> This forces the driver to be loaded correctly.
>
> This Xorg configuration should not be required in the long term. There
> are obviously still some bugs to be fixed. But, I wanted to let you know
> that progress was being made and give you good news.
>
> Attached is a screenshot of Xeyes over KVM.
>
> Regards,
> Daniel
>
> ** Attachment added: "xeyes.png"
>https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/
> 1691991/+attachment/4889182/+files/xeyes.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691991
>
> Title:
>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>   [sudo] password for ubuntu:
>
>   X.Org X Server 1.18.4
>   Release Date: 2016-07-19
>   X Protocol Version 11, Revision 0
>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
> earlycon=pl011,mmio,0x602B console=tty0
>   Build Date: 02 November 2016  10:05:28PM
>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
> http://www.ubuntu.com/support)
>   Current version of pixman: 0.33.6
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
>   Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   pci id for fd 10: 19e5:1711, driver (null)
>   EGL_MESA_drm_image required.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>   (EE)
>   (EE) Segmentation fault at address 0xa0
>   (EE)
>   Fatal server error:
>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>   (EE)
>   (EE)
>   Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>for help.
>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
>   (EE)
>   (EE) Server terminated with error (1). Closing log file.
>   Aborted (core dumped)
>   ubuntu@ubuntu:~$
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

-- 
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/1691991

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,

[Desktop-packages] [Bug 1695864] [NEW] lightdm does not respect tap to click from GNOME/libinput settings

[fcole90]

Public bug reported:

When using lightdm as display manager and GNOME Shell as DE, with
libinput installed, lightdm doesn't respect the GNOME setting for tap to
click.

This setting is correctly respected under gdm3.

This setting is also correctly respected when using lightdm without
libinput installed.

The synaptic driver is installed as well, if it was of any interest.

Also, this seems to be fixed (or always enabled) in 17.10, as I could
use tap to click in lightdm with the Daily ISO (with GNOME DE
installed).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Jun  5 11:04:14 2017
InstallationDate: Installed on 2016-09-09 (268 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Summary changed:

- lightdm does not respect tap to click
+ lightdm does not respect tap to click from GNOME/libinput

** Summary changed:

- lightdm does not respect tap to click from GNOME/libinput
+ lightdm does not respect tap to click from GNOME/libinput settings

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

Title:
  lightdm does not respect tap to click from GNOME/libinput settings

Status in lightdm package in Ubuntu:
  New

Bug description:
  When using lightdm as display manager and GNOME Shell as DE, with
  libinput installed, lightdm doesn't respect the GNOME setting for tap
  to click.

  This setting is correctly respected under gdm3.

  This setting is also correctly respected when using lightdm without
  libinput installed.

  The synaptic driver is installed as well, if it was of any interest.

  Also, this seems to be fixed (or always enabled) in 17.10, as I could
  use tap to click in lightdm with the Daily ISO (with GNOME DE
  installed).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:04:14 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695864/+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 1695839] [NEW] firefox unstable

[Hadmut Danisch]

Public bug reported:

Sorry, I can't give a more precise report, just to give some feedback:

Since latest update of firefox in 16.04, firefox is quite unstable and
crashes or freezes several times a day here.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 52.0.2+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hadmut 4148 F pulseaudio
BuildID: 20170329150444
Channel: Unavailable
CurrentDesktop: XFCE
Date: Mon Jun  5 09:55:11 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Plugins:
 Windows Media Player Plug-in - 
/usr/lib/mozilla/plugins/gecko-mediaplayer-wmp.so
 RealPlayer 9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-rm.so
 QuickTime Plug-in 7.6.9 - /usr/lib/mozilla/plugins/gecko-mediaplayer-qt.so
 DivX Browser Plug-In - /usr/lib/mozilla/plugins/gecko-mediaplayer-dvx.so
 mplayerplug-in is now gecko-mediaplayer 1.0.8 - 
/usr/lib/mozilla/plugins/gecko-mediaplayer.so
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profile3Extensions: extensions.sqlite corrupt or missing
Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile3Locales: extensions.sqlite corrupt or missing
Profile3PrefSources: prefs.js
Profile3Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile0 - LastVersion=46.0.1/20160511223818 (Out of date)
 Profile1 - LastVersion=36.0.1/20150306140254 (Out of date)
 Profile2 (Default) - LastVersion=52.0.2/20170329150444
 Profile3 - LastVersion=52.0.2/20170329150444
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1695839

Title:
  firefox unstable

Status in firefox package in Ubuntu:
  New

Bug description:
  Sorry, I can't give a more precise report, just to give some feedback:

  Since latest update of firefox in 16.04, firefox is quite unstable and
  crashes or freezes several times a day here.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 52.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 4148 F pulseaudio
  BuildID: 20170329150444
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Mon Jun  5 09:55:11 2017
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  Profile0Extensions: extensions.sqlite corrupt or missing