date:20171017

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

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

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

Title:
  keyboard autorepeat not happening when I hold down any key

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The failure to auto repeat happens in all terminal apps I've tried in
  Artful. If I open a virtual console, it looks like a phantom is typing
  ^@ about once per second. This prevents successfully typing a
  password, and is probably what is breaking autorepeat in the GUI
  terminals, although they don't show the ^@.  Gnome terminal and guake
  also can't stay scrolled up in the buffer for more than a second
  before popping back down to the bottom.

  This problem happens in the Ubuntu desktop or Gnome and it doesn't
  matter if I pick the xorg or default Wayland options. It happens under
  both the open source and proprietary nvidia drivers. It also happens
  with a newly created user with no home directory baggage.

  xev reports a constant stream of the following about the same frequency as 
the ^@ in console:
  KeyPress event, serial 62, synthetic NO, window 0x381,
  root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501),
  state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  
  If I boot into a recovery shell, the problem does _not_ appear. 

  My system was built with a fresh install of 17.04, installed my usual
  packages, then upgrade to 17.10 when the problem began. I'm certain it
  was not present in 17.04 for the few days before I upgraded. There
  were similar bugs reported a decade ago, but didn't help me.

  Expectation: Hold down any key in terminal window. After a moment, the
  letter should repeat until key is released.

  Actually: Key will repeat 0 or a few times, but stop repeating before
  I release the key.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct  9 10:43:56 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago)

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

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

[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key

2017-10-17 Thread Gunar Dierigen

I have the same problem, using a Lenovo Laptop.

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

Title:
  keyboard autorepeat not happening when I hold down any key

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The failure to auto repeat happens in all terminal apps I've tried in
  Artful. If I open a virtual console, it looks like a phantom is typing
  ^@ about once per second. This prevents successfully typing a
  password, and is probably what is breaking autorepeat in the GUI
  terminals, although they don't show the ^@.  Gnome terminal and guake
  also can't stay scrolled up in the buffer for more than a second
  before popping back down to the bottom.

  This problem happens in the Ubuntu desktop or Gnome and it doesn't
  matter if I pick the xorg or default Wayland options. It happens under
  both the open source and proprietary nvidia drivers. It also happens
  with a newly created user with no home directory baggage.

  xev reports a constant stream of the following about the same frequency as 
the ^@ in console:
  KeyPress event, serial 62, synthetic NO, window 0x381,
  root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501),
  state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  
  If I boot into a recovery shell, the problem does _not_ appear. 

  My system was built with a fresh install of 17.04, installed my usual
  packages, then upgrade to 17.10 when the problem began. I'm certain it
  was not present in 17.04 for the few days before I upgraded. There
  were similar bugs reported a decade ago, but didn't help me.

  Expectation: Hold down any key in terminal window. After a moment, the
  letter should repeat until key is released.

  Actually: Key will repeat 0 or a few times, but stop repeating before
  I release the key.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct  9 10:43:56 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago)

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

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

[Desktop-packages] [Bug 1723593] Re: HP2540 Printer installs Ok but does not print

2017-10-17 Thread John Rose

Can you make a cups-filters-core-drivers version 1.13.0-2 package for
16.04?

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

Title:
  HP2540 Printer installs Ok but does not print

Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  HP2540 All In One printer printed under Ubuntu 14.04. But does not
  print under Ubuntu 16.04. Have tried removing and installing printer
  without success. Tried installing hplip 3.16.3 package. Printer found
  Ok but did nothing when I tried to print test page. Printer Properties
  says that Printer State is "Processing - Processing page 1" but
  Document Print Status is "Processing - Not connected?". After a time,
  a window pops up from hplip saying that device is busy. lsusb shows
  "Bus 002 Device 010: ID 03f0:c211 Hewlett-Packard". Same problem with
  installing hplip 3.13.4 (and 3.17.9 from HP's web site) using
  instructions at:
  
https://sourceforge.net/projects/hplip/files/hplip/3.17.4/hplip-3.17.4.run/download?use_mirror=ufpr

  I've run "sudo hp-check": it gave error & warning about missing
  python3-dev & python3-notify2. So I installed them using Synaptic (it
  also brought in some other dependent packages). However, it gave
  "warning: Printer is not HPLIP installed. Printers must use the hp: or
  hpfax: CUPS backend for HP-Devices".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hplip 3.16.3+repack0-1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 14 11:08:42 2017
  InstallationDate: Installed on 2016-12-08 (309 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat:
   device for HP-Deskjet-2540-series: 
ipps://Desktop.local:631/printers/HP-Deskjet-2540-series
   device for Samsung-SCX-472x-Series: 
dnssd://Samsung%20SCX-472x%20Series%20(SEC001599D2245B)._printer._tcp.local/
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung-SCX-472x-Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Samsung-SCX-472x-Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=6de99e91-062b-4308-ae7d-79a3adc92f88 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

2017-10-17 Thread Bug Watch Updater

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

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  This is a minimal patch cherry-picked from GTK 3.22 git master (will be part 
of future GTK+ 3.22.25). I also pushed this patch to Debian unstable.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  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-shell/+bug/1724439/+subscriptions

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

[Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

Also tracking in:
https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
+ gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from 
ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from 
function_call()

** Description changed:

+ https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854
+ 
+ ---
+ 
  left virtual box to update win10 came back and got error message
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
-  PC (0x7feb2ed42d94) ok
-  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
+  PC (0x7feb2ed42d94) ok
+  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
+  destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
-  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ?? () from /usr/lib/libgjs.so.0
-  ?? () from /usr/lib/libgjs.so.0
+  meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
+  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ?? () from /usr/lib/libgjs.so.0
+  ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  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-shell/+bug/1724439/+subscriptions

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

[Desktop-packages] [Bug 1724447] [NEW] /usr/bin/gnome-shell:11:meta_window_get_monitor:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

2017-10-17 Thread errors.ubuntu.com bug bridge

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

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.26.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 
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: artful precise saucy trusty vivid wily 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/1724447

Title:
  /usr/bin/gnome-
  
shell:11:meta_window_get_monitor:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

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.26.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 
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/1724447/+subscriptions

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-10-17 Thread PeterPall

** Description changed:

  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.
  
  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27
  
  This appears to be no bigger change than any ordinary new version of the
  library.
  
  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.
  
  Therefore, adding Provides: libsane seems reasonable here.
  
  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.
  
  It won't install before this SRU because it Depends: libsane
  
  Regression Potential
  
- The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.
+ The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless. 
  
  It doesn't seem like adding the Provides will make things any worse for
- third-party drivers but it has a good chance of making things better for
- some.
+ third-party drivers but it has a goodme chance of making things better
+ for some.
  
  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  This appears to be no bigger change than any ordinary new version of
  the library.

  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.

  Therefore, adding Provides: libsane seems reasonable here.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless. 

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1724447] Re: /usr/bin/gnome-shell:11:meta_window_get_monitor:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

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

** This bug has been marked a duplicate of bug 1724439
   gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_window_get_monitor:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

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.26.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 
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/1724447/+subscriptions

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

[Desktop-packages] [Bug 1724437] Re: wrong shortcut created on Add to Favorites action

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

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

Title:
  wrong shortcut created on Add to Favorites action

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

Bug description:
  I installed Firefox Developer edition to `/opt/firefox` and ran it
  from a terminal with `/opt/firefox/firefox`.  With no Favorite added
  for any Firefox on my dock and only the Developer version of Firefox
  running, I right click on the Firefox icon on the dock and select Add
  to Favorites.  I close out of Firefox Developer version.  I click on
  the Favorite that was just added to the dock.  Firefox non-Developer
  version is started.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7
  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: ubuntu:GNOME
  Date: Tue Oct 17 20:47:15 2017
  InstallationDate: Installed on 2017-10-03 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1724437/+subscriptions

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  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-shell/+bug/1724439/+subscriptions

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

[Desktop-packages] [Bug 1724375] Re: chromium-browser crashed with SIGSEGV

2017-10-17 Thread Olivier Tilloy

Thanks for the report Sebastian.
Can you please describe what you were doing when chromium crashed?
Can you reliably reproduce the crash?

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9a
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1724375/+subscriptions

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-10-17 Thread PeterPall

In the above I didn't copy-and-paste the additional info that about 100
packages can be autoremoved after removing libsane1 because after
removing all applications that depend on gtk many libraries are unused.

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  This appears to be no bigger change than any ordinary new version of
  the library.

  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.

  Therefore, adding Provides: libsane seems reasonable here.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a good chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions

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

[Desktop-packages] [Bug 1724443] Re: udisksd crashed with SIGSEGV in g_mutex_lock() I have got a warning box for days, that program " " has crashes, or script " " has stopped at line num 0, or so

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

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 #1707451, 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/1724443/+attachment/4974427/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1707451
   udisksd crashed with SIGSEGV in g_mutex_lock()

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock() I have got a warning
  box for days, that program "" has crashes, or script "   " has
  stopped at line num 0, or somthing has broken do now we will do a
  stack trace, which results in a string of blank spaces... This is at
  boot, and they all seem to relate to launching & running the welcome
  screen, but it mostly does launch & run these days.

Status in udisks2 package in Ubuntu:
  New

Bug description:
  udisksd crashed with SIGSEGV in g_mutex_lock() I have got a warning box for 
days, that program "" has crashes, or script "   " has stopped at line num 
0, or somthing has broken do now we will do a stack trace, which results in a 
string of blank spaces... This is at boot, and they all seem to relate to 
launching & running the welcome screen, but it mostly does launch & run these 
days.
  repetition does make the heart grow fonder.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu2
  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
  Date: Wed Oct 18 10:46:36 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-09-27 (20 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170829.1)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cb669e16-5d97-418e-be69-88e013af883b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7f6f3a0a35b5 :   lock xadd 
%eax,(%rdi)
   PC (0x7f6f3a0a35b5) ok
   source "%eax" ok
   destination "(%rdi)" (0x75736f6e2c777220) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 152731] Re: [regression] gnome-power-manager laptop backlight not working on VAIO VGN-FSxxx

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

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

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

Title:
  [regression] gnome-power-manager laptop backlight not working on VAIO
  VGN-FSxxx

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

Bug description:
  Binary package hint: gnome-power-manager

  Laptop Sony VAIO VGN-FS620/W

  Last working: Gutsy Beta CD

  Problem: In gnome-power-manager it no longer allows the control of the
  brightness by either AC power or battery power.

  When problem happened: Doing an update from the Beta CD to what was
  available on Sunday October 14th 2007. After that the screen was on
  it's lowest dim setting, and none of the sliders would change the
  brightness. It is as if the control panel is still there, but is no
  longer sending a signal to the right place that it used to in the beta
  cd.

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

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

[Desktop-packages] [Bug 1711745] Re: constantly running scripts, lagging page load time

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

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

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

Title:
  constantly running scripts, lagging page load time

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox has been running slowly, and a script is being run several
  times daily that slows the system.

  ProblemType: Bug
  DistroRelease: Kali 2017.1
  Package: firefox 55.0~b11+build1-0ubuntu0.17.04.1 [origin: unknown]
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shiningdove   3157 F pulseaudio
   /dev/snd/controlC0:  shiningdove   3157 F pulseaudio
  BrokenPermissions: saved-telemetry-pings/2d43099a-baa5-4318-bebd-6db945e38bc4 
(0o600, wrong owner)
  BuildID: 20170720221345
  Channel: beta
  CurrentDesktop: Unity:Unity7
  Date: Fri Aug 18 15:24:13 2017
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-03-23 (147 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-3c205d14-24ff-41ab-b71d-0d4ac0170803
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/vendor-gre.js
   /usr/lib/firefox/defaults/pref/channel-prefs.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=55.0/20170720221345 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 017HYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/06/2015:svnDellInc.:pnInspiron5758:pvr01:rvnDellInc.:rn017HYC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5758
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1724442] [NEW] Search feature returns seemingly unrelated results

2017-10-17 Thread Scott Palmer

Public bug reported:

This bug should actually be linked to ubuntu software, not gnome
software.


Search for "libre"

1. yacas 
2. wormhole
.
.
.

I can't even find "libre" in the package name, nor the description of
the first few pages of results.

Way down on the list is "libreoffice" but even it isn't grouped with
"LibreOffice Writer", "LibreOffice Calc" which are several pages lower.

What is the order of results?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-software 3.26.1-0ubuntu1
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: ubuntu:GNOME
Date: Tue Oct 17 21:10:29 2017
InstallationDate: Installed on 2017-10-03 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.1-0ubuntu1
PackageArchitecture: all
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Search feature returns seemingly unrelated results

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This bug should actually be linked to ubuntu software, not gnome
  software.

  
  Search for "libre"

  1. yacas 
  2. wormhole
  .
  .
  .

  I can't even find "libre" in the package name, nor the description of
  the first few pages of results.

  Way down on the list is "libreoffice" but even it isn't grouped with
  "LibreOffice Writer", "LibreOffice Calc" which are several pages
  lower.

  What is the order of results?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-software 3.26.1-0ubuntu1
  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: ubuntu:GNOME
  Date: Tue Oct 17 21:10:29 2017
  InstallationDate: Installed on 2017-10-03 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

2017-10-17 Thread PeterPall

@dino99: You cannot sqitch the zesty version any more. At least if you
want your computer have a working graphical user interface: lib colord
depends in libsane1 - and colord on libcolord. And gnome on colord:

gunter@Marius:~$ sudo apt-get remove libcolord2 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  emacs25-lucid xaw3dg
Suggested packages:
  emacs25-common-non-dfsg
The following packages will be REMOVED:
  apport-gtk apturl bamfdaemon baobab brasero brasero-cdrkit cairo-dock
  cairo-dock-core cairo-dock-plug-ins
  cairo-dock-plug-ins-dbus-interface-python cairo-dock-plug-ins-integration
  caribou cheese chrome-gnome-shell classicmenu-indicator colord compiz
  compiz-gnome dconf-editor easytag emacs24 emacs25 evince
  evolution-data-server evolution-data-server-online-accounts file-roller
  firefox frei0r-plugins gcr gedit gir1.2-appindicator3-0.1 gir1.2-caribou-1.0
  gir1.2-clutter-1.0 gir1.2-gcr-3 gir1.2-gdl-3 gir1.2-gnomebluetooth-1.0
  gir1.2-gnomedesktop-3.0 gir1.2-gspell-1 gir1.2-gtk-3.0 gir1.2-gtksource-3.0
  gir1.2-gtkspell3-3.0 gir1.2-gweather-3.0 gir1.2-mutter-1 gir1.2-nautilus-3.0
  gir1.2-nmgtk-1.0 gir1.2-peas-1.0 gir1.2-rb-3.0 gir1.2-totem-1.0
  gir1.2-vte-2.91 gir1.2-webkit2-4.0 gir1.2-wnck-3.0 gjs gkbd-capplet
  gnome-bluetooth gnome-control-center gnome-disk-utility gnome-font-viewer
  gnome-getting-started-docs gnome-getting-started-docs-de gnome-keyring
  gnome-online-accounts gnome-power-manager gnome-screensaver gnome-screenshot
  gnome-session gnome-session-bin gnome-session-wayland gnome-settings-daemon
  gnome-shell gnome-software gnome-software-plugin-snap gnome-system-log
  gnome-system-monitor gnome-system-tools gnome-terminal gnome-tweak-tool
  gnome-user-docs gnome-user-guide gnome-user-share gstreamer1.0-clutter-3.0
  gstreamer1.0-plugins-bad gtk3-engines-unico gucharmap gufw handbrake ibus
  ibus-gtk3 indicator-application indicator-printers language-selector-gnome
  libappindicator3-1 libavahi-ui-gtk3-0 libbrasero-media3-1 libcanberra-gtk3-0
  libcanberra-gtk3-module libcaribou0 libcheese-gtk25 libcheese8
  libclutter-1.0-0 libclutter-gst-3.0-0 libclutter-gtk-1.0-0 libcolord-gtk1
  libcolord2 libcolorhug2 libevdocument3-4 libevview3-3 libgail-3-0
  libgcr-ui-3-1 libgdl-3-5 libgdl-3-dev libgjs0g libgldi3 libgnome-bluetooth13
  libgnome-desktop-3-12 libgnomekbd8 libgoa-backend-1.0-1 libgspell-1-1
  libgspell-1-dev libgtk-3-0 libgtk-3-bin libgtk-3-dev libgtkmm-3.0-1v5
  libgtkmm-3.0-dev libgtksourceview-3.0-1 libgtksourceview-3.0-dev
  libgtkspell3-3-0 libgtkspell3-3-dev libgtkspellmm-3.0-0v5
  libgtkspellmm-3.0-dev libgucharmap-2-90-7 libgweather-3-6 libido3-0.1-0
  libindicator3-7 libmetacity1 libmutter-1-0 libnautilus-extension1a
  libnm-gtk0 libnma0 libopencv-calib3d3.1 libopencv-contrib3.1
  libopencv-features2d3.1 libopencv-highgui3.1 libopencv-objdetect3.1
  libopencv-stitching3.1 libopencv-videostab3.1 libpeas-1.0-0
  libreoffice-avmedia-backend-gstreamer libreoffice-gnome libreoffice-gtk3
  librhythmbox-core10 librsvg2-bin libtimezonemap1 libtotem0 libunique-3.0-0
  libunity-settings-daemon1 libvte-2.91-0 libwebkit2gtk-4.0-37
  libwebkit2gtk-4.0-37-gtk2 libwebkit2gtk-4.0-dev libwebkitgtk-3.0-0
  libwnck-3-0 libyelp0 lightdm-gtk-greeter meld metacity mousetweaks mutter
  nautilus nautilus-extension-brasero network-manager-gnome
  network-manager-openvpn-gnome notify-osd pinentry-gnome3 policykit-1-gnome
  python-nautilus python3-aptdaemon.gtk3widgets qt5-gtk-platformtheme
  redshift-gtk seahorse seahorse-daemon shotwell software-properties-gtk
  soundconverter ssh-askpass-gnome system-config-printer
  system-config-printer-common thunderbird thunderbird-locale-de
  thunderbird-locale-en thunderbird-locale-en-gb thunderbird-locale-en-us
  totem totem-plugins transmission-gtk ubuntu-docs ubuntu-release-upgrader-gtk
  ubuntu-software update-manager update-notifier usb-creator-gtk vino weston
  xdg-user-dirs-gtk xiphos yelp zenity
The following NEW packages will be installed:
  emacs25-lucid xaw3dg
0 upgraded, 2 newly installed, 206 to remove and 0 not upgraded.
Need to get 3.650 kB of archives.
After this operation, 673 MB disk space will be freed.
Do you want to continue? [Y/n] 

This basically means that you currently need two Ubuntu installations:
One you can scan with - and one to do the rest of the work.

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.

  libsane 1.0.25 in zesty

[Desktop-packages] [Bug 1724011] Re: gnome-control-center crashed with SIGSEGV

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

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

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  added google account, then switched to new tab in settings.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  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: ubuntu:GNOME
  Date: Mon Oct 16 19:35:17 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7f087bd3fb3b:mov0x8(%rax),%rax
   PC (0x7f087bd3fb3b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  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/1724011/+subscriptions

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

[Desktop-packages] [Bug 1724431] Re: gnome-control-center crashed with SIGSEGV after reducing items retrieved via google account

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

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 #1724011, 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/1724431/+attachment/4974382/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724011
   gnome-control-center 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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724431

Title:
  gnome-control-center crashed with SIGSEGV after reducing items
  retrieved via google account

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

Bug description:
  I had added a google account which then adds all subfunctions. Through
  the calendar app I adjusted the account settings to a subset. This
  completed but then resulted in a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 20:20:51 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
  ProcCmdline: /usr/bin/gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7ff33d18ab3b:mov0x8(%rax),%rax
   PC (0x7ff33d18ab3b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  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/1724431/+subscriptions

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

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

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with signal 5
+ gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from 
st_widget_allocate()

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

Title:
  gnome-shell crashed with signal 5 in clutter_box_layout_allocate()
  from st_widget_allocate()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was trying to unlock my screen which took a while and then I
  received this crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 17 11:18:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2013-01-16 (1735 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  ProcCmdline: gnome-shell --sm-client-id 
10aeea5677451824be150033639041251008268
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev 
sambashare sbuild sudo

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

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

[Desktop-packages] [Bug 1724098] Re: For some BRIEF time, SOUND ICON in tray is very BIG in size

... or if the problem is brief then photo/video.

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

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1724098] Re: For some BRIEF time, SOUND ICON in tray is very BIG in size

Thanks. Can you also provide a screenshot? I wonder if this is related
to the giant icon rendering bug 1718238.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1724098

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1724295] Re: All Apps screen aren't removed from overview when there's no apps to show

I feel this is one of the areas that was improved in Gnome 3.26. So I
suggest waiting a day or so and then Ubuntu 17.10 will be officially
released. Download 17.10, and boot up a live session. Does the bug still
exist there?

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

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

Title:
  All Apps screen aren't removed from overview when there's no apps to
  show

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After install the Ubuntu 16 with Gnome, I opened the Activities
  screen. I pressed the button "Show All Apps". Then I pressed the
  button "Show All Apps" again. The All Apps screen did'nt close. Then,
  I closed the overview and opened it again. The All Apps Screen was
  still there behind the opened windows.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.3-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 17 14:15:22 2017
  InstallationDate: Installed on 2017-04-17 (183 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gdm3
  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/1724295/+subscriptions

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

[Desktop-packages] [Bug 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change

Yes, you can get a stack trace without debug packages. It's just going
to be much less detailed, and risks not showing enough information. But
we would welcome a stack trace (or multiple traces to ensure you're
looking in the right spot), even without debug info.

** Summary changed:

- System freeze after docking and display configuration change
+ gnome-shell frozen and using 100% CPU after docking and display configuration 
change

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

Title:
  gnome-shell frozen and using 100% CPU after docking and display
  configuration change

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have been having regular system freezes after switching from using
  my laptop stand-alone to waking it up on a docking station with an
  external monitor. I have seen this using two identical docking station
  plus monitor combinations. I am still trying to find a pattern.  I was
  able to ssh in and use apport to save this bug information.  The
  gnome-shell process was hung at 100% CPU utilisation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: ubuntu:GNOME
  Date: Tue Oct 17 15:56:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['gnome-terminal']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (504 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago)

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

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

[Desktop-packages] [Bug 1724424] [NEW] Problem with video after suspending the machine and wake it up

2017-10-17 Thread Julian A. Viola

Public bug reported:

The bug I found is this, I suspend the machine, and when I wake it up,
the display doesn't work correctly or doesn't display the video or
things correctly. It looks like if I hadn't the display driver in that
moment. It looks like with a wrong resolution, a lower resolution,
things looks bigger... It happens all the times when I wake it up with
the mouse. I've just wake it up with the keyboard and didn't happen, but
it happens almost all the times... All the times when I did wake it up
with the mouse.

The display gets fixed after entering to the Display configurations or
Appearance, by right-clicking on the desktop and entering to Change
Wallpaper and it looks good after that, but displays some things wrong
sometimes. But when entering to Appearance, the displays goes black and
then it looks good.

I don't know if the problem is with xorg, or with the display driver or
related to another package.

My OS is Ubuntu 16.04.03, my graphics card is a NVIDIA GT610 and I am
using the proprietary driver of NVIDIA.

Maybe in the picture attached you cannot see well the problem. I wanted
to attached two images, but I can't.

Let me know, if you need more information or if I can help with
something.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog: [[0m[0;31m* [0m] (1 of 10) A start job is running fo...for SMP 
systems (31s / 5min 15s)
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Oct 17 22:47:35 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-93-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-97-generic, x86_64: installed
 nvidia-375, 375.66, 4.4.0-93-generic, x86_64: installed
 nvidia-375, 375.66, 4.4.0-97-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2013-07-06 (1564 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=4e6f7004-c9c6-4390-98ff-6e9442080b31 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A88-V EVO
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.:bvr1202:bd03/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
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

[Desktop-packages] [Bug 1724295] [NEW] All Apps screen aren't removed from overview when there's no apps to show

You have been subscribed to a public bug:

After install the Ubuntu 16 with Gnome, I opened the Activities screen.
I pressed the button "Show All Apps". Then I pressed the button "Show
All Apps" again. The All Apps screen did'nt close. Then, I closed the
overview and opened it again. The All Apps Screen was still there behind
the opened windows.

---

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gdm3 3.18.3-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 17 14:15:22 2017
InstallationDate: Installed on 2017-04-17 (183 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: activities gnome gnome-shell overview ubuntu
-- 
All Apps screen aren't removed from overview when there's no apps to show
https://bugs.launchpad.net/bugs/1724295
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)

Keep an eye on bug 1720684, where upstream now has a fix that might
help.

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

Title:
  Bluetooth audio stuck in A2DP profile ([pulseaudio] module-
  bluez5-device.c: Refused to switch profile to headset_head_unit: Not
  connected)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

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

[Desktop-packages] [Bug 1723544] Re: workspace to dock disabled after suspend

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

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

Title:
  workspace to dock disabled after suspend

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  affects gnome shell ubuntu 17.10 Beta

  until now after suspend Workspace to dock is missing but restarting X brought 
it back
  last time restarting X in all these ways DID NOT WORK: Method 1-4
  Method 1
  ‣ Ctl+Alt+F1 to exit, and Ctl+Alt+F3 to bring one back
  • Method 2 
  • sudo /etc/init.d/gdm3 restart,   or
  • Method 3
  • systemctl restart gdm.service,   or
  • Method 4
  • sudo service gdm3 restart

  Method 5
  • dbus-send --type=method_call --print-reply --dest=org.gnome.Shell 
/org/gnome/Shell org.gnome.Shell.Eval string:'global.reexec_self()'

  or a restart Does Work

  Odd?

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

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

[Desktop-packages] [Bug 1720083] Re: Profile defaults to headset mode instead of a2dp

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

Upstream has completed a fix for this, this week. It's linked to LP bug
1720684.

** This bug has been marked a duplicate of bug 1720684
   Bluetooth speaker used the HSP/HFP profile by default rather than the 
higher-quality A2DP profile

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

Title:
  Profile defaults to headset mode instead of a2dp

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using 17.10

  # Reproduce:

  1. Pair bluetooth headphone with mic (like Bose QC35)
  2. Play music

  # What I get:

  Music is very bad quality because the "headset head unit (HSP/HFP)"
  profile is chosen by default. Switching to the "High Fidelity Playback
  (A2DP Sink)" profile fixes the audio.

  # What I expect:

  Music is good quality because A2DP profile is chosen by default.

  # Why should A2DP be chosen by default?

  1. Given that HSP quality is so low, we can assume that the primary use for 
bluetooth headsets is to listen to music. As a result, setting it to A2DP by 
default will give good experience for the biggest amount of use-cases.
  2. Bluez supports automatic switching from A2DP to HSP when a program 
identifies a recording stream as "Phone" (or optionally when it doesn't 
identify the recording stream with PulseAudio 11 [1]) so in many cases, it's 
not even needed to manually switch to HSP.

  [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/

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

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

[Desktop-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile

** Also affects: pulseaudio via
   https://bugs.freedesktop.org/show_bug.cgi?id=103058
   Importance: Unknown
   Status: Unknown

** Tags added: a2dp

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

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

Title:
  Bluetooth speaker used the HSP/HFP profile by default rather than the
  higher-quality A2DP profile

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

Bug description:
  Kubuntu 17.04
  Bluetooth device: 
https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1
 (itentifies itself as "C6")

  The above Bluetooth speaker paired and started streaming audio
  perfectly in Kubuntu 17.04. But the audio quality was poor, because
  the default audio profile was the low-quality HSP/HFP one. When I
  switched it to the A2DP profile, it sounded perfect again.

  Can we make A2DP the default playback profile for Bluetooth audio
  devices?

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

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

[Desktop-packages] [Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login

Tessa,

I know it's confusing but the way LaunchPad works is that you may still
be suffering from a bug even after it shows as "Fix Released". This is
because the fix has been released in the latest Ubuntu 17.10 (only). As
you are using Ubuntu 17.04 you don't yet have the fix, we know.

I have nominated 17.04 to receive the fix for you, but it is not always
guaranteed that a fix will get backported to previous releases. Still,
the right place to discuss the problem is here.

Only if someone still experiences the problem in 17.10 should a new
separate bug be opened.

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

Title:
  System goes to sleep with external monitor and lid closed after login

Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Artful:
  Invalid
Status in gnome-settings-daemon source package in Artful:
  Fix Released
Status in gnome-shell source package in Artful:
  Invalid

Bug description:
  Using a laptop with lid closed and an external monitor, you can boot.
  Bios will show on the external monitor, as well as gdm when boot is finished.
  You can then choose a user and type in your password, which is accepted.
  But then, system goes to sleep (as the lid is cloesd I guess).

  Going out of sleep with the power button shows the gnome shell.

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

This is for Xenial.

** Patch added: "pulseaudio_8.0-0ubuntu3.5.debdiff"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718824/+attachment/4974334/+files/pulseaudio_8.0-0ubuntu3.5.debdiff

** Tags added: ubuntu-sponsors

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

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

Status in HWE Next:
In Progress
Status in pulseaudio package in Ubuntu:
Fix Committed

Bug description:
SRU Document:

[Impact]

If users use the latest Dell USB Dock, e.g. TB16, they will found the
analog audio (lineout jack) can't work under ubuntu linux

[Test Case]

After applying the fix, users can play sound via analog speaker or
lineout freely. Without the fix, users can't play sound from lineout
jack.

[Regression Potential]

No any possibility to introduce regression since this fix just adding
a new dock's support, it does not change any existing code.

[Other Info]

No more info here

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

Expected results: Line-out port can work

Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

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

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1723378, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1723378
   gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from 
_st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from 
st_icon_update_shadow_pipeline()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Very likely a dupe of a previously reported bug, but its' not showing
  up publicly yet.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Oct 17 15:39:47 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-08-03 (1170 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () at /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: Upgraded to artful on 2017-09-29 (18 days ago)
  UserGroups: adm cdrom dip docker kvm libvirtd lpadmin lxd plugdev sambashare 
sudo video www-data

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

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

[Desktop-packages] [Bug 1724363] Re: xwayland gnome-shell crashes on 17.10

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

Yes, when Xwayland crashes gnome-shell commits suicide because it
doesn't yet know how to survive without Xwayland or how to restart it.

That is what your log shows and that is generally bug 1505409 or bug
1556601. Possibly others too, but they will all have the same fix.

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

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

Title:
  xwayland gnome-shell crashes on 17.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta, my Wayland used to work now i get this error
  message

  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: Failed to apply DRM 
plane transform 0: Permission denied
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: Fatal server 
error:
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE) 
wl_drm@4: error 0: authenicate failed
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: X Wayland crashed; 
aborting
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session[1253]: 
gnome-session-binary[1253]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Oct 16 08:58:01 ExColo-Galago-Pro gdm-launch-environment][1042]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Starting with guard context 
"default"
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Bootstrapped 80%: Connecting to 
the Tor network
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Signaled readiness to systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: ubuntu:GNOME
  Date: Tue Oct 17 13:19:40 2017
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  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/1724363/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

debdiff for Artful and Zesty


** Patch added: "pulseaudio_10.0-2ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718824/+attachment/4974320/+files/pulseaudio_10.0-2ubuntu4.debdiff

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

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

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

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

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

2017-10-17 Thread Yuan-Chen Cheng

** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

** Changed in: modemmanager (Ubuntu)
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

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

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

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

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

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

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

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

  # environment information:

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

   * uname -r: 4.4.0-73-generic

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

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

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

** Description changed:

  SRU Document:
  
  [Impact]
  
- If users use the latest Dell USB Dock, e.g. TD16, they will found the
+ If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux
  
  [Test Case]
  
  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.
  
  [Regression Potential]
  
  No any possibility to introduce regression since this fix just adding a
  new dock's support, it does not change any existing code.
  
  [Other Info]
-  
+ 
  No more info here
- 
- 
  
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings
  
  Expected results: Line-out port can work
  
  Actual results: Line-out port not work

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

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

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

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

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

** Description changed:

+ SRU Document:
+ 
+ [Impact]
+ 
+ If users use the latest Dell USB Dock, e.g. TD16, they will found the
+ analog audio (lineout jack) can't work under ubuntu linux
+ 
+ [Test Case]
+ 
+ After applying the fix, users can play sound via analog speaker or
+ lineout freely. Without the fix, users can't play sound from lineout
+ jack.
+ 
+ [Regression Potential]
+ 
+ No any possibility to introduce regression since this fix just adding a
+ new dock's support, it does not change any existing code.
+ 
+ [Other Info]
+  
+ No more info here
+ 
+ 
+ 
  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings
  
  Expected results: Line-out port can work
  
  Actual results: Line-out port not work

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

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

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TD16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]
   
  No more info here



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

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

Stephan Fabel, as reports to package xorg (Ubuntu) is used as a staging
ground, and you have tested the latest version of Ubuntu, I'll mark this
Triaged so a developer may review, and further review.

Also, it would be helpful to have a camera picture of the corruption, or
screencast as this can help in root causing.

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

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1724413] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  itdoesntResolve to update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Tue Oct 17 19:17:46 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-17  19:17:34
   Commandline: apt-get autoremove
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-09-01 (777 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724413] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-10-17 Thread Guillermo Wusterhaus

Public bug reported:

itdoesntResolve to update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Tue Oct 17 19:17:46 2017
DpkgHistoryLog:
 Start-Date: 2017-10-17  19:17:34
 Commandline: apt-get autoremove
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-09-01 (777 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  itdoesntResolve to update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Tue Oct 17 19:17:46 2017
  DpkgHistoryLog:
   Start-Date: 2017-10-17  19:17:34
   Commandline: apt-get autoremove
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-09-01 (777 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

** Description changed:

- When I connect my laptop to my AOC E2775SJ Monitor via a DisplayLink
- based device (Wavlink universal USB 3.0 docking station
- https://www.wavlink.com/en/product/150 WL-UG39DK1V) the mouse icon
- flickers and vanishes for several minutes, but remains active.
+ When I connect my laptop to my DisplayLink based device with USB
+ (Wavlink universal USB 3.0 docking station
+ https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
+ Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
+ Only if the mouse is on the laptop monitor, it can vanish for several
+ minutes, but remains active.
+ 
+ Animations/overlays or typing inside a Chrome window causes the mouse
+ pointer to flicker more often. If there is no interaction or animation,
+ the mouse pointer remains static and drawn.
  
  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor
+ 
+ This issue doesn't happen if I don't connect my laptop to an external
+ monitor via the Wavlink device.
  
  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.
  
  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver

[Desktop-packages] [Bug 1548720] Re: nautilus crashed with SIGSEGV in ffi_call_unix64()

2017-10-17 Thread Guybrush88

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

** Description changed:

  I got this right after closing a .avi video
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 23 10:42:34 2016
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1446050710
  InstallationDate: Installed on 2015-10-08 (137 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: nautilus -n
- ProcCwd: /home/davide
+ ProcCwd: /home/username
  ProcEnviron:
-  LANGUAGE=it_IT
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=it_IT.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=it_IT
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=it_IT.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7feef4fc4c33:mov(%rcx),%rdi
-  PC (0x7feef4fc4c33) ok
-  source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
-  destination "%rdi" ok
+  Segfault happened at: 0x7feef4fc4c33:mov(%rcx),%rdi
+  PC (0x7feef4fc4c33) ok
+  source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
+  destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
-  ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
-  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
+  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to wily on 2015-10-23 (122 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  nautilus crashed with SIGSEGV in ffi_call_unix64()

Status in totem package in Ubuntu:
  New

Bug description:
  I got this right after closing a .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 23 10:42:34 2016
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1446050710
  InstallationDate: Installed on 2015-10-08 (137 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: nautilus -n
  ProcCwd: /home/username
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feef4fc4c33:mov(%rcx),%rdi
   PC (0x7feef4fc4c33) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to wily on 2015-10-23 (122 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1724404] [NEW] VGA Driver

2017-10-17 Thread eduardotomassi

Public bug reported:

I might be having issues with the display driver. the issue that i
currently have is the fact that the fan is constantly running at max
speed

this is the lspci output
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

and also i have xserver-xorg-video-intel installed at newest version

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Oct 17 19:51:39 2017
InstallationDate: Installed on 2017-10-17 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Description changed:

  I might be having issues with the display driver. the issue that i
- currently has is the fact that the fun is constantly running at max
+ currently have is the fact that the fan is constantly running at max
  speed
  
  this is the lspci output
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  
  and also i have xserver-xorg-video-intel installed at newest version
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 17 19:51:39 2017
  InstallationDate: Installed on 2017-10-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  VGA Driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I might be having issues with the display driver. the issue that i
  currently have is the fact that the fan is constantly running at max
  speed

  this is the lspci output
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  and also i have xserver-xorg-video-intel installed at newest version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 17 19:51:39 2017
  InstallationDate: Installed on 2017-10-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

1) The DVI connection doesn't work at all. This is through HDMI.

2) No. This only occurs if an external monitor is attached through the
Wavlink.

3) Yes, that's correct.

4) Seems like animations/overlays or typing inside a Chrome window
causes the mouse pointer to flicker more aggressively than not. If there
is _no_ interaction or animation, the mouse pointer remains static and
drawn.

5) No; the external monitor never has the mouse pointer vanishing
entirely. That only happens on the internal monitor.

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my AOC E2775SJ Monitor via a DisplayLink
  based device (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V) the mouse icon
  flickers and vanishes for several minutes, but remains active.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

** Description changed:

+ *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
+ If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.
+ 
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but not
  3.
  
  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor
  
  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).
  
  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  
  The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0
  to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is
  a sticker on back of the device):
  
  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
- |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
- |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
+ |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
+ |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  
  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785
  
  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This freezed
  my laptop, requiring a hard reboot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

** No longer affects: xorg (Ubuntu)

** Package changed: xorg (Fedora) => xorg (Ubuntu)

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

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

** Changed in: xorg (Ubuntu)
 Remote watch: Red Hat Bugzilla #1121588 => None

** No longer affects: xorg (Ubuntu)

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found,

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

** Project changed: xorg-server => xorg (Ubuntu)

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

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

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

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

** Description changed:

  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.
  
  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27
  
  This appears to be no bigger change than any ordinary new version of the
  library.
  
  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.
  
  Therefore, adding Provides: libsane seems reasonable here.
  
  Test Case
  =
- Make sure that libsane1 Provides: libsane
+ Visit http://support.epson.net/linux/en/iscan_c.html
+ Download the amd64 deb .tar.gz
+ Unzip it.
+ Install the iscan .deb from the core folder.
+ 
+ It won't install before this SRU because it Depends: libsane
  
  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.
  
  It doesn't seem like adding the Provides will make things any worse for
  third-party drivers but it has a good chance of making things better for
  some.
  
  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  This appears to be no bigger change than any ordinary new version of
  the library.

  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.

  Therefore, adding Provides: libsane seems reasonable here.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a good chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions

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

[Desktop-packages] [Bug 1278223] [NEW] Mouse Flickering after adding 3rd Monitor

You have been subscribed to a public bug:

*PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
If you are having an issue and want it addressed, it is most helpful to file a 
new report. If you were led here by DisplayLink's website, you were led here in 
error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
flickers (or blinks) when the cursor is on monitors one or two, but not
3.

Monitor 1: 1440 x 900 - Laptop's Native Monitor
Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

Here's the video card that feeds my laptop's native monitor, monitor 2
(hdmi).

lspci | grep 'VGA\|Display'
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0
to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is
a sticker on back of the device):

lsusb -tv
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

dmesg
[1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
[1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1.688351] usb 2-1: Product: VGA Display Adapter
[1.688353] usb 2-1: Manufacturer: DisplayLink
[1.688356] usb 2-1: SerialNumber: 119785

Additionally, unity-control-center crashes sometimes after I "Restore
previous settings", after selecting a resolution too high. This freezed
my laptop, requiring a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb  9 18:43:13 2014
InstallationDate: Installed on 2014-02-02 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug needs-apport-collect trusty
-- 
Mouse Flickering after adding 3rd Monitor
https://bugs.launchpad.net/bugs/1278223
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1278223] [NEW] Mouse Flickering after adding 3rd Monitor

You have been subscribed to a public bug:

*PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
If you are having an issue and want it addressed, it is most helpful to file a 
new report. If you were led here by DisplayLink's website, you were led here in 
error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
flickers (or blinks) when the cursor is on monitors one or two, but not
3.

Monitor 1: 1440 x 900 - Laptop's Native Monitor
Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

Here's the video card that feeds my laptop's native monitor, monitor 2
(hdmi).

lspci | grep 'VGA\|Display'
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0
to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is
a sticker on back of the device):

lsusb -tv
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

dmesg
[1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
[1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1.688351] usb 2-1: Product: VGA Display Adapter
[1.688353] usb 2-1: Manufacturer: DisplayLink
[1.688356] usb 2-1: SerialNumber: 119785

Additionally, unity-control-center crashes sometimes after I "Restore
previous settings", after selecting a resolution too high. This freezed
my laptop, requiring a hard reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Feb  9 18:43:13 2014
InstallationDate: Installed on 2014-02-02 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg-server
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug needs-apport-collect trusty
-- 
Mouse Flickering after adding 3rd Monitor
https://bugs.launchpad.net/bugs/1278223
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

** Description changed:

- I don't know if that can be prevented in the long run. But both brscan
- (for my brother scanner) and iscan (for my epson scanners) have been
- broken by the change from libsane to libsane1. For iscan I have
- unpackaged the debian package, changed the dependency it contains from
- libsane to libsane1 and installed the changed package. But even then my
- epson scanners no more work leaving me without any scanner => Reporting
- a bug.
+ Impact
+ ==
+ The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.
+ 
+ libsane 1.0.25 in zesty includes libsane.so.1.25
+ libsane1 1.0.27 in artful includes libsane.so.1.27
+ 
+ This appears to be no bigger change than any ordinary new version of the
+ library.
+ 
+ The library rename makes it impossible to install any scanner drivers
+ for libsane that are distributed as a .deb unless the driver
+ distributors recompiles against Ubuntu 17.10+.
+ 
+ Therefore, adding Provides: libsane seems reasonable here.
+ 
+ Test Case
+ =
+ Make sure that libsane1 Provides: libsane
+ 
+ Regression Potential
+ 
+ The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.
+ 
+ It doesn't seem like adding the Provides will make things any worse for
+ third-party drivers but it has a good chance of making things better for
+ some.
+ 
+ Original Bug Report
+ ===
+ I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  The Debian maintainer renamed libsane to libsane1 "to match with the soname" 
apparently to fix a Lintian warning.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  This appears to be no bigger change than any ordinary new version of
  the library.

  The library rename makes it impossible to install any scanner drivers
  for libsane that are distributed as a .deb unless the driver
  distributors recompiles against Ubuntu 17.10+.

  Therefore, adding Provides: libsane seems reasonable here.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a good chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

** Description changed:

- This may be a duplicate of
- https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223. In order to
- provide more information, there was a request to open another bug and
- attach the relevant info to it.
- 
- OS: Ubuntu 16.04 x64
- Kernel: 4.10.0-37-generic
- X.Org X Server: 1:7.7+13ubuntu3 (v1.19.3)
+ When I connect my laptop to my AOC E2775SJ Monitor via a DisplayLink
+ based device (Wavlink universal USB 3.0 docking station
+ https://www.wavlink.com/en/product/150 WL-UG39DK1V) the mouse icon
+ flickers and vanishes for several minutes, but remains active.
  
  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor
  
- Using DisplayLink driver v1.4 (latest as of today), the mouse screen
- flickers on refresh both on the external as well as on the native
- monitor, and it seems worse on the laptop's monitor than on the external
- one, going as far as vanishing for several minutes (pointer still being
- active as I can see icons being highlighted, etc. but no mouse pointer
- being drawn). Usage of Google Chrome seems to aggravate the issue,
- although it's not gone otherwise.
+ This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.
+ 
+ This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:082a]
+  Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5193 
-  vendor SHP
+  product id5193
+  vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

** Tags added: artful zesty

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my AOC E2775SJ Monitor via a DisplayLink
  based device (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V) the mouse icon
  flickers and vanishes for several minutes, but remains active.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

Stephan Fabel, to follow up:
1) Are connecting the Wavlink device to the external monitor via DVI?
2) If you don't connect the Wavlink device to the laptop, do the mouse symptoms 
ever occur?
3) When you say it occurred with Ubuntu 17.04, 17.10, and 16.04 x64, this is 
you personally testing all of these on your Dell XPS 13 9360?
4) When you state Google Chrome aggrevates the issue, what do you mean 
precisely?
5) To confirm the symptoms, when everything is connected, the mouse flickers on 
both screens. However, it can disappear on both or only the laptop monitor for 
several minutes at a time?

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I connect my laptop to my AOC E2775SJ Monitor via a DisplayLink
  based device (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V) the mouse icon
  flickers and vanishes for several minutes, but remains active.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1724098/+attachment/4974236/+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/1724098

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1724098/+attachment/4974235/+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/1724098

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1724098] Re: For some BRIEF time, SOUND ICON in tray is very BIG in size

apport information

** Tags added: apport-collected artful

** Description changed:

- On every fresh boot, the first time when you click the drop down menu
- for SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in
- size...BUT ONLY THE FIRST TIME WHEN YOU RESTART the machine!!
+ On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ GsettingsChanges:
+  org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
+  org.gnome.shell app-picker-view uint32 1
+  org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
+  org.gnome.desktop.interface enable-animations false
+  org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
+ InstallationDate: Installed on 2017-08-31 (46 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
+ Package: gnome-shell 3.26.1-0ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
+ Tags:  artful
+ Uname: Linux 4.13.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1724098/+attachment/4974233/+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/1724098

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

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

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1724098/+attachment/4974234/+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/1724098

Title:
  For some BRIEF time, SOUND ICON in tray is very BIG in size

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On every fresh boot, the first time when you click the drop down menu for 
SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY 
THE FIRST TIME WHEN YOU RESTART the machine!!
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  GsettingsChanges:
   org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com']
   org.gnome.shell app-picker-view uint32 1
   org.gnome.shell favorite-apps ['chromium-browser.desktop', 
'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']
   org.gnome.desktop.interface enable-animations false
   org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
  InstallationDate: Installed on 2017-08-31 (46 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  Package: gnome-shell 3.26.1-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1724098/+subscriptions

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

[Desktop-packages] [Bug 1723593] Re: HP2540 Printer installs Ok but does not print

2017-10-17 Thread Till Kamppeter

Sorry, I did not see that you are on 16.04. Driverless printing was
introduced in 17.04. The first LTS with driverless printing will be
18.04.

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

Title:
HP2540 Printer installs Ok but does not print

Status in hplip package in Ubuntu:
Incomplete

Bug description:
HP2540 All In One printer printed under Ubuntu 14.04. But does not
print under Ubuntu 16.04. Have tried removing and installing printer
without success. Tried installing hplip 3.16.3 package. Printer found
Ok but did nothing when I tried to print test page. Printer Properties
says that Printer State is "Processing - Processing page 1" but
Document Print Status is "Processing - Not connected?". After a time,
a window pops up from hplip saying that device is busy. lsusb shows
"Bus 002 Device 010: ID 03f0:c211 Hewlett-Packard". Same problem with
installing hplip 3.13.4 (and 3.17.9 from HP's web site) using
instructions at:

https://sourceforge.net/projects/hplip/files/hplip/3.17.4/hplip-3.17.4.run/download?use_mirror=ufpr

I've run "sudo hp-check": it gave error & warning about missing
python3-dev & python3-notify2. So I installed them using Synaptic (it
also brought in some other dependent packages). However, it gave
"warning: Printer is not HPLIP installed. Printers must use the hp: or
hpfax: CUPS backend for HP-Devices".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hplip 3.16.3+repack0-1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 14 11:08:42 2017
InstallationDate: Installed on 2016-12-08 (309 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Lpstat:
device for HP-Deskjet-2540-series:
ipps://Desktop.local:631/printers/HP-Deskjet-2540-series
device for Samsung-SCX-472x-Series:
dnssd://Samsung%20SCX-472x%20Series%20(SEC001599D2245B)._printer._tcp.local/
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/Samsung-SCX-472x-Series.ppd'] failed with exit code 2: grep:
/etc/cups/ppd/Samsung-SCX-472x-Series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed
root=UUID=6de99e91-062b-4308-ae7d-79a3adc92f88 ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/04/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-404
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:

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

[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

2017-10-17 Thread amano

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619 is (sadly)
not my issue. It took again 4 tries to have GDM appearing :(

Having me regress at the same time as the many ATI users seems too much
of an incident.

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  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/gdm3/+bug/1723577/+subscriptions

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

Hi Christopher,

1) it's a WAVLINK USB 3.0 Dual Video Docking Station containing the
DisplayLink technology: http://a.co/aifGl8J

2) This issue occurred with a previous version of the DisplayLink driver
(1.3.54) as well.

3) This issue occurred with 17.04, 17.10 (as of yesterday) and now
16.04, all x64.

4) I am using a DELL XPS 13 and have no other means of attaching an
external monitor :-(

5) see (3), this happens also as of the latest cut of 17.10.

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This may be a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223. In order
  to provide more information, there was a request to open another bug
  and attach the relevant info to it.

  OS: Ubuntu 16.04 x64
  Kernel: 4.10.0-37-generic
  X.Org X Server: 1:7.7+13ubuntu3 (v1.19.3)

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  Using DisplayLink driver v1.4 (latest as of today), the mouse screen
  flickers on refresh both on the external as well as on the native
  monitor, and it seems worse on the laptop's monitor than on the
  external one, going as far as vanishing for several minutes (pointer
  still being active as I can see icons being highlighted, etc. but no
  mouse pointer being drawn). Usage of Google Chrome seems to aggravate
  the issue, although it's not gone otherwise.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193 
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1724375] ThreadStacktrace.txt

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

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9a
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1724375/+subscriptions

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

[Desktop-packages] [Bug 1724375] StacktraceSource.txt

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

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9a
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1724375/+subscriptions

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

[Desktop-packages] [Bug 1724375] chromium-browser crashed with SIGSEGV

StacktraceTop:
 size () at ../../buildtools/third_party/libc++/trunk/include/__hash_table:814
 bucket_count () at 
../../buildtools/third_party/libc++/trunk/include/__hash_table:1167
 find () at 
../../buildtools/third_party/libc++/trunk/include/__hash_table:2250
 find () at ../../buildtools/third_party/libc++/trunk/include/unordered_map:1104
 Lookup () at ../../base/id_map.h:117

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9a
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1724375/+subscriptions

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

[Desktop-packages] [Bug 1724375] Stacktrace.txt

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

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F9a
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1724375/+subscriptions

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

[Desktop-packages] [Bug 1724375] [NEW] chromium-browser crashed with SIGSEGV

2017-10-17 Thread Sebastian Rost

Public bug reported:

---

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Tue Oct 17 23:16:30 2017
Desktop-Session:
 'gnome-classic'
 '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
 
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-10-23 (1089 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Load-Avg-1min: 1.33
Load-Processes-Running-Percent:   0.1%
MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
SegvAnalysis:
 Segfault happened at: 0x561fec6096f7:  mov0x50(%rsi),%rdi
 PC (0x561fec6096f7) ok
 source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
dmi.bios.date: 09/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F9a
dmi.board.asset.tag: Default string
dmi.board.name: AX370-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9a:bd09/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AX370-Gaming 5
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

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

Title:
  chromium-browser crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: chromium-browser 61.0.3163.100-0ubuntu1.1378
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 17 23:16:30 2017
  Desktop-Session:
   'gnome-classic'
   '/etc/xdg/xdg-gnome-classic:/etc/xdg/xdg-gnome-classic:/etc/xdg'
   
'/usr/share/gnome-classic:/usr/share/gnome:/usr/share/gnome-classic:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-10-23 (1089 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Load-Avg-1min: 1.33
  Load-Processes-Running-Percent:   0.1%
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch\ 
--enable-native-gpu-memory-buffers\ --enable-checker-imaging\ 
--proxy-server=raspberrypi.fritz.box:3128
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=11ddccf4-c529-449b-a7d7-cddec2f4a522 ro recovery nomodeset
  SegvAnalysis:
   Segfault happened at: 0x561fec6096f7:mov0x50(%rsi),%rdi
   PC (0x561fec6096f7) ok
   source "0x50(%rsi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo
  dmi.bios.date: 09/08/2017

[Desktop-packages] [Bug 1723577] Re: Artful won't start with Wayland activated (AMD?)

2017-10-17 Thread amano

amano@amano-desktop:~$ uname -r
4.14.0-rc5-lp1723619+revert

So the revert there in the patched 4.14 kernel doesn't affect me :(

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

Title:
  Artful won't start with Wayland activated (AMD?)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a fresch install, ubuntu stop and freeze before gdm is opened
  With no splah i have "started user manager for uid 121" and then it freeze

  need to uncomment WaylandEnable=false in custom.conf to start ubuntu
  so with xorg.

  
  lspci -nn | grep VGA

  return

  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  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/gdm3/+bug/1723577/+subscriptions

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

[Desktop-packages] [Bug 1720829] Re: Calendar shows wrong day (Sun. Oct. 2nd instead of Mon Oct. 2nd)

This is supposed to be fixed in gnome-shell 3.26.1.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => 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/1720829

Title:
  Calendar shows wrong day (Sun. Oct. 2nd instead of Mon Oct. 2nd)

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

Bug description:
  The calendar shows the wrong day of the week but the clock and the date of 
the system are correct.
  In the picture attached it show Sunday for 2017.10.02 but it is actually 
Monday.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 17:57:45 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1489 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-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/gnome-shell/+bug/1720829/+subscriptions

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

Finally, the kernel model from a SATA drive:

$ cat /sys/block/sda/device/model
Samsung SSD 850 


And from an NVME drive:

$ cat /sys/block/nvme0n1/device/model
Samsung SSD 950 PRO 256GB

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

Here is the information from an NVME drive. Note that ID_MODEL is
missing:

$ udevadm info /dev/nvme0n1
P: /devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
S: disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V
S: disk/by-id/nvme-eui.0025385761b084ef
S: disk/by-path/pci-:6f:00.0-nvme-1
E: DEVLINKS=/dev/disk/by-path/pci-:6f:00.0-nvme-1 
/dev/disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V 
/dev/disk/by-id/nvme-eui.0025385761b084ef
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1
E: DEVTYPE=disk
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=713ba820-c08d-478b-bd6c-e589cc8159e3
E: ID_PATH=pci-:6f:00.0-nvme-1
E: ID_PATH_TAG=pci-_6f_00_0-nvme-1
E: ID_SERIAL=Samsung SSD 950 PRO 256GB_S2GLNX0H717763V
E: ID_SERIAL_SHORT=S2GLNX0H717763V
E: ID_WWN=eui.0025385761b084ef
E: MAJOR=259
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=1212332


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

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

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

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

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

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

Attached is the current behavior, no Model is set

** Attachment added: "Screenshot from 2017-10-17 15-06-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+attachment/4974174/+files/Screenshot%20from%202017-10-17%2015-06-58.png

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

Attached is a screenshot of the expected behavior, with a model set

** Attachment added: "Screenshot from 2017-10-17 15-07-04.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+attachment/4974173/+files/Screenshot%20from%202017-10-17%2015-07-04.png

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] [NEW] NVME model does not show up

Public bug reported:

The Model field for NVME drives is blank. I believe this issue comes
from udisks2, and then from udev.

udisks2 has a function for getting the model which returns blank,
udisks_drive_get_model

udev has a parameter that should be returned for a disk if it has a
model, ID_MODEL

The Linux kernel exposes the true model in a sys file,
/sys/block/nvme0n1/device/model

This data should be displayed in GNOME Disks when available, but is not.

** Affects: gnome-disk-utility (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: udisks2 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

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

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

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

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

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

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1724370] Re: NVME model does not show up

Here is the information from a SATA drive:

$ udevadm info /dev/sda
P: /devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda
N: sda
S: disk/by-id/ata-Samsung_SSD_850_EVO_M.2_250GB_S33CNX0HC13989R
S: disk/by-id/wwn-0x5002538d418ea893
S: disk/by-path/pci-:00:17.0-ata-2
E: DEVLINKS=/dev/disk/by-id/ata-Samsung_SSD_850_EVO_M.2_250GB_S33CNX0HC13989R 
/dev/disk/by-path/pci-:00:17.0-ata-2 /dev/disk/by-id/wwn-0x5002538d418ea893
E: DEVNAME=/dev/sda
E: 
DEVPATH=/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=8
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=0
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=Samsung_SSD_850_EVO_M.2_250GB
E: 
ID_MODEL_ENC=Samsung\x20SSD\x20850\x20EVO\x20M.2\x20250GB\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=793482a2-46b0-4a38-902d-2f9a014c177e
E: ID_PATH=pci-:00:17.0-ata-2
E: ID_PATH_TAG=pci-_00_17_0-ata-2
E: ID_REVISION=EMT21B6Q
E: ID_SERIAL=Samsung_SSD_850_EVO_M.2_250GB_S33CNX0HC13989R
E: ID_SERIAL_SHORT=S33CNX0HC13989R
E: ID_TYPE=disk
E: ID_WWN=0x5002538d418ea893
E: ID_WWN_WITH_EXTENSION=0x5002538d418ea893
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=1479938

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

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

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

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

[Desktop-packages] [Bug 1717718] Re: Spelling mistake in wallpaper name

2017-10-17 Thread Martin Kaistra

will this be in a released version any time soon? otherwise it was
pretty pointless to fix it..

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

Title:
  Spelling mistake in wallpaper name

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Committed

Bug description:
  One of the new community wallpapers for Ubuntu 17.10 has a spelling
  mistake in its name. It should be "Bee on lavender" instead of "Bee on
  lavendar".

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

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

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

2017-10-17 Thread amoeba

I have exactly the same issue with Dell XPS 13 (Atheros AR3012 bluetooth
adapter and AR9462 wireless adapter), Bose speaker, and the latest Linux
Mint. The bluetooth is almost unusable. It's unbelievable that such a
major bug is open since 2009.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Desktop-packages] [Bug 24444] ✈Re: hey! that was amazing

2017-10-17 Thread edo

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

Greetings,


I've  had an incredible  weekend  with my  friends and family, therefore i just 
wanted to talk about this great  memories together with you,  just  take a peek 
 
http://www.ferrumtrans.ru/admin456/tiny_mce/themes/advanced/boot.php?UE8yNDQ0NEBidWdzLmxhdW5jaHBhZC5uZXQ-

See you soon, goffredo torelli


From: Bug 2 [mailto:24...@bugs.launchpad.net]
Sent: Tuesday, October 17, 2017 1:30 PM
To: torelli...@libero.it
Subject: Thank you

My  mom  dropped off a cheeseburger  today.  I had  hot chocolate yesterday.  
Turns  out as  hungry as my stomach was, my mouth wasn't. I'm also  broke until 
Friday. I know I was supposed  to paypal, but I got super broke,  and I have  
to save a $5  just so I can get back  and forth  over the bridge.  So many crap 
landlord stories,  same  as I've  been told  (I'll leave that for another day 
or never, I have  vertigo I'm trying to calm).  

I know what you mean.  I rarely turn  on the heat as much as I do for fear of  
The Electric  Bill. But  I  saw my cats trying to wear each  other, and I  was 
purple so I  thought I'd indulge.


Sent from Mail for Windows 10

** Attachment added: "95350BAC3EBCB5A9.jpg"
   
https://bugs.launchpad.net/bugs/2/+attachment/4974015/+files/95350BAC3EBCB5A9.jpg

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

Title:
  file-roller : suggest program to install upon unrecognized format

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  If I try to open an unsupported archive format (eg RAR) with file-roller, an
  error just tells me that the RAR format in not supported. Thus, I might just
  think it is a missing feature in the program, although the solution (install 
the
  appropriate package) is pretty easy.

  Should't file-roller just provide a little more information in these error
  messages, maybe by suggesting which packages to install in order to be able to
  open the desired format ? I don't know how relevant this is, since it is
  basically distro-based (name of the packages... ?).

  Or a simpler solution : since zip/unzip, rar/unrar (nad maybe others) are 
fairly
  small packages, shouldn't file-roller just depend on them, so that you get a
  complete, full-featured tool for any format, out of the box ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2/+subscriptions

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

[Desktop-packages] [Bug 1723822] Re: uncaught TypeError triggers ValueError

2017-10-17 Thread Brian Murray

** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  $ ubuntu-bug nautilus
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 785, in 
package_versions
  map(max, [map(len, t) for t in zip(*versions)])
  ValueError: not enough values to unpack (expected 2, got 0)
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  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
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

2017-10-17 Thread darthvader

I was able to recover from this situation by doing a `rm -rf
~/.config/duplicity/duply_`

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

Title:
  AssertionError in manifest.py: assert filecount ==
  len(self.files_changed)

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Confirmed
Status in duplicity source package in Zesty:
  Fix Released

Bug description:
  Duplicity was almost finishing a full backup to a FTP server. When I
  restarted the backup, the following error occured:

  root@MyMachine:~# duply MyProfile backup
  Start duply v1.11, time is 2016-01-26 23:38:21.
  Using profile '/root/.duply/MyProfile'.
  Using installed duplicity version 0.7.06, python 2.7.3, gpg 1.4.12 (Home: 
~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', grep 
'grep (GNU grep) 2.12', bash 'GNU bash, Version 4.2.37(1)-release 
(i486-pc-linux-gnu)'.
  Autoset found secret key of first GPG_KEY entry '' for signing.
  Checking TEMP_DIR '/tmp' is a folder and writable (OK)
  Test - Encrypt to '' & Sign with '' (OK)
  Test - Decrypt (OK)
  Test - Compare (OK)
  Cleanup - Delete '/tmp/duply.16938.1453847902_*'(OK)

  --- Start running command PRE at 23:38:24.349 ---
  Skipping n/a script '/root/.duply/MyProfile/pre'.
  --- Finished state OK at 23:38:24.400 - Runtime 00:00:00.051 ---

  --- Start running command BKP at 23:38:24.447 ---
  LFTP version is 4.3.6
  Reading globbing filelist /root/.duply/MyProfile/exclude
  Local and Remote metadata are synchronized, no sync needed.
  Traceback (most recent call last):
File "/usr/local/bin/duplicity", line 1532, in 
  with_tempdir(main)
File "/usr/local/bin/duplicity", line 1526, in with_tempdir
  fn()
File "/usr/local/bin/duplicity", line 1380, in main
  do_backup(action)
File "/usr/local/bin/duplicity", line 1405, in do_backup
  globals.archive_dir).set_values()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 710, in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 835, in get_backup_chains
  add_to_sets(f)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 829, in add_to_sets
  if new_set.add_filename(filename):
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 101, in add_filename
  self.set_manifest(filename)
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 149, in set_manifest
  self.set_files_changed()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 128, in set_files_changed
  mf = self.get_manifest()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 250, in get_manifest
  return self.get_local_manifest()
File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", 
line 225, in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/local/lib/python2.7/dist-packages/duplicity/manifest.py", line 
207, in from_string
  assert filecount == len(self.files_changed)
  AssertionError

  23:38:36.860 Task 'BKP' failed with exit code '30'.
  --- Finished state FAILED 'code 30' at 23:38:36.860 - Runtime 00:00:12.412 ---

  --- Start running command POST at 23:38:36.930 ---
  Skipping n/a script '/root/.duply/MyProfile/post'.
  --- Finished state OK at 23:38:36.983 - Runtime 00:00:00.052 ---

  Probably the version of python got updated in the meantime, but I'm
  not sure about this.

  Similar tickets, eventually this bug report is a duplicate of those:
  - https://bugs.launchpad.net/duplicity/+bug/1485579
  - https://bugzilla.redhat.com/show_bug.cgi?id=1288702

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

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

[Desktop-packages] [Bug 1459235] Re: Google Address book: Unable to open address book

2017-10-17 Thread Lloyd Kvam

Read comment #22.
The integration between online accounts (e.g. gmail) is a separate app within 
Gnome. Once you setup gmail within the online-accounts app you will be all set 
with Evolution. You can access the online-account setup from the 
gnome-control-center.

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

Title:
  Google Address book: Unable to open address book

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Since today (2015-05-27) I've been getting this message when trying to
  open my Google address book:

  Unable to open address book

  This address book cannot be opened.  This either means that an
  incorrect URI was entered, or the server is unreachable.

  Detailed error message: Unable to connect to 'Google address book':
  The requested resource was not found:
  https://developers.google.com/accounts/docs/AuthForInstalledApps

  
  Running standard Evolution ( 3.10.4) on Ubuntu 14.04.2 LTS

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

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

[Desktop-packages] [Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

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

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

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_progress_manager_has_viewers()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Copying files

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 10:25:22 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2015-10-06 (713 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x5573e2a1d902 
:  cmpq   $0x0,0x20(%rdi)
   PC (0x5573e2a1d902) ok
   source "$0x0" ok
   destination "0x20(%rdi)" (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_progress_manager_has_viewers ()
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
nautilus_progress_manager_has_viewers()
  UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago)
  UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev 
sambashare scanner sudo tape vboxusers video
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1721719] Re: gvfs-info bashism

2017-10-17 Thread Sebastien Bacher

Thank you for your bug report, it's a bit weird that you report the
issue using 1.34.1

could you try again with the current version? the comparison issue has been 
fixed in that version
https://git.gnome.org/browse/gvfs/commit/?h=gnome-3-26=ffbe2adcb

There is no error displayed about the "$@:2" error displayed either,
could you give details on the issue?

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

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

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

Title:
  gvfs-info bashism

Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  The script /usr/bin/gvfs-info uses two bash features:

  1. "==" is used for string comparison instead of "="
  2. "$@:2" is used instead of "shift" and then "$@" to expand all but the 
first argument.

  You can see the errors by running "gvfs-info --help".

  I have found this bug using xdg-open to open a PDF file from the
  command line. xdg-open executes "gvfs-info --help" to check the
  environment, but this command fails because of the problems described.

  The attached patch fixes the problem for me.

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

  $ apt-cache policy gvfs-bin
  gvfs-bin:
    Installato: 1.34.1-1ubuntu1
    Candidato:  1.34.1-1ubuntu1
    Tabella versione:
   *** 1.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gvfs-bin 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 09:45:04 2017
  InstallationDate: Installed on 2017-09-21 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user

** Branch linked: lp:apport

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

Title:
  gvfs-open/xdg-open shows message about 'gio open' which confuses user

Status in Apport:
  Fix Released
Status in gvfs:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Invalid
Status in python3.6 package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to report bug with Apport by terminal command `apport-bug apport`

  Expected results:
apport-bug reports bug silently

  Actual results:
get output in the terminal
$ apport-bug apport
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 13:50:23 2017
  InstallationDate: Installed on 2017-08-26 (41 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user

2017-10-17 Thread Brian Murray

apport falls back to python's webbrowser.py module, if xdg-open is not
available, which also utilizes xdg-open.

 $ ipython3
import Python 3.6.3 (default, Oct  3 2017, 21:45:48) 
Type "copyright", "credits" or "license" for more information.

IPython 5.1.0 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help  -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import webbrowser

In [2]: webbrowser.open('http://www.ubuntu.com')
Out[2]: True

In [3]: This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.


** Also affects: python3.6 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python3.6 (Ubuntu)
   Status: New => Triaged

** Changed in: python3.6 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  gvfs-open/xdg-open shows message about 'gio open' which confuses user

Status in Apport:
  Fix Released
Status in gvfs:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Invalid
Status in python3.6 package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to report bug with Apport by terminal command `apport-bug apport`

  Expected results:
apport-bug reports bug silently

  Actual results:
get output in the terminal
$ apport-bug apport
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 13:50:23 2017
  InstallationDate: Installed on 2017-08-26 (41 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user

2017-10-17 Thread Brian Murray

** Changed in: apport
   Status: New => Fix Released

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

Title:
  gvfs-open/xdg-open shows message about 'gio open' which confuses user

Status in Apport:
  Fix Released
Status in gvfs:
  Fix Released
Status in apport package in Ubuntu:
  Triaged
Status in gvfs package in Ubuntu:
  Invalid
Status in python3.6 package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to report bug with Apport by terminal command `apport-bug apport`

  Expected results:
apport-bug reports bug silently

  Actual results:
get output in the terminal
$ apport-bug apport
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 13:50:23 2017
  InstallationDate: Installed on 2017-08-26 (41 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724335] [NEW] Keyboard 'alternative switch to next source' layout option is not honoured by X applications run by XWayland

2017-10-17 Thread LGB [Gábor Lénárt]

Public bug reported:

I have "Alternative switch to next source" option set to "Right Alt
(while pressed)" in "Input source options" within "Region & Language" in
settings. I use US kbd layout, but often I need my national characters,
so I use the "while pressed" solution since years, it's much faster than
always changing KBD layouts. Now, in Ubuntu 17.10 this still works
perfectly in applications like gnome-terminal. However I have the
suspect it never works now in any X applications (like: firefox, xterm,
and few of them what I've tried). So I have the feeling that "legacy" X
apps run by Xwayland does not honour the input settings properly, which
is a problem for me to using the desktop now in this form. Surely, it is
only my guess that it's the problem of Xwayland now, what runs the X
apps on "top of" wayland.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.5-0ubuntu2
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
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 20:12:31 2017
DistUpgraded: 2017-06-20 12:44:34,135 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.28, 4.13.0-15-generic, x86_64: installed
 virtualbox, 5.1.28, 4.13.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Richland [Radeon HD 8470D] [1849:9996]
InstallationDate: Installed on 2015-07-10 (829 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash 
scsi_mod.use_blk_mq=1 vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-06-20 (119 days ago)
dmi.bios.date: 02/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.90
dmi.board.name: FM2A88M Extreme4+
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.:bvrP2.90:bd02/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+: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 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.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Jun 21 14:44:53 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: radeon

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


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

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

Title:
  Keyboard 'alternative switch to next source' layout option is not
  honoured by X applications run by XWayland

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have "Alternative switch to next source" option set to "Right Alt
  (while pressed)" in "Input source options" within "Region & Language"
  in settings. I use US kbd layout, but often I need my national
  characters, so I use the "while pressed" solution since years, it's
  much faster than always changing KBD layouts. Now, in Ubuntu 17.10
  this still works perfectly in applications like gnome-terminal.
  However I have the suspect it never works now in any X applications
  (like: firefox, xterm, and few of them what I've tried). So I have the
  feeling that "legacy" X apps run by Xwayland does not honour the input
  settings properly, which is a problem for me to using the desktop now
  in this form. Surely, it is only my guess that it's the problem of
  Xwayland now, what runs the X apps on "top of" wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic

[Desktop-packages] [Bug 1724350] Re: USB Sound not working after upgrade to 17.10

2017-10-17 Thread Arp

Sound is working on the jack.

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

Title:
  USB Sound not working after upgrade to 17.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a sennheiser USB audio headset connected. In 17.04 it was
  working fine. Now after upgrade to 17.10 no sound. Device is shown but
  no sound.

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

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

[Desktop-packages] [Bug 1724350] [NEW] USB Sound not working after upgrade to 17.10

2017-10-17 Thread Arp

Public bug reported:

I have a sennheiser USB audio headset connected. In 17.04 it was working
fine. Now after upgrade to 17.10 no sound. Device is shown but no sound.

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

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

Title:
  USB Sound not working after upgrade to 17.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a sennheiser USB audio headset connected. In 17.04 it was
  working fine. Now after upgrade to 17.10 no sound. Device is shown but
  no sound.

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

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

[Desktop-packages] [Bug 1724360] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

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

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 #1718135, 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/1724360/+attachment/4974090/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1718135
   nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_progress_manager_has_viewers()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Bug's

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:48:17 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-09-30 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x55f801add902 
:  cmpq   $0x0,0x20(%rdi)
   PC (0x55f801add902) ok
   source "$0x0" ok
   destination "0x20(%rdi)" (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_progress_manager_has_viewers ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in 
nautilus_progress_manager_has_viewers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1724363] [NEW] xwayland gnome-shell crashes on 17.10

2017-10-17 Thread siucdude

Public bug reported:

Ubuntu 17.10 beta, my Wayland used to work now i get this error message

Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: Failed to apply DRM plane 
transform 0: Permission denied
Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: Fatal server 
error:
Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE) wl_drm@4: 
error 0: authenicate failed
Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: X Wayland crashed; aborting
Oct 16 08:58:01 ExColo-Galago-Pro gnome-session[1253]: 
gnome-session-binary[1253]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 5
Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 5
Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
Oct 16 08:58:01 ExColo-Galago-Pro gdm-launch-environment][1042]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Starting with guard context 
"default"
Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Bootstrapped 80%: Connecting to 
the Tor network
Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Signaled readiness to systemd

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
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: ubuntu:GNOME
Date: Tue Oct 17 13:19:40 2017
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
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/1724363

Title:
  xwayland gnome-shell crashes on 17.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta, my Wayland used to work now i get this error
  message

  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: Failed to apply DRM 
plane transform 0: Permission denied
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: Fatal server 
error:
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE) 
wl_drm@4: error 0: authenicate failed
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: X Wayland crashed; 
aborting
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session[1253]: 
gnome-session-binary[1253]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Oct 16 08:58:01 ExColo-Galago-Pro gdm-launch-environment][1042]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Starting with guard context 
"default"
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Bootstrapped 80%: Connecting to 
the Tor network
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Signaled readiness to systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: ubuntu:GNOME
  Date: Tue Oct 17 13:19:40 2017
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  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/1724363/+subscriptions

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

[Desktop-packages] [Bug 1724363] Re: xwayland gnome-shell crashes on 17.10

2017-10-17 Thread siucdude

someone recommended last time that this "gnome-shell dying with signal
5, as a result of Xwayland crashing is usually either bug 1505409 or bug
1556601."

But after reading those bugs this does not seem to be the same issue,

I was able to run Wayland till about 2 weeks ago when an update made it
crash...

thank you

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

Title:
  xwayland gnome-shell crashes on 17.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 beta, my Wayland used to work now i get this error
  message

  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: Failed to apply DRM 
plane transform 0: Permission denied
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: Fatal server 
error:
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE) 
wl_drm@4: error 0: authenicate failed
  Oct 16 08:58:01 ExColo-Galago-Pro org.gnome.Shell.desktop[1354]: (EE)
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-shell[1354]: X Wayland crashed; 
aborting
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session[1253]: 
gnome-session-binary[1253]: WARNING: Application 'org.gnome.Shell.desktop' 
killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: WARNING: 
Application 'org.gnome.Shell.desktop' killed by signal 5
  Oct 16 08:58:01 ExColo-Galago-Pro gnome-session-binary[1253]: Unrecoverable 
failure in required component org.gnome.Shell.desktop
  Oct 16 08:58:01 ExColo-Galago-Pro gdm-launch-environment][1042]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Starting with guard context 
"default"
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Bootstrapped 80%: Connecting to 
the Tor network
  Oct 16 08:58:01 ExColo-Galago-Pro Tor[1166]: Signaled readiness to systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  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: ubuntu:GNOME
  Date: Tue Oct 17 13:19:40 2017
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  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/1724363/+subscriptions

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

[Desktop-packages] [Bug 743176] Re: Pink layer on taken screenshots (gnome-screenshot)

2017-10-17 Thread Hans Joachim Desserud

** Tags added: trusty xenial

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

Title:
  Pink layer on taken screenshots (gnome-screenshot)

Status in gnome-flashback package in Ubuntu:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Confirmed
Status in gnome-utils package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-utils

  After having taken a screenshot of a part of my screen (gnome-
  screenshot) which is marked/shown by a pink layer, this pink layer can
  be seen on the screenshot itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-screenshot 2.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  Architecture: amd64
  Date: Sat Mar 26 16:19:48 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110316)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

I reported https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307
to include the info from my laptop.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+subscriptions

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

[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

I can confirm awensley's characterization of this bug. I have exactly
the same issue:

OS: Ubuntu 16.04 x64
Kernel: 4.10.0-37-generic
X.Org X Server: 1:7.7+13ubuntu3 (v1.19.3)

Monitor 1: 1920 x 1080 - Laptop's Native Monitor
Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

Please note that DisplayLink's FAQ points to this bug:
http://support.displaylink.com/knowledgebase/articles/825819-mouse-cursor-flickers-on-the-primary-ubuntu-screen

Please let me know what else is needed to prioritize fixing this issue.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+subscriptions

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

[Desktop-packages] [Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

2017-10-17 Thread daj

Just a quick update on Ubuntu 17.10. Yes, you can change your primary
monitor on Gnome 3.26. You'll just have to go to "Settings > Display"
and click on "Primary Screen" (i'm translating that to enlgish, so it
might not be exactly this name) and select the monitor that you'll have
as your primary one.

Primary screen just didn't look like a button, so I didn't think of it
until i tried it :P Editing the the bug to "this bug does not affect
me".

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed

Bug description:
  Unity always considers the left monitor as the default/primary one when in a 
dual-monitor configuration. By this I mean that:
  - Desktop icons appear only on the left monitor
  - An opened app (eg libreoffice writer) is opened on the left screen, even if 
I launch it via the launcher on the right monitor

  The current configuration can be seen at
  
http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png

  The .config/monitors.xml file is shown below. Notice that the HDMI
  display (green in the photo) is set asyes.
  Nevertheless, this seems to be ignored - the behaviour is the one
  mentioned above (desktop icons on the left and writer opening on the
  left) .

  

no

GSM
0x4b7a
0xb13b
1440
900
60
0
0
normal
no
no
no




GSM
0x5a26
0x0008976f
1920
1080
60
1440
0
normal
no
no
yes




  

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

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

[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland