[Desktop-packages] [Bug 1718083] Re: UIFe: Add Additional Printer Settings button

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/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/1718083

Title:
  UIFe: Add Additional Printer Settings button

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

Bug description:
  Impact
  ==
  The Ubuntu Desktop Team would like to add a button to the "Printers" part of 
the Settings app (gnome-control-center) named "Additional Printer Settings" 
that will open system-config-printer. system-config-printer has been part of 
the Ubuntu default install for years.

  Justification
  ==
  The GNOME integrated Printer Settings is nice but it still misses a few 
settings that were easily configurable in Ubuntu 17.04. The most prominent 
missing settings is Printer Sharing. See GNOME upstream bug 
https://bugzilla.gnome.org/692532

  Hopefully, we can drop the button before 18.04 LTS is released.

  Notifications
  =
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020539.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007405.html

  Other Info
  ==
  At the same time, we'll replace one string in Ubuntu Dock settings from 
"Screen Placement" to "Placement on Screen". (LP: #1715869)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718083/+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 1718612] Re: Align Dock UI better with other panels

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/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/1718612

Title:
  Align Dock UI better with other panels

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

Bug description:
  Multiple changes suggested by upstream for our own ubuntu dock panel:
  - "Screen position" to be replaced by "Position on screen" (already covered 
by the other UIFe in the same upload)
  - add slighter larger marging (there is no icon in this panel, and so, the 
rows are smaller
  - only display "Show on" if multiple screens are available (doesn't make 
sense when there is only one screen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718612/+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 1718839] Re: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build

[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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1718839

Title:
  nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After installing new drivers when I restart, it shows crash report.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 340.104-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-11-generic
  Date: Thu Sep 21 15:08:42 2017
  DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2017-04-03 (171 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageVersion: 340.104-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+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 1687089] Re: Can't access websites on DSL (PPPoE) connection

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't access websites on DSL (PPPoE) connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I found strange problem with PPPoE connection on Ubuntu 17.04 (16.10 is 
affected too).
  To reproduce this problem you need to connect to PPPoE ISP and try to open 
some sites in browser. It happens every time on my machine. However I still can 
resolve ip addreses with nslookup. And Google still working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 28 17:45:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-04-25 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.1.1 dev enp0s25 proto static metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.2 metric 100
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=uk
   TERM=xterm
   PATH=(custom, no user)
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH

   enp0s25  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
З’єднання Ethernet 1  f021ebe1-6abd-4196-bc04-ec7b5a5fe598  
/org/freedesktop/NetworkManager/ActiveConnection/30 
   wlp6s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
------  

   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1687089/+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 1718839] [NEW] nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build

[Biren]

Public bug reported:

After installing new drivers when I restart, it shows crash report.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nvidia-340 340.104-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 4.13.0-11-generic
Date: Thu Sep 21 15:08:42 2017
DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2017-04-03 (171 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageVersion: 340.104-0ubuntu1
Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~rc4
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  After installing new drivers when I restart, it shows crash report.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 340.104-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-11-generic
  Date: Thu Sep 21 15:08:42 2017
  DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2017-04-03 (171 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageVersion: 340.104-0ubuntu1
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+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 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

[Hooman]

Also, I think this is a critical bug, because lock screen is essential
in keeping users safe, when they leave their computers unattended. I
think the importance of this bug should not be Low.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.


  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
 array [
object path "/org/gnome/SessionManager/Inhibitor1686"
 ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId 
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason 
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.


  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+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 13319] Re: nautilus should sort by extensions

[Alexandra Tilbrook]

2017 and this STILL exists???

I have a bunch of files for my TRS80 Color Computer (For DriveWire) and
I need to sort out the CAS, DSK and ROM Files. Those are the extensions.

Here's a small sample and I have "Sort by type" selected...

Wildcatting (1981)(Tandy)[26-3067].rom
Zaxxon (1983)(Tandy)[26-3062].cas
Zaxxon (1983)(Tandy)[26-3062].rom
Zone Runner (1987)(Tandy)[26-3286].dsk

I tried the steps to include "MIME Type" but those are sorted as
"application/octet-stream". I just need to have .cas files with .cas
files, ditto for .rom files and .dsk files. How is this not useful? I'm
in agreement with #4. I swear the GNOME people are trying to dumb down
Linux users.

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

Title:
  nautilus should sort by extensions

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  In Warty I have a folder with tons of still pics, bmp and jpg, and a few WMV
  video files.
  Normally when I sort them by type, all the video files are put the bottom, 
which
  make sit easy to find them.

  Now with Hoary, it doesn't work anymore, the WMV files are in the middle of 
all
  the bmp and jpg files, it's a pain to find them :o(

  I think Warty used the file extension to sort the files, hence "WMV" came 
after
  "bmp" then "jpg".
  But it looks like Hoary uses the "MIME" (?) description.

  "bmp" is called "Windows BMP image" and "WMV" is called "Microsfot WMV video".
  "Windows" comes after "Microsoft", and here you go, the video files end up 
lost
  in the middle of all the other image types :-/
  Is there a way to change the sorting mechanism/method back to what it used to 
be
  ? Or is it configurable somewhere ?

  http://bugzilla.gnome.org/show_bug.cgi?id=168663:
  http://bugzilla.gnome.org/show_bug.cgi?id=168663

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/13319/+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 871325] Re: Implement Unity Launcher API in Firefox for downloads' progress and quicklist

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Invalid

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

Title:
  Implement Unity Launcher API in Firefox for downloads' progress and
  quicklist

Status in Mozilla Firefox:
  Invalid
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu, Firefox should use the Unity Launcher API to show progress of the 
downloads and to show a quicklist (for example, New Window).
  There's yet an extension about the downloads' progress: UnityFox 
(https://launchpad.net/unityfox).
  Could you integrate the extension in Firefox by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/871325/+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 1718826] Re: gnome-shell crashed with signal 5

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1556601, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954765/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954767/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954770/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954771/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954772/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954773/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718826/+attachment/4954774/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1556601
   gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() 
["Connection to xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  one more failure while trying to use activity hotcorner

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Sep 21 17:35:09 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-07-08 (75 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-07-19 (64 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718826/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

** Tags added: originate-from-1715596 somerville xenial

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1718824] [NEW] The analogue audio does not work on the Dell USB Dock

[Hui Wang]

Public bug reported:

Steps:
1. Cold boot system with BME/IE connected
2. Plug in a speaker to Line-out jack
3. Set Analog Stereo Output from Sound settings

Expected results: Line-out port can work

Actual results: Line-out port not work

** Affects: hwe-next
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New

** Affects: pulseaudio (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1715596 somerville xenial

** Changed in: hwe-next
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Yuan-Chen Cheng]

** Tags added: risk

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  Triaged
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1718809] Re: nautilus crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1676799, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954730/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954732/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954737/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954738/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954739/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954740/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718809/+attachment/4954741/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1676799

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I did not realize what caused that mistake.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 20:43:38 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-06-08 (104 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1718809/+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 1718170] Re: Search broken after snapd is restarted

[Robert Ancell]

commit 3e8a4ed577b48c485039d2b0d00f2936da92a00d
Author: Robert Ancell 
Date:   Thu Sep 21 12:55:12 2017 +1200

snap: Don't use a common SnapdClient

If the client fails (e.g. snapd is restarted) this means that snapd 
operations
don't restart. Since GNOME Software runs as a background process this is
unrecoverable.

I could have checked for connection failures and reconnected when these 
occurred
but this seems simpler. The cost of a SnapdClient is low (basically a single
socket connection).

This reverts the change in 696d076.


** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Search broken after snapd is restarted

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Test Case:
  1. Start gnome-software and close it
  2. Make sure gnome-software is still running in the background
  $ pgrep -l gnome-software
  3. Restart snapd
  $ sudo service snapd restart
  4. Open gnome-software
  5. Click on 'Search'
  6. Search 'gedit'

  Expected result
  There should be at least 2 records for gedit as a deb and as a snap

  Actual result
  There is no result and after a while only debs are shown in the list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:14:03 2017
  InstallationDate: Installed on 2013-09-03 (1476 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu1
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1718170/+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 1718552] Re: gnome-shell uses lots of memory

[Claude Champagne]

It was on a fresh install in Virtual Box, with only Open Weather as
extension, on the Ubuntu session, nothing else.

That said, I tried earlier Ubuntu 17.10, but with the Pop!_OS PPA. And
it was taking less RAM.

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

Title:
  gnome-shell uses lots of memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of
  memory, even more after opening and closing just a few apps
  (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb.

  Also,the CPU usage is quite high too, even if nothing is running in
  the foreground.

  See screen captures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718552/+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 1718793] Re: Unable to unlock account to enable auto-login

[Jeremy Bicha]

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

Title:
  Unable to unlock account to enable auto-login

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

Bug description:
  Please take a look @ screencast. Account isn't unlocked after entering 
password and setting window disappears.
  Can assist with fixing it, but need guidelines how to do it.

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

** Branch linked: lp:~mozillateam/firefox/firefox.zesty

** Branch linked: lp:~mozillateam/firefox/firefox.trusty

-- 
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 1559396] Re: gimp-2.8 crashed with SIGSEGV in g_build_path_va()

[Launchpad Bug Tracker]

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

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

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

Title:
  gimp-2.8 crashed with SIGSEGV in g_build_path_va()

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  alteração nas preferencias , apois isso feito fechei e depois não
  abriu mais o gimp

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Mar 19 01:02:00 2016
  ExecutablePath: /usr/bin/gimp-2.8
  InstallationDate: Installed on 2016-03-05 (14 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160103)
  ProcCmdline: gimp-2.8
  SegvAnalysis:
   Segfault happened at: 0x7fee0395eda2:cmpb   $0x0,(%rax)
   PC (0x7fee0395eda2) ok
   source "$0x0" ok
   destination "(%rax)" (0x207974706d4520) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gimp
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_build_filename () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   gtk_rc_find_pixmap_in_path () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so
  Title: gimp-2.8 crashed with SIGSEGV in g_build_filename()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

-- 
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 1718793] [NEW] Unable to unlock account to enable auto-login

[Alex]

Public bug reported:

Please take a look @ screencast. Account isn't unlocked after entering password 
and setting window disappears.
Can assist with fixing it, but need guidelines how to do it.

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

** Attachment added: "Peek 2017-09-21 23-45.gif"
   
https://bugs.launchpad.net/bugs/1718793/+attachment/4954693/+files/Peek%202017-09-21%2023-45.gif

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

Title:
  Unable to unlock account to enable auto-login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Please take a look @ screencast. Account isn't unlocked after entering 
password and setting window disappears.
  Can assist with fixing it, but need guidelines how to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718793/+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 1716009] Re: problem with the sound since the latest update

[FilipGH]

the problem is still available - there has been no change since the date
of publication - the hitherto released updates have not resolved it

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

Title:
  problem with the sound since the latest update

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716009/+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 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

[Brian Murray]

On Thu, Sep 21, 2017 at 02:03:41PM -, Jarno Suni wrote:
> Brian, however, as you installed the kernel by apt-get install, the
> kernel becomes manually installed, and will not later be removed by
> 'sudo apt autoremove', unless you change it to be marked as
> automatically installed.

No, this is not the behavior I observed. After installing a new kernel
version via update-manager or 'sudo apt-get install' on Ubuntu 16.04, 'sudo
apt autoremove' does the right thing and wants to remove my third newest
kernel.

--
Brian Murray

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

Title:
  By default settings unattended-upgrade is unable to automatically
  remove packages that become unused in conjunction with updating by
  other software.

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+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 1718671] Re: Gnome-Shell crashes after unlocking Lockscreen

[Brian Murray]

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

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

Title:
  Gnome-Shell crashes after unlocking Lockscreen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  lsb_release  -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  gnome-shell:
Installed: 3.26.0-0ubuntu1
Candidate: 3.26.0-0ubuntu1
Version table:
   *** 3.26.0-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  When using Super+L to lock the screen first all is working as
  intended. After some time i want to unlock the Screen. I provide my
  credentials and now all application that were open before are closed.
  It looks like a new Session.

  This happens only after some Time has passed. If I lock the screen and
  immediately unlock it, all is working as intended

  I attached parts of journalctl:
  It seems a segfault causing parts of gnome getting killed by a SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718671/+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 1718671] [NEW] Gnome-Shell crashes after unlocking Lockscreen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,

lsb_release  -rd
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

gnome-shell:
  Installed: 3.26.0-0ubuntu1
  Candidate: 3.26.0-0ubuntu1
  Version table:
 *** 3.26.0-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

When using Super+L to lock the screen first all is working as intended.
After some time i want to unlock the Screen. I provide my credentials
and now all application that were open before are closed. It looks like
a new Session.

This happens only after some Time has passed. If I lock the screen and
immediately unlock it, all is working as intended

I attached parts of journalctl:
It seems a segfault causing parts of gnome getting killed by a SIGSEGV

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


** Tags: bot-comment
-- 
Gnome-Shell crashes after unlocking Lockscreen
https://bugs.launchpad.net/bugs/1718671
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell 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 1718552] Re: gnome-shell uses lots of memory

[Sebastien Bacher]

Well, none of the distribution you have been using had GNOME 3.26 either
which is brand new.

gnome-shell uses 236M here on my uptodate artful amd64 installation with
a session which has been open for a day and cpu usage is low

in summary, right the situation is not normal and would deserve some
debugging, it could come from your configuration (do you use some
extension?) or be a bug (likely upstream since we have little
modifications to the shell). Do you see the same issue under a GNOME
session rather than an Ubuntu one? Do you have it if you switch to
Adwaita?

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

Title:
  gnome-shell uses lots of memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of
  memory, even more after opening and closing just a few apps
  (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb.

  Also,the CPU usage is quite high too, even if nothing is running in
  the foreground.

  See screen captures.

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

[dino99]

** Description changed:

  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that session crashing. And then relogin to a wayland session has failed, but a 
xorg one is ok. (not rebooted at time)
+ 
+ note:
+ the relogin problem is not met after a cold boot; so this seems a 
transitional issue due to some of the latest packages upgrade (needing a reboot 
to work as expected. Maybe that crash also is related to that fact)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that session crashing. And then relogin to a wayland session has failed, but a 
xorg one is ok. (not rebooted at time)
  
  note:
- the relogin problem is not met after a cold boot; so this seems a 
transitional issue due to some of the latest packages upgrade (needing a reboot 
to work as expected. Maybe that crash also is related to that fact)
+ the relogin problem is not met after a cold boot; so this seems a 
transitional issue due to some of the latest daily packages upgrade (needing a 
reboot to work as expected. Maybe that crash also is related to that fact)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard 

[Desktop-packages] [Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed

[Wolf Rogner]

Which Thinkpad? None. Tlp comes by default in every Ubuntu installation
(even 17.10)

Removing tlp allows the battery to be loaded up to 98%.
On other machines up to 100% (newer system).
The battery life is extended after deinstall by approx 15%. (I don't have an 
exact test suite though, just average work).

Currently I experiment with Ubuntu 17.10.
I have tlp deinstalled and
a) my network is reasonable stable
b) bluetooth is broken
c) Firefox does not cause high CPU and fan speeds

Haven't got the time to experiment with tlp. At least, it's
deinstallable on its own.

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

Title:
  Slow Firefox performance and high CPU load when tlp is installed

Status in firefox package in Ubuntu:
  New
Status in tlp package in Ubuntu:
  New

Bug description:
  After installing Firefox 55 the browser generates huge cpu load,
  startup is extremely slow (it takes > 10s for the taskbar to accept
  entries after launch (this is new to 55)

  Due to high cpu load the computer tends to overheat, ventilation jumps
  in making the machine extremely loud.

  Using Chromium does not show these symptoms (on the same page).

  
  ---
  LSB Ubuntu 17.04 (budgie desktop)
  firefox:
Installed: 55.0.1+build2-0ubuntu0.17.04.2
Candidate: 55.0.1+build2-0ubuntu0.17.04.2
Version table:
   *** 55.0.1+build2-0ubuntu0.17.04.2 500
  500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   50.1.0+build2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.1+build2-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BuildID: 20170814193419
  CurrentDesktop: Budgie:GNOME
  Date: Thu Aug 17 16:30:30 2017
  InstallationDate: Installed on 2017-05-25 (83 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711382/+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 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Launchpad Bug Tracker]

This bug was fixed in the package gdk-pixbuf - 2.36.10-2

---
gdk-pixbuf (2.36.10-2) unstable; urgency=medium

  * Add git_fix-tiff-build.patch:
- Backport patch to fix tiff loader build (LP: #1718526)

 -- Jeremy Bicha   Wed, 20 Sep 2017 19:04:33 -0400

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+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 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

[Olivier Tilloy]

libreoffice base still crashing at startup on xenial i386 with kernels
4.4.0-96.119 (in xenial-security) and 4.4.0-97.120 (in xenial-proposed)

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

Title:
  linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-
  image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression:
  many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in commons-daemon package in Ubuntu:
  Confirmed
Status in eclipse package in Ubuntu:
  Confirmed
Status in imagej package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in octave package in Ubuntu:
  Confirmed
Status in python-jpype package in Ubuntu:
  Confirmed
Status in rustc package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1718736] Re: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[dino99]

** Description changed:

  I was using chromium-browser when first a general freeze has happened.
- Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)
+ Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that session crashing. And then relogin to a wayland session has failed, but a 
xorg one is ok. (not rebooted at time)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
-  PC (0x7f6714b10d81) ok
-  source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
+  PC (0x7f6714b10d81) ok
+  source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
+  destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
-  g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that session crashing. And then relogin to a wayland session has failed, but a 
xorg one is ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade 

[Desktop-packages] [Bug 1718737] Re: Firefox: all tabs loose page display and internet access but new tabs work normally

[Michael F Winthrop]

The following kern.log is a record of the kernel events. Please note
that I used the widget to close the Ethernet connection, and note
subsequent issues. Also note that the WiFi connection has a lease time
for a nailed up connection IP address (??)

dad@dad314159:/var/log$ tail kern.log -n 100
Sep 21 10:53:51 dad314159 sddm[3332]: Session 
"/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
Sep 21 10:53:51 dad314159 sddm[3332]: Adding cookie to 
"/var/run/sddm/{cfd8e347-ff7a-40eb-936b-7b97cbf4a408}"
Sep 21 10:53:51 dad314159 sddm-helper[3622]: [PAM] Starting...
Sep 21 10:53:51 dad314159 sddm-helper[3622]: [PAM] Authenticating...
Sep 21 10:53:51 dad314159 sddm-helper[3622]: [PAM] returning.
Sep 21 10:53:51 dad314159 sddm[3332]: Authenticated successfully
Sep 21 10:53:51 dad314159 sddm-helper[3622]: Starting: "/etc/sddm/Xsession" 
"/usr/bin/startkde"
Sep 21 10:53:51 dad314159 sddm-helper[3694]: Adding cookie to 
"/home/dad/.Xauthority"
Sep 21 10:53:51 dad314159 sddm[3332]: Session started
Sep 21 10:53:51 dad314159 kernel: [   11.697101] audit: type=1400 
audit(1506005631.852:30): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=3747 comm="usb" capability=35  
capname="wake_alarm"
Sep 21 10:53:51 dad314159 kernel: [   11.702854] usblp0: removed
Sep 21 10:53:51 dad314159 kernel: [   11.718373] usblp 2-2.2:1.1: usblp0: USB 
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
Sep 21 10:53:56 dad314159 NetworkManager[956]:   [1506005636.1609] 
manager: WiFi hardware radio set enabled
Sep 21 10:53:56 dad314159 NetworkManager[956]:   [1506005636.1610] 
manager: WWAN hardware radio set enabled
Sep 21 10:53:56 dad314159 kernel: [   16.467172] audit: type=1400 
audit(1506005636.620:31): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/4030/status" 
pid=4030 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 21 10:53:56 dad314159 kernel: [   16.467176] audit: type=1400 
audit(1506005636.620:32): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/sys/devices/system/node/" pid=4030 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep 21 10:53:56 dad314159 kernel: [   16.467178] audit: type=1400 
audit(1506005636.620:33): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/4030/status" 
pid=4030 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 21 10:53:56 dad314159 kernel: [   16.495191] audit: type=1400 
audit(1506005636.648:34): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/etc/mysql/my.cnf.fallback" pid=4030 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep 21 10:53:56 dad314159 kernel: [   16.521493] audit: type=1400 
audit(1506005636.676:35): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/4031/status" 
pid=4031 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 21 10:53:56 dad314159 kernel: [   16.524452] audit: type=1400 
audit(1506005636.680:36): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/sys/devices/system/node/" pid=4031 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Sep 21 10:53:56 dad314159 kernel: [   16.524699] audit: type=1400 
audit(1506005636.680:37): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/proc/4031/status" 
pid=4031 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.1598] device 
(wlp12s0): re-acquiring supplicant interface (#1).
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.1983] device 
(wlp12s0): supplicant interface state: starting -> ready
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.1984] device 
(wlp12s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.7826] device 
(wlp12s0): supplicant interface state: ready -> inactive
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.8650] 
policy: auto-activating connection 'Disco'
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.8708] device 
(wlp12s0): Activation: starting connection 'Disco' 
(facc7167-12ef-42d2-a39f-35aaf8a261f5)
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.8910] device 
(wlp12s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.8937] device 
(wlp12s0): state change: prepare -> config (reason 'none') [40 50 0]
Sep 21 10:53:58 dad314159 NetworkManager[956]:   [1506005638.8958] device 
(wlp12s0): Activation: (wifi) access point 'Disco' has security, but secrets 
are 

[Desktop-packages] [Bug 1718742] Re: gvfsd-mtp crashed with SIGSEGV

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954583/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954585/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954588/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954589/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954590/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954591/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718742/+attachment/4954592/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 19:31:43 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-10-16 (706 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.8 /org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fdf574f75a9:mov0x18(%rax),%rax
   PC (0x7fdf574f75a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1718742/+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 1718736] gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Apport retracing service]

StacktraceTop:
 g_type_check_instance_is_fundamentally_a 
(type_instance=type_instance@entry=0x55bebd461b50, 
fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x55bebd461b50) at ../../../../gobject/gobject.c:3180
 g_weak_ref_get (weak_ref=) at ../../../../gobject/gobject.c:4353
 g_settings_backend_invoke_closure (user_data=0x7f6704010dc0) at 
../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x55bebd4660d0) at ../../../../glib/gmain.c:3148

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+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 1718736] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1718736/+attachment/4954571/+files/StacktraceSource.txt

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+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 1718736] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718736/+attachment/4954570/+files/Stacktrace.txt

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+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 1718552] Re: gnome-shell uses lots of memory

[Claude Champagne]

While it is true that Gnome is the desktop that uses the most RAM, I've
never seen gnome-shell use that much RAM or CPU in any Linux
distribution.

Just to make you think a bit, System76 decided to change their GTK theme
based on Adapta because they noticed it was causing high memory usage.
Pop!_OS is based on Ubuntu and it takes less RAM...

I have tried many Gnome distros, Fedora, Manjaro, OpenSuse, and none
took that much RAM. And that's not talking about CPU usage.

So, please, take the time to review this before shoveling the problem to
upstream.

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

Title:
  gnome-shell uses lots of memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of
  memory, even more after opening and closing just a few apps
  (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb.

  Also,the CPU usage is quite high too, even if nothing is running in
  the foreground.

  See screen captures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718552/+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 1718736] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718736/+attachment/4954572/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718736/+attachment/4954551/+files/CoreDump.gz

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+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 1718736] [NEW] gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[dino99]

Public bug reported:

I was using chromium-browser when first a general freeze has happened.
Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & 
other keyboard combinations to unlock the wayland session, but i only got that 
crash. And then relogin to a wayland session has failed, but a xorg one is ok. 
(not rebooted at time)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 21 19:01:49 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6714b10d81 
:movzbl 0x14(%rdx),%eax
 PC (0x7f6714b10d81) ok
 source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

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

Title:
  gsd-keyboard crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

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

Bug description:
  I was using chromium-browser when first a general freeze has happened.
  Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc 
& other keyboard combinations to unlock the wayland session, but i only got 
that crash. And then relogin to a wayland session has failed, but a xorg one is 
ok. (not rebooted at time)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 19:01:49 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6714b10d81 
:  movzbl 0x14(%rdx),%eax
   PC (0x7f6714b10d81) ok
   source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gsd-keyboard crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+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 1713285] Re: 17.10: Missing Add-ons category

[Iain Lane]

https://git.gnome.org/browse/gnome-
software/commit/?id=2e5bb73486ae15e53498f86afea1e284428e5059

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  17.10: Missing Add-ons category

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  I don't see the Add-ons category in GNOME Software's front page.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.25.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 26 18:56:47 2017
  EcryptfsInUse: Yes
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.25.91-1ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1713285/+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 1718737] [NEW] Firefox: all tabs loose page display and internet access but new tabs work normally

[Michael F Winthrop]

Public bug reported:

Significant problems with KUBUNTU 16.04.3 WiFi.

I had been an early adopter of KUBUNTU 16.04, before the warnings about
on-line upgrade from KUBUNTU 14.04 came out. To solve those problems, I
re-installed KUBUNTU 16.04.3 from disk over the system partition of my
PC while retaining my user partition, applications, and downloads
partitions (also WIN10) KUBUNTU 16.04 WiFi was bad before and remained
bad after. KUBUNTU 14.04 had some problems, but that eventually was
resolved.

Most recent complaint is Firefox will loose all displayed tabbed web
pages and those web pages cannot be refreshed. Opening a new web tab
works perfectly. Pasting a broken web page URL into a new tab works
perfectly.

For some time I have had WiFi failures on boot.The ifconfig initially
said there was no WiFi device.  IMPORTANT NOTE: Ethernet has always
worked and I have had to string a cat5 cable across my house several
times to get network access for repairs. I installed network-manager (it
was missing ??) and WiFi showed up via ifconfig.

After installing network-manager (again) ifconfig showed WiFi with a new
ID: wlp12s0. Next I manually inserted this new ID into
/etc/network/interfaces because wlan0 is apparently OBE:

#--- wlp12s0  ---wlan--
auto wlp12s0

iface wlp12s0 inet static
  address 192.168.99.12
  netmask 255.255.255.0 
  gateway 192.168.99.1
  wpa-ssid Disco
  wpa-psk pre-shared-key

At this point, WiFi would work about 50% of the time on boot/reboot.
ifconfig always shows it as configured. The network-manager widget only
shows it when it is configured via boot-up. If boot-up fails to
configure WiFi the widget only shows Ethernet. It is displayed in
network-manager but it is not available to connect. Network-manager
showed Ethernet as available to turn OFF. Eventually I tried to put
Ethernet up/down in as an option and eliminated Ethernet always up (this
was explicitly not set to be always up, but that was the case anyhow)
Now Ethernet up/down is always up on boot-up.

BEGIN DIGRESSION
When I looked at the password, I noted that in network-manager there is a 
wallet requirement to access the password (if I chose to use it) so I tried 
that. That accomplished requiring me to unlock the wallet on the occasions when 
WiFi was working. However WiFi did operate more often the before. I made the 
password available without wallet since it did no useful help in this problem. 
This improve operations even more, but not reliably at all times,
END OF DIGRESSION

I next installed WiFiRadar which sometimes would run and other times
would not.(It remains installed but I am not using it now. In
particular, it could not raise WiFi from the dead when it did execute
properly. It did allow me to correct some elements of the WiFi
configuration that network-manager had wrong. It fixed the password
issue.

An odd part of this problem still occurs when WiFi does work (now about
80% of the time): ifupdown enp9s0 is connected as UP when WiFi is also
UP on boot-up. In this situation Ethernet interferes with network access
as if it is a valid connection to the same router as WiFi. When I
disconnect ifupdown enp9s0, it remains available for connect but WiFi no
longer is interfered with by the Ethernet connection that was not there.
When I run ifconfig enp9s0 down, ifconfig no longer shows enp9s0 but the
widget still shows ifupdown enp9s0 available to connect.

The Firefox issue appears to not be related to that application
directly.

I have a broadcom WiFi device in a Dell 1525 Inspiron laptop.

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

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

Title:
  Firefox: all tabs loose page display and internet access but new tabs
  work normally

Status in gnome-nettool package in Ubuntu:
  New

Bug description:
  Significant problems with KUBUNTU 16.04.3 WiFi.

  I had been an early adopter of KUBUNTU 16.04, before the warnings
  about on-line upgrade from KUBUNTU 14.04 came out. To solve those
  problems, I re-installed KUBUNTU 16.04.3 from disk over the system
  partition of my PC while retaining my user partition, applications,
  and downloads partitions (also WIN10) KUBUNTU 16.04 WiFi was bad
  before and remained bad after. KUBUNTU 14.04 had some problems, but
  that eventually was resolved.

  Most recent complaint is Firefox will loose all displayed tabbed web
  pages and those web pages cannot be refreshed. Opening a new web tab
  works perfectly. Pasting a broken web page URL into a new tab works
  perfectly.

  For some time I have had WiFi failures on boot.The ifconfig initially
  said there was no WiFi device.  IMPORTANT NOTE: Ethernet has always
  worked and I have had to string a cat5 cable across my house several
  times to get network access for repairs. I installed network-manager
  (it was missing ??) and 

[Desktop-packages] [Bug 1718680] Re: gnome-shell sigfault in libxkbcommon

[Cliff Carson]

I see nothing for this time/date (2017-09-21 05:35) in the /var/crash.
The system didn't indicate there was a problem only saw a partial
desktop background screen for 10-20 seconds then the screen when back to
the login screen again.

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

Title:
  gnome-shell sigfault in libxkbcommon

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Intermittent problem shows up as the desktop background partially
  opens after login and then freezes.  After a short pause the screen
  clears and goes back to the login screen.  Logging in again will
  result in a working system.  Add the file PartialDT.txt which is the
  syslog portion that I think shows the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 09:34:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-24 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718680/+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 1718731] [NEW] nm-applet doesn't indicate by default when networks are unencrypted

[Jeff Abrahamson]

Public bug reported:

It looks like nm knows about security, because `nmcli device wifi list`
shows a column about security.  But the graphical indicator doesn't warn
me (nor is there a notification on connection) when the wifi network is
unencrypted.

This is a security-related feature request: I think it should provide a
warning, even if that warning is unactionnable beyond choosing possibly
not to remain connected or to restrict some activities.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager-gnome 1.4.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: i3
Date: Thu Sep 21 12:38:51 2017
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-12-17 (644 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 10.176.32.1 dev wlp6s0 proto static metric 600 
 10.176.32.0/20 dev wlp6s0 proto kernel scope link src 10.176.43.35 metric 600 
 10.226.16.20 via 10.176.32.1 dev wlp6s0 proto dhcp metric 600 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to zesty on 2017-06-06 (107 days ago)
nmcli-dev:
 DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
docker0 16dafb11-675e-4681-8ab2-77ab905406a6  
/org/freedesktop/NetworkManager/ActiveConnection/0  
 wlp6s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  NYPL  
  3d406aa5-be38-4abe-a6c7-150fed39f880  
/org/freedesktop/NetworkManager/ActiveConnection/10 
 lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  nm-applet doesn't indicate by default when networks are unencrypted

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

Bug description:
  It looks like nm knows about security, because `nmcli device wifi
  list` shows a column about security.  But the graphical indicator
  doesn't warn me (nor is there a notification on connection) when the
  wifi network is unencrypted.

  This is a security-related feature request: I think it should provide
  a warning, even if that warning is unactionnable beyond choosing
  possibly not to remain connected or to restrict some activities.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-gnome 1.4.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: i3
  Date: Thu Sep 21 12:38:51 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-17 (644 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 10.176.32.1 dev wlp6s0 proto static metric 600 
   10.176.32.0/20 dev wlp6s0 proto kernel scope link src 10.176.43.35 metric 
600 
   10.226.16.20 via 10.176.32.1 dev wlp6s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to zesty on 2017-06-06 (107 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
docker0  

[Desktop-packages] [Bug 1718364] Re: Character Map window picture missing in help

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

I can confirm the image is missing from the Getting started section in
help (gucharmap 1:10.0.1-1 on Ubuntu artful).

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

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

Title:
  Character Map window picture missing in help

Status in gucharmap package in Ubuntu:
  Confirmed

Bug description:
  Character Map help I find: When you start Character Map, the following window 
is displayed.
  but the picture of the window is missing.
  see my screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gucharmap 1:10.0.1-1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 09:43:58 2017
  ExecutablePath: /usr/bin/gucharmap
  InstallationDate: Installed on 2017-09-12 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170911)
  SourcePackage: gucharmap
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1718364/+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 1555569] Re: Use 'title' field for snap apps

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Use 'title' field for snap apps

Status in Snapcraft:
  New
Status in Software Center Agent:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps show using the snap 'name', which has a limited character set and is 
not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is 
more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd 
supports this field we should use it in GNOME Software.

  [Test Case]
  1. Start GNOME Software
  2. Search for 'moon'

  Expected result:
  A snap called 'Moon Buggy' is shown.

  Observed result:
  A snap called 'moon-buggy' is shown.

  [Regression Potential]
  The fix is to use the new field if it is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/169/+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 1685141] Re: System freezes after locking screen

[Paulo Canedo]

Also affects me. AMD GPU.

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

Title:
  System freezes after locking screen

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  When locking the screen or whenever the screensaver starts
  automatically, I cannot log in again, but my system completely freezes
  and I have to restart the computer. In most cases I was able to do the
  restart by pressing Alt-REISUB, in some cases however I had to do a
  hard reset. This is a new bug in zesty (Ubuntu 17.04). In the previous
  version everything worked fine. I tested both the upgrade and a fresh
  new installation on the same computer. Package is gnome-screensaver
  version 3.6.1-7ubuntu5.

  I attach an excerpt from my syslog. Hope this might help to find the
  bug.

  I installed zesty on another computer (laptop) as well and there the
  bug did not appear. So I assume it has something to do with the
  installed graphics card or graphics driver. Installed graphics card in
  this case is: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1).

  Update: After a few days the bug now appears on the second computer as
  well. However, I could unlock the screen and continue working, until
  suddenly (an hour later or so) the whole system froze. I add the
  kernel-nullpointer-dereference syslog of this event (syslog2.txt) to
  the attachments for this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+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 1704904] Re: Shows 'core' snap as an application

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Shows 'core' snap as an application

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software shows the 'core' snap as an application. It should be 
correctly marked as a runtime so GNOME Software will display it more 
appropriately.

  [Test Case]
  1. Ensure at least one snap is installed so the core snap has been installed.
  2. Open GNOME Software.
  3. Browse to installed apps.

  Expected result:
  'core' is shown as an add-on.

  Observed result:
  'core' is shown in the app list.

  [Regression Potential]
  Fix is to tag the app object as a 'runtime' in GNOME Software based on the 
snap 'type' field. This could expose new bugs in the runtime code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704904/+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 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1708140/+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 1706478] Re: Show promoted snap in "Featured" section

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Show promoted snap in "Featured" section

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Featured" banner only shows hard-coded .debs that are available. This 
should show the currently promoted snap.

  [Test Case]
  1. Open GNOME Software
  2. Look at featured section

  Expected result:
  The currently promoted snap is shown.

  Observed result:
  A hard-coded .deb is shown.

  [Regression Potential]
  The change is to use the first snap from the "featured" store section and 
show it here. If there is a screenshot with the name "banner" then this is used 
as the promotion image (and not shown in screenshots).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1706478/+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 1704888] Re: Doesn't download snap icons greater than 65kB

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Doesn't download snap icons greater than 65kB

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Won't Fix
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Due to a hard-coded limitation in the gnome-software snap support it is 
unable to download icons greater than 65kB in size (e.g. pin-town).

  [Test Case]
  1. Install pin-town from the command line (sudo snap install pin-town
  2. Open GNOME Software
  3. Go to installed apps

  Expected result:
  pin-town is shown

  Observed result:
  pin-town is not shown (due to failure to download icon).

  [Regression Potential]
  Solution is to backport snapd code from gnome-software 3.24. This has a risk 
of introducing new bugs. The code has been used in 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704888/+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 1705953] Re: Show only snaps in "Editor's Picks"

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Show only snaps in "Editor's Picks"

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  The "Editor's Picks" section currently contains a mix of hard-coded values, 
values based on Ubuntu reviews and snaps from the "featured" snap store 
section. As snaps are the newest and preferred method of installing things in 
Ubuntu it should show only these in the order provided by snapd, falling back 
to the default behaviour if no snaps are found.

  [Test Case]
  1. Open GNOME Software
  2. Look at "Editor's Picks" section

  Expected result:
  This section contains the snaps from the "featured" snap store section in the 
correct order.

  Observed result:
  This section contains a mix of .deb and snaps. Some snaps may not be shown 
due to not being able to fit them all in. The order is random (changes daily).

  [Regression Potential]
  Solution is to add featured snaps last after clearing the existing featured 
apps. GNOME Software was modified to not randomize this list. Some risk of 
breaking related code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1705953/+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 1708936] Update Released

[Brian Murray]

The verification of the Stable Release Update for gnome-software has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  GNOME Software 3.20.5 doesn't install 3rd party deb's, doesn't prompt
  for authentication

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Ubuntu GNOME 16.04.3
  gnome-software 3.20.5-0ubuntu0.16.04.5

  Impact
  --
  Not being able to install 3rd party deb's is a very serious regression.

  Test Case
  -
  Visit https://www.google.com/chrome/ in Firefox and download Chrome.
  Open with "Software Install"
  The Ubuntu/GNOME Software app should start and show you a basic page about 
Google Chrome
  Click Install.
  Google Chrome should install itself

  What Happens
  
  The Install page does show up.
  After clicking the Install button, the button changes to Installing for a few 
seconds and then changes back to Install.
  Google Chrome is not installed.
  There is no PolicyKit authentication prompt to install software.
  When I run gnome-software --verbose, Progress says 9% which I think is when 
it would ask for authentication.

  Regression Potential
  
  This fixes a High Impact bug.
  And the fix is minimal:
  
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-software/ubuntu-xenial/revision/41

  Other Info
  --
  I am setting the importance of this bug to critical according to #7 of
  https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1708936/+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 1708936] Re: GNOME Software 3.20.5 doesn't install 3rd party deb's, doesn't prompt for authentication

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.6

---
gnome-software (3.20.5-0ubuntu0.16.04.6) xenial; urgency=medium

  * debian/patches/0001-Add-gs_app_set_local_file.patch:
  * debian/patches/0017-Add-an-APT-plugin.patch:
- Fix being unable to load .deb files (LP: #1708936)
  * debian/patches/0018-Add-a-Snap-plugin.patch:
- Fix icons larger than 65kB not loading (LP: #1704888)
- Stop 'core' snap showing as an app (LP: #1704904)
- Use new title field from snapd (LP: #169)
  * debian/patches/0045-Don-t-generate-popular-apps-from-Ubuntu-reviews.patch:
  * debian/patches/0046-snap-Use-first-featured-snap-as-featured-app.patch
  * debian/patches/0047-snap-Only-feature-snaps.patch
  * debian/patches/0048-Don-t-randomize-editors-picks.patch
- Only show snaps in "Editor's picks" (LP: #1705953)
- Show snap in "Featured" section (LP: #1706478)
  * debian/patches/0049-snap-Replace-libsoup-icon-loading-code-with-AsIcon.patch
- Fix crash loading cached icons (LP: #1708140)

 -- Robert Ancell   Thu, 24 Aug 2017
12:19:14 +1200

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Software 3.20.5 doesn't install 3rd party deb's, doesn't prompt
  for authentication

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Ubuntu GNOME 16.04.3
  gnome-software 3.20.5-0ubuntu0.16.04.5

  Impact
  --
  Not being able to install 3rd party deb's is a very serious regression.

  Test Case
  -
  Visit https://www.google.com/chrome/ in Firefox and download Chrome.
  Open with "Software Install"
  The Ubuntu/GNOME Software app should start and show you a basic page about 
Google Chrome
  Click Install.
  Google Chrome should install itself

  What Happens
  
  The Install page does show up.
  After clicking the Install button, the button changes to Installing for a few 
seconds and then changes back to Install.
  Google Chrome is not installed.
  There is no PolicyKit authentication prompt to install software.
  When I run gnome-software --verbose, Progress says 9% which I think is when 
it would ask for authentication.

  Regression Potential
  
  This fixes a High Impact bug.
  And the fix is minimal:
  
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-software/ubuntu-xenial/revision/41

  Other Info
  --
  I am setting the importance of this bug to critical according to #7 of
  https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1708936/+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 1718727] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718727/+attachment/4954525/+files/Stacktrace.txt

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

Title:
  gnome-control-center crashed with SIGSEGV in
  nm_device_filter_connections()

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

Bug description:
  Crash when open printer settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 13:08:40 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-08-02 (414 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f1112c62233 :  
mov0x8(%r12),%eax
   PC (0x7f1112c62233) ok
   source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   net_device_get_valid_connections ()
   ()
   ()
   g_simple_async_result_complete () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+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 1718727] gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()

[Apport retracing service]

StacktraceTop:
 nm_device_filter_connections (device=0x0, connections=connections@entry=0x0) 
at libnm/nm-device.c:2516
 net_device_get_valid_connections (device=0x560607eb4600) at net-device.c:326
 populate_ap_list (device_wifi=device_wifi@entry=0x560607eb4600) at 
net-device-wifi.c:2075
 nm_device_wifi_refresh_ui (device_wifi=device_wifi@entry=0x560607eb4600) at 
net-device-wifi.c:625
 get_secrets_cb (source_object=0x560607dfb130, res=, 
data=0x560607eb4600) at net-device-wifi.c:373

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

Title:
  gnome-control-center crashed with SIGSEGV in
  nm_device_filter_connections()

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

Bug description:
  Crash when open printer settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 13:08:40 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-08-02 (414 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f1112c62233 :  
mov0x8(%r12),%eax
   PC (0x7f1112c62233) ok
   source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   net_device_get_valid_connections ()
   ()
   ()
   g_simple_async_result_complete () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+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 1718727] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1718727/+attachment/4954526/+files/StacktraceSource.txt

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

Title:
  gnome-control-center crashed with SIGSEGV in
  nm_device_filter_connections()

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

Bug description:
  Crash when open printer settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 13:08:40 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-08-02 (414 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f1112c62233 :  
mov0x8(%r12),%eax
   PC (0x7f1112c62233) ok
   source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   net_device_get_valid_connections ()
   ()
   ()
   g_simple_async_result_complete () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+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 1718727] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718727/+attachment/4954527/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718727/+attachment/4954504/+files/CoreDump.gz

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in
  nm_device_filter_connections()

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

Bug description:
  Crash when open printer settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 13:08:40 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-08-02 (414 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f1112c62233 :  
mov0x8(%r12),%eax
   PC (0x7f1112c62233) ok
   source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   net_device_get_valid_connections ()
   ()
   ()
   g_simple_async_result_complete () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+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 1718729] [NEW] Black screen with a few white pixels on Virtualbox VM

[Jeremy LaCroix]

Public bug reported:

I installed Ubuntu 17.04 from a daily image downloaded yesterday in a
Virtualbox VM (Host Ubuntu version is 17.04). The installation works
fine and without any issues. However, when I install all the updates and
reboot, I am no longer able to log in. GDM doesn't start. Instead, I see
a completely black screen with a few (one or two) white pixels. I am
still able to SSH into the installation after this.

Steps to reproduce:
* Create a Virtualbox VM
* Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 
12:49pm Eastern)
* Install all updates (sudo apt-get update && sudo apt-get dist-upgrade)
* Reboot

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Thu Sep 21 12:11:34 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2017-09-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful corruption regression reproducible ubuntu

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

Title:
  Black screen with a few white pixels on Virtualbox VM

Status in xorg package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 17.04 from a daily image downloaded yesterday in a
  Virtualbox VM (Host Ubuntu version is 17.04). The installation works
  fine and without any issues. However, when I install all the updates
  and reboot, I am no longer able to log in. GDM doesn't start. Instead,
  I see a completely black screen with a few (one or two) white pixels.
  I am still able to SSH into the installation after this.

  Steps to reproduce:
  * Create a Virtualbox VM
  * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 
12:49pm Eastern)
  * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade)
  * Reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 12:11:34 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No 

[Desktop-packages] [Bug 1718727] [NEW] gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()

[Wellington Torrejais da Silva]

Public bug reported:

Crash when open printer settings

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Sep 21 13:08:40 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2016-08-02 (414 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
ProcCmdline: gnome-control-center printers
SegvAnalysis:
 Segfault happened at: 0x7f1112c62233 :
mov0x8(%r12),%eax
 PC (0x7f1112c62233) ok
 source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 net_device_get_valid_connections ()
 ()
 ()
 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

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


** Tags: amd64 apport-crash artful need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV in
  nm_device_filter_connections()

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

Bug description:
  Crash when open printer settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 13:08:40 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-08-02 (414 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: gnome-control-center printers
  SegvAnalysis:
   Segfault happened at: 0x7f1112c62233 :  
mov0x8(%r12),%eax
   PC (0x7f1112c62233) ok
   source "0x8(%r12)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0
   net_device_get_valid_connections ()
   ()
   ()
   g_simple_async_result_complete () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
nm_device_filter_connections()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+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 1672698] Re: Broken/Missing font rendering in firefox

[Domenico]

I have had the same issue on 16.04 and Firefox 55. Fixed installing
fonts-roboto-hinted

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

Title:
  Broken/Missing font rendering in firefox

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On some websites,e.g., https://zenodo.org and https://www.youtube.com
  the text is not visible on the site. However, when selecting all
  (CTRL-a) and copying the text to an text editor, the proper text is
  available. Therefore, the text is not rendered or using an strange
  font without any glyphs in it. I repeated this with the usually not
  used "Guest Account". Hence it is not an issue with my personal
  setting.

  The issue appeared when upgrading to Ubuntu Zesty (17.04). The current
  Firefox package install is 52.0+build2-0ubuntu0.16.10.1

  I will downgrade not to 50.1.0+build2-0ubuntu1 to reexamine the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1672698/+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 1718715] Re: package docbook-xml 4.5-7.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[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 docbook-xml in Ubuntu.
https://bugs.launchpad.net/bugs/1718715

Title:
  package docbook-xml 4.5-7.3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in docbook-xml package in Ubuntu:
  New

Bug description:
  I wasn't able to update my system because of this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: docbook-xml 4.5-7.3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 11:07:16 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-09-21 (364 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: docbook-xml
  Title: package docbook-xml 4.5-7.3 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/docbook-xml/+bug/1718715/+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 1718709] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1714745, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954404/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954406/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954411/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954412/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954413/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954414/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1718709/+attachment/4954415/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1714745
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
shell_gtk_embed_window_created_cb() from g_closure_invoke() from 
signal_emit_unlocked_R()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Different stack trace compared to other bugs here.

  Stacktrace:
   #0  0x7fe15d4dfe56 in g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   #1  0x7fe15dabb69c in  () at /usr/lib/gnome-shell/libgnome-shell.so
   #2  0x7fe15d4b9f9d in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   #3  0x7fe15d4ccd5e in  () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   #4  0x7fe15d4d5535 in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   #5  0x7fe15d4d5f4f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   #6  0x7fe15b72bc03 in  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   #7  0x7fe15b743b70 in meta_window_x11_new () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   #8  0x7fe15b7385e9 in  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   #9  0x7fe15b7394cb in  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   #10 0x7fe15a9958af in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   #11 0x7fe15a995b99 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   #12 0x7fe15a95f9c0 in gdk_display_get_event () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   #13 0x7fe15a995942 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   #14 0x7fe15d1e0f77 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
   #15 0x7fe15d1e11b0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   #16 0x7fe15d1e14c2 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
   #17 0x7fe15b719c1c in meta_run () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   #18 0x5579eea3a307 in  ()
   #19 0x7fe15b0ac1c1 in __libc_start_main (main=0x5579eea39f10, argc=1, 
argv=0x7fffac57ce88, init=, fini=, 
rtld_fini=, stack_end=0x7fffac57ce78) at ../csu/libc-start.c:308

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Sep 21 12:28:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-12-01 (1024 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fe15d4dfe56 :
mov(%rdi),%rdi
   PC (0x7fe15d4dfe56) ok
   source "(%rdi)" (0x008041ed) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at 

[Desktop-packages] [Bug 1718715] [NEW] package docbook-xml 4.5-7.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[John King]

Public bug reported:

I wasn't able to update my system because of this.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docbook-xml 4.5-7.3
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Sep 21 11:07:16 2017
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-09-21 (364 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: docbook-xml
Title: package docbook-xml 4.5-7.3 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: docbook-xml (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package docbook-xml 4.5-7.3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in docbook-xml package in Ubuntu:
  New

Bug description:
  I wasn't able to update my system because of this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: docbook-xml 4.5-7.3
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 11:07:16 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-09-21 (364 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: docbook-xml
  Title: package docbook-xml 4.5-7.3 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/docbook-xml/+bug/1718715/+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 1596662] Re: pcscd fails to read CAC card data, errors out

[Mario Limonciello]

Just to add clarity to this issue:

The ID's in the old FW release are not supported by CCID and have been removed 
in git:
https://github.com/LudovicRousseau/CCID/commit/e6a7548623f35d428f9f410f4b885fd04e34070a
https://github.com/LudovicRousseau/CCID/commit/2f68054ce81aa10ec60adf9a92c66dca64bdd415

After performing a FW upgrade new device ID's will be created which are 
compliant.
If you're seeing the old ID's you'll have to upgrade the FW (which there 
unfortunately isn't currently a way to do this on Linux).

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

Title:
  pcscd fails to read CAC card data, errors out

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  When I use Firefox to try and access a website using my CAC card, with a 
Broadcom Corp 5880 [Contacted SmartCard] smart card reader on a Dell Precision 
7510 and libcackey, my web browser hangs for a bit, then fails, and looking at 
pcscd's log shows the following (note the lines:
  "0026 ifdwrapper.c:348:IFDStatusICC() Card not transacted: 612
  0002 winscard.c:592:SCardReconnect() Error resetting card."

  Ubuntu 14.04.4, kernel 4.2.0-38-generic.

  See below:

  winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0003 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x0 for client 15
  0039 winscard_svc.c:319:ContextThread() Received command: TRANSMIT from 
client 15
  0008 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0003 winscard.c:1587:SCardTransmit() Send Protocol: T=0
  0003 APDU: 00 C0 00 00 BA 
  0003 ifdhandler.c:1266:IFDHTransmitToICC() 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  00014006 commands.c:1456:CCID_Receive() Can't read all data (54 out of 188 
expected)
  0012 SW: 
  0003 ifdwrapper.c:527:IFDTransmit() Card not transacted: 612
  0003 winscard.c:1612:SCardTransmit() Card not transacted: 0x80100016
  0002 winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0003 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x80100016 for client 
15
  0038 winscard_svc.c:319:ContextThread() Received command: RECONNECT from 
client 15
  0007 winscard.c:504:SCardReconnect() Attempting reconnect to token.
  0003 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  00230568 ccid_usb.c:790:ReadUSB() read failed (1/5): -8 Resource temporarily 
unavailable
  0026 ifdwrapper.c:348:IFDStatusICC() Card not transacted: 612
  0002 winscard.c:592:SCardReconnect() Error resetting card.
  0002 winscard.c:793:SCardReconnect() UnrefReader() count was: 2
  0003 winscard_svc.c:472:ContextThread() RECONNECT rv=0x80100066 for 
client 15
  0049 winscard_svc.c:319:ContextThread() Received command: TRANSMIT from 
client 15
  0007 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0002 winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0001 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x80100068 for client 
15
  0014 winscard_svc.c:319:ContextThread() Received command: DISCONNECT from 
client 15
  0004 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0002 winscard.c:850:SCardDisconnect() Active Contexts: 1
  0002 winscard.c:851:SCardDisconnect() dwDisposition: 0
  0001 winscard.c:1016:SCardDisconnect() powerState: 
POWER_STATE_GRACE_PERIOD
  0003 ifdhandler.c:362:IFDHGetCapabilities() tag: 0xFB2, 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  0002 winscard.c:1030:SCardDisconnect() Stopping polling thread
  0014 ifdhandler.c:327:IFDHStopPolling() 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  0147 winscard.c:1043:SCardDisconnect() UnrefReader() count was: 2
  0007 winscard_svc.c:490:ContextThread() DISCONNECT rv=0x0 for client 15
  0049 winscard_svc.c:319:ContextThread() Received command: CONNECT from 
client 15
  0024 winscard.c:235:SCardConnect() Attempting Connect to Broadcom Corp 
5880 [Contacted SmartCard] (0123456789ABCD) 00 00 using protocol: 3
  0002 readerfactory.c:745:RFReaderInfo() RefReader() count was: 1
  0002 winscard.c:322:SCardConnect() Card Not Powered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1596662/+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 1718694] Re: /usr/lib/gvfs/gvfsd-mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

[Bug Watch Updater]

** Changed in: gvfs
   Status: Unknown => Confirmed

** Changed in: gvfs
   Importance: Unknown => Medium

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

Title:
  /usr/lib/gvfs/gvfsd-
  
mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1718694/+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 1718694] Re: /usr/lib/gvfs/gvfsd-mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

[Sebastien Bacher]

** Changed in: gvfs (Ubuntu)
   Status: New => Triaged

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

** Also affects: gvfs via
   https://bugzilla.gnome.org/show_bug.cgi?id=787992
   Importance: Unknown
   Status: Unknown

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

Title:
  /usr/lib/gvfs/gvfsd-
  
mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1718694/+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 1596662] Re: pcscd fails to read CAC card data, errors out

[Mario Limonciello]

** Changed in: pcsc-lite (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  pcscd fails to read CAC card data, errors out

Status in pcsc-lite package in Ubuntu:
  Won't Fix

Bug description:
  When I use Firefox to try and access a website using my CAC card, with a 
Broadcom Corp 5880 [Contacted SmartCard] smart card reader on a Dell Precision 
7510 and libcackey, my web browser hangs for a bit, then fails, and looking at 
pcscd's log shows the following (note the lines:
  "0026 ifdwrapper.c:348:IFDStatusICC() Card not transacted: 612
  0002 winscard.c:592:SCardReconnect() Error resetting card."

  Ubuntu 14.04.4, kernel 4.2.0-38-generic.

  See below:

  winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0003 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x0 for client 15
  0039 winscard_svc.c:319:ContextThread() Received command: TRANSMIT from 
client 15
  0008 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0003 winscard.c:1587:SCardTransmit() Send Protocol: T=0
  0003 APDU: 00 C0 00 00 BA 
  0003 ifdhandler.c:1266:IFDHTransmitToICC() 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  00014006 commands.c:1456:CCID_Receive() Can't read all data (54 out of 188 
expected)
  0012 SW: 
  0003 ifdwrapper.c:527:IFDTransmit() Card not transacted: 612
  0003 winscard.c:1612:SCardTransmit() Card not transacted: 0x80100016
  0002 winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0003 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x80100016 for client 
15
  0038 winscard_svc.c:319:ContextThread() Received command: RECONNECT from 
client 15
  0007 winscard.c:504:SCardReconnect() Attempting reconnect to token.
  0003 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  00230568 ccid_usb.c:790:ReadUSB() read failed (1/5): -8 Resource temporarily 
unavailable
  0026 ifdwrapper.c:348:IFDStatusICC() Card not transacted: 612
  0002 winscard.c:592:SCardReconnect() Error resetting card.
  0002 winscard.c:793:SCardReconnect() UnrefReader() count was: 2
  0003 winscard_svc.c:472:ContextThread() RECONNECT rv=0x80100066 for 
client 15
  0049 winscard_svc.c:319:ContextThread() Received command: TRANSMIT from 
client 15
  0007 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0002 winscard.c:1632:SCardTransmit() UnrefReader() count was: 2
  0001 winscard_svc.c:608:ContextThread() TRANSMIT rv=0x80100068 for client 
15
  0014 winscard_svc.c:319:ContextThread() Received command: DISCONNECT from 
client 15
  0004 readerfactory.c:772:RFReaderInfoById() RefReader() count was: 1
  0002 winscard.c:850:SCardDisconnect() Active Contexts: 1
  0002 winscard.c:851:SCardDisconnect() dwDisposition: 0
  0001 winscard.c:1016:SCardDisconnect() powerState: 
POWER_STATE_GRACE_PERIOD
  0003 ifdhandler.c:362:IFDHGetCapabilities() tag: 0xFB2, 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  0002 winscard.c:1030:SCardDisconnect() Stopping polling thread
  0014 ifdhandler.c:327:IFDHStopPolling() 
usb:0a5c/5800:libudev:1:/dev/bus/usb/001/005 (lun: 0)
  0147 winscard.c:1043:SCardDisconnect() UnrefReader() count was: 2
  0007 winscard_svc.c:490:ContextThread() DISCONNECT rv=0x0 for client 15
  0049 winscard_svc.c:319:ContextThread() Received command: CONNECT from 
client 15
  0024 winscard.c:235:SCardConnect() Attempting Connect to Broadcom Corp 
5880 [Contacted SmartCard] (0123456789ABCD) 00 00 using protocol: 3
  0002 readerfactory.c:745:RFReaderInfo() RefReader() count was: 1
  0002 winscard.c:322:SCardConnect() Card Not Powered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1596662/+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 1716946] Re: gvfsd-network crashed with signal 5 in g_main_context_new()

[Sebastien Bacher]

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

or rather the command upstream suggested in the report

"printf "  count\tpid\tname\n"; lsof | awk '{ if (NR > 1) print $2 "\t"
$1; }' | sort | uniq -c | sort -rn | head -10"

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

Title:
  gvfsd-network crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Invalid
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 12:10:50 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-network
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 
/org/gtk/gvfs/exec_spaw/3
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-network crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1716946/+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 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed

[Raphaël HALIMI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, sorry for the late answer, I'm quite busy these days.

Le 21/08/2017 à 13:27, Wolf Rogner a écrit :
> Mind: deinstalling eliminates a set of issues (see above).

Which issues did it eliminate exactly ? From what I can tell:

> higher CPU load (not only in Firefox)

It's the first time I hear about this one.

> not fully charged battery on laptops (stops at 94% of capacity)

This may be related to battery charge thresholds, but the default TLP
configuration doesn't change them. Some questions to narrow down the
problem :

- - Which model of ThinkPad do you have ?
- - Did you change those thresholds by other means ? Please check
/etc/sysfs.conf and snippets under /etc/sysfs.d
- - Do you dual boot Windows on this machine, and have Lenovo power
manager installed in it ?

> kicks in fans arbitrarily (even when CPU temp is below average
> normal state)

I'm pretty sure it has nothing to do with TLP. I have this problem on
two distinct X200 and uninstalling TLP didn't fix it. Unfortunately I
noticed this problem after a long time and I'm not sure what change on
my machines caused it, it may be a kernel upgrade (I noticed it after
upgrading to Debian Jessie). I also noticed that, when unplugged from
AC, after a while, the fan calms down, but the problem comes back after
re-plugging. If you can tell me more I'm interested.

> terminates bluetooth connections every 2 mins

This is a known problem and it's more or less fixed by version 1.0 of
TLP (which I had uploaded by my sponsor in Debian Unstable, but
unfortunately didn't make it in Artful before the sync freeze). When
it will be synced to Ubuntu, you may request a backport (but don't
take my word on that, I'm not sure of how the process works for
Ubuntu, the package may need to hit a stable release first;
documentation I found on the web only states "from within the Ubuntu
repositories"). In the meantime, you could use packages from
upstream's PPA. In any case, you'll have to set the new option
USB_BLACKLIST_BTUSB to 1.

> terminates network connections every 2-5 mins

I'm really not sure about this one. Maybe change the value of
PCIE_ASPM_ON_BAT or various RUNTIME_PM* options ?

> Maybe you check whether machine is a thinkpad and only install
> then.

No. TLP works on all kind of laptops. The only ThinkPad-specific
features are the ones related to battery (dis)charge thresholds.

Regards,

- -- 
Raphaël Halimi
-BEGIN PGP SIGNATURE-

iQKtBAEBCgCXFiEEb6lOxdKMjWi+eSrvTZn2ZgpZgnsFAlnD0S9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZG
QTk0RUM1RDI4QzhENjhCRTc5MkFFRjREOTlGNjY2MEE1OTgyN0IZHHJhcGhhZWwu
aGFsaW1pQGdtYWlsLmNvbQAKCRBNmfZmClmCe2bXD/4rAxDLRZKtKF/zCvxj0dEL
IrIce5l4VQT7hdBchXA/Hbt5Kr1Dl8ohB8oHmGnt9EqhKIluNeoqQNE8QrifKaYk
U+99s3MKJMcwHEtTXxQkxfZcVUHaoNF6EqZxRl0DW1vJCPcxiUIPsEjZoN82mHCZ
iF3rzD6gfOYNfJbGhuuo8QVWhnZvnoMK9xyaV6aH7wd37XrGONlKn/695sIm08LG
qduYCcE2AZ6ZkJm7qLJ/cpuSdmC1+65hH0XjJPQ+rNMHU6lnA23xoQ55ycRHZaYq
RR0frGHDV8/Ttk5urbZ6mz/v4BjzIuTh6SK+tIpV0Ex+6+yxoFbClXFTNWBuERPW
RxPaA/SHnEEC/ZogekEzqp5eiomqPfb/BNJ70QDh0s7iHwS2YwE+c7tZOjxNJDyS
gFwJfylyp6xeisptY+2gWoOWK2U8nyB60opdveVu4HLr1H25XX+sMg7hzfrMEaXS
n0/V7g3UkxOerPCVNB2B/jXSFOaBe1LpHdzLjTSgtICryTDoyMyLMyMHda9JVD63
YuexvvrBEWh9kUWGOFYTSYcsUlby/e24It8DnWjAHTSMX+bv28UOO8KNC25h72u1
K/Y4TLcX5whnJnPLuXYBuCuci65Lf8nvEneEjYJ9aVkVE+rwMtwR2lUBvv/XozSt
xPWLv8OsqvF0wTRkIngQUg==
=WUZx
-END PGP SIGNATURE-

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

Title:
  Slow Firefox performance and high CPU load when tlp is installed

Status in firefox package in Ubuntu:
  New
Status in tlp package in Ubuntu:
  New

Bug description:
  After installing Firefox 55 the browser generates huge cpu load,
  startup is extremely slow (it takes > 10s for the taskbar to accept
  entries after launch (this is new to 55)

  Due to high cpu load the computer tends to overheat, ventilation jumps
  in making the machine extremely loud.

  Using Chromium does not show these symptoms (on the same page).

  
  ---
  LSB Ubuntu 17.04 (budgie desktop)
  firefox:
Installed: 55.0.1+build2-0ubuntu0.17.04.2
Candidate: 55.0.1+build2-0ubuntu0.17.04.2
Version table:
   *** 55.0.1+build2-0ubuntu0.17.04.2 500
  500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   50.1.0+build2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.1+build2-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: 

[Desktop-packages] [Bug 1716946] Re: gvfsd-network crashed with signal 5 in g_main_context_new()

[Sebastien Bacher]

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

the issue is 
Creating pipes for GWakeup: Demasiados archivos abiertos

something is leaking file descriptors, could you give the output of
"lsof" when having the issue?


** This bug has been marked a duplicate of bug 1716940
   gvfsd-trash crashed with signal 5 in g_main_context_new()

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

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

Title:
  gvfsd-network crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Invalid
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 12:10:50 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-network
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 
/org/gtk/gvfs/exec_spaw/3
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-network crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1716946/+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 1706097] Re: gvfsd-mtp crashed with SIGSEGV

[Sebastien Bacher]

seems the same as bug #1718694 reported upstream on
https://bugzilla.gnome.org/show_bug.cgi?id=787992

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

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I get this every day when I have connected my Android phone for
  charging its battery.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
   PC (0x7fea768b6cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1706097/+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 1718694] Re: /usr/lib/gvfs/gvfsd-mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

[Sebastien Bacher]

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

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

Title:
  /usr/lib/gvfs/gvfsd-
  
mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1718694/+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 1718692] Re: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[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 gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1718692

Title:
  package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Wanted to Update "OS Updates" and "Software". Somewhere there is
  issue. Did not complete updates. Thank you!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 16:26:12 2017
  DuplicateSignature:
   package:libgtk2.0-0:i386:2.24.30-1ubuntu1.16.04.2
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-0: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-03-23 (181 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.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/gtk+2.0/+bug/1718692/+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 1718694] [NEW] /usr/lib/gvfs/gvfsd-mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gvfs (Ubuntu)
 Importance: High
 Status: New


** Tags: artful kylin-17.10 wily xenial yakkety zesty

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

Title:
  /usr/lib/gvfs/gvfsd-
  
mtp:11:unregister_mount_got_proxy_cb:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/03a99ff8e78e46a37528a5880fa765a386ff5f3d 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1718694/+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 1718692] [NEW] package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[Christoph Heim]

Public bug reported:

Wanted to Update "OS Updates" and "Software". Somewhere there is issue.
Did not complete updates. Thank you!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Sep 21 16:26:12 2017
DuplicateSignature:
 package:libgtk2.0-0:i386:2.24.30-1ubuntu1.16.04.2
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libgtk2.0-0: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-03-23 (181 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gtk+2.0
Title: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.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: gtk+2.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 gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1718692

Title:
  package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Wanted to Update "OS Updates" and "Software". Somewhere there is
  issue. Did not complete updates. Thank you!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 16:26:12 2017
  DuplicateSignature:
   package:libgtk2.0-0:i386:2.24.30-1ubuntu1.16.04.2
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-0: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-03-23 (181 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.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/gtk+2.0/+bug/1718692/+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 1718680] Re: gnome-shell sigfault in libxkbcommon

[Sebastien Bacher]

or do you have any report in /var/crash about the issue?

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

Title:
  gnome-shell sigfault in libxkbcommon

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Intermittent problem shows up as the desktop background partially
  opens after login and then freezes.  After a short pause the screen
  clears and goes back to the login screen.  Logging in again will
  result in a working system.  Add the file PartialDT.txt which is the
  syslog portion that I think shows the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 09:34:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-24 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718680/+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 1718552] Re: gnome-shell uses lots of memory

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

Title:
  gnome-shell uses lots of memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 (daily build, VirtualBox), gnome-shell uses lots of
  memory, even more after opening and closing just a few apps
  (LibreOffice Writer, Chromium, Nautilus.) More than 640 mb.

  Also,the CPU usage is quite high too, even if nothing is running in
  the foreground.

  See screen captures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718552/+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 1718680] Re: gnome-shell sigfault in libxkbcommon

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1718680

Title:
  gnome-shell sigfault in libxkbcommon

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Intermittent problem shows up as the desktop background partially
  opens after login and then freezes.  After a short pause the screen
  clears and goes back to the login screen.  Logging in again will
  result in a working system.  Add the file PartialDT.txt which is the
  syslog portion that I think shows the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 09:34:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-24 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718680/+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 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

[Jarno Suni]

Brian, however, as you installed the kernel by apt-get install, the
kernel becomes manually installed, and will not later be removed by
'sudo apt autoremove', unless you change it to be marked as
automatically installed.

I question the use of 'sudo apt autoremove' in this case. If its action was the 
desired one, setting 
Unattended-Upgrade::Remove-Unused-Dependencies "false";
would be the setting to use, instead of the current default
Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
Balint Reczey tries to explain in #11 why that setting is not desired.

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

Title:
  By default settings unattended-upgrade is unable to automatically
  remove packages that become unused in conjunction with updating by
  other software.

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+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 1718643] Re: Inability to move child dialogues separate from parent applicaitons

[Jeremy Bicha]

You can also disable this feature by installing GNOME Tweaks (gnome-
tweak-tool).

Open the Windows panel and turn off Attach Modal Dialogs.

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

Title:
  Inability to move child dialogues separate from parent applicaitons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When dragging a save dialogue (or similar) in the latest A Ubuntu
  release, the WM does not allow me to move the dialogue independently
  from the application.

  This is a huge nuisance, in the case where I want to move the dialogue
  to uncover some text from the underlying document, to construct a save
  file name (e.g. matching title of document to filename etc..).

  It is really unexpected that dragging the title bar of an dialogue
  also moves the parent application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718643/+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 1718643] Re: Inability to move child dialogues separate from parent applicaitons

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

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

Title:
  Inability to move child dialogues separate from parent applicaitons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When dragging a save dialogue (or similar) in the latest A Ubuntu
  release, the WM does not allow me to move the dialogue independently
  from the application.

  This is a huge nuisance, in the case where I want to move the dialogue
  to uncover some text from the underlying document, to construct a save
  file name (e.g. matching title of document to filename etc..).

  It is really unexpected that dragging the title bar of an dialogue
  also moves the parent application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718643/+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 1718526] Re: Artful-proposed: gdk-pixbuf breaks tiff file visibility

[Jeremy Bicha]

** Tags removed: block-proposed

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

Title:
  Artful-proposed: gdk-pixbuf breaks tiff file visibility

Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading the package gdk-pixbuf to 2.36.10-1 (artful-proposed) the 
tiff files cannot be opened any more.
  For example Eye of Gnome claims the file type tiff is unknown.
  Downgrading to the artful release version 2.36.5-3ubuntu1 solves the issue 
and tiff's are OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1718526/+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 1718680] [NEW] gnome-shell sigfault in libxkbcommon

[Cliff Carson]

Public bug reported:

Intermittent problem shows up as the desktop background partially opens
after login and then freezes.  After a short pause the screen clears and
goes back to the login screen.  Logging in again will result in a
working system.  Add the file PartialDT.txt which is the syslog portion
that I think shows the error.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 21 09:34:15 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-07-24 (58 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "PartialDT_0921.txt"
   
https://bugs.launchpad.net/bugs/1718680/+attachment/4954334/+files/PartialDT_0921.txt

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

Title:
  gnome-shell sigfault in libxkbcommon

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Intermittent problem shows up as the desktop background partially
  opens after login and then freezes.  After a short pause the screen
  clears and goes back to the login screen.  Logging in again will
  result in a working system.  Add the file PartialDT.txt which is the
  syslog portion that I think shows the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 21 09:34:15 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-24 (58 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718680/+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 1718612] Re: Align Dock UI better with other panels

[Alberto Salvia Novella]

@ Ubuntu Documentation Team members

If you are interested in following up this bug report, please subscribe to it:
(https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718612/+subscribe)

I'm unsubscribing the team as a hole now, so only the members interested
in this report will receive notifications about it.

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

Title:
  Align Dock UI better with other panels

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

Bug description:
  Multiple changes suggested by upstream for our own ubuntu dock panel:
  - "Screen position" to be replaced by "Position on screen" (already covered 
by the other UIFe in the same upload)
  - add slighter larger marging (there is no icon in this panel, and so, the 
rows are smaller
  - only display "Show on" if multiple screens are available (doesn't make 
sense when there is only one screen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718612/+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 1718653] Re: Windows buttons gone on specific programs

[lotuspsychje]

@Jean-Baptiste #2

https://imgur.com/a/S3VCU

Cant add images neither in browsing in my folders, cause no files show anymore 
neither
also sluggish overall on launching programs etc, weird things happened

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+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 1718612] Re: Align Dock UI better with other panels

[Didier Roche]

** Summary changed:

- [UIFe] Align Dock UI better with other panels
+ Align Dock UI better with other panels

** Description changed:

  Multiple changes suggested by upstream for our own ubuntu dock panel:
- - "Screen position" to be replaced by "Position on screen"
+ - "Screen position" to be replaced by "Position on screen" (already covered 
by the other UIFe in the same upload)
  - add slighter larger marging (there is no icon in this panel, and so, the 
rows are smaller
  - only display "Show on" if multiple screens are available (doesn't make 
sense when there is only one screen)
- - Show on should pilot the primary display + the existing on all screens, it 
doesn't make sense to place the dock on one display only and the top bar on 
another one.

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

Title:
  Align Dock UI better with other panels

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

Bug description:
  Multiple changes suggested by upstream for our own ubuntu dock panel:
  - "Screen position" to be replaced by "Position on screen" (already covered 
by the other UIFe in the same upload)
  - add slighter larger marging (there is no icon in this panel, and so, the 
rows are smaller
  - only display "Show on" if multiple screens are available (doesn't make 
sense when there is only one screen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718612/+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 1718653] Re: Windows buttons gone on specific programs

[TJ]

I'd suspect the recent update to:

mesa (17.2.1-0ubuntu1) artful; urgency=medium

  * New upstream bugfix release. (LP: #1716250)

 -- Timo Aaltonen   Mon, 18 Sep 2017 14:42:16 +0300

I've only looked at Firefox's dependencies so far but of them all this
is the only project updated in the past 2-3 days which supplies:

libwayland-egl1-mesa

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+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 1718660] [NEW] Show on ubuntu panel should pilot primary monitor

[Didier Roche]

Public bug reported:

Show on should pilot the primary display + the existing on all screens,
it doesn't make sense to place the dock on one display only and the top
bar on another one.

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

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

Title:
  Show on ubuntu panel should pilot primary monitor

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

Bug description:
  Show on should pilot the primary display + the existing on all
  screens, it doesn't make sense to place the dock on one display only
  and the top bar on another one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718660/+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 1718653] Re: Windows buttons gone on specific programs

[lotuspsychje]

** Description changed:

- Ubuntu 17.10 64bit Development version up to date @ 21/9/2017
+ Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
+ Xwayland
  
  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  
  other programs have working buttons
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland
  
  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
+ on a black window header with disformed white letters as window title
  
  other programs have working buttons
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+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 1718653] Re: Windows buttons gone on specific programs

[Jean-Baptiste Lallement]

Thanks for your report.

Could you please attach a screenshot of one of the affected application?
Thanks.

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1718653

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017 on
  Xwayland

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)
  on a black window header with disformed white letters as window title

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+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 1718654] [NEW] Touchpad input doesn't work after longer suspend.

[Michał Sawicz]

Public bug reported:

When I resume my laptop from a longer (not sure what the threshold is
yet) suspend, I don't get input from the touchpad, a short suspend cycle
fixes it.

Touchscreen works all the time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 14:20:56 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  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/1718654/+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 1718653] [NEW] Windows buttons gone on specific programs

[lotuspsychje]

Public bug reported:

Ubuntu 17.10 64bit Development version up to date @ 21/9/2017

kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
(maybe more that i havent tested)

other programs have working buttons

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 14:17:17 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-08-31 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Windows buttons gone on specific programs

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 64bit Development version up to date @ 21/9/2017

  kernel: Linux ArtfullBOX 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12
  16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  Windows buttons are gone for specific programs like Firefox, hexchat, 
photoprint,chromium
  (maybe more that i havent tested)

  other programs have working buttons

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:17:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830)
  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/1718653/+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 1713285] Re: 17.10: Missing Add-ons category

[Iain Lane]

I think it's because 90123ee63 changed "Addon::" to "Addons::", meaning
things were being added to the wrong category.

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

Title:
  17.10: Missing Add-ons category

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I don't see the Add-ons category in GNOME Software's front page.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.25.91-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 26 18:56:47 2017
  EcryptfsInUse: Yes
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.25.91-1ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1713285/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[M.Witte]

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

Still not fixed.

Same as @rouniy:

When I lock package version:
sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-glib4=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm0=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-util2=1.2.2-0ubuntu0.16.04.4
sudo apt install resolvconf=1.78ubuntu2
sudo apt-mark hold network-manager
sudo apt-mark hold libnm-glib-vpn1
sudo apt-mark hold libnm-glib4
sudo apt-mark hold libnm0
sudo apt-mark hold libnm-util2
sudo apt-mark hold resolvconf

It works again.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

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

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  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
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  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.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1718648] Re: unity7 default keybindings are preserved after upgrade and considered as non-default keybindings

[Jean-Baptiste Lallement]

keybindings defined after an upgrade from 17.04

** Attachment added: "upgraded-keybindings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1718648/+attachment/4954291/+files/upgraded-keybindings.txt

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

Title:
  unity7 default keybindings are preserved after upgrade and considered
  as non-default keybindings

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  After an upgrade from stock installation of zesty, keybindings defined
  for unity7 are preserved and considered as non default keybindings.

  For example:
  in unity 7, ctrl+super+up/down maximizes/restores a window
  in gnome-shell super-up/down does the same

  but after an upgrade it is still ctrl+super+up/down

  I expect that after an upgrade, the default keybindings should be used
  if the corresponding binding as not been modified before the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gsettings-desktop-schemas 3.24.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 13:51:49 2017
  InstallationDate: Installed on 2013-09-03 (1478 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1718648/+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 1718648] [NEW] unity7 default keybindings are preserved after upgrade and considered as non-default keybindings

[Jean-Baptiste Lallement]

Public bug reported:

After an upgrade from stock installation of zesty, keybindings defined
for unity7 are preserved and considered as non default keybindings.

For example:
in unity 7, ctrl+super+up/down maximizes/restores a window
in gnome-shell super-up/down does the same

but after an upgrade it is still ctrl+super+up/down

I expect that after an upgrade, the default keybindings should be used
if the corresponding binding as not been modified before the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gsettings-desktop-schemas 3.24.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 13:51:49 2017
InstallationDate: Installed on 2013-09-03 (1478 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gsettings-desktop-schemas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Summary changed:

- unity7 keybindings are preserved after upgrade and considered as non-default 
keybindings
+ unity7 default keybindings are preserved after upgrade and considered as 
non-default keybindings

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

Title:
  unity7 default keybindings are preserved after upgrade and considered
  as non-default keybindings

Status in gsettings-desktop-schemas package in Ubuntu:
  New

Bug description:
  After an upgrade from stock installation of zesty, keybindings defined
  for unity7 are preserved and considered as non default keybindings.

  For example:
  in unity 7, ctrl+super+up/down maximizes/restores a window
  in gnome-shell super-up/down does the same

  but after an upgrade it is still ctrl+super+up/down

  I expect that after an upgrade, the default keybindings should be used
  if the corresponding binding as not been modified before the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gsettings-desktop-schemas 3.24.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 13:51:49 2017
  InstallationDate: Installed on 2013-09-03 (1478 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1718648/+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 1699731] Re: Icons appear corrupted when dragged on the Desktop or in Nautilus

[Taras Denysenko]

** Description changed:

  After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop 
or from a Nautilus window now looks quite strange.
  In both cases the image under cursor, which represents the icon being 
dragged, has no transparency and includes a piece of the background, on which 
the original icon is located, and the dragged icon itself appears to be 
somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue.
  
  When searching for the solution for this issue, I found the following
  question on askubuntu, which seems to describe the same problem:
  https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus-
  when-dragging-icons . Unfortunately, the question is unanswered and
  there are no mentions of a bug report, so I decided to go ahead and
  submit one myself.
  
  I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia
  driver v.375.66 is installed. The problem reproduces regardless of which
  graphics card is selected via nvidia-prime.
  
  Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command:
  
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller
   Kernel driver in use: i915
   Kernel modules: i915
  --
  08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
   Subsystem: Dell GeForce 820M
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375
+ 
+ 
+ `apt list nautilus` gives the following output:
+ 
+ Listing... Done
+ nautilus/zesty,now 1:3.20.4-0ubuntu2 amd64 [installed]

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

Title:
  Icons appear corrupted when dragged on the Desktop or in Nautilus

Status in Ayatana Design:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop 
or from a Nautilus window now looks quite strange.
  In both cases the image under cursor, which represents the icon being 
dragged, has no transparency and includes a piece of the background, on which 
the original icon is located, and the dragged icon itself appears to be 
somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue.

  When searching for the solution for this issue, I found the following
  question on askubuntu, which seems to describe the same problem:
  https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus-
  when-dragging-icons . Unfortunately, the question is unanswered and
  there are no mentions of a bug report, so I decided to go ahead and
  submit one myself.

  I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia
  driver v.375.66 is installed. The problem reproduces regardless of
  which graphics card is selected via nvidia-prime.

  Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command:

  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller
   Kernel driver in use: i915
   Kernel modules: i915
  --
  08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
   Subsystem: Dell GeForce 820M
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375

  
  `apt list nautilus` gives the following output:

  Listing... Done
  nautilus/zesty,now 1:3.20.4-0ubuntu2 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1699731/+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 1717012] Re: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installi

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1708503
   package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: 
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  
nochmal installieren, bevor Sie die Konfiguration versuchen.

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

Title:
  package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libwacom package in Ubuntu:
  New

Bug description:
  no further

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 13 20:50:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-09-13  20:49:13
   Commandline: apt-get install -f
   Requested-By: thomas (1000)
   Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic)
   Upgrade: linux-image-generic-hwe-16.04:amd64 (4.10.0.32.34, 4.10.0.33.35), 
linux-generic-hwe-16.04:amd64 (4.10.0.32.34, 4.10.0.33.35), 
linux-headers-4.10.0-32:amd64 (4.10.0-32.36~16.04.1, 4.10.0-32.36~16.04.1), 
linux-headers-generic-hwe-16.04:amd64 (4.10.0.30.33, 4.10.0.33.35)
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller 
[10cf:150a]
  InstallationDate: Installed on 2017-07-22 (53 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: FUJITSU LIFEBOOK AH530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=27e085d5-ec9d-4e23-81e3-fe76537c7d5c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libwacom
  Title: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.19
  dmi.board.name: FJNBB06
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd08/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK AH530
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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
  xserver.bootTime: Wed Sep 13 21:38:57 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1717012/+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 1708503] Re: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installi

[Timo Aaltonen]

the package is fine, your upgrade got interrupted for some reason and
you need to fix it manually

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

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

Title:
  package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libwacom package in Ubuntu:
  Invalid

Bug description:
  Defektes Paket verhindert die Aktualisierung des Systems

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libwacom-common: Install
   libwacom-common: Configure
   libwacom2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug  3 19:50:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-08-03  19:50:03
   Commandline: apt-get install -f
   Requested-By: thomas (1000)
   Upgrade: libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1)
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller 
[10cf:150a]
  InstallationDate: Installed on 2017-07-22 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: FUJITSU LIFEBOOK AH530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=27e085d5-ec9d-4e23-81e3-fe76537c7d5c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libwacom
  Title: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.19
  dmi.board.name: FJNBB06
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd08/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK AH530
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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
  xserver.bootTime: Thu Aug  3 18:12:36 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1708503/+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 1712011] Re: Unable to close Printer properties

[Jeremy Bicha]

** Description changed:

  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.
  
  Occurs using 17.10 default and Wayland.
  
  Screenshot added
+ 
+ Workaround
+ --
+ Press the Esc key to close the dialog.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
-Subsystem: Dell Radeon HD 6670 [1028:0b0e]
+  Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
+    Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
-  inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
-  inputUSB OPTICAL MOUSEMOUSE, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
+  inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
+  inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

Title:
  Unable to close Printer properties

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

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  Workaround
  --
  Press the Esc key to close the dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh 

[Desktop-packages] [Bug 1718643] [NEW] Inability to move child dialogues separate from parent applicaitons

[Peter Clifton]

Public bug reported:

When dragging a save dialogue (or similar) in the latest A Ubuntu
release, the WM does not allow me to move the dialogue independently
from the application.

This is a huge nuisance, in the case where I want to move the dialogue
to uncover some text from the underlying document, to construct a save
file name (e.g. matching title of document to filename etc..).

It is really unexpected that dragging the title bar of an dialogue also
moves the parent application.

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

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

Title:
  Inability to move child dialogues separate from parent applicaitons

Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  When dragging a save dialogue (or similar) in the latest A Ubuntu
  release, the WM does not allow me to move the dialogue independently
  from the application.

  This is a huge nuisance, in the case where I want to move the dialogue
  to uncover some text from the underlying document, to construct a save
  file name (e.g. matching title of document to filename etc..).

  It is really unexpected that dragging the title bar of an dialogue
  also moves the parent application.

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