[Desktop-packages] [Bug 1749686] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()

2018-02-15 Thread 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1749686

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

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

Bug description:
  Crashed on trying to open users section.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 15:02:50 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so
   gst_device_provider_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_device_monitor_start () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


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

2018-02-15 Thread 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/1749901/+attachment/5056470/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1749901/+attachment/5056479/+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/1749901

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Feb 14 22:03:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-21 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180119)
  JournalErrors:
   -- Logs begin at Sun 2018-01-21 12:26:05 CET, end at Fri 2018-02-16 08:36:44 
CET. --
   feb 16 08:36:15 hostname avahi-daemon[1021]: chroot.c: open() failed: No 
such file or directory
   feb 16 08:36:16 hostname NetworkManager[1052]: 
((src/devices/nm-device.c:1452)): assertion '' failed
   feb 16 08:36:16 hostname gnome-session-binary[1221]: CRITICAL: Unable to 
create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for 
org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1
   feb 16 08:36:44 hostname pulseaudio[2636]: [pulseaudio] bluez5-util.c: 
GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  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/1749901/+subscriptions

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


[Desktop-packages] [Bug 1749424] GsettingsChanges.txt

2018-02-15 Thread Patrik Jelinko
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1749424/+attachment/5056481/+files/GsettingsChanges.txt

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1749424] Re: gnome-shell at 100% after waking up from sleep, screen frozen

2018-02-15 Thread Patrik Jelinko
Hi Daniel,

I think I managed it now. First saved the record to a local file, then
used the "apport-cli -u 1749424 filename" to send it. Pls check

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1749903] [NEW] indicator-keyboard-service (11) gtk_css_node_invalidate → gtk_css_node_invalidate_style_provider → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_vali

2018-02-15 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-keyboard.  This problem was most recently seen with package version 
0.0.0+18.04.20171212-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5f38283500156203b37f960958501df9a3822c1f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: indicator-keyboard (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: artful bionic xenial yakkety zesty

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

Title:
  indicator-keyboard-service (11) gtk_css_node_invalidate →
  gtk_css_node_invalidate_style_provider → g_closure_invoke →
  signal_emit_unlocked_R → g_signal_emit_valist

Status in indicator-keyboard package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-keyboard.  This problem was most recently seen with package version 
0.0.0+18.04.20171212-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5f38283500156203b37f960958501df9a3822c1f 
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/indicator-keyboard/+bug/1749903/+subscriptions

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


[Desktop-packages] [Bug 1749424] JournalErrors.txt

2018-02-15 Thread Patrik Jelinko
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749424/+attachment/5056482/+files/JournalErrors.txt

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1749424] ProcCpuinfoMinimal.txt

2018-02-15 Thread Patrik Jelinko
apport information

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

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1749424] ProcEnviron.txt

2018-02-15 Thread Patrik Jelinko
apport information

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

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1749424] Re: gnome-shell at 100% after waking up from sleep, screen frozen

2018-02-15 Thread Patrik Jelinko
apport information

** Tags added: apport-collected wayland-session

** Description changed:

  About 30% of the times when my computer wakes up from sleep/suspend, the
  screen is frozen. I can remotely login via ssh, and every time what I
  found is the gnome-shell process is using 100% CPU time. If I kill
  gnome-shell, it it takes me back to the login screen, and everything
  seems to be fine, I'm just loosing my session, which is quite annoying.
  Let me know if you need anything else, easy to reproduce the behaviour.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-08-25 (539 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
+ Tags:  wayland-session artful
+ Uname: Linux 4.13.0-32-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-25 (539 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-16 (61 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1748151] Re: [snap] cannot load hsqldb driver

2018-02-15 Thread Olivier Tilloy
** Changed in: libreoffice (Ubuntu)
   Status: New => In Progress

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

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

Title:
  [snap] cannot load hsqldb driver

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Testing the libreoffice snap (both 5.4.4.2 from the stable channel,
  and the upcoming 6.0.0.3) on Ubuntu 18.04, when creating a database
  with libreoffice.base, when I try to edit/add tables, I get the
  following error message box:

  « The connection to the data source "test db" could not be
  established.

The driver class 'org.hsqldb.jdbcDriver' could not be loaded.The
  additional driver class path is
  'file:///usr/share/java/hsqldb1.8.0.jar
  vnd.sun.star.expand:$LO_JAVA_DIR/sdbc_hsqldb.jar'.

[OK] [More] »

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

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


[Desktop-packages] [Bug 1749665] Re: clickpad emulated right click button now emitting left click event

2018-02-15 Thread Tim
I am well after they are only in software that is why I called them
"emulated"!

However, and this is the thing that confused me initially or I might
have twigged on the settings change, is that the button area is still a
dead area on the clickpad, if I dwell my finger for the slightest moment
before initiating a drag/swipe, then when I do drag the cursor does not
move.

Have there been any other reports of that? wondering if its hardware
specific or just a general upstream libinput bug (only one of my laptops
has a clickpad)

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

Title:
  clickpad emulated right click button now emitting left click event

Status in gsettings-desktop-schemas package in Ubuntu:
  Won't Fix

Bug description:
  I upgraded my laptop to bionic last week. It is a Dell Inspiron 5000
  series skylake laptop with Synaptics clickpad.

  It has 2 emulated buttons at the bottom, however since upgrading the
  right click button (area) is now emitting a left click instead of
  right click.

  2 finger right click continues to work as expected.

  xev output (first event is left click area, second right click)
  ButtonPress event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5203741, (67,75), root:(117,189),
  state 0x10, button 1, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5203964, (67,75), root:(117,189),
  state 0x110, button 1, same_screen YES

  ButtonPress event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5207317, (67,75), root:(117,189),
  state 0x10, button 1, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5207493, (67,75), root:(117,189),
  state 0x110, button 1, same_screen YES

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.9.4-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,snap,regex,gnomecompat,mousepoll,wall,move,grid,vpswitch,unitymtgrabhandles,place,resize,animation,expo,workarounds,session,fade,ezoom,scale,unityshell,dbus]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Feb 15 20:31:56 2018
  DistUpgraded: 2018-02-11 12:12:03,492 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.6, 4.12.0-13-generic, x86_64: installed
   virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:06b2]
  InstallationDate: Installed on 2016-05-27 (628 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160509)
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=312a4c17-55ca-49fc-8052-35c29b1cf0ce ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: libinput
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (4 days ago)
  dmi.bios.date: 12/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 052K07
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd12/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn052K07:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  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+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/gsettings-desktop-schemas/+bug/1749665/+subscriptions

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Steve Bainton
Right now boots perfectly every time. I'll keep testing.

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With Xubuntu or Kubuntu the screen turns off a few seconds after
  choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
  minutes to be presented. From that point on everything seems to work
  as normal.

  Booting consistently took only a minute in Kubuntu 14.04.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1749424] Re: gnome-shell at 100% after waking up from sleep, screen frozen

2018-02-15 Thread Daniel van Vugt
Maybe try:

apport-cli --hanging -P `pidof -s gnome-shell`

If that then creates a new bug then please just tell us the new bug ID.

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)

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

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


[Desktop-packages] [Bug 1749424] Re: gnome-shell at 100% after waking up from sleep, screen frozen

2018-02-15 Thread Patrik Jelinko
Daniel,

Can you pls double-check the command I need to run? It gives me the following 
error message:
---
@x:~$ apport-cli -u 1749424 --hanging -P `pidof -s gnome-shell`
Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash 
file]

apport-cli: error: -u/--update-bug option cannot be used together with options 
for a new report
---
apport-cli --version
2.20.7
---

I have tried to play around with the options, but nothing seems to be
working, always the same error message.

Thanks,
Patrik

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

Title:
  gnome-shell at 100% after waking up from sleep, screen frozen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  About 30% of the times when my computer wakes up from sleep/suspend,
  the screen is frozen. I can remotely login via ssh, and every time
  what I found is the gnome-shell process is using 100% CPU time. If I
  kill gnome-shell, it it takes me back to the login screen, and
  everything seems to be fine, I'm just loosing my session, which is
  quite annoying. Let me know if you need anything else, easy to
  reproduce the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 22:06:26 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-25 (537 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-12-16 (59 days ago)

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

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


[Desktop-packages] [Bug 1725955] Re: "Printer added" notification

2018-02-15 Thread brad
This notification pops up each time the network is changed (connected,
disconnected), printer turned off or on, and during a daily chron job.

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

Title:
  "Printer added" notification

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've recently installed Ubuntu 17.10 (Gnome shell). After a while I
  saw an OSD notification with the message "printer added", and thought
  that must be because of the new driverless printers feature in the
  kernel. I have a brother printer in the network, and I tested it and
  it worked. The thing is that the message repeats itself, approximately
  every two minutes, and it's really distracting. I saw a question about
  this on AskUbuntu (https://askubuntu.com/questions/918462/ubuntu-17-04
  -printer-added-notifications-under-gnome), and a solution, but it
  seemed like no one had filed a bug report.

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

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


[Desktop-packages] [Bug 1747929] Re: Do not watch the movie

2018-02-15 Thread dino99
I suppose your issue is now solved with the latest mesa 18 into
'proposed' archive.

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Do not watch the movie

Status in Gstreamer1.0:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I am enclosing screenshot.

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  7 11:37:31 2018
  InstallationDate: Installed on 2017-10-13 (116 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM

2018-02-15 Thread Daniel van Vugt
** Tags added: noclick

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

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

Title:
  Mouse & Keyboard completely unresponsive when starting a VM

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

Bug description:
  Could be virt-manager or gnome-shell related.

  I was passing through 1 USB device that wasn't my main mouse or
  keyboard. Otherwise pretty normal configuration that I've used before.

  After the VM's bios screen, the whole system froze except the clock in
  the desktop menu bar/panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 23:47:02 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-27 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   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/1749895/+subscriptions

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


[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-02-15 Thread Bug Watch Updater
** Changed in: gnome-bluetooth
   Status: Unknown => Fix Released

** Changed in: gnome-bluetooth
   Importance: Unknown => Medium

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  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: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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


[Desktop-packages] [Bug 1749895] [NEW] Mouse & Keyboard completely unresponsive when starting a VM

2018-02-15 Thread Enigma
Public bug reported:

Could be virt-manager or gnome-shell related.

I was passing through 1 USB device that wasn't my main mouse or
keyboard. Otherwise pretty normal configuration that I've used before.

After the VM's bios screen, the whole system froze except the clock in
the desktop menu bar/panel.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
Uname: Linux 4.15.1-041501-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 23:47:02 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-27 (112 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Mouse & Keyboard completely unresponsive when starting a VM

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Could be virt-manager or gnome-shell related.

  I was passing through 1 USB device that wasn't my main mouse or
  keyboard. Otherwise pretty normal configuration that I've used before.

  After the VM's bios screen, the whole system froze except the clock in
  the desktop menu bar/panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 23:47:02 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-27 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   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/1749895/+subscriptions

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


[Desktop-packages] [Bug 886435] Re: Duplicate entry for Bengali (Probhat) keyboard layout

2018-02-15 Thread Launchpad Bug Tracker
[Expired for xkeyboard-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Duplicate entry for Bengali (Probhat) keyboard layout

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  1. System Settings
  2. Keyboard Layout
  3. '+'
  4. Scroll down to Bengali
  5. Note that there are two Bengali entries (these are different and the 
labels should be changed) and two entries labeled 'Bengali (Probhat)'.
  6. Select the first Bengali (Probhat)
  7. Preview
  8. Select the second Bengali (Probhat)
  9. Preview
  10. Compare the two layouts.  They are identical.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Nov  4 20:23:41 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to oneiric on 2011-09-30 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/886435/+subscriptions

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


[Desktop-packages] [Bug 1749690] Re: hp-setup fails to install plugin

2018-02-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  hp-setup fails to install plugin

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  My HP printer requires a binary driver and the only way to install it
  is to run hp-setup from hplip package. It was doing job fine for last
  three years at least, but when I tried to install driver today on a
  fresh 16.04 installation, it couldn't download it.

  $ hp-setup -i 192.168.220.10
  ...
  -
  | PLUG-IN INSTALLATION FOR HPLIP 3.16.3 |
  -

Option  Description   
--  --
d   Download plug-in from HP (recommended)
p   Specify a path to the plug-in (advanced)  
q   Quit hp-plugin (skip installation)

  Enter option (d=download*, p=specify path, q=quit) ? d

  ---
  | DOWNLOAD PLUGIN |
  ---

  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\   
] 0% 
  error: Found No Section in /tmp/tmpjeh9zqmg. Please set the http proxy for 
root and try again.

  error:  file does not match its checksum. File may have been corrupted or 
altered
  error: Failed to install Plugin.
  error: The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins. Please run 
'hp-plugin' as normal user to install plug-ins.Visit http://hplipopensource.com 
for more infomation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hplip 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Feb 15 14:55:08 2018
  InstallationDate: Installed on 2018-01-19 (27 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire V3-771
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=07eba8bf-f5de-4911-9574-0416813d1387 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.28
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.28:bd10/21/2013:svnAcer:pnAspireV3-771:pvrV2.28:rvnAcer:rnVA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-771
  dmi.product.version: V2.28
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1077993] Re: Compose Key action for "c" key misbehaving.

2018-02-15 Thread Launchpad Bug Tracker
[Expired for xkeyboard-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Compose Key action for "c" key misbehaving.

Status in xkeyboard-config package in Ubuntu:
  Expired

Bug description:
  Starting with Ubuntu 12.04 and still in 12.10, Compose+'+c is
  producing "ç" rather than the expected "ć".

  This is throughout the various toolkits. Locale is set to en_CA.UTF-8,
  which should derive the compose settings from en_US.UTF-8. Keyboard
  layout is "us".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xkb-data 2.5-1ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 12 10:55:38 2012
  Dependencies:
   
  DistUpgraded: 2012-11-12 09:35:49,856 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  InstallationDate: Installed on 2010-08-30 (804 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MachineType: Intel Corporation SandyBridge Platform
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic 
root=UUID=1574940e-4e48-4f57-8cec-758832600ffb ro quiet splash vt.handoff=7
  SourcePackage: xkeyboard-config
  UpgradeStatus: Upgraded to quantal on 2012-11-12 (0 days ago)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ASNBCPT1.86C.0058.P00.1012221118
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: LosLunas CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  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.:bvrASNBCPT1.86C.0058.P00.1012221118:bd12/22/2010:svnIntelCorporation:pnSandyBridgePlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLosLunasCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SandyBridge Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.0-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1077993/+subscriptions

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


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

2018-02-15 Thread 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/1749891/+attachment/5056392/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1749891/+attachment/5056401/+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/1749891

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb 15 22:29:04 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-15 (0 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:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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: 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/1749891/+subscriptions

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


[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-02-15 Thread Daniel van Vugt
OK, if not https://bugzilla.gnome.org/show_bug.cgi?id=775376 then maybe
https://bugzilla.gnome.org/show_bug.cgi?id=782530

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

** No longer affects: gnome-bluetooth

** Also affects: gnome-bluetooth via
   https://bugzilla.gnome.org/show_bug.cgi?id=782530
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  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: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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


[Desktop-packages] [Bug 1742950] Re: Snap sections are not shown in GNOME Software

2018-02-15 Thread 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/1742950

Title:
  Snap sections are not shown in GNOME Software

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

Bug description:
  The Snap Store maintains app sections:

  $ snap find --section=games
  NameVersionDeveloper   Notes  Summary
  boa 0.3njmcphail   -  WolfenDoom: Blade 
of Agony
  pin-town2.0.79 failsafegames   -  Help the Pin Pals 
in this physics puzzle game, inspired by Pachinko
  …

  However, GNOME Software does not make use of these. It should be
  taught to display these and their contents when snap support is
  enabled.

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

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


[Desktop-packages] [Bug 1749893] [NEW] d

2018-02-15 Thread Pedro Rodriguez
Public bug reported:

d

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Feb 15 23:02:31 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
InstallationDate: Installed on 2018-02-12 (4 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
MachineType: Dell Inc. OptiPlex 7010
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f0fb8733-b752-4d96-a6b4-0265d1c7e1a8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0YXT71
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0YXT71:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
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.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  d

Status in xorg package in Ubuntu:
  New

Bug description:
  d

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Feb 15 23:02:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0577]
  InstallationDate: Installed on 2018-02-12 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. OptiPlex 7010
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f0fb8733-b752-4d96-a6b4-0265d1c7e1a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0YXT71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd09/09/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0YXT71:rvrA02:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-02-15 Thread Bug Watch Updater
** Changed in: gnome-bluetooth
   Status: Confirmed => 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/1738838

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Invalid
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  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: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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


[Desktop-packages] [Bug 1742950] Re: Snap sections are not shown in GNOME Software

2018-02-15 Thread Robert Ancell
** Also affects: gnome-software (Ubuntu Bionic)
   Importance: High
 Assignee: Robert Ancell (robert-ancell)
   Status: Triaged

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

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

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

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

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

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

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

Title:
  Snap sections are not shown in GNOME Software

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

Bug description:
  The Snap Store maintains app sections:

  $ snap find --section=games
  NameVersionDeveloper   Notes  Summary
  boa 0.3njmcphail   -  WolfenDoom: Blade 
of Agony
  pin-town2.0.79 failsafegames   -  Help the Pin Pals 
in this physics puzzle game, inspired by Pachinko
  …

  However, GNOME Software does not make use of these. It should be
  taught to display these and their contents when snap support is
  enabled.

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

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


[Desktop-packages] [Bug 1749890] [NEW] Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share"

2018-02-15 Thread Jason Heeris
Public bug reported:

Under 17.04, I had added an Owncloud account to the Gnome Online
Accounts under Gnome 3. This created an entry in Nautilus' sidebar that
allowed me to remotely browse my Owncloud account. Since upgrading to
17.10, clicking on the entry just brings up an error dialog:

Unable to access "@"
Not a WebDAV enabled share
[OK]

I get exactly the same error if I type
"davs:///remote.php/webdav/" into the location field.

I had earlier accessed the same server successfully that morning under
17.04, and I'm certain nothing's changed server side. Rebooting doesn't
help, installing davfs2 doesn't help, neither does fusedav. I've tried
removing and re-adding the account in Online Accounts. The server is
accessible via web and the desktop sync client sees it fine.

The server is not internal, it's on the public internet. There is a
corporate proxy for which I use CNTLM. But again, this hasn't changed
since before the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb 16 14:28:56 2018
InstallationDate: Installed on 2017-04-25 (296 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2018-01-24 (22 days ago)

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


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

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

Title:
  Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share"

Status in nautilus package in Ubuntu:
  New

Bug description:
  Under 17.04, I had added an Owncloud account to the Gnome Online
  Accounts under Gnome 3. This created an entry in Nautilus' sidebar
  that allowed me to remotely browse my Owncloud account. Since
  upgrading to 17.10, clicking on the entry just brings up an error
  dialog:

  Unable to access "@"
  Not a WebDAV enabled share
  [OK]

  I get exactly the same error if I type
  "davs:///remote.php/webdav/" into the location field.

  I had earlier accessed the same server successfully that morning under
  17.04, and I'm certain nothing's changed server side. Rebooting
  doesn't help, installing davfs2 doesn't help, neither does fusedav.
  I've tried removing and re-adding the account in Online Accounts. The
  server is accessible via web and the desktop sync client sees it fine.

  The server is not internal, it's on the public internet. There is a
  corporate proxy for which I use CNTLM. But again, this hasn't changed
  since before the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 16 14:28:56 2018
  InstallationDate: Installed on 2017-04-25 (296 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2018-01-24 (22 days ago)

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

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


[Desktop-packages] [Bug 1552040] Re: Laptop sometimes doesn't detect external monitor

2018-02-15 Thread Sergey Menshikov
Ubuntu 17.10 Gnome/Xorg Lenovo 4th gen X1  20FBxxx Skylake i7 Intel built-in 
video
Kernel 4.13.0-32-generic #35-Ubuntu SMP

When connecting Thinkpad Dock with 2 Dell monitors, screen locks up
(mouse is moving though) and is not responding. Monitors are not
recognized. Unlocks 20 sec after disconnect. Happens every time after
first connection following a reboot (first connection after reboot is
OK)

dmesg shows a lot of:
drm:intel_wait_ddi_buf_idle [i915_bpo]] *ERROR* ...

Workaround:

sudo vi /usr/share/X11/xorg.conf.d/20-intel.conf

paste:

Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
Option  "DRI"   "3"
EndSection

reboot
The issue does not return, unless the above file it removed.

Hat tip to
https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support

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

Title:
  Laptop sometimes doesn't detect external monitor

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Usually a reboot fixes the problem. I see stuff like this in dmesg.

  [15294.887642] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15295.568309] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15295.587193] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15296.267547] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15296.286426] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15296.886015] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15296.886264] [drm:intel_dp_link_training_channel_equalization [i915]] 
*ERROR* failed to train DP, aborting
  [15296.898472] [drm:intel_dp_link_training_channel_equalization [i915]] 
*ERROR* Timed out waiting for DP idle patterns
  [15296.899688] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15297.579305] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15297.598328] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15298.279238] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15298.298275] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15298.965500] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15298.984539] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15299.665619] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15299.684522] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15300.367119] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15300.386173] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15301.067203] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15301.086097] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting 
for DDI BUF C idle bit
  [15301.768998] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too 
many voltage retries, give up
  [15301.769703] [drm:intel_dp_link_training_channel_equalization [i915]] 
*ERROR* failed to train DP, aborting
  [15301.781947] [drm:intel_dp_link_training_channel_equalization [i915]] 
*ERROR* Timed out waiting for DP idle patterns

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BootLog: [  OK  ] Started LSB: Speech Dispatcher.
  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 Mar  1 20:58:27 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2016-02-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  MachineType: LENOVO 20AQS00500
  

[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Steve Bainton
Sure.

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With Xubuntu or Kubuntu the screen turns off a few seconds after
  choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
  minutes to be presented. From that point on everything seems to work
  as normal.

  Booting consistently took only a minute in Kubuntu 14.04.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


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

2018-02-15 Thread 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/1749880/+attachment/5056346/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1749880/+attachment/5056355/+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/1749880

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed on S4

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb 15 19:08:50 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-15 (0 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:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () 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: 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/1749880/+subscriptions

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


[Desktop-packages] [Bug 1749876] Re: /usr/bin/gnome-shell:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:__alloc_dir:opendir_tail

2018-02-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1749732 ***
https://bugs.launchpad.net/bugs/1749732

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

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

Title:
  /usr/bin/gnome-
  
shell:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:__alloc_dir:opendir_tail

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.20.4-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce 
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/gnome-shell/+bug/1749876/+subscriptions

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


[Desktop-packages] [Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()

2018-02-15 Thread Daniel van Vugt
Tracking in:
https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce

** Description changed:

+ https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce
+ 
+ ---
+ 
  This is:
  apt-cache policy gnome-shell
  gnome-shell:
-   Installed: 3.18.5-0ubuntu0.3
-   Candidate: 3.18.5-0ubuntu0.3
-   Version table:
- on Ubuntu 
+   Installed: 3.18.5-0ubuntu0.3
+   Candidate: 3.18.5-0ubuntu0.3
+   Version table:
+ on Ubuntu
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  Gnome Shell will crash just about every time when doing software
  updates. For instance this morning when updating:
  
  Start-Date: 2018-02-15  09:04:14
  Commandline: apt-get -y install postfix postfix-doc
  Upgrade: postfix:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3), 
postfix-doc:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3)
  End-Date: 2018-02-15  09:05:31
  
  it crashed.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Feb 15 08:56:24 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (1210 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
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  malloc_consolidate (av=av@entry=0x7f5cbb99eb20 ) at malloc.c:4183
-  _int_malloc (av=av@entry=0x7f5cbb99eb20 , 
bytes=bytes@entry=32816) at malloc.c:3450
-  __GI___libc_malloc (bytes=32816) at malloc.c:2913
-  __alloc_dir (statp=0x7ffea71631b0, flags=0, close_fd=true, fd=33) at 
../sysdeps/posix/opendir.c:247
-  opendir_tail (fd=33) at ../sysdeps/posix/opendir.c:145
+  malloc_consolidate (av=av@entry=0x7f5cbb99eb20 ) at malloc.c:4183
+  _int_malloc (av=av@entry=0x7f5cbb99eb20 , 
bytes=bytes@entry=32816) at malloc.c:3450
+  __GI___libc_malloc (bytes=32816) at malloc.c:2913
+  __alloc_dir (statp=0x7ffea71631b0, flags=0, close_fd=true, fd=33) at 
../sysdeps/posix/opendir.c:247
+  opendir_tail (fd=33) at ../sysdeps/posix/opendir.c:145
  Title: gnome-shell crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce

  ---

  This is:
  apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.3
    Candidate: 3.18.5-0ubuntu0.3
    Version table:
  on Ubuntu
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Gnome Shell will crash just about every time when doing software
  updates. For instance this morning when updating:

  Start-Date: 2018-02-15  09:04:14
  Commandline: apt-get -y install postfix postfix-doc
  Upgrade: postfix:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3), 
postfix-doc:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3)
  End-Date: 2018-02-15  09:05:31

  it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Feb 15 08:56:24 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (1210 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: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f5cbb99eb20 ) at malloc.c:4183
   _int_malloc (av=av@entry=0x7f5cbb99eb20 , 
bytes=bytes@entry=32816) at malloc.c:3450
   __GI___libc_malloc (bytes=32816) at malloc.c:2913
   __alloc_dir (statp=0x7ffea71631b0, flags=0, close_fd=true, fd=33) at 
../sysdeps/posix/opendir.c:247
   opendir_tail (fd=33) at ../sysdeps/posix/opendir.c:145
  Title: gnome-shell crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm 

[Desktop-packages] [Bug 1749675] Re: gnome-shell crashes randomly

2018-02-15 Thread Daniel van Vugt
Unfortunately we can't help you without some kind of crash file or dump
file.

Please have a look in /var/crash for such related files and upload them
using this tool:

  ubuntu-bug /var/crash/YOURFILE.crash

When done, add a comment here telling us the new bug ID.

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

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

Title:
  gnome-shell crashes randomly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  `gnome-shell` crashes randomly. Hard to tell why since the `apport-
  gtk` popup doesn't show up. The crash seems to be related to high I/O
  load on ZFS datasets.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  Uname: Linux 4.15.0-041500-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 11:10:08 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 
'clipboard-indica...@tudmotu.com', 'system-moni...@paradoxxx.zero.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'vlc_vlc.desktop', 
'kde4-kile.desktop', 'org.gnome.gedit.desktop', 'gnome-system-monitor.desktop', 
'keepassx.desktop', 'jabref.desktop', 'virtualbox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: 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/1749675/+subscriptions

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


[Desktop-packages] [Bug 1749876] [NEW] /usr/bin/gnome-shell:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:__alloc_dir:opendir_tail

2018-02-15 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1749732 ***
https://bugs.launchpad.net/bugs/1749732

Public bug reported:

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

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


** Tags: xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
shell:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:__alloc_dir:opendir_tail

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.20.4-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce 
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/gnome-shell/+bug/1749876/+subscriptions

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


[Desktop-packages] [Bug 1749665] Re: clickpad emulated right click button now emitting left click event

2018-02-15 Thread Daniel van Vugt
For clickpads this is the expected default behaviour now (see bug
1699033).

Your "emulated buttons" actually don't exist, except in software.
They're just paint on the touchpad and not real buttons.

To change back to the old behaviour you can install package 'gnome-tweak-tool' 
and set:
   Keyboard & Mouse > Touchpad > Click Method = Areas

** Package changed: libinput (Ubuntu) => gsettings-desktop-schemas
(Ubuntu)

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  clickpad emulated right click button now emitting left click event

Status in gsettings-desktop-schemas package in Ubuntu:
  Won't Fix

Bug description:
  I upgraded my laptop to bionic last week. It is a Dell Inspiron 5000
  series skylake laptop with Synaptics clickpad.

  It has 2 emulated buttons at the bottom, however since upgrading the
  right click button (area) is now emitting a left click instead of
  right click.

  2 finger right click continues to work as expected.

  xev output (first event is left click area, second right click)
  ButtonPress event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5203741, (67,75), root:(117,189),
  state 0x10, button 1, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5203964, (67,75), root:(117,189),
  state 0x110, button 1, same_screen YES

  ButtonPress event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5207317, (67,75), root:(117,189),
  state 0x10, button 1, same_screen YES

  ButtonRelease event, serial 37, synthetic NO, window 0x341,
  root 0x137, subw 0x0, time 5207493, (67,75), root:(117,189),
  state 0x110, button 1, same_screen YES

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libinput10 1.9.4-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,snap,regex,gnomecompat,mousepoll,wall,move,grid,vpswitch,unitymtgrabhandles,place,resize,animation,expo,workarounds,session,fade,ezoom,scale,unityshell,dbus]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Feb 15 20:31:56 2018
  DistUpgraded: 2018-02-11 12:12:03,492 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.6, 4.12.0-13-generic, x86_64: installed
   virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:06b2]
  InstallationDate: Installed on 2016-05-27 (628 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160509)
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=312a4c17-55ca-49fc-8052-35c29b1cf0ce ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: libinput
  UpgradeStatus: Upgraded to bionic on 2018-02-11 (4 days ago)
  dmi.bios.date: 12/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 052K07
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd12/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn052K07:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  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+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/gsettings-desktop-schemas/+bug/1749665/+subscriptions

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


[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

2018-02-15 Thread Daniel van Vugt
Please install 'openssh-server' and log into the system from another
computer. Now reproduce the freeze and during the freeze, run this from
your ssh login:

  apport-cli -u 1749779 --hanging -P `pidof -s gnome-shell`

With some luck that will give us the information we need to debug this.

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

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.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/1749779/+subscriptions

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


[Desktop-packages] [Bug 1749665] [NEW] clickpad emulated right click button now emitting left click event

2018-02-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I upgraded my laptop to bionic last week. It is a Dell Inspiron 5000
series skylake laptop with Synaptics clickpad.

It has 2 emulated buttons at the bottom, however since upgrading the
right click button (area) is now emitting a left click instead of right
click.

2 finger right click continues to work as expected.

xev output (first event is left click area, second right click)
ButtonPress event, serial 37, synthetic NO, window 0x341,
root 0x137, subw 0x0, time 5203741, (67,75), root:(117,189),
state 0x10, button 1, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x341,
root 0x137, subw 0x0, time 5203964, (67,75), root:(117,189),
state 0x110, button 1, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x341,
root 0x137, subw 0x0, time 5207317, (67,75), root:(117,189),
state 0x10, button 1, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x341,
root 0x137, subw 0x0, time 5207493, (67,75), root:(117,189),
state 0x110, button 1, same_screen YES

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libinput10 1.9.4-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,snap,regex,gnomecompat,mousepoll,wall,move,grid,vpswitch,unitymtgrabhandles,place,resize,animation,expo,workarounds,session,fade,ezoom,scale,unityshell,dbus]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Feb 15 20:31:56 2018
DistUpgraded: 2018-02-11 12:12:03,492 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.6, 4.12.0-13-generic, x86_64: installed
 virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 520 [1028:06b2]
   Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:06b2]
InstallationDate: Installed on 2016-05-27 (628 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160509)
MachineType: Dell Inc. Inspiron 5559
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=312a4c17-55ca-49fc-8052-35c29b1cf0ce ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: libinput
UpgradeStatus: Upgraded to bionic on 2018-02-11 (4 days ago)
dmi.bios.date: 12/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 052K07
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd12/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn052K07:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.89-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
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+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: gsettings-desktop-schemas (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic regression single-occurrence 
third-party-packages ubuntu
-- 
clickpad emulated right click button now emitting left click event
https://bugs.launchpad.net/bugs/1749665
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.

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


[Desktop-packages] [Bug 1734044] Re: gnome-shell crashes when monitor turned off or switch kvm

2018-02-15 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Fix Released

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  gnome-shell crashes when monitor turned off or switch kvm

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome shell will crash every time when I turn off monitor or switch the kvm 
to my other system.
  Following message was captured in my journalctl log previously:

  Nov 10 17:34:31 ubox gnome-shell[1235]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
  Nov 10 17:34:31 ubox gnome-shell[1235]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 22 23:10:24 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-27 (27 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/gnome-shell/+bug/1734044/+subscriptions

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


[Desktop-packages] [Bug 1749864] [NEW] simple-scan crashes scanning on brother mfc-J985DW scanner

2018-02-15 Thread bjb1959
Public bug reported:

[+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
[+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
[+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 
'detailed_action_name != NULL' failed
[+0.05s] DEBUG: app-window.vala:1714: Loading state from 
/home/bartb1959/.cache/simple-scan/state
[+0.09s] DEBUG: app-window.vala:1671: Restoring window to 600x400 pixels
[+0.09s] DEBUG: app-window.vala:1675: Restoring window to maximized
[+0.09s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0.09s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0.15s] DEBUG: scanner.vala:1454: sane_init () -> SANE_STATUS_GOOD
[+0.15s] DEBUG: scanner.vala:1460: SANE version 1.0.27
[+0.15s] DEBUG: scanner.vala:1521: Requesting redetection of scan devices
[+0.15s] DEBUG: scanner.vala:806: Processing request
[+0.19s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+0.32s] DEBUG: Encoding raw
[+0.32s] DEBUG: Dimensions: 16 x 16
[+0.32s] DEBUG: Rowstride: 64, Length: 1048
[+0.32s] DEBUG: Copy pixels == false
[+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+0.32s] DEBUG: Encoding raw
[+0.32s] DEBUG: Dimensions: 16 x 16
[+0.32s] DEBUG: Rowstride: 64, Length: 1048
[+0.32s] DEBUG: Copy pixels == false
[+0.32s] DEBUG: gdk_pixbuf_from_pixdata() called on:
[+0.32s] DEBUG: Encoding raw
[+0.32s] DEBUG: Dimensions: 16 x 16
[+0.32s] DEBUG: Rowstride: 64, Length: 1048
[+0.32s] DEBUG: Copy pixels == false
[+0.41s] DEBUG: app-window.vala:1775: Saving state to 
/home/bartb1959/.cache/simple-scan/state
[+3.08s] DEBUG: simple-scan.vala:454: Requesting scan at 300 dpi from device 
'(null)'
[+3.08s] DEBUG: scanner.vala:1569: Scanner.scan ("(null)", dpi=300, 
scan_mode=ScanMode.COLOR, depth=8, type=ScanType.SINGLE, paper_width=2159, 
paper_height=2794, brightness=0, contrast=0, delay=15ms)
[+6.98s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:net1;dev0" 
vendor="Brother" model="*mfcj985dwxl" type="MFCJ985DW"
[+6.98s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev7" 
vendor="Brother" model="MFC-J985DW" type="USB scanner"
[+6.98s] DEBUG: scanner.vala:806: Processing request
[+8.67s] DEBUG: scanner.vala:867: sane_open ("brother4:net1;dev0") -> 
SANE_STATUS_GOOD
[+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (0)
[+8.67s] DEBUG: scanner.vala:738: Option 0: name='(null)' title='Number of 
options' type=bool size=4 cap=soft-detect
[+8.67s] DEBUG: scanner.vala:741:   Description: Read-only option that 
specifies how many options a specific devices supports.
[+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (1)
[+8.67s] DEBUG: scanner.vala:738: Option 1: name='(null)' title='Mode' 
type=group size=4 cap=advanced
[+8.67s] DEBUG: scanner.vala:741:   Description: 
[+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (2)
[+8.67s] DEBUG: scanner.vala:738: Option 2: name='mode' title='Scan mode' 
type=string size=30 values=["Black & White", "Gray[Error Diffusion]", "True 
Gray", "24bit Color", "24bit Color[Fast]"] cap=soft-select,soft-detect
[+8.67s] DEBUG: scanner.vala:741:   Description: Select the scan mode
[+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (3)
[+8.67s] DEBUG: scanner.vala:738: Option 3: name='resolution' title='Scan 
resolution' type=int size=4 unit=dpi values=[100, 150, 200, 300, 400, 600, 
1200, 2400, 4800, 9600] cap=soft-select,soft-detect
[+8.67s] DEBUG: scanner.vala:741:   Description: Sets the resolution of the 
scanned image.
[+8.67s] DEBUG: scanner.vala:888: sane_get_option_descriptor (4)
[+8.67s] DEBUG: scanner.vala:738: Option 4: name='source' title='Scan source' 
type=string size=64 values=["FlatBed", "Automatic Document Feeder(left 
aligned)", "Automatic Document Feeder(left aligned,Duplex)", "Automatic 
Document Feeder(centrally aligned)", "Automatic Document Feeder(centrally 
aligned,Duplex)"] cap=soft-select,soft-detect
[+8.67s] DEBUG: 


[+0.00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.3, PID=14852
[+0.02s] CRITICAL: g_action_print_detailed_name: assertion 
'g_action_name_is_valid (action_name)' failed
[+0.02s] CRITICAL: gtk_application_set_accels_for_action: assertion 
'detailed_action_name != NULL' failed
[+0.05s] DEBUG: app-window.vala:1714: Loading state from 
/home/bartb1959/.cache/simple-scan/state
[+0.09s] DEBUG: app-window.vala:1671: Restoring window to 600x400 pixels
[+0.09s] DEBUG: app-window.vala:1675: Restoring window to maximized
[+0.09s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0.09s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0.15s] DEBUG: scanner.vala:1454: sane_init () -> SANE_STATUS_GOOD
[+0.15s] DEBUG: scanner.vala:1460: 

[Desktop-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-15 Thread Christopher M. Penalver
Pierre Wilch:

Regarding GNOME Flashback, one would have to install it via a terminal:
sudo apt-get install gnome-session-flashback

Once installed, and you restart to the login screen, GNOME Flashback
(Metacity) should be an option.

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Conditions:
  - in the upper bar the display of the seconds must be enabled
    (in my case the entire date-and-time is displayed, excepted the week 
number);
  - system is set to automatically go into sleep state after the selected delay
    (in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows.

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).

  WORKAROUND: When the seconds are not displayed in the upper bar there
  is no problem.

  ---
  .tmp.unity_support_test.0:

  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1532508] Update Released

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

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed
Status in gnome-shell package in Fedora:
  In Progress

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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


[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2018-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.4.5+16.04.20171201.3

---
unity (7.4.5+16.04.20171201.3) xenial; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * InputMonitor: add an unity class that monitors XInput2 events and
converts them to XEvent
  * EdgeBarrierController: use InputMonitor to get the barrier events
instead of relying on its implementation
  * DecorationsMenuLayout: use input monitor for menu scrubbing (LP:
#1614597)
  * PanelView: use InputMonitor to track menu events
  * LockScreenPanel: use InputMonitor events instead of mouse polling
for menu scrubbing
  * MenuManager: add support for mouse trackers with triangle algorithm
support (LP: #1618405)
  * PanelView: scale gradient refinement properly
  * PanelService: don't allow to deactivate menus if they've been opened
too shortly
  * LockScreenController: ignore icon_paths_changed signal in
menumanager for Lockscreen
  * LockScreenController: use InputMonitor to get all the events and
hide the Blank Window (LP: #1321075)
  * LockScreenController: use input monitor to get the events to switch
monitor (LP: #1316862)
  * LauncherOptions: use track_obj to manage option changes (LP:
#1622995)
  * UnityScreen: toggle gestures recognition on lock (LP: #1645507)
  * GnomeSessionManager: add gcancellable to instance and use it for
calls with temporary proxies
  * BackgroundSettings: use gnome-bg to generate textures with proper
scaling (LP: #1666359)
  * UnityWindow: safely check validity of UnityWindow from scaled one
(LP: #1659847)
  * Panel: ensure the menu-manager tracker is updated to match monitor
(LP: #1671432)
  * compiz-profile-setter: tool to update the current profile and use in
systemd and Unity settings (LP: #1668950)
  * BGHash, UnityScreen: get desktop averageColor from compiz
  * Launcher: disable or reduce most icon effects on lowgfx (LP:
#1700859)
  * PanelController: ensure we disconnect from signals on destruction
(LP: #1504870)
  * tools: add migration script to set the default values for unity-
lowgfx profile

  [ Andrea Azzarone ]
  * Properly handle the file manager copy dialog in
FileManagerLauncherIcon and in StorageLauncherIcon. (LP: #1575452,
LP: #1609845)
  * Correctly position the force quit dialog when scaling is different
than 1.0 (LP: #1637991)
  * GnomeSession: Retrieve the session id using dbus if $XDG_SESSION_ID
is not set
  * Round gtk scaling factor to closest integer. (LP: #1649736)
  * Keep the screen locked if rebooting with autologin. (LP: #1600389)
  * Use g_mkdir_with_parents instead of mkdir.
  * Lockscreen: always draw the background-color in the lockscreen (LP:
#1702701)
  * Refactor the way UserAuthenticator is created and passed around.
Handle failures to create new threads and fallback to a "Switch to
greeter..." button in case of failure. (LP: #1311316)
  * Wait until the color buffer is cleared before suspending. (LP:
#1532508)

  [ Kai-Heng Feng ]
  * UnitySettings: If scale-factor is not set, find and set right scale
for HiDPI displays.

  [ Eleni Maria Stea ]
  * shouldn't create blur rectangles when there's no blur, skips the
blur rects processing in low gfx.
  * removes lowgfx option from ccsm, reads the "lowgfx" gsetting (LP:
#1668950)

  [ Nick Dedekind ]
  * Fixed tooltip scaling issues. (LP: #1673950)

 -- Marco Trevisan (Treviño)   Fri, 01 Dec 2017 18:46:01
+

** Changed in: unity (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed
Status in gnome-shell package in Fedora:
  In Progress

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

Re: [Desktop-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-15 Thread Pierre Wilch
Christopher M. Penalver,

Thank you for your help.

1)  I was using Ubuntu 16.04 since July 2016, and 14.04 before.
I think the problem appeared in spring or summer 2017 with an update.
I do not remember since when I put the seconds display in the upper bar. 
I think already in 2014, but without warranty.
In May 2017 I changed my hard disk from a 320 GB with Windows 10 in dual 
boot UEFI to a 1 TB without Windows, and made a fresh install of Ubuntu 
16.04 only.
I do not remember if the problem came at that time or later. There were 
many things to think about,... and other serious problems with the 16.04 
(now solved) .

2)  I clicked on your link about GNOME Flashback, tried a couple of 
clicks, but did not find the way to log in.
How should I do?
What is Metacity?


On the video I joined notice that the blinking of the screen happens 
simultaneously with the display of the seconds. You can improve the 
description in this way.


I discovered Ubuntu in April 2014.
At the beginning it worked by me on a SD card (legacy) to see what it 
was about, and since that time I have learned a lot, and it is not finished.
With Ubuntu/linux it is never finished.


Le 15/02/2018 à 19:16, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> 1)
>> "So long I remember, this bug appeared before september 2017. No problem in 
>> year 2016."
> What version of Ubuntu were you using in 2016 when this was not reproducible?
>   
> 2) To further root cause, could you please test for this problem by logging 
> into a GNOME Flashback (Metacity) session via 
> https://launchpad.net/ubuntu/+source/gnome-flashback and advise to the 
> results?
>
> ** Description changed:
>
> - Ubuntu 16.04.3 LTS, every updates done.
> -
>Conditions:
>- in the upper bar the display of the seconds must be enabled
> -   (in my case the entire date-and-time is displayed, excepted the week 
> number);
> - - system has set himself automatically in sleep state after the selected 
> delay
> -   (in my case the option "lock the keyboard" is not enabled).
> +   (in my case the entire date-and-time is displayed, excepted the week 
> number);
> + - system is set to automatically go into sleep state after the selected 
> delay
> +   (in my case the option "lock the keyboard" is not enabled).
>On awakening, for example by using the shift touch, parts of the screen 
> are blinking according to 1 second rate and 3 seconds cycle.
> - Coming back to normal behavior needs to close and re-open windows (no!, not 
> M$), etc...
> + Coming back to normal behavior needs to close and re-open windows.
>
>To help to reproduce:
>- edit a message with thunderbird;
>- select ubuntu "parameters";
>- select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
>- select "1 minute";
>- wait 1 minute and going into sleep state;
>- when in sleep state press the "shift" key;
>and then I have a blinking "Christmas tree", too complicated to be 
> described.
>I tested it again 3 times why writing this post (firefox had also an 
> opened window, under thunderbird; with firefox alone, the screen blinks only 
> one time -should also not-).
> - When the seconds are not displayed in the upper bar there is no problem.
>
> - Please do not blame me if xorg is not involved. A way to post had to be 
> found.
> - 'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
> paquet pkgname'.
> - ---
> + WORKAROUND: When the seconds are not displayed in the upper bar there is
> + no problem.
> +
> + ---
>.tmp.unity_support_test.0:
> -
> +
>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
>DistUpgraded: Fresh install
>DistroCodename: xenial
>DistroRelease: Ubuntu 16.04
>DistroVariant: ubuntu
>ExtraDebuggingInterest: Yes
>GraphicsCard:
> -  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
> (rev 09) (prog-if 00 [VGA controller])
> -Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
> Controller [1179:fb31]
> +  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
> (rev 09) (prog-if 00 [VGA controller])
> +    Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
> Controller [1179:fb31]
>InstallationDate: Installed on 2017-06-29 (223 days ago)
>InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
> (20170215.2)
>MachineType: TOSHIBA SATELLITE PRO C850-1GR
>Package: xorg 1:7.7+13ubuntu3
>PackageArchitecture: amd64
>ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
> root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
>ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-15 Thread Yuriy Vidineev
One more detail: this bug is for wireless networks only. Looks like
wired works as expected (please see "Dell docking" on screenshot)

** Attachment added: "Wired network - works"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5056254/+files/Screenshot%20from%202018-02-15%2015-49-40.png

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1734513] Re: Terminal button is breaking

2018-02-15 Thread Egmont Koblinger
Most likely the same as bug 1718238 /
https://gitlab.gnome.org/GNOME/mutter/issues/23 .

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

Title:
  Terminal button is breaking

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I am using ubuntu 18.04 from developer branch. it was rendering
  perfectly on Wayland. but after facing the screen share issue I
  switched it to xorg.

  after this, it is looking like attached image

  I have installed Gnome OSX-IV-1.3 theme, but I tried to switch the
  theme but it is behaving the same.

  NOTE: with the wayland it is not having any issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 14:02:30 2017
  InstallationDate: Installed on 2017-11-19 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171117)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749449] Re: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which i

2018-02-15 Thread Jaime Cruz
Attempted to update from the command line and got this:

The following packages will be upgraded:
  libgl1-mesa-dri:i386
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/6,258 kB of archives.
After this operation, 20.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 255782 files and directories currently installed.)
Preparing to unpack .../libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over 
(17.2.8-0ubuntu0~16.04.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb 
(--unpack):
 trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
Errors were encountered while processing:
 /var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1
  -mesa-dri/changelog.Debian.gz', which is different from other
  instances of package libgl1-mesa-dri:i386

Status in mesa package in Ubuntu:
  New

Bug description:
  Error occurred when running the software updater this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  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
  Date: Wed Feb 14 08:00:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1
   Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over 
(17.2.8-0ubuntu0~16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] 
[1002:682b] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3]
  InstallationDate: Installed on 2014-09-06 (1256 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: HP 510-p127c
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: CNV64609PD
  dmi.board.name: 822A
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.asset.tag: CNV64609PD
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 510-p127c
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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: 

[Desktop-packages] [Bug 1749842] [NEW] /usr/bin/evolution:11:webkit_web_view_drag_end:g_cclosure_marshal_VOID__OBJECTv:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit_by_name

2018-02-15 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

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


** Tags: trusty vivid wily xenial

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

Title:
  
/usr/bin/evolution:11:webkit_web_view_drag_end:g_cclosure_marshal_VOID__OBJECTv:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit_by_name

Status in evolution package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution.  This problem was most recently seen with package version 
3.18.5.2-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/0fdf8157960b2a680071a2ae22c91831947fc8ad 
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/evolution/+bug/1749842/+subscriptions

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


[Desktop-packages] [Bug 1703941] Re: bluetooth not work and wifi some time disable and enable

2018-02-15 Thread Christopher M. Penalver
Abhijeet Ravi Raj, thank you for reporting this and helping make Ubuntu
better.

1) Regarding bluetooth, this appears a known issue due to the vendor not 
providing upstream support:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1355096

Regarding WiFi:

2) Could you please provide the full computer model as noted on the
sticker of the computer itself (not from the Bug Description, or the
result of a terminal command)?

3) Is this something that started to happen after an update? If so,
which?

4) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Description changed:

- my bluetooth and wifi hardware is belongs to Ralink and its detail is
- rt3290, It problem is that it sometime auto disable till the hareware
- which ih turn on and when trying to enable then it not enable its
- fail.My bluetooth is not work infact it doesn't show visibility enable
- option and not work in any ubuntu version.Please tell me what to do?to
- inform me please send me email at "abhirajp...@gmail.com"
+ It problem is that it sometime auto disable till the hareware which ih
+ turn on and when trying to enable then it not enable its fail.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 12 22:16:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2017-07-11 (1 days ago)
  InstallationMedia: It
  Lsusb:
-  Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
-  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
+  Bus 001 Device 002: ID 8087:8000 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  LANG=en_IN
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=6e79f8f5-ebf2-4c7a-a87e-a9f61697f325 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard
  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: Wed Jul 12 21:45:38 2017
  

[Desktop-packages] [Bug 1704250] Re: ERROR

2018-02-15 Thread Christopher M. Penalver
Ricardo, thank you for reporting this and helping make Ubuntu better.

1) Could you please provide a screenshot of the breakdown?

2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  ERROR

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The system has a breakdown problem since the new update from ubuntu
  15.04, I would like to know how to repair it. From already thank you
  very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 13 22:20:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, i686: installed
   bbswitch, 0.8, 4.4.0-66-generic, i686: installed
   bbswitch, 0.8, 4.4.0-75-generic, i686: installed
   bbswitch, 0.8, 4.4.0-83-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] NX8600GT-T2D256EZ 
[1462:0910]
  InstallationDate: Installed on 2017-02-09 (154 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard
   Bus 002 Device 002: ID 04f3:0230 Elan Microelectronics Corp. 3D Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. GA-73VM-S2
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=73161ce2-6cf4-4d9d-8c08-a11a9e14405b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4c
  dmi.board.name: GA-73VM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd10/07/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-73VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-73VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-73VM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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: Thu Jul 13 22:17:49 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB+PS/2 Optical Mouse MOUSE, id 8
   inputHID 0b38:0010KEYBOARD, id 9
   inputHID 0b38:0010KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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


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

2018-02-15 Thread Christopher M. Penalver
Charlie, thank you for reporting this and helping make Ubuntu better.

1) Is this something that started to happen after an update? If so,
which specifically?

2) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

** Tags added: bios-outdated-a27

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using two monitors:

  1. Moved an image from picture folder to primary secondary monitor
  desktop

  2. Opened a folder on primary monitor

  3. Tried to drag image file into - file 'declines and mouse curser is
  now a fist icon and mouse clicks on image have no effect.

  4. Logged out and right click mouse menu is back and I can send the
  image to rubbish bin and return to the desktop but issue still occurs
  and is repeatable.

  I realize that this may not be a Xorg problem but not sure what is
  causing my issue. Happy to carry out more tests/supply more
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic i686
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Jul 16 17:20:37 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1704409] Re: Flickering screen on ubuntu 16.04.2 Lenovo B70

2018-02-15 Thread Christopher M. Penalver
lotuspsychje, thank you for reporting this and helping make Ubuntu
better.

1) Could you please advise to why you use the non-default kernel parameter:
acpi_osi=Windows 2013

2) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: bios-outdated-d1cn96ww

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Flickering screen on ubuntu 16.04.2 Lenovo B70

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Tested both unity & ubuntu-gnome on 16.04.2
  and both are constantly flickering from login to desktop and on LIVEusb on a 
product: 

  Haswell-ULT Integrated Graphics Controller and driver=i915

  and kernel: Linux fernand-Lenovo-B70-80 4.8.0-58-generic
  #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64
  x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.9
  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: Fri Jul 14 17:18:12 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3987]
  InstallationDate: Installed on 2017-07-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp.
   Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=c471367f-a9a5-4e15-a987-f7b614634a1d ro quiet splash 
"acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D1CN06WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrD1CN06WW:bd05/18/2015:svnLENOVO:pn80MR:pvrLenovoB70-80:rvnLENOVO:rnLenovoB70-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB70-80:
  dmi.product.name: 80MR
  dmi.product.version: Lenovo B70-80
  dmi.sys.vendor: LENOVO
  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 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: Fri Jul 14 17:06:37 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5921
   vendor CMN
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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

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


[Desktop-packages] [Bug 1748999] Re: [SRU] libreoffice 5.4.5 for artful

2018-02-15 Thread Adolfo Jayme
** Information type changed from Public to Public Security

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

Title:
  [SRU] libreoffice 5.4.5 for artful

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice-l10n package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 5.4.5 is the fifth bugfix release of the still 5.4 line. 
Version 5.4.4 is currently in artful-proposed.
 For a list of fixed bugs compared to 5.4.4 see the list of bugs fixed in 
the RC1:
   https://wiki.documentfoundation.org/Releases/5.4.5/RC1#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.5 fixes CVE-2018-6871

  [Test Case]

   * CVE-2018-6871 should be verified to be fixed

   * No other specific test case, bugs fixed upstream hopefully come
  with unit/regression tests, and the release itself is extensively
  exercised upstream (both in an automated manner and manually) by a
  community of testers. Each minor release usually goes through two
  release candidates, but 5.4.5 was initially unscheduled and it had a
  shortened cycle (only a single RC).

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 69 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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


[Desktop-packages] [Bug 1705297] Re: login after booting hangs

2018-02-15 Thread Christopher M. Penalver
Peter Schmitt, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect 1705297

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

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

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


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

2018-02-15 Thread Christopher M. Penalver
** Description changed:

- Seems to only happen when using the nouveau driver (switching to
- nvidia-375 driver yields a stable system.)
+ Freeze has happened in two situations - first was when opening Totem,
+ the second occurred when opening the Plex Media Manager (which opens in
+ Chrome browser).
  
- Freeze has happened in two situations that I've noticed - first one was
- when open Totem movie player, second one occurred when opening the Plex
- Media Manager (which opens in Chrome browser).
+ WORKAROUND: Use the nvidia-375 driver.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,imgpng,resize,compiztoolbox,gnomecompat,regex,move,animation,vpswitch,mousepoll,snap,wall,grid,place,unitymtgrabhandles,expo,workarounds,session,fade,scale,ezoom,unityshell]
  Date: Thu Jul 20 17:51:44 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
-  bbswitch, 0.8, 4.4.0-79-generic, x86_64: installed
-  bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
-  virtualbox, 5.0.40, 4.4.0-79-generic, x86_64: installed
-  virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-79-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
+  virtualbox, 5.0.40, 4.4.0-79-generic, x86_64: installed
+  virtualbox, 5.0.40, 4.4.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
-  NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
+  NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
  InstallationDate: Installed on 2016-10-02 (291 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=c1765f93-69c1-4371-9aed-52f9168c068d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FE
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S2PV
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFE:bd06/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PV:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: Thu Jul 20 17:32:21 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freeze has 

[Desktop-packages] [Bug 1749692] Re: My Resolution is verry Low

2018-02-15 Thread Christopher M. Penalver
Everton Messias Santos Sena, thank you for reporting this and helping
make Ubuntu better.

1) Could you please provide the full monitor manufacturer and model as
noted on the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command)?

2) How are you connecting the monitor to the computer, VGA, HDMI, etc.?

3) Is this something that started to happen after an update? If so,
which specifically?

** Tags added: bios-outdated-0406

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  My Resolution is verry Low

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My monitor is HD but the system only shows low resolution.The highest is 
1024x768.
  What can I do to get more resolution options?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-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: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:04:20 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Generation Core Processor Family 
Integrated Graphics Controller [103c:0266]
  InstallationDate: Installed on 2018-02-06 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP 402 G1 SFF Business PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a8d31c50-2e57-46fd-bbfb-a8f11d427e0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: BRJ448DM7Q
  dmi.board.name: 0266
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: BRJ448DM7Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 1.02
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd04/03/2014:svnHewlett-Packard:pnHP402G1SFFBusinessPC:pvr1.02:rvnHewlett-Packard:rn0266:rvr1.02:cvnHewlett-Packard:ct3:cvr1.02:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP 402 G1 SFF Business PC
  dmi.product.version: 1.02
  dmi.sys.vendor: Hewlett-Packard
  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 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

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

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-02-15 Thread Jeremy Bicha
You're welcome to work on this bug before those transitions happen. :)

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-02-15 Thread Khurshid Alam
Thanks. I will wait for these transitions to finish first.

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


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

2018-02-15 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  plugged my htc one m8 into USB after a factory reset of the phone.
  n.b. the phone is running lineage os, and I was getting this before
  reset

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Feb 15 21:22:16 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2014-08-13 (1282 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 
/org/gtk/gvfs/exec_spaw/17
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f21504465a9:mov0x18(%rax),%rax
   PC (0x7f21504465a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1749822] Re: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2018-02-15 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libvorbis package in Ubuntu:
  New

Bug description:
  after installing pdfsam from the appstore the progam did not start. I
  have update ubuntu in terminal and I have got the error. I have
  removed and reinstalled the program but no solution. Check the issue
  on forums and try the solution. The problem maintain the same

  Earlier today I have installed dropbox but this is function fine.

  Ubuntu 16.04.3 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libvorbis0a: Install
   libvorbis0a: Configure
   libvorbisenc2: Configure
   libvorbisfile3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Feb 15 22:05:56 2018
  DuplicateSignature:
   package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
   Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
   dpkg: error processing package libvorbisenc2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-11 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: libvorbis
  Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Christopher M. Penalver
Steve Bainton:

To advise, post the terminal commands along with demsg after a bad boot.
Posting it after a good boot doesn't help.

** Description changed:

- Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
- after choosing Ubuntu in grub2 menu, and after about 5 minutes the login
- screen is presented and from that point on everything seems to work as
+ With Xubuntu or Kubuntu the screen turns off a few seconds after
+ choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
+ minutes to be presented. From that point on everything seems to work as
  normal.
+ 
+ Booting consistently took only a minute in Kubuntu 14.04.
  
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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

** Attachment removed: "systemd-analyze*blame"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056015/+files/systemd-analyze%2Ablame

** Attachment removed: "systemd-analyze*critical-chain.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056016/+files/systemd-analyze%2Acritical-chain.txt

** Attachment removed: "systemd-analyze"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056014/+files/systemd-analyze

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  With Xubuntu or Kubuntu the screen turns off a few seconds after
  choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5
  minutes to be presented. From that point on everything seems to work
  as normal.

  Booting consistently took only a minute in Kubuntu 14.04.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1749822] [NEW] package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

2018-02-15 Thread Marco Vronik
Public bug reported:

after installing pdfsam from the appstore the progam did not start. I
have update ubuntu in terminal and I have got the error. I have removed
and reinstalled the program but no solution. Check the issue on forums
and try the solution. The problem maintain the same

Earlier today I have installed dropbox but this is function fine.

Ubuntu 16.04.3 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 libvorbis0a: Install
 libvorbis0a: Configure
 libvorbisenc2: Configure
 libvorbisfile3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Feb 15 22:05:56 2018
DuplicateSignature:
 package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
 Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
 dpkg: error processing package libvorbisenc2:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-11 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: libvorbis
Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libvorbis package in Ubuntu:
  New

Bug description:
  after installing pdfsam from the appstore the progam did not start. I
  have update ubuntu in terminal and I have got the error. I have
  removed and reinstalled the program but no solution. Check the issue
  on forums and try the solution. The problem maintain the same

  Earlier today I have installed dropbox but this is function fine.

  Ubuntu 16.04.3 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libvorbisenc2:amd64 1.3.5-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libvorbis0a: Install
   libvorbis0a: Configure
   libvorbisenc2: Configure
   libvorbisfile3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Feb 15 22:05:56 2018
  DuplicateSignature:
   package:libvorbisenc2:amd64:1.3.5-3ubuntu0.1
   Setting up libvorbis0a:amd64 (1.3.5-3ubuntu0.1) ...
   dpkg: error processing package libvorbisenc2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-11 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: libvorbis
  Title: package libvorbisenc2:amd64 1.3.5-3ubuntu0.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection

2018-02-15 Thread Thomas Criscione
** Description changed:

- lsb_release -rd: 
+ lsb_release -rd:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  Network Settings package version in Software Center:
  15.04.0+16.04.20160705-0ubuntu1
  
  Prior to upgrading to 16.04 LTS I was running 14.04 LTS.  Using the
  "Edit Connections..." menu option I had created a custom Ethernet
  connection that had some custom routes added.  These routes are required
  for me to connect to certain resources on a local network while using
  Wifi for basic internet. (Physical network locked down, no Internet
  access available)
  
  I've attached a screenshot showing the routes.  These routes were
  working great in 14.04 (And prior releases of Ubuntu).
  
  However, upon upgrading to 16.04, I noticed this connection would no
  longer "connect".  It would just silently fail.  I noticed that if I
  deleted my custom routes, it would work, but I need those in order to
  connect to my required network services.
  
  When I try to connect with the routes in place, the connection silently
  fails in the NetworkManager UI (I get no error message in the UI) but I
  took a look at syslog and found these:
  
- 
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  
[1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 
101 (Network is unreachable)
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  
[1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 
101 (Network is unreachable)
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  
[1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 
101 (Network is unreachable)
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  
[1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: 
failure 101 (Network is unreachable)
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:   
[1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 
'config-failed') [70 120 4]
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:   
[1470057319.7289] device (enp0s31f6): Activation: failed for connection 
'Windstream'
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:   
[1470057319.7309] device (enp0s31f6): state change: failed -> disconnected 
(reason 'none') [120 30 0]
  
- 
- Now, if I remove the custom routes from the UI, then I can connect.  I them 
manually add the routes using the "ip" command:
+ Now, if I remove the custom routes from the UI, then I can connect.  I
+ them manually add the routes using the "ip" command:
  
  sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6
  sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6
  sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6
  sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6
  
  This is able to add the routes successfully.  So there has to be some
  problem in the new implementation of NetworkManager in 16.04, because
  these routes worked in 14.04 and they still work in 16.04 if I just
  manually add them from the command line.
  
  For now I can work around this issue by manually adding these routes
  from the command line every time I connect.

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

Title:
  ip4 static routes added in NetworkManager UI fail and prevent
  connection

Status in network-manager package in Ubuntu:
  Confirmed

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

  Network Settings package version in Software Center:
  15.04.0+16.04.20160705-0ubuntu1

  Prior to upgrading to 16.04 LTS I was running 14.04 LTS.  Using the
  "Edit Connections..." menu option I had created a custom Ethernet
  connection that had some custom routes added.  These routes are
  required for me to connect to certain resources on a local network
  while using Wifi for basic internet. (Physical network locked down, no
  Internet access available)

  I've attached a screenshot showing the routes.  These routes were
  working great in 14.04 (And prior releases of Ubuntu).

  However, upon upgrading to 16.04, I noticed this connection would no
  longer "connect".  It would just silently fail.  I noticed that if I
  deleted my custom routes, it would work, but I need those in order to
  connect to my required network services.

  When I try to connect with the routes in place, the connection
  silently fails in the NetworkManager UI (I get no error message in the
  UI) but I took a look at syslog and found these:

  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  
[1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 
101 (Network is unreachable)
  Aug  1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]:  

[Desktop-packages] [Bug 1749690] Re: hp-setup fails to install plugin

2018-02-15 Thread Till Kamppeter
** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  hp-setup fails to install plugin

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  My HP printer requires a binary driver and the only way to install it
  is to run hp-setup from hplip package. It was doing job fine for last
  three years at least, but when I tried to install driver today on a
  fresh 16.04 installation, it couldn't download it.

  $ hp-setup -i 192.168.220.10
  ...
  -
  | PLUG-IN INSTALLATION FOR HPLIP 3.16.3 |
  -

Option  Description   
--  --
d   Download plug-in from HP (recommended)
p   Specify a path to the plug-in (advanced)  
q   Quit hp-plugin (skip installation)

  Enter option (d=download*, p=specify path, q=quit) ? d

  ---
  | DOWNLOAD PLUGIN |
  ---

  Checking for network connection...
  Downloading plug-in from: 
  Downloading plug-in: [\   
] 0% 
  error: Found No Section in /tmp/tmpjeh9zqmg. Please set the http proxy for 
root and try again.

  error:  file does not match its checksum. File may have been corrupted or 
altered
  error: Failed to install Plugin.
  error: The device you are trying to setup requires a binary plug-in. Some 
functionalities may not work as expected without plug-ins. Please run 
'hp-plugin' as normal user to install plug-ins.Visit http://hplipopensource.com 
for more infomation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hplip 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Feb 15 14:55:08 2018
  InstallationDate: Installed on 2018-01-19 (27 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire V3-771
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=07eba8bf-f5de-4911-9574-0416813d1387 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.28
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.28:bd10/21/2013:svnAcer:pnAspireV3-771:pvrV2.28:rvnAcer:rnVA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-771
  dmi.product.version: V2.28
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Steve Bainton
** Attachment added: "systemd-analyze*blame"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056015/+files/systemd-analyze%2Ablame

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
  after choosing Ubuntu in grub2 menu, and after about 5 minutes the
  login screen is presented and from that point on everything seems to
  work as normal.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Steve Bainton
** Attachment added: "systemd-analyze*critical-chain.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056016/+files/systemd-analyze%2Acritical-chain.txt

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
  after choosing Ubuntu in grub2 menu, and after about 5 minutes the
  login screen is presented and from that point on everything seems to
  work as normal.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Steve Bainton
1) It's pretty much hit and miss at this point, sometimes takes longer
sometimes shorter, 5 minutes is still not out of the question but most
of the time it boots ok, although a new error started appearing: [
3.292085] usb 1-3.5.1: device descriptor read/64, error -32

2a,b,c) I've been using Kubuntu 14.04 for years without any problems.
The problems started recently, when I upgraded to 16.04.(maybe I should
consider downgrading kernel?) Never encountered any serious problems on
this hardware in any distro/version prior to 16.04 (as I mentioned
earlier, current kernel misbehaves in Xubuntu, Kubuntu and OpenSUSE)

2d) nothing out of ordinary, a minute or so (guess) 
3) attached (as you will find on this occasion boot up was quick but it's not 
always the case)

Tomorrow I will have time to test it more thoroughly to observe how
frequently abnormalities appear.

** Attachment added: "systemd-analyze"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+attachment/5056014/+files/systemd-analyze

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
  after choosing Ubuntu in grub2 menu, and after about 5 minutes the
  login screen is presented and from that point on everything seems to
  work as normal.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

2018-02-15 Thread Francis Ginther
** Tags added: id-5a37e0a701a3f39adbe6e4b9

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu1

---
gtk+3.0 (3.22.28-1ubuntu1) bionic; urgency=medium

  * Merge with Debian. Remaining changes:
+ Install a settings.ini file to set our themes
+ Enable Mir backend
+ Update debian/libgtk-3-0.symbols
+ debian/control.in:
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
  - box-shadow-changes-modify-clip.ui
  - label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - ubuntu_fileselector_behaviour.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch
  - gtksocket-unscale-before-sending-configurenotify.patch
  - no_content_hub.patch

gtk+3.0 (3.22.28-1) unstable; urgency=medium

  * New upstream release (LP: #1698270) (LP: #1714518)
  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump Standards-Version to 4.1.3
  * Update Vcs fields for migration to https://salsa.debian.org/
  * Drop git_text-view-support-emoji-chooser.patch: Applied in new release

 -- Jeremy Bicha   Thu, 15 Feb 2018 10:15:34 -0500

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Desktop-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2018-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu1

---
gtk+3.0 (3.22.28-1ubuntu1) bionic; urgency=medium

  * Merge with Debian. Remaining changes:
+ Install a settings.ini file to set our themes
+ Enable Mir backend
+ Update debian/libgtk-3-0.symbols
+ debian/control.in:
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
  - box-shadow-changes-modify-clip.ui
  - label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - ubuntu_fileselector_behaviour.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch
  - gtksocket-unscale-before-sending-configurenotify.patch
  - no_content_hub.patch

gtk+3.0 (3.22.28-1) unstable; urgency=medium

  * New upstream release (LP: #1698270) (LP: #1714518)
  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump Standards-Version to 4.1.3
  * Update Vcs fields for migration to https://salsa.debian.org/
  * Drop git_text-view-support-emoji-chooser.patch: Applied in new release

 -- Jeremy Bicha   Thu, 15 Feb 2018 10:15:34 -0500

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749585] Re: postgresql-client-common is not compatible with current postgresql-servers

2018-02-15 Thread Hans Joachim Desserud
** Tags added: xenial

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

Title:
  postgresql-client-common is not compatible with current postgresql-
  servers

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Hi,
  i'm using 16.04 xenial  as host for applications. Our DB-server was updated 
from 9.4 to 9.6 recently and I'm using pg_dump from time to time to clone 
databases. But I'm no more able to do that :-(

  Right now postgresql-client-common can connect to pg up to version 9.5 . I 
tried to install postgresql-client-9.6 manually but I failed because 
postgresql-client-9.6 depends on a newer version of libpg5.  As a workaround I 
tried to manually install the latest version of libpg5 (9.6.7) but another 
depenency (libgss...?) failed.
  Can you please have a look or even ask upstream about the possibility to 
provide postgresql-client for all current server versions (9.6,and 10.2??)

  Nevertheless thank you all for providing the software. It works like a
  charm

  Marc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749585/+subscriptions

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


[Desktop-packages] [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot

2018-02-15 Thread Eric Desrochers
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-slashd

** Changed in: postgresql-common (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: postgresql-common (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: postgresql-common (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  configured stats_temp_directory does not get created after reboot

Status in postgresql-common package in Ubuntu:
  In Progress
Status in postgresql-common source package in Xenial:
  In Progress
Status in postgresql-common source package in Artful:
  In Progress
Status in postgresql-common source package in Bionic:
  In Progress
Status in postgresql-common package in Debian:
  New

Bug description:
  Default postgres installation in Ubuntu (and Debian) configures
  stats_temp_directory inside /var/run/postgresql:

  $ grep stats_temp /etc/postgresql/10/main/postgresql.conf 
  stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp'

  However, this directory is not created after reboot.

  In most cases this is not a problem as systemd starts postgres via
  pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and
  pg_ctlcluster will create missing directories before starting
  postgres.

  But in cases where systemd is not starting postgres this is a problem.
  Specifically, when postgres is controlled by pacemaker (using postgres 
resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't 
create missing directories and therefore postgres fails to start.

  The simplest solution for this issue is to have systemd recreate
  missing directories via /usr/lib/tmpfiles.d/postgresql.conf file.

  Currently only /var/run/postgresql and /var/log/postgresql are created
  using systemd-tmpfiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+subscriptions

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


[Desktop-packages] [Bug 1749729] Re: ares_library_init_mem missing from ares.h

2018-02-15 Thread Hans Joachim Desserud
** Tags added: xenial

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

Title:
  ares_library_init_mem missing from ares.h

Status in c-ares package in Ubuntu:
  New

Bug description:
  In summary:

  Looks like the manual page for c-ares is unclear as to the
  availability of the two functions it covers:
  ares_library_init
  ares_library_init_mem

  Secondly the #define only seems to cover availability of:
  ares_library_init

  I would suggest an update to the manual with the addition of 
  2. Another page/section for ares_library_init_mem another define
  for the ares_library_init_mem function which I am guess came in after 1.10.

  
  I am making calls to:

  ares_library_init_mem

  I am expecting it to compile

  However I am getting:

  undefined reference to `ares_library_init_mem'

  This code is further protected with:
  #ifdef CARES_HAVE_ARES_LIBRARY_INIT 

  see manual page text:
  AVAILABILITY
  This function was first introduced in c-ares version 1.7.0 along with the 
definition of preprocessor symbol CARES_HAVE_ARES_LIBRARY_INIT as an indication 
of the availability of this function. Its recursive behavior, which requires a 
matching number of calls to ares_library_cleanup() in order to deinitialize the 
library, is present since c-ares version 1.10.0. Earlier versions would 
deinitialize the library on the first call to ares_library_cleanup().

  Since the introduction of this function it is absolutely mandatory to
  call it for any Win32/64 program using c-ares.

  Non-Win32/64 systems can still use c-ares version 1.7.0 without
  calling ares_library_init due to the fact that currently it is nearly
  a do-nothing function on non-Win32/64 platforms at this point.

  Found inside ares_versions.h:

  #define ARES_VERSION_MAJOR 1
  #define ARES_VERSION_MINOR 10
  #define ARES_VERSION_PATCH 0
  #define ARES_VERSION ((ARES_VERSION_MAJOR<<16)|\
 (ARES_VERSION_MINOR<<8)|\
 (ARES_VERSION_PATCH))
  #define ARES_VERSION_STR "1.10.0"

  #if (ARES_VERSION >= 0x010700)
  #  define CARES_HAVE_ARES_LIBRARY_INIT 1
  #  define CARES_HAVE_ARES_LIBRARY_CLEANUP 1
  #else
  #  undef CARES_HAVE_ARES_LIBRARY_INIT
  #  undef CARES_HAVE_ARES_LIBRARY_CLEANUP
  #endif
  --
  System Info:
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  libc-ares-dev:
Installed: 1.10.0-3ubuntu0.2
Candidate: 1.10.0-3ubuntu0.2
Version table:
   *** 1.10.0-3ubuntu0.2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c-ares/+bug/1749729/+subscriptions

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


[Desktop-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade

2018-02-15 Thread Marco Bianchi
I do not have /etc/netplan directory on my ubuntu 14.04? Marco

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

Title:
  No network connectivity (NIC unmanaged) after upgrade

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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


[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-02-15 Thread Francis Ginther
** Tags added: id-59653842b438d4859259928d

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  In Progress

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

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

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

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

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

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


[Desktop-packages] [Bug 1749785] [NEW] package libxtst6 2:1.2.2-1 [modified: usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright] failed to install/upgrade: trying to overwrite

2018-02-15 Thread nahuel deniz
Public bug reported:

trying to run codewarrior for linux

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxtst6 2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright]
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 libxtst6: Install
 libxtst6: Configure
 libxtst6: Configure
 NULL: ConfigurePending
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Feb 15 16:35:12 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgTerminalLog:
 Preparing to unpack .../libxtst6_2%3a1.2.2-1_i386.deb ...
 Unpacking libxtst6:i386 (2:1.2.2-1) over (2:1.2.0-4ubuntu0.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libxtst6_2%3a1.2.2-1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libxtst6/copyright', which is 
different from other instances of package libxtst6:i386
DuplicateSignature:
 package:libxtst6:2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright]
 Unpacking libxtst6:i386 (2:1.2.2-1) over (2:1.2.0-4ubuntu0.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libxtst6_2%3a1.2.2-1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libxtst6/copyright', which is 
different from other instances of package libxtst6:i386
ErrorMessage: trying to overwrite shared '/usr/share/doc/libxtst6/copyright', 
which is different from other instances of package libxtst6:i386
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2017-09-19 (149 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=97b8ffe0-3938-4d6e-9f86-132c97712574 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: libxtst
Title: package libxtst6 2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libxtst6/copyright', which is different from other instances of 
package libxtst6:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: B85M-DS3H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-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: Thu Feb 15 15:02:36 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  package libxtst6 2:1.2.2-1 [modified:
  usr/share/doc/libxtst6/changelog.Debian.gz
  usr/share/doc/libxtst6/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libxtst6/copyright', which is
  

[Desktop-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

2018-02-15 Thread Francis Ginther
** Tags added: id-5a6f2ec772ac06a254f2247f

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in friendly-recovery package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in thermald package in Ubuntu:
  Invalid

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions

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


[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

2018-02-15 Thread Francis Ginther
** Tags added: id-5a57962350afc7d4aa391919

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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

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


[Desktop-packages] [Bug 1749785] Re: package libxtst6 2:1.2.2-1 [modified: usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright] failed to install/upgrade: trying to overwrite s

2018-02-15 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libxtst6 2:1.2.2-1 [modified:
  usr/share/doc/libxtst6/changelog.Debian.gz
  usr/share/doc/libxtst6/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libxtst6/copyright', which is
  different from other instances of package libxtst6:i386

Status in libxtst package in Ubuntu:
  New

Bug description:
  trying to run codewarrior for linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxtst6 2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright]
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libxtst6: Install
   libxtst6: Configure
   libxtst6: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Feb 15 16:35:12 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgTerminalLog:
   Preparing to unpack .../libxtst6_2%3a1.2.2-1_i386.deb ...
   Unpacking libxtst6:i386 (2:1.2.2-1) over (2:1.2.0-4ubuntu0.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libxtst6_2%3a1.2.2-1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libxtst6/copyright', which is 
different from other instances of package libxtst6:i386
  DuplicateSignature:
   package:libxtst6:2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright]
   Unpacking libxtst6:i386 (2:1.2.2-1) over (2:1.2.0-4ubuntu0.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libxtst6_2%3a1.2.2-1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libxtst6/copyright', which is 
different from other instances of package libxtst6:i386
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libxtst6/copyright', 
which is different from other instances of package libxtst6:i386
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2017-09-19 (149 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=97b8ffe0-3938-4d6e-9f86-132c97712574 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: libxtst
  Title: package libxtst6 2:1.2.2-1 [modified: 
usr/share/doc/libxtst6/changelog.Debian.gz usr/share/doc/libxtst6/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libxtst6/copyright', which is different from other instances of 
package libxtst6:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-DS3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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: Thu Feb 15 15:02:36 2018
  xserver.configfile: 

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2018-02-15 Thread Francis Ginther
** Tags added: id-5a7491099adc12270ee9c94d

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

Title:
  DNS domain search paths not updated when VPN started

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

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage 

[Desktop-packages] [Bug 1749779] [NEW] System freeze when going back and forth fullscreen mode with Firefox

2018-02-15 Thread Hadrien
Public bug reported:

Use Ubuntu 17.10
Open a Wayland session
Start Firefox
Press F11 repeatedly
--> The System freezes

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 20:09:27 2018
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-02 (135 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.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/1749779/+subscriptions

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


[Desktop-packages] [Bug 1512027] Re: open of device pixma:MX7600_... failed: invalid argument

2018-02-15 Thread Michael Foster
I too have the same issue with a Brother DCP-L2540DW on Ubuntu 16.04.

$ dpkg -l |grep libsane
ii  libsane:amd64   1.0.27+git20180209-xenial0  
 amd64API library for scanners
ri  libsane-common  1.0.27+git20180209-xenial0  
 amd64API library for scanners -- documentation and support 
files
ii  libsane-hpaio:amd64 3.16.3+repack0-1
 amd64HP SANE backend for multi-function peripherals


Output from simple-scan -d
[+0.00s] DEBUG: simple-scan.vala:674: Starting Simple Scan 3.20.0, PID=19090
[+0.00s] DEBUG: Connecting to session manager
[+0.10s] DEBUG: ui.vala:2032: Loading state from 
/home/mfoster/.cache/simple-scan/state
[+0.10s] DEBUG: ui.vala:1995: Restoring window to 684x996 pixels
[+0.10s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0.10s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0.10s] CRITICAL: gtk_event_controller_reset: assertion 
'GTK_IS_EVENT_CONTROLLER (controller)' failed
[+0.15s] DEBUG: scanner.vala:1447: sane_init () -> SANE_STATUS_GOOD
[+0.15s] DEBUG: scanner.vala:1453: SANE version 1.0.27
[+0.15s] DEBUG: scanner.vala:1514: Requesting redetection of scan devices
[+0.15s] DEBUG: scanner.vala:803: Processing request
[+0.20s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0.30s] DEBUG: ui.vala:2124: Saving state to 
/home/mfoster/.cache/simple-scan/state
[+3.30s] DEBUG: simple-scan.vala:404: Requesting scan at 150 dpi from device 
'(null)'
[+3.30s] DEBUG: scanner.vala:1560: Scanner.scan ("(null)", dpi=150, 
scan_mode=ScanMode.GRAY, depth=2, type=ScanType.ADF_BOTH, paper_width=2159, 
paper_height=2794, brightness=0, contrast=0)
[+6.39s] DEBUG: scanner.vala:338: sane_get_devices () -> SANE_STATUS_GOOD
[+6.39s] DEBUG: scanner.vala:350: Device: name="brother4:bus3;dev1" 
vendor="Brother" model="DCP-L2540DW" type="USB scanner"
[+6.39s] DEBUG: scanner.vala:803: Processing request
[+6.40s] DEBUG: scanner.vala:864: sane_open ("brother4:bus3;dev1") -> 
SANE_STATUS_INVAL
[+6.40s] WARNING: scanner.vala:868: Unable to get open device: Invalid argument
[+6.77s] DEBUG: ui.vala:2124: Saving state to 
/home/mfoster/.cache/simple-scan/state

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

Title:
  open of device pixma:MX7600_... failed: invalid argument

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Up until recently, I've been able to scan fine with my Canon Pixma
  MX7600. Then I upgraded to Ubuntu Wily and I've started getting:

  $ scanimage
  scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument

  The device pings and I can get to its HTTP port. Everything appears
  OK.

  If I run

  strace -f -s 256 -o /tmp/trace.txt scanimage

  the relevant output appears to be:

  socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204
  connect(204, {sa_family=AF_INET, sin_port=htons(8612),
  sin_addr=inet_addr("192.168.2.107")}, 16) = 0
  sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16
  select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257})
  recvfrom(204, 
"BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k",
  2048, 0, NULL, N
  ULL) = 32
  close(204)
  write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed:
  Invalid argument\n", 78) = 78

  It appears to me that the scanner is responding but the driver doesn't
  like the response. I'm running sane 1.0.14-11 and sane-utils
  1.0.25+git201505.

  WORKAROUND: Use the PPA from
  https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+subscriptions

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


[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

2018-02-15 Thread roots
You can make those settings permanent by editing

/etc/sysctl.conf

and adding the line

vm.dirty_bytes = 2

By issuing

$ sysctl -p

you won't have to reboot to use the new settings right away.

Anyway, for me it does not make any difference transfer speed wise when
copying files to USB with Ubuntu 16.04.3.


Cheers,
rooots.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)

2018-02-15 Thread Vladimir
** Tags added: xenial

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

Title:
  [Asus U36JC] Non-existent display detected in both intel driver and
  nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)

Status in nvidia-prime package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Precise:
  Triaged
Status in ubuntu-drivers-common source package in Precise:
  Invalid
Status in nvidia-prime source package in Trusty:
  Invalid
Status in ubuntu-drivers-common source package in Trusty:
  Fix Released

Bug description:
  SRU Request

  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  [Impact]
   * The ghost VGA output confuses lightdm and the gnome-settings-daemon making 
the system unusable.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check the output of the 
"xrandr -q" command
  - Expected: only the outputs that are actually connected will be marked 
as active.
  - Bad behavior: a non-existent VGA device will show up in the output.

  [Regression Potential]
   * Low, as it only disables CRT outputs in the nvidia driver.

  [Other Info]
   * N/A

  --

  There is a non existent display detected in both intel driver only and nvidia 
331 driver installation.
  The non existent display is "Unknown Display" shown in gnome-control-center 
--> display and "CRT-0" in nvidia-settings, and "VGA-0" in xrandr -q output.
  It will cause gdm failed to start. gnome-shell has some crazy layouts. 
lightdm will only occupy 2/3 of monitor in top left corner.
  I tested this in intel driver only environment. and nvidia-331 installation 
environment.
  My laptop is Asus U36JC. My monitor correct resolution is 1366x768.

  The following is the output of "xrandr -q" in gnome-shell with
  nvidia-331 installed:

  $ xrandr -q
  Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192
  VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm panning 1366x768+0+0
     680x384 60.0*+
     1366x768 60.0
     1360x768 60.0
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 
293mm x 165mm
     1366x768 60.0*+
     1360x768 59.8 60.0
     1024x768 60.0 60.0
     960x720 60.0
     928x696 60.1
     896x672 60.0
     960x600 60.0
     960x540 60.0
     800x600 60.0 60.3 56.2
     840x525 60.0 59.9
     800x512 60.2
     700x525 60.0
     640x512 60.0
     720x450 59.9
     640x480 60.0 59.9
     680x384 59.8 60.0
     576x432 60.1
     512x384 60.0
     400x300 60.3 56.3
     320x240 60.1
  VGA-1-0 disconnected (normal left inverted right x axis y axis)
  HDMI-1-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1-0 disconnected (normal left inverted right x axis y axis)
    1366x768 (0x46) 69.3MHz
  h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz
  v: height 768 start 773 end 782 total 785 clock 60.0Hz
    1360x768 (0x48) 72.0MHz
  h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz
  v: height 768 start 771 end 781 total 790 clock 60.0Hz
    680x384 (0x5c) 36.0MHz
  h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz
  v: height 384 start 385 end 390 total 395 clock 60.0Hz

  The following is the output of "xrandr -q" in lxde with nvidia-331
  installed:

  $ xrandr -q
  Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192
  VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y 
axis) 0mm x 0mm panning 1366x768+0+0
     680x38460.0 +
     1366x768   60.0
     1360x768   60.0
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 
293mm x 165mm
     1366x768   60.0*+
     1360x768   59.8 60.0
     1024x768   60.0 60.0
     960x72060.0
     928x69660.1
     896x67260.0
     960x60060.0
     960x54060.0
     800x60060.0 60.3 56.2
     840x52560.0 59.9
     800x51260.2
     700x52560.0
     640x51260.0
     720x45059.9
     640x48060.0 59.9
     680x38459.8 60.0
     576x43260.1
     512x38460.0
     400x30060.3 56.3
     320x24060.1
  VGA-1-0 disconnected (normal left inverted right x axis y axis)
  HDMI-1-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1-0 disconnected (normal left inverted right x axis y axis)
    1366x768 (0x46)   69.3MHz
  h: width  1366 start 1425 end 1464 

[Desktop-packages] [Bug 1705951] Re: Ubuntu 17.10 freezes soon after login.

2018-02-15 Thread Tim
After a number of updates I've retried a couple scenarios:
1) noveau driver and wayland : froze ~30 seconds after login (I clicked on 
terminal from the dock)
2) noveau driver and xorg : freezes from time to time.  System preferences 
never opens and sometimes freezes the entire system

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

Title:
  Ubuntu 17.10 freezes soon after login.

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  Edited 1: After some updates received, it freezes just after login,
  making any action impossible.

  
  I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 
17.10 and have had many problems with crashes and freezes. After login, the 
normal screen appears, the screen flashes and the top bar disappears, flashes 
again and appears normal, but frozen. Clicking again blinks back to the login 
screen. In order to access the system I was forced to install GNOME Classic. I 
noticed that in ubuntu 17.04 and ubuntu GNOME 16.04 it works normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.gpu:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0xff000e1b:0x1f000302
  .proc.driver.nvidia.agp.host-bridge:
   Host Bridge:  PCI device 1106:0308
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0x1f000a1b:0x0b02
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 8x
   Fast Writes:  Disabled
   SBA:  Enabled
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
   GCC version:  gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1)
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul 23 18:13:59 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.135, 4.11.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-07-17 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=7a3a72ab-cccf-4c14-97c3-1dcd85b1aca8 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:

  dmi.bios.date: 11/08/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5VDC-X
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jul 23 18:12:42 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputMicrosoft Basic Optical Mouse MOUSE, id 9
   inputAT Translated Set 2 

[Desktop-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-15 Thread Christopher M. Penalver
Pierre Wilch:

1)
>"So long I remember, this bug appeared before september 2017. No problem in 
>year 2016."

What version of Ubuntu were you using in 2016 when this was not reproducible?
 
2) To further root cause, could you please test for this problem by logging 
into a GNOME Flashback (Metacity) session via 
https://launchpad.net/ubuntu/+source/gnome-flashback and advise to the results?

** Description changed:

- Ubuntu 16.04.3 LTS, every updates done.
- 
  Conditions:
  - in the upper bar the display of the seconds must be enabled
-   (in my case the entire date-and-time is displayed, excepted the week 
number);
- - system has set himself automatically in sleep state after the selected delay
-   (in my case the option "lock the keyboard" is not enabled).
+   (in my case the entire date-and-time is displayed, excepted the week 
number);
+ - system is set to automatically go into sleep state after the selected delay
+   (in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
- Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...
+ Coming back to normal behavior needs to close and re-open windows.
  
  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
- When the seconds are not displayed in the upper bar there is no problem.
  
- Please do not blame me if xorg is not involved. A way to post had to be found.
- 'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
- --- 
+ WORKAROUND: When the seconds are not displayed in the upper bar there is
+ no problem.
+ 
+ ---
  .tmp.unity_support_test.0:
-  
+ 
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager

2018-02-15 Thread Vladimir
Xorg.0.log too

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055938/+files/Xorg.0.log

** Tags added: amd64 nvidia packaging

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

Title:
  Nvidia-prime after enable PRIME Synchronization  non-existent VGA
  device will show up in the output of xrandr and in Display manager

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  1) Ubuntu 16.04.3 LTS
  2) nvidia-prime 0.8.2
  3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

  4) When i enable PRIME Synchronization by set option options
  nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
  graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
  after reboot and here you go in xrandr --verbose there non-existent
  display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

   it's same bug as here https://bugs.launchpad.net/ubuntu/+source
  /nvidia-prime/+bug/1296020 but on LTS version of ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions

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


[Desktop-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen

2018-02-15 Thread Christopher M. Penalver
Steve Bainton:

1) Regarding your latest dmesg, you don't have any kernel crashes
(good). Could you please advise if there is any improvement on the 5
minute delay of booting to the login screen, even if minor?

2) Regarding your comment 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/comments/43 :
>"Ubuntu 14.04 works fine"

2a) To clarify, when did you test 14.04 on this hardware?

2b) Were you using Xubuntu or Kubuntu?

2c) Was this reproducible on any releases between 14.04 and 16.04?

2d) How long did it take to boot in 14.04?

3) To further root cause the boot process, you please post the results of the 
following terminal commands:
systemd-analyze
systemd-analyze blame
systemd-analyze critical-chain

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

** Tags removed: bios-outdated-1.90
** Tags added: latest-bios-1.90

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

Title:
  5 minute delay on booting to login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
  after choosing Ubuntu in grub2 menu, and after about 5 minutes the
  login screen is presented and from that point on everything seems to
  work as normal.

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr: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.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-02-15 Thread Jeremy Bicha
Khurshid, I apologize for changing this bug without adding a comment to
explain myself.

This bug has block-proposed set which is the only thing preventing those
NM addons to land in bionic. However, it also was preventing unrelated
bug fixes to gnome-shell to land in bionic today.

I will be uploading unity-control-center within a few days as part of
the gnoem-desktop3 transition so I removed that task temporarily. We
could add it back now if you want or we can wait for these transitions
to finish first.

But yes, it would be nice if unity-control-center would be updated to
not require libnm-glib in time for 18.04.

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager

2018-02-15 Thread Vladimir
And here my gpu-manager.log

** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055936/+files/gpu-manager.log

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

Title:
  Nvidia-prime after enable PRIME Synchronization  non-existent VGA
  device will show up in the output of xrandr and in Display manager

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  1) Ubuntu 16.04.3 LTS
  2) nvidia-prime 0.8.2
  3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

  4) When i enable PRIME Synchronization by set option options
  nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
  graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
  after reboot and here you go in xrandr --verbose there non-existent
  display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

   it's same bug as here https://bugs.launchpad.net/ubuntu/+source
  /nvidia-prime/+bug/1296020 but on LTS version of ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions

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


[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager

2018-02-15 Thread Vladimir
and in kern.log there always:

Feb 15 21:13:09 volnes-TWH kernel: [ 1284.817144] nvidia-modeset: WARNING: 
GPU:0: Unable to read EDID for display device VGA-0
Feb 15 21:13:20 volnes-TWH kernel: [ 1295.056345] nvidia-modeset: WARNING: 
GPU:0: Unable to read EDID for display device VGA-0

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

Title:
  Nvidia-prime after enable PRIME Synchronization  non-existent VGA
  device will show up in the output of xrandr and in Display manager

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  1) Ubuntu 16.04.3 LTS
  2) nvidia-prime 0.8.2
  3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

  4) When i enable PRIME Synchronization by set option options
  nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
  graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
  after reboot and here you go in xrandr --verbose there non-existent
  display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

   it's same bug as here https://bugs.launchpad.net/ubuntu/+source
  /nvidia-prime/+bug/1296020 but on LTS version of ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions

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


[Desktop-packages] [Bug 1749769] Re: Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager

2018-02-15 Thread Vladimir
And lspci

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+attachment/5055937/+files/lspci.txt

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

Title:
  Nvidia-prime after enable PRIME Synchronization  non-existent VGA
  device will show up in the output of xrandr and in Display manager

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  1) Ubuntu 16.04.3 LTS
  2) nvidia-prime 0.8.2
  3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

  4) When i enable PRIME Synchronization by set option options
  nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
  graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
  after reboot and here you go in xrandr --verbose there non-existent
  display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

   it's same bug as here https://bugs.launchpad.net/ubuntu/+source
  /nvidia-prime/+bug/1296020 but on LTS version of ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions

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


[Desktop-packages] [Bug 1749769] [NEW] Nvidia-prime after enable PRIME Synchronization non-existent VGA device will show up in the output of xrandr and in Display manager

2018-02-15 Thread Vladimir
Public bug reported:

Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
hardcoded in the BIOS. This leads the system into thinking that there is
actually one more active output than there really is.

1) Ubuntu 16.04.3 LTS
2) nvidia-prime 0.8.2
3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

4) When i enable PRIME Synchronization by set option options
nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
after reboot and here you go in xrandr --verbose there non-existent
display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

 it's same bug as here https://bugs.launchpad.net/ubuntu/+source/nvidia-
prime/+bug/1296020 but on LTS version of ubuntu

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 nvidia packaging xenial

** Attachment added: "xrandr.txt"
   https://bugs.launchpad.net/bugs/1749769/+attachment/5055935/+files/xrandr.txt

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

Title:
  Nvidia-prime after enable PRIME Synchronization  non-existent VGA
  device will show up in the output of xrandr and in Display manager

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices
  hardcoded in the BIOS. This leads the system into thinking that there
  is actually one more active output than there really is.

  1) Ubuntu 16.04.3 LTS
  2) nvidia-prime 0.8.2
  3) When i enable PRIME Synchronization by set option options nvidia_390_drm 
modeset from '0' to '1' in  /etc/modprobe.d/nvidia-graphics-drivers.conf and 
add option to grub nvidia-drm.modeset=1 and after reboot there only one active 
output in  xrandr --verbose is LVDS.

  4) When i enable PRIME Synchronization by set option options
  nvidia_390_drm modeset from '0' to '1' in  /etc/modprobe.d/nvidia-
  graphics-drivers.conf and add option to grub nvidia-drm.modeset=1 and
  after reboot and here you go in xrandr --verbose there non-existent
  display detected VGA-0 (Ghost screen with wrong resolution 1360x768).

   it's same bug as here https://bugs.launchpad.net/ubuntu/+source
  /nvidia-prime/+bug/1296020 but on LTS version of ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1749769/+subscriptions

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


[Desktop-packages] [Bug 1749766] [NEW] No libGLESv1_CM.so symlink present

2018-02-15 Thread a1batross
Public bug reported:

libGLESv1_CM.so is a common name for any GLESv1 implementation library.

I see, that libGL.so implements GLESv1, but software mostly don't
consider about this library naming. For example, SDL2 tries to find
GLESv1 implementation in libGLESv1_CM.so and it just shows me a error
like: "Could not initialize OpenGL / GLES library".

SDL2 isn't the only, there is many other possible code, which doesn't
know that libGL.so.1 implements GLES interface.

Meanwhile, libGLESv1_CM.so present only in nvidia-* driver package.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libglapi-mesa 17.2.4-0ubuntu1~17.10.2
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
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Feb 15 20:36:48 2018
Dependencies:
 gcc-7-base 7.2.0-8ubuntu3
 libc6 2.26-0ubuntu2.1
 libgcc1 1:7.2.0-8ubuntu3
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
InstallationDate: Installed on 2017-12-06 (71 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20354
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=b1945f5a-569f-437a-8562-73446b5a924e ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN91WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A5
dmi.board.vendor: LENOVO
dmi.board.version: 31900059WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN91WW:bd07/21/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20354
dmi.product.version: Lenovo Z50-70
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.4-0ubuntu1~17.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
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

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

Title:
  No libGLESv1_CM.so symlink present

Status in mesa package in Ubuntu:
  New

Bug description:
  libGLESv1_CM.so is a common name for any GLESv1 implementation
  library.

  I see, that libGL.so implements GLESv1, but software mostly don't
  consider about this library naming. For example, SDL2 tries to find
  GLESv1 implementation in libGLESv1_CM.so and it just shows me a error
  like: "Could not initialize OpenGL / GLES library".

  SDL2 isn't the only, there is many other possible code, which doesn't
  know that libGL.so.1 implements GLES interface.

  Meanwhile, libGLESv1_CM.so present only in nvidia-* driver package.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglapi-mesa 17.2.4-0ubuntu1~17.10.2
  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
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Feb 15 20:36:48 2018
  Dependencies:
   gcc-7-base 7.2.0-8ubuntu3
   libc6 2.26-0ubuntu2.1
   libgcc1 1:7.2.0-8ubuntu3
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
  InstallationDate: Installed on 2017-12-06 (71 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20354
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-02-15 Thread Balint Reczey
I'm working on removing old kernels in u-u and also make the similar
changes to update-manager: https://github.com/mvo5/unattended-
upgrades/pull/97

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  In Progress

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

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

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

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

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

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-02-15 Thread Khurshid Alam
Jeremy, why u-c-c is not affected any more? If we want to compile u-c-c
with lbnma we will still have to port it along other nertwork-manager-*
packages.

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

2018-02-15 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-shell - 3.26.2-0ubuntu3

---
gnome-shell (3.26.2-0ubuntu3) bionic; urgency=medium

  * debian/patches/ubuntu_panel_center_date_workarea.patch:
Align date entry relative to workarea. That way, title bars are
centered relative to date entry. (LP: #1716432)
  * :
Don't allow ubuntu mode extension to update
Ensure that no update is proposed or loaded if sideloaded (always
prefer system version) on the ubuntu session.
We want to ensure that the default code running is going through
our QA and security team process than being loaded from a 3rd
party website.
Also, that will enable us to upload newer versions on GNOME
extension website while still letting older ubuntu release versions
running expected extension version.
Note that the patch set is simplified with a hardcoded extension list
until https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1 is merged.
The patch set is too large otherwise to keep it maintainable as a distro
patch.
See also https://bugzilla.gnome.org/show_bug.cgi?id=789852.

 -- Didier Roche   Thu, 15 Feb 2018 15:25:18 +0100

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

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

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

Title:
  With dash to dock enabled, title in window is not centred aligned to
  clock when the window is maximised

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  With the dash-to-dock extension enabled and intelli-hide not enabled,
  the title of applications is not centre aligned with the gnome shell
  clock, as shown here [0].

  Possible solutions are
  1) When the window is maximised to align the title to the monitor centre not 
window centre
  2) When dash-to-dock is enabled move the clock to be slightly off monitor 
centre so it would line up with the window centre
  3) Ignore the alignment issue :-)

  0 - http://imgur.com/a/5cJ47

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

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


[Desktop-packages] [Bug 1749440] Re: Unable to send mail via Gnome-Gmail

2018-02-15 Thread Dave Steele
Confirmed. The main gnome-gmail application is unable to launch
(English). This does not happen with other launchers (file browser,
LibreOffice, ...).

As a work around, open the doc with another application, e.g. Chromium.

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

Title:
  Unable to send mail via Gnome-Gmail

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have set GNOME-Gmail as my default e-mail application in Ubuntu
  17.10. Now when I run Evince and select "Send to" (German "Senden an")
  nothing happens.

  I started Evince in a terminal which gave me the following error code:
  "/usr/bin/gnome-gmail: 3: exec: /usr/share/gnome-gmail/gnomegmail.py: 
Permission denied"

  Can anyone confirm this? Work-around or fix much appreciated! Thx

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

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


[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2018-02-15 Thread M Grmn
Might not be helpful. I edited my radeon.conf (which had "Detail") so I removed 
that.
Plus I had to chown {user}:{user} .Xauthority to be able to login (otherwise it 
would just kick me back to login screen) It helpt me logging in, but ofcourse 
not as it should.

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

Title:
  Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530

  ---

  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.4-0ubuntu2
  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
  CrashCounter: 1
  Date: Mon Feb  8 17:07:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffc9e34fc8) at libc-start.c:289
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  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:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Mon Feb  8 17:08:14 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 9847 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.17.3-2ubuntu2

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

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


  1   2   >