[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-23 Thread Daniel van Vugt
j, please log a new bug for your issue.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

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

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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


[Desktop-packages] [Bug 1711393] Re: [snap] won't run on wayland

2017-10-23 Thread Olivier Tilloy
** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] won't run on wayland

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  The deb package runs fine under XDG_SESSION_DESKTOP=ubuntu-wayland.
  The snap doesn't. When running /snap/bin/chromium from a terminal, it
  returns almost instantly, and silently. With additional debugging
  info:

  osomon@bribon:~$ /snap/bin/chromium --enable-logging=stderr --v=1
  [3071:3071:0817/172403.433381:VERBOSE1:breakpad_linux.cc(1971)] Breakpad 
disabled
  [1:1:0817/172403.726801:VERBOSE1:zygote_main_linux.cc(631)] ZygoteMain: 
initializing 0 fork delegates
  [1:1:0817/172403.727121:INFO:cpu_info.cc(50)] Available number of cores: 4
  [3071:3071:0817/172403.731547:WARNING:browser_main_loop.cc(266)] Gtk: cannot 
open display: :0
  osomon@bribon:~$

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

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


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

2017-10-23 Thread Khurshid Alam
@Carlos

You need to disable ignore-lid-switch-tweak from autostart-manager to
make tweak-tool-settings work.

See https://bugzilla.gnome.org/show_bug.cgi?id=715022

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1726704] Re: [snap] desktop actions don't work

2017-10-23 Thread Olivier Tilloy
Fixed with https://git.launchpad.net/~osomon/+git/chromium-
snap/commit/?id=7fbb8eeec57a396a2fc7c857f0b5faf8bd524e20

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [snap] desktop actions don't work

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Testing the candidate snap for chromium (currently at 62.0.3202.62) in Ubuntu 
17.10.
  Desktop actions (which are displayed in a context menu when right-clicking 
the chromium icon in the dock) do nothing.

  Upon inspection, it turns out snapd strips the corresponding Exec
  commands from the desktop file it installs in
  /var/lib/snapd/desktop/applications/ because they reference "chromium-
  browser", not "chromium".

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

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


[Desktop-packages] [Bug 1672161] Re: Add more Compress options

2017-10-23 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Confirmed => Expired

** Changed in: nautilus
   Importance: Medium => Wishlist

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

Title:
  Add more Compress options

Status in Nautilus:
  Expired
Status in Ubuntu GNOME:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have a system running Ubuntu GNOME 16.10 with GNOME 3.22 and I have
  found that in this version of GNOME if one right-clicks on a file or
  folder or a group of them and goes to "Compress..." that they are
  provided with 3 different formats to compress into, however the
  options which allow splitting of large archives into smaller ones as
  well as the ability to encrypt them with a password are gone. This can
  obviously still be done through the CLIs of the various tools, however
  it would be useful to have such features accessible as they used to be
  through the GUI. Perhaps this is a side-effect of making all Nautilus
  activities central to the Nautilus GUI? Because I think I remember it
  possibly opening another program in the past which had these options.

  Regardless of what it and how it did it in the past, these are vital
  options which are missing and I think should be added back for ease of
  use.

  I am fine with using the CLI, but many users are not.

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

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


[Desktop-packages] [Bug 1726704] [NEW] [snap] desktop actions don't work

2017-10-23 Thread Olivier Tilloy
Public bug reported:

Testing the candidate snap for chromium (currently at 62.0.3202.62) in Ubuntu 
17.10.
Desktop actions (which are displayed in a context menu when right-clicking the 
chromium icon in the dock) do nothing.

Upon inspection, it turns out snapd strips the corresponding Exec
commands from the desktop file it installs in
/var/lib/snapd/desktop/applications/ because they reference "chromium-
browser", not "chromium".

** Affects: chromium-browser (Ubuntu)
 Importance: Medium
 Assignee: Olivier Tilloy (osomon)
 Status: Fix Committed


** Tags: snap

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

Title:
  [snap] desktop actions don't work

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Testing the candidate snap for chromium (currently at 62.0.3202.62) in Ubuntu 
17.10.
  Desktop actions (which are displayed in a context menu when right-clicking 
the chromium icon in the dock) do nothing.

  Upon inspection, it turns out snapd strips the corresponding Exec
  commands from the desktop file it installs in
  /var/lib/snapd/desktop/applications/ because they reference "chromium-
  browser", not "chromium".

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

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


[Desktop-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2017-10-23 Thread Markward Kufleitner
Still comes up just after logging in to cinnamon.

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1726696] Re: Xorg crashed with SIGABRT in OsAbort()

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1562639 ***
https://bugs.launchpad.net/bugs/1562639

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 17.10  the system would hang when attempting
  to use dual monitors.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 23 21:18:36 2017
  DistUpgraded: 2017-10-23 19:13:02,141 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Dell RV515/M54 [Mobility Radeon X1400] [1028:2003]
  InstallationDate: Installed on 2014-08-21 (1159 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  MachineType: Dell Inc. MM061
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8f6499c8-a2d1-4e83-b9a4-c817deaeaaa3 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-23 Thread j
'nomodeset' does not work as a workaround in my case.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

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

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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


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

2017-10-23 Thread Khurshid Alam
@Sebastien

Unity use unity-settings-daemon which depends on gnome-settings-daemon-
schemas and gsetting-ubuntu-schemas for power related settings.

How to reproduce:

1) Log in to unity-session

2) UCC-> Power

3) Choose "Do nothing" for lid is closed option.

It won't work. Certainly not without tweak-tool. But the Ubuntu
autostart ignore-lid-switch-tweak (/usr/lib/gnome-tweak-tool/gnome-
tweak-tool-lid-inhibitor) which needs to be disabled as well.


The patch only changes inhibit_lid_switch_action behavior. Gnome-shell can have 
tweak-tool, but other sessions are affected.


In short it's broken



Solution:


gsettings set org.gnome.settings-daemon.plugins.power.lid-close-ac-action 
'nothing'
gsettings set org.gnome.settings-daemon.plugins.power 
lid-close-suspend-with-external-monitor false

These schemas needs to be set to make it work properly. And we can do
that in "ubuntu-settings".

Also when laptop boots with lid-closed it's all gdm before login. So
these settings needs to be changed on the behalf of the gdm.

That way there won't be any conflict, both gnome-tweak-tool and unity
power settings will work properly.

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1726333] Re: Mouse cursor flickers shortly and then vanishes under Wayland

2017-10-23 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mouse cursor flickers shortly and then vanishes under Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sorry for this being filed under xorg, but I do not get "Wayland"
  offered.

  After logging in to Ubuntu 17.10 in Wayland, the mouse cursor flickers 
shortly and then is gone.
  In XOrg session all is fine.

  I had no issues with the cursor in the artful beta release - I was
  using the beta release of Ubuntu 17.10 7 to 10 days before the final
  release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 23 11:39:45 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:3801]
  InstallationDate: Installed on 2017-10-12 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 80VF
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a5819d75-73ad-458c-8bde-fd93b2f7d230 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-384 (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/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

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

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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


[Desktop-packages] [Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics

2017-10-23 Thread Daniel van Vugt
modeset=0 sounds similar to the workaround for bug 1705369. Although the
symptoms are a bit different.


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

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

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

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

Title:
  gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid
  graphics

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in gdm3 package in Fedora:
  Unknown

Bug description:
  I've just upgraded to Ubuntu 17.10 and switched the login manager from
  sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The
  /usr/share/xsessions folder indeed only contains the -xorg -related
  sessions:

  $ ls -la /usr/share/xsessions
  total 36
  drwxr-xr-x   2 root root  4096 okt 18 16:00 .
  drwxr-xr-x 427 root root 20480 okt 18 15:56 ..
  -rw-r--r--   1 root root   201 okt 13 12:56 gnome-xorg.desktop
  -rw-r--r--   1 root root  2354 aug 23 16:39 plasma.desktop
  -rw-r--r--   1 root root   262 okt 13 12:56 ubuntu-xorg.desktop

  How can I enable the ubuntu-wayland session please?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 16:37:47 2017
  InstallationDate: Installed on 2016-09-05 (408 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago)

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

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


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

2017-10-23 Thread Daniel van Vugt
As this bug is effectively closed for 17.10, new issues should be logged
as new bugs.

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1726195] Re: Can't change focus with Alt-`, Alt-Tab when using Sloppy Window Focus

2017-10-23 Thread Daniel van Vugt
** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=739718
   Importance: Unknown
   Status: Unknown

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

Title:
  Can't change focus with Alt-`, Alt-Tab when using Sloppy Window Focus

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have Window Focus set to Sloppy under Windows in gnome-tweak-tool.

  When I Alt-` or Alt-Tab to switch to another window, focus switches to
  the new window briefly and then switches back to the window that the
  mouse is hovering over.

  This is a regression from 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 21:28:57 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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


[Desktop-packages] [Bug 1725836] Re: No more than 2 displays

2017-10-23 Thread Daniel van Vugt
What exactly do you see on the third display? Is it off/sleeping?

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

Title:
  No more than 2 displays

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

Bug description:
  I have three displays that worked fine in 17.04.
  Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
  All three seem to be properly specified in monitors.xml.
  The display setup scree detects all three.
  UBUNTU 17.10
  AMD PitcairnLSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-02-23 (242 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2017-10-23 Thread Daniel van Vugt
** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ordinary bug report in 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 13:08:15 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi
   PC (0x7f8d82fc8c5c) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_x11_configure_request () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

2017-10-23 Thread Daniel van Vugt
Consider deduplicating with bug 1716341?

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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


[Desktop-packages] [Bug 1589240] Re: Gnome on-screen keyboard doesn't appear when a text field is focused

2017-10-23 Thread Daniel van Vugt
This bug is closed, rightly or wrongly. Yes, please do open a new bug if
you have any problems.

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

Title:
  Gnome on-screen keyboard doesn't appear when a text field is focused

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Xenial:
  Fix Released
Status in gnome-shell source package in Yakkety:
  Fix Released
Status in gnome-shell source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  Without 'caribou' installed, the Screen Keyboard setting, if Enabled, only 
works for for the login screen, password prompts and the Activities Overview 
search.

  It looks the caribou gir and library are enough for those places, but
  the 'caribou' binary is needed for the Screen Keyboard to work in
  screen input in apps.

  Test Case
  -
  From Ubuntu GNOME, install the update.

  caribou should be installed now.

  Open the Settings app (gnome-control-center).
  Click Universal Access then turn on Screen Keyboard.

  Open Text Editor (gedit)
  Click (or tap) in the window to start typing.
  The onscreen keyboard should be

  Regression Potential
  
  I also tested with gnome-shell-extension-onboard installed. Onboard appears 
to completely ignore the Screen Keyboard setting (LP: #1690582). Also when 
Onboard is enabled, caribou is not shown at all except in the password prompts 
and Activities Overview search where onboard is currently not working. In other 
words, I tested whether having caribou installed would interfere with Onboard 
and I can see that Caribou provides no problem.

  Original Bug Report
  ---
  The gnome on-screen keyboard is hidden by default and should appear when a 
text field is focused.
  This behavior is working as expected clicking on one of the text field of the 
shell such as the search field in the gnome overview. Clicking on text fields 
not owned by the gnome-shell such as in gedit or in a terminal emulator doesn't 
un-hide the keyboard.

  Steps to reproduce the issue:
   * Enable the keyboard in accessibility.
   * Open a text editor. (I've tested with gedit)
   * Click on the text field/area.

  Expected behavior:
   * The keyboard should appear.

  Actual behavior:
   * The keyboard doesn't appear.

  Also, I think it would be useful to be able to choose:
   * Between the "fullscreen" mode (the default one) and a windowed mode.
   * Between the "show on focus" behavior and a "always shown" behavior.

  The "fullscreen" mode should be incompatibile with the "always shown"
  behavior unless there is a way to close it manually (a button on the
  on-screen keyboard) in order to prevent a deadlock-like situation
  where the keyboard is preventing us from closing itself because we
  can't click in a window behind it. That button already exists and has
  a similar behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jun  5 13:49:03 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-22 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726690] Re: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1726145 ***
https://bugs.launchpad.net/bugs/1726145

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I was attempting to create a libreoffice base file. In a terminal I
  entered the command 'libreoffice --base'. The splash screen was follow
  by the create database dialog box. I entered a file name and clicked
  save, the window froze and then disappeared. There was no message in
  the terminal.

  This is the first time I that I have tried libreoffice since
  installing 17.10.  I was not able to run libreoffice base on 17.04
  either.  On 17.04, libreoffice base would crash on creating a database
  or querying an existing database.

  OpenOffice4 base worked on 17.04 but I have not tried it on 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 22:59:31 2017
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LD_LIBRARY_PATH=
  SegvAnalysis:
   Segfault happened at: 0xa70a8bc5:movb   $0x0,(%eax)
   PC (0xa70a8bc5) ok
   source "$0x0" ok
   destination "(%eax)" (0xbf28bfe0) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   JNI_CreateJavaVM () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
  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/libreoffice/+bug/1726690/+subscriptions

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


[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1716341 ***
https://bugs.launchpad.net/bugs/1716341

Thanks for the bug report. This issue is already being tracked in bug
1292398 and bug 1716341.

** Tags added: multimonitor

** This bug has been marked a duplicate of bug 1716341
   Settings for external monitor are deleted after reboot, suspension, log out

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

Title:
  Dual monitor configuration not saved across logout / login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System76 Galaga UltraPro laptop.

  Two monitors, one plugged into the DisplayPort and one plugged into
  HDMI.

  I use the Displays settings page to tell the system which monitor is
  on the right and which is on the left, and tell it to make the left
  monitor the primary one. All is well.

  Then I log out and log back in.

  Now the two monitors are reversed -- i.e., it thinks that the monitor
  on the right is on the left and vice versa -- and the right monitor
  (which, remember, it thinks is on the left) is the primary one.

  In short, it forgets the configuration I told it to use immediately
  before logging out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:55:09 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (157 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)

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

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


[Desktop-packages] [Bug 1726555] Re: Use mainstream theme solution for gnome-terminal, drop patch

2017-10-23 Thread Daniel van Vugt
** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  Use mainstream theme solution for gnome-terminal, drop patch

Status in Ubuntu theme:
  New
Status in gnome-terminal package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to-
  some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and
  Radiance themes' apps/gnome-terminal.css relies on this to get the
  desired look for the notebook widget.

  Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be
  necessary. It's just an additional burden to carry this patch, plus an
  unnecessary complication for those who wish to manually compile gnome-
  terminal for whatever reason.

  gnome-terminal.css should ideally be modified to use the CSS names
  provided by mainstream gnome-terminal, and once done, the gnome-
  terminal patch can be dropped.

  Upstream references:
  https://bugzilla.gnome.org/show_bug.cgi?id=765590
  https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6
  https://bugzilla.gnome.org/show_bug.cgi?id=788044

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726555/+subscriptions

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


[Desktop-packages] [Bug 1697450] Re: Gnome Shell hangs at startup

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

Great, thanks. Looks like a duplicate of bug 1505409.

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

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

Title:
  Gnome Shell hangs at startup

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-30 (71 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Tags:  artful wayland-session
  Uname: Linux 4.8.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

2017-10-23 Thread Nick Rapoport
Same thing after 17.04 upgrade to 17.10: no usb flash (ssd drives in the
system), but with Logitech usb transmitter and a 3dconnection SpacePilot
Pro (no driver installed yet for SpacePilot) plugged in to USB

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1726692] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1724699 ***
https://bugs.launchpad.net/bugs/1724699

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724699
   nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_file_get_search_fts_snippet()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I search something in nautilus and then clic in the arrow to expand a
  folder to see his files and the nautilus crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Oct 24 01:37:49 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-04-26 (545 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x55e79c80 : 
mov0x18(%rdi),%rax
   PC (0x55e79c80) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   nautilus_file_get_search_fts_snippet ()
   ()
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_hash_table_foreach () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

2017-10-23 Thread Daniel van Vugt
Consider de-duplicating with bug 1292398?

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

Status in gnome-control-center:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Artful:
  Triaged

Bug description:
  New Gnome Settings on Ubuntu 17.10

  Settings for external monitor are working but after reboot/suspension
  /log-out log-in, the system will not remember the setup.

  Example:
  1- open Gnome Settings and select "Devices → Displays"
  2- set the external monitor as "Single Display" and click on "Apply"
  3- log-out

  After log-in the laptop monitor will be set as default instead of the
  external monitor.

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

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


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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1720768 ***
https://bugs.launchpad.net/bugs/1720768

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1720768
   gnome-shell crashed with SIGTRAP in object_instance_finalize from 
js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be 
unrooted: Gio.Subprocess\n"]

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  auto detected

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 23:09:27 2017
  DisplayManager: lightdm
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['ubuntu-amazon-default.desktop', 
'thunderbird.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'update-manager.desktop', 
'org.gnome.Software.desktop', 'firefox-trunk.desktop', 'virtualbox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'0.9375'
  InstallationDate: Installed on 2016-07-20 (460 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip libvirt lpadmin lxd plugdev pulse 
pulse-access sambashare sudo video

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

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


[Desktop-packages] [Bug 1573693] Re: Microphone is not working

2017-10-23 Thread Daniel van Vugt
** Tags added: mic

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

Title:
  Microphone is not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Microphone is not working on ASUS X552L laptop.

  Just installed latest ubuntu version 16.04 LTS

  After installed Skype, tried a test call, sound was very low volume.
  Tried to adjust microphone volume with the slider, mic went dead for
  good, no sound at all. tried to reinstall alsa package

  apt-get remove --purge alsa-base pulseaudio

  and install it again, nothing works.

  Did not work on older ubuntu version either.

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  alsa-base:
Telepítve: 1.0.25+dfsg-0ubuntu5
Jelölt:1.0.25+dfsg-0ubuntu5
Verziótáblázat:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Telepítve: 1:8.0-0ubuntu3
Jelölt:1:8.0-0ubuntu3
Verziótáblázat:
   *** 1:8.0-0ubuntu3 500
  500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  irma   1425 F pulseaudio
   /dev/snd/pcmC1D0c:   irma   1425 F...m pulseaudio
   /dev/snd/controlC1:  irma   1425 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 22 18:17:49 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.509
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.509:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

2017-10-23 Thread Launchpad Bug Tracker
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/1725814

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

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

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


[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

2017-10-23 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

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

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


[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

2017-10-23 Thread Daniel van Vugt
** Summary changed:

- The Activities top left button reacts to a mouse-up instead of click
+ The Activities top left button reacts to a mouse-up (e.g. drag and drop) 
instead of a click

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

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

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


Re: [Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-23 Thread Tushar Semwal
Everytime I reboot, it rotates anticlockwise 90 and sometimes randomly it
switches to inverted screen. I tried using xandr to correct the rotation,
but nothing worked.

On Oct 24, 2017 9:50 AM, "Nevet Dnulho" <1726...@bugs.launchpad.net>
wrote:

In continuing to determine issue, it seems that when waking from
suspend, or logging in from power up, the orientation rotates clockwise
90*. I have had 'xrandr -o 0' orient to the right, the bottom, and the
left and back to the top of the screen after closing the lid, letting it
suspend itself, then reopening the lid.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1726509).
https://bugs.launchpad.net/bugs/1726160

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14
17:13:13 PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2)
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log
file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-
Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:
rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed 

[Desktop-packages] [Bug 1214144] Re: gvfsd-mtp crashed with SIGSEGV in __GI___pthread_mutex_lock()

2017-10-23 Thread Jonathan Polak
in ubuntu 17.10

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

Title:
  gvfsd-mtp crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  Ejected phone in Nautilus.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gvfs-backends 1.17.2-0ubuntu6
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: c8e1190bd2b988587064325803c84440
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Mon Aug 19 22:22:35 2013
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  MarkForUpload: True
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
  SegvAnalysis:
   Segfault happened at: 0x7fb3df73cf74 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7fb3df73cf74) ok
   source "0x10(%rdi)" (0x0110) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0xbefaae) at pthread_mutex_lock.c:50
   libusb_submit_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_bulk_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
  Title: gvfsd-mtp crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: Upgraded to saucy on 2013-07-06 (43 days ago)
  UserGroups: adm admin cdrom dialout kismet libvirtd lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 1726688] Re: totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2017-10-23 Thread David Gil
This is the video of what actually happened.

** Attachment added: "vokoscreen-2017-10-24_12-24-57.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1726688/+attachment/4990092/+files/vokoscreen-2017-10-24_12-24-57.mkv

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  New

Bug description:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1668445] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

2017-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс
  установлен сценарий post-removal возвратил код ошибки 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  can't upgrade-distr from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-110-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   xubuntu-desktop: Purge
   ubuntu-desktop: Purge
   lightdm: Purge
  Architecture: amd64
  Date: Thu Feb 23 00:43:32 2017
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2015-02-02 (754 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: lightdm
  Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: подпроцесс 
установлен сценарий post-removal возвратил код ошибки 1
  UpgradeStatus: Upgraded to trusty on 2017-02-26 (0 days ago)

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

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


[Desktop-packages] [Bug 1726688] [NEW] totem media player in the Ubuntu dock right click menu does not work, rewind does not work, nor full screen works

2017-10-23 Thread David Gil
Public bug reported:

totem media player in the Ubuntu dock right click menu does not work,
rewind does not work, nor full screen works.

I'm completely aware that there is a similar bug report of Ubuntu DBUS
PlayPause() Function. However it is no longer just Play and Pause
anymore.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 12:22:01 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-10-19 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

Title:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works

Status in totem package in Ubuntu:
  New

Bug description:
  totem media player in the Ubuntu dock right click menu does not work,
  rewind does not work, nor full screen works.

  I'm completely aware that there is a similar bug report of Ubuntu DBUS
  PlayPause() Function. However it is no longer just Play and Pause
  anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:22:01 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1653320] Re: Chromium stopped understanding HiDPI in GNOME?Wayland

2017-10-23 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Chromium stopped understanding HiDPI in GNOME?Wayland

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  On upgrade to 55.0.2883.87-0ubuntu1.16.10.1330
  Chromium stopped understanding that it was on a low DPI display in a HiDPI 
environment
  - impact: all fonts 2x too high
  - this used to work
  - getaround: launch like: chromium-browser --force-device-scale-factor=0.5
- causes chrome and popups to be 50% too small
- browsed content is correct size on low DPI displays

  Chromium also decides to launch all windows on display 3, which is the lowest 
resolution display
  - It used to open windows at the location they were last at

  I think this worked in 55.0.2883.87-0ubuntu0.16.10.1328
  It certainly worked in 53.0.2785.143-0ubuntu1.1307

  dpkg --status chromium-browser | egrep "^(V|Pa)"
  Package: chromium-browser
  Version: 55.0.2883.87-0ubuntu1.16.10.1330

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 55.0.2883.87-0ubuntu1.16.10.1330
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAQrGNATDk1MAUWAQOAQCh46o2FrU81sSUOUFSlSwBxT4EAgYCpQNEA0UABAQEB4mgAoKBALmAwIDYAgZEhAAAa/wBQSDVOWTIyMjA1OUwK/ABERUxMIFUzMDExCiAg/QAxVh1xHAAKICAgICAgAMc=
   modes: 2560x1600 1920x1440 1920x1200 1600x1200 1280x1024 1280x1024 1280x800 
1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchck6AEAADIQAQOANCB4Ku+Vo1RMmyYPUFS/7wBhRnFAcU+BT4GAqUCzANEAKDyAoHCwI0AwIDYABkQhAAAaAR2AGHEcFiBYLCUABkQhAACe/QAxSw9QEQAKICAgICAg/ABBY2VyIEFMMjQxNlcKAS4CAQQAAR0AclHQHiBuKFUABkQhAAAejArQiiDgLRAQPpYABkQhAAAYjAqgFFHwFgAmfEMABkQhAACYAR2A0HIcFiAQLCWABkQhAACejArQkCBAMSAMQFUABkQhAAAYAR0AvFLQHiC4KFVABkQhAAAeWg==
   modes: 1920x1200 1920x1080i 1920x1080i 1920x1080i 1600x1200 1680x1050 
1280x1024 1280x1024 1280x960 1152x864 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 1024x768 1440x480i 832x624 800x600 800x600 800x600 
800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGECmgADIXAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEE8=
   modes: 2560x1600
  Date: Fri Dec 30 20:09:09 2016
  Desktop-Session:
   'gnome-wayland'
   
'/etc/xdg/xdg-gnome-wayland:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share/gnome-wayland:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  Load-Avg-1min: 2.78
  Load-Processes-Running-Percent:   0.1%
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic 
root=/dev/mapper/C89-RFS ro i915.enable_rc6=0
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (44 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 

[Desktop-packages] [Bug 1675106] Re: Restarting compiz crashes chromium-browser

2017-10-23 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Restarting compiz crashes chromium-browser

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I'm using Chomium 56 on Ubuntu 16.10. Nvidia drivers are installed in
  the system and compiz is active. Normally I don't have any problem
  running chromium but if I try to restart compiz while chromium is
  running, chromium windows crash and it also prevents compiz from
  restarting.

  The problem happens when I restart compiz by killing it or using
  compiz --replace command.

  Chromium does not vanish instantly, all windows and plugins crash
  separately. Each window goes blank and each plugin generates a "This
  plugin crashed" message. Chromium is still responsive after this point
  and you can refresh tabs, but since compiz fails to restart there is
  not much to do except restarting X session somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 56.0.2924.76-0ubuntu0.16.10.1335
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card1-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card1-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card1-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card1-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMg0wyAAAXAQSVIhN4Cs6FnltMlCYXUFQBAQEBAQEBAQEBAQEBAQEB3DeAoHA4QEAwICUAWMIQAAAZDwAAAB6CEFIA/gBTQU1TVU5HCiAgICAg/gAxNTZITDAxLTEwNAogAM8=
   modes: 1920x1080
  Date: Wed Mar 22 20:13:20 2017
  Desktop-Session:
   'ubuntu'
   
'/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-02-11 (404 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Load-Avg-1min: 1.35
  Load-Processes-Running-Percent:   0.2%
  MachineType: ASUSTeK COMPUTER INC. N551JW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic.efi.signed 
root=UUID=021ad30b-7bc5-464f-bafb-8c90d2910f20 ro quiet splash acpi_osi=
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-11-28 (113 days ago)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JW.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JW.207:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1655918] Re: chromium UI lags horribly when a new window is opened in another workspace

2017-10-23 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  chromium UI lags horribly when a new window is opened in another
  workspace

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  This bug started to appear maybe two weeks ago, probably when Chromium
  was upgraded to newer version. As long as there is only one Chromium
  window, it behaves fast and proper. When I open a new Chromium window
  with one tab and move it to another workspace, this still works.

  However, when I switch to another workspace and open a new chromium
  tab there (by middle-clicking the Chromium icon in Unity), the
  Chromium UI in all windows start to lag horribly. There is usually no
  response for 2-5 seconds for any mouse+keyboard activity, then things
  work for ~10 seconds, then the UI again starts to act choppy.

  Thanks ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: chromium-browser 55.0.2883.87-0ubuntu1.16.10.1330
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card1-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAw5KcEAAAZAQSVIhN46qHFlFlXjycgUFQBAQEBAQEBAQEBAQEBAQEBLjaAoHA4H0AwIDUAWMIQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE1NldGNi1TUEsxAE8=
   modes: 1920x1080
  Date: Thu Jan 12 12:19:36 2017
  Desktop-Session:
   'ubuntu'
   
'/etc/xdg/xdg-ubuntu:/usr/share/upstart/systemd-session:/usr/share/upstart/xdg:/etc/xdg'
   '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-09-05 (129 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Load-Avg-1min: 0.86
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20EN0005MS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=/dev/mapper/vg0-lv1--root ro splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to yakkety on 2016-09-30 (103 days ago)
  dmi.bios.date: 12/08/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET64W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0005MS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EN0005MS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1712870] Re: Navegador Firefox com paginas em Branco

2017-10-23 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Navegador Firefox com paginas em Branco

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Várias páginas em branco ao acessar internet com Firefox...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pjribamarvas   1816 F pulseaudio
   /dev/snd/controlC0:  pjribamarvas   1816 F pulseaudio
  BuildID: 20170816210057
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Aug 24 13:52:34 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-08 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp6s0  proto static  metric 600 
   192.168.1.0/24 dev wlp6s0  proto kernel  scope link  src 192.168.1.3  metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816210057 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-23 Thread Nevet Dnulho
In continuing to determine issue, it seems that when waking from
suspend, or logging in from power up, the orientation rotates clockwise
90*. I have had 'xrandr -o 0' orient to the right, the bottom, and the
left and back to the top of the screen after closing the lid, letting it
suspend itself, then reopening the lid.

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1721315 ***
https://bugs.launchpad.net/bugs/1721315

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


** This bug has been marked a duplicate of bug 1721315
   On-screen keyboard shows up on first touch even when touch does not activate 
a text-field

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

Status in gnome-desktop:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Confirmed

Bug description:
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears.
  It is disabled in System Preferences > Universal Access.  This didn't
  happen in any previous Ubuntus, including 17.04 GNOME, nor in Fedora,
  which is GNOME based.

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

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


[Desktop-packages] [Bug 1726682] [NEW] Xorg freeze

2017-10-23 Thread Daniel C Aragao
Public bug reported:

This problem occur: 
- when I input USB stick
- When I have click about system (more details of Ubuntu)
- Using normally, so open a video then system log off or freeze.

I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM login
screen.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Oct 24 00:44:02 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
InstallationDate: Installed on 2017-10-19 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RCX.075.160311.JJ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370E4K-KW3BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: SAMSUNG ATIV
dmi.product.name: 370E4K
dmi.product.version: P06RCX
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

** Attachment added: "System log"
   https://bugs.launchpad.net/bugs/1726682/+attachment/4990043/+files/Problems

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem occur: 
  - when I input USB stick
  - When I have click about system (more details of Ubuntu)
  - Using normally, so open a video then system log off or freeze.

  I try Ctrl + Shft + F1 or Ctrl + Shift + F2 but it goes to the GDM
  login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 24 00:44:02 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755]
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2016
  dmi.bios.vendor: American 

[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up instead of click

2017-10-23 Thread Daniel van Vugt
** Package changed: gnome-desktop (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  The Activities top left button reacts to a mouse-up instead of click

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.


  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

  
  ---

  Description:  Ubuntu 17.10
  Release:  17.10

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

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


[Desktop-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

2017-10-23 Thread Daniel van Vugt
** Package changed: gnome-desktop (Ubuntu) => gnome-shell (Ubuntu)

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  nautilus lacks file search in the gnome activities screen

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

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  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/1725064/+subscriptions

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


[Desktop-packages] [Bug 1726192] Re: 17.10 Login To Wayland Fails Unless User Logs Into Unity First

2017-10-23 Thread Daniel van Vugt
** Changed in: gnome-desktop (Ubuntu)
   Status: Incomplete => New

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

Title:
  17.10 Login To Wayland Fails Unless User Logs Into Unity First

Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  After upgrading from 17.04 to 17.10, it's not possible to log into the
  default 'Ubuntu' session unless I log into Unity first. If I log into
  Unity, immediately log out, then log into Ubuntu, it logs in without
  issue.

  If I don't log into Unity first, the login attempt to Ubuntu briefly
  shows a black screen, then returns immediately to the login prompt.

  From suspend or hibernate, I can continue using the Wayland session
  without issue through poweroff. If I reboot or shutdown, the first
  login needs to be Unity, then I can log out and back to the Ubuntu
  session normally.

  Attached is some output from syslog showing gnome-session related
  errors. I'm not sure if they show the specific error, but they do
  appear at the time a first Ubuntu login is attempted.

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

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


[Desktop-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center

2017-10-23 Thread David Gil
I tried to address the user issue part using the virtual machine version
of Ubuntu 17.10. It is still the same.

** Attachment added: "vokoscreen-2017-10-24_11-42-07.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4990035/+files/vokoscreen-2017-10-24_11-42-07.mkv

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

Title:
  pptp vpn cannot be easily connected in gnome network manager and gnome
  control center

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I tried to reactivate a VPN (for PPTP) several times again and again
  using PPTP, and it is just that it just suddenly turns off every time
  I try to turn on. There is no process ongoing for PPTP.

  I tried to use an OpenVPN plugin for VPN, it works depending on the
  VPN server.

  I depend on VPN a lot especially on FreeVPN PPTP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 07:48:21 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

2017-10-23 Thread David Gil
I wish that the effect here in Ubuntu 7.10 GNOME Shell search is the
same as this when it is integrated in the files. I upgraded to Ubuntu
7.10 expecting for this.

** Attachment added: "Selection_009.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990022/+files/Selection_009.png

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

Title:
  nautilus lacks file search in the gnome activities screen

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen

2017-10-23 Thread David Gil
I got this instead though...

** Attachment added: "Screenshot from 2017-10-24 11-20-30.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990023/+files/Screenshot%20from%202017-10-24%2011-20-30.png

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

Title:
  nautilus lacks file search in the gnome activities screen

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I used to search a file and access it immediately using Ubuntu 16.04
  LTS and some other distributions of GNOME. However, this time, almost
  only folders are shown in the file search.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 08:23:44 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center

2017-10-23 Thread David Gil
If that could be the case, I updated the bug report to NetworkManager
component of GNOME instead.
https://bugzilla.gnome.org/show_bug.cgi?id=789341


** Attachment added: "Selection_008.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4990011/+files/Selection_008.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/1725055

Title:
  pptp vpn cannot be easily connected in gnome network manager and gnome
  control center

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  I tried to reactivate a VPN (for PPTP) several times again and again
  using PPTP, and it is just that it just suddenly turns off every time
  I try to turn on. There is no process ongoing for PPTP.

  I tried to use an OpenVPN plugin for VPN, it works depending on the
  VPN server.

  I depend on VPN a lot especially on FreeVPN PPTP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 07:48:21 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726634] Re: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users

2017-10-23 Thread Daniel van Vugt
It looks like you're logging in as root, is that correct?


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

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

Title:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  the sound laptop speaker is not working and it sound interface isnt
  showing in "sound" app. sound works perfectly in other users

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maximum2935 F chrome
maximum7304 F AudioThread
  CurrentDesktop: Unity
  Date: Mon Oct 23 19:05:32 2017
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.asset.tag: MAXIMUM
  dmi.board.name: 05GRXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: MAXIMUM
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5530 non-vPro
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1726403] Re: Sound app controls are gone from top bar menus

2017-10-23 Thread Daniel van Vugt
It's not enabled by default, but the option is there:

sudo apt install gnome-shell-extension-mediaplayer gnome-tweak-tool

Then open Gnome Tweak Tool > Extensions and enable it.

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

Title:
  Sound app controls are gone from top bar menus

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  In 17.04, when Rhythmbox was running, I was able to launch Rhyhmbox,
  play/pause, fast forward / reverse, etc., from the top bar menus, and
  the menus also showed the current playing song. I.e., there was
  essentially a mini-player in the top-bar menu.

  It's gone in 17.10. When I launch rhythmbox and then close the
  rhythmbox window, music keeps playing like in 17.04, but there's no
  way for me to control it or to easily open the main rhythmbox window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 09:27:34 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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


[Desktop-packages] [Bug 1726464] Re: Add option to disable sticky edges

2017-10-23 Thread Daniel van Vugt
Is this the sticky edges feature, or generally a cursor barrier problem?
Are you dragging a window when the problem happens?

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

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

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

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

Title:
  Add option to disable sticky edges

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

Bug description:
  The sticky edge thing between monitors is very annoying as the cursor
  never ends up where it should when it's moved over to the other
  screen. It's annoying to the degree that I feel like I can not use
  multiple monitors with standard Ubuntu anymore.

  Unity had an option to disable this, please add one to Gnome as well.

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

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


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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  17.10 ubuntu
  during caja operations of copying files to connected android phone. tried 
doing something in a different window of caja. busted

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Oct 23 19:44:02 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2016-07-23 (457 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/7
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f1171ae05a9:mov0x18(%rax),%rax
   PC (0x7f1171ae05a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-01 (22 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare saned sudo 
vboxusers

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

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


[Desktop-packages] [Bug 1726331] Re: gnome-shell crashed with SIGABRT

2017-10-23 Thread Daniel van Vugt
** 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/1726331

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  crash after startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 11:37:03 2017
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['pdfchain.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'torbrowser.desktop', 'chromium-browser.desktop', 
'pdfsam.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia:
   
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/nvidia-340/libGL.so.1
   ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.104
   ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.104
   ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.104
   ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.104
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_upda

2017-10-23 Thread Daniel van Vugt
hackel, I agree Launchpad could be made more intelligent. If you like
you can log an enhancement request here:
https://bugs.launchpad.net/launchpad/+filebug

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

Title:
  gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels()
  from _st_create_shadow_pipeline() from
  _st_create_shadow_pipeline_from_actor() from
  st_icon_update_shadow_pipeline()

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

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

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


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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1719124 ***
https://bugs.launchpad.net/bugs/1719124

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1719124
   gnome-shell crashed with signal 5 in g_settings_schema_get_value() from 
g_settings_schema_key_init() from g_settings_get_value(key="opaque-background") 
["Settings schema 'org.gnome.shell.extensions.dash-to-dock' does not contain a 
key named 'opaque-background'"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was testing some new Gnome-shell-extensions and immediately after
  having enabled one extension called "dashtodock" the system froze and
  I had to reboot via a tty.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  :~$ apt-cache policy gnome-shell-extension-dashtodock 
  gnome-shell-extension-dashtodock:
Installed: 61-1
Candidate: 61-1
Version table:
   *** 61-1 500
  500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

  I was expecting to enable and test some Gnome-shell-extensions, but
  after trying the one called "dashtodock" the system came to a halt and
  I had to login via tty and reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 22:09:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-07 (442 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () 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_settings_get_value () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
  UserGroups: adm cdrom dip kismet lpadmin lxd netdev plugdev sambashare sudo 
wireshark

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

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


[Desktop-packages] [Bug 1726666] Re: gnome-shell-extension-prefs crashed with signal 5.

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1719124 ***
https://bugs.launchpad.net/bugs/1719124

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


** This bug has been marked a duplicate of bug 1719124
   gnome-shell crashed with signal 5 in g_settings_schema_get_value() from 
g_settings_schema_key_init() from g_settings_get_value(key="opaque-background") 
["Settings schema 'org.gnome.shell.extensions.dash-to-dock' does not contain a 
key named 'opaque-background'"]

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

Title:
  gnome-shell-extension-prefs crashed with signal 5.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I've added some gnome-shell-extensions to my desktop, and after having
  enabled one called "dashtodock", the system inmmediately froze and I
  had to reboot via login in to tty2. As a result of that, I could no
  longer login to my system using the gnome-shell desktop, nor the
  Gnome-classic, nor the Ubuntu-on-x DE; I could, however, login with
  Unity.

  I think the culprit could be the gnome-shell-extension-dashtodock package.
  This is not a fresh-installed system, I've been upgrading since 16.04 I 
believe.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  :~$ apt-cache policy gnome-shell-extension-dashtodock
  gnome-shell-extension-dashtodock:
    Installed: 61-1
    Candidate: 61-1
    Version table:
   *** 61-1 500
  500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

  I was testing these extra functionalities that Gnome-shell-extension
  offer, and I was expecting this particular Gnome-shell-extension
  activated some new dock-related feature but could never experienced
  this new feature since the system came to a total halt and I had to
  reboot via a tty.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 22:08:49 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2016-08-07 (442 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () 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_settings_bind_with_mapping () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_bind () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell-extension-prefs crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
  UserGroups: adm cdrom dip kismet lpadmin lxd netdev plugdev sambashare sudo 
wireshark

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

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


[Desktop-packages] [Bug 1621723] Re: Desktop (nautilus) text no longer scales to HiDPI with the rest of the system. Stays small.

2017-10-23 Thread Daniel van Vugt
** Tags added: hidpi

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

Title:
  Desktop (nautilus) text no longer scales to HiDPI with the rest of the
  system. Stays small.

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Nautilus text no longer scales to HiDPI with the rest of the desktop.
  Stays small.

  (following recent updates/reinstall of yakkety)

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

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


[Desktop-packages] [Bug 1726116] Re: Thunderbird "unread email" counter doesn't always update when unread emails are opened

2017-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Thunderbird "unread email" counter doesn't always update when unread
  emails are opened

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  With Thunderbird in the Ubuntu Dock favorites, a counter will appear in the 
top-right showing the number of (I believe) a combination of unread emails 
and/or new email notifications. After opening some of those emails, the counter 
in the top-right doesn't always change. It looks like any unread emails that 
were present upon opening Thunderbird don't alter the counter when they're 
opened, but new emails received after Thunderbird is opened will alter the 
counter number when opened.

  EXPECTED BEHAVIOR
  For the counter number to be affected when emails are opened, regardless 
whether they were received after Thunderbird opened or not. (Could just be my 
ignorance as to whether the counter is alerting me of new email notifications 
or total unread emails.)

  BUG DISCOVERED USING
  Ubuntu 17.10
  Thunderbird 52.4.0
  GNOME 3.26.1
  Nvidia 384.90 proprietary driver
  X.org 1.19.5
  Linux kernel 4.13.0-16-generic

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

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


[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-23 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Importance: Low => Undecided

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

** Tags added: nvidia

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1725732] Re: gnome-shell crashed with SIGABRT in g_assertion_message() (icon_info_get_pixbuf_ready (icon_info))

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1722599 ***
https://bugs.launchpad.net/bugs/1722599

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


** This bug has been marked a duplicate of bug 1722599
   gnome-shell crash on search specific app 
[gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: 
(icon_info_get_pixbuf_ready (icon_info))]

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message()
  (icon_info_get_pixbuf_ready (icon_info))

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I log in, the desktop appears briefly (1-2s) and then I get sent
  back to the login screen.

  I have removed all extensions (by deleting everything in
  ~/.local/share/gnome-shell/extensions).

  This is Ubuntu 17.10.

  gnome-shell:
Installé : 3.26.1-0ubuntu4
Candidat : 3.26.1-0ubuntu4

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 17:05:06 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 
'workspace-g...@mathematical.coffee.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'emacs24.desktop', 'chromium-browser.desktop', 'eog.desktop', 
'gog_com-STAR_WARS_Tie_Fighter_Special_Edition_1.desktop', 
'gog_com-Sid_Meiers_Colonization_French_1.desktop', 'skype.desktop', 
'kde4-amarok.desktop', 'org.gnome.Nautilus.desktop', 'audacity.desktop', 
'qBittorrent.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2013-10-24 (1457 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_icon_info_load_icon_finish () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm cdrom dialout dip fuse lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1722599] Re: gnome-shell crash on search specific app [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))]

2017-10-23 Thread Daniel van Vugt
More details in duplicate bug 1725732.

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

Title:
  gnome-shell crash on search specific app
  [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  org.gnome.Shell.desktop[1759]:
  
Gtk:ERROR:/build/gtk+3.0-Th_a5U/gtk+3.0-3.22.24/./gtk/gtkicontheme.c:4258:gtk_icon_info_load_icon_finish:
  assertion failed: (icon_info_get_pixbuf_ready (icon_info))

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 19:20:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-25 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726116] Re: Thunderbird "unread email" counter doesn't always update when unread emails are opened

2017-10-23 Thread Daniel van Vugt
** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Thunderbird "unread email" counter doesn't always update when unread
  emails are opened

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  With Thunderbird in the Ubuntu Dock favorites, a counter will appear in the 
top-right showing the number of (I believe) a combination of unread emails 
and/or new email notifications. After opening some of those emails, the counter 
in the top-right doesn't always change. It looks like any unread emails that 
were present upon opening Thunderbird don't alter the counter when they're 
opened, but new emails received after Thunderbird is opened will alter the 
counter number when opened.

  EXPECTED BEHAVIOR
  For the counter number to be affected when emails are opened, regardless 
whether they were received after Thunderbird opened or not. (Could just be my 
ignorance as to whether the counter is alerting me of new email notifications 
or total unread emails.)

  BUG DISCOVERED USING
  Ubuntu 17.10
  Thunderbird 52.4.0
  GNOME 3.26.1
  Nvidia 384.90 proprietary driver
  X.org 1.19.5
  Linux kernel 4.13.0-16-generic

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

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


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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1718477 ***
https://bugs.launchpad.net/bugs/1718477

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  system generated report.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Oct 23 20:56:38 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_markup_parse_context_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGABRT in 
g_slice_free_chain_with_offset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1528319] Re: Scaling factors for HiDPI on multiple monitors

2017-10-23 Thread Rocko
It looks like it's working now in Ubuntu 17.10! In the display settings
you can set the resolution and the scaling individually per monitor if
you are using Wayland. You might have to turn on fractional scaling (see
http://www.omgubuntu.co.uk/2017/09/enable-fractional-scaling-gnome-
linux).

If I set my laptop monitor to 3840 x 2160 and 175% scaling and the
external monitor to 1920x1080 and 100% scaling, xrandr says:

Screen 0: minimum 320 x 200, current 2192 x 2313, maximum 8192 x 8192
XWAYLAND0 connected 2192x1233+0+1080 (normal left inverted right x axis y axis) 
350mm x 190mm
   2192x1233 59.89*+
XWAYLAND4 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
530mm x 300mm
   1920x1080 59.96*+

I am seeing a flickering white line just above the gnome top bar (and it
flickers on the right hand side), though.

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

Title:
  Scaling factors for HiDPI on multiple monitors

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

Bug description:
  Hello,

  a bug report for my problem was suggested here: 
https://answers.launchpad.net/ubuntu/+question/274062
  I also created a question at askubuntu: 
http://askubuntu.com/questions/614301/how-to-set-different-scaling-on-multiple-monitors

  I'm trying to use an external monitor on my HiDPI Dell XPS 13 9343. It
  has a resolution of 3200x1800. The monitor I'm trying to connect has a
  resolution of 2560x1440 (or 1920x1080). When using the notebook alone
  I need to use a scaling factor of 1,75 due to the high resolution. The
  problem occurs when changing the scaling factor for the external
  monitor, which is too high with 1,75.

  As the GUI settings describe, it is possible to set different scaling
  factors for different monitors. Unfortunately the settings always take
  effect on all monitors. For example:

  Scaling factor: 1
  Monitor 3200x1800: everything too small
  Monitor: 2560x1440: everything good

  Scaling factor 1,75: vice versa

  In the question on askubuntu (see above) you can see how the gsettings
  are changed when altering the scaling factor. It seems like it is not
  possible to set the value separately for each monitor.

  I would be grateful if you can check that. I hope all necessary
  information are included in the bug report. If not, please describe
  how I can help.

  Regards,
  lum3n

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 21 19:24:41 2015
  DistUpgraded: 2015-11-02 20:46:01,871 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installedError! Could 
not locate dkms.conf file.
   File:  does not exist.

   bcmwl, 6.30.223.248+bdcom, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-07-06 (168 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-02 (48 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd03/12/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-23 Thread Daniel van Vugt
** Summary changed:

- On login, display rotates to wrong orientation.
+ On login, display rotates to wrong orientation [HP Pavilion]

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1726509] Re: screen rotates randomly on ubuntu 17.10

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726160 ***
https://bugs.launchpad.net/bugs/1726160

*If* you can get the screen to rotate back to normal orientation, you
can then quickly try and press the rotation lock button (second circle
in the panel menu, top-right) to keep it there.

But yeah I know this makes the laptop unusable. I've seen it happen a
couple of different ways.

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

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

Title:
  screen rotates randomly on ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from Ubuntu 17.04 to 17.10. Everything went well, but 
when I boot up the system, my screen rotation was set to left. Then I tried 
using xandr to rotate my screen, but my every effort failed.
  Can anybody help me on the same?

  I have an HP Pavilion 14 inch laptop.

  Thank you.

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

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


[Desktop-packages] [Bug 1726333] Re: Mouse Cursor not available under Wayland

2017-10-23 Thread Daniel van Vugt
Also, this sounds contradictory. Which is true? :) ...

"Sorry for this being filed under xorg, but I do not get "Wayland" offered.
After logging in to Ubuntu 17.10 in Wayland" ...

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

** Tags added: cursor

** Summary changed:

- Mouse Cursor not available under Wayland
+ Mouse cursor flickers shortly and then vanishes under Wayland

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

Title:
  Mouse cursor flickers shortly and then vanishes under Wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sorry for this being filed under xorg, but I do not get "Wayland"
  offered.

  After logging in to Ubuntu 17.10 in Wayland, the mouse cursor flickers 
shortly and then is gone.
  In XOrg session all is fine.

  I had no issues with the cursor in the artful beta release - I was
  using the beta release of Ubuntu 17.10 7 to 10 days before the final
  release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 23 11:39:45 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:3801]
  InstallationDate: Installed on 2017-10-12 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 80VF
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a5819d75-73ad-458c-8bde-fd93b2f7d230 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1726509] Re: screen rotates randomly on ubuntu 17.10

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1726160 ***
https://bugs.launchpad.net/bugs/1726160

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


** This bug has been marked a duplicate of bug 1726160
   On login, display rotates to wrong orientation [HP Pavilion]

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

Title:
  screen rotates randomly on ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from Ubuntu 17.04 to 17.10. Everything went well, but 
when I boot up the system, my screen rotation was set to left. Then I tried 
using xandr to rotate my screen, but my every effort failed.
  Can anybody help me on the same?

  I have an HP Pavilion 14 inch laptop.

  Thank you.

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

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


[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

2017-10-23 Thread Launchpad Bug Tracker
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/1726160

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1726621] Re: Super+A doesn't close the Show Applications if it is already open

2017-10-23 Thread Daniel van Vugt
Wouldn't closing be the job of gnome-shell itself?

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

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

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

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

Title:
  Super+A doesn't close the Show Applications if it is already open

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

Bug description:
  Test Case
  =
  From Ubuntu 17.10:

  Press Super+A to open the Show Applications view.
  Press Super+A to exit it.

  What Happens
  
  Super+A shows the Activities Overview instead of exiting the Show 
Applications view and Activities Overview.

  Workaround
  --
  Press Super+A to open the Show Applications view.
  Press Super to exit.

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

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


[Desktop-packages] [Bug 1696030] Re: gnome-shell logging is too brief to be useful

2017-10-23 Thread Daniel van Vugt
I'm not sure Gnome bug 789237 alone is sufficient here.

A proper solution should log GPU and monitor details _always_ on
startup, to allow easier diagnosis of start-up bugs. Both Xorg and Mir
do this already...

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

** Description changed:

  gnome-shell appears to only log a couple of relevant lines at most on
  start-up (`journalctl /usr/bin/gnome-shell`):
  
  org.gnome.Shell.desktop[1893]: glamor: EGL version 1.4 (DRI2):
  gnome-shell[1893]: GNOME Shell started at Tue Jun 06 2017 09:38:50 GMT+0800 
(AWST)
  
- and also some "JS WARNING" messages. Not enough information to be useful
- for debugging peoples start-up issues.
+ Not enough information to be useful for debugging peoples' GPU and
+ monitor start-up issues.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun  6 10:04:35 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 
'cariboukkk', 'cariboujj']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-shell logging is too brief to be useful

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

Bug description:
  gnome-shell appears to only log a couple of relevant lines at most on
  start-up (`journalctl /usr/bin/gnome-shell`):

  org.gnome.Shell.desktop[1893]: glamor: EGL version 1.4 (DRI2):
  gnome-shell[1893]: GNOME Shell started at Tue Jun 06 2017 09:38:50 GMT+0800 
(AWST)

  Not enough information to be useful for debugging peoples' GPU and
  monitor start-up issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun  6 10:04:35 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 
'cariboukkk', 'cariboujj']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726608] Re: Alt+Arrow in gnome-shell unexpectedly switches VTs

2017-10-23 Thread Daniel van Vugt
** Summary changed:

- Alt + Arrow to switch windows takes me to gdm
+ Alt+Arrow in gnome-shell unexpectedly switches VTs

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

Title:
  Alt+Arrow in gnome-shell unexpectedly switches VTs

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again.

  Test Case
  -
  schroot -u root -c trusty-amd64
  edit /etc/apt/sources.list to xenial
  apt-get update
  apt-get install console-setup
  use alt+tab to bring up the window switcher
  then use alt+arrow to switch windows

  I then end up at the gdm login screen or a virtual tty.

  Installing a different set of packages, via apt-get dist-upgrade,
  actually ended up killing my desktop session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:30:16 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 
'datetime-for...@daniel-khodabakhsh.github.com', 
'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 
'firefox.desktop', 'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  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/1726608/+subscriptions

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


[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

2017-10-23 Thread Daniel van Vugt
It continues... bug 1726608

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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


[Desktop-packages] [Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen

2017-10-23 Thread Daniel van Vugt
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  two mouse cursors visible at the same time on rotated screen

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

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1725941] Re: hotCorner modification breaks official apps-menu extension

2017-10-23 Thread Daniel van Vugt
Someone could always attempt a proper fix and propose it upstream. If
upstream don't have to do the work then they might be more accepting of
a fix.

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

Title:
  hotCorner modification breaks official apps-menu extension

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 x64
  Activities Overview Hot Corner disabled using Gnome Tweaks

  When hot corners are disabled, the official Gnome Extension "Applications 
Menu"
   (https://extensions.gnome.org/extension/6/applications-menu/) is broken -- 
error shows when attempting to enable extensions and clicking menu does 
nothing. A small fix to the extension was suggested to the developer "Apps-menu 
crashes when there is no hotcorner"
   (https://bugzilla.gnome.org/show_bug.cgi?id=712625) but his response is that 
this problem does not fall in his court, at least while "dconf config option 
for disabling the activities hot corner" 
(https://bugzilla.gnome.org/show_bug.cgi?id=688320) is still open.

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

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


[Desktop-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

2017-10-23 Thread Daniel van Vugt
Thanks for your testing.

Yes, we already have PulseAudio 11 planned for inclusion in Ubuntu
18.04. It would have been included in Ubuntu 17.10, but PulseAudio 11.0
was released too late in the cycle.

** Tags added: pulse11

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

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

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

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

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


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

2017-10-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378

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


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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome shell freezes and restarts

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 21:08:46 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () from 
/usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1426163] Re: no locally integrated menus in gnome-terminal

2017-10-23 Thread Bug Watch Updater
** Changed in: gnome-terminal
   Status: Confirmed => Fix Released

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

Title:
  no locally integrated menus in gnome-terminal

Status in GNOME Terminal:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  see the enclose screenshot.

  compared to nautilus/unity-settings - you can see that there is no
  locally integrated menus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 26 23:28:54 2015
  InstallationDate: Installed on 2014-11-27 (91 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141123)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_upda

2017-10-23 Thread Treviño
The fix is ongoing, thanks

For future cases, in order to provide debug infos, just read this
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details
#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-
shell

Thanks

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

Title:
  gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels()
  from _st_create_shadow_pipeline() from
  _st_create_shadow_pipeline_from_actor() from
  st_icon_update_shadow_pipeline()

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

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

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


[Desktop-packages] [Bug 1716184] Re: failure of xrandr to find any outputs

2017-10-23 Thread gjs
I got the bios upgraded, but the problem has not gone away.  
I hope someone would look into this problem.  The machine is usable, but I 
cannot
access any display output except default, as described in the the original bug
report.  I can demonstrate that the hardware is correctly working by changing 
the 
bios setting to boot using the hdmi display, but then the laptop screen does 
not 
work and xrandr does not find it.

The current machine state is as follows:

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x4F0E8000.

Handle 0x, DMI type 222, 14 bytes
OEM-specific Type
Header and Data:
DE 0E 00 00 01 99 00 03 10 01 20 02 30 03
Strings:
Memory Init Complete
End of DXE Phase
BIOS Boot Complete

Handle 0x0001, DMI type 14, 8 bytes
Group Associations
Name: Intel(R) Silicon View Technology
Items: 1
0x ()

Handle 0x0002, DMI type 134, 13 bytes
OEM-specific Type
Header and Data:
86 0D 02 00 17 07 17 20 00 00 00 00 00

Handle 0x0003, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2

Handle 0x0004, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0003
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: Row Of Chips
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: LPDDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2133 MHz
Manufacturer: Micron
Serial Number: 
Asset Tag: None
Part Number: MT52L1G32D4PG-093 
Rank: 2
Configured Clock Speed: 2133 MHz
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.2 V

Handle 0x0005, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0003
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: Row Of Chips
Set: None
Locator: ChannelB-DIMM0
Bank Locator: BANK 2
Type: LPDDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2133 MHz
Manufacturer: Micron
Serial Number: 
Asset Tag: None
Part Number: MT52L1G32D4PG-093 
Rank: 2
Configured Clock Speed: 2133 MHz
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.2 V

Handle 0x0006, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x000
Ending Address: 0x003
Range Size: 16 GB
Physical Array Handle: 0x0003
Partition Width: 2

Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Parity
System Type: Unified
Associativity: 8-way Set-associative

Handle 0x0008, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 4-way Set-associative

Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3 Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 4096 kB
Maximum Size: 4096 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 16-way Set-associative

Handle 0x000A, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: E9 06 08 00 FF FB EB BF
Signature: Type 0, Family 6, Model 142, Stepping 9
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)

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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Logged in with Ubuntu on Xorg and this crash report came up straight
  away.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 23 01:37:51 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-22 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1716184] Re: failure of xrandr to find any outputs

2017-10-23 Thread gjs
** Description changed:

  I have a very new Lenovo X1 Yoga 2nd edition, with oled display.
  The exact model is 20JECTO1WW.
  The BIOS is N1NET27W.  I am running a vanilla Ubuntu 16.04
  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  
  uname -a
  Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  Until recently things worked quite well.  But on August 26 I got an update 
from Ubuntu and
  things began to decay.
  
  In particular, I can no longer display except on the built-in display:  For 
example, xrandr
  cannot find any outputs, even though this laptop has a (working) HDMI output 
port.
  
  xrandr --verbose
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
  default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm
-   Identifier: 0x271
-   Timestamp:  33974
-   Subpixel:   unknown
-   Clones:
-   CRTC:   0
-   CRTCs:  0
-   Transform:  1.00 0.00 0.00
-   0.00 1.00 0.00
-   0.00 0.00 1.00
-  filter: 
-   _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 
-   2560x1440 (0x272) 342.835MHz *current
- h: width  2560 start0 end0 total 2560 skew0 clock 
133.92KHz
- v: height 1440 start0 end0 total 1440   clock  93.00Hz
+  Identifier: 0x271
+  Timestamp:  33974
+  Subpixel:   unknown
+  Clones:
+  CRTC:   0
+  CRTCs:  0
+  Transform:  1.00 0.00 0.00
+  0.00 1.00 0.00
+  0.00 0.00 1.00
+ filter:
+  _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0
+   2560x1440 (0x272) 342.835MHz *current
+ h: width  2560 start0 end0 total 2560 skew0 clock 
133.92KHz
+ v: height 1440 start0 end0 total 1440   clock  93.00Hz
  
  Notice there are no (even disconnected) outputs other than default.
  
  Another symptom is that system restart always turns off the power rather
  than rebooting.
  
  I looked at the manifest of the update that seems to have caused trouble and 
the only
- suspicious entry is a microcode update from Intel.  
+ suspicious entry is a microcode update from Intel.
  Here is the entry from the apt history log:
  
  Start-Date: 2017-08-26  17:54:05
  Commandline: aptdaemon role='role-commit-packages' sender=':1.87'
  Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0),
  
  I hope that someone knows what is the problem here.  I am stumped.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  .tmp.unity_support_test.1:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  9 18:54:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:224e]
+  Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Device [17aa:224e]
  InstallationDate: Installed on 2017-07-27 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd 
-  Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd
+  Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20JECTO1WW
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET27W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  

[Desktop-packages] [Bug 1726642] Re: gnome-calendar crashed with SIGSEGV in gcal_manager_is_client_writable()

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1719273 ***
https://bugs.launchpad.net/bugs/1719273

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Crash with an unknown cause. Possibly related to the rejection of an
  untrusted SSL certificate.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 11:06:19 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x56387d72cf31 :
mov0x18(%rdi),%rdi
   PC (0x56387d72cf31) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_is_client_writable ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in 
gcal_manager_is_client_writable()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1726014] Re: gimp-2.8 crashed with SIGSEGV in printf_positional()

2017-10-23 Thread Seth Arnold
** Information type changed from Private Security to Public

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

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

Status in gimp package in Ubuntu:
  New

Bug description:
  I opened a photo in gimp. Tryed to cut a part og photo. Trhen tryed to
  revert, but gimp was crushed and after that couldn't opened a gimp.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:34:51 2017
  ExecutablePath: /usr/bin/gimp-2.8
  ProcCmdline: gimp-2.8
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff703418416 <__strlen_sse2+38>: movdqu 
(%rax),%xmm4
   PC (0x7ff703418416) ok
   source "(%rax)" (0x0009) not located in a known VMA region (needed 
readable region)!
   destination "%xmm4" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gimp
  StacktraceTop:
   printf_positional (s=s@entry=0x7fffaa0609a0, 
format=format@entry=0x7ff707c4a4fb , readonly_format=readonly_format@entry=0, 
ap=ap@entry=0x7fffaa060b30, ap_savep=ap_savep@entry=0x7fffaa060548, done=22, 
nspecs_done=1, lead_str_end=, work_buffer=, 
save_errno=, grouping=, thousands_sep=) at vfprintf.c:2023
   _IO_vfprintf_internal (s=s@entry=0x7fffaa0609a0, format=, 
format@entry=0x7ff707c4a4fb , ap=ap@entry=0x7fffaa060b30) at vfprintf.c:1688
   __GI___vasprintf_chk (result_ptr=0x7fffaa060af0, flags=1, 
format=0x7ff707c4a4fb , 
args=0x7fffaa060b30) at vasprintf_chk.c:66
   g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gimp-2.8 crashed with SIGSEGV in printf_positional()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


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

2017-10-23 Thread Seth Arnold
*** This bug is a duplicate of bug 1720400 ***
https://bugs.launchpad.net/bugs/1720400

** Information type changed from Private Security to Public

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Accounts on-line

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 09:16:25 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-05 (17 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb06a542f:mov0x4(%eax),%ecx
   PC (0xb06a542f) ok
   source "0x4(%eax)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

2017-10-23 Thread Brian Murray
** Changed in: udisks2 (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: udisks2 (Ubuntu)
 Assignee: Felipe Pereira Costa (felipecosta99) => (unassigned)

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


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

2017-10-23 Thread Jerome Covington
*** This bug is a duplicate of bug 1720400 ***
https://bugs.launchpad.net/bugs/1720400

Yeah, I'm seeing the same almost immediately after adding a Google
account.

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  g-c-c hangs then crashes after successful adding online account

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  Uname: Linux 4.13.7-041307-generic x86_64
  NonfreeKernelModules: 8723bu
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 19 11:13:19 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-08-30 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center background
  SegvAnalysis:
   Segfault happened at: 0x7f85caf39b3b:mov0x8(%rax),%rax
   PC (0x7f85caf39b3b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  UserGroups: adm cdrom dip i2c lpadmin plugdev sambashare sudo video

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

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


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

2017-10-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1724334 ***
https://bugs.launchpad.net/bugs/1724334

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724334
   gnome-shell crashed with signal 5 in clutter_box_layout_allocate() from 
st_widget_allocate()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was just trying to log in after locking my screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 16:40:00 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['sound-output-device-choo...@kgshank.net', 'multi-monitors-add-on@spin83', 
'datetime-for...@daniel-khodabakhsh.github.com', 
'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 
'firefox.desktop', 'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2013-01-16 (1741 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  ProcCmdline: gnome-shell --sm-client-id 
10aeea5677451824be150033639041251008268
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev 
sambashare sbuild sudo

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

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


[Desktop-packages] [Bug 1725667] Re: Wacom Intuos comic/draw/photo/art is not detected

2017-10-23 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  Wacom Intuos comic/draw/photo/art is not detected

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

Bug description:
  The tablet works but since it's not detected it's not possible to change 
settings from the control center. However, command-line commands such as 
''xsetwacom'' do work to an extent (could map the output to a specific monitor 
but could not assign a key to all 4 buttons of the tablet, only 2). The 
configuration is lost each time the pc is restarted or if the tablet is removed 
and then replugged.
  (ps. This bug might be related to the fact that this tablet does not have a 
''rubber'' on the other end of the pen, but I cannot confirm it).

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

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


[Desktop-packages] [Bug 1720442] Re: Software (gnome-software) crashes after several seconds. Entirely unusable.

2017-10-23 Thread Dan Bright
Think you're nailing it. The output references the snap I was attempting
to create one evening, before I abandoned the experiment and deleted it
(as referenced above). It was called "nominal-roll-generator".

** Attachment added: "nc.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1720442/+attachment/4989635/+files/nc.txt

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

Title:
  Software (gnome-software) crashes after several seconds. Entirely
  unusable.

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu version: Ubuntu Artful Aardvark (development branch), Release: 17.10
  gnome-software package version: 3.26.0-0ubuntu2

  Expected: To be able to use the application.

  What happened instead: The application crashes after several seconds.
  Bug replicated every time the application is opened, rending it
  entirely unusable.

  Journald shows a segfault, as per attached snippet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 21:01:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1726638] [NEW] some programs are missing icons in 17.10

2017-10-23 Thread Walt Mankowski
Public bug reported:

Several programs in this package, notably xload and xcalc, don't have
icons in the new dock in 17.10. Most of the others (e.g. xclock, xeyes)
do.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: x11-apps 7.7+6ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 19:35:45 2017
DistUpgraded: 2017-10-20 10:51:35,135 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.10.0-37-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev 
a1) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-12-27 (300 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ssd--vg-root--lv ro
SourcePackage: x11-apps
UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
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.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: x11-apps (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful possible-manual-nvidia-install ubuntu

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

Title:
  some programs are missing icons in 17.10

Status in x11-apps package in Ubuntu:
  New

Bug description:
  Several programs in this package, notably xload and xcalc, don't have
  icons in the new dock in 17.10. Most of the others (e.g. xclock,
  xeyes) do.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: x11-apps 7.7+6ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, 

[Desktop-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other

2017-10-23 Thread ChaiTan3
Using the following extra option in apt-get bypasses the problem.

-o Dpkg::Options::="--force-overwrite"

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

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

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


[Desktop-packages] [Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_upda

2017-10-23 Thread hackel
I just want to point out that when following the apport bug reporting
process, it initially pulls up a list of existing bugs by searching for
the subject "gnome-shell crashed with signal 5 in g_malloc0()", and this
bug does not show up in that list.  In fact, the most recent bug in that
list is from 2012.  As a result, people (or at least me, until now)
aren't finding this to report issues as a duplicate, and they are
commenting on these really old, unrelated bug reports.  It might be a
good idea to close out all of those old bugs so as to elevate issues
arising now that gnome-shell is the default.

I get hit with this bug multiple times a day, so I'm going to just stop
reporting it as I'm sure there are plenty of reports here by now, but
please let me know if there's anything I can do to assist with debugging
this issue.

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

Title:
  gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels()
  from _st_create_shadow_pipeline() from
  _st_create_shadow_pipeline_from_actor() from
  st_icon_update_shadow_pipeline()

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

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

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


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

2017-10-23 Thread hackel
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  appens seemingly random with no detected cause so far.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 17:57:33 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'thunderbird.desktop', 
'org.gnome.Terminal.desktop', 'Thunar.desktop', 'discord_discord.desktop', 
'shutter.desktop', 'xsane.desktop', 'xchat.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-21 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () from 
/usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


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

2017-10-23 Thread hackel
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378

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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  crash while connecting hdmi screen

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:46:55 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['nvidiatemp@baco', 
'cpufreq@konkor']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'google-chrome.desktop', 'rstudio.desktop', 'atom.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () from 
/usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


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

2017-10-23 Thread hackel
*** This bug is a duplicate of bug 1723378 ***
https://bugs.launchpad.net/bugs/1723378

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It was in the middle of the screen, probably trying to dock to the
  side of the screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 14:31:06 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges: b'org.gnome.shell' b'favorite-apps' 
b"['org.gnome.Nautilus.desktop', 'keepassx.desktop', 'google-chrome.desktop', 
'firefox.desktop', 'gnome-control-center.desktop']"
  InstallationDate: Installed on 2017-06-08 (137 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () from /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () from 
/usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1725708] Re: Gedit (Text Editor) window minimizes on right click due to wrongly placed bubble menu.

2017-10-23 Thread Doug McMahon
Atm I'd put 'blame' on ubuntu themes (ambiance, radiance) while in wayland 
session & maybe only with gedit.
If using awaita theme this won't occur even if the bubble menu opens slightly 
outside header bar.
(- it seems the actual cursor position when initiating the r. click will affect 
where the top of the bubble menu is.

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

Title:
  Gedit (Text Editor) window minimizes on right click due to wrongly
  placed bubble menu.

Status in GNOME Shell:
  Confirmed
Status in gedit package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Login to the default Ubuntu session
  3. Open Gedit text editor
  3. Make right mouse click on its top window bar
  4. Window drop-down menu is shown, mouse is over "Minimize" option

  Expected results:
  * window drop-down menu is opened, user is able to select option from it (for 
example move to other workspace or maximize)

  Actual results:
  * Gedit window got minimized instantly

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 17:27:44 2017
  DisplayManager: gdm3
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725888] Re: Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

2017-10-23 Thread dennyg...@gmail.com
I can add this, this is a completely fresh install as of just three or
four days ago via the 17.10 iso. there should be then no trace of Unity,
of I am not mistaken. So i think I can attest to this being a gnome
issue via wayland. again, simply installing parcellite suffices, as long
as you don't mind the parcellite icon constantly being on the top right.
but a clipboard manager is really a necessary thing these days if you
work on your nix box like I do.

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

Title:
  Ubuntu 17.10: clipboard contents lost if app is closed (Wayland)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 has no functioning clipboard manager. This means that if
  you copy something from an application, and then close that
  application before pasting it elsewhere, it's lost.

  For now I was able to fix this issue by installing parcellite.

  Also, there should be a better way to add a bug report to launchpad
  than fudging it like i had to, but I brought this up as a bug before,
  to no joy.

  -Denny

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-release-upgrader-core 1:17.10.7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 20:57:29 2017
  InstallationDate: Installed on 2017-10-20 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  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/1725888/+subscriptions

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


  1   2   3   4   5   >