date:20170928

This bug was fixed in the package libinput - 1.8.2-1ubuntu2

---
libinput (1.8.2-1ubuntu2) artful; urgency=medium

  * debian/patches/0005-touchpad-don-t-resume-a-disabled-touchpad.patch:
Backport from upstream - keep the disabled state properly across
suspend/resume. Thanks to Jonas Ådahl for help investigating. (LP:
#1715479)

 -- Iain Lane   Thu, 28 Sep 2017 18:40:24
+0100

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

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Fix Released
Status in libinput package in Debian:
  Confirmed
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1720262] [NEW] gnome-screenshot Actions don't work in default Ubuntu 17.10 session

Public bug reported:

Ubuntu 17.10 Beta
Ubuntu session (Wayland)

Open the Activities Overview.
Right-click on Screenshot.

2 of the 3 extra desktop actions don't work.

Works
=
Take a Screenshot of the Whole Screen

Doesn't Work

Take a Screenshot of the Current Window
Take a Screenshot of a Selected Area

Other Info
==
All 3 functions work if you open Screenshot and click the buttons in the app.

The Current Window action is upstream, but Selected Area is an Ubuntu
patch.

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


** Tags: artful rls-aa-incoming

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

Title:
  gnome-screenshot Actions don't work in default Ubuntu 17.10 session

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 Beta
  Ubuntu session (Wayland)

  Open the Activities Overview.
  Right-click on Screenshot.

  2 of the 3 extra desktop actions don't work.

  Works
  =
  Take a Screenshot of the Whole Screen

  Doesn't Work
  
  Take a Screenshot of the Current Window
  Take a Screenshot of a Selected Area

  Other Info
  ==
  All 3 functions work if you open Screenshot and click the buttons in the app.

  The Current Window action is upstream, but Selected Area is an Ubuntu
  patch.

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

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

[Desktop-packages] [Bug 1654730] Re: Resuming from suspend, network manager can only see 1 WiFi network

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

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

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

Title:
  Resuming from suspend, network manager can only see 1 WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hardware:
  Dell XPS15 9550
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter

  Software:
  Ubuntu 16.04.1 LTS 4.4.0-58-generic
  network-manager 1.2.4-0ubuntu0.16.04.1
  network-manager-gnome 1.2.0-0ubuntu0.16.04.4

  
  02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Flags: bus master, fast devsel, latency 0, IRQ 136
Memory at dd20 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

  
  When resuming from suspend, network-manager only displays one random network 
(random/different one each time).

  Switching WiFi off and on does not fix it.  iwlist scanning does not
  fix it.

  After running "sudo iwlist scanning", network manager works normally
  again immediately.

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

I also edited /etc/modprobe.d/nvidia-graphics-drivers.conf and set
'modeset=1' for the nvidia driver where it was previously 0, you might
give that a shot and if that works we can mark this a duplicate.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

After some research I believe this may be related:

* https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033
* 
https://devtalk.nvidia.com/default/topic/1000172/linux/root-less-xorg-does-not-detect-displays-which-leads-to-segfault-in-mutter/

I am trying a work around, let me know if this fixes anything:

echo 'needs_root_rights = yes' | sudo tee -a /etc/X11/Xwrapper.config

and reboot.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

Thanks for your report; I have uploaded a merge.

When testing it I stumbled upon the problem in bug #1720250.

As regards "IBUS_ENABLE_SYNC_MODE=0", how serious do you consider the
issue you mention to be?

** Changed in: im-config (Ubuntu)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu)
   Status: New => Fix Committed

** Changed in: im-config (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  Fix Committed

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

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

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

** Tags removed: patch

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  New

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

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

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

[Desktop-packages] [Bug 1702078] Re: Boot to blank screen

2017-09-28 Thread Timo Aaltonen

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Boot to blank screen

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful 
Daily
  Installation went OK.
  At boot the grub menu is shown.
  After selection of Ubuntu the screen gets blank. The plymouth screen isn't 
shown.
  When I press Ctrl repeatedly the plymouth screen is shown and then the login 
screen.
  The installation is set to use the swedish keyboard, but the english keyboard 
is used.
  Except for that the installation behaves OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  BootLog: /dev/sdc1: clean, 153910/39075840 files, 4226467/156282624 blocks
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Jul  3 13:56:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:e174]
  InstallationDate: Installed on 2017-07-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703)
  MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e83ef1bc-3743-4dde-a4e8-b774b544ef66 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: GA-990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990FXA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jul  3 15:28:22 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY Compaq USB Keyboard KEYBOARD, id 8
   inputCHICONY Compaq USB Keyboard KEYBOARD, id 9
   inputMicrosoft Corporation Microsoft ® Laser Mouse 6000 MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()

** Changed in: gnome-shell
   Status: Unknown => Confirmed

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint()

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8

  ---

  As of an upgrade to 3.25.91 (last session that did not exhibit this
  behavior was a 3.24.x session), I've experienced several crashes of
  the shell in the overview. journalctl shows the following output at
  the time of the crash:

  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: 
Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
  Sep 01 08:14:41 spiny gnome-shell[8506]: 
meta_renderer_native_release_onscreen: assertion 
'onscreen_native->gbm.next_fb_id == 0' failed
  Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 
'onscreen->winsys == ((void *)0)' failed
  Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 
7fc6008dd296 sp 7fff2df360f0 error 4 in 
libmutter-1.so.0.0.0[7fc6007f9000+13e000]
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error:
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read 
Wayland events: Connection reset by peer
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.868, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco
  Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 
known processed) with 0 events remaining.
  Sep 01 08:14:41 spiny gdm-launch-environment][8400]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3.
  Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default.
  Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission 
store...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets.
  Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket.
  Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System.
  Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown.
  Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session...
  Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 
(kill).
  Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121.
  Sep 01 08:14:41 spiny systemd[1]: Removed slice User Slice of gdm.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-

[Desktop-packages] [Bug 1720250] [NEW] im-config configuration ignored with gdm3

Public bug reported:

After having logged in via gdm3, the IM related environment variables
are always set like this:

$ env | grep -E '_IM|XMOD'
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus

Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
all other IM frameworks but IBus from working.

This problem seems to be similar to bug #1594681 (which was fixed).

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

** Affects: im-config (Ubuntu)
 Importance: High
 Status: New

** Also affects: im-config (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: im-config (Ubuntu)
   Importance: Undecided => High

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

Title:
  im-config configuration ignored with gdm3

Status in gdm3 package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New

Bug description:
  After having logged in via gdm3, the IM related environment variables
  are always set like this:

  $ env | grep -E '_IM|XMOD'
  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  Changing ~/.xinputrc to e.g. xim makes no difference, so gdm3 prevents
  all other IM frameworks but IBus from working.

  This problem seems to be similar to bug #1594681 (which was fixed).

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

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

** Changed in: libinput (Debian)
   Status: Unknown => 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/1715479

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Fix Committed
Status in libinput package in Debian:
  Confirmed
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint()

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8

  ---

  As of an upgrade to 3.25.91 (last session that did not exhibit this
  behavior was a 3.24.x session), I've experienced several crashes of
  the shell in the overview. journalctl shows the following output at
  the time of the crash:

  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: 
Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
  Sep 01 08:14:41 spiny gnome-shell[8506]: 
meta_renderer_native_release_onscreen: assertion 
'onscreen_native->gbm.next_fb_id == 0' failed
  Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 
'onscreen->winsys == ((void *)0)' failed
  Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 
7fc6008dd296 sp 7fff2df360f0 error 4 in 
libmutter-1.so.0.0.0[7fc6007f9000+13e000]
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error:
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read 
Wayland events: Connection reset by peer
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.868, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco
  Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 
known processed) with 0 events remaining.
  Sep 01 08:14:41 spiny gdm-launch-environment][8400]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3.
  Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default.
  Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission 
store...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets.
  Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket.
  Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System.
  Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown.
  Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session...
  Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 
(kill).
  Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121.
  Sep 01 08:14:41 spiny systemd[

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint()

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8

  ---

  As of an upgrade to 3.25.91 (last session that did not exhibit this
  behavior was a 3.24.x session), I've experienced several crashes of
  the shell in the overview. journalctl shows the following output at
  the time of the crash:

  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: 
Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
  Sep 01 08:14:41 spiny gnome-shell[8506]: 
meta_renderer_native_release_onscreen: assertion 
'onscreen_native->gbm.next_fb_id == 0' failed
  Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 
'onscreen->winsys == ((void *)0)' failed
  Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 
7fc6008dd296 sp 7fff2df360f0 error 4 in 
libmutter-1.so.0.0.0[7fc6007f9000+13e000]
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error:
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read 
Wayland events: Connection reset by peer
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.868, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco
  Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 
known processed) with 0 events remaining.
  Sep 01 08:14:41 spiny gdm-launch-environment][8400]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3.
  Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default.
  Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission 
store...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets.
  Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket.
  Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System.
  Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown.
  Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session...
  Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 
(kill).
  Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121.
  Sep 01 08:14:41 spiny systemd[1]: Removed slice User Slice of gdm.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8

[Desktop-packages] [Bug 1720227] Re: xdg-open snap:// results in a segfault

https://git.gnome.org/browse/gnome-software/commit/?h=wip/ubuntu-
master&id=d2e6e0104b48cd91855dad3adf4e5f86cbc60969

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

Title:
  xdg-open snap:// results in a segfault

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  0. pkill gnome-software
  1. Open Ubuntu Software from a terminal
  2. From another terminal run xdg-open snap://lxd
  3. Note that Software has now seg faulted

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

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

[Desktop-packages] [Bug 1720227] Re: xdg-open snap:// results in a segfault

https://errors.ubuntu.com/problem/b14424dca812b6167da1346383707ab577d0b2e0

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

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

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

Title:
  xdg-open snap:// results in a segfault

Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  0. pkill gnome-software
  1. Open Ubuntu Software from a terminal
  2. From another terminal run xdg-open snap://lxd
  3. Note that Software has now seg faulted

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

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

[Desktop-packages] [Bug 1720232] Re: /usr/bin/gnome-software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

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

** This bug has been marked a duplicate of bug 1720227
   xdg-open snap:// results in a segfault

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

Title:
  /usr/bin/gnome-
  
software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

Status in gnome-software package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1720213] Re: Word moving with left-arrow-ctrl broken in wayland

2017-09-28 Thread Egmont Koblinger

Is the behavior the same in other apps, e.g. gedit, libreoffice writer,
firefox, etc...?

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

Title:
  Word moving with left-arrow-ctrl broken in wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, Wayland session.

  In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right-
  arrow` moves the cursor one word to the left and to the right. In Xorg
  this works, no matter which key you press first (ctrl or arrow). In
  wayland, you have to press the ctrl key first, otherwise, the cursor
  will not move.

  # How to reproduce:

  type some words in gnome terminal press `left-arrow` key, wait for the
  cursor to move and, and press `ctrl`.

  # What happens

  The cursor first moves one character per "tick", and stops immediately
  when you press `ctrl`.

  # What should happen

  The cursor first moves one character per "tick", and starts moving one
  word per "tick" when you press `ctrl`.

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-28 Thread lavezarez

Firefox (55.0.2+build1-0ubuntu0.16.04.1) still crashing / unable to open
on my Asus Chromebook running crouton target lxde

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-28 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  New

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

2017-09-28 Thread Rachel Greenham

I can't reproduce this in Xorg on my non-nvidia machine (on which I
normally run Wayland because I can). It appears to be nvidia specific.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720232] [NEW] /usr/bin/gnome-software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

2017-09-28 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/b14424dca812b6167da1346383707ab577d0b2e0 
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-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

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

Title:
  /usr/bin/gnome-
  
software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

Status in gnome-software package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1720227] Re: xdg-open snap:// results in a segfault

2017-09-28 Thread Sebastien Bacher

bug #1720232 seems the corresponding e.u.c report

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

Title:
  xdg-open snap:// results in a segfault

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  0. pkill gnome-software
  1. Open Ubuntu Software from a terminal
  2. From another terminal run xdg-open snap://lxd
  3. Note that Software has now seg faulted

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

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

[Desktop-packages] [Bug 1720232] Re: /usr/bin/gnome-software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

2017-09-28 Thread Sebastien Bacher

bug #1720227 is probably the same issue

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

Title:
  /usr/bin/gnome-
  
software:11:g_type_check_instance:g_signal_handlers_disconnect_matched:set_app:gs_details_page_url_to_app_cb:g_task_return_now

Status in gnome-software package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1720234] [NEW] /usr/bin/gnome-software:11:g_mutex_lock:g_mutex_locker_new:gs_app_list_filter:gs_overview_page_get_featured_cb:g_task_return_now

2017-09-28 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/78b7635cf91dcadf2f57be1c091ac73d99aeb495 
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-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

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

Title:
  /usr/bin/gnome-
  
software:11:g_mutex_lock:g_mutex_locker_new:gs_app_list_filter:gs_overview_page_get_featured_cb:g_task_return_now

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.26.0-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/78b7635cf91dcadf2f57be1c091ac73d99aeb495 
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-software/+bug/1720234/+subscriptions

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

[Desktop-packages] [Bug 1720227] [NEW] xdg-open snap:// results in a segfault

2017-09-28 Thread Will Cooke

Public bug reported:

Steps to reproduce:

0. pkill gnome-software
1. Open Ubuntu Software from a terminal
2. From another terminal run xdg-open snap://lxd
3. Note that Software has now seg faulted

** Affects: gnome-software (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Confirmed

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

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

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

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

Title:
  xdg-open snap:// results in a segfault

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  0. pkill gnome-software
  1. Open Ubuntu Software from a terminal
  2. From another terminal run xdg-open snap://lxd
  3. Note that Software has now seg faulted

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

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

[Desktop-packages] [Bug 1720224] [NEW] cannot arrange the monitors differently

2017-09-28 Thread Carlos Gomes

Public bug reported:

in the widget display arrangement, one cannot drag a monitor in order to
position it on the other side or below the primary screen (using 2
screens)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu3
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-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 28 21:30:04 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-09-24 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Picture showing the window"
   
https://bugs.launchpad.net/bugs/1720224/+attachment/4958239/+files/Screenshot%20from%202017-09-28%2021-33-08.png

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

Title:
  cannot arrange the monitors differently

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

Bug description:
  in the widget display arrangement, one cannot drag a monitor in order
  to position it on the other side or below the primary screen (using 2
  screens)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu3
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 28 21:30:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-24 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720213] [NEW] Word moving with left-arrow-ctrl broken in wayland

Public bug reported:

Ubuntu 17.10, Wayland session.

In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right-
arrow` moves the cursor one word to the left and to the right. In Xorg
this works, no matter which key you press first (ctrl or arrow). In
wayland, you have to press the ctrl key first, otherwise, the cursor
will not move.

# How to reproduce:

type some words in gnome terminal press `left-arrow` key, wait for the
cursor to move and, and press `ctrl`.

# What happens

The cursor first moves one character per "tick", and stops immediately
when you press `ctrl`.

# What should happen

The cursor first moves one character per "tick", and starts moving one
word per "tick" when you press `ctrl`.

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

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


** Tags: artful wayland

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

** Tags added: artful

** Tags added: wayland

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

Title:
  Word moving with left-arrow-ctrl broken in wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10, Wayland session.

  In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right-
  arrow` moves the cursor one word to the left and to the right. In Xorg
  this works, no matter which key you press first (ctrl or arrow). In
  wayland, you have to press the ctrl key first, otherwise, the cursor
  will not move.

  # How to reproduce:

  type some words in gnome terminal press `left-arrow` key, wait for the
  cursor to move and, and press `ctrl`.

  # What happens

  The cursor first moves one character per "tick", and stops immediately
  when you press `ctrl`.

  # What should happen

  The cursor first moves one character per "tick", and starts moving one
  word per "tick" when you press `ctrl`.

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

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

I have the same issue - screen blank is enabled, suspend is disabled.
Using proprietary NVidia driver also.

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

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

[Desktop-packages] [Bug 1720199] Re: gvfs-open --help returns 1 exit code

2017-09-28 Thread Николай Кузьмин

** Summary changed:

- gvfs-open always returns 1 exit code
+ gvfs-open --help returns 1 exit code

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

Title:
  gvfs-open --help returns 1 exit code

Status in gvfs package in Ubuntu:
  New

Bug description:
  gvfs-open --help prints following text and fails

  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  /usr/bin/gvfs-open: 10: [: --help: unexpected operator
  /usr/bin/gvfs-open: 10: [: --help: unexpected operator
  gio: Unknown option --help

  Usage:
gio open LOCATION...

  Open files with the default application that
  is registered to handle files of this type.

  Reason:
  gvfs-open uses wrong comparison operator.
  command '[' compares strings using single '=' character. 
  '/usr/bin/[' and bash builtin [ also allow '==', but dash (which currently 
used as /bin/sh) requires '='.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gvfs-bin 1.34.0-0ubuntu1
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 22:42:59 2017
  InstallationDate: Installed on 2017-04-10 (171 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  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/1720199/+subscriptions

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

[Desktop-packages] [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep

Forgot to mention - running on the daily build of Ubuntu 17.10

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell itself segfaulting
  that's causing the login session to end?

  Not observed on my Wayland system.

  This is not new as of the current version of gnome-shell but I think
  it is relatively recent. Now my hackintosh partition is wrecked by a
  failed upgrade to High Sierra I'm using my Linux system more in
  earnest than before, so I'm hitting this often enough for it to
  provoke a bug report (and much of the time, to just turn all auto
  suspend/display-sleep off and instead shut down the computer when I'm
  leaving it for any length of time).

  The ubuntu bug reporter is not picking this up by itself, so I presume
  a crash report of the sort that uses is not being saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 14:41:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-30 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

** Changed in: epiphany-browser (Debian)
   Status: New => 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 Epiphany Browser:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in epiphany-browser package in Debian:
  Confirmed

Bug description:
  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/epiphany-browser/+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 1716470] Re: xdg-open doesn't respect gnome3 associations

2017-09-28 Thread Николай Кузьмин

I've investigated a bit, this is actually gvfs-open bug.
It uses '[ str1 == str2 ]' to compare strings, which is wrong. When /bin/sh is 
a bash it is ok, bash builtin forgives that mistake, but when /bin/sh is a 
symlink to a dash shell, dash's builtin '[' command fails.
Filled bug https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1720199

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

Title:
  xdg-open doesn't respect gnome3 associations

Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  xdg-open internaly uses "gvfs-open --help" to check if gvfs-open is present 
and functional, but gvfs-open is deprecated in new gnome (3.25.90) and 
"gvfs-open --help" returns with error code = 1.
  gvfs-open still can be used to open files and urls, new way to open 
associated files is "gio open ARG".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xdg-utils 1.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 11 23:59:06 2017
  InstallationDate: Installed on 2017-04-10 (154 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to artful on 2017-09-10 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1716470/+subscriptions

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

[Desktop-packages] [Bug 1264713] Re: [Acer Aspire 5750-9668] Tapping top right of touchpad pastes undesirably

2017-09-28 Thread Vasya Pupkin

I have the same issue and thanks for the workaround. I wish there was
some permanent one, though.

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

Title:
  [Acer Aspire 5750-9668] Tapping top right of touchpad pastes
  undesirably

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Invalid

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  2) uname -a
  Linux monikerpc 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 
x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy xserver-xorg-input-synaptics
  xserver-xorg-input-synaptics:
    Installed: 1.7.1-0ubuntu1
    Candidate: 1.7.1-0ubuntu1
    Version table:
   *** 1.7.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is if one taps the top right of the
  touchpad, it does not paste anything.

  4) What happens instead is it consistently pastes. Unfortunately,
  there are no settings exposed by the GUI in Applications Menu ->
  Settings -> Mouse and Touchpad to adjust this. As well, this is
  despite in that menu -> tab Devices -> checkbox Disable touchpad while
  typing is unchecked. This is quite inconvenient as one could have
  their mouse towards the top of the screen, scrolling with the touchpad
  and not notice things are being pasted unintentionally. Hence, this
  functionality should be opt-in, versus opt-out.

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input8
  U: Uniq=
  H: Handlers=mouse0 event12
  B: PROP=9
  B: EV=b
  B: KEY=6420 3 0 0 0 0
  B: ABS=26080001103

  WORKAROUND: Change RTCornerButton=2 to 0 via:
  synclient RTCornerButton=0

  WORKAROUND: Ensure one does not accidentally use a clicking motion on
  the top right of the touchpad when scrolling.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  moniker1532 F pulseaudio
   /dev/snd/pcmC0D0p:   moniker1532 F...m pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Dec 28 11:05:43 2013
  HibernationDevice: RESUME=UUID=2acfb304-f013-4949-80e4-1ecdd0cb0632
  InstallationDate: Installed on 2013-12-19 (9 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131219)
  MachineType: Acer Aspire 5750
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic 
root=UUID=83e7409a-0aa3-4a56-b32e-294c6722287f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750:pvrV1.21:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21:
  dmi.product.name: Aspire 5750
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1264713/+subscriptions

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

[Desktop-packages] [Bug 1720199] [NEW] gvfs-open --help returns 1 exit code

2017-09-28 Thread Николай Кузьмин

Public bug reported:

gvfs-open --help prints following text and fails

This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

/usr/bin/gvfs-open: 10: [: --help: unexpected operator
/usr/bin/gvfs-open: 10: [: --help: unexpected operator
gio: Unknown option --help

Usage:
  gio open LOCATION...

Open files with the default application that
is registered to handle files of this type.

Reason:
gvfs-open uses wrong comparison operator.
command '[' compares strings using single '=' character. 
'/usr/bin/[' and bash builtin [ also allow '==', but dash (which currently used 
as /bin/sh) requires '='.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gvfs-bin 1.34.0-0ubuntu1
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-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 28 22:42:59 2017
InstallationDate: Installed on 2017-04-10 (171 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  gvfs-open --help returns 1 exit code

Status in gvfs package in Ubuntu:
  New

Bug description:
  gvfs-open --help prints following text and fails

  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  /usr/bin/gvfs-open: 10: [: --help: unexpected operator
  /usr/bin/gvfs-open: 10: [: --help: unexpected operator
  gio: Unknown option --help

  Usage:
gio open LOCATION...

  Open files with the default application that
  is registered to handle files of this type.

  Reason:
  gvfs-open uses wrong comparison operator.
  command '[' compares strings using single '=' character. 
  '/usr/bin/[' and bash builtin [ also allow '==', but dash (which currently 
used as /bin/sh) requires '='.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gvfs-bin 1.34.0-0ubuntu1
  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-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 28 22:42:59 2017
  InstallationDate: Installed on 2017-04-10 (171 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  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/1720199/+subscriptions

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

Uploaded the cherry-picked patch

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

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Fix Committed
Status in libinput package in Debian:
  Unknown
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Fix Committed
Status in libinput package in Debian:
  Unknown
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

2017-09-28 Thread James Henstridge

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

** Also affects: libinput (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1448962
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Triaged
Status in libinput package in Debian:
  Unknown
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

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

** Also affects: gnome-shell (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873523
   Importance: Unknown
   Status: Unknown

** Package changed: gnome-shell (Debian) => libinput (Debian)

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Triaged
Status in libinput package in Debian:
  Unknown
Status in libinput package in Fedora:
  Unknown

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-28 Thread Mitsuya Shibata

NOTE:
"IBUS_ENABLE_SYNC_MODE=0" will be fix on Korean and xim problems.
However this fix will be cause with Java application.
Please refer: https://github.com/ibus/ibus/issues/1847#issuecomment-205230677

** Bug watch added: github.com/ibus/ibus/issues #1847
   https://github.com/ibus/ibus/issues/1847

** Patch added: "sample debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+attachment/4958191/+files/im-config.debdiff

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  New

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

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

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

** Package changed: gnome-settings-daemon (Ubuntu) => libinput (Ubuntu)

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

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

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Triaged

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715479/+subscriptions

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

2017-09-28 Thread James Henstridge

While looking around for code that might resume the touchpad, I noticed
that the libinput master code was a bit different to the version we
ship: there's a tp_resume_conditional() function that checks sendevents.

And checking the history shows up this patch:

https://cgit.freedesktop.org/wayland/libinput/commit/src?id=53d53dd18ef14484d632421027cd7b6130013cf0

Fedora is also shipping this as a patch against their libinput-1.8.2 in
Fedora 27:

  https://src.fedoraproject.org/rpms/libinput/blob/f27/f/0001-touchpad-
don-t-resume-a-disabled-touchpad.patch

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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-settings-daemon/+bug/1715479/+subscriptions

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

[Desktop-packages] [Bug 1720184] [NEW] Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-28 Thread Mitsuya Shibata

Public bug reported:

Please merge im-config 0.32-1 (main) from Debian unstable (main)

Changelogs from ubuntu package:

im-config (0.32-1) unstable; urgency=medium

  [ HIGUCHI Daisuke (VDR dai) ]
  * Disable uim-toolbar-gtk{,3}-systray due to outdated.   
- They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}). 
  
  * Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
  * Wait a sec before starting uim-toolbar.
- uim-toolbar's spawning is too faster than desktop environment's starting. 
  

 -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

im-config (0.31-1) unstable; urgency=medium

  [ Osamu Aoki ]   
  * Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, #876794 
  
  * Add Czech language strings to the desktop file.  Closes: #868036 
  * im-config -l doesn't need GUI.  Closes: #804067
  * Update PO with trivial unfuzzy. 

  [ Boyuan Yang ]
  * Refresh debian/copyright file as machine-readable format.

 -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

im-config (0.30-1) unstable; urgency=medium

  * New upstream release acknowledging all NMU patches.

 -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

** Affects: im-config (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

Status in im-config package in Ubuntu:
  New

Bug description:
  Please merge im-config 0.32-1 (main) from Debian unstable (main)

  Changelogs from ubuntu package:

  im-config (0.32-1) unstable; urgency=medium

[ HIGUCHI Daisuke (VDR dai) ]
* Disable uim-toolbar-gtk{,3}-systray due to outdated.   
  - They are outdated, buggy and have alternatives (uim-toolbar-gtk{,3}).   

* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).   
* Wait a sec before starting uim-toolbar.
  - uim-toolbar's spawning is too faster than desktop environment's 
starting.   

   -- Osamu Aoki   Wed, 27 Sep 2017 21:15:24 +0900

  im-config (0.31-1) unstable; urgency=medium

[ Osamu Aoki ]   
* Start ibus with IBUS_ENABLE_SYNC_MODE=0.  Closes: #812826, #838318, 
#876794   
* Add Czech language strings to the desktop file.  Closes: #868036 
* im-config -l doesn't need GUI.  Closes: #804067
* Update PO with trivial unfuzzy. 

[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.

   -- Osamu Aoki   Tue, 26 Sep 2017 22:41:36 +0900

  im-config (0.30-1) unstable; urgency=medium

* New upstream release acknowledging all NMU patches.

   -- Osamu Aoki   Wed, 07 Dec 2016 22:00:16 +0900

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

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

[Desktop-packages] [Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend

2017-09-28 Thread James Henstridge

So, I don't think there is any problem on the gnome-control-center side:
it just sets the org.gnome.desktop.peripherals.touchpad/send-events
GSetting key to disabled, and that is persisting over sleeps.

The code in mutter watches this key, and calls
MetaInputSettings::set_send_events() on each touchpad device, and
ensures it is called on each new input device.

https://git.gnome.org/browse/mutter/tree/src/backends/meta-input-
settings.c#n667

In a Wayland session, this calls
libinput_device_config_send_events_set_mode():

https://git.gnome.org/browse/mutter/tree/src/backends/native/meta-input-
settings-native.c#n36

The touchpad implementation of this is found here:

https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt-
touchpad.c#n3089

... which calls tp_suspend:

https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt-
touchpad.c#n1670

Which will either leave the touchpad enabled to support soft buttons, or
call evdev_device_suspend() otherwise, which closes the underlying
device.

Looking in /proc, gnome-shell definitely doesn't have the touchpad evdev
device open when I disable the touchpad, but somehow opens it again
after resume.

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

Title:
  Touchpad won't stay disabled after resuming from suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I've disabled my touchpad using the mouse and touchpad control panel
  however it does not last very long i.e. after I've disabled it, it
  somehow becomes enabled even though the control panel continues to
  show it as disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 12:47:26 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-01-22 (593 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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-settings-daemon/+bug/1715479/+subscriptions

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

[Desktop-packages] [Bug 1720177] [NEW] [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] Background noise or low volume

2017-09-28 Thread Khan Rafin Ahmed

Public bug reported:

Sound Quality is poor. When I am powering up the volume to 100% audio
sounds distorted. I am using Windows 8.1 in this very laptop as well
where the audio is working perfectly. So, it's not a hardware related
problem. Audio level is low too. Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   rafin  1677 F...m pulseaudio
 /dev/snd/controlC0:  rafin  1677 F pulseaudio
CurrentDesktop: Unity
Date: Thu Sep 28 22:02:35 2017
InstallationDate: Installed on 2017-09-25 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_Type: High background noise, or volume is too low
Title: [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] 
Background noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IRR Ver. F.40
dmi.board.name: 17F6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 58.1D
dmi.chassis.asset.tag: 2CE3070VGQ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.40:bd01/29/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1009002:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4540s
dmi.product.version: A1009002
dmi.sys.vendor: Hewlett-Packard

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI]
  Background noise or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound Quality is poor. When I am powering up the volume to 100% audio
  sounds distorted. I am using Windows 8.1 in this very laptop as well
  where the audio is working perfectly. So, it's not a hardware related
  problem. Audio level is low too. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   rafin  1677 F...m pulseaudio
   /dev/snd/controlC0:  rafin  1677 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 28 22:02:35 2017
  InstallationDate: Installed on 2017-09-25 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: High background noise, or volume is too low
  Title: [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.40
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1D
  dmi.chassis.asset.tag: 2CE3070VGQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.40:bd01/29/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1009002:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1009002
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720177/+subscriptions

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

[Desktop-packages] [Bug 1617620] Re: Autorun files from Removable Media

Hi,

To get the default changed, could you please file a bug with the
upstream GNOME project here:

https://bugzilla.gnome.org/

Once you've filed the bug, please like the upstream bug to this one.

Thanks!

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

Title:
  Autorun files from Removable Media

Status in gsettings-desktop-schemas package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16 is still automatically executing software that resides in an
  external resource (removable media), such as USB or CD.

  I don't need to tell you how bad this is..

  ---

  You can see the default value that allows to autoplay / autorun files
  by doing the following steps:

  1. In Ubuntu 16.04, go to Settings -> Details.
  2. In the left pane choose "Removable Media".
  3. On the right pane you'll see "Software", while the value in the drop-down 
menu is "Run Software".

  ---

  A fix suggestion:
  Instead of "Run Software", the default value should be "Do nothing".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1617620/+subscriptions

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

[Desktop-packages] [Bug 1710350] Re: black screen after suspend

2017-09-28 Thread Fusion

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

Title:
  black screen after suspend

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 17.10 (gnome 3.24.2)
  4.11.0-13-generic
  GeForce GTX 1050 Ti/PCIe/SSE2 - 384.59
  AMD® Fx(tm)-4170 quad-core processor × 4
  monitor 3840x2160 (dvi)

  It happens on 1 of 3 times. I don't know what causes that.

  When I am going to leave my pc for several hours I put it first on
  suspend/sleep mode. At about one third of resumes (from suspend mode)
  a black screen occurs and there is nothing I could do about it (except
  from hard reset). If something is pressed by keyboard like
  'ctrl+alt+F1' or F2, screen starts again black (it searches for signal
  - backlight turned on - working mode). If nothing is pressed by
  keyboard, the screen closes after 1-2sec (backlight turned off -
  standby mode).

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

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

[Desktop-packages] [Bug 1720150] Re: Windows not scaled in hidpi setups using "Ubuntu Xorg" session.

** Changed in: gnome-settings-daemon
   Status: Unknown => Confirmed

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

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

Title:
  Windows not scaled in hidpi setups using "Ubuntu Xorg" session.

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

Bug description:
  Windows are not scaled on 17.10 using "Ubuntu Xorg" session.

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

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

[Desktop-packages] [Bug 1717346] Re: When starting up after running down the battery, it will sometimes not go into the lock screen and instead going directly to the desktop.

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

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

Title:
  When starting up after running down the battery, it will sometimes not
  go into the lock screen and instead going directly to the desktop.

Status in gnome-screensaver package in Ubuntu:
  Triaged

Bug description:
  When starting up after running the battery down on my laptop, it will
  go directly to the desktop instead of going to the lock screen. This
  does not happen if it was shut down correctly or from suspension or
  hibernate. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-screensaver 3.6.1-7ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 14 13:39:44 2017
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2017-09-06 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8

  ---

  As of an upgrade to 3.25.91 (last session that did not exhibit this
  behavior was a 3.24.x session), I've experienced several crashes of
  the shell in the overview. journalctl shows the following output at
  the time of the crash:

  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: 
Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
  Sep 01 08:14:41 spiny gnome-shell[8506]: 
meta_renderer_native_release_onscreen: assertion 
'onscreen_native->gbm.next_fb_id == 0' failed
  Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 
'onscreen->winsys == ((void *)0)' failed
  Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 
7fc6008dd296 sp 7fff2df360f0 error 4 in 
libmutter-1.so.0.0.0[7fc6007f9000+13e000]
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error:
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read 
Wayland events: Connection reset by peer
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.868, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco
  Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 
known processed) with 0 events remaining.
  Sep 01 08:14:41 spiny gdm-launch-environment][8400]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3.
  Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default.
  Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission 
store...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets.
  Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket.
  Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System.
  Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown.
  Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session...
  Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 
(kill).
  Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121.
  Sep 01 08:14:41 spiny systemd[1]: Removed slice User Slice of gdm.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-ge

[Desktop-packages] [Bug 1719782] Re: problem

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  problem

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  give me proper update for my system

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: openafs wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 27 11:33:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c2]
  InstallationDate: Installed on 2016-11-24 (306 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro plymouth:debug splash quiet 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd04/14/2017:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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 2:1.18.4-0ubuntu0.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 26 23:06:47 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20049 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.5

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

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

[Desktop-packages] [Bug 1719821] Re: haven't been able to truely downn

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  haven't been able to truely downn

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  packages. everything is only halfoperating
  . I am a newbie to computers as it is so I  dont fully understand what needs 
tobe done all the time or how to adjust thing to fitwhat I'm doing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 27 05:20:21 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.10.0-35-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:fb20]
  InstallationDate: Installed on 2017-09-21 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite C855
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-36-generic.efi.signed 
root=UUID=40c6e0e5-3568-4c9a-92dd-13d7316eb99f ro nopat plymouth:debug 
vesafb.invalid=1 drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.60
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.60:bd01/14/2013:svnTOSHIBA:pnSatelliteC855:pvrPSCBLU-02J006:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C855
  dmi.product.version: PSCBLU-02J006
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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: Wed Sep 27 03:47:53 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1720169] [NEW] [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background noise or low volume

2017-09-28 Thread efrain avila

Public bug reported:

White noise all the time, no matter volume level. I tried disable power
save option. It didn't work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  efrain 1971 F pulseaudio
CurrentDesktop: Unity
Date: Thu Sep 28 10:10:31 2017
InstallationDate: Installed on 2017-04-03 (178 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Audio Interno - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: High background noise, or volume is too low
Title: [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background 
noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.9
dmi.board.name: 0Y7WYT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.9:bd02/06/2017:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7040
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-28T10:04:33.733342

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front]
  Background noise or low volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  White noise all the time, no matter volume level. I tried disable
  power save option. It didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  efrain 1971 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 28 10:10:31 2017
  InstallationDate: Installed on 2017-04-03 (178 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: High background noise, or volume is too low
  Title: [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.9
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.9:bd02/06/2017:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-28T10:04:33.733342

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720169/+subscriptions

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

[Desktop-packages] [Bug 1642447] Re: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versã

2017-09-28 Thread Mattia Rizzolo

You'll need to install the same version of the i386 package together.  I
don't know what you were running, but please try to contact user support
instead.

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

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

Title:
  package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote
  libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois
  libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1)

Status in graphite2 package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  libgraphite2-3:
Instalado: 1.3.9-1
Candidato: 1.3.9-1
Tabela de versão:
   *** 1.3.9-1 500
  500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 
Packages
  500 http://mirror.ufscar.br/ubuntu zesty-proposed/main amd64 Packages
  100 /var/lib/dpkg/status
   1.3.8-1ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://cz.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty/main amd64 Packages
  500 http://mirror.ufscar.br/ubuntu zesty/main amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgraphite2-3:amd64 1.3.9-1
  ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
  Uname: Linux 4.9.0-1-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Thu Nov 17 00:03:37 2016
  Dependencies:
   gcc-6-base 6.2.0-13ubuntu1
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-13ubuntu1
  ErrorMessage: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado 
pois libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1)
  InstallationDate: Installed on 2016-02-11 (279 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote 
libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 
tem uma versão diferente (1.3.8-1ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717737] Re: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status

2017-09-28 Thread Mattia Rizzolo

We'll need more than just the final error message to even start to
imagine what's happening here.

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

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

Title:
  package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade:
  package libgraphite2-3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in graphite2 package in Ubuntu:
  Incomplete

Bug description:
  tried to install gcc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libgraphite2-3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 16 19:44:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2017-09-16  19:44:19
   Commandline: apt-get install gcc
   Requested-By: kev (1000)
  DpkgTerminalLog:
   dpkg: error processing package libgraphite2-3:amd64 (--configure):
package libgraphite2-3:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-07-03 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720142] Re: For 1719254

2017-09-28 Thread dino99

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

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

Title:
  For 1719254

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  For bug report 1719254

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 28 19:25:32 2017
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 
2017-09-16T22:30:01.532539

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

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

[Desktop-packages] [Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()

2017-09-28 Thread Sebastien Bacher

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  shell_gtk_embed_window_created_cb() from g_closure_invoke() from
  signal_emit_unlocked_R()

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

Bug description:
  https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 02:41:44 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (562 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
   PC (0x7feb5dff7e26) ok
   source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/gnome-shell/libgnome-shell.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1719254] Re: freeze and crashes while playing video or using multimedia files

2017-09-28 Thread Aravind R

I dont know I just stuck in terminal as

Ign http://dl.google.com/linux/chrome/deb stable InRelease 
Get:1 http://repo.mysql.com/apt/ubuntu xenial InRelease [19.1 kB]  
Get:2 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]   
Get:3 http://archive.canonical.com/ubuntu xenial InRelease [11.5 kB]   
Get:4 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial InRelease 
[24.3 kB]
Get:5 http://dl.google.com/linux/chrome/deb stable Release [1189 B]
Get:6 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B] 
Get:7 http://ppa.launchpad.net/mkusb/ppa/ubuntu xenial InRelease [18.0 kB] 
Get:8 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]   
Get:9 http://archive.canonical.com/ubuntu xenial/partner amd64 Packages [3128 B]
Get:10 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1396 B]
Get:11 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:12 http://ppa.launchpad.net/morphis/anbox-support/ubuntu xenial InRelease 
[17.5 kB]
Get:13 http://archive.ubuntu.com/ubuntu xenial-security InRelease [102 kB] 
Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1201 kB]   
Get:15 http://repo.mysql.com/apt/ubuntu xenial/mysql-cluster-7.5 Sources [991 B]
Get:16 http://repo.mysql.com/apt/ubuntu xenial/mysql-apt-config amd64 Packages 
[563 B]
Get:17 http://ppa.launchpad.net/noobslab/icons/ubuntu xenial InRelease [17.5 kB]
Get:18 http://download.virtualbox.org/virtualbox/debian xenial InRelease [7877 
B]
Get:19 http://repo.mysql.com/apt/ubuntu xenial/mysql-cluster-7.5 amd64 Packages 
[4538 B]
Get:20 http://repo.mysql.com/apt/ubuntu xenial/mysql-tools amd64 Packages [2872 
B]
Get:21 http://ppa.launchpad.net/noobslab/icons2/ubuntu xenial InRelease [17.5 
kB]
Get:22 https://download.sublimetext.com apt/stable/ InRelease [2562 B] 
Get:23 http://ppa.launchpad.net/noobslab/themes/ubuntu xenial InRelease [17.6 
kB]
Get:24 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 
Packages [1469 B]
Get:25 https://download.sublimetext.com apt/stable/ Packages [729 B]   
Get:26 http://deb.torproject.org/torproject.org xenial InRelease [3536 B]  
Get:27 http://ppa.launchpad.net/snwh/pulp/ubuntu xenial InRelease [17.5 kB]
Get:28 http://deb.torproject.org/torproject.org xenial/main amd64 Packages 
[4596 B]
Get:29 http://ppa.launchpad.net/tista/adapta/ubuntu xenial InRelease [17.5 kB] 
Get:30 https://dl.winehq.org/wine-builds/ubuntu xenial InRelease [4701 B]  
Get:31 http://ppa.launchpad.net/tsbarnes/indicator-keylock/ubuntu xenial 
InRelease [17.6 kB]
Get:32 https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages 
[17.7 kB]
Get:33 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main amd64 
Packages [12.4 kB]
Get:34 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata [733 
kB]
Get:35 http://ppa.launchpad.net/mkusb/ppa/ubuntu xenial/main amd64 Packages 
[1384 B]
Get:36 http://ppa.launchpad.net/morphis/anbox-support/ubuntu xenial/main amd64 
Packages [656 B]
Get:37 http://ppa.launchpad.net/noobslab/icons/ubuntu xenial/main amd64 
Packages [13.2 kB]
Get:38 http://ppa.launchpad.net/noobslab/icons2/ubuntu xenial/main amd64 
Packages [2584 B]
Get:39 http://ppa.launchpad.net/noobslab/themes/ubuntu xenial/main amd64 
Packages [6036 B]
Get:40 http://ppa.launchpad.net/snwh/pulp/ubuntu xenial/main amd64 Packages 
[768 B]
Get:41 http://ppa.launchpad.net/tista/adapta/ubuntu xenial/main amd64 Packages 
[680 B]
Get:42 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 kB]
Get:43 http://ppa.launchpad.net/tsbarnes/indicator-keylock/ubuntu xenial/main 
amd64 Packages [591 B]
Get:44 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages [8344 
B]
Get:45 http://archive.ubuntu.com/ubuntu xenial/restricted amd64 DEP-11 Metadata 
[186 B]
Get:46 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB]
Get:47 http://archive.ubuntu.com/ubuntu xenial/universe amd64 DEP-11 Metadata 
[3410 kB]
Get:48 http://archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons 
[7448 kB]
Get:49 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 
kB]
Get:50 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 DEP-11 Metadata 
[63.8 kB]
Get:51 http://archive.ubuntu.com/ubuntu xenial/multiverse DEP-11 64x64 Icons 
[230 kB]
Get:52 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [633 
kB]
Get:53 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 
Metadata [305 kB]
Get:54 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons 
[211 kB]
Get:55 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
Packages [7972 B]
Get:56 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 DEP-11 
Metadata [157 B]
Get:57 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 
[538 kB

[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful

2017-09-28 Thread Ldx

(I post here the same comment I posted for duplicate bug #1716277):

Same issue on my Ubuntu 17.10 beta, freshly installed (no upgrade).

Just for completeness, this behaviour happens by just dragging any file
from desktop to any other window of nautilus.

Dragging from nautilus to desktop works.
Dragging from nautilus to another nautilus windows works.
Cut/Paste from/to desktop works.

It's the dragging action from desktop that looks flawed.

If useful, here is a screen recording that shows the issue (well, the
initial mouse drag and subsequent click attempts are not clearly visible
but I think that one can get the idea of the problem):

https://www.dropbox.com/s/kjzqucqb7hdcnvy/Screencast_drag_issue_ubuntu-17-10-beta.mp4?dl=0

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

Title:
can't drag file from desktop to folder window on Artful

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

Bug description:
I'm running Ubuntu 17.10 (Artful). If I create a text file on my
desktop and then attempt to drag it into a Nautilus folder window, it
fails: when I release the mouse cursor over the folder window nothing
happens and the file is not moved.

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

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

[Desktop-packages] [Bug 1720149] [NEW] gnome-shell segv on wake from display or system sleep

2017-09-28 Thread Rachel Greenham

Public bug reported:

The observable symptom is that if I go away and let the computer go
either to display sleep or suspend, when I come back and try to wake it
up again, I find myself, after sliding up the lock screen, at the gdm
login screen. I'm logged out, and logging in gives me a fresh new
session. Anything I had open in the previous session is lost. (I'm
getting used to saving stuff before I step away from the computer!)

The only trace I've been able to find is that in /var/log/syslog I see a
line like:

Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
libmutter-1.so.0.0.0[7f6200de4000+14]

This happens at the time of attempted wake, not the time of going to
sleep. It's preceded by a lot of activity from gdm-x-session that I'm
not sure is indicating any error, just the process of waking up. I will
attach a portion of syslog surrounding the whole event in the hope it
helps. (In fact attaching the whole current syslog file - it has two
such events occuring in it, first display sleep/wake at 09:02 this
morning, and secondly (because I was experimenting) a suspend-wake at
14:38 this afternoon.

This is only affecting Xorg sessions, and may possibly only be affecting
where nvidia is in use, I'm not sure about that. But the fact it occurs
on display wake alone, not needing the system itself to have suspended
(I was trying suspend to see if it *avoided* the problem, which it
doesn't), does point the finger in that direction I guess. But
ultimately I'm guessing it's gnome-shell itself segfaulting that's
causing the login session to end?

Not observed on my Wayland system.

This is not new as of the current version of gnome-shell but I think it
is relatively recent. Now my hackintosh partition is wrecked by a failed
upgrade to High Sierra I'm using my Linux system more in earnest than
before, so I'm hitting this often enough for it to provoke a bug report
(and much of the time, to just turn all auto suspend/display-sleep off
and instead shut down the computer when I'm leaving it for any length of
time).

The ubuntu bug reporter is not picking this up by itself, so I presume a
crash report of the sort that uses is not being saved.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
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-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 28 14:41:07 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-07-30 (59 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago)

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


** Tags: amd64 apport-bug artful

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1720149/+attachment/4958094/+files/syslog

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

Title:
  gnome-shell segv on wake from display or system sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The observable symptom is that if I go away and let the computer go
  either to display sleep or suspend, when I come back and try to wake
  it up again, I find myself, after sliding up the lock screen, at the
  gdm login screen. I'm logged out, and logging in gives me a fresh new
  session. Anything I had open in the previous session is lost. (I'm
  getting used to saving stuff before I step away from the computer!)

  The only trace I've been able to find is that in /var/log/syslog I see
  a line like:

  Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]:
  segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in
  libmutter-1.so.0.0.0[7f6200de4000+14]

  This happens at the time of attempted wake, not the time of going to
  sleep. It's preceded by a lot of activity from gdm-x-session that I'm
  not sure is indicating any error, just the process of waking up. I
  will attach a portion of syslog surrounding the whole event in the
  hope it helps. (In fact attaching the whole current syslog file - it
  has two such events occuring in it, first display sleep/wake at 09:02
  this morning, and secondly (because I was experimenting) a suspend-
  wake at 14:38 this afternoon.

  This is only affecting Xorg sessions, and may possibly only be
  affecting where nvidia is in use, I'm not sure about that. But the
  fact it occurs on display wake alone, not needing the system itself to
  have suspended (I was trying suspend to see if it *avoided* the
  problem, which it doesn't), does point the finger in that direction I
  guess. But ultimately I'm guessing it's gnome-shell

[Desktop-packages] [Bug 1720150] [NEW] Windows not scaled in hidpi setups using "Ubuntu Xorg" session.

Public bug reported:

Windows are not scaled on 17.10 using "Ubuntu Xorg" session.

** Affects: gnome-settings-daemon
 Importance: Unknown
 Status: Unknown

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

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

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

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

Title:
  Windows not scaled in hidpi setups using "Ubuntu Xorg" session.

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Windows are not scaled on 17.10 using "Ubuntu Xorg" session.

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

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

[Desktop-packages] [Bug 1720142] Re: For 1719254

2017-09-28 Thread Aravind R

Kindly delete or ignore this.

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

Title:
  For 1719254

Status in nautilus package in Ubuntu:
  New

Bug description:
  For bug report 1719254

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 28 19:25:32 2017
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 
2017-09-16T22:30:01.532539

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

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

[Desktop-packages] [Bug 1720142] [NEW] For 1719254

2017-09-28 Thread Aravind R

Public bug reported:

For bug report 1719254

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 28 19:25:32 2017
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 
2017-09-16T22:30:01.532539

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


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

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

Title:
  For 1719254

Status in nautilus package in Ubuntu:
  New

Bug description:
  For bug report 1719254

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 28 19:25:32 2017
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 
2017-09-16T22:30:01.532539

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

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

[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

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

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

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in kscreenlocker package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  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/ecryptfs/+bug/1085706/+subscriptions

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

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

2017-09-28 Thread Stephen Allen

I can't even get vpn and/or socks5 to work. This is dangerous, perhaps
it should be stressed that people shouldn't use 11.10 as a daily OS
until this is fixed. I know, I know, me should know better. I'm just
glad I checked before assuming I was in a secure tunnel. Otherwise 11.10
is working fine without any show stoppers for moi.

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

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

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

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

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

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

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

[Desktop-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-09-28 Thread chenzero

I tried the Artful image.
on the Artful image, it doesn't need to change any settings, the adapter is 
automatically recognized as 148f:7601, however, the same vendor request -110 
error in the dmesg log.

Please see the attached artful-image.txt

Thanks!


** Attachment added: "artful-image.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/4958084/+files/artful-image.txt

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 fai

[Desktop-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

2017-09-28 Thread ChristianEhrhardt

The remaining trusty task is fixed in curtin according to c#29 as well,
updating the tasks to match that.

** Changed in: maas (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Committed
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Fix Released
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)

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

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

[Desktop-packages] [Bug 1719777] Re: Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug fixes and performance improvements

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

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

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

Title:
  Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug
  fixes and performance improvements

Status in pitivi package in Ubuntu:
  Confirmed

Bug description:
  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
  22 and is already packaged in Debian unstable - I'm pasting
  debian/changelog since 0.98.1 version which is currently in Ubuntu
  artful:

  pitivi (0.99-2) unstable; urgency=medium

* debian/patches/0001-Don-t-require-gst-validate-to-be-available.patch:
  + Don't require gst-validate to be available (Closes: #876607)

   -- Sebastian Dröge   Sun, 24 Sep 2017 09:46:35
  +0300

  pitivi (0.99-1) unstable; urgency=medium

* New upstream release

   -- Sebastian Dröge   Sat, 23 Sep 2017 14:28:52
  +0300

  Explanation of FeatureFreeze exception:
  0.99 release is just big bugfix, no new features, but many bug fixes and 
performance improvements, test suite grew considerably, from 164 to 191 
meaningful unit tests, see https://git.gnome.org/browse/pitivi/log/?h=1.0

  Please sync Pitivi packages from Debian unstable before 17.10 release.

  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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

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

[Desktop-packages] [Bug 1718850] Re: System extensions appear off by default

Are you going to work on it?

If not, this is Won't Fix in Launchpad.

** Tags removed: rls-aa-incoming

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

Title:
  System extensions appear off by default

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-tweak-tool package in Ubuntu:
  New

Bug description:
  Go to the Extensions panel in Tweaks.
  System extensions (dock and appindicators) appear off by default, where they 
are obviously not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-tweak-tool 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 08:02:59 2017
  ExecutablePath: /usr/bin/gnome-tweak-tool
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SourcePackage: gnome-tweak-tool
  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/1718850/+subscriptions

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

[Desktop-packages] [Bug 208217] Re: Masks don't work on print or PDF

2017-09-28 Thread hanan

I think this bug is back again in Inkscape 0.92+ (Fedora 26 but not
exist in inkscape flatpak), and when I tried to set a mask by a
rectangle full with gradient from white to black, the shape disappeared,
when I released the mask again the rectangle turned to black without
gradient. I tried this process again but I inverted the gradient (Black
is up and white is down) and the after (mask- set) step, the shape still
itself without any transparency, when I released the mask the rectangle
turned to  completely white this time. so I think the bug is that the
mask set by one color from the gradient, almost it is the second color
as I noticed.

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

Title:
  Masks don't work on print or PDF

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released

Bug description:
  When printing on 0.46 branch, objects with masks don't appear on the
  print.

  In the attached picture, the turtle sitting in the water has a mask
  with a gradient to make his feet fade into the water. He prints fine
  in 0.45.1, but in 0.46 branch he's gone.

  Exporting to bitmap works fine on 0.46. Printing to bitmap (Render as
  bitmap) works fine also on 0.46. Save as PDF via cairo keeps the
  turtle but loses all blurs (blurs not implemented in PDF) and the
  mask, so his legs are fully visible. I think PDF should be capable of
  a blend to transparent, because the leaves on the bushes blend to
  transparent and they export to pdf beautifully.

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

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

[Desktop-packages] [Bug 1720133] [NEW] USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer

2017-09-28 Thread Szymon Kunc

Public bug reported:

[Impact]

* This impacts all Ubuntu releases which received an update of x.org to
1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

* End users are unable to use their USB displays unless they workaround
the problem which currently involves disabling pageflip for modesetting
in x.org.conf file

* The fix which has been submitted to x.org extends blacklisting
mechanism so the EVDI kernel module which is essential for DisplayLink
USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME
sync is disabled in such case; The patch can be found here:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

[Test Case]

1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54
downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed
requirements and instructions can be found here:
2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking
station
3. Plug in an external monitor (HDMI or DisplayPort) to the docking station

Expected result:
The external monitor should light up and show the desktop

Actual result:
The monitor remains black or shows frozen desktop.

[Regression Potential]

* The patchset extends number of modules for which x.org changes its
functionality. It checks if "evdi" string is in the syspath so it is
quite unlikely there would be any impact on anything else then USB 3.0
displays which use EVDI module.

[Other Info]

* The patch has been applied to Ubuntu x.org source code built and tested.

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

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

Title:
USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or
newer

Status in xorg package in Ubuntu:
New

Bug description:
[Impact]

* This impacts all Ubuntu releases which received an update of x.org
to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10

* End users are unable to use their USB displays unless they
workaround the problem which currently involves disabling pageflip for
modesetting in x.org.conf file

* The fix which has been submitted to x.org extends blacklisting
mechanism so the EVDI kernel module which is essential for DisplayLink
USB 3.0 devices to work is correctly recognised by x.org. Then the
PRIME sync is disabled in such case; The patch can be found here:

https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1

[Test Case]

Expected result:
The external monitor should light up and show the desktop

Actual result:
The monitor remains black or shows frozen desktop.

[Regression Potential]

[Other Info]

* The patch has been applied to Ubuntu x.org source code built and tested.

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

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

2017-09-28 Thread Jean-Baptiste Lallement

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happened after I entered the password to unlock the screensaver
  (note that this was not after a suspend/resume cycle). The unlock
  screen froze for some time (after displaying asterisks to represent
  some of the password), then went black, then came back (displaying
  more asterisks this time), then went black, then gnome-shell crashed
  and burned and I found this in /var/crash when I logged back in.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  Uname: Linux 4.13.3-041303-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 28 11:33:27 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-08-16 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-08-17 (42 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-09-28 Thread Jason Gambrel

No other wireless devices.  I use the touchpad or a wired mouse on my
laptop.  I use a Wireless G AP (I'm guessing that is 2.4G)  I will try
using my bluetooth headset connecting to my phone while I use my laptop
to see if it interferes.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1716208] Re: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

2017-09-28 Thread Joaquín Ignacio Aramendía

The crash seems random when opening the overview mode in Gnome shell. The 
entire desktop crashes and the user is logged out from session.
Uninstalling Epiphany browser for now as a workaround seems to make crash go 
away.

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

Title:
  epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

Status in epiphany-browser package in Ubuntu:
  Confirmed

Bug description:
  I don't know.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.25.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  9 21:23:06 2017
  ExecutablePath: /usr/lib/epiphany-search-provider
  ExecutableTimestamp: 1504471514
  InstallationDate: Installed on 2014-08-22 (1114 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/lib/epiphany-search-provider
  ProcCwd: /home/thomas
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_IN:en
   LANG=en_IN
  SegvAnalysis:
   Segfault happened at: 0x7f945c37ce30 :   mov
%rbp,(%rax)
   PC (0x7f945c37ce30) ok
   source "%rbp" ok
   destination "(%rax)" (0x0005) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: epiphany-browser
  StacktraceTop:
   wl_list_insert_list () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   wl_display_destroy () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()
  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/epiphany-browser/+bug/1716208/+subscriptions

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

[Desktop-packages] [Bug 1662031] Re: Switching language and format broken

If nobody figures out what makes the variables in ~/.pam_environment be
overridden by the variables in /etc/default/locale, I'm thinking of an
ugly hack which may work.

~/.pam_environment is maintained by /usr/share/language-tools/save-to-
pam-env. In case of a GNOME desktop we could make that file write to
~/.profile as well.

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

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

Title:
  Switching language and format broken

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  New
Status in accountsservice source package in Artful:
  New
Status in gdm3 source package in Artful:
  Confirmed
Status in gnome-control-center source package in Artful:
  New

Bug description:
  In Ubuntu GNOME 16.10 it doesn't matter what display language I select
  - the effective language is still the one stated in
  /etc/default/locale. ~/.pam_environment is changed as expected, but
  the variables set in /etc/default/locale override ~/.pam_environment.

  In Ubuntu GNOME 16.04 language switching takes effect, but the reason
  for that seems to be that /etc/default/locale is changed as well, so
  when a user changes the display language (or format), it changes it
  for all users on the system.

  The overriding by /etc/default/locale is probably caused by some other
  package(s) but g-c-c.

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

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

[Desktop-packages] [Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations

2017-09-28 Thread dajare

The problem still exists in 17.10. Even sadder. :'(

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

Title:
  Operation not permitted while writing to symlinked fuse locations

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in gvfs source package in Xenial:
  Confirmed

Bug description:
  Affected releases:
  Ubuntu from 14.10+ (14.04 was working fine) 

  Steps to reproduce:
  1. Setup a gvfs mount (I used smb and sftp shares configured via nautilus).
  2. Create a symlink to the fuse-mounted location e.g.
  cd ~/Desktop; ln -sf 
/run/user/1000/gvfs/smb-share:server=10.0.20.6,share=share1/symlinktest
  3. Navigate with nautilus to the symlinked location, open a file available 
there with e.g. gedit or libreofficeand try to save it.

  Expected result:
  File is saved.

  Actual result:
  An enigmatic error message is displayed
  (Cannot handle "file:" locations in write mode - for gedit, or "General 
input/output error while accessing " for libreoffice).

  The problems started with commit
  548ba46c2ba51c4ec5b0dd8442b476f3a2a7000b fuse: Don't g_file_append_to
  unless O_APPEND is given. Reverting it makes the issue disappear.

  I have rebuild gvfs enabling debugging (#define DEBUG_ENABLED 1) and here is 
what I got in ~/vfs.debug:
  # accessing via symlink
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=52
  vfs_open: -> Operation not supported
  # accessing via /run/user/(...)
  vfs_open: /smb-share:server=10.0.20.6,share=share1/grouptest/symlinktest/test
  open_common: flags=110
  setup_input_stream: have stream
  setup_input_stream: doing read
  vfs_open: -> Success

  For reasons beyond my understanding the flags are different while
  accessing the file via the default gvfs-mountpoint causing the
  execusion to skip the modified section of client/gvfsdfusedaemon.c
  (returning -ENOTSUP).

  I am attaching the full vfs.debug created.
  Collapse All Comments
  Expand All Comments
  Add Comment

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

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

[Desktop-packages] [Bug 1720090] Re: package nvidia-340 (not installed) failed to install/upgrade: cannot remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system

2017-09-28 Thread Yurii Zhytskyi

with lightdm is work fine

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: cannot
  remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only
  file system

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

Bug description:
  After installing nvidia-340.104 and restarting GNOME desktop was crashed, 
only blink my monitor
  Then i remove nvidia drivers, but now i got this report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  AptOrdering:
   nvidia-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   nvidia-prime:amd64: Remove
   nvidia-settings:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep 25 10:13:30 2017
  ErrorMessage: cannot remove 
'/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system
  InstallationDate: Installed on 2016-10-14 (348 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: cannot 
remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system
  UpgradeStatus: Upgraded to artful on 2017-09-10 (17 days ago)
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1720090/+subscriptions

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

[Desktop-packages] [Bug 1716470] Re: xdg-open doesn't respect gnome3 associations

2017-09-28 Thread Mario Abarca

I can reproduce this problem even from a Live Ubuntu 17.10 session.

Here's a provisional fix for this problem: force gnome-open instead of
xdg-open. This also fixes issues with texdoc, google-crhome and other
KDE-apps. Here are the commands I used at the Terminal:

$ mkdir --parents ~/bin
$ ln --symbolic /usr/bin/gnome-open ~/bin/xdg-open

Restart your session and you are good to go (until a real fix is
issued).

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

Title:
  xdg-open doesn't respect gnome3 associations

Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  xdg-open internaly uses "gvfs-open --help" to check if gvfs-open is present 
and functional, but gvfs-open is deprecated in new gnome (3.25.90) and 
"gvfs-open --help" returns with error code = 1.
  gvfs-open still can be used to open files and urls, new way to open 
associated files is "gio open ARG".

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xdg-utils 1.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 11 23:59:06 2017
  InstallationDate: Installed on 2017-04-10 (154 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: Upgraded to artful on 2017-09-10 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1716470/+subscriptions

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

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

2017-09-28 Thread Jh

Well i didnt think of that, so I tried it, too. When I turn off my Display that 
is connected via Displayport, the Gnomeshell is killed after turning the Screen 
on again. After turning on the Screen the login-window can be seen.
When you log in, its a new Session.
That would explain why in Bug #1718671 the session is only crashing after when 
you want to unlock the Screen, because the Display was turned off after locking 
the screen.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This crash appears after login in, when gnome-shell restarts it seems
  to be stable.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 09:18:43 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-03 (153 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff4e23f8b24 :  
mov0x2c(%rax),%eax
   PC (0x7ff4e23f8b24) ok
   source "0x2c(%rax)" (0x002c) 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_is_on_primary_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_on_all_workspaces_changed () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
  UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1720089] [NEW] Desktop isn't part of "places" (left bar) in artful

Public bug reported:

Artful re-enabled the desktop, but it is not showing up in the left bar
of nautilus [This used to be called "places"?].

I'm talking about this bar: https://pasteboard.co/GMqxauJ.png

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


** Tags: artful

** Tags added: artful

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

Title:
  Desktop isn't part of "places" (left bar) in artful

Status in nautilus package in Ubuntu:
  New

Bug description:
  Artful re-enabled the desktop, but it is not showing up in the left
  bar of nautilus [This used to be called "places"?].

  I'm talking about this bar: https://pasteboard.co/GMqxauJ.png

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

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

[Desktop-packages] [Bug 1720090] [NEW] package nvidia-340 (not installed) failed to install/upgrade: cannot remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system

2017-09-28 Thread Yurii Zhytskyi

Public bug reported:

After installing nvidia-340.104 and restarting GNOME desktop was crashed, only 
blink my monitor
Then i remove nvidia drivers, but now i got this report

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
AptOrdering:
 nvidia-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 nvidia-prime:amd64: Remove
 nvidia-settings:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Sep 25 10:13:30 2017
ErrorMessage: cannot remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': 
Read-only file system
InstallationDate: Installed on 2016-10-14 (348 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: cannot 
remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system
UpgradeStatus: Upgraded to artful on 2017-09-10 (17 days ago)
modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]

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


** Tags: amd64 apport-package artful

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: cannot
  remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only
  file system

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

Bug description:
  After installing nvidia-340.104 and restarting GNOME desktop was crashed, 
only blink my monitor
  Then i remove nvidia drivers, but now i got this report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  AptOrdering:
   nvidia-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   nvidia-prime:amd64: Remove
   nvidia-settings:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep 25 10:13:30 2017
  ErrorMessage: cannot remove 
'/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system
  InstallationDate: Installed on 2016-10-14 (348 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: cannot 
remove '/usr/lib32/nvidia-340/vdpau/libvdpau_nvidia.so.1': Read-only file system
  UpgradeStatus: Upgraded to artful on 2017-09-10 (17 days ago)
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1720090/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

** Tags added: artful

-- 
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 1720083] [NEW] Profile defaults to headset mode instead of a2dp