[Desktop-packages] [Bug 1723577] [NEW] Artfull won't start with wayland activated

[frenchy82]

Public bug reported:

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

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


lspci -nn | grep VGA

return

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

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 14 07:36:30 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-10-13 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Artfull won't start with wayland activated

Status in gnome-shell package in Ubuntu:
  New

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

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

  
  lspci -nn | grep VGA

  return

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 07:36:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'thunderbird.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'libreoffice-calc.desktop', 'libreoffice-writer.desktop', 
'simple-scan.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1152226] Re: nautilus no longer remembers view per directory

[tellapu]

I have stopped waiting :-( and use Nemo instead.

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

Title:
  nautilus no longer remembers view per directory

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

Bug description:
  Nautilus in raring no longer remembers the view per directory as it
  did in previous releases. This is a functionality regression.

  Steps to reproduce:

  1- Open nautilus from launcher
  2- Go to "Downloads" directory
  3- Switch view to "list"
  4- Close nautilus window
  5- Open nautilus again, and go to "Downloads" directory

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  7 10:50:01 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1004x670+148+241'"
  InstallationDate: Installed on 2012-11-13 (113 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-02-13 (21 days ago)

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

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

[Desktop-packages] [Bug 1722427] Re: [error-report]error occurs when reading /etc/profile

[handsome_feng]

Hi, Gunnar, I have modified the 22_fcitx.rc in ubuntu kylin as you
mentioned, and It worked, Thank you!

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

Title:
  [error-report]error occurs when reading /etc/profile

Status in Ubuntu Kylin:
  Confirmed
Status in fcitx package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  system:artful-1008-64bit

  process:
  1.start the system
  2.put in password
  3.after the log in screen, an error message shows up, check the attached file

  expectation:
  no error message shows up after log in

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

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

[Desktop-packages] [Bug 599662] Re: Ubuntu Firefox Plugin Causes Issues In Firefox 3.7

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu Firefox Plugin Causes Issues In Firefox 3.7

Status in ubufox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ubufox

  Ubuntu Firefox Plugin causes the following issues in Firefox 3.7:

  New windows while in private browsing mode are broken.
  Every other open of Firefox does not open previous tabs.

  See:

  https://bugzilla.mozilla.org/show_bug.cgi?id=575134

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: ubufox 0.9~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-6.7-generic 2.6.35-rc3
  Uname: Linux 2.6.35-6-generic x86_64
  Architecture: amd64
  Date: Tue Jun 29 08:25:18 2010
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubufox

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

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

[Desktop-packages] [Bug 1723571] [NEW] Terminal will never open in usb livecd

[NoBugs!]

Public bug reported:

On newly set up 17.10 I tried updating, I tried installing updates,
restarting, still no terminal at all. I can't install another terminal
because event Ctrl+Alt+Fn key is completely useless in the livecd mode
as I don't know the username/password. This makes the first step in
debugging and getting actual work done completely broken!

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.385
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 14 04:04:08 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=
 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

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

Title:
  Terminal will never open in usb livecd

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On newly set up 17.10 I tried updating, I tried installing updates,
  restarting, still no terminal at all. I can't install another terminal
  because event Ctrl+Alt+Fn key is completely useless in the livecd mode
  as I don't know the username/password. This makes the first step in
  debugging and getting actual work done completely broken!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.385
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 04:04:08 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=
   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/1723571/+subscriptions

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

[Desktop-packages] [Bug 1152226] Re: nautilus no longer remembers view per directory

[JD]

...still waiting...

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

Title:
  nautilus no longer remembers view per directory

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

Bug description:
  Nautilus in raring no longer remembers the view per directory as it
  did in previous releases. This is a functionality regression.

  Steps to reproduce:

  1- Open nautilus from launcher
  2- Go to "Downloads" directory
  3- Switch view to "list"
  4- Close nautilus window
  5- Open nautilus again, and go to "Downloads" directory

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
  Uname: Linux 3.8.0-11-generic x86_64
  ApportVersion: 2.9-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  7 10:50:01 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1004x670+148+241'"
  InstallationDate: Installed on 2012-11-13 (113 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-02-13 (21 days ago)

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  I plugged in my Samsung smartphone to do a USB tether.  The prompt
  came on the screen of my phone asking if I wanted to allow access to
  my device, I answered no and went into the settings to enable the USB
  tether.  Shortly afterwards this error popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 19:53:49 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-10-03 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/0
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f0c2b56c5a9:mov0x18(%rax),%rax
   PC (0x7f0c2b56c5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1723565] Re: With vaapi plugin DVD_VIDEO media renders quite poorly in wayland session

[Doug McMahon]

** Description changed:

  Test Case:
  Install the gstreamer-vaapi plugin.
  Install & reconfigure libdvd
  Playback a commercial dvd in the ubuntu session with totem
  
  What happens:
  Video window flickers between a green screen & video
  Pausing may show video or just green (timing?
- If in the main menu picking the main title produces flickering og,
+ If in the main menu picking the main title produces flickering of,
  green screen, menu, video
  
  Only occurs in a ubuntu session with the gst-vaapi plugin installed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 22:48:39 2017
  InstallationDate: Installed on 2017-10-06 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: totem
  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 totem in Ubuntu.
https://bugs.launchpad.net/bugs/1723565

Title:
  With vaapi plugin DVD_VIDEO  media renders quite poorly in wayland
  session

Status in totem package in Ubuntu:
  New

Bug description:
  Test Case:
  Install the gstreamer-vaapi plugin.
  Install & reconfigure libdvd
  Playback a commercial dvd in the ubuntu session with totem

  What happens:
  Video window flickers between a green screen & video
  Pausing may show video or just green (timing?
  If in the main menu picking the main title produces flickering of,
  green screen, menu, video

  Only occurs in a ubuntu session with the gst-vaapi plugin installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 22:48:39 2017
  InstallationDate: Installed on 2017-10-06 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723565] [NEW] With vaapi plugin DVD_VIDEO media renders quite poorly in wayland session

[Doug McMahon]

Public bug reported:

Test Case:
Install the gstreamer-vaapi plugin.
Install & reconfigure libdvd
Playback a commercial dvd in the ubuntu session with totem

What happens:
Video window flickers between a green screen & video
Pausing may show video or just green (timing?
If in the main menu picking the main title produces flickering of,
green screen, menu, video

Only occurs in a ubuntu session with the gst-vaapi plugin installed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 13 22:48:39 2017
InstallationDate: Installed on 2017-10-06 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  With vaapi plugin DVD_VIDEO  media renders quite poorly in wayland
  session

Status in totem package in Ubuntu:
  New

Bug description:
  Test Case:
  Install the gstreamer-vaapi plugin.
  Install & reconfigure libdvd
  Playback a commercial dvd in the ubuntu session with totem

  What happens:
  Video window flickers between a green screen & video
  Pausing may show video or just green (timing?
  If in the main menu picking the main title produces flickering of,
  green screen, menu, video

  Only occurs in a ubuntu session with the gst-vaapi plugin installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 22:48:39 2017
  InstallationDate: Installed on 2017-10-06 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723130] Re: totem crashed with SIGSEGV in wl_proxy_add_listener()

[Doug McMahon]

Seems to happen with any number of preceding actions, those seeing
should note if gst-vappi is installed. If so does removing the plugin
clear up this issue?

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

Title:
  totem crashed with SIGSEGV in wl_proxy_add_listener()

Status in totem package in Ubuntu:
  New

Bug description:
  I just opened the video from nautilus with double click

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 16:06:22 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-09-17 (24 days ago)
  InstallationMedia: It
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f368b77c77c : testb  
$0x4,0x28(%rdi)
   PC (0x7f368b77c77c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.26.1-0ubuntu3

---
gnome-shell (3.26.1-0ubuntu3) artful; urgency=medium

  * Cherry-pick git_layout-unset-when-headless.patch from gnome-3-26
branch to fix crash bug (LP: #1717170)

 -- Jeremy Bicha   Fri, 13 Oct 2017 16:10:59 -0400

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

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

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

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723564] Re: transmission-gtk crashed with SIGSEGV in tr_torrentInfo()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  transmission-gtk crashed with SIGSEGV in tr_torrentInfo()

Status in transmission package in Ubuntu:
  New

Bug description:
  random crash after deleting old torrent which was not progressing

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: transmission-gtk 2.92-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 07:08:49 2017
  ExecutablePath: /usr/bin/transmission-gtk
  InstallationDate: Installed on 2017-10-09 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008)
  ProcCmdline: transmission-gtk 
/home/username/Downloads/Lethal.Weapon.S02E03.HDTV.x264-LOL[eztv].mkv.torrent
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_IN:en
   LANG=en_IN
  SegvAnalysis:
   Segfault happened at: 0x55c547174897 : cmpl   
$0x1753d,0xb8(%rdi)
   PC (0x55c547174897) ok
   source "$0x1753d" ok
   destination "0xb8(%rdi)" (0x00b7) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: transmission
  StacktraceTop:
   tr_torrentInfo ()
   tr_cpMissingBlocksInPiece ()
   ?? ()
   ?? ()
   ?? ()
  Title: transmission-gtk crashed with SIGSEGV in tr_torrentInfo()
  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/transmission/+bug/1723564/+subscriptions

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

[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

[Bug Watch Updater]

** Changed in: xorg-server
   Status: In Progress => Won't Fix

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

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

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

[Desktop-packages] [Bug 1723563] [NEW] synaptic does not work with wayland in ubuntu 17.10

[honorio]

Public bug reported:

Only in wayland synaptic do not open after entering the password. In X
org works well.

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

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

Title:
  synaptic does not work with wayland in ubuntu 17.10

Status in remmina package in Ubuntu:
  New

Bug description:
  Only in wayland synaptic do not open after entering the password. In X
  org works well.

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

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

[Desktop-packages] [Bug 1716357] Please test proposed package

[Brian Murray]

Hello Esko, or anyone else affected,

Accepted evince into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/evince/3.24.0-0ubuntu1.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Xenial:
  Fix Committed
Status in evince source package in Zesty:
  Fix Committed

Bug description:
  * Impact
  there is an extra ";" in the mimetype list leading to a buggy mailcap entry

  * Test case:
  check if /etc/mailcap contains a line
  "; evince-previewer %s; test=test -n "$DISPLAY""

  * regression potentiel
  check that evince is correcly used when trying to open file associated to it

  -

  
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Brian Murray]

I ended up doing the extra work myself.

** Changed in: evince (Ubuntu Zesty)
   Status: New => Fix Committed

** Tags added: verification-needed-zesty

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Xenial:
  Fix Committed
Status in evince source package in Zesty:
  Fix Committed

Bug description:
  * Impact
  there is an extra ";" in the mimetype list leading to a buggy mailcap entry

  * Test case:
  check if /etc/mailcap contains a line
  "; evince-previewer %s; test=test -n "$DISPLAY""

  * regression potentiel
  check that evince is correcly used when trying to open file associated to it

  -

  
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Brian Murray]

Hello Esko, or anyone else affected,

Accepted evince into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/evince/3.18.2-1ubuntu4.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: evince (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Xenial:
  Fix Committed
Status in evince source package in Zesty:
  Fix Committed

Bug description:
  * Impact
  there is an extra ";" in the mimetype list leading to a buggy mailcap entry

  * Test case:
  check if /etc/mailcap contains a line
  "; evince-previewer %s; test=test -n "$DISPLAY""

  * regression potentiel
  check that evince is correcly used when trying to open file associated to it

  -

  
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

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

[Treviño]

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

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

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

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

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

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

[Desktop-packages] [Bug 1722000] Re: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 00007f22c7bdf877 sp 00007ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+

[Treviño]

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

** This bug has been marked a duplicate of bug 1723048
   gnome-shell crashed with signal 5 in x_io_error from _XIOError from 
_XReadEvents from XIfEvent from meta_display_get_current_time_roundtrip

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

Title:
  gnome shell crashes after scaling is changed from 100% to 200%
  (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in
  libmutter-1.so.0.0.0[7f22c7b36000+141000])

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Attached screenshots for "before applying" and after.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 21:57:36 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago)

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

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

[Desktop-packages] [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

[chris pollock]

That would be great if it happened each and every time I did a software
update however the crash is very, very intermittent.

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

Title:
  gnome-shell crashed with heap corruption in g_strfreev() from
  g_themed_icon_finalize()

Status in gnome-shell package in Ubuntu:
  Incomplete

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

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Happened during update of these packages
  Start-Date: 2017-07-24  16:09:37
  Commandline: apt-get -y install imagemagick imagemagick-6.q16 
imagemagick-common libimage-magick-perl libimage-magick-q16-perl 
libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra 
libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr 
xserver-xorg-core xserver-xorg-legacy
  Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8)
  End-Date: 2017-07-24  16:12:37

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next 
size (fast): 0x05eed540 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 16:11:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1496068513
  InstallationDate: Installed on 2014-10-24 (1004 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/chris
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at 
malloc.c:5006
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3867
   __GI___libc_free (mem=) at malloc.c:2968
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid next size (fast): 0x05eed540 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  gnome-shell:
Installed: 3.26.1-0ubuntu2
Candidate: 3.26.1-0ubuntu2
Version table:
   *** 3.26.1-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  This occurs after I logged in

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 13 21:05:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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/gnome-shell/+bug/1723557/+subscriptions

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

[Desktop-packages] [Bug 1723266] Re: Hide Caribou from Startup Applications

[Bug Watch Updater]

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

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

Title:
  Hide Caribou from Startup Applications

Status in Caribou:
  Fix Released
Status in caribou package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu still includes the Startup Applications app in the default
  install (it was dropped in gnome-session upstream years ago).

  To prevent users from being able to easily disable system services
  that they probably shouldn't, Ubuntu makes sure that apps included by
  default set NoDisplay=true in their autostart files. This hides the
  services from the Startup Applications app.

  Test Case
  =
  Open Startup Applications
  Does Caribou show in the list?

  Other Info
  ==
  SSH Key Agent is intentionally in the Startup Applications list.

  By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
  https://github.com/mate-desktop/mate-session-manager/issues/134

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

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

[Desktop-packages] [Bug 1584740] Re: Libreoffice impress hanging and high cpu on slide operations

[niniendowarrior]

Just want to add insight that removing libreoffice-gtk* does make
Impress usable.  However, I run into issues where sometimes the
graphical rendering of the UI and some of the edits are glitched and
don't refresh correctly. This happens when I have the Impress window go
maximize.

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

Title:
  Libreoffice impress hanging and high cpu on slide operations

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - Create a presentation in libreoffice impress, 30-100 slides with or without 
images
  - Add, copy or delete slides
  - On those operations LO Impress hangs a lot; sometimes 5 mins or more
  - Opening and saving works quick

  Tested on 2 different laptops, both had the same issue. Both did have
  Intel Graphics, but different  ones.  It works fine on the same laptop
  with LO 5.1 on Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-impress 1:5.1.2-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 23 12:55:08 2016
  InstallationDate: Installed on 2016-04-29 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text()

[Treviño]

It's quite hard to debug this without a javascript dump...

Please if anyone gets this frequently, connect to gnome-shell with sudo
gdb -p $(gnome-shell) continue the execution and when the crash happens,
do a "call gjs_dumpstack()"

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  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/1714989/+subscriptions

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

[Desktop-packages] [Bug 1723554] [NEW] Blue border flickers in Overview when you hover mouse away from & over window

[Jesse]

Public bug reported:

BEHAVIOR
When you enter activities overview, and hover your mouse over an open window 
(or away from an open window and then back over an open window) the blue border 
around the window flickers: it briefly fades, then returns. The blue border 
also flickers when you hover over the "X" close button at the top-right of a 
window in Overview, and then back to the window.

EXPECTED BEHAVIOR
That the blue border wouldn't flicker (or quickly fade out then fade back in) 
when you move the mouse into, over, or away from the window in Activities 
Overview.

BUG DISCOVERED USING
Ubuntu 17.10 beta 2
GNOME shell 3.26.1 (gnome-session package, vanilla gnome shell)
Nvidia 384.90 proprietary drivers
X.org 1.19.4
Linux kernel 4.13.0-15-generic

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

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

Title:
  Blue border flickers in Overview when you hover mouse away from & over
  window

Status in gnome-session package in Ubuntu:
  New

Bug description:
  BEHAVIOR
  When you enter activities overview, and hover your mouse over an open window 
(or away from an open window and then back over an open window) the blue border 
around the window flickers: it briefly fades, then returns. The blue border 
also flickers when you hover over the "X" close button at the top-right of a 
window in Overview, and then back to the window.

  EXPECTED BEHAVIOR
  That the blue border wouldn't flicker (or quickly fade out then fade back in) 
when you move the mouse into, over, or away from the window in Activities 
Overview.

  BUG DISCOVERED USING
  Ubuntu 17.10 beta 2
  GNOME shell 3.26.1 (gnome-session package, vanilla gnome shell)
  Nvidia 384.90 proprietary drivers
  X.org 1.19.4
  Linux kernel 4.13.0-15-generic

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

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

[Desktop-packages] [Bug 1723048] Re: gnome-shell crashed with signal 5 in x_io_error from _XIOError from _XReadEvents from XIfEvent from meta_display_get_current_time_roundtrip

[Treviño]

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

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

Title:
  gnome-shell crashed with signal 5 in x_io_error from _XIOError from
  _XReadEvents from XIfEvent from
  meta_display_get_current_time_roundtrip

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Test Case
  1. Attach an external monitor to a laptop and set the output to external 
display only
  2. Suspend the laptop
  3. Detach the external monitor
  4. Resume the laptop

  Actual Result
  The system didn't resume and this crash was present

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 11:18:21 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'google-chrome-beta.desktop', 'streamtuner2.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2014-07-23 (1176 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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
   _XReadEvents () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XIfEvent () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   meta_display_get_current_time_roundtrip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to artful on 2017-06-13 (120 days ago)
  UserGroups: adm dialout libvirt lpadmin lxd sambashare sudo

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

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

[Desktop-packages] [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

[Treviño]

Having a stacktrace with symbols would be quite improtant, since there
are no enough informations here.

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

Title:
  gnome-shell crashed with heap corruption in g_strfreev() from
  g_themed_icon_finalize()

Status in gnome-shell package in Ubuntu:
  Incomplete

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

  apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
Version table:
   *** 3.18.5-0ubuntu0.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Happened during update of these packages
  Start-Date: 2017-07-24  16:09:37
  Commandline: apt-get -y install imagemagick imagemagick-6.q16 
imagemagick-common libimage-magick-perl libimage-magick-q16-perl 
libmagick++-6.q16-5v5 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra 
libmagickwand-6.q16-2 perlmagick xserver-common xserver-xephyr 
xserver-xorg-core xserver-xorg-legacy
  Upgrade: libimage-magick-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-common:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xorg-core:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), libimage-magick-q16-perl:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), xserver-xorg-legacy:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), xserver-xephyr:amd64 (2:1.18.4-0ubuntu0.2, 
2:1.18.4-0ubuntu0.3), imagemagick-6.q16:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), imagemagick-common:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8), perlmagick:amd64 (8:6.8.9.9-7ubuntu5.7, 
8:6.8.9.9-7ubuntu5.8)
  End-Date: 2017-07-24  16:12:37

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid next 
size (fast): 0x05eed540 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 16:11:34 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1496068513
  InstallationDate: Installed on 2014-10-24 (1004 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/chris
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f7cec07de98 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7f7cec07df10 "free(): invalid next size (fast)", action=3) at 
malloc.c:5006
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3867
   __GI___libc_free (mem=) at malloc.c:2968
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid next size (fast): 0x05eed540 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

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

[Treviño]

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

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

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

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7

  ---

  This crash appears after login in, when gnome-shell restarts it seems
  to be stable.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 09:18:43 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-03 (153 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff4e23f8b24 :  
mov0x2c(%rax),%eax
   PC (0x7ff4e23f8b24) ok
   source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_is_on_primary_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_on_all_workspaces_changed () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
  UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

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

[Treviño]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1723378
   
/usr/bin/gnome-shell:5:g_malloc0:blur_pixels:_st_create_shadow_pipeline:_st_create_shadow_pipeline_from_actor:st_icon_update_shadow_pipeline

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Apparently random crash.  I wasn't using the machine at the time, it
  was sitting idle, but unlocked, open to gnome-shell and several apps
  when suddenly gnome-shell crashed (window decoration disappeared).  No
  idea what triggered it.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Oct 13 15:59:28 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-08-03 (1166 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: gnome-shell --replace
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_malloc0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline () at /usr/lib/gnome-shell/libst-1.0.so
   _st_create_shadow_pipeline_from_actor () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with signal 5 in g_malloc0()
  UpgradeStatus: Upgraded to artful on 2017-09-29 (14 days ago)
  UserGroups: adm cdrom dip docker kvm libvirtd lpadmin lxd plugdev sambashare 
sudo video www-data

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

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

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

[markackerm...@gmail.com]

Public bug reported:

affects gnome shell ubuntu 17.10 Beta

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

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

or a restart Does Work

Odd?

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

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

Title:
  workspace to dock disabled after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  affects gnome shell ubuntu 17.10 Beta

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

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

  or a restart Does Work

  Odd?

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

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

[Desktop-packages] [Bug 1723279] Re: xwayland doesn't let root access the display, even via sudo or pkexec

[Paul]

Marking as duplicate (thanks to @brian-murray for identifying the
original).

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

Title:
  xwayland doesn't let root access the display, even via sudo or pkexec

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running a GUI application as root (apport-bug, gparted, etc.),
  the command invariably fails, no matter how it's run:

  $ sudo xclock
  No protocol specified
  Error: Can't open display: :0
  $ pkexec xclock
  Error: Can't open display: 

  Workaround: root can be granted access via xhost as follows, but this
  is insecure on multi-user systems.

  $ xhost +si:localuser:root
  localuser:root being added to access control list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,snap,vpswitch,wall,unitymtgrabhandles,animation,expo,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:14:47 2017
  DistUpgraded: 2017-10-13 08:53:41,683 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:183d]
  InstallationDate: Installed on 2016-12-02 (313 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: ASUSTeK COMPUTER INC. UX303LAB
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-15-generic 
root=UUID=795346fb-c6f2-478b-88c6-363f7317e849 ro rootflags=subvol=@ quiet 
splash acpi_osi= vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)
  dmi.bios.date: 08/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LAB.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LAB.210:bd08/25/2015:svnASUSTeKCOMPUTERINC.:pnUX303LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

[Jeremy Bicha]

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

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

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

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-shell/ubuntu

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

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

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723358] Re: gnome-settings-daemon duplicate input-sources each login

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-settings-daemon -
3.26.1-0ubuntu5

---
gnome-settings-daemon (3.26.1-0ubuntu5) artful; urgency=medium

  * debian/patches/ubuntu_ibus_configs.patch:
 - configure sources only when there is none, that code is meant to be
   used on first login only, the issue was due to a merge error in the
   recent changes, thanks Mitsuya Shibata for pointing the error
   (lp: #1723358)

 -- Sebastien Bacher   Fri, 13 Oct 2017 13:07:31
+0200

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-settings-daemon duplicate input-sources each login

Status in Ubuntu Japanese Kaizen Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
  1. Login to Ubuntu 17.10
  2. Exec on terminal
  $ gsettings get org.gnome.desktop.input-sources sources
  [('xkb', 'us'), ('ibus', 'mozc-jp')]
  3. Logout
  4. (re-)Login to Ubuntu 17.10
  5. Exec on terminal
  $ gsettings get org.gnome.desktop.input-sources sources

  Expected result:
  [('xkb', 'us'), ('ibus', 'mozc-jp')]

  Actual result:
  [('xkb', 'us'), ('ibus', 'mozc-jp'), ('ibus', 'mozc-jp')]

  => Duplicate input sources

  ---
  Original description:
  Subject: Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する

  10月12日付けの artful-desktop-amd64.iso を Virtualbox にインストールし、
  何度もログアウトや再起動を繰り返した所、トップバーのキーボードの「あ」が増える現象に遭遇しました。

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/1723358/+subscriptions

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

[Desktop-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

[Lorenzo]

Hi again,
I've got an interesting piece of news: I've recently discovered that the 
problem only appears when I'm connected to the optical fiber network in the 
flat where I live during the week; when I use ubuntu with the wi-fi at my home 
(much slower, at 7 Mbps) everything is working just fine.
I don't know  if there is a problem with the management of the fiber network in 
Ubuntu or if the issue is caused by a wrong configuration of the router.

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsig

[Jeremy Bicha]

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
  manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
  assertion failed: ((unsigned int) number < g_list_length
  (manager->logical_monitors))

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8

  ---

  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i dont know - it seems that the apport gui took me here.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 13 15:20:45 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-01 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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/gnome-shell/+bug/1723514/+subscriptions

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  pc GL753v   aSUS

  starting...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 13 18:44:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (238 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.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/1723518/+subscriptions

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

[Desktop-packages] [Bug 1681077] Re: ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull function

[Launchpad Bug Tracker]

This bug was fixed in the package libimobiledevice -
1.2.0+dfsg-3.1ubuntu3

---
libimobiledevice (1.2.0+dfsg-3.1ubuntu3) artful; urgency=medium

  * debian/patches/git_ios11_devices.patch:
- backport upstream commit required to work with iOS11 devices
  (lp: #1681077)

 -- Sebastien Bacher   Fri, 13 Oct 2017 12:27:18
+0200

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

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

Title:
  ideviceinfo (libimobiledevice): GnuTLS error: Error in the pull
  function

Status in Libimobiledevice:
  New
Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  Cannot connect to IPhone 5S with ifuse or ideviceinfo due to GnuTLS
  error.

  Reproducable on Ubuntu 16.04.2 LTS and Ubuntu 15.04.

  ideviceinfo 
  GnuTLS error: Error in the pull function.
  ERROR: Could not connect to lockdownd, error code -5

  As far as I know from google, the current IOS 10 release uses TLS instead of 
the insecure SSLv3.
  libimobiledevice (used by ideviceinfo) must be configured to use GnuTLS with 
TLS to successfully connect to IOS 10.
  For IOS 9 there are some (not recommended because insecure) hacks to 
re-enable SSLv3 to get it working.
  But I couldn't find any instructions how to get this working without 
compromising security.

  Other idevice tools like idevicebackup also don't work.

  Successfully using ifuse and idevicebackup for backup purposes is
  quite urgent for me to have a recent backup in case attackers could
  manage to remotely compromise or erase iphones as mentioned in the
  latest news.

  lsb_release -rd
  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  
  Paket: libimobiledevice6
  Zustand: Installiert
  Automatisch installiert: ja
  Multi-Arch: same
  Version: 1.2.0+dfsg-3~ubuntu0.2
  Priorität: optional
  Bereich: libs
  Verwalter: Ubuntu Developers 
  Architektur: amd64
  Unkomprimierte Größe: 181 k
  Hängt ab von: libc6 (>= 2.15), libgcrypt20 (>= 1.6.1), libgnutls30 (>= 3.4.2),
libplist3 (>= 1.11), libtasn1-6 (>= 4.5), libusbmuxd4 (>= 
1.0.10)
  Empfiehlt: usbmuxd
  Schlägt vor: libusbmuxd-tools
  Kollidiert mit: libiphone0
  Beschädigt: libimobiledevice6:i386 (!= 1.2.0+dfsg-3~ubuntu0.2)
  Ersetzt: libimobiledevice0, libimobiledevice1, libiphone0,
   libimobiledevice6:i386 (< 1.2.0+dfsg-3~ubuntu0.2)
  Beschreibung: Bibliothek zur Kommunikation mit dem iPhone und iPod Touch.
   Die Bibliothek libimobiledevice beherrscht die nativen USB-Protokolle von
   Apple, welche von iPhone und iPod Touch verwendet werden. Im Gegensatz zu
   anderen Projekten hängt libimobiledevice nicht von der Verwendung 
irgendwelcher
   vorhandener Apple-Bibliotheken ab.
  Homepage: http://libimobiledevice.org/

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

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

[Desktop-packages] [Bug 1723505] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_free()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-smb-browse crashed with SIGABRT in _talloc_free()

Status in gvfs package in Ubuntu:
  New

Bug description:
  It just popped up on a fresh install of 17.10 beta 2

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 21:10:05 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.15 
/org/gtk/gvfs/exec_spaw/8
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_free () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_free()
  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/gvfs/+bug/1723505/+subscriptions

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

[Desktop-packages] [Bug 1723318] Re: gnome-language-selector crashed with TypeError in getCurrentInputMethod(): 'NoneType' object is not subscriptable

[Gunnar Hjalmarsson]

Thanks! The fact that you couldn't choose language in the installer
seems to be either a bug in the installer or something related to the
other bug report I mentioned. Hopefully it will be fine in a few days.

Anyway, to fix it for yourself now, you can run this terminal command:

im-config -n none

That ought to allow you to open and use Language Support.

Even if this is an oddity, the language-selector package should be able
to handle it without crashing. I'm going to fix it in language-selector
in the beginning of the 18.04 development cycle.

** Changed in: language-selector (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: language-selector (Ubuntu)
Milestone: None => ubuntu-18.04

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

Title:
  gnome-language-selector crashed with TypeError in
  getCurrentInputMethod(): 'NoneType' object is not subscriptable

Status in language-selector package in Ubuntu:
  Triaged

Bug description:
  - fresh Lubuntu 17.10 install with daily iso from 10/12/2017 incl. latest 
updates
  - opening of Start => Preferences => Language Support results in the error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: language-selector-gnome 0.180
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Oct 13 06:11:35 2017
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: /home/steven/Error: command ['which', 'python'] failed with 
exit code 1:, Error: [Errno 2] No such file or directory: "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:": "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:", unpackaged
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getCurrentInputMethod(): 'NoneType' object is not subscriptable
  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/language-selector/+bug/1723318/+subscriptions

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

[Desktop-packages] [Bug 1705458] Re: Mouse clicks pass through to window underneath

[Will Cooke]

Can't reproduce any more.


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

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

Title:
  Mouse clicks pass through to window underneath

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Maybe this is a gedit bug?

  Steps to reproduce

  Log in to an X session - this doesn't seem to affect Wayland session.
  Open GNOME Terminal
  Open Gedit
  Click Open
  Click on the "Other documents" option at the bottom of the menu
  Notice that the click doesn't happen on the "other docs" button, but passes 
through to underneath.

  You can see this demonstrated in the attached video.

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

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

[Desktop-packages] [Bug 1721953] Re: my first bug report...

[Tyler Hicks]

Hi Jan - congrats on creating your first bug report. We appreciate all
feedback and look forward to receiving more from you in the future.

As for this specific bug report, I suspect that it is an issue with the
package in the specific PPA that you're trying to install from. Since
PPAs are maintained by individuals and do not directly correspond to
packages in the Ubuntu archive, you'll need to contact the owner of the
PPA directly. If you let them know what error you're seeing when
attempting to install the problematic package, I'm sure they'll be able
to help you out and/or provide an updated package in the PPA. Good luck!

** Information type changed from Private Security to Public

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

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

Title:
  my first bug report...

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Couldn'T install a PPA-package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct  7 13:47:03 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics 
Controller [1025:040e]
  InstallationDate: Installed on 2017-09-24 (12 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Aspire 1830T
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV10_CS
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire1830T:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1830T
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Oct  7 13:36:37 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1723493] [NEW] gnome-shell on wayland sleeps system when laptop lid closed

[Tessa]

Public bug reported:

Just testing out gnome-shell on Wayland, Ubuntu 17.04. When I close my
laptop lid to just use my external display, the machine sleeps, even
though sleeping on battery power is disabled in power settings. When
running on Xorg, it correctly disables the builtin display and continues
working with just the external monitor.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 13 11:14:40 2017
DisplayManager: lightdm
InstallationDate: Installed on 2016-07-08 (461 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to zesty on 2017-04-14 (182 days ago)

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


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

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

Title:
  gnome-shell on wayland sleeps system when laptop lid closed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Just testing out gnome-shell on Wayland, Ubuntu 17.04. When I close my
  laptop lid to just use my external display, the machine sleeps, even
  though sleeping on battery power is disabled in power settings. When
  running on Xorg, it correctly disables the builtin display and
  continues working with just the external monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 11:14:40 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-07-08 (461 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (182 days ago)

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

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

[Desktop-packages] [Bug 1723318] Re: gnome-language-selector crashed with TypeError in getCurrentInputMethod(): 'NoneType' object is not subscriptable

[sourcepower]

I didn't change the LANG environment variables during or after the
installation. I used the Lubuntu 17.10 Alternate ISO (version from
10/12/2017) to install the Lubuntu system. I also remember that the
"Choose Language" section (comes first in the installer) during the
install process didn't work so i just continued with the next step.

steven@box:~$ cat /etc/default/locale
#  File generated by update-locale
LANG="C"

steven@box:~$ locale -a
C
C.UTF-8
POSIX

steven@box:~$ locale
LANG=C
LANGUAGE=en
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

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

Title:
  gnome-language-selector crashed with TypeError in
  getCurrentInputMethod(): 'NoneType' object is not subscriptable

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  - fresh Lubuntu 17.10 install with daily iso from 10/12/2017 incl. latest 
updates
  - opening of Start => Preferences => Language Support results in the error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: language-selector-gnome 0.180
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Oct 13 06:11:35 2017
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: /home/steven/Error: command ['which', 'python'] failed with 
exit code 1:, Error: [Errno 2] No such file or directory: "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:": "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:", unpackaged
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getCurrentInputMethod(): 'NoneType' object is not subscriptable
  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/language-selector/+bug/1723318/+subscriptions

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

[Desktop-packages] [Bug 1722319] Re: Totem Player not working correctly on 17.10 Beta 2

[corrado venturini]

I don't know how to document this problem, i can just add some experience:
Problem does not happens in wayland.
Problem happens in x11 with many .webm videos created by cheese.
In x11 I click on the video thumbnail and at 1st time usually (not allways) i 
see the video, next time the totem window appears but with a black video. Click 
another thumbnail, sometime ok other time black video.
If I call totem from terminal like 'totem Videos/prova.webm' i have mostly the 
video correctly played.
The attached video is a very small sample giving the problem.

** Attachment added: "video giving the problem"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+attachment/4970228/+files/prova.webm

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1723197] Re: cups-browsed crashed with signal 7 in elf_machine_rel_relative()

[Till Kamppeter]

** Changed in: cups-filters (Ubuntu)
   Status: New => Incomplete

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

Title:
  cups-browsed crashed with signal 7 in elf_machine_rel_relative()

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
   I was booting using kernel 4.13.0-14-generic-i686 to see if bug
  #1723033 occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-browsed 1.17.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4
  Uname: Linux 4.13.0-14-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  Date: Thu Oct 12 18:17:39 2017
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  Lpstat: device for Brother-HL-2250DN-series: 
dnssd://Brother%20HL-2250DN%20series._pdl-datastream._tcp.local/
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  Papersize: a4
  PpdFiles: Brother-HL-2250DN-series: Brother HL-2250DN - CUPS+Gutenprint 
v5.2.13
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-14-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 ro quiet splash vt.handoff=7
  Signal: 7
  SourcePackage: cups-filters
  StacktraceTop:
   elf_machine_rel_relative (reloc_addr_arg=0xb721f28c, reloc=0xb7158464, 
l_addr=3071598592) at ../sysdeps/i386/dl-machine.h:636
   elf_dynamic_do_Rel (skip_ifunc=, lazy=, 
nrelative=, relsize=, reladdr=, 
map=0xb728c650) at do-rel.h:112
   _dl_relocate_object (scope=, reloc_mode=, 
consider_profiling=) at dl-reloc.c:259
   dl_main (phdr=, phnum=, user_entry=, auxv=) at rtld.c:2187
   _dl_sysdep_start (start_argptr=0xbfe792a0, dl_main=0xb7f65cc0 ) at 
../elf/dl-sysdep.c:253
  Title: cups-browsed crashed with signal 7 in elf_machine_rel_relative()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1556601
   gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() 
["Connection to xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Do not have further information

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 13 19:37:21 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-09 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171007)
  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
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

[Adam Kwarciak]

I was close to submit missing log file. 
The command returned that I am not the owner of this bug (translated from 
Polish :)

How I can contribute?
I would be really happy to get the HDMI working properly on my ASRock J4205-ITX.
I know it is not a major issue nor the hardware popular - but Win10 works 
out-of-the-box.

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

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

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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

[Desktop-packages] [Bug 1723197] Re: cups-browsed crashed with signal 7 in elf_machine_rel_relative()

[Till Kamppeter]

There are some odd things visible in your dmesg. Can you please try to
reboot and then run fsck? After that see whether the system runs stably
without crashes.

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

Title:
  cups-browsed crashed with signal 7 in elf_machine_rel_relative()

Status in cups-filters package in Ubuntu:
  New

Bug description:
   I was booting using kernel 4.13.0-14-generic-i686 to see if bug
  #1723033 occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-browsed 1.17.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4
  Uname: Linux 4.13.0-14-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  Date: Thu Oct 12 18:17:39 2017
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  Lpstat: device for Brother-HL-2250DN-series: 
dnssd://Brother%20HL-2250DN%20series._pdl-datastream._tcp.local/
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  Papersize: a4
  PpdFiles: Brother-HL-2250DN-series: Brother HL-2250DN - CUPS+Gutenprint 
v5.2.13
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-14-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 ro quiet splash vt.handoff=7
  Signal: 7
  SourcePackage: cups-filters
  StacktraceTop:
   elf_machine_rel_relative (reloc_addr_arg=0xb721f28c, reloc=0xb7158464, 
l_addr=3071598592) at ../sysdeps/i386/dl-machine.h:636
   elf_dynamic_do_Rel (skip_ifunc=, lazy=, 
nrelative=, relsize=, reladdr=, 
map=0xb728c650) at do-rel.h:112
   _dl_relocate_object (scope=, reloc_mode=, 
consider_profiling=) at dl-reloc.c:259
   dl_main (phdr=, phnum=, user_entry=, auxv=) at rtld.c:2187
   _dl_sysdep_start (start_argptr=0xbfe792a0, dl_main=0xb7f65cc0 ) at 
../elf/dl-sysdep.c:253
  Title: cups-browsed crashed with signal 7 in elf_machine_rel_relative()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Found in /var/crash, not sure exactly when this happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 17:08:35 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2016-05-31 (500 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 /org/gtk/gvfs/exec_spaw/4
  SegvAnalysis:
   Segfault happened at: 0x7f52e13eb5a9:mov0x18(%rax),%rax
   PC (0x7f52e13eb5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-05 (8 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers

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

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

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

[Launchpad Bug Tracker]

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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Oct  7 17:18:27 2017
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-23 (1079 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_monitor_manager_get_logical_monitor_from_number () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_workspace_get_work_area_for_monitor () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare 
sudo

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1556601
   gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XSync() 
["Connection to xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Found this in /var/crash.  Unfortunately GNOME Shell is crashing so
  often I can't tell which particular crash this was.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Oct 12 13:08:19 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['gnome-terminal']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (500 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  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
   _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: Upgraded to artful on 2017-10-05 (8 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Brian Murray]

** Tags added: rls-aa-incoming

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To 

[Desktop-packages] [Bug 1723318] Re: gnome-language-selector crashed with TypeError in getCurrentInputMethod(): 'NoneType' object is not subscriptable

[Gunnar Hjalmarsson]

Thanks for your report. I see that the LANG environment variable is set
to C, which is not normal in a desktop session (it should be some .UTF-8
locale), and I think it explains the crash. Unless you set LANG=C
yourself, that value may be related to
.

Can you please show us the output from these terminal commands:

cat /etc/default/locale

locale -a

locale

** Changed in: language-selector (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-language-selector crashed with TypeError in
  getCurrentInputMethod(): 'NoneType' object is not subscriptable

Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  - fresh Lubuntu 17.10 install with daily iso from 10/12/2017 incl. latest 
updates
  - opening of Start => Preferences => Language Support results in the error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: language-selector-gnome 0.180
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Oct 13 06:11:35 2017
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: /home/steven/Error: command ['which', 'python'] failed with 
exit code 1:, Error: [Errno 2] No such file or directory: "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:": "/home/steven/Error: 
command ['which', 'python'] failed with exit code 1:", unpackaged
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getCurrentInputMethod(): 'NoneType' object is not subscriptable
  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/language-selector/+bug/1723318/+subscriptions

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

[Desktop-packages] [Bug 1723462] Re: GNOME: Universal Access - Larger mouse cursor only works with GDM not with LightDM and with GDM inconsistent

[Jeremy Bicha]

I think most of this bug is about unity-greeter, except the last line
mentions GDM.

Therefore, I'm reassigning to unity-greeter. Feel free to file a bug
against GDM if you like.

** Summary changed:

- GNOME: Universal Access - Larger mouse cursor only works with GDM not with 
LightDM and with GDM inconsistent
+ GNOME: Universal Access - Larger mouse cursor is not supported by 
unity-greeter

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

** Tags added: a11y

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

Title:
  GNOME: Universal Access - Larger mouse cursor is not supported by
  unity-greeter

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  I have a vision problem and due to this I do not see very well the
  mouse pointer in its original size on my 14" HiDPI 2560x1440 QHD
  screen of my laptop. Therefore I go to "Universal Access" in the GNOME
  Settings and choose "Medium" for "Cursor Size".

  Due to bug 1722988 I happened to temporarily use GDM instead of
  LightDM and so I observed that my cursor size change is only applied
  if I am running my system with GDM as the greeter. With LightDM the
  cursor stays in original size all the time. So I have currently
  switched to GDM again to be able to have the larger mouse cursor.

  The commmands I have used (as of comment #9 of bug 1722988):

  --
  sudo systemctl disable lightdm
  sudo systemctl stop lightdm
  sudo systemctl enable gdm #Seems to fail
  sudo systemctl start gdm
  sudo dpkg-reconfigure gdm3 #Shows lightdm selected
  select gdm3, push enter

  Reboot
  --

  But the large mouse cursor with GDM is also not perfect, as in some
  situations it stays in the small size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1723462/+subscriptions

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

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

[Andrew]

I am just now affected by this bug, using a DisplayPort monitor for the
first time.

OS: Ubuntu 17.04 x64
Kernel: 4.10.0-37
X.Org X Server : 1.19.3

Monitor 1: 1920 x 1080 - Laptop's Native Monitor
Monitor 2: 1920 x 1080 - DisplayLink (USB-C) connected MB16AC ASUS Monitor


In an interesting twist: my cursor flickers on both screens, but far more often 
on my laptop screen. On my laptop screen, the cursor flickers about 10 
times/second. On my DisplayLink monitor, the cursor flickers about once every 2 
seconds.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package

[John Cooper]

There's also sources on the same host for the main project git server under the 
following names:-
https://cgit.libimobiledevice.org/idevicerestore.git/
https://cgit.libimobiledevice.org/libirecovery.git/

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

Title:
  Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils
  package

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Currently all of the other important utilities are included for
  installation on Ubuntu. However currently though a Ubuntu Linux user,
  is unable to perform an iOS device restore. In order to do so
  currently the user needs to have some way of running an up to date
  iTunes software with a usb connection to the iPhone, iPad or iPod
  Touch.

  Which is quite a hassle to go through in order to completely reload
  the device's iOS software. It would be much better if a binary
  compiled version of the software (idevicerestore and libirecovery)
  could be included in the utilities package.

  It would allow the Ubuntu user to be able to quickly and easily
  perform software update or device restore functions. Without the need
  for a virtual machine running a compatible version of Windows and
  iTunes etc. While also saving them from having to run Wine, its
  dependencies, iTunes and its own software requirements.

  All the would need is what is required to install idevicerestore and
  run its actions (the appropriate iOS release download image file).

  The code for idevice restore is available here
  (https://cgit.sukimashita.com/idevicerestore.git/) and the library
  from here (https://cgit.sukimashita.com/libirecovery.git/).

  Running Ubuntu 16.04.3
  libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed

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

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

[Desktop-packages] [Bug 1723369] Re: man m-tx has bad 'see also' reference

[Hans Joachim Desserud]

** Tags added: manpage

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

Title:
  man m-tx has bad 'see also' reference

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  man m-tx has a reference 'SEE ALSO: ... mtx260.pdf'.
  That doesn't seem to exist, either on the system or on the web.
  The reference should perhaps be to 'mtx060.pdf' ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: texlive-music 2015.20160320-1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Fri Oct 13 09:53:13 2017
  InstallationDate: Installed on 2017-03-09 (217 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: texlive-extra
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1723369/+subscriptions

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

[Desktop-packages] [Bug 1723178] Re: package libreoffice-common 1:5.3.1-0ubuntu2 failed to install/upgrade: intentando sobreescribir `/usr/lib/libreoffice/program/pagein-draw', que está también en el

[Tyler Hicks]

** Information type changed from Private Security to Public

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

Title:
  package libreoffice-common 1:5.3.1-0ubuntu2 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/libreoffice/program/pagein-draw',
  que está también en el paquete libreoffice-draw
  1:5.4.2~rc2-0ubuntu0.17.04.1~lo1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  no funciona writer

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Tue Oct 10 14:28:00 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/libreoffice/program/pagein-draw', que está también en el paquete 
libreoffice-draw 1:5.4.2~rc2-0ubuntu0.17.04.1~lo1
  InstallationDate: Installed on 2017-09-13 (28 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.3.1-0ubuntu2 failed to install/upgrade: 
intentando sobreescribir `/usr/lib/libreoffice/program/pagein-draw', que está 
también en el paquete libreoffice-draw 1:5.4.2~rc2-0ubuntu0.17.04.1~lo1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723462] Re: GNOME: Universal Access - Larger mouse cursor only works with GDM not with LightDM and with GDM inconsistent

[Till Kamppeter]

** Summary changed:

- GNOME: Universal Access - Larger mouse cursor only works with GDM not with 
LightDM and with GDM inconsistennt
+ GNOME: Universal Access - Larger mouse cursor only works with GDM not with 
LightDM and with GDM inconsistent

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

Title:
  GNOME: Universal Access - Larger mouse cursor only works with GDM not
  with LightDM and with GDM inconsistent

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a vision problem and due to this I do not see very well the
  mouse pointer in its original size on my 14" HiDPI 2560x1440 QHD
  screen of my laptop. Therefore I go to "Universal Access" in the GNOME
  Settings and choose "Medium" for "Cursor Size".

  Due to bug 1722988 I happened to temporarily use GDM instead of
  LightDM and so I observed that my cursor size change is only applied
  if I am running my system with GDM as the greeter. With LightDM the
  cursor stays in original size all the time. So I have currently
  switched to GDM again to be able to have the larger mouse cursor.

  The commmands I have used (as of comment #9 of bug 1722988):

  --
  sudo systemctl disable lightdm
  sudo systemctl stop lightdm
  sudo systemctl enable gdm #Seems to fail
  sudo systemctl start gdm
  sudo dpkg-reconfigure gdm3 #Shows lightdm selected
  select gdm3, push enter

  Reboot
  --

  But the large mouse cursor with GDM is also not perfect, as in some
  situations it stays in the small size.

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

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

[Desktop-packages] [Bug 1722427] Re: [error-report]error occurs when reading /etc/profile

[Gunnar Hjalmarsson]

I have found another way to fix this issue, which I think is better.
Fcitx is launched at login from the /usr/share/im-
config/data/22_fcitx.rc file. Changing line #6 in that file from

/usr/bin/fcitx &

to

/usr/bin/fcitx 2>/dev/null &

makes the 'noise' from launching Fcitx disappear so it won't trigger the
error dialog. This keeps the fix within the im-config package without
involving lightdm.

At least this worked for me on Unity. It would be great if some Kylin
users could test it on Ubuntu Kylin.

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

Title:
  [error-report]error occurs when reading /etc/profile

Status in Ubuntu Kylin:
  Confirmed
Status in fcitx package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  system:artful-1008-64bit

  process:
  1.start the system
  2.put in password
  3.after the log in screen, an error message shows up, check the attached file

  expectation:
  no error message shows up after log in

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

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

[Desktop-packages] [Bug 1722988] Re: Crash, black screen with lightdm

[Jeremy Bicha]

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

I'm marking as duplicate since this bug is no longer reproducible after
today's updates according to the comments here.

Till, Ubuntu 17.10 does use GDM by default. And if you upgrade now from
17.04, you should be transitioned from LightDM to GDM automatically
(unless you have other desktop environments installed I think).

LightDM itself does not use either unity-settings-daemon or gnome-
settings-daemon. unity-greeter though does use unity-settings-daemon.
Unity requires unity-settings-daemon to be installed for the lockscreen.

While I'd love to see unity-settings-daemon be removed, it would cause
regressions with keyboard shortcuts ("hotkeys") and gnome-control-
center's Displays panel wouldn't work. These are fixable with developer
effort (GNOME Flashback managed to fix both of these issues) but there
aren't really developers working on improving Unity now.


** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1722940] Re: 17.10 boots to black screen with cursor

[Jeremy Bicha]

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

** This bug is no longer a duplicate of bug 1722988
   Crash, black screen with lightdm
** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  17.10 boots to black screen with cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After the following update
  Start-Date: 2017-10-11  21:02:12
  Commandline: aptdaemon role='role-commit-packages' sender=':1.136'
  Install: fonts-gubbi:amd64 (1.3-3, automatic), fonts-indic:amd64 (2:1.2, 
automatic), fonts-beng-extra:amd64 (1.0-6, automatic), fonts-deva:amd64 (2:1.2, 
automatic), fonts-samyak-deva:amd64 (1.2.2-4, automatic), 
fonts-telu-extra:amd64 (2.0-4, automatic), fonts-smc:amd64 (6.0-1, automatic), 
fonts-gargi:amd64 (2.0-4, automatic), fonts-deva-extra:amd64 (3.0-4, 
automatic), fonts-kalapi:amd64 (1.0-2, automatic), 
linux-image-extra-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-navilu:amd64 (1.2-2, automatic), linux-tools-4.13.0-15-generic:amd64 
(4.13.0-15.16, automatic), fonts-orya:amd64 (2:1.2, automatic), 
linux-headers-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-pagul:amd64 (1.0-7, automatic), fonts-knda:amd64 (2:1.2, automatic), 
fonts-sahadeva:amd64 (1.0-4, automatic), fonts-lohit-deva:amd64 (2.95.4-2, 
automatic), fonts-taml:amd64 (2:1.3, automatic), fonts-samyak-taml:amd64 
(1.2.2-4, automatic), fonts-telu:amd64 (2:1.2, automatic), 
fonts-lohit-orya:amd64 (2.91.2-
 1, automatic), linux-headers-4.13.0-15:amd64 (4.13.0-15.16, automatic), 
fonts-lohit-knda:amd64 (2.5.4-1, automatic), fonts-gujr:amd64 (2:1.2, 
automatic), fonts-samyak-gujr:amd64 (1.2.2-4, automatic), 
linux-tools-4.13.0-15:amd64 (4.13.0-15.16, automatic), fonts-nakula:amd64 
(1.0-3, automatic), fonts-lohit-beng-bengali:amd64 (2.91.5-1, automatic), 
fonts-orya-extra:amd64 (2.0-5, automatic), fonts-mlym:amd64 (2:1.2, automatic), 
fonts-lohit-taml:amd64 (2.91.3-1, automatic), fonts-beng:amd64 (2:1.2, 
automatic), fonts-samyak-mlym:amd64 (1.2.2-4, automatic), 
fonts-lohit-telu:amd64 (2.5.5-1, automatic), fonts-gujr-extra:amd64 (1.0-6, 
automatic), linux-image-4.13.0-15-generic:amd64 (4.13.0-15.16, automatic), 
fonts-lohit-beng-assamese:amd64 (2.91.5-1, automatic), fonts-lohit-gujr:amd64 
(2.92.4-2, automatic), linux-signed-image-4.13.0-15-generic:amd64 
(4.13.0-15.16, automatic), fonts-sarai:amd64 (1.0-2, automatic), 
fonts-lohit-mlym:amd64 (2.92.2-1, automatic), fonts-lohit-taml-classical:amd64 (
 2.5.4-1, automatic)
  Upgrade: libgraphicsmagick-q16-3:amd64 (1.3.26-12, 1.3.26-13), 
libunity-settings-daemon1:amd64 (15.04.1+17.04.20170619-0ubuntu3, 
15.04.1+17.10.20171003-0ubuntu1), libmpx0:amd64 (5.4.1-13ubuntu1, 
5.5.0-1ubuntu1), empathy-common:amd64 (3.25.90-0ubuntu1, 
3.25.90+really3.12.14-0ubuntu1), libgcj17:amd64 (6.4.0-7ubuntu1, 
6.4.0-8ubuntu1), gnome-control-center-data:amd64 (1:3.26.1-0ubuntu1, 
1:3.26.1-0ubuntu3), libgcc-5-dev:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), 
poppler-utils:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), postfix:amd64 (3.2.2-1, 
3.2.3-1), libseccomp2:amd64 (2.3.1-2.1ubuntu2, 2.3.1-2.1ubuntu3), 
gnome-settings-daemon-schemas:amd64 (3.26.1-0ubuntu1, 3.26.1-0ubuntu3), 
unity-schemas:amd64 (7.5.0+17.10.20170925.1-0ubuntu1, 
7.5.0+17.10.20171010-0ubuntu1), update-manager-core:amd64 (1:17.10.10, 
1:17.10.11), libsemanage1:amd64 (2.7-1, 2.7-2), linux-headers-generic:amd64 
(4.13.0.12.13, 4.13.0.15.16), gnome-session-common:amd64 (3.26.0-0ubuntu2, 
3.26.1-0ubuntu3), unity-session:amd64 (3.2
 6.0-0ubuntu2, 3.26.1-0ubuntu3), gir1.2-mutter-1:amd64 (3.26.1-1, 3.26.1-2), 
gnome-control-center:amd64 (1:3.26.1-0ubuntu1, 1:3.26.1-0ubuntu3), 
linux-libc-dev:amd64 (4.13.0-12.13, 4.13.0-15.16), 
gnome-software-plugin-snap:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), 
va-driver-all:amd64 (1.8.3-1, 1.8.3-2), linux-image-generic:amd64 
(4.13.0.12.13, 4.13.0.15.16), cpp-5:amd64 (5.4.1-13ubuntu1, 5.5.0-1ubuntu1), 
cpp-6:amd64 (6.4.0-7ubuntu1, 6.4.0-8ubuntu1), gsettings-ubuntu-schemas:amd64 
(0.0.7+17.04.20161109-0ubuntu1, 0.0.7+17.10.20170922-0ubuntu1), 
update-manager:amd64 (1:17.10.10, 1:17.10.11), postfix-sqlite:amd64 (3.2.2-1, 
3.2.3-1), libpoppler-qt4-4:amd64 (0.57.0-2ubuntu2, 0.57.0-2ubuntu4), 
linux-signed-image-generic:amd64 (4.13.0.12.13, 4.13.0.15.16), 
gnome-software:amd64 (3.26.0-0ubuntu3, 3.26.1-0ubuntu1), libmutter-1-0:amd64 
(3.26.1-1, 3.26.1-2), ubuntu-standard:amd64 (1.402, 1.403), 
gir1.2-accountsservice-1.0:amd64 (0.6.42-0ubuntu2, 0.6.42-0ubuntu3), 
nodejs:amd64 (6.11.2~dfsg-3ubuntu1
 , 6.11.4~dfsg-1ubuntu1), ubuntu-session:amd64 (3.26.0-0ubuntu2, 
3.26.1-0ubuntu3), gnome-orca:amd64 (3.26.0-1ubuntu1, 3.26.0-1ubuntu2), 
ubuntu-desktop:amd64 (1.402, 1.403), gnome-settings-daemon:amd64 
(3.26.1-0ubuntu1, 

[Desktop-packages] [Bug 1723156] Re: lightdm only shows black screen with cursor on 17.10

[Jeremy Bicha]

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

** This bug is no longer a duplicate of bug 1722988
   Crash, black screen with lightdm
** This bug has been marked a duplicate of bug 1722920
   unity-settings-daemon crashed with signal 5

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

Title:
  lightdm only shows black screen with cursor on 17.10

Status in lightdm package in Ubuntu:
  New

Bug description:
  after recent updates on 17.10 (development) lightdm fails. It only
  shows a black screen and the cursor. Cant change to tty1 with
  ctrl+alt+f1.

  started from grub with systemd.unit=multi-user.target into tty1 and
  started gdm from there, so i could log on to unity (with broken gtk).

  nothing obvious for me in the log files from syslog or lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 12 17:15:29 2017
  InstallationDate: Installed on 2013-09-28 (1475 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to artful on 2017-06-30 (104 days ago)

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

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

[Desktop-packages] [Bug 1723266] Re: Hide Caribou from Startup Applications

[Launchpad Bug Tracker]

This bug was fixed in the package caribou - 0.4.21-2

---
caribou (0.4.21-2) unstable; urgency=medium

  * Add autostart-set-nodisplay.patch:
- Hide Caribou from Ubuntu's Startup Applications (LP: #1723266)
  * Bump Standards-Version to 4.1.1

 -- Jeremy Bicha   Thu, 12 Oct 2017 18:42:47 -0400

** Changed in: caribou (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Hide Caribou from Startup Applications

Status in Caribou:
  Confirmed
Status in caribou package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu still includes the Startup Applications app in the default
  install (it was dropped in gnome-session upstream years ago).

  To prevent users from being able to easily disable system services
  that they probably shouldn't, Ubuntu makes sure that apps included by
  default set NoDisplay=true in their autostart files. This hides the
  services from the Startup Applications app.

  Test Case
  =
  Open Startup Applications
  Does Caribou show in the list?

  Other Info
  ==
  SSH Key Agent is intentionally in the Startup Applications list.

  By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
  https://github.com/mate-desktop/mate-session-manager/issues/134

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

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

[Desktop-packages] [Bug 1723462] [NEW] GNOME: Universal Access - Larger mouse cursor only works with GDM not with LightDM and with GDM inconsistennt

[Till Kamppeter]

Public bug reported:

I have a vision problem and due to this I do not see very well the mouse
pointer in its original size on my 14" HiDPI 2560x1440 QHD screen of my
laptop. Therefore I go to "Universal Access" in the GNOME Settings and
choose "Medium" for "Cursor Size".

Due to bug 1722988 I happened to temporarily use GDM instead of LightDM
and so I observed that my cursor size change is only applied if I am
running my system with GDM as the greeter. With LightDM the cursor stays
in original size all the time. So I have currently switched to GDM again
to be able to have the larger mouse cursor.

The commmands I have used (as of comment #9 of bug 1722988):

--
sudo systemctl disable lightdm
sudo systemctl stop lightdm
sudo systemctl enable gdm #Seems to fail
sudo systemctl start gdm
sudo dpkg-reconfigure gdm3 #Shows lightdm selected
select gdm3, push enter

Reboot
--

But the large mouse cursor with GDM is also not perfect, as in some
situations it stays in the small size.

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

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

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

Title:
  GNOME: Universal Access - Larger mouse cursor only works with GDM not
  with LightDM and with GDM inconsistennt

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a vision problem and due to this I do not see very well the
  mouse pointer in its original size on my 14" HiDPI 2560x1440 QHD
  screen of my laptop. Therefore I go to "Universal Access" in the GNOME
  Settings and choose "Medium" for "Cursor Size".

  Due to bug 1722988 I happened to temporarily use GDM instead of
  LightDM and so I observed that my cursor size change is only applied
  if I am running my system with GDM as the greeter. With LightDM the
  cursor stays in original size all the time. So I have currently
  switched to GDM again to be able to have the larger mouse cursor.

  The commmands I have used (as of comment #9 of bug 1722988):

  --
  sudo systemctl disable lightdm
  sudo systemctl stop lightdm
  sudo systemctl enable gdm #Seems to fail
  sudo systemctl start gdm
  sudo dpkg-reconfigure gdm3 #Shows lightdm selected
  select gdm3, push enter

  Reboot
  --

  But the large mouse cursor with GDM is also not perfect, as in some
  situations it stays in the small size.

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

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

[Desktop-packages] [Bug 1722988] Re: Crash, black screen with lightdm

[dino99]

@Till

i have not closed the report as your #12 comment makes sense; so waiting
for Jeremy (or else dev) opinion.

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1722988] Re: Crash, black screen with lightdm

[Till Kamppeter]

I can also confirm that LightDM is working again.

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

Title:
  Crash, black screen with lightdm

Status in lightdm package in Ubuntu:
  Incomplete
Status in unity-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Got a crash when lightdm is selected, but apport warns about a non
  ubuntu package:

  unity-settings-daemon (15.04.1+17.10.20171003-0ubuntu1) artful;
  urgency=medium

    * XSettings: under unity use com.ubuntu.user-interface.desktop keys
  for scaling settings

   -- Marco Trevisan (Treviño)   Tue, 03 Oct 2017
  06:05:23 +

  so i'm joining the crasfh file

  This happen now with each cold boot: get a black screen, does not even get a 
login screen (using lightdm), so startx is ran from a console to finally get 
the gnome-shell loaded.
  ---
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Tags:  artful
  Uname: Linux 4.13.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:58:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (897 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.20 /org/gtk/gvfs/exec_spaw/3
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f909a6615a9:mov0x18(%rax),%rax
   PC (0x7f909a6615a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo wireshark

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

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

[Desktop-packages] [Bug 1723446] [NEW] gvfsd-mtp crashed with SIGSEGV

[Till Kamppeter]

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Oct 13 10:58:55 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (897 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.20 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f909a6615a9:  mov0x18(%rax),%rax
 PC (0x7f909a6615a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Oct 13 10:58:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (897 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.20 /org/gtk/gvfs/exec_spaw/3
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f909a6615a9:mov0x18(%rax),%rax
   PC (0x7f909a6615a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo wireshark

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

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

[Desktop-packages] [Bug 1392887] Re: serial wacom devices gone after upgrade to utopic/14.10

[Christine Tessier]

** Changed in: xf86-input-wacom (Ubuntu Trusty)
   Status: New => Fix Released

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

Title:
  serial wacom devices gone after upgrade to utopic/14.10

Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom-lts-utopic package in Ubuntu:
  New
Status in xf86-input-wacom source package in Trusty:
  Fix Released
Status in xf86-input-wacom-lts-utopic source package in Trusty:
  New
Status in xf86-input-wacom source package in Utopic:
  Fix Released
Status in xf86-input-wacom source package in Vivid:
  Fix Released
Status in xf86-input-wacom source package in Wily:
  Fix Released

Bug description:
  [Impact]
  udev rules and systemd service file are installed in the wrong path due to 
assuming that dh_install can rename files, instead it installed the files under 
the "renamed" directory

  [Test case]
  try to use a serial wacom device, it fails

  [Regression potential]
  none, restore original behaviour

  --

  Recently I upgraded ubuntu from 14.04 to 14.10 on my HP EliteBook 2760p. 
After that, all serial wacom devices (for the touchscreen) are gone:
     serial wacom stylus
     serial wacom eraser
     serial wacom touch

  xinput -list and xsetwacom --list don't show these devices and the
  Wacom Tablet section of the system setings reports 'no tablet
  detected' rather than showing the usual settings. Booting with the old
  linux 3.13 kernel makes no difference to the new version 3.16.

  To find out what happened I played around on a spare partition with the 
following results:
  1) fresh installation of 14.10 - result is the same like reported above: no 
touch devices
  2) fresh installation of 14.04 - touch works out of the box
  3) upgraded the fresh installation of trusty to utopic: touch devices gone 
again
  4) manually changed repos to utopic after fresh installation of 14.04 and 
updated ONLY the xserver-xorg-input-wacom package: apt pulled some dependencies 
and installed without errors, touch devices gone (so it reproduces the error 
exactly as the full upgrade)

  WORKAROUND: Replace the udev rule 
/lib/udev/rules.d/69-wacom.rules/wacom.rules by the old file from Ubuntu 14.04 
by putting it in /lib/udev/rules.d/ :
  
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1392887/+attachment/4264135/+files/69-xserver-xorg-input-wacom.rules

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-input-wacom 1:0.25.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 22:51:05 2014
  DistUpgraded: 2014-11-01 04:28:11,674 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2012-10-16 (759 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Hewlett-Packard HP EliteBook 2760p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 ro quiet splash vt.handoff=7
  SourcePackage: xf86-input-wacom
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (13 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SOU Ver. F.50
  dmi.board.name: 162A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 05.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2760p
  dmi.product.version: A0005F02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 14 21:19:38 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   22337
   vendor SEC
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  gnome-control-center crashed in the wireless lan tab when I clicked
  the thre dots "..." in the header bar and then clicked "add a new
  hidden wireless lan". After the crash I opened the control center
  again and tried to do the same again and then it worked, no crash
  appeared and I could enter the hidden wireless lan

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 16:00:20 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-08 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1723438] [NEW] Regression: Gnome Shell crashes when plugging or unplugging external monitor

[gpothier]

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

Public bug reported:

A recent update (less than two weeks) in 17.10 introduced a bug where plugging 
or unplugging an external monitor immediately terminates Gnome Shell and brings 
back the login screen.
I think these are the relevant log entries:

Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: **
Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: 
mutter:ERROR:backends/meta-monitor-manager.c:2267:meta_monitor_manager_get_logical_monitor_from_number:
 assertion failed: ((
unsigned int) number < g_list_length (manager->logical_monitors))
Oct 13 11:07:39 tadzim3 owncloud[2934]: Error reading events from display: 
Broken pipe
Oct 13 11:07:39 tadzim3 evolution-alarm[2925]: Error reading events from 
display: Broken pipe
Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE)
Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: Fatal server error:
Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE) failed to read 
Wayland events: Broken pipe
Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE)
Oct 13 11:07:39 tadzim3 gnome-session-binary[2526]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Oct 13 11:07:39 tadzim3 gnome-session[2526]: gnome-session-binary[2526]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Oct 13 11:07:39 tadzim3 gnome-session-binary[2526]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 13 11:08:24 2017
DisplayManager: gdm3
InstallationDate: Installed on 2015-01-23 (993 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-06-15 (120 days ago)

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


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

** This bug has been marked a duplicate of bug 1717170
   gnome-shell crashes with SIGABRT: 
mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number:
 assertion failed: ((unsigned int) number < g_list_length 
(manager->logical_monitors))

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

Title:
  Regression: Gnome Shell crashes when plugging or unplugging external
  monitor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  A recent update (less than two weeks) in 17.10 introduced a bug where 
plugging or unplugging an external monitor immediately terminates Gnome Shell 
and brings back the login screen.
  I think these are the relevant log entries:

  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: **
  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: 
mutter:ERROR:backends/meta-monitor-manager.c:2267:meta_monitor_manager_get_logical_monitor_from_number:
 assertion failed: ((
  unsigned int) number < g_list_length (manager->logical_monitors))
  Oct 13 11:07:39 tadzim3 owncloud[2934]: Error reading events from display: 
Broken pipe
  Oct 13 11:07:39 tadzim3 evolution-alarm[2925]: Error reading events from 
display: Broken pipe
  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE)
  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: Fatal server error:
  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE) failed to read 
Wayland events: Broken pipe
  Oct 13 11:07:39 tadzim3 org.gnome.Shell.desktop[2576]: (EE)
  Oct 13 11:07:39 tadzim3 gnome-session-binary[2526]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Oct 13 11:07:39 tadzim3 gnome-session[2526]: gnome-session-binary[2526]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
  Oct 13 11:07:39 tadzim3 gnome-session-binary[2526]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 11:08:24 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-01-23 (993 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-06-15 (120 days ago)

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

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

[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Fix Released

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

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

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

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

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

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

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

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

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

[Apport retracing service]

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

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

Title:
  cheese crashed with SIGSEGV in wl_proxy_add_listener()

Status in cheese package in Ubuntu:
  New

Bug description:
  Started cheese on fresh 17.10 beta install, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cheese 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 16:24:43 2017
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2017-10-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: EXOPC EXOPG06411
  ProcCmdline: cheese
  RelatedPackageVersions:
   cheese3.26.0-0ubuntu1
   cheese-common 3.26.0-0ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f73668c777c : testb  
$0x4,0x28(%rdi)
   PC (0x7f73668c777c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: linux
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: cheese crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-CE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EXOPG06411
  dmi.board.vendor: EXOPC
  dmi.board.version: R2.0/R1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: EXOPC
  dmi.chassis.version: R2.0/R1.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-CE-133:bd11/22/2010:svnEXOPC:pnEXOPG06411:pvrR2.0/R1.1:rvnEXOPC:rnEXOPG06411:rvrR2.0/R1.1:cvnEXOPC:ct1:cvrR2.0/R1.1:
  dmi.product.family: Series-11.6
  dmi.product.name: EXOPG06411
  dmi.product.version: R2.0/R1.1
  dmi.sys.vendor: EXOPC

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

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

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

[Apport retracing service]

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

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

** Changed in: cheese (Ubuntu)
   Importance: Undecided => Medium

** Tags removed: need-amd64-retrace

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

Title:
  cheese crashed with SIGSEGV in wl_proxy_add_listener()

Status in cheese package in Ubuntu:
  New

Bug description:
  Started cheese on fresh 17.10 beta install, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cheese 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 16:24:43 2017
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2017-10-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: EXOPC EXOPG06411
  ProcCmdline: cheese
  RelatedPackageVersions:
   cheese3.26.0-0ubuntu1
   cheese-common 3.26.0-0ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f73668c777c : testb  
$0x4,0x28(%rdi)
   PC (0x7f73668c777c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: linux
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: cheese crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-CE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EXOPG06411
  dmi.board.vendor: EXOPC
  dmi.board.version: R2.0/R1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: EXOPC
  dmi.chassis.version: R2.0/R1.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-CE-133:bd11/22/2010:svnEXOPC:pnEXOPG06411:pvrR2.0/R1.1:rvnEXOPC:rnEXOPG06411:rvrR2.0/R1.1:cvnEXOPC:ct1:cvrR2.0/R1.1:
  dmi.product.family: Series-11.6
  dmi.product.name: EXOPG06411
  dmi.product.version: R2.0/R1.1
  dmi.sys.vendor: EXOPC

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

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

[Desktop-packages] [Bug 1723426] cheese crashed with SIGSEGV in wl_proxy_add_listener()

[Apport retracing service]

StacktraceTop:
 wl_proxy_add_listener (proxy=0x0, 
implementation=implementation@entry=0x7f73615f9e08 , 
data=data@entry=0x563e6f86a7a0) at ../src/wayland-client.c:469
 wl_buffer_add_listener (data=0x563e6f86a7a0, listener=0x7f73615f9e08 
, wl_buffer=) at 
/usr/include/wayland-client-protocol.h:1709
 dri2_wl_swap_buffers_with_damage (drv=, disp=0x563e6de103e0, 
draw=0x563e6f86a7a0, rects=0x0, n_rects=0) at 
../../../src/egl/drivers/dri2/platform_wayland.c:872
 eglSwapBuffers (dpy=0x563e6de103e0, surface=) at 
../../../src/egl/main/eglapi.c:1243
 _cogl_winsys_onscreen_swap_buffers_with_damage (onscreen=0x563e6f86a220, 
rectangles=0x7ffd3f471af0, n_rectangles=0) at winsys/cogl-winsys-egl.c:848

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

Title:
  cheese crashed with SIGSEGV in wl_proxy_add_listener()

Status in cheese package in Ubuntu:
  New

Bug description:
  Started cheese on fresh 17.10 beta install, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cheese 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 16:24:43 2017
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2017-10-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: EXOPC EXOPG06411
  ProcCmdline: cheese
  RelatedPackageVersions:
   cheese3.26.0-0ubuntu1
   cheese-common 3.26.0-0ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f73668c777c : testb  
$0x4,0x28(%rdi)
   PC (0x7f73668c777c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: linux
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: cheese crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-CE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EXOPG06411
  dmi.board.vendor: EXOPC
  dmi.board.version: R2.0/R1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: EXOPC
  dmi.chassis.version: R2.0/R1.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-CE-133:bd11/22/2010:svnEXOPC:pnEXOPG06411:pvrR2.0/R1.1:rvnEXOPC:rnEXOPG06411:rvrR2.0/R1.1:cvnEXOPC:ct1:cvrR2.0/R1.1:
  dmi.product.family: Series-11.6
  dmi.product.name: EXOPG06411
  dmi.product.version: R2.0/R1.1
  dmi.sys.vendor: EXOPC

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

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

[Desktop-packages] [Bug 1723426] Re: cheese crashed with SIGSEGV in wl_proxy_add_listener()

[Ville Ranki]

I wonder why this was reported to linux, not cheese.

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

** Information type changed from Private to Public

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

Title:
  cheese crashed with SIGSEGV in wl_proxy_add_listener()

Status in cheese package in Ubuntu:
  New

Bug description:
  Started cheese on fresh 17.10 beta install, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cheese 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 16:24:43 2017
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2017-10-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: EXOPC EXOPG06411
  ProcCmdline: cheese
  RelatedPackageVersions:
   cheese3.26.0-0ubuntu1
   cheese-common 3.26.0-0ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f73668c777c : testb  
$0x4,0x28(%rdi)
   PC (0x7f73668c777c) ok
   source "$0x4" ok
   destination "0x28(%rdi)" (0x0028) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: linux
  StacktraceTop:
   wl_proxy_add_listener () from 
/usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: cheese crashed with SIGSEGV in wl_proxy_add_listener()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-CE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EXOPG06411
  dmi.board.vendor: EXOPC
  dmi.board.version: R2.0/R1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: EXOPC
  dmi.chassis.version: R2.0/R1.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-CE-133:bd11/22/2010:svnEXOPC:pnEXOPG06411:pvrR2.0/R1.1:rvnEXOPC:rnEXOPG06411:rvrR2.0/R1.1:cvnEXOPC:ct1:cvrR2.0/R1.1:
  dmi.product.family: Series-11.6
  dmi.product.name: EXOPG06411
  dmi.product.version: R2.0/R1.1
  dmi.sys.vendor: EXOPC

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

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

[Desktop-packages] [Bug 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

[Sebastien Bacher]

Thank you for your bug report, that's a known gtk/wayland issue, see
https://bugzilla.gnome.org/show_bug.cgi?id=766284

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

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

** Changed in: gedit (Ubuntu)
   Status: New => Triaged

** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu)

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

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=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/gtk/+bug/1723403/+subscriptions

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

[Desktop-packages] [Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

[Sebastien Bacher]

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

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

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The Shell Extensions subcategory in GNOME Software is empty. I am
  using the latest (3.26.1-0ubuntu1) GNOME Software package.

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

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1720768
   gnome-shell crashed with SIGTRAP in object_instance_finalize from 
js::Class::doFinalize

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I can access Ubuntu Unity 17.10 but not Gnome, Gnome Shell 3.26. It
  drops back to login.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  Uname: Linux 4.13.5-041305-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 13 06:42:23 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:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1723413] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1720653
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  i am a new user. i don't know anything.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 13 16:06:39 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-10 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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

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

[Desktop-packages] [Bug 1720653] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  2 to 5 times diff bugs popped up

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv wl
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Sun Oct  1 18:54:49 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-22 (132 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1723413] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[kishor kumar]

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

Public bug reported:

i am a new user. i don't know anything.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Oct 13 16:06:39 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-10-10 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  i am a new user. i don't know anything.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 13 16:06:39 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-10 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-10-13 (0 days ago)

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

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

[Desktop-packages] [Bug 1723402] Re: Gnone Terminal does not start on Ubuntu Destkop 20171013

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1723404
   Wrong locale ' UTF-8' in /etc/locale.gen on desktop live image

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

Title:
  Gnone Terminal does not start on Ubuntu Destkop 20171013

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Gnome terminal fails to start with a timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.385
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 11:25:13 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171013)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=
   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/1723402/+subscriptions

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

[Desktop-packages] [Bug 1723409] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in nautilus package in Ubuntu:
  New

Bug description:
  No idea. Happened when I tried to reach my secondary HDD while
  nautilus was trying to load google drive.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 14:29:01 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-05 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f7b56faccdf 
:  mov(%rdx),%rdx
   PC (0x7f7b56faccdf) ok
   source "(%rdx)" (0x5441554156415741) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1642965] Re: Firefox crashes - Error loading theme icon

[Dimitri John Ledkov]

Although this is a valid report, it is out of scope for Ubuntu on z to fix.
Currently upstream releases of firefox v56 is failing to build on ppc64el and 
s390x and thus are not shipped by Ubuntu anymore. Please work with upstream to 
resolve build issues and all the test issues of firefox and mozjs52. Without 
continious integration, build, and testing upstream on ppc64el and s390x it 
will continue to regress further and is unlikely to be ever provided on ubuntu 
and debian. Note debian is discussing dropping mozjs42 on ppc64el & s390x at 
the moment including all the reverse dependencies.

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Firefox crashes - Error loading theme icon

Status in firefox package in Ubuntu:
  Won't Fix

Bug description:
  Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x 
s390x s390x GNU/Linux
  Firefox:
  firefox   47.0+build3-0ubuntu0.16.04.1

  Description:
  Firefox crashes when trying to start it on the server and display on the 
local client.
  Other X application can be displayed.

  Reproduction:
  Login to the server: ssh -X lnxserver
  Start firefox: firefox --no-remote

  Error Message:
  (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for 
stock: Icon 'list-add' not present in theme System
  Segmentation fault (core dumped)

  == Comment: #6 - Thorsten Diehl  - 2016-11-16 
11:50:35 ==
  I can confirm this.

  I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then 
x11-apps, which were working fine (xclock, xeyes).
  I installed firefox and started it:
  firefox --no-remote 
  it created tons of messages, all complaing about an unknown image format.
  Any subsequent start does not create that many messages. But even with 
--safe-mode I can't get it started:
  root@s8330009:~# firefox --no-remote --safe-mode

  (firefox:1487): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=0.627128) [GFX1]: Unknown image format 1
  Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 
(t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown 
image format 0
  [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private 
resource denied); 3 requests ago: file 
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157
  [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private 
resource denied); 3 requests ago: file 
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, 
line 157

  Perhaps a graphics library (gtklib?) has a problem?

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

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

[Desktop-packages] [Bug 1723402] [NEW] Gnone Terminal does not start on Ubuntu Destkop 20171013

[Jean-Baptiste Lallement]

Public bug reported:

Gnome terminal fails to start with a timeout

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.385
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 13 11:25:13 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171013)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=
 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

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

Title:
  Gnone Terminal does not start on Ubuntu Destkop 20171013

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Gnome terminal fails to start with a timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.385
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 11:25:13 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171013)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=
   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/1723402/+subscriptions

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

[Desktop-packages] [Bug 1723403] [NEW] Gedit doesn't Gain Focus Upon Opening a File in Nautilus

[Lonnie Lee Best]

Public bug reported:

If you already have one tab open in gedit, and then minimize gedit, if
you double click on another file in nautilus, gedit should regain focus,
but it does not.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 13 06:26:01 2017
InstallationDate: Installed on 2017-10-13 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=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/1723403

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in gedit package in Ubuntu:
  New

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=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/1723403/+subscriptions

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

[Desktop-packages] [Bug 1723358] Re: gnome-settings-daemon duplicate input-sources each login

[Sebastien Bacher]

Thanks Mitsuya, you are right, that was a merge conflict resolution
error when restoring that feature, I did merge a fix and uploaded now

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

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

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

Title:
  gnome-settings-daemon duplicate input-sources each login

Status in Ubuntu Japanese Kaizen Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed

Bug description:
  How to reproduce:
  1. Login to Ubuntu 17.10
  2. Exec on terminal
  $ gsettings get org.gnome.desktop.input-sources sources
  [('xkb', 'us'), ('ibus', 'mozc-jp')]
  3. Logout
  4. (re-)Login to Ubuntu 17.10
  5. Exec on terminal
  $ gsettings get org.gnome.desktop.input-sources sources

  Expected result:
  [('xkb', 'us'), ('ibus', 'mozc-jp')]

  Actual result:
  [('xkb', 'us'), ('ibus', 'mozc-jp'), ('ibus', 'mozc-jp')]

  => Duplicate input sources

  ---
  Original description:
  Subject: Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する

  10月12日付けの artful-desktop-amd64.iso を Virtualbox にインストールし、
  何度もログアウトや再起動を繰り返した所、トップバーのキーボードの「あ」が増える現象に遭遇しました。

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/1723358/+subscriptions

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

[Desktop-packages] [Bug 1685747] Re: xchat-gnome crashed with SIGSEGV in gdk_wayland_display_get_selection

[Launchpad Bug Tracker]

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

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

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

Title:
  xchat-gnome crashed with SIGSEGV in gdk_wayland_display_get_selection

Status in xchat-gnome package in Ubuntu:
  Confirmed

Bug description:
  Trying to file a bug with apport-cli from the crash file, but it won’t
  open a browser window. So here’s a manual bug report with the crash
  file attached, and retraced stacktrace:

  #0  0x7f600a8c1c00 in gdk_wayland_display_get_selection 
(display=display@entry=0x0) at ././gdk/wayland/gdkdisplay-wayland.c:1318
  #1  0x7f600a8c8b8c in gdk_wayland_selection_add_targets_libgtk_only 
(window=0x0, selection=0x1, ntargets=4, targets=0x282ae80) at 
././gdk/wayland/gdkselection-wayland.c:1495
  #2  0x7f600adf5869 in gtk_selection_add_targets (widget=0x284b6f0 
[GtkXText], selection=0x1, targets=, ntargets=4) at 
././gtk/gtkselection.c:976
  #3  0x7f60098e601b in g_type_create_instance (type=) at 
../../../../gobject/gtype.c:1866
  #4  0x7f60098c7eab in g_object_new_internal (class=class@entry=0x27e1b40, 
params=params@entry=0x0, n_params=n_params@entry=0) at 
../../../../gobject/gobject.c:1783
  #5  0x7f60098c98bd in g_object_newv 
(object_type=object_type@entry=41755792, n_parameters=n_parameters@entry=0, 
parameters=parameters@entry=0x0) at ../../../../gobject/gobject.c:1930
  #6  0x7f60098ca074 in g_object_new (object_type=41755792, 
first_property_name=0x0) at ../../../../gobject/gobject.c:1623
  #7  0x0043e68d in gtk_xtext_new ()
  #8  0x0041e60e in  ()
  #9  0x7f60098e601b in g_type_create_instance (type=) at 
../../../../gobject/gtype.c:1866
  #10 0x7f60098c7eab in g_object_new_internal (class=class@entry=0x27e1400, 
params=params@entry=0x0, n_params=n_params@entry=0) at 
../../../../gobject/gobject.c:1783
  #11 0x7f60098c98bd in g_object_newv (object_type=42123136, 
n_parameters=0, parameters=0x0) at ../../../../gobject/gobject.c:1930
  #12 0x7f600ac5d6ea in _gtk_builder_construct (builder=0x26e10e0 
[GtkBuilder], info=0x27db460, error=0x7ffe7892fb20) at ././gtk/gtkbuilder.c:717
  #13 0x7f600ac5ed45 in builder_construct 
(object_info=object_info@entry=0x27db460, error=error@entry=0x7ffe7892fb20, 
data=) at ././gtk/gtkbuilderparser.c:139
  #14 0x7f600ac607f1 in end_element (context=, 
element_name=, user_data=0x26e1400, error=0x7ffe7892fb20) at 
././gtk/gtkbuilderparser.c:1075
  #15 0x7f60095ec927 in emit_end_element (context=context@entry=0x26e28a0, 
error=error@entry=0x7ffe7892fc30) at ../../../../glib/gmarkup.c:1076
  #16 0x7f60095ed753 in g_markup_parse_context_parse (context=0x26e28a0, 
text=text@entry=0x26e6bf0 "\n\n\n  \n

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

[Bug Watch Updater]

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

** Changed in: totem
   Importance: Unknown => Medium

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

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

Status in GTK+:
  Confirmed
Status in Totem:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  In Progress

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

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

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

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

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

[Desktop-packages] [Bug 1720624] Re: Ubuntu 17.10 blank CD or audio CD not detected

[Launchpad Bug Tracker]

This bug was fixed in the package udisks2 - 2.6.5-2ubuntu2

---
udisks2 (2.6.5-2ubuntu2) artful; urgency=medium

  * debian/patches/git_property_change.patch:
- backport an upstream fix for how UDisksClient filters property
  changes, fixes handling of blank or audio cds (lp: #1720624)

 -- Sebastien Bacher   Fri, 06 Oct 2017 13:47:16
+0200

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

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

Title:
  Ubuntu 17.10 blank CD or audio CD not detected

Status in lshw package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in udisks2 package in Ubuntu:
  Fix Released
Status in lshw source package in Artful:
  Invalid
Status in nautilus source package in Artful:
  Invalid
Status in udisks2 source package in Artful:
  Fix Released

Bug description:
  Audio CD are not detected while data CD and data DVD are detected.
  When I insert a data CD or DVD I have a notification and I see the CD in 
files. With audio CD nothing happens.
  Also empty CD and DVD are not detected.
  No problem on same PC, different partition with Ubuntu 16.04.
  I have the same problem on 3 different PC running Ubuntu 17.10.

  I opened a question about this problem: 
https://answers.launchpad.net/ubuntu/+question/658807
  and I was invited to open a bug.

  In Ubuntu 16.04 
  when I insert a blank CD I see a box with a message 'You have just inserted a 
blank CD. Choose what application ...'
  when I insert an audio CD I see a box with a message 'You have just inserted 
a Audio CD. Choose what application ...'

  In Ubuntu 17.10 
  when I insert a blank CD or an Audio CD nothing happens so I can't access the 
CD.
  when I insert a data CD od DVD I see a notification at the top of the screen 
and I can see the inserted CD in files.

  In attachment:
  screenshot of messages from Ubuntu 16.04
  messages from 'sudo lshw -c disk' in Ubuntu 16.04
  messages from 'sudo lshw -c disk' in Ubuntu 17.10
   
  corrado@corrado-0926:~$ inxi -Fx
  System:Host: corrado-0926 Kernel: 4.13.0-12-generic x86_64 bits: 64 gcc: 
7.2.0
 Desktop: Gnome 3.26.0 (Gtk 3.22.21-0ubuntu1) Distro: Ubuntu Artful 
Aardvark (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.3 ) driver: i915 Resolution: 
1680x1050@59.88hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.2.1 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-12-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 (6.2% used)
 ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
  Partition: ID-1: / size: 32G used: 6.0G (20%) fs: ext4 dev: /dev/sda3
 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: 37.5C mobo: N/A
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 239 Uptime: 3 min Memory: 782.8/7684.1MB Init: systemd 
runlevel: 5 Gcc sys: N/A
 Client: Shell (bash 4.4.121) inxi: 2.3.37 
  corrado@corrado-0926:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lshw 02.18-0.1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 12:50:48 2017
  InstallationDate: Installed on 2017-09-29 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: lshw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716267] Re: Duplicates in Notifications panel in 3.25.x

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.26.1-0ubuntu4

---
gnome-control-center (1:3.26.1-0ubuntu4) artful; urgency=medium

  * debian/patches/ubuntu-legacy-notifications.patch:
- Ubuntu ships compatibility names for .desktop that got renamed
  upstream, those use NoDisplay but the panel doesn't respect that key,
  skip known buggy entries for file-roller and nautilus (lp: #1716267)

  [ Didier Roche ]
  * debian/patches/ubuntu-white-lists.patch:
- use white background for list as expected, clearer that way.

 -- Sebastien Bacher   Fri, 13 Oct 2017 11:39:10
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Duplicates in Notifications panel in 3.25.x

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  I can see duplicates of 'Archive Manager' and 'Files' in the
  Notifications panel in the new g-c-c 3.25.x. See the attached
  screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 19:58:28 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-09 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1723382] Re: ibus keyboard source added each time I log in

[Jun Kobayashi]

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

** This bug has been marked a duplicate of bug 1723358
   gnome-settings-daemon duplicate input-sources each login

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

Title:
  ibus keyboard source added each time I log in

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  ibus keyboard source added each time I log in.
  I'm attaching screenshot.

  The cause seems to be in debian/patches/ubuntu_ibus_configs.patch

  Ubuntu version: 17.10
  Package version: 3.26.1-0ubuntu4

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

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

[Desktop-packages] [Bug 1723365] Re: /usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.26.1-0ubuntu5

---
gnome-session (3.26.1-0ubuntu5) artful; urgency=medium

  * debian/unity-gnome-shell-migration.17.10.py:
- Only reset rhythmbox keys if installed (LP: #1723365)

 -- Didier Roche   Fri, 13 Oct 2017 11:56:41 +0200

** Changed in: gnome-session (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/share/session-migration/scripts/unity-gnome-shell-
  
migration.17.10.py:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Crash for people upgradring to 17.10 if are in the ubuntu session
  and don't have rhythmbox installed.

  [Test Case]

   * Install 17.04
   * Uninstall rhythmbox
   * upgrade to 17.10
   * First login in the ubuntu session will result in the migration script 
crashing

  [Regression Potential]

   * The script is already crashing, even if not functionally annoying
  (this is the last step of the migration script), this causes whoopsie
  to popup for those users. The fix ensure we just skip the rhythmbox
  part if the rhythmbox schema isn't installed.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-session.  This problem was most recently seen with package version 
3.26.1-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/32345bd88e1c6091a5af096d1a5b22c13bdab1b6 
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-session/+bug/1723365/+subscriptions

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

[Desktop-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

[Sebastien Bacher]

Thanks for the report and pointing that patch, I uploaded a backport to
artful now

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

** Changed in: libimobiledevice (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Desktop-packages] [Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

[Didier Roche]

** Description changed:

  When a bug is submitted to ubuntu about gnome-shell it would be
  convenient to have such settings.
  
  Monitors.xml is quite important to understand the configuration for
  mutter-related crashes, while other desktop settings (to be filtered-
  out) could be needed too.
  
  Ah, also the logs from
-   journalctl /usr/bin/gnome-shell -o short-iso
+   journalctl /usr/bin/gnome-shell -b -o short-iso

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

Title:
  Include logs, monitors.xml and org.gnome.desktop.* settings in the
  apport-retrace data

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When a bug is submitted to ubuntu about gnome-shell it would be
  convenient to have such settings.

  Monitors.xml is quite important to understand the configuration for
  mutter-related crashes, while other desktop settings (to be filtered-
  out) could be needed too.

  Ah, also the logs from
    journalctl /usr/bin/gnome-shell -b -o short-iso

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

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

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

[Andrea Azzarone]

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

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

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

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

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  NONE

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 11:01:46 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['realvnc-vncviewer.desktop', 
'org.gnome.Nautilus.desktop', 'SecureCRT.desktop', 
'org.gnome.Terminal.desktop', 'mysql-workbench.desktop', 
'qt_utils_pyo.desktop', 'google-chrome.desktop', 'sublime_text.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
  InstallationDate: Installed on 2016-07-26 (444 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f20c55a20fe 
:   mov
0x18(%rax),%rdx
   PC (0x7f20c55a20fe) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_wayland_surface_show_inhibit_shortcuts_dialog () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_wayland_surface_show_inhibit_shortcuts_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

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

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