date:20171219

Also tracking in:
https://errors.ubuntu.com/problem/6beead7e96eaeffc4ef77511ca7b9e70982af8c0

** Description changed:

+ https://errors.ubuntu.com/problem/6beead7e96eaeffc4ef77511ca7b9e70982af8c0
+ 
+ ---
+ 
  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset()
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 11:57:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  GsettingsChanges:
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome.desktop', 'libreoffice-startcenter.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop', 
'org.gnome.Screenshot.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome.desktop', 'libreoffice-startcenter.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop', 
'org.gnome.Screenshot.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-15 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANGUAGE=en_GB:en
-  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANGUAGE=en_GB:en
+  LANG=en_GB.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7feb6b6963a8 :   
mov0x30(%rdi),%rbp
-  PC (0x7feb6b6963a8) ok
-  source "0x30(%rdi)" (0x0031) not located in a known VMA region (needed 
readable region)!
-  destination "%rbp" ok
+  Segfault happened at: 0x7feb6b6963a8 :   
mov0x30(%rdi),%rbp
+  PC (0x7feb6b6963a8) ok
+  source "0x30(%rdi)" (0x0031) not located in a known VMA region (needed 
readable region)!
+  destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  icaltimezone_get_utc_offset () from /usr/lib/x86_64-linux-gnu/libical.so.3
-  icaltimezone_convert_time () from /usr/lib/x86_64-linux-gnu/libical.so.3
-  icaltime_convert_to_zone () from /usr/lib/x86_64-linux-gnu/libical.so.3
-  icaltime_compare () from /usr/lib/x86_64-linux-gnu/libical.so.3
-  ?? () from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
+  icaltimezone_get_utc_offset () from /usr/lib/x86_64-linux-gnu/libical.so.3
+  icaltimezone_convert_time () from /usr/lib/x86_64-linux-gnu/libical.so.3
+  icaltime_convert_to_zone () from /usr/lib/x86_64-linux-gnu/libical.so.3
+  icaltime_compare () from /usr/lib/x86_64-linux-gnu/libical.so.3
+  ?? () from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server crashed with SIGSEGV in 
icaltimezone_get_utc_offset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/6beead7e96eaeffc4ef77511ca7b9e70982af8c0

  ---

  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 11:57:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome.desktop', 'libreoffice-startcenter.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop', 
'org.gnome.Screenshot.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-15 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash

[Desktop-packages] [Bug 1736664] Re: /usr/bin/gnome-shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log

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

** This bug is no longer 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()
** 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/1736664

Title:
  /usr/bin/gnome-
  shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1737702] Re: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset()

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

Title:
  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/6beead7e96eaeffc4ef77511ca7b9e70982af8c0

  ---

  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset()

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 11:57:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome.desktop', 'libreoffice-startcenter.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop', 
'org.gnome.Screenshot.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-15 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7feb6b6963a8 :   
mov0x30(%rdi),%rbp
   PC (0x7feb6b6963a8) ok
   source "0x30(%rdi)" (0x0031) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   icaltimezone_get_utc_offset () from /usr/lib/x86_64-linux-gnu/libical.so.3
   icaltimezone_convert_time () from /usr/lib/x86_64-linux-gnu/libical.so.3
   icaltime_convert_to_zone () from /usr/lib/x86_64-linux-gnu/libical.so.3
   icaltime_compare () from /usr/lib/x86_64-linux-gnu/libical.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server crashed with SIGSEGV in 
icaltimezone_get_utc_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-shell/+bug/1737702/+subscriptions

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

[Desktop-packages] [Bug 1739364] [NEW] Hp Laptop Airplane mode won't turn off after sleep mode.

2017-12-19 Thread Jay Narale

Public bug reported:

Whenever my Dual boot Ubuntu Hp Laptop is put to sleep by closing the
lid, airplane mode won't turn off.I have tried rfkill ,reset the power
management settings but nothing seems to work.This was not the problem
in my ubuntu 16.04 but when I updated to 17.10, this problem has arisen.

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: gnome-nettool (Ubuntu) => ubuntu

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

Title:
  Hp Laptop Airplane mode won't turn off  after sleep mode.

Status in Ubuntu:
  New

Bug description:
  Whenever my Dual boot Ubuntu Hp Laptop is put to sleep by closing the
  lid, airplane mode won't turn off.I have tried rfkill ,reset the power
  management settings but nothing seems to work.This was not the problem
  in my ubuntu 16.04 but when I updated to 17.10, this problem has
  arisen.

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

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

[Desktop-packages] [Bug 1739361] Re: gnome-shell-calendar-server crashed with SIGSEGV in icaltimezone_get_utc_offset() from icaltimezone_convert_time() from icaltime_convert_to_zone() from icaltime_co

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

** Summary changed:

- 
/usr/lib/gnome-shell/gnome-shell-calendar-server:11:icaltimezone_get_utc_offset:icaltimezone_convert_time:icaltime_convert_to_zone:icaltime_compare:cal_obj_remove_duplicates_and_invalid_dates
+ gnome-shell-calendar-server crashed with SIGSEGV in 
icaltimezone_get_utc_offset() from icaltimezone_convert_time() from 
icaltime_convert_to_zone() from icaltime_compare() from 
cal_obj_remove_duplicates_and_invalid_dates()

** This bug has been marked a duplicate of bug 1737702
   gnome-shell-calendar-server crashed with SIGSEGV in 
icaltimezone_get_utc_offset()

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

Title:
  gnome-shell-calendar-server crashed with SIGSEGV in
  icaltimezone_get_utc_offset() from icaltimezone_convert_time() from
  icaltime_convert_to_zone() from icaltime_compare() from
  cal_obj_remove_duplicates_and_invalid_dates()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

2017-12-19 Thread Kulasangar Gowrisangar

I'm using the latest version of 17.10 and whenever I play videos on full 
screen, the OS get freezed.
Hence I had to restart my machine, every single time in order to get back 
alive. The file I've played was a .mp4 file.

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

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

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

[Desktop-packages] [Bug 1739361] [NEW] /usr/lib/gnome-shell/gnome-shell-calendar-server:11:icaltimezone_get_utc_offset:icaltimezone_convert_time:icaltime_convert_to_zone:icaltime_compare:cal_obj_remov

2017-12-19 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: bionic

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

Title:
  /usr/lib/gnome-shell/gnome-shell-calendar-
  
server:11:icaltimezone_get_utc_offset:icaltimezone_convert_time:icaltime_convert_to_zone:icaltime_compare:cal_obj_remove_duplicates_and_invalid_dates

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1739362] [NEW] /usr/bin/gnome-software:11:g_mutex_lock:g_main_loop_quit:do_call:call_vanished_handler:call_vanished_handler

2017-12-19 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: artful bionic kylin-17.10 zesty

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

Title:
  /usr/bin/gnome-
  
software:11:g_mutex_lock:g_main_loop_quit:do_call:call_vanished_handler:call_vanished_handler

Status in gnome-software package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

2017-12-19 Thread Hairong Zhu

I have this problem on Dell Inspiron 7370(Realtek ALC3254) when using
Xubuntu 17.10(4.13 kernel). After upgrading to Ubuntu mainline kernel
4.14, the problem seems gone.

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1739346] [NEW] Freeze up

2017-12-19 Thread Carlos Hamer

Public bug reported:

OS freezes up all the time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Dec 19 23:16:31 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
MachineType: Gateway NE56R
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EG50_HC_HR
dmi.board.vendor: Gateway
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.13
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
dmi.product.family: Type1Family
dmi.product.name: NE56R
dmi.product.version: V2.13
dmi.sys.vendor: Gateway
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.4-0ubuntu1~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Nov 12 16:56:54 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Freeze up

Status in xorg package in Ubuntu:
  New

Bug description:
  OS freezes up all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec 19 23:16:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0649]
  MachineType: Gateway NE56R
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=056e1ca6-0c77-4e90-afee-879313071881 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnGateway:pnNE56R:pvrV2.13:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.family: Type1Family
  dmi.product.name: NE56R
  dmi.product.version: V2.13
  dmi.sys.vendor: Gateway
  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.4-0ubuntu1~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev:

[Desktop-packages] [Bug 989611] Re: terminal not working properly problem inside usr/bin

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

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

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

Title:
  terminal not working properly problem inside usr/bin

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  terminal is empty.No user or root at all

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Fri Apr 27 16:36:39 2012
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1525579] Re: terminal freezes when I use : run-mozilla.sh

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

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

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

Title:
  terminal freezes when I use : run-mozilla.sh

Status in gnome-terminal package in Ubuntu:
  Expired

Bug description:
  i cannot update firefox-3.0 to  firefox-42.0.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: LinuxMint 7
  ExecutablePath: /usr/bin/gnome-terminal
  Package: gnome-terminal 2.26.0-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  Uname: Linux 2.6.28-11-generic i686
  UnreportableReason: This is not a genuine LinuxMint package

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

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

[Desktop-packages] [Bug 1656034] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

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

** Changed in: doc-base (Ubuntu)
   Status: New => Confirmed

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

Title:
  package doc-base 0.10.7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in doc-base package in Ubuntu:
  Confirmed

Bug description:
  Rebooted, this error popped up, recently upgraded perl and uninstalled
  apache2

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: doc-base 0.10.7
  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
  Date: Thu Jan 12 11:46:51 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-12-14 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: doc-base
  Title: package doc-base 0.10.7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/1656034/+subscriptions

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

[Desktop-packages] [Bug 1734890] Re: pulse audio does not load because "module-switch-on-connect" should be loaded once at most

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

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 1720519, 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 1720519
   KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at 
most. Refusing to load.

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

Title:
  pulse audio does not load because "module-switch-on-connect" should be
  loaded once at most

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This laptop was initially loaded with kubuntu 17.04. Yesterday I used
  do-release-upgrade to update to 17.10.

  This morning I noticed that the pulse audio mixer was broken while
  chrome and amarok could still play sound.  Cold booted just in case.

  Still no pulse mixing.  But alsamixer was working.  Found that no
  pulse processes are running.

  
$ ps auxww | grep pulse
niclangf  9666  0.0  0.0  15900  1180 pts/3S+   15:13   0:00 grep 
--color=auto pulse
$ pulseaudio 
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most. 
Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
$ ps auxww | grep pulse
niclangf  9833  0.0  0.0  15900  1036 pts/3S+   15:16   0:00 grep 
--color=auto pulse

  Removed .config/pulse and .gconf/system/pulseaudio

$ pulseaudio 
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.pulse-cookie': No such file or directory
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most. Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.

$ pulseaudio 
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most.  Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.

  Nicolai

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Nov 28 15:11:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-18 (133 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-11-27 (1 days ago)
  dmi.bios.date: 12/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET25W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS1C200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS1C200:pvrThinkPadT470s:rvnLENOVO:rn20HGS1C200:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HGS1C200
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

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

** Tags added: sru

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

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

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

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

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

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

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

  # environment information:

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

   * uname -r: 4.4.0-73-generic

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

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

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

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

[Desktop-packages] [Bug 1739022] Re: Wayland session does not start any more when bash is the default shell

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1739019] Re: Gnome Shell does not start in Xorg mode

Thanks. This log message of yours might be related:

Dec 20 07:39:17 hostname gnome-shell[1471]: setup_framebuffers: assertion 
'width > 0' failed
Dec 20 07:39:17 hostname gnome-shell[1471]: setup_framebuffers: assertion 
'width > 0' failed

Please try removing your monitor config file (delete or rename): 
~/.config/monitors.xml
and then log in again.

If that doesn't work, please also attach:
 * Output from 'lspci -k'
 * /var/log/Xorg.*   (from immediately after the problem has been reproduced)


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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

[Desktop-packages] [Bug 1739022] Re: Wayland session does not start any more when bash is the default shell

apport information

** Tags added: apport-collected bionic third-party-packages wayland-
session

** Description changed:

  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.
  
  
  How I discovered the issue:
  
  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my fish
  configuration. That solved the issue.
  
  However, I was worried that /etc/profile.d might contain more important
  scripts and new apps might add more scrpts there that I don't want to
  miss out on, so I switched back to bash to try it out. To my surprise
  the wayland session stopped working. GDM logged me in to a black screen
  with white cursor in the center. The cursor does not move and nothing
  happens.
  
  I thought this might be because one of the scripts in /etc/profile.d/ so
  I removed them all. Also removed /etc/bash.bashrc. However this did not
  fix the issue at all. I removed the bashrc related files in my home
  directory as well.
  
  So for me, wayland session does not start when bash is my default shell.
  Only works with fish.
  
  
  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019
  
- However, I cannot prove that X11 fails because of the same reason
- because it never runs irrespective of whether I use bash or fish as my
- default shell.
+ However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-11-19 (30 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ Package: gnome-shell 3.26.2-0ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
+ Tags: third-party-packages wayland-session bionic
+ Uname: Linux 4.13.0-17-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8

[Desktop-packages] [Bug 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

** Description changed:

+ Need to have fix in Bionic, better to have it in xenial.
+ 
  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.
  
  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

** Changed in: oem-priority/xenial
   Importance: Medium => Critical

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

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  New
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  Need to have fix in Bionic, better to have it in xenial.

  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1691032/+subscriptions

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

[Desktop-packages] [Bug 1739019] Re: Gnome Shell does not start in Xorg mode

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

apport information

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 362091] Re: The selection should not change when using back or forward navigation

** Changed in: nautilus
   Status: New => Invalid

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

Title:
  The selection should not change when using back or forward navigation

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Invalid
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  This is a very frustrating bug that remains in Gnome 2.24.1: Nautilus
  2.24.1.  I think this is a bug and not really a wishlist item.

  Reproduce it:
  1. Open home dir in Nautilus.
  2. Select a subdirectory of home, say "my_dir".
  3. Open that dir by hitting Enter or Ctrl+o.
  4. Click Nautilus' "BACK" button.
  5. BUG: Actual Behavior is that the selection is cleared.  Expected behavior 
is
  that the selection remain from the last time I viewed that directory.

  Caveat and inconsistency:
  1. Open home dir in Nautilus.
  2. Select a subdirectory of home, say "my_dir".
  3. Open that dir by hitting Enter or Ctrl+o.
  4. Click Nautilus' "UP" button.
  5. The behavior that I would expect for going BACK is is found!  The
  subdirectory ("my_dir") is now in the selection.  In fact, would say this 
could
  be another bug as well.  I expect the "UP" action to act as if I am navigating
  to a new directory, a fresh start.  I do not want the directory I was in to be
  selected.

  Perhaps the code for BACK and UP got swapped accidentally?


  Example use case: I want to examine a directory's contents before doing
  something with it (copying, moving, deleting, etc.):
  1. Open my home directory in Nautilus.
  2. Double-click some directory, say "my_dir" to view its contents.
  3. I see that it's some stuff I want to copy to a flash drive.
  4. Use Nautilus' "Back" button to go back to my home directory.
  5. Assuming that the "my_dir" directory remains selected, I can easily pick it
  out in the long list of files without worrying if I got the right one or not. 
  I can even do a Edit->Copy without having to find "my_dir" again and reselect.

  
  This bug may be related to Bug #64287 (spatial nautilus should remember 
selected items), but that deals with "spatial" nautilus and with closed windows.

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/nautilus
  Package: nautilus 1:2.24.1-0ubuntu2
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  Uname: Linux 2.6.27-11-generic x86_64

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

** Changed in: nautilus
   Status: Unknown => Confirmed

** Changed in: nautilus
   Importance: Unknown => Critical

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

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

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

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

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

apport information

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1739022] Re: Wayland session does not start any more when bash is the default shell

Uploaded the information. 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/1739022

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1672619] Re: "disable touchpad while typing" doesn't work on xps 13 and some other laptop

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  "disable touchpad while typing" doesn't work on xps 13 and some other
  laptop

Status in OEM Priority Project:
  Triaged
Status in Xserver Xorg Input Synaptics:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  It's reported that there are lots of false action of touch pad as using 
keyboard on xps 13
  with the factory image.

  The factory image is based on xenial.

  One propose that install xserver-xorg-input-libinput with modification
  90-libinput.conf in /usr/share/X11/xorg.conf.d from

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  EndSection
  ...

  to

  ...
  Section "InputClass"
  Identifier "libinput touchpad catchall"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Driver "libinput"
  Option "Tapping" "on"
  Option "PalmDetection" "on"
  EndSection
  ...

  helps a lot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1672619/+subscriptions

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736227

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed on start after the last update procedure

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Dec  4 20:42:44 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-08 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171108)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1734330

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

Status in gnome-shell package in Ubuntu:
  New

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-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.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Nov 24 08:47:53 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (67 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1735819

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This message has begon to be displayed after upgrading the kernel to
  4.13.0-18... Actualy I had problem with the nvidia driver after the
  upgrade. I'm trying to reinstall it.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Dec  1 17:10:48 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-29 (63 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: 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/1735819/+subscriptions

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1733275

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with signal 5 in g_log_default_handler

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-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.8-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 20 09:17:50 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (63 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1734755

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running gnome-shell and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  Uname: Linux 4.14.2-041402-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 27 15:24:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (45 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1351772] Re: "disable touchpad while typing" doesn't work

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  "disable touchpad while typing" doesn't work

Status in OEM Priority Project:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  When selecting "disable while typing" under the touchpad section of
  the "Mouse & Touchpad" preferences, nothing changes, the touchpad
  stays active while typing. I can rapidly type multiple characters with
  my left hand and continue to move the cursor with the touchpad with my
  right hand.

  I can see from my processlist that syndaemon is running with the
  following options:

   2185 ?S  1:31  |   \_ syndaemon -i 1.0 -t -K -R

  First, the -t option isn't what's expected with this setting, it
  should disable the touchpad entirely. Also, it doesn't seem to even do
  that correctly, as I can definitely click the touchpad while typing as
  well as moving the cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  Uname: Linux 3.14.0-997-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug  2 17:20:22 2014
  InstallationDate: Installed on 2014-04-22 (102 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1351772/+subscriptions

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736030

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I'm working... and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  Uname: Linux 4.14.3-041403-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Dec  1 15:44:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (51 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1734276

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Just started. only firefox active.
  corrado@corrado-p6-bb-1114:~$ inxi -Fx
  System:Host: corrado-p6-bb-1114 Kernel: 4.13.0-16-generic x86_64 bits: 64 
gcc: 7.2.0
 Desktop: Gnome 3.26.2 (Gtk 2.24.31) Distro: Ubuntu Bionic Beaver 
(development branch)
  Machine:   Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: 
American Megatrends v: P1.10 date: 05/11/2017
  CPU:   Dual core Intel Core i3-7100 (-HT-MCP-) arch: Skylake rev.9 cache: 
3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 3900 MHz 2: 3900 MHz 3: 3900 MHz 4: 
3900 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.5 ) driver: i915 Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.2.4 Direct Render: Yes
  Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 
00:1f.3
 Sound: Advanced Linux Sound Architecture v: k4.13.0-16-generic
  Network:   Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 
3.2.6-k bus-ID: 00:1f.6
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86
  Drives:HDD Total Size: 1000.2GB (1.6% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 6.9G (24%) fs: ext4 dev: /dev/sda6
 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 34.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 232 Uptime: 8 min Memory: 1179.2/7684.1MB Init: systemd 
runlevel: 5 Gcc sys: 7.2.0
 Client: Shell (bash 4.4.121) inxi: 2.3.40 
  corrado@corrado-p6-bb-1114:~$ 

  corrado@corrado-p6-bb-1114:~$ apt policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu1
Candidate: 3.26.2-0ubuntu1
Version table:
   *** 3.26.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p6-bb-1114:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Nov 23 22:24:01 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-16 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171114)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

** Changed in: oem-priority/xenial
   Status: In Progress => Confirmed

** Changed in: oem-priority/xenial
   Importance: Critical => Medium

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

   * It is a very bad user experience that the WiFi device is recognized
  as an Ethernet device making Ubuntu users unable to connect to WiFi
  network.

  [Test Case]

   * Find some laptop that can reduplicate this issue.
   * Keep rebooting the system until you see this issue.
   * Usually this issue can be reduplicated within 10 reboot cycles on the 
right laptop.

  [Regression Potential]

   * No trivial regression.

  [Other Info]
   
   * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial

  [Original Bug Description]

  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1732907

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with signal 5 in g_log_default_handler

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-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.8-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Nov 17 14:27:19 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736512

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  That crash happen after trying to use the driver r8168-dkms (which
  fully fails) for better performance with that r8168e chipset, instead
  of the kernel builtin r8169 which set a 576 MTU instead of a supported
  1500.

  This is with a gnome on xorg login session.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Dec  5 17:14:05 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1735883

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happened right after startup

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Nov 30 10:01:39 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-12 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: 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/1735883/+subscriptions

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

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

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

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 1505409, 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 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/1732878

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

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

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Nov 16 06:57:59 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-14 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2017-11-15 (1 days ago)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1733673

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

Status in gnome-shell package in Ubuntu:
  New

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-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.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Nov 21 19:47:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (64 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1739335] [NEW] Decimal to fractions conversion not always correct.

2017-12-19 Thread rjs1943

Public bug reported:

Example: In Libre office calc: If I put in a decimal number like .5 in
A1 and format B1 a fraction (# ??/??) and then put formula =A1 it shows
1/2.  But if I put in .75 in A1, B1 then shows a 1 and should be 3/4. It
does this error on some decimals, not all.  Is there a fix for this
soon.  I don't have this problem in Excel or WPS Spreadsheet
applications.

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

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

Title:
  Decimal to fractions conversion not always correct.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Example: In Libre office calc: If I put in a decimal number like .5 in
  A1 and format B1 a fraction (# ??/??) and then put formula =A1 it
  shows 1/2.  But if I put in .75 in A1, B1 then shows a 1 and should be
  3/4. It does this error on some decimals, not all.  Is there a fix for
  this soon.  I don't have this problem in Excel or WPS Spreadsheet
  applications.

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

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

[Desktop-packages] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

** Changed in: oem-priority
   Importance: Critical => High

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736693

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This error just popped up, I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Dec  6 09:33:38 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-08-21 (106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

apport information

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

[Desktop-packages] [Bug 1739022] Re: Wayland session does not start with bash as default shell

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1739022

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Summary changed:

- Wayland session does not start with bash as default shell
+ Wayland session does not start any more when bash is the default shell

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

Title:
  Wayland session does not start any more when bash is the default shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It appears the wayland session does not start on my XPS 13 on Ubuntu
  17.10 and 18.04 if I use bash as my default shell. It only works if I
  switch my default shell to fish.


  How I discovered the issue:

  I've used fish for a few years now. Recently I realized that snap apps
  don't show up in Gnome shell dash. Turns out `/var/lib/snapd/desktop/`
  was not part of `$XDG_DATA_DIRS`. Turns out it is set by one of the
  scripts in `/etc/profile.d/` and since I've set fish as my default
  shell, this never runs. I solved this by adding this manually in my
  fish configuration. That solved the issue.

  However, I was worried that /etc/profile.d might contain more
  important scripts and new apps might add more scrpts there that I
  don't want to miss out on, so I switched back to bash to try it out.
  To my surprise the wayland session stopped working. GDM logged me in
  to a black screen with white cursor in the center. The cursor does not
  move and nothing happens.

  I thought this might be because one of the scripts in /etc/profile.d/
  so I removed them all. Also removed /etc/bash.bashrc. However this did
  not fix the issue at all. I removed the bashrc related files in my
  home directory as well.

  So for me, wayland session does not start when bash is my default
  shell. Only works with fish.


  It might be related to this: https://bugs.launchpad.net/ubuntu/+source
  /gnome-shell/+bug/1739019

  However, I cannot prove that X11 fails because of the same reason because it 
never runs irrespective of whether I use bash or fish as my default shell.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell 3.26.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

apport information

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

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

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1739018] Re: Gnome shell is sometimes slow to recognize some running apps

apport information

** Tags added: apport-collected bionic third-party-packages wayland-
session

** Description changed:

  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to recognize
  that an app is running and show it in launcher and alt-tab. It does
  however show the window immediately in the window spread UI.
  
  This mostly happens with electron apps especially after a cold boot.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-11-19 (30 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ Package: gnome-shell-extension-ubuntu-dock
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
+ Tags: third-party-packages wayland-session bionic
+ Uname: Linux 4.13.0-17-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736573

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  just booted

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Dec  5 07:47:01 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1737294

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

Status in gnome-shell package in Ubuntu:
  New

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Dec  8 22:22:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (82 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

apport information

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

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

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

apport information

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1737238

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I'm working and open apport

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  Uname: Linux 4.15.0-041500rc2-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Dec  7 15:02:44 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (56 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

apport information

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

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

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.
  --- 
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-11-19 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Tags: third-party-packages wayland-session bionic
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2017-12-01 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1739019] Re: Gnome Shell does not start in Xorg mode

I've uploaded the report but from a working Wayland session as Xorg does
not run at all.

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

[Desktop-packages] [Bug 1739019] Re: Gnome Shell does not start in Xorg mode

apport information

** Tags added: apport-collected bionic third-party-packages wayland-
session

** Description changed:

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

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

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1736771

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

Status in gnome-shell package in Ubuntu:
  New

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

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Dec  5 17:34:43 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-17 (79 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1737235

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  just started, only firefox active
  corrado@corrado-HP-p3-bb:~$ inxi -Fx
  System:Host: corrado-HP-p3-bb Kernel: 4.13.0-17-generic x86_64 bits: 64 
gcc: 7.2.0
 Desktop: Gnome 3.26.2 (Gtk 2.24.31) Distro: Ubuntu Bionic Beaver 
(development branch)
  Machine:   Device: laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 serial: N/A
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: N/A UEFI: 
Insyde v: F.36 date: 12/18/2014
  BatteryBAT1: charge: 21.3 Wh 90.9% condition: 23.4/23.4 Wh (100%) model: 
13-42 OA03031 status: Discharging
  CPU:   Dual core Intel Core i5-4210U (-HT-MCP-) arch: Haswell rev.1 
cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9578
 clock speeds: max: 2700 MHz 1: 2394 MHz 2: 2394 MHz 3: 2394 MHz 4: 
2394 MHz
  Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller bus-ID: 
00:02.0
 Display Server: x11 (X.Org 1.19.5 ) driver: i915 Resolution: 
1366x768@60.00hz
 OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 
17.2.4 Direct Render: Yes
  Audio: Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel 
bus-ID: 00:1b.0
 Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel 
bus-ID: 00:03.0
 Sound: Advanced Linux Sound Architecture v: k4.13.0-17-generic
  Network:   Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
controller
 driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 08:00.0
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce
 Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: 
rt2800pci v: 2.3.0 bus-ID: 09:00.0
 IF: wlo1 state: up mac: ac:d1:b8:82:03:5d
  Drives:HDD Total Size: 500.1GB (2.2% used)
 ID-1: /dev/sda model: ST500LT012 size: 500.1GB
  Partition: ID-1: / size: 32G used: 6.4G (22%) fs: ext4 dev: /dev/sda3
 ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 39.0C mobo: 39.0C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 227 Uptime: 9 min Memory: 1296.4/3880.0MB Init: systemd 
runlevel: 5 Gcc sys: 7.2.1
 Client: Shell (bash 4.4.121) inxi: 2.3.45 
  corrado@corrado-HP-p3-bb:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Dec  8 17:02:20 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-12-04 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171128)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1737501

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Got that crash while upgrading some applets from extensions.gnome.org

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 11 10:00:15 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

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

** This bug is no longer a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()
** 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/1739113

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I', working with gnome-shell and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500rc4-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Dec 19 13:06:12 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1512819693
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (67 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

** Changed in: oem-priority/xenial
   Importance: Undecided => Medium

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

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  New
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1691032/+subscriptions

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

[Desktop-packages] [Bug 1318875] Re: Airplane mode cannot save the previous status after reboot

** Changed in: oem-priority
   Importance: Medium => Low

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

Title:
  Airplane mode cannot save the previous status after reboot

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  Airplane mode cannot save the previous status after reboot.

  Steps to reproduce:
  1. open network settings
  2. turn on airplane mode
  3. reboot -> issue occurs, airplane mode is off
  ---
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140502-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140502-06:48
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:3.4.2-0ubuntu0.13.1stella1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Tags:  precise running-unity
  Uname: Linux 3.11.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu4
   gnome-bluetooth 3.2.2-0ubuntu5.1stella2
   indicator-datetime  0.3.94-0ubuntu2
  ---
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong-trusty-amd64-20140606-1
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-09 (7 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140606-09:30
  NonfreeKernelModules: nvidia wl
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1318875/+subscriptions

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

[Desktop-packages] [Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

** Changed in: oem-priority
   Importance: High => Low

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

Title:
  Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues

Status in OEM Priority Project:
  Confirmed
Status in Unity Control Center:
  New
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  This issue is related to sound not working properly on Ubuntu when
  switching between an external display using HDMI with 4K resolution
  and the standard laptop display.

  Issue 1 - Sound only works on laptop when plugged into 4k HDMI display
  Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display

  When you plug in a 4k Display that supports sound to the Dell XPS 15
  2016 model the sound only works on the laptop. Only when you go to
  Sound Settings and manually select the HDMI output for sound does the
  sound start to work on the display itself instead of the laptop.

  When you unplug the HDMI 4k display the sound doesn't work on the
  laptop. When you go to the Sound Settings dialog it only shows one
  output that is selected - if you select the same output thats already
  selected the sound starts to work again on the laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1649763/+subscriptions

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

[Desktop-packages] [Bug 1667222] Re: set password in "user accounts panel' won't remove user from "nopasswdlogin" in all cases

** Changed in: oem-priority
   Importance: Medium => Low

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

Title:
  set password in "user accounts panel' won't remove user from
  "nopasswdlogin" in all cases

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Step to reproduce

  1. add the current login user to "nopasswdlogin" group by
   1.1 launch "user accounts panel" in unity-control-center
   1.2 Click "Unlock" at the top right, and enter the user's password.
   1.3. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
   1.4 In the combo box at the top, select "Log in without a password". Save 
the dialog.
   1.5 Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  2. log out, and confirm password is not needed to login.
  3. launch launch "user accounts panel" in unity-control-center again.
  4. change the login user's password

  Expected behavior
  1. new user password is set without any warning message, and user is removed 
from group "nopasswdlogin".

  Current behavior
  1. system prompt "Authentication is required to change user data", and the 
only way out is press cancel.
  2. after press cancel, new user password is set, but the user is still in 
"nopasswdlogin" group. (checked by `grep nopasswdlogin /etc/group`)

  Note: this is still reproducible even use the new  unity-control-
  center in LP: #1630156.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1667222/+subscriptions

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

[Desktop-packages] [Bug 1739018] Re: Gnome shell is sometimes slow to recognize some running apps

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

** Tags added: performance

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

** Changed in: gnome-shell-extension-ubuntu-dock (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/1739018

Title:
  Gnome shell is sometimes slow to recognize some running apps

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

Bug description:
  In Ubuntu 17.10 and 18.04, gnome-shell takes a few seconds to
  recognize that an app is running and show it in launcher and alt-tab.
  It does however show the window immediately in the window spread UI.

  This mostly happens with electron apps especially after a cold boot.

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

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

[Desktop-packages] [Bug 1739019] Re: Gnome Shell does not start in Xorg mode

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1739019

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Summary changed:

- Gnome Shell does not start with X11
+ Gnome Shell does not start in Xorg mode

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

Title:
  Gnome Shell does not start in Xorg mode

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 17.10 and 17.04, Gnome session has stopped working with the
  X11 mode for me. Selecting "Ubuntu on X" in GDM logs me in to a black
  screen with the cursor. If I have an app configured to auto start, the
  app launches without any window decorations. Clicking the app through
  File > Quit menu turns the cursor in a black cross.

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

The upstream bug link is here:
https://bugzilla.gnome.org/show_bug.cgi?id=742463

It's probably worth focusing comments there instead for now.

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

** Also affects: nautilus via
   https://bugzilla.gnome.org/show_bug.cgi?id=742463
   Importance: Unknown
   Status: Unknown

** Package changed: gnome-shell (Ubuntu) => nautilus (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/1729887

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

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

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

[Desktop-packages] [Bug 1392012] Re: [MIR] libteam

2017-12-19 Thread Seth Arnold

I reviewed libteam version 1.26-1 as checked into bionic. This shouldn't
be considered a full security audit but rather a quick gauge of
maintainability.

No CVEs for libteam in our UCT database.

libteam provides a userspace version of various methods of bonding NICs
together that's more flexible than the kernelspace implementations.

- Build-Depends: debhelper, dh-autoreconf, libdaemon-dev, libdbus-1-dev,
  libjansson-dev, libnl-3-dev, libnl-cli-3-dev, libnl-genl-3-dev,
  libnl-route-3-dev, pkg-config
- Daemon manages interfaces, listens on dbus and zmq
- Daemonization code looks complicated, pidfile handling is baffling, but
  nothing that looks insecure.
- No pre/post inst/rm scripts
- No initscripts
- No dbus services
- No setuid files
- bond2team, teamd, teamctl, and teamnl binaries in /usr/bin
- No sudo fragments
- No udev rules
- No test suite
- No cronjobs
- Clean build logs

- No subprocesses spawned
- Memory management looked clean
- Only real 'file' handling is the pidfile, and that's iffy
- Logging looked clean
- two uses of environment variables, TEAM_LOG and TEAMDCTL_LOG, looked
  clean
- privileged operations looked clean
- No cryptography
- Extensive networking operations
- No privileged portions of code
- No temp files
- No WebKit
- No javascript
- No policykit
- Clean cppcheck

Congratulations to the libteam authors, this feels like a large
improvement over the previous review review I performed. I found one
issue with the Debian packaging that I don't understand, one small bug
in teamd_usock_sock_open(), and I still hate the pidfile handling. (If
it works I can understand why no one wants to touch it. I just have
trouble believing it works.)

- lintian warning malformed-deb-archive newer compressed control.tar.xz

- teamd_usock_sock_open() forgot to check the return value from
listen(2)

pidfile handling is baffling -- does it work?
 - teamd_context_init() sets the global variable to point to a pointer to
   the pidfile name (NULL at start)
 - a function pointer named daemon_pid_file_proc is created to alias
   teamd_pid_file_proc()
 - teamd_set_default_pid_file() generates a dynamically allocated name
 - when teamd_pid_file_proc() is called via the function pointer variable,
   it just returns the global variable that is probably NULL at this point
 - None of this looks security relevant but it sure is surprisingly gross.


Security team ACK for promoting libteam to main.

Thanks


** Changed in: libteam (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libteam

Status in libteam package in Ubuntu:
  New

Bug description:
  Availability:
  The package is available in universe, built on all architectures.

  Rationale:
  The package is a new (Build-)Depends for network-manager, for network device 
teaming (aka user-space bonding) support.

  Security:
  Could not find any related security advisories.

  Quality assurance:
  The package is well-maintained in Debian and expected to not require 
extensive effort to maintain in Ubuntu.

  UI standards:
  Not applicable.

  Dependencies:
  All build and binary dependencies are in main.

  Standards compliance:
  The package meets requirements.

  Maintenance:
  The package meets requirements.

  Background information:
  libteam is a library for communicating with the netlink kernel layer in order 
to create bonded interfaces.

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

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

[Desktop-packages] [Bug 314481] Re: selection should not be case limited

** Changed in: nautilus
   Status: New => Confirmed

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

Title:
  selection should not be case limited

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

Bug description:
  Binary package hint: nautilus

  Ubuntu Intrepid Ibex amd64

  Nautilus 2.24.1-0ubuntu1

  When I hit Ctrl+s a window appears and I can write a simple
  expression. All file whose name matches this expression are then
  selected. There is only a problem for me: the filter used should be
  case insensitive. There is no point in me searching for a file whose
  name I can barely remember if I should also rembember the case..

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

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

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

2017-12-19 Thread Pierre Wilch

Public bug reported:

Ubuntu 16.04.3 LTS, every updates done.

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

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

Please do not blame me if xorg is not involved. A way to post had to be found.
'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.

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

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

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

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

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.

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

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

[Desktop-packages] [Bug 1739310] [NEW] Sound crackling in Ubuntu 16.04

2017-12-19 Thread Marlon Pavanello

Public bug reported:

Sometimes, when i’m watching videos in youtube or facebook, the sound is
distorced with a “static sound”. After searching the web for a solution,
i found this site (maybe it’s the same problem, with better explanations
in english): https://github.com/mumble-voip/mumble/issues/2350

Always when i start the service “speech-dispatcher” for the first time
while playing something with sound, the bug occurs. So, i think maybe
the problem is with this “speed-dispatcher” service. When i restart
pulseaudio everything becomes normal again… This problem happens in
ubuntu 17.10 too. It’s a annoying bug and i don’t know the best way to
report it.

My specs:
GPU: Nvidia GTX 950
Motherboard: Gigabyte 78LMT-USB3 (Rev. 6.0)
CPU: AMD FX 8300

P.S: I'm using Xubuntu now but this bug occurs in all ubuntu 16.04
"family". Sorry for the bad english.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: speech-dispatcher 0.8.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Dec 19 20:50:34 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-13 (36 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: speech-dispatcher
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Description changed:

- Sometimes, when i’m wathing videos in youtube or facebook, the sound is
+ Sometimes, when i’m watching videos in youtube or facebook, the sound is
  distorced with a “static sound”. After searching the web for a solution,
  i found this site (maybe it’s the same problem, with better explanations
  in english): https://github.com/mumble-voip/mumble/issues/2350
  
  Always when i start the service “speech-dispatcher” for the first time
  while playing something with sound, the bug occurs. So, i think maybe
  the problem is with this “speed-dispatcher” service. When i restart
  pulseaudio everything becomes normal again… This problem happens in
  ubuntu 17.10 too. It’s a annoying bug and i don’t know the best way to
  report it.
  
  My specs:
  GPU: Nvidia GTX 950
  Motherboard: Gigabyte 78LMT-USB3 (Rev. 6.0)
  CPU: AMD FX 8300
  
  P.S: I'm using Xubuntu now but this bug occurs in all ubuntu 16.04
  "family". Sorry for the bad english.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: speech-dispatcher 0.8.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 19 20:50:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-13 (36 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: speech-dispatcher
  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 speech-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1739310

Title:
  Sound crackling in Ubuntu 16.04

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  Sometimes, when i’m watching videos in youtube or facebook, the sound
  is distorced with a “static sound”. After searching the web for a
  solution, i found this site (maybe it’s the same problem, with better
  explanations in english): https://github.com/mumble-
  voip/mumble/issues/2350

  Always when i start the service “speech-dispatcher” for the first time
  while playing something with sound, the bug occurs. So, i think maybe
  the problem is with this “speed-dispatcher” service. When i restart
  pulseaudio everything becomes normal again… This problem happens in
  ubuntu 17.10 too. It’s a annoying bug and i don’t know the best way to
  report it.

  My specs:
  GPU: Nvidia GTX 950
  Motherboard: Gigabyte 78LMT-USB3 (Rev. 6.0)
  CPU: AMD FX 8300

  P.S: I'm using Xubuntu now but this bug occurs in all ubuntu 16.04
  "family". Sorry for the bad english.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: speech-dispatcher 0.8.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec 19 20:50:34 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-13 (36 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No

[Desktop-packages] [Bug 1739306] [NEW] nouveau preventing shutdown after suspend-resume

2017-12-19 Thread yurad

Public bug reported:

My ASUS X556U laptop has two video cards: 
*-display 
   description: VGA compatible controller
   product: HD Graphics 520
   vendor: Intel Co
and 
*-display
   description: 3D controller
   product: GM108M [GeForce 940MX]
   vendor: NVIDIA Corporation
There is a nouveau bug, when nouveau preventing shutdown after suspend-resume. 
I found another report regarding this bug: 
https://bugs.freedesktop.org/show_bug.cgi?id=99889 , but I want to report to 
Ubuntu. 
I am getting error messages like this one:
"nouveau :01:00.0: Xorg[1039]: failed to idle channel 3[Xorg[1039]"
I cannot shutdown and have to turn off without shutdown that is unsafe. (The 
proprietary NVIDIA driver is even worse. I cannot resume after suspend)

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: sysstat (Ubuntu) => xserver-xorg-video-nouveau
(Ubuntu)

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

Title:
  nouveau preventing shutdown after suspend-resume

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  My ASUS X556U laptop has two video cards: 
  *-display 
 description: VGA compatible controller
 product: HD Graphics 520
 vendor: Intel Co
  and 
  *-display
 description: 3D controller
 product: GM108M [GeForce 940MX]
 vendor: NVIDIA Corporation
  There is a nouveau bug, when nouveau preventing shutdown after 
suspend-resume. I found another report regarding this bug: 
https://bugs.freedesktop.org/show_bug.cgi?id=99889 , but I want to report to 
Ubuntu. 
  I am getting error messages like this one:
  "nouveau :01:00.0: Xorg[1039]: failed to idle channel 3[Xorg[1039]"
  I cannot shutdown and have to turn off without shutdown that is unsafe. (The 
proprietary NVIDIA driver is even worse. I cannot resume after suspend)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1739306/+subscriptions

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

[Desktop-packages] [Bug 1739306] [NEW] nouveau preventing shutdown after suspend-resume

You have been subscribed to a public bug:

My ASUS X556U laptop has two video cards: 
*-display 
   description: VGA compatible controller
   product: HD Graphics 520
   vendor: Intel Co
and 
*-display
   description: 3D controller
   product: GM108M [GeForce 940MX]
   vendor: NVIDIA Corporation
There is a nouveau bug, when nouveau preventing shutdown after suspend-resume. 
I found another report regarding this bug: 
https://bugs.freedesktop.org/show_bug.cgi?id=99889 , but I want to report to 
Ubuntu. 
I am getting error messages like this one:
"nouveau :01:00.0: Xorg[1039]: failed to idle channel 3[Xorg[1039]"
I cannot shutdown and have to turn off without shutdown that is unsafe. (The 
proprietary NVIDIA driver is even worse. I cannot resume after suspend)

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

-- 
nouveau preventing shutdown after suspend-resume
https://bugs.launchpad.net/bugs/1739306
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.

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

[Desktop-packages] [Bug 1681768] Re: Allow adding of categories to dock

** Changed in: gnome-shell
   Status: Confirmed => Won't 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/1681768

Title:
  Allow adding of categories to dock

Status in GNOME Shell:
  Won't Fix
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I find the categories in the Activities Overview's applications list
  rather useful when it comes to certain groups of applications which I
  use, however I have to go all the way into the list to get the
  grouping which should make it much easier to access certain
  applications which are perhaps used together (I mean categories such
  as Sundry or Utilities).

  So I think it would be rather useful if one could 'Favourite' these
  and make it so that they stay in the dock. Then perhaps when clicking
  on them a long thing could come out of the dock with the icon lists of
  the various applications in the list, or some other way of allowing
  the user to select the application they wish from the category.

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

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

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

2017-12-19 Thread Treviño

No, the fix isn't in Ubuntu yet.

It has been commited in the upstream repository, but it won't hit ubuntu
until mutter 3.26.3 will be relased and released in 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/1724557

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

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1739005] Re: (QT5 bug?) In Kubuntu 17.10 the printing options (size, quality...) don't show in printer properties dialog

2017-12-19 Thread Dmitry Shachnev

> the patch for the recovery of the "Advanced" tab would be a good step
forward

This one is also quite complex. The upstream work was a series of
commits
(https://code.qt.io/cgit/qt/qtbase.git/log/src/printsupport/dialogs/qprintdialog_unix.cpp/?h=b4330bc391bbb088),
and most of them do not apply cleanly on 5.9 branch. After resolving
some conflicts (blindly, I did not test), the resulting patch is 6 files
changed, 460 insertions(+), 100 deletions(-).

This is not something I would be happy about in our Qt packaging (but
still better than the OpenSSL 1.1 patch though).

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

Title:
(QT5 bug?) In Kubuntu 17.10 the printing options (size, quality...)
don't show in printer properties dialog

Status in cups package in Ubuntu:
Invalid
Status in qtbase-opensource-src package in Ubuntu:
New

Bug description:
I just moved to Kubuntu 17.10.

When I want to print a pdf doc (okular), a picture (gwenview), a mail
etc. the tab specifying the printer options, as duplex printing,
printing quality, paper size etc. doesn't appear anymore.

My printer is an Epson WF-7620 and the drivers are up to date. I can
still modify the printing options via cups (localhost:631) or the kde
settings panel.

It seems to be a Qt bug as I found this report :
https://bugreports.qt.io/browse/QTBUG-54464
This reports seems to mention that the problem has found a solution and that
this solution will be included in next spring qt version. I'm not able to work
this out by myself but this is a really annoying issue and I don't like much
the idea of waiting 6 more months with it.

Any chance someone could build an official update with a patch?

Thanks in advance for your work an any answer...

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

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

[Desktop-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

2017-12-19 Thread Jack Random

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

the exact same is happening to me, also on a latitude e7470, but with
arch linux, 4.14.6 kernel.

I can also reproduce this behaviour including the not-in-reality-existing 
monitor showing up in xrandr in Ubuntu 17.10 live ISO. Latest Fedora 28 live 
also affected. As this problem doesn't go away with booting LTS kernels, I 
suppose it's not a kernel related bug, nor related to video drivers.
 
I'm also not sure if this is really a duplicate of bug #1505409, as this is new 
behavior and nothing a bug from 2015 could be. Ubuntu 16.04/10 not affected for 
example.

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

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

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  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: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  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/xserver-xorg-video-intel/+bug/1727320/+subscriptions

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

[Desktop-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

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

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

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Confirmed

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

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

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  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: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  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/xserver-xorg-video-intel/+bug/1727320/+subscriptions

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

[Desktop-packages] [Bug 1587854] Re: Nautilus goes into 'Sleeping' state and needs to be manually restarted before used again

** Changed in: nautilus
   Status: Confirmed => Expired

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

Title:
  Nautilus goes into 'Sleeping' state and needs to be manually restarted
  before used again

Status in Nautilus:
  Expired
Status in Ubuntu GNOME:
  New
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I have recently found that after upgrading to GNOME 3.20 on Ubuntu
  GNOME 16.04 that Nautilus randomly will suddenly go into the state
  'Sleeping' and then although all applications will be able to be
  clicked off when clicking on the desktop, no other interactions with
  the desktop will be able to occur, for instance I am unable to select
  or drag anything on the desktop nor can I access the right-click menu
  nor open any icons. If I then go into the Activities Overview and
  attempt to open Nautilus nothing happens, in fact the only way
  seemingly to solve this problem is to manually end the Nautilus
  process and then restart it again in the normal way, after doing this
  all works fine until it decides to have nap again.

  This has happened at least 3 times so far, 2 twice in the same
  session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.20.1-0ubuntu1~xenial2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  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: Wed Jun  1 13:10:17 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'sort-directories-first' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'795x694+0+27'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'date_accessed', 'owner']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-05-15 (16 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (3 days ago)

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

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

[Desktop-packages] [Bug 1641264] Re: libreoffice crashes on startup when using OpenGL rendering and proprietary nvidia driver.

2017-12-19 Thread Stéphane Berbigier

Hello,
I just encountered this bug too as I upgraded to Kubuntu 17.10.
That is : libreoffice crashes if use of opengl is set to true (it doesn't even 
start) and returns :

X Error: BadMatch (invalid parameter attributes) 8
  Extension:154 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x9a00024
soffice.bin: Couldn't find current GLX or EGL context.

My system :
Libreoffice version : 5.4.2.2
Nvidia driver 384.90
Opengl version 4.5.0

Thanks...

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

Title:
  libreoffice crashes on startup when using OpenGL rendering and
  proprietary nvidia driver.

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I noticed that Libreoffice was rendering very slow (I can see each
  menu option drawn) so I tried using OpenGL rendering, which causes
  libreoffice to crash immediately on start-up.

  I confirm that OpenGL is working fine:

  $ glxinfo | head
  name of display: :0.0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4

  I'm able to use glxgears and other apps like djv_view with fast
  rendering.

  I've attached the gdb trace resulting from the crash with debug
  symbols, following is an except:

  Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  #0  0x in ?? ()
  #1  0x768e96f7 in OpenGLContext::AcquireFramebuffer (this=0x128f600, 
rTe
  xture=...) at 
/build/libreoffice-OypX7x/libreoffice-5.1.4/vcl/source/opengl/Open
  GLContext.cxx:1773

  WORKAROUND: Use 5.3.0~rc3-0ubuntu1~xenial1.1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice 1:5.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 11 18:45:52 2016
  InstallationDate: Installed on 2010-11-05 (2198 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to xenial on 2016-11-02 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1641264/+subscriptions

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

[Desktop-packages] [Bug 199167] Re: Owner changed after saving file

2017-12-19 Thread Liam McDermott

Problem is still present in 17.10. It's almost certainly a GVFS issue,
since I'm seeing it with multiple editors (when editing files in a
directory mounted over SSH in Nautilus). Editors tested include: Gedit,
Atom, VSCode.

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

Title:
  Owner changed after saving file

Status in Geany:
  Unknown
Status in gedit:
  Confirmed
Status in geany package in Ubuntu:
  Triaged
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gvfs

  I've edited a text file with gedit via sftp. After saving it, the
  owner user and group is changed to the user that logged on the ssh
  server. This should not happen.

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

2017-12-19 Thread Trev Peterson

I should mention I'm running gnome-flashback (compiz) as this might have
an impact.

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

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

2017-12-19 Thread Trev Peterson

This just started happening to me on 17.10.  The behavior changes with
the circumstances.  I've done several tests and see the following
reproducible behavior:

scenario 1 (moves as expected)
-drag and drop file from Desktop to Desktop/tmp (no nautilus window open) - 
File is moved as expected

scenario 2 (bug: copy instead of move):
-open nautilus to Desktop/tmp
-drag and drop file1 from Desktop to Desktop/tmp(nautilus) - Bug: file is 
copied not moved

scenario 3 (moves as expected when first moved in nautilus, however, only does 
it once):
-open nautilus to Desktop/tmp
-drag and drop file1 from Desktop(nautilus) to Desktop/tmp(nautilus) - file is 
moved as expected
-drag and drop file1 from Desktop/tmp(nautilus) to Desktop(nautilus) - file is 
moved as expected
-drag and drop file1 from Desktop to Desktop/tmp(nautilus) - file is moved as 
expected
-drag and drop file1 from Desktop/tmp(nautilus) to Desktop - file is moved as 
expected
-drag and drop file1 from Desktop to Desktop/tmp(nautilus) - Bug: file is copied

I tested this with several different files and types (text, pdf, ods,
etc) to ensure it was not related to type or specific file, the behavior
was the same for all.  Closing nautilus window or moving another file
before moving file1 causes the file to be copied instead of moved.

Sorry for the long comment but I hoped this might help the devs isolate
the 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/1729887

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

[Desktop-packages] [Bug 1739264] [NEW] Gedit always open new window in gnome shell

2017-12-19 Thread shantanu saha

Public bug reported:

How to regenerate:
1. Open dash and search for gedit
2. Click to open gedit
3. After opening a gedit window, open dash again and search for gedit
4. In gnome shell, icon doesn't show any indicator that another window of gedit 
is already running and click on the icon will create a new window


Possible cause:
Installation of gedit create two .desktop file in /usr/share/applications. 
(gedit.desktop and org.gnome.gedit.desktop)

Workaround:
1. Delete /usr/share/applications/gedit.desktop
2. Edit /usr/share/applications/org.gnome.gedit.desktop and modify 
NoDisplay=true to NoDisplay=false

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1 [modified: 
usr/share/applications/org.gnome.gedit.desktop]
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 20 01:05:33 2017
InstallationDate: Installed on 2017-10-26 (54 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gedit always open new window in gnome shell

Status in gedit package in Ubuntu:
  New

Bug description:
  How to regenerate:
  1. Open dash and search for gedit
  2. Click to open gedit
  3. After opening a gedit window, open dash again and search for gedit
  4. In gnome shell, icon doesn't show any indicator that another window of 
gedit is already running and click on the icon will create a new window

  
  Possible cause:
  Installation of gedit create two .desktop file in /usr/share/applications. 
(gedit.desktop and org.gnome.gedit.desktop)

  Workaround:
  1. Delete /usr/share/applications/gedit.desktop
  2. Edit /usr/share/applications/org.gnome.gedit.desktop and modify 
NoDisplay=true to NoDisplay=false

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1 [modified: 
usr/share/applications/org.gnome.gedit.desktop]
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 20 01:05:33 2017
  InstallationDate: Installed on 2017-10-26 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1739263] [NEW] Gnome terminal always open new window in gnome shell

2017-12-19 Thread shantanu saha

Public bug reported:

How to regenerate:
1. Open dash and search for terminal
2. Click to open terminal
3. After opening a terminal window, open dash again and search for terminal
4. In gnome shell, icon doesn't show any indicator that another window of 
terminal is already running and click on the icon will create a new window


Possible cause:
Installation of gnome-terminal create two .desktop file in 
/usr/share/applications. (gnome-terminal.desktop and org.gnome.Terminal.desktop)

Workaround:
1. Delete /usr/share/applications/gnome-terminal.desktop
2. Edit /usr/share/applications/org.gnome.Terminal.desktop and modify 
NoDisplay=true to NoDisplay=false

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4 [modified: 
usr/share/applications/org.gnome.Terminal.desktop]
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 20 01:04:16 2017
InstallationDate: Installed on 2017-10-26 (54 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gnome terminal always open new window in gnome shell

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  How to regenerate:
  1. Open dash and search for terminal
  2. Click to open terminal
  3. After opening a terminal window, open dash again and search for terminal
  4. In gnome shell, icon doesn't show any indicator that another window of 
terminal is already running and click on the icon will create a new window

  
  Possible cause:
  Installation of gnome-terminal create two .desktop file in 
/usr/share/applications. (gnome-terminal.desktop and org.gnome.Terminal.desktop)

  Workaround:
  1. Delete /usr/share/applications/gnome-terminal.desktop
  2. Edit /usr/share/applications/org.gnome.Terminal.desktop and modify 
NoDisplay=true to NoDisplay=false

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4 [modified: 
usr/share/applications/org.gnome.Terminal.desktop]
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 20 01:04:16 2017
  InstallationDate: Installed on 2017-10-26 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland