[Desktop-packages] [Bug 1755366] Re: gnome-shell crashed with signal 5

[Apport retracing service]

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

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 #1748450, 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/1755366/+attachment/5077737/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell (gdm user) crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 18:47:20 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1520332728
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-12-27 (1536 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.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 bionic on 2018-02-09 (31 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755366/+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 1755362] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755362/+attachment/5077693/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The computer suddenly crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 20:24:21 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755362/+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 1755361] [NEW] package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Edman Kasperjov]

Public bug reported:

snap

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 shotwell: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Mar 12 21:19:59 2018
DpkgTerminalLog:
 dpkg: error processing package shotwell (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2018-02-11 (29 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: shotwell
Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shotwell (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 shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1755361

Title:
  package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in shotwell package in Ubuntu:
  New

Bug description:
  snap

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   shotwell: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Mar 12 21:19:59 2018
  DpkgTerminalLog:
   dpkg: error processing package shotwell (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2018-02-11 (29 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: shotwell
  Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1755361/+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 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Daniel van Vugt]

Thanks.

This certainly looks like a kernel bug or hardware failure. Your errors
coming from the 'pcieport' kernel module appear to correlate with errors
from the 'nvme' module (for a solid state hard drive). So I think that's
the problem area, which will indeed slow down everything and make
various hardware devices non-responsive.

Your description also mentions wifi issues (which would be your
'ath10k_pci' kernel module) but I think that's most likely a side-effect
of the PCIe problems from the former.

If I had to guess then you probably need one of:
  (a) a kernel bug fix; or
  (b) a new solid state drive; or
  (c) a new motherboard.

We'll wait and see what the kernel people say...

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

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

** Summary changed:

- 18.04 3.27 Gnome-shell Near-Fatalities
+ Lots of pcieport and nvme kernel errors on resuming from sleep - system 
non-responsive

** Summary changed:

- Lots of pcieport and nvme kernel errors on resuming from sleep - system 
non-responsive
+ Lots of pcieport and nvme kernel errors - system non-responsive

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

Title:
  Lots of pcieport and nvme kernel errors - system non-responsive

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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/1754425/+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 1754425] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1754425

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (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/1754425

Title:
  Lots of pcieport and nvme kernel errors - system non-responsive

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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/1754425/+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 1740291] Re: evince crashed with SIGSEGV in g_list_length()

[Launchpad Bug Tracker]

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

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

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

Title:
  evince crashed with SIGSEGV in g_list_length()

Status in evince package in Ubuntu:
  Expired

Bug description:
  I wanted to search in a LaTeX beamer document.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 19:30:09 2017
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2017-10-13 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f0468a790e0 : mov
0x8(%rdi),%rdi
   PC (0x7f0468a790e0) ok
   source "0x8(%rdi)" (0xdbcc8c08) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   g_list_length () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
   ev_view_find_restart () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evince crashed with SIGSEGV in g_list_length()
  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/ubuntu/+source/evince/+bug/1740291/+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 1739019] Re: Gnome Shell does not start in Xorg mode

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  In Ubuntu 17.10 and 17.04, Gnome session has stopped working with the X11 
mode for me. Selecting "Ubuntu on X" in GDM logs me in to a black screen with 
the cursor. If I have an app configured to auto start, the app launches without 
any window decorations. Clicking the app through File > Quit menu turns the 
cursor in a black cross.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739019/+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 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

** Attachment added: "dmesg.text"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+attachment/5077678/+files/dmesg.text

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

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

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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/1754425/+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 1754759] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1754759

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754759/+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 1755349] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear().

[Apport retracing service]

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

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 #1754202, 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/1755349/+attachment/5077656/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1755349

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear().

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Happened after i closed the app.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 13 04:34:45 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=da
   PATH=(custom, no user)
   LANG=da_DK.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f575ae43517 :mov
0x28(%rdi),%rbp
   PC (0x7f575ae43517) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  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-calendar/+bug/1755349/+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 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop

[Kai-Heng Feng]

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

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

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

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

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754759/+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 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

[shankao]

Shouldn't this info be included in the original report that ubuntu-bug
creates? It would remove the step of asking it later in the bug report

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

Title:
  LLVMpipe renderer used instead of Intel on Xorg sessions

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1603183] Re: Bottom right area of touchpad no longer treated as right click

[Daniel van Vugt]

Incomplete for libinput. I misread comment 18.

Is there still a bug at all?

** No longer affects: libinput

** Changed in: libinput (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

You can also modify the xorg.conf to prioritize modesetting driver over
intel.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

[shankao]

$ apt-cache policy libegl-mesa0 libglx-mesa0
libegl-mesa0:
  Installed: 18.0.0~rc4-1ubuntu3
  Candidate: 18.0.0~rc4-1ubuntu3
  Version table:
 *** 18.0.0~rc4-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libglx-mesa0:
  Installed: 18.0.0~rc4-1ubuntu3
  Candidate: 18.0.0~rc4-1ubuntu3
  Version table:
 *** 18.0.0~rc4-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  LLVMpipe renderer used instead of Intel on Xorg sessions

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

[Kain Centeno]

just happened to me again. deja-dup running on the background, no backup
setup

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in deja-dup source package in Bionic:
  Confirmed
Status in webkit2gtk source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1751460/+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 1755326] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1755326

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755326/+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 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Daniel van Vugt]

Please attach the full output from dmesg (as a file):

dmesg > dmesg.txt


** Description changed:

- If I close the lid, it seems that the computer flat-out doesn't wake up.
+ If I open the lid, it seems that the computer flat-out doesn't wake up.
  HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
  the power button, SOMETIMES, the computer will "snap out of it" and come
  back to my desktop. Although RAM is 25% used, and CPU usage is around
  25-50% or less (depending on apps), mouse will regularly freeze up for
  some seconds every 10 seconds or so. Wifi will claim to be "on", but
  there aren't any networks in the "select network" dialogue. Turning wifi
  off and then on does not fix this problem. So I'll be in this terrifying
  state of non-responsive every few seconds computer, with no ability to
  reconnect to networks and report bug.
  
  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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)

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

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

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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/1754425/+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 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

[Daniel van Vugt]

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

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755326/+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 1755166] Re: gnome-shell crashed with SIGSEGV in _g_type_boxed_copy() from boxed_proxy_collect_value() from intel_update_image_buffers() from intel_update_renderbuffers()

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in _g_type_boxed_copy() from 
boxed_proxy_collect_value() from intel_update_image_buffers() from 
intel_update_renderbuffers()

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

Title:
  gnome-shell crashed with SIGSEGV in _g_type_boxed_copy() from
  boxed_proxy_collect_value() from intel_update_image_buffers() from
  intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not sure if a duplicate still, but this crashes the window manager
  whenever I turn my monitor back on.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 08:49:42 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-05-28 (288 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f33a2b01a4b:mov0x8(%rax),%rax
   PC (0x7f33a2b01a4b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755166/+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 1755144] Re: No audio on vlc or videos sound or video files

[Daniel van Vugt]

First, please check System Settings > Sound > Applications
and verify (while running) that the problematic applications aren't muted or 
have different volume.

Second, it's interesting you say a few weeks ago because the latest
pulseaudio update is only a few weeks old:

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.8

Maybe try downloading and manually installing the previous version's
packages from here:

https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.7/+build/1375

It looks like you should only need to get the ones named:

  libpulse0, libpulsedsp, pulseaudio, pulseaudio-module-x11, pulseaudio-
utils


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

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

Title:
  No audio on vlc or videos sound or video files

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Up until a few weeks ago there was no problem with playing sound from mp3 
files. I have a pair of usb speakers. Audio plays Ok on them for video clips 
using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), 
neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok 
using Rhythmbox. I've also tried vlc 3.0 with no success.
  Interestingly, the standard Videos app (Totem?) also doesn't play sound on 
these speakers either of an mp4 file (downloaded from YouTube, though it plays 
Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I 
first reported this as bug 1752267 as I thought that the problem was with vlc. 
On that bug, it was suggested that the problem is with Pulseaudio.
  Just now, I've tried to play sound through my monitor's built in speakers 
connected by hdmi (though the monitor displays Ok) with no success even though 
the built-in speakers play sound using pavucontrol when testing is invoked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  john   2410 F pulseaudio
   /dev/snd/controlC0:  john   2410 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 12 11:06:46 2018
  InstallationDate: Installed on 2016-12-08 (458 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1754862] Re: Screen remains active on lid close

[Daniel van Vugt]

Yes for JournalErrors.txt it would be better to get a fresh log after
the problem occurs.

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

Title:
  Screen remains active on lid close

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9370 (early 2018 model) with Ubuntu 17.04
  installed. I use the Gnome on XOrg session.

  When I close the laptop lid, I can see through the small (< 1mm) hairline 
crack that the screen is still active, showing the entire desktop. This happens 
only once I am logged in to the gnome shell session, I tried closing the lid 
before logging and the screen is correctly blanked.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-03-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754862/+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 894496] Re: Add support for Google Play Music

[Bug Watch Updater]

** Changed in: amarok
   Status: Fix Released => Won't Fix

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

Title:
  Add support for Google Play Music

Status in Amarok:
  Won't Fix
Status in Banshee:
  New
Status in Exaile:
  Won't Fix
Status in Unity:
  Confirmed
Status in audacious package in Ubuntu:
  New
Status in banshee package in Ubuntu:
  Triaged
Status in clementine package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Add support for Google Music to Unity as a scope.
  https://music.google.com/

  And to media players as a music store and music cloud storage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amarok/+bug/894496/+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 1754903] Re: "Close" string not marked for translation

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.27.92-0ubuntu3

---
gnome-software (3.27.92-0ubuntu3) bionic; urgency=medium

  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix string not marked for translation (LP: #1754903)

 -- Robert Ancell   Tue, 13 Mar 2018
12:52:50 +1300

** Changed in: gnome-software (Ubuntu)
   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/1754903

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 1733335] Re: gnome-shell crashed with SIGABRT in meta_bug()

[chris pollock]

Crash happened again this evening for no apparent reason.

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

Title:
  gnome-shell crashed with SIGABRT in meta_bug()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/3b3e47f50b53e343bec0f21df4482cb7471f9270

  ---

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.3
    Candidate: 3.18.5-0ubuntu0.3
    Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Gnome-shell crashed while loading a message in Evolution.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Nov 20 08:37:56 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (1123 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_bug () from /usr/lib/libmutter.so.0
   ?? () from /usr/lib/libmutter.so.0
   meta_core_begin_grab_op () from /usr/lib/libmutter.so.0
   meta_ui_frame_handle_event () from /usr/lib/libmutter.so.0
   meta_window_handle_ungrabbed_event () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in meta_bug()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/175/+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 1755326] [NEW] Periodic glitch in sound with Firewire and snd-dice

[Kim Ake]

Public bug reported:

I have a fresh installation of Ubuntu 17.10 with almost nothing extra
installed yet besides Bitwig Studio, Cadence and a few other things from
the KX Studio repositories.

But I also tried the bug after a fresh install with nothing else than
Bitwig Studio installed, it's the same.

I have a TC Electronics Impact Twin Firewire audio interface.
It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

The ALSA snd-dice drivers work, but with glitches.

There is a periodic, glitch in the sound that sounds like a part of the stream 
is missing, or something. It is steady in timing, nothing seems to have an 
effect on it.
Recording seems to work. All outputs and inputs, also the ADAT outputs seem to 
work, altough I could not test if the ADAT outputs feature the glitch too.

Seemingly randomly there might be a short maybe around 0.3 second total
break in the sound.

I'm not getting xruns at all.

I tried also Ubuntu Studio live USB, it has the exact same glitch. I
also tried a Native Instruments Audio2DJ USB interface, with that there
is no problem with the sound on my computer.

I tried also with Carla and ZynAddSubFx, and also with the live USB of
Linux Mint (current version), and the same glitch is present.

I tried also another Firewire controller card with a XIO2200A Texas
Instruments chip, it features the same glitch, but running a different
speed.

I had a KX Studio 14.x installation a few years ago, where the interface
was working without a hitch. But then I was running with FFADO.

So to me it seems that the kernel integration of snd-dice has some
problem with timing with a TC Electronics interface?

I could not get FFADO to run with Jack now so I can't say if the FFADO
implementation would work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
 /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
 /dev/snd/controlC4:  kim3563 F jackdbus
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 13 02:11:51 2018
InstallationDate: Installed on 2018-03-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-bug artful third-party-packages wayland-session

** Attachment added: "Sound output recorded through a Tascam DR-44WL recorder"
   
https://bugs.launchpad.net/bugs/1755326/+attachment/5077558/+files/180313_0044S3.wav

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  

[Desktop-packages] [Bug 1755327] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755327/+attachment/5077565/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  immediately at reboot after update installation

  maybe from this? gnome-session-common:amd64 (3.27.91-0ubuntu3, 3.27.91-0ubu
  ntu4)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  Uname: Linux 4.16.0-041600rc4-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 20:17:49 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-08 (155 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171007)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (118 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755327/+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 1755320] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755320/+attachment/5077521/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Had just rebooted after Software Updater running.

  Another potential bug (DHCP/network guys): From syslog [cat syslog |
  grep Renewing] shows that the DHCP client is either requesting a very
  short lease, or that's what's being provided.  Please refer this one.

  syslog attached.

  matt

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 16:28:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-06 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755320/+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 1754903] Re: "Close" string not marked for translation

[Robert Ancell]

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => 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/1754903

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 844582] Re: "Invalid argument" when trying to scan

[Rolf Leggewie]

Hans, we can certainly disagree.  But it seems you as well as some of
the upstream devs do not understand much about packaging.  If you want
timely fixes, pay someone to do it.  If you want to make a mess of your
system, install random packages.  I'm fine with any of that.  I'm not
fine if then such person comes back and waste Ubuntu devs time with a
problem they did not create or gives Ubuntu a bad name that they did not
deserve in this case.  I hope that makes sense.

BTW, scanner support is the responsibility of the manufacturer, don't
you think?  Have you complained to them about lack of FOSS support?
Have you taken this into consideration when you purchased your scanner?
Or have you simply purchased whatever was cheapest?  IMO, what is not
acceptable is buying cheap, unsupported stuff and then complaining to
people doing a LOT of work for you for free.  Last comment, if you feel
that all of this is so unacceptable then have you rolled up your sleeve
and provided a patch or at least tried to?

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  "Invalid argument" when trying to scan

Status in gscan2pdf package in Ubuntu:
  Incomplete
Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
  it works more or less well with Ubuntu.

  I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
  another scanner.

  All I get is a meaningless "Invalid argument" when I hit the scan
  button.

  When I start gscan2pdf from the command line I see these lines
  appearing when I hit the scan button:

  Error running process: Died at (eval 39) line 7.

$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
 print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}

my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
 $device->cancel;
 $shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
 $shash{$sane_thread}{go} = 0;
 die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gscan2pdf 0.9.31-2
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Thu Sep  8 09:44:25 2011
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no username)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gscan2pdf
  UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+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 1754903] Re: "Close" string not marked for translation

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 385948] Re: Invest stock data does not refresh automatically

[Bug Watch Updater]

** Changed in: gnome-applets
   Status: In Progress => Expired

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

Title:
  Invest stock data does not refresh automatically

Status in GNOME Applets:
  Expired
Status in gnome-applets package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-applets

  Running the Invest GNOME-applet (2.26.1) on Ubuntu 9.04.  The stock
  data does not refresh automatically, I have to right-click on the
  applet and select "refresh."  There doesn't seem to be any options for
  controlling a refresh interval.

  Stock data should periodically refresh automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-applets/+bug/385948/+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 1754903] Re: "Close" string not marked for translation

[Robert Ancell]

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

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

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

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 1637107] Re: Wrong audio profile (on a Skylake system), causing volume problems.

[Ubfan]

See bug Bug #1755309 for the mismatched prototype in the 4.4 linux
headers for i915_component.h -- preventing building the HDMI audio code.
The 4.10 kernel code finally matched the prototype, and the
intel_audio.c file compiles.

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

Title:
  Wrong audio profile (on a Skylake system), causing volume problems.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Skylake system (ASRock Z170 Gaming-ITX/ac) with (x)Ubuntu
  16.04.

  My speakers are connected via the SPDIF port, but there is a problem.

  When I inspect the audio profile (in `pavucontrol`), I see that `Analog 
Stereo Output (unplugged)` is selected.
  The speakers play regularly, even if this profile is wrong, but the volume 
doesn't work correctly - anything above mute will cause the speakers to play at 
maximum volume.

  If I choose the `Digital Stereo (IEC958)`, the speakers won't receive
  any signal at all.

  Debug info:

  ~$ lspci -vv # extract
  00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
Subsystem: ASRock Incorporation Sunrise Point-H HD Audio
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  ~$ dmesg | grep 00:1f.3
  [0.181004] pci :00:1f.3: [8086:a170] type 00 class 0x040300
  [0.181034] pci :00:1f.3: reg 0x10: [mem 0xdf14-0xdf143fff 
64bit]
  [0.181062] pci :00:1f.3: reg 0x20: [mem 0xdf12-0xdf12 
64bit]
  [0.181091] pci :00:1f.3: PME# supported from D3hot D3cold
  [0.181176] pci :00:1f.3: System wakeup disabled by ACPI
  [0.579846] iommu: Adding device :00:1f.3 to group 8
  [3.126041] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915_bpo])
  [4.185983] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input11
  [4.186034] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input12
  [4.186081] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1f.3/sound/card0/input13
  [4.186135] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input14
  [4.186188] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input15
  [4.186228] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input16
  [4.186267] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input17
  [4.186304] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input18

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   saverio3012 F...m pulseaudio
   /dev/snd/controlC0:  saverio3012 F pulseaudio
   /dev/snd/controlC1:  saverio3012 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Oct 27 10:21:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (108 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Microsoft® LifeCam VX-2000 - Microsoft® LifeCam VX-2000
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.10
  dmi.board.name: Z170 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Burt P.]

I spoke too soon, the lock screen is still 640x480, but when unlocked it
returns to 1920x1080. I can live with this, but something is still wrong
with the driver.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1755305] [NEW] .xsession-errors filled with entries

[Brian]

Public bug reported:

I hope I am in the right place for this. My .xsession-errors file is
filled with entries in the following format, in that order/sequence,
over and over and continuously:

(nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
'GTK_IS_WIDGET (widget)' failed

(nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
'GTK_IS_WIDGET (widget)' failed

(nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which has
a parent

Ubuntu MATE 17.10

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

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

Title:
  .xsession-errors filled with entries

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

Bug description:
  I hope I am in the right place for this. My .xsession-errors file is
  filled with entries in the following format, in that order/sequence,
  over and over and continuously:

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-CRITICAL **: gtk_widget_destroy: assertion
  'GTK_IS_WIDGET (widget)' failed

  (nm-applet:1839): Gtk-WARNING **: Can't set a parent on widget which
  has a parent

  Ubuntu MATE 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1755305/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10

[genti]

Yes, it's working for me with 1.0.27. I compiled from the same Git
source like you. I own a CanoScan LIDE 200.

The problem was obviously the use of rewind instead of slow_back_home
(see posted link). In the source I compiled it was using slow_back_home
again at the very specific position mentioned in the link I posted
earlier (somewhere around line 2069).

sane-config --version says that I have 1.0.27 installed.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  On Windows it works but on my Ubuntu 17.10 I see a black band on
  scanned image. The scanner is Canon CanoScan LIDE100. Libsane version
  is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+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 1755297] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()

[Apport retracing service]

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

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 #1754202, 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/1755297/+attachment/5077466/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1755297

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Gnome Calendar is crashing when I am adding my Google account.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 22:31:39 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2016-04-03 (708 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160401)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f69f42be517 :mov
0x28(%rdi),%rbp
   PC (0x7f69f42be517) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-03-10 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1755297/+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 1755296] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755296/+attachment/5077456/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed suddenly while using OS

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 22:21:34 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-11 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755296/+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 1755283] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755283/+attachment/5077431/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  just having firefox open and browsing the net

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 21:06:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-23 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755283/+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 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

[Timo Aaltonen]

wrong package, sorry:

apt-cache policy libegl-mesa0 libglx-mesa0

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

Title:
  LLVMpipe renderer used instead of Intel on Xorg sessions

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1755277] [NEW] Fail start x

[diego ezequiel]

Public bug reported:

No desktop visual start. After sleep partial funcionality with errors.
Sorry.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic i686
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: i386
CompositorRunning: None
Date: Mon Mar 12 17:01:51 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
   Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
InstallationDate: Installed on 2018-03-11 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20180106)
MachineType: LENOVO 1952AP6
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=dc47c574-ff68-42ce-a683-ac420cedf1bd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETC9WW (2.09 )
dmi.board.name: 1952AP6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETC9WW(2.09):bd12/22/2006:svnLENOVO:pn1952AP6:pvrThinkPadT60:rvnLENOVO:rn1952AP6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 1952AP6
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.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 Mar 12 16:47:07 2018
xserver.configfile: default
xserver.errors:
 event5  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
 event5  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16448 
 vendor LEN
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: apport-bug artful i386 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/1755277

Title:
  Fail start x

Status in xorg package in Ubuntu:
  New

Bug description:
  No desktop visual start. After sleep partial funcionality with errors.
  Sorry.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic i686
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  CompositorRunning: None
  Date: Mon Mar 12 17:01:51 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2018-03-11 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20180106)
  MachineType: LENOVO 1952AP6
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=dc47c574-ff68-42ce-a683-ac420cedf1bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETC9WW (2.09 )
  dmi.board.name: 1952AP6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

Re: [Desktop-packages] [Bug 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()

[stephen saines]

I can't completely confirm mine was at Chromium app shutdown, but it
probably was, as I also didn't notice it until seeing the crash icon in the
launcher. I usually shutdown a browser app when too tabs have accumulated.
It's the first instance I've noticed on Chromium, which has otherwise been
stable. I use in lieu of FF which is very unstable, and usually crashes
when trying to open a new tab.

I do update daily, so if Chromium becomes a problematic trend, I'd suspect
an update. So far though, Chromium appears rock-solid other than that
glitch.

On Mon, Mar 12, 2018 at 3:18 PM, Olivier Tilloy <
olivier.til...@canonical.com> wrote:

> Thanks for the confirmation Tom. Until now I didn't even know when that
> crash happened, this will be helpful in reproducing the issue and
> investigating it.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1753259).
> https://bugs.launchpad.net/bugs/1729963
>
> Title:
>   chromium-browser crashed in OnConnectionDisconnectedFilter()
>
> Status in chromium-browser package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding chromium-browser.  This problem was most recently seen with
> package version 62.0.3202.62-0ubuntu0.17.10.1380, the problem page at
> https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884
> 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/chromium-browser/+bug/1729963/+
> subscriptions
>


-- 
stephen saines
cell  647 631 0711

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

Title:
  chromium-browser crashed in OnConnectionDisconnectedFilter()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
62.0.3202.62-0ubuntu0.17.10.1380, the problem page at 
https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 
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/chromium-browser/+bug/1729963/+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 250997] Re: gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string()

[Bug Watch Updater]

** Changed in: gnome-applets
   Status: New => Expired

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

Title:
  gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string()

Status in GNOME Applets:
  Expired
Status in gnome-applets package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-applets

  N/A

  ProblemType: Crash
  Architecture: i386
  Date: Tue Jul 22 14:25:49 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/lib/gnome-applets/gweather-applet-2
  NonfreeKernelModules: nvidia
  Package: gnome-applets 2.22.2-0ubuntu2
  PackageArchitecture: i386
  ProcCmdline: /usr/lib/gnome-applets/gweather-applet-2 
--oaf-activate-iid=OAFIID:GNOME_GWeatherApplet_Factory --oaf-ior-fd=22
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gnome-applets
  StacktraceTop:
   ?? () from /usr/lib/libbonoboui-2.so.0
   ?? () from /usr/lib/libbonoboui-2.so.0
   ?? () from /usr/lib/libbonoboui-2.so.0
   bonobo_ui_node_to_string () from /usr/lib/libbonoboui-2.so.0
   bonobo_ui_util_set_ui () from /usr/lib/libbonoboui-2.so.0
  Title: gweather-applet-2 crashed with SIGSEGV in bonobo_ui_node_to_string()
  Uname: Linux 2.6.24-19-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
powerdev scanner video

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-applets/+bug/250997/+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 1561278] Re: internal sound card not detected HP X2

[Francisco Postigo García]

This pc has the same audio chip
may anyone try?

https://ubuntu-mate.community/t/intel-22b8-sound-chip-no-soundcard-
found-on-hp-x2-210-g2/10673/6

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1561278] Re: internal sound card not detected HP X2

[Francisco Postigo García]

What? you got audio working in HDMI?
is there any way to fool ubuntu to think that the hdmi is connected and derive 
the sound to the speakers?
and i will try with Ubuntu 18.04

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()

[Olivier Tilloy]

Thanks for the confirmation Tom. Until now I didn't even know when that
crash happened, this will be helpful in reproducing the issue and
investigating it.

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

Title:
  chromium-browser crashed in OnConnectionDisconnectedFilter()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
62.0.3202.62-0ubuntu0.17.10.1380, the problem page at 
https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 
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/chromium-browser/+bug/1729963/+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 1755262] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755262/+attachment/5077326/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Start up my computer and the error just poped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 14:45:55 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-15 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

[Sebastien Bacher]

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

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

Title:
  gnome-appearance-properties crashed with SIGSEGV in
  g_main_context_dispatch()

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

Bug description:
  Binary package hint: gnome-control-center

  I don't speak English

  ProblemType: Crash
  Architecture: i386
  Date: Fri Nov  6 20:03:48 2009
  Disassembly: 0x1bc92c0:   Cannot access memory at address 0x1bc92c0
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-appearance-properties
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:2.28.1-0ubuntu1
  ProcCmdline: gnome-appearance-properties --show-page=background
  ProcEnviron:
   LANGUAGE=ru_RU.UTF-8
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SegvAnalysis:
   Segfault happened at: 0x1bc92c0: Cannot access memory at address 
0x1bc92c0
   PC (0x01bc92c0) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   g_main_context_dispatch () from /lib/libglib-2.0.so.0
   ?? () from /lib/libglib-2.0.so.0
  Title: gnome-appearance-properties crashed with SIGSEGV in 
g_main_context_dispatch()
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev 
sambashare scanner tape video

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

[Sebastien Bacher]

Robert, that's a segfault in the snap/channel code, could you have a
look?

** Information type changed from Private to Public

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

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  gnome-software crashed with SIGSEGV in g_ptr_array_add()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.92-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 11 23:22:06 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-03 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.27.92-0ubuntu2
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f497b574e07 :   mov
%rbp,(%rdx,%rax,8)
   PC (0x7f497b574e07) ok
   source "%rbp" ok
   destination "(%rdx,%rax,8)" (0x) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   g_ptr_array_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
   ?? ()
   ?? ()
  Title: gnome-software crashed with SIGSEGV in g_ptr_array_add()
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1755198/+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 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()

[tom]

It can happen at application shutdown, this has happened at least twice
for me.

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

Title:
  chromium-browser crashed in OnConnectionDisconnectedFilter()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
62.0.3202.62-0ubuntu0.17.10.1380, the problem page at 
https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 
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/chromium-browser/+bug/1729963/+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 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

1. Yes, opening the lid.

2. In dmesg, I see a ton of 
[52698.053359] pcieport :00:1d.0: AER: Corrected error received: id=00e8
[52698.053373] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e8(Transmitter ID)
[52698.053383] pcieport :00:1d.0:   device [8086:a118] error 
status/mask=1000/2000
[52698.053389] pcieport :00:1d.0:[12] Replay Timer Timeout  

repeating  over and over.

3. lspci -k
hangs the system for several seconds. then:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 05)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
Subsystem: Dell Device 07be
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 05)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
Subsystem: Dell Sunrise Point-H USB 3.0 xHCI Controller
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal 
subsystem (rev 31)
Subsystem: Dell Sunrise Point-H Thermal subsystem
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial 
IO I2C Controller #0 (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial 
IO I2C Controller #1 (rev 31)
Subsystem: Dell Sunrise Point-H Serial IO I2C Controller
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
Subsystem: Dell Sunrise Point-H CSME HECI
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31)
Subsystem: Dell Sunrise Point-H SATA Controller [AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
Subsystem: Dell Sunrise Point-H LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
Subsystem: Dell Sunrise Point-H PMC
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
Subsystem: Dell CM238 HD Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
Subsystem: Dell Sunrise Point-H SMBus
Kernel modules: i2c_i801
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev 
a1)
Subsystem: Dell GP107M [GeForce GTX 1050 Mobile]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
Subsystem: Dell RTS525A PCI Express Card Reader
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
04:00.0 Non-Volatile memory controller: Device 1c5c:1283
Subsystem: Device 1c5c:
Kernel driver in use: nvme


when i try to copy the text in terminal, it 

[Desktop-packages] [Bug 1754932] Re: Files won't open from nautilus (error dispatching to Wayland display)

[Sebastien Bacher]

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

the issue is going to be fixed in 3.28, see
https://gitlab.gnome.org/GNOME/mutter/issues/63

** Package changed: nautilus (Ubuntu) => mutter (Ubuntu)

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Files won't open from nautilus (error dispatching to Wayland display)

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  When using Nautilus, clicking on files or hitting "enter" won't open the 
file. Instead, nautilus window closes.
  This happens whatever the file type is, and whatever application is to be 
used to view the file.

  When launched from a shell, nautilus prints the error message:

  Gdk-Message: 09:25:04.445: Error 71 (Protocol error) dispatching to
  Wayland display.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 11 09:20:10 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-01-22 (47 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1754932/+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 1594424] Re: Evince window spans several monitors

[Launchpad Bug Tracker]

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

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

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

Title:
  Evince window spans several monitors

Status in Evince:
  Confirmed
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  When opening some PDF files, the Evince window sometimes span several 
monitors. I have a vertical two-monitor setup (one monitor above the other). 
The primary monitor is on top and is external, while the other one (below) is 
the laptop's panel.
  In some cases, when opening a PDF, the Evince window is taller than a single 
monitor, sometimes spanning the full height of both monitors, sometime 
something in-between. If I resize the window, close the file, and open it 
again, Evince remembers its last size and position.

  Evince is the only application affected by this problem on my system.

  It seems to be related to these bug reports:
  https://bugzilla.redhat.com/show_bug.cgi?id=460810 (comment #24)
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587152

  The example attachment on the redhat tracker does trigger the issue on
  my system: https://bugzilla.redhat.com/attachment.cgi?id=959040

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 20 10:58:17 2016
  InstallationDate: Installed on 2015-01-23 (513 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (91 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1594424/+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 1755254] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755254/+attachment/5077283/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I restart my laptop I get this error after login.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar  9 22:52:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-07 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  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:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755254/+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 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

[Rik Mills]

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

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in casper package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1572244/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[fu2qi4]

How to install the latest gcc compiler without pain

sudo add-apt-repository --remove ppa:ubuntu-toolchain-r/test # the best 
remedy whatsoever
sudo add-apt-repository --remove ppa:jonathonf/gcc-7.2# (also 
broken  
https://askubuntu.com/questions/1009433/dependency-issues-while-installing-gcc-7-3-from-jonathon-fs-ppa)

sudo add-apt-repository -y ppa:jonathonf/gcc
sudo apt-get update
sudo apt-get install gcc-8 g++-8 # will install 7.3.0-5ubuntu1~16.04.york0
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 40 --slave 
/usr/bin/g++ g++ /usr/bin/g++-8

As Asus ROG user i'm aware of ongoing struggle with Nvidia driver, which
is in conflict with Devian-based systems (https://bugs.debian.org/cgi-
bin/pkgreport.cgi?pkg=nvidia-driver;dist=unstable
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852152  ).

I disable NVidia card editing boot config

(Restart your computer and enter BOIS (hold down f2)
Change boot priority to boot to your USB Stick first.
Save and reboot
When the grub boot loader menu is visible highlight “Try Ubuntu GNOME without
installing” (use your up and down arrows)
 Press “e” on your keyboard, this will allow you to edit the boot config.
nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux
i915.preliminary_hw_support=1 idle=nomwait

Run the command: sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get 
-y
dist-upgrade
Remove all Nvidia installs(if any), run this command: 
sudo apt-get purge nvidia*
 Run the command: sudo apt-get install nvidia-361-updates nvidia-prime
 Reboot: sudo reboot

I used boot-repair software https://sourceforge.net/p/boot-repair/home/Home/ 
It was indispensable
=
Links, used in combination with each other. Nothing is like a silver bullet.
https://jeremymdyson.wordpress.com/2016/04/27/ubuntugnome-16-04-on-asus-rog-gl552v/
https://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/
https://askubuntu.com/questions/624966/cant-login-after-nvidia-driver-install-v-14-04
https://www.reddit.com/r/linux/comments/4etbsw/nouveau_error_during_installation_of_ubuntu_gnome/

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

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 

[Desktop-packages] [Bug 1317752] Re: Right-clicking a file, choosing "Open With -> Other Application" provides no way to run an arbitrary command on the file

[Ads20000]

Please could a Bug Control member mark this Won't Fix as per
https://gitlab.gnome.org/GNOME/nautilus/issues/291#note_79791 ?

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

Title:
  Right-clicking a file, choosing "Open With -> Other Application"
  provides no way to run an arbitrary command on the file

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I installed Sublime Text 3 from a third-party source.  That installed
  and worked fine, and it shows up in the Applications menu as normal.
  When I right click any file (I've tried Makefiles and .txt files),
  click "Open With", then click "Other Application", there's a list of
  possible programs I can open the given file from.  Problem is, if the
  program I want to use isn't on that list, I can't use it--i.e. I can't
  put in an arbitrary command that can be saved and used in the future.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri May  9 02:03:14 2014
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+0+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-09-26 (224 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to saucy on 2013-11-01 (188 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1317752/+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 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://

[Ads20000]

Upstream says their latest stable and master works fine (see previous
link), so this is an Ubuntu-specific bug

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

Title:
  Segmentation fault whilst opening Rubbish Bin/ trash://

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ 
vivid/main amd64 Packages
  Ubuntu 15.04 amd64 on an i5-4670K CPU

  Hi, I'm currently getting a consistent SIGSEGV from Nautilus when
  attempting to open the rubbish bin. This happens whether I click the
  bookmark on the left or instantaneously if I run `nautilus trash://`.
  The crash occurs before the icons have fully loaded, but a second
  after the rubbish bin is selected.

  I installed the debug symbols for nautilus and ran with gdb and got
  the following output:

  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
  [Thread 0x77f8ba00 (LWP 21736) exited]
  [Inferior 1 (process 21736) exited normally]
  (gdb) run
  Starting program: /usr/bin/nautilus 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  nautilus-wipe-Message: Initializing
  [New Thread 0x7fffe9017700 (LWP 22649)]
  [Thread 0x7fffe9017700 (LWP 22649) exited]
  [New Thread 0x7fffc1347700 (LWP 22680)]
  [New Thread 0x7fffe35f1700 (LWP 22651)]
  [New Thread 0x7fffe3fff700 (LWP 22650)]
  [New Thread 0x7fffe9818700 (LWP 22648)]

  Program received signal SIGSEGV, Segmentation fault.
  0x7372332e in __GI__IO_default_xsputn (f=0x7f7ff5f0, 
data=0x50e080, n=6) at genops.c:447
  447   genops.c: No such file or directory.

  I can provide more info if needed as I can easily reproduce the bug. I
  know a little about using gdb as well, but may need a bit of guidance
  as I'm no hardened C programmer. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

Olivier:
1) Yes
2) Yes
3) Yes
4) I'll have to log out and/or reboot to get it back into that state.  Will 
post when I get a chance to do that.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1755242] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1755242/+attachment/5077242/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 12 19:35:57 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-03-04 (373 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755242/+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 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

[Rik Mills]

Seems there is still another aspect to this, resulting in it still being
unfixed for the Kubuntu Live session.

casper runs in scripts/casper-bottom/34disable_kde_services

rm -f /root/usr/share/kde4/services/kwalletd.desktop
rm -f /root/usr/share/kservices5/kwalletd5.desktop
rm -f /root/usr/share/dbus-1/services/org.kde.kwalletd5.service
rm -f /root/usr/share/dbus-1/services/org.kde.kwalletd.service

which was done in 2015 to stop kwallet dunning in the live session
completely.

This sadly now has the consequence that plasma-nm sees no actual written
config disabling kwalllet, but maybe simply fails to access it thinking
it should be available, then falls back to the password with network
manager. Hence possibly the double password request.

Since 2016 releases of plasma 5.7.x the change "Store password into
NetworkManager by default when KWallet is not enabled" enables fallback
to network manager, but seemingly only when plasma-nm knows kwallet is
disabled by config, not when it has been just broken by casper.

So one possible solution could be to leave kwallet's files in place, but
write a temp config file 'kwalletrc' for just the live session disabling
kwallet, so plasma-nm knows to not use it, hence using a working route
first time.

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1755248] Re: Network card does not connect anymore

[lotuspsychje]

*-network:1
   description: Ethernet interface
   product: 3c940 10/100/1000Base-T [Marvell]
   vendor: 3Com Corporation
   physical id: e
   bus info: pci@:00:0e.0
   logical name: enp0s14
   version: 12
   serial: 00:50:8d:f5:59:c6
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 66MHz
   capabilities: pm vpd bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=skge 
driverversion=1.14 duplex=full latency=32 link=yes maxlatency=31 mingnt=23 
multicast=yes port=twisted pair speed=100Mbit/s
   resources: irq:22 memory:eb014000-eb017fff ioport:b400(size=256)

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

Title:
  Network card does not connect anymore

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 daily @ 12/3/2018

  Network card does not connect anymore an several machines and ubuntu versions 
18.04 daily & 16.04
  with different chipsets, this bug has been following around across many 
ubuntu versions, please fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 18:33:10 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-16 (86 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  IpRoute:
   default via 192.168.1.1 dev wlp0s9 proto dhcp metric 600
   169.254.0.0/16 dev wlp0s9 scope link metric 1000
   192.168.1.0/24 dev wlp0s9 proto kernel scope link src 192.168.1.4 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
   ACTIVE-PATH SLAVE
   Wired connection 1  23c53d9f-11b8-3a57-9683-119513fb5647  ethernet  
1515749288  vr 12 jan 2018 10:28:08 CET  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/2  yes enp0s14  activating  
/org/freedesktop/NetworkManager/ActiveConnection/4  --
   belkin7 adbd0980-d486-4399-85ce-073f67e96c69  wifi  
1520875892  ma 12 mrt 2018 18:31:32 CET  yes  0 no  
  /org/freedesktop/NetworkManager/Settings/1  yes wlp0s9   activated   
/org/freedesktop/NetworkManager/ActiveConnection/2  --
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID
  CON-PATH
   wlp0s9   wifi  connected  
/org/freedesktop/NetworkManager/Devices/3  belkin7 
adbd0980-d486-4399-85ce-073f67e96c69  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s14  ethernet  connecting (getting IP configuration)  
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
23c53d9f-11b8-3a57-9683-119513fb5647  
/org/freedesktop/NetworkManager/ActiveConnection/4
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755248/+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 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()

[Olivier Tilloy]

>From possible duplicate bug #1755233, the user reported that « Browser
did not gracefully exit », which suggests the crash happens at
application shutdown.

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

Title:
  chromium-browser crashed in OnConnectionDisconnectedFilter()

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
chromium-browser.  This problem was most recently seen with package version 
62.0.3202.62-0ubuntu0.17.10.1380, the problem page at 
https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 
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/chromium-browser/+bug/1729963/+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 1755233] Re: chromium-browser crashed with SIGABRT

[Olivier Tilloy]

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

Probably a duplicate of bug #1729963, although the stack trace is
incomplete so not 100% sure. Tentatively marking it as such.

** This bug has been marked a duplicate of bug 1729963
   chromium-browser crashed in OnConnectionDisconnectedFilter()

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Browser did not gracefully exit.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.146-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Mon Mar 12 11:43:51 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (138 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.44
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (21 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1755233/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Olivier Tilloy]

Thanks for the feedback Stephen. This thread has become very long and
it's hard to extract the relevant information, so just to make sure that
I fully understand the issue:

 - can you confirm that chrom{e,ium} takes a long time to open (in the
original description it was 2 minutes, is this the same for you)?

 - if so, do you eventually see a popup prompting for your password to
unlock the keyring?

 - after closing it and opening again, I take it it's not blocked on the
keyring, assuming you previously unlocked it?

 - can you launch chromium from a terminal with the following command,
and share the output:

  chromium-browser --enable-logging=stderr

Thanks in advance!

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1755248] [NEW] Network card does not connect anymore

[lotuspsychje]

Public bug reported:

Ubuntu 18.04 daily @ 12/3/2018

Network card does not connect anymore an several machines and ubuntu versions 
18.04 daily & 16.04
with different chipsets, this bug has been following around across many ubuntu 
versions, please fix

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 12 18:33:10 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-12-16 (86 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
IpRoute:
 default via 192.168.1.1 dev wlp0s9 proto dhcp metric 600
 169.254.0.0/16 dev wlp0s9 scope link metric 1000
 192.168.1.0/24 dev wlp0s9 proto kernel scope link src 192.168.1.4 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE   
ACTIVE-PATH SLAVE
 Wired connection 1  23c53d9f-11b8-3a57-9683-119513fb5647  ethernet  1515749288 
 vr 12 jan 2018 10:28:08 CET  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/2  yes enp0s14  activating  
/org/freedesktop/NetworkManager/ActiveConnection/4  --
 belkin7 adbd0980-d486-4399-85ce-073f67e96c69  wifi  1520875892 
 ma 12 mrt 2018 18:31:32 CET  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp0s9   activated   
/org/freedesktop/NetworkManager/ActiveConnection/2  --
nmcli-dev:
 DEVICE   TYPE  STATE  DBUS-PATH
  CONNECTION  CON-UUID  
CON-PATH
 wlp0s9   wifi  connected  
/org/freedesktop/NetworkManager/Devices/3  belkin7 
adbd0980-d486-4399-85ce-073f67e96c69  
/org/freedesktop/NetworkManager/ActiveConnection/2
 enp0s14  ethernet  connecting (getting IP configuration)  
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
23c53d9f-11b8-3a57-9683-119513fb5647  
/org/freedesktop/NetworkManager/ActiveConnection/4
 lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

** Summary changed:

- Realtek network card does not connect anymore
+ Network card does not connect anymore

** Description changed:

  Ubuntu 18.04 daily @ 12/3/2018
  
  Network card does not connect anymore an several machines and ubuntu versions 
18.04 daily & 16.04
- with different realtek chipsets, this bug has been following around across 
many ubuntu versions, please fix
+ with different chipsets, this bug has been following around across many 
ubuntu versions, please fix
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 18:33:10 2018
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2017-12-16 (86 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  IpRoute:
-  default via 192.168.1.1 dev wlp0s9 proto dhcp metric 600 
-  169.254.0.0/16 dev wlp0s9 scope link metric 1000 
-  192.168.1.0/24 dev wlp0s9 proto kernel scope link src 192.168.1.4 metric 600
+  default via 192.168.1.1 dev wlp0s9 proto dhcp metric 600
+  169.254.0.0/16 dev wlp0s9 scope link metric 1000
+  192.168.1.0/24 dev wlp0s9 proto kernel scope link src 192.168.1.4 metric 600
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  RfKill:
-  0: phy0: Wireless LAN
-   Soft 

[Desktop-packages] [Bug 1754973] Re: Clicking on the website button closes Ubuntu Software

[Jeremy Bicha]

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

I can reproduce this bug in the Ubuntu on Wayland session but not the
Ubuntu session. Therefore, I'm marking this a duplicate of LP: #1754169.

** This bug has been marked a duplicate of bug 1754169
   [Bionic] [wayland] many gnome applications exit or crash when a file is 
opened from within

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

Title:
  Clicking on the website button closes Ubuntu Software

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged

Bug description:
  Clicking on the website button on a particular app closes Ubuntu
  Software. I tried it on a few app (qBittorrent, Deluge, gThumb) all
  resulted in Ubuntu Software closes and the designated website not
  opening in my default browser (Firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.92-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 11 09:49:14 2018
  InstallationDate: Installed on 2018-02-25 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.27.92-0ubuntu2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1754973/+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 1754904] Re: Startup Applications desktop file untranslated on Ubuntu 18.04

[Gunnar Hjalmarsson]

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  Startup Applications desktop file untranslated on Ubuntu 18.04

Status in Ubuntu Translations:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  The desktop entry for Startup Applications (gnome-session-properties)
  is untranslated since some recent update on my non-English (Czech)
  Ubuntu 18.04 system. It is fully translated upstream and used to be
  translated in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754904/+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 1755233] Re: chromium-browser crashed with SIGABRT

[Apport retracing service]

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Browser did not gracefully exit.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.146-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Mon Mar 12 11:43:51 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (138 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.44
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
   ()
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (21 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1755233/+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 1754169] Re: [Bionic] [wayland] many gnome applications exit or crash when a file is opened from within

[Jeremy Bicha]

A proposed fix for this issue has been identified:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/42

I'm closing all the other bug tasks since we don't need them for every
affected app.

** No longer affects: deja-dup (Ubuntu)

** No longer affects: deja-dup (Ubuntu Bionic)

** No longer affects: gedit (Ubuntu)

** No longer affects: gedit (Ubuntu Bionic)

** No longer affects: gnome-control-center (Ubuntu)

** No longer affects: gnome-control-center (Ubuntu Bionic)

** No longer affects: gnome-disk-utility (Ubuntu)

** No longer affects: gnome-disk-utility (Ubuntu Bionic)

** No longer affects: gnome-logs (Ubuntu)

** No longer affects: gnome-logs (Ubuntu Bionic)

** No longer affects: gnome-photos (Ubuntu)

** No longer affects: gnome-photos (Ubuntu Bionic)

** No longer affects: polari (Ubuntu)

** No longer affects: polari (Ubuntu Bionic)

** Package changed: nautilus (Ubuntu Bionic) => mutter (Ubuntu Bionic)

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

** Changed in: mutter (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

Title:
  [Bionic] [wayland] many gnome applications exit or crash when a file
  is opened from within

Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  Workaround
  ---
  From the login screen, click your name, then click the gear button and select 
Ubuntu. Log in.

  Steps to reproduce for Nautilus
  ---
  0) From the login screen, click your name, then click the gear button and 
select Ubuntu on Wayland. Log in.
  1) Open nautilus (currently 3.26.2 in bionic)
  2) Browse to a location with a textfile or an archive (eg. 
/home/user/.thunderbird )
  3) Right click a textfile or an archive (eg. profiles.ini)
  4) Choose gedit or File Roller from the list, click ok.
  5) Nautilus crashes, gedit or File Roller don't come up

  Another observation: This problem is not limited to Nautilus. Thus
  going back to Nautilus 3.26.0 will not help.

  Steps to reproduce for other apps (via opening yelp files)
  --
  1) Open nautilus
  2) click on the nautilus entry in the top bar (right of "Activities").
  3) Select "Help"
  4) nautilus exits, yelp doesn't come up
  5) open polari
  6) click on the "Polari" entry in the top bar (right of "Acitivies").
  7) Select "Help"
  8) See polari crash
  9) Open gnome-control-center
  10) See that gnome-control-center will exit/crash, see that yelp doesn't come 
up

  Affected applications
  -
  Not all applications crash. Most applications don't offer the possibility to 
open yelp from the top bar. So those are not mentioned in the list below:

  * Deja Dup, Gnome control center, Nautilus, Polari, Gnome-Disks,
  Gnome-Photos, gEdit and gnome-logs will crash

  * Gnome Terminal, Rhythmbox, Gnome-Sudoku, Cheese, Gthumb, Gnome-
  Mahjongg, Gnome-Mines, Simple-Scan, Gnome-Calculator and Gnome-Clocks,
  File Roller, gnome-screenshot, baobab, gnome-system-monitor and Totem
  will not.

  Other Info
  --
  Opening a file from Nautilus with LibreOffice doesn't crash Nautilus.

  Conclusion
  --
  Is that a Mutter or Gnome-shell regression? Is it going to be fixed upstream? 
It seems that some (XDG?-) handover between some gnome apps doesn't work as 
expected and both apps have to exit.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Mar  7 22:13:00 2018
  InstallationDate: Installed on 2018-02-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1754169/+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 1754773] Re: network-manager-openvpn-gnome - VPN definition is damaged when saved

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1754172
   NetworkManager breaks OpenVPN configuration on connection

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

Title:
  network-manager-openvpn-gnome - VPN definition is damaged when saved

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

Bug description:
  OpenVPN connection settings are upon saving.

  Steps to reproduce:

  1. create OpenVPN connection using nmcli: nmcli connection import type 
openvpn test.ovpn
  2. go to VPN settings
  3. edit 'test' OpenVPN connection
  4. fill random User private key password
  5. save / apply changes
  6. edit 'test' OpenVPN connection again

  You'll see:
  - User certificate is lost (filled with CA certificate)
  - User private key is lost (empty)

  
  Package & OS info

  dpkg -l|grep openvpn-gnome
  ii  network-manager-openvpn-gnome  1.8.0-2
   amd64network management framework (OpenVPN plugin GNOME GUI)

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn-gnome 1.8.0-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 23:12:03 2018
  InstallationDate: Installed on 2018-03-07 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1754773/+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 1754491] Re: "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.27.91-0ubuntu4

---
gnome-session (3.27.91-0ubuntu4) bionic; urgency=medium

  * debian/rules: Simplify code for adding X-Ubuntu-Gettext-Domain
(LP: #1754904, LP: #1754491).

 -- Gunnar Hjalmarsson   Mon, 12 Mar 2018 15:51:00
+0100

** Changed in: gnome-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  It looks like that the "Ubuntu on Wayland" translation disappeared
  after some recent Ubuntu 18.04 update, although the string is fully
  translated on Launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1754491/+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 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04

[AsciiWolf]

It's a virtual machine under KVM on my desktop PC.

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

Title:
  GNOME Power Statistics shows nothing on Ubuntu 18.04

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot
  enable timerstats" error. See the attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+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 1754172] Re: NetworkManager breaks OpenVPN configuration on connection

[Jeremy Bicha]

Thanks for the follow up. I'm marking this as fixed now.

Please feel free to report any other bug you find.

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NetworkManager breaks OpenVPN configuration on connection

Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  A previously working OpenVPN configuration stopped connecting, with
  nm-openvpn complaining about wrong options:

  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8258] 
audit: op="connection-activate" uuid="e3553582-0f39-404f-bd71-4dc6b92992de" 
name="Router.Michal" pid=6735 uid=1000 result="success"
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8337] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 Started the VPN service, PID 26187
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8421] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 Saw the service appear; activating connection
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8611] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN plugin: state changed: starting (3)
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8615] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN connection: (ConnectInteractive) reply received
  mar 07 22:35:45 michal-laptop nm-openvpn[26190]: Options error: If you use 
one of --cert or --key, you must use them both
  mar 07 22:35:45 michal-laptop nm-openvpn[26190]: Use --help for more 
information.
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8648] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN plugin: failed: connect-failed (1)
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8651] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN plugin: failed: connect-failed (1)
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8658] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN plugin: state changed: stopping (5)
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8660] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN plugin: state changed: stopped (6)
  mar 07 22:35:45 michal-laptop NetworkManager[3172]:   [1520458545.8680] 
vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]:
 VPN service disappeared

  
  The config, however, includes correct ca/cert/key stanzas:

  ca=ca.crt
  cert=michal.crt
  key=michal.key

  The attached screenshot shows a related breakage in the GUI, after
  making the correct certificate/key file selections, and saving the
  config, the config file gets broken indeed:

  ca=ca.crt
  cert=ca.crt
  # no key entry at all

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn 1.8.0-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 22:32:57 2018
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (28 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1754172/+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 1754904] Re: Startup Applications desktop file untranslated on Ubuntu 18.04

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.27.91-0ubuntu4

---
gnome-session (3.27.91-0ubuntu4) bionic; urgency=medium

  * debian/rules: Simplify code for adding X-Ubuntu-Gettext-Domain
(LP: #1754904, LP: #1754491).

 -- Gunnar Hjalmarsson   Mon, 12 Mar 2018 15:51:00
+0100

** Changed in: gnome-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Startup Applications desktop file untranslated on Ubuntu 18.04

Status in Ubuntu Translations:
  New
Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  The desktop entry for Startup Applications (gnome-session-properties)
  is untranslated since some recent update on my non-English (Czech)
  Ubuntu 18.04 system. It is fully translated upstream and used to be
  translated in Ubuntu 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754904/+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 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)

[John Doe]

** Information type changed from Private Security to Public

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

Title:
  Clone Mac Address Function On Default Wifi Setting Does Not Work
  (Ubuntu 17.10)

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am Just Using Ubuntu 17.10.

  My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri
  Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

  Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is
  also (MAC Address Randomization issue). I can fixed it and can use
  default mac address spoofing function from wifi setting -> Network
  Profile Setting (*) -> Identity -> Cloned Address -> And Add mac
  address to spoof for particular network.

  This Default mac address spoof function is very useful for me.

  Clearly, I doesn't mean (MAC Address Randomization issue)
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513

  Now I have a trouble with this feature (default mac spoffing). I can
  connect Wifi-s with great signal easily without using cloned address
  function.

  But when I added spoof address to setting, the wifi-s cannot be
  connected. I tried two wifi-s from near me which can connect on fedora
  26. One is open type network and the other is WPA Enterprise network.

  If this function doesn't work for anyone, this must be a bug.
  If it is a bug, hope it will fix it next release.

  Please, Don't Hesitate to ask more information. I really want to help
  to fix bug.

  #info
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  network-manager:
    Installed: 1.8.4-1ubuntu3
    Candidate: 1.8.4-1ubuntu3
    Version table:
   *** 1.8.4-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1755237] [NEW] Missing graphic driver

[Peter Wigen Bjarnø]

Public bug reported:

intel i7 8700K

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.15
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
CurrentDesktop: Unity
Date: Mon Mar 12 17:32:55 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b43]
InstallationDate: Installed on 2018-03-12 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Micro-Star International Co., Ltd. MS-7B43
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=7e4708d7-5020-4264-b21c-175e2d590abb ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00
dmi.board.asset.tag: Default string
dmi.board.name: Z370I GAMING PRO CARBON AC (MS-7B43)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd10/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B43:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370IGAMINGPROCARBONAC(MS-7B43):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7B43
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Mon Mar 12 18:18:26 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


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

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

Title:
  Missing graphic driver

Status in xorg package in Ubuntu:
  New

Bug description:
  intel i7 8700K

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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
  CurrentDesktop: Unity
  Date: Mon Mar 12 17:32:55 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7b43]
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Micro-Star International Co., Ltd. MS-7B43
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=7e4708d7-5020-4264-b21c-175e2d590abb ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370I GAMING PRO CARBON AC (MS-7B43)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  

[Desktop-packages] [Bug 1755239] [NEW] Wacom Cintiq not working in Ubuntu 17.10

[eezacque]

Public bug reported:

The screen of the tablet works, the stylus cannot be found.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-input-wacom 1:0.34.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 12 17:36:24 2018
DistUpgraded: 2018-03-08 12:19:15,834 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
InstallationDate: Installed on 2014-10-24 (1234 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash 
vt.handoff=7
SourcePackage: xf86-input-wacom
UpgradeStatus: Upgraded to artful on 2018-03-08 (4 days ago)
dmi.bios.date: 06/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO(Wi-Fi ac)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.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: Wed Mar  7 19:06:07 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Wacom Cintiq not working in Ubuntu 17.10

Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  The screen of the tablet works, the stylus cannot be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-input-wacom 1:0.34.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 17:36:24 2018
  DistUpgraded: 2018-03-08 12:19:15,834 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  InstallationDate: Installed on 2014-10-24 (1234 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash 
vt.handoff=7
  SourcePackage: xf86-input-wacom
  UpgradeStatus: Upgraded to artful on 2018-03-08 (4 days ago)
  dmi.bios.date: 06/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO(Wi-Fi ac)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Desktop-packages] [Bug 476684] Re: gnome-appearance-properties crashed with SIGSEGV in g_main_context_dispatch()

[Timmn]

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => 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/476684

Title:
  gnome-appearance-properties crashed with SIGSEGV in
  g_main_context_dispatch()

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

Bug description:
  Binary package hint: gnome-control-center

  I don't speak English

  ProblemType: Crash
  Architecture: i386
  Date: Fri Nov  6 20:03:48 2009
  Disassembly: 0x1bc92c0:   Cannot access memory at address 0x1bc92c0
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-appearance-properties
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:2.28.1-0ubuntu1
  ProcCmdline: gnome-appearance-properties --show-page=background
  ProcEnviron:
   LANGUAGE=ru_RU.UTF-8
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SegvAnalysis:
   Segfault happened at: 0x1bc92c0: Cannot access memory at address 
0x1bc92c0
   PC (0x01bc92c0) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   ?? () from /usr/lib/libgdk-x11-2.0.so.0
   g_main_context_dispatch () from /lib/libglib-2.0.so.0
   ?? () from /lib/libglib-2.0.so.0
  Title: gnome-appearance-properties crashed with SIGSEGV in 
g_main_context_dispatch()
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev 
sambashare scanner tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/476684/+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 1755232] [NEW] Xorg crashes when tapping Unity system tray icons

[krzychoocpp]

Public bug reported:

This bug requires some prerequisites to reproduce:

0. Make sure you've got multitouch-enable display
1. Start Unity+xorg session
2. Verify that four-finger tap gesture works (shows unity app search tool)
3. Wait some time for this gesture to stop working - this is another bug, not 
necessarily xorg one,  already known and thought to be connected with Google 
Chrome running.
4. Once it stops working, quickly tap all icons in the Unity system tray like 
you would be pretending to play a piano (tapping them individually or slowly 
does not cause any problems).
5. Xorg crashes immediately.

This scenario is 100% reproducible on my setup.

I recompiled xorg with debug info enabled and got this nice trace:


[ 22705.385] (EE) 
[ 22705.385] (EE) Backtrace: 
[ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f]
 
[ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) 
[0x7f382f64414f]   
[ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f382f2880bb] 
[ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) 
[0x7f382f289f5d]  
[ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) 
[0x7f382f2d22bd]  
[ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) 
[0x7f382f2d9f7a]
[ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) 
[0x7f382f2de0fe]   
[ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) 
[0x7f382f2e044e]   
[ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32]
[ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) 
[0x562a3698428f]   
[ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) 
[0x562a3698ea8b]   
[ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) [0x562a369bc371] 
 
[ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689]   
 
[ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) 
[0x562a3696e488] 
[ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9]
[ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3]  
 
[ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22]   
 
[ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7f382f2721c1]  
[ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a] 
 
[ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] 


Looks like FreeGrab tries to free pGrab for the second time (some
multithreading issue?)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
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
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Mar 12 17:03:34 2018
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:2245]
InstallationDate: Installed on 2017-09-01 (192 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20HES2130Q
ProcEnviron:
 LANGUAGE=pl_PL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y 
acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 
i915.enable_guc_submission=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to artful on 2018-02-11 (29 days ago)
dmi.bios.date: 05/23/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1QET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HES2130Q
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1QET55W(1.30):bd05/23/2017:svnLENOVO:pn20HES2130Q:pvrThinkPadT470:rvnLENOVO:rn20HES2130Q:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470
dmi.product.name: 20HES2130Q
dmi.product.version: ThinkPad T470
dmi.sys.vendor: LENOVO
version.compiz: compiz 

[Desktop-packages] [Bug 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04

[Sebastien Bacher]

Thank you for your bug report. What sort of computer do you use? On a laptop it 
should least batteries info, on a desktop indeed you get only the CPU 
information and that seems buggy.
There is a Debian bug report describing similar problems on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689298
It might have to do with upower/kernel options, needs investigation

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

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

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

Title:
  GNOME Power Statistics shows nothing on Ubuntu 18.04

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot
  enable timerstats" error. See the attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+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 1755233] [NEW] chromium-browser crashed with SIGABRT

[Stephen Michael Kellat]

Public bug reported:

Browser did not gracefully exit.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 65.0.3325.146-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
 modes: 1366x768 1366x768
Date: Mon Mar 12 11:43:51 2018
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2017-10-24 (138 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
Load-Avg-1min: 3.44
Load-Processes-Running-Percent:   0.2%
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5567
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 ()
 ()
 ()
 dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
 ()
Title: chromium-browser crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-02-19 (21 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
dmi.bios.date: 01/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  chromium-browser crashed with SIGABRT

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Browser did not gracefully exit.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.146-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5CUFAAAaAQSVIhN4CkLlkVhVjygeUFQBAQEBAQEBAQEBAQEBAQEB0B1W9FAAFjAwIDUAWMIQAAAa2RdW9FAAFjAwIDUAWMIQAAAa/gBIOTdIMYAxNTZXSFUKQTGUABkBCiAgAI0=
   modes: 1366x768 1366x768
  Date: Mon Mar 12 11:43:51 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-10-24 (138 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Load-Avg-1min: 3.44
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  

[Desktop-packages] [Bug 1755166] Re: gnome-shell crashed with SIGSEGV

[Jean-Baptiste Lallement]

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not sure if a duplicate still, but this crashes the window manager
  whenever I turn my monitor back on.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 08:49:42 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-05-28 (288 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f33a2b01a4b:mov0x8(%rax),%rax
   PC (0x7f33a2b01a4b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

[Jean-Baptiste Lallement]

** 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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1752645

Title:
  gnome-software crashed with SIGSEGV in g_type_check_instance()

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.27.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Feb 28 23:18:23 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-06-18 (255 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170618)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.27.90-1ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.27.90-1ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fe66804f17d : mov
(%rdi),%rax
   PC (0x7fe66804f17d) ok
   source "(%rdi)" (0x0001) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_handlers_disconnect_matched () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in g_type_check_instance()
  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-software/+bug/1752645/+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 1648846] Re: Chromium ignores no_proxy environment variable

[JanCeuleers]

I cannot reproduce the issue at present.
But it's strange that I encountered a problem in 2016 which was fixed upstream 
in 2009.
Anyway, let's close this for now.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Chromium ignores no_proxy environment variable

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I need the proxy to be bypassed for a number of sites. These sites are
  listed in the no_proxy environment variable. However, this is ignored
  by Chromium. There does not appear to be any way in Chromium (nor in
  the system proxy settings) to specify sites for which the proxy should
  be bypassed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 53.0.2785.143-0ubuntu0.16.04.1.1257
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  DRM.card0-DP-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0-LVDS-1:
   edid-base64: 
AP///wAGr54TAAETAQOAJhV4CsSVnldTkiYPUFQBAQEBAQEBAQEBAQEBAQEBHCpAbmGEDDAwIDYAftYQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTczUlcwMSBWMyAKACQ=
   dpms: On
   modes: 1600x900
   enabled: enabled
   status: connected
  DRM.card0-VGA-1:
   edid-base64: 
   dpms: Off
   modes: 
   enabled: disabled
   status: disconnected
  Date: Fri Dec  9 17:23:04 2016
  Desktop-Session:
   'gnome-flashback-compiz'
   '/etc/xdg/xdg-gnome-flashback-compiz:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/gnome-flashback-compiz:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-12-07 (732 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Load-Avg-1min: 1.11
  Load-Processes-Running-Percent:   0.1%
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=9a82200b-b3aa-44b6-b217-8db2a403850f ro ipv6.disable=1 quiet splash 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (229 days ago)
  dmi.bios.date: 05/21/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.19
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1803
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.19:bd05/21/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr06902120471620100:rvnHewlett-Packard:rn1803:rvr10.59:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 06902120471620100
  dmi.sys.vendor: Hewlett-Packard
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2016-04-24T14:29:37.993623

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1648846/+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 1754903] Re: "Close" string not marked for translation

[Jeremy Bicha]

Test Case
-
Open GNOME Software.
Search for Chromium.
Install it (this is the Chromium snap).
Click the Chromium details page.
There is a third button named Permissions next to the Launch button and the 
Remove button.
Click Permissions. There is a Close button in the dialog's header bar.

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

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Stephen M]

- I'm seeing slow downs.
 - I'm not using automatic login.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1430531] Re: FILEOPEN: Opening file from Samba share produce Document in Use dialog (~/.gvfs or mount.cifs)

[Olivier Tilloy]

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

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

Title:
   FILEOPEN: Opening file from Samba share produce Document in Use
  dialog (~/.gvfs or mount.cifs)

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  New

Bug description:
  This bug is somehow related to other -  LibO 72337 [1].

  I'm on Ubuntu 12.04.5 with all updates and LibreOffice 3.5.7.2
  Build ID: 350m1(Build:2)
  (libreoffice 1:3.5.7-0ubuntu7) from official repository.
  The problem exists in more modern versions of LibreOffice from PPA 
(3.6.6-0ubuntu1~precise1~ppa1 , 4.0.4~rc2-0ubuntu1~precise1 , 
4.1.6-0ubuntu1~precise1~ppa1 , 4.2.8~rc2-0ubuntu1~precise1 , 
4.3.6~rc2-0ubuntu1~precise1 , 4.4.1~rc2-0ubuntu1~precise1).

  Steps to reproduce:
  1. I have shared Public folder (read write, allow guest) from other Ubuntu 
12.04.5 laptop using nautilus-share (0.7.3-1ubuntu2), placed test.odt file in 
it.
  2a. I navigate Nautilus on other laptop to smb://laptop/public, clicked 'Open 
in Terminal here' (or launch terminal and "cd ~/.gvfs/public\ on\ laptop").  
Run "libreoffice test.odt" in terminal.
  2b. I navigate Nautilus on other laptop to smb://laptop/public, clicked on 
'test.odt' file.
  2c. I mount share from terminal with
  sudo mount.cifs //192.168.3.11/public /mnt/smb/ -o uid=`id -u`,gid=`id 
-g`,guest,sec=none,noperm
  then
  libreoffice /mnt/smb/test.odt

  3. Got "Document in Use" window with text:

     Document file 'test.odt' is locked for editing by:

     Unknown User

     Open document read-only or open a copy of the document for editing.

     Open Read-Only Open Copy Cancel

  4a. If I click 'Open Read-Only' the document is opened in read-only.
  4b. If I click 'Open Copy' the "Untitled 1" document is opened.
  4c. Cancel closes this window.

  Expected results:
     The "test.odt" files is opened in read-write mode, user can edit it.

  Actual results:
     User can't edit original document (see pp. 3-4 above).

  This functionality is essential. Please fix this bug.

  Notes:
    If I try to open document with the command 'libreoffice 
smb://laptop/public/test.odt' I run into other bug (bug 1214352).
    If I use Windows as SMB/CIFS server I can open and edit document from share.
Problem does not exist with SFTP(SSH)- or NFS- file-servers.
    My test results are located in Google Docs/Drive Table (  
http://goo.gl/jY9Ubj  ).

    Global Samba config (/etc/samba/smb.conf) is default.
    My useshare config is:
  cat /var/lib/samba/usershares/public
  #VERSION 2
  path=/home/norbert/Public
  comment=
  usershare_acl=S-1-1-0:F
  guest_ok=y
  sharename=Public

  1. https://bugs.documentfoundation.org/show_bug.cgi?id=72337 .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice 1:3.5.7-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-46.77~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Tue Mar 10 23:52:04 2015
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1430531/+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 1753383] Re: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1028: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.

[Sebastien Bacher]

** Information type changed from Private to Public

** Package changed: xorg-server (Ubuntu) => libinput (Ubuntu)

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

Title:
  Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1028:
  tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.

Status in libinput package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AssertionMessage: Xorg: ../src/evdev-mt-touchpad-tap.c:1028: 
tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 15:19:19 2018
  DistUpgraded: 2018-02-23 18:43:25,406 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [17aa:3902]
  InstallationDate: Installed on 2018-02-21 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:0671 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80M1
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=7c316ffa-779d-4eda-a8d6-f7a20492e6bb ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f844e3247d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7f844b16af75 "tp->tap.nfingers_down 
>= 1", file=file@entry=0x7f844b16afb8 "../src/evdev-mt-touchpad-tap.c", 
line=line@entry=1028, function=function@entry=0x7f844b16b2b0 
"tp_tap_handle_state") at assert.c:92
   __GI___assert_fail (assertion=0x7f844b16af75 "tp->tap.nfingers_down >= 1", 
file=0x7f844b16afb8 "../src/evdev-mt-touchpad-tap.c", line=1028, 
function=0x7f844b16b2b0 "tp_tap_handle_state") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10
  Title: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1028: 
tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed.
  UpgradeStatus: Upgraded to bionic on 2018-02-23 (9 days ago)
  UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev 
sambashare sambashare sudo sudo
  dmi.bios.date: 08/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C7CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 300-11IBR
  dmi.modalias: 
dmi:bvnLENOVO:bvrC7CN31WW:bd08/05/2016:svnLENOVO:pn80M1:pvrLenovoYoga300-11IBR:rvnLENOVO:rnMini:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoYoga300-11IBR:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M1
  dmi.product.version: Lenovo Yoga 300-11IBR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1753383/+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 1754903] Re: "Close" string not marked for translation

[Sebastien Bacher]

Could you describe what actions you take to trigger that dialog and
maybe add a screenshot?

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

Title:
  "Close" string not marked for translation

Status in Ubuntu Translations:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  It looks like that string for the "Close" button from the Permissions
  window of GNOME Software is not available for translation. Would it be
  possible to fix this? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1754903/+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 1307041] Re: browser window resizes to max height each time i open it

[Olivier Tilloy]

Yeah, sorry for the lack of feedback. Let's assume this was fixed along
the way and close this issue.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  browser window resizes to max height each time i open it

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I'm on Ubuntu, using Chrome browser. I like running the browser in a
  non-maximized window, where the height is not max height of the
  window, and the width is not either. However, whenever I close the
  browser and re-open it, it will adjust its' height slightly each time
  I open it, until it has reached max window height eventually. End
  result is that I have to adjust the window height every time I open
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Apr 12 19:23:09 2014
  InstallationDate: Installed on 2014-01-08 (94 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1307041/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Burt P.]

Regarding #43, #44, #51, here is what I did:
* Reset the grub config file
* Removed all nvidia* packages
* Reverted everything to the standard bionic as described here: 
https://askubuntu.com/a/229663
* Removed all the old package information using: dpkg --purge `dpkg 
--get-selections | grep deinstall | cut -f1`
* Installed nvidia-driver-390: apt-get install nvidia-driver-390
* Restarted

Everything seems to work.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

[shankao]

$ apt-cache policy libgl1 libegl1
libgl1:
  Installed: 1.0.0-2ubuntu2
  Candidate: 1.0.0-2ubuntu2
  Version table:
 *** 1.0.0-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libegl1:
  Installed: 1.0.0-2ubuntu2
  Candidate: 1.0.0-2ubuntu2
  Version table:
 *** 1.0.0-2ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  LLVMpipe renderer used instead of Intel on Xorg sessions

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1755181] Re: chromium-browser crashed with signal 5

[Olivier Tilloy]

Unfortunately the stacktrace is not usable.

@cubells: can you explain what you were doing when the crash occurred?
Can you reliably trigger it, by any chance?

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  chromium-browser crashed with signal 5

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy chromium-browser
  chromium-browser:
Instal·lat: 65.0.3325.146-0ubuntu1
Candidat:   65.0.3325.146-0ubuntu1
Taula de versió:
   *** 65.0.3325.146-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.146-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLTINRTZQMCMaAQOAPCJ4KlKVpVZUnSUOUFS7jACzAIHAgQCBgJUAqcABAQEBAjqAGHE4LUBYLEUAVlAhAAAe/QAySB5REQAKICAgICAg/ABDMjdGMzkwCiAgICAg/wBIVFFIODAzNjYyCiAgAeQCAxrxRpAEHxMSAyMJBweDAQAAZgMMABAAgAEdALxS0B4guChVQFZQIQAAHowK0JAgQDEgDEBVAFZQIQAAGIwK0Iog4C0QED6WAFZQIQAAGAAAYQ==
   modes: 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 800x600 
720x576 720x480 720x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANryAXAAIVAQSQJhV4Au2Vo1RMnCYPUFQBAQEBAQEBAQEBAQEBAQEB4TaArnA4JkA0IzYAftcQAAAaHSSAoHA4H0AwIDUAftcQAAAa/gBIQzlHS4AxNzNIR0UKQTGeAAIBCiAgAPM=
   modes: 1920x1080 1920x1080
  Date: Mon Mar 12 14:58:32 2018
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/etc/xdg'
   
'/home/cubells/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-08-20 (1300 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Load-Avg-1min: 2.69
  Load-Processes-Running-Percent:   0.1%
  MachineType: Notebook P17SM-A
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=zygote\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=28.0.0.126
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=9b47749a-0a02-480a-b6d4-c0cd3de49bf8 ro quiet splash vt.handoff=1
  Signal: 5
  SourcePackage: chromium-browser
  StacktraceTop:
   ()
   ()
   ()
   ()
   ChromeMain ()
  Title: chromium-browser crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-01-02 (68 days ago)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev pulse pulse-access 
sambashare sudo video www-data
  dmi.bios.date: 03/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P17SM-A
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/27/2014:svnNotebook:pnP17SM-A:pvrNotApplicable:rvnNotebook:rnP17SM-A:rvrNotApplicable:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Not Applicable
  dmi.product.name: P17SM-A
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Olivier Tilloy]

> This bug is not resolved. Seeing it under 16.04LTS without
> dbus-user-session or flatpak installed.

I can reliably reproduce the issue of the keyring not being
automatically unlocked at startup in an up-to-date 16.04 VM without
dbus-user-session installed. Not seeing any application slowdown though,
chromium doesn't block at startup, but it does pop up a dialog prompting
to unlock the keyring.

That VM was configured to automatically log in the only user account
though, and I had removed the user's password. After setting back a
password for the user and disabling the automatic login, I verified that
the keyring was correctly unlocked after logging in.

To everyone affected:
 - can you comment on whether you're seeing application slowdown/blocking when 
the login keyring is not unlocked?
 - can you share whether automatic login is enabled, and whether you have unset 
your user's password (this is not recommended)

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1755174] Re: rhythmbox ignores proxy settings

[Hadmut Danisch]

I tried to subscribe an audio podcast under a regular URL.

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

Title:
  rhythmbox ignores proxy settings

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I just tested the upcoming 18.04 release from a network behind a web
  proxy without direct internet access. Although I have set the proxy in
  the desktop settings and other programs (e.g. this bug report) honor
  and use the proxy, rhythmbox complains that there is no network and
  seems to completely ignore proxy settings.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 13:22:46 2018
  InstallationDate: Installed on 2018-03-05 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1755174/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Jeremy Bicha]

> I do not feel comfortable removing dbus-user-session as a workaround

Nothing in Ubuntu 16.04 LTS uses dbus-user-session. It is completely
safe to remove it there.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1755097] Re: LLVMpipe renderer used instead of Intel on Xorg sessions

[Timo Aaltonen]

run:

apt-cache policy libgl1 libegl1

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

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

Title:
  LLVMpipe renderer used instead of Intel on Xorg sessions

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  3D acceleration is not working at the moment in Xorg because the
  LLVMpipe renderer is used. Instead, the correct Intel driver is used
  when trying Wayland sessions.

  shankao@schwifty:~$ glxinfo | grep -i opengl
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc4
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.0 Mesa 18.0.0-rc4
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc4
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:
  shankao@schwifty:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libegl-mesa0 18.0.0~rc4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 12 15:06:16 2018
  DistUpgraded: 2018-01-09 22:07:50,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:118c]
  InstallationDate: Installed on 2018-01-09 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Acer Swift SF314-52
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e60d0a36-2013-48c7-bf91-fd01764bae3b ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: Upgraded to bionic on 2018-01-09 (61 days ago)
  dmi.bios.date: 07/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Suntory_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/18/2017:svnAcer:pnSwiftSF314-52:pvrV1.06:rvnKBL:rnSuntory_KL:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-52
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Olivier Tilloy]

> Also, on a side-note, does anyone know the exact details of what the
> password-store argument does? For example, if I turn password saving
> in Chromium off and don't use Google/Chrome sync, am I "safe" to log
> into websites without my passwords being stored in plain-text on my
> hard drive (even if temporary)?

Yes you should be safe, chromium won't store passwords if the
corresponding setting is off.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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