[Bug 1725570] 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/1725570/+attachment/4980978/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725570/+attachment/4980987/+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"]

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725570] [NEW] gnome-shell crashed with signal 5 in _XIOError()

[krishnan sampath]

Public bug reported:

Got this after ubuntu dock crashed and failed to load on subsequent
reboots.Running dash to dock instead.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Oct 20 16:50:09 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-10-02 (18 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

livecd-rootfs fixed in version 2.468:

livecd-rootfs (2.468) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Drop obsolete fix-ups of resolv.conf, debootstrap should now result in
correct symlink to resolved without any further fixes.

  [ Michael Hudson-Doyle ]
  * Have subiquity.service order after on a service defined by the subiquity
snap, which in turn will order after the job that mounts the subiquity
snap. (LP: #1721414)


** Changed in: livecd-rootfs (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Cannot resolve DNS in artful daily

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725564] Re: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

[Apport retracing service]

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

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 #1421050, 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/1725564/+attachment/4980914/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

netcfg is also fixed.

netcfg (1.142ubuntu4) artful; urgency=medium

  * Add resolved support. LP: #1714167

 -- Dimitri John Ledkov   Wed, 20 Sep 2017 09:52:03
+0100


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

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

Title:
  Cannot resolve DNS in artful daily

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

network-manager is also fixed:

network-manager (1.8.2-1ubuntu6) artful; urgency=medium

  * src/dns/nm-dns-manager.c:
- Fix resolved detection, the symlink target is usually relative to
the root, such that in chroots the file points to a file inside the
chroot. But keep absolute targets too, as these may have been in use
with older version of systemd.
- Add support for stub-resolv.conf detection.


** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Cannot resolve DNS in artful daily

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

[Cleber Cassol]

Ok, a little workaround did restore the System Settings for me (assuming
one had this problem after changing the dock position just like me):

- sudo apt install dconf-editor
- Navigate to org>gnome>shell-extensions>dash-to-dock>dock-position
- Restore dock position to it's default value

System Settings is working properly now. However, my mouse cursor still
disappears if I move it to the screen edge to the right.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

[Cleber Cassol]

I believe I know what's happening: it looks like Ubuntu created a
virtual screen. If I put my mouse pointer to the right, it vanishes the
same way it does when there's a second monitor/screen attached to the
system. Don't know how it happened, though, since I haven't changed my
screen resolution or displays.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1711897] Re: gnome-control-center crashed with signal 5 in g_settings_get_value()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-control-center crashed with signal 5 in g_settings_get_value()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

[Cleber Cassol]

I'm having the same problem. Started soon after I changed the dock
position from left to bottom. Have already tried to reinstall gnome-
control-center, but to no avail. Rebooting won't help either.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

[Bug Watch Updater]

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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() (dash-to-panel specific?)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725559] [NEW] 17.10 - multi-monitor screen positions are not saved

[David Britton]

Public bug reported:

wayland, gnome-shell, 17.10, up-to-date system.

It seems my monitors.xml is not consulted on gdm launch/session launch,
either wayland or X.  I have two monitors, and I want to place one on
the right and one on the left.  This isn't working, I just get the
default sort, which, of course is wrong.

I've attached standard apport-collect information, I'm willing to debug
more, but it's just plain not working for me right now.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 21:23:53 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['world_clock@ailin.nemui', 
'system-monitor', 'system-moni...@paradoxxx.zero.gmail.com', 
'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 
'clipboard-indica...@tudmotu.com']"
 b'org.gnome.shell' b'favorite-apps' b"['terminator.desktop', 
'google-chrome.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.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 wayland-session

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

Title:
  17.10 - multi-monitor screen positions are not saved

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725558] [NEW] package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Michael Fagan]

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

Public bug reported:

na

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: systemd-sysv 232-21ubuntu5
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: Fri Oct 20 22:00:08 2017
ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: systemd
Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 third-party-packages zesty

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

Title:
  package systemd-sysv 232-21ubuntu5 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725551] 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/1725551/+attachment/4980809/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725551/+attachment/4980818/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725551

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725555] [NEW] control-center display panel cannot move monitors

[David Britton]

Public bug reported:

Running wayland, gnome-shell, 17.10, up-to-date.

I have two monitors plugged into my computer, a couple days ago,
everything was fine.  Now, after a couple of crashes, and package
upgrades, I can no longer re-arrange my monitors on the control center
interface.  When I mouse over a monitor, the cursor changes into a
grabby-hand, but when I click and drag, the monitors just stay where
they are.  No movement at all.

Things I've tried so far --

- removing .config/monitors.xml and rebooting
- disabling & re-enabling monitors

I'm happy to do some debugging on this, but my searches and
troubleshooting so far is coming up empty.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 21:03:06 2017
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  control-center display panel cannot move monitors

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725549] Re: Crash on resume with multiple monitors

[David Britton]

core file

** Attachment added: "core.1.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725549/+attachment/4980795/+files/core.1.xz

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

Title:
  Crash on resume with multiple monitors

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725549] Re: Crash on resume with multiple monitors

[David Britton]

Installed package versions

dpb@aries:~[0]$ dpkg -l |grep gnome-shell
ii  chrome-gnome-shell 9-0ubuntu1   
   all  GNOME Shell extensions integration for web browsers
ii  gnome-shell3.26.1-0ubuntu4  
   amd64graphical shell for the GNOME desktop
ii  gnome-shell-common 3.26.1-0ubuntu4  
   all  common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator 17.10.1  
   all  App indicators for GNOME Shell
ii  gnome-shell-extension-move-clock   1.01-1   
   all  move clock extension for GNOME shell
ii  gnome-shell-extension-system-monitor   32-3 
   all  Display system information in GNOME Shell status bar
ii  gnome-shell-extension-ubuntu-dock  0.7  
   all  Ubuntu Dock for GNOME Shell
dpb@aries:~[0]$ dpkg -l |grep wayland
ii  libwayland-client0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - client library
ii  libwayland-cursor0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - cursor library
ii  libwayland-egl1-mesa:amd64 17.2.2-0ubuntu1  
   amd64implementation of the Wayland EGL platform -- runtime
ii  libwayland-server0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - server library
ii  xwayland   2:1.19.5-0ubuntu2
   amd64Xwayland X server
dpb@aries:~[0]$ dpkg -l |grep mutter
ii  gir1.2-mutter-1:amd64  3.26.1-2ubuntu1  
   amd64GObject introspection data for Mutter
ii  libmutter-1-0:amd643.26.1-2ubuntu1  
   amd64window manager library from the Mutter window manager
ii  mutter 3.26.1-2ubuntu1  
   amd64lightweight GTK+ window manager
ii  mutter-common  3.26.1-2ubuntu1  
   all  shared files for the Mutter window manager
dpb@aries:~[0]$ uname -a
Linux aries 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
dpb@aries:~[0]$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

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

Title:
  Crash on resume with multiple monitors

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Alessandro Stamatto]

I'm having the same problem, following Marius Tip theres one Input
Device that keeps repeating events. Is this normal? It's really
annoying, it interrupts all key holdings (even the arrow ones, ugh). The
device that keeps repeating the events, and the repeated events:

/dev/input/event9:  PEAQ WMI hotkeys

E: 0.01 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 0.01     #  SYN_REPORT (0) -- +0ms
E: 0.17 0001 00d5   # EV_KEY / KEY_SOUND0
E: 0.17     #  SYN_REPORT (0) -- +0ms
E: 0.768001 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 0.768001     #  SYN_REPORT (0) -- +768ms
E: 0.768017 0001 00d5   # EV_KEY / KEY_SOUND0
E: 0.768017     #  SYN_REPORT (0) -- +0ms
E: 1.535971 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 1.535971     #  SYN_REPORT (0) -- +767ms
E: 1.535988 0001 00d5   # EV_KEY / KEY_SOUND0
E: 1.535988     #  SYN_REPORT (0) -- +0ms
E: 2.303989 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 2.303989     #  SYN_REPORT (0) -- +768ms
E: 2.304007 0001 00d5   # EV_KEY / KEY_SOUND0
E: 2.304007     #  SYN_REPORT (0) -- +1ms

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725487] Re: ubuntu.css styling issues - hot corner ripple box

[Nathanel Titane]

See bugs

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725545 (user
avatar)

and

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725546
(login background)

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

Title:
  ubuntu.css styling issues - hot corner ripple box

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725549] [NEW] Crash on resume with multiple monitors

[David Britton]

Public bug reported:

I'm resuming from suspend with multiple monitors attached, and
occasionally I get a crash of gnome-shell.  Will attach the core file

   PID: 1349 (gnome-shell)
   UID: 1000 (dpb)
   GID: 1000 (dpb)
Signal: 8 (FPE)
 Timestamp: Fri 2017-10-20 20:24:01 MDT (8min ago)
  Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-2.scope
  Unit: session-2.scope
 Slice: user-1000.slice
   Session: 2
 Owner UID: 1000 (dpb)
   Boot ID: 10e0e8b9f3bc4937a94e4f4cbae411d2
Machine ID: 58b9ae27536a4e6bb76f4f1b9c561651
  Hostname: aries
   Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1000.10e0e8b9f3bc4937a94e4f4cbae411d2.1349.150855264100.lz4
   Message: Process 1349 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 1349:
#0  0x7f7e5fd30450 n/a (libmutter-1.so.0)
#1  0x7f7e5fcfb683 meta_window_move_resize_internal 
(libmutter-1.so.0)
#2  0x7f7e617d16ad g_slist_foreach (libglib-2.0.so.0)
#3  0x7f7e5fced114 meta_screen_foreach_window 
(libmutter-1.so.0)
#4  0x7f7e5fcefc86 n/a (libmutter-1.so.0)
#5  0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
#6  0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
#7  0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
#8  0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
#9  0x7f7e5fcb2e3d n/a (libmutter-1.so.0)
#10 0x7f7e5fcb5187 meta_monitor_manager_rebuild 
(libmutter-1.so.0)
#11 0x7f7e5fd3a132 n/a (libmutter-1.so.0)
#12 0x7f7e5fcb2e7c n/a (libmutter-1.so.0)
#13 0x7f7e5fcb3e99 meta_monitor_manager_ensure_configured 
(libmutter-1.so.0)
#14 0x7f7e5b710e18 ffi_call_unix64 (libffi.so.6)
#15 0x7f7e5b71087a ffi_call (libffi.so.6)
#16 0x7f7e61a8c799 g_cclosure_marshal_generic 
(libgobject-2.0.so.0)
#17 0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
#18 0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
#19 0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
#20 0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
#21 0x7f7e541429d4 n/a (libgudev-1.0.so.0)
#22 0x7f7e617b2e25 g_main_context_dispatch 
(libglib-2.0.so.0)
#23 0x7f7e617b31f0 n/a (libglib-2.0.so.0)
#24 0x7f7e617b3502 g_main_loop_run (libglib-2.0.so.0)
#25 0x7f7e5fce868c meta_run (libmutter-1.so.0)
#26 0x563b4961e2e7 n/a (gnome-shell)
#27 0x7f7e5f67a1c1 __libc_start_main (libc.so.6)
#28 0x563b4961e3fa n/a (gnome-shell)

Stack trace of thread 1391:
#0  0x7f7e5f761901 __GI___poll (libc.so.6)
#1  0x7f7e39188451 n/a (libpulse.so.0)
#2  0x7f7e39179e10 pa_mainloop_poll (libpulse.so.0)
#3  0x7f7e3917a4a0 pa_mainloop_iterate (libpulse.so.0)
#4  0x7f7e3917a530 pa_mainloop_run (libpulse.so.0)
#5  0x7f7e39188399 n/a (libpulse.so.0)
#6  0x7f7e38f29ed8 n/a (libpulsecommon-10.0.so)
#7  0x7f7e5fa407fc start_thread (libpthread.so.0)
#8  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 1394:
#0  0x7f7e5fa47072 futex_wait_cancelable (libpthread.so.0)
#1  0x7f7e582f4864 n/a (libmozjs-52.so.0)
#2  0x7f7e582f4ab5 n/a (libmozjs-52.so.0)
#3  0x7f7e586ead15 n/a (libmozjs-52.so.0)
#4  0x7f7e5870b352 n/a (libmozjs-52.so.0)
#5  0x7f7e5fa407fc start_thread (libpthread.so.0)
#6  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 1352:
#0  0x7f7e5f761901 __GI___poll (libc.so.6)
#1  0x7f7e617b3169 n/a (libglib-2.0.so.0)
#2  0x7f7e617b3502 g_main_loop_run (libglib-2.0.so.0)
#3  0x7f7e61d9cb26 n/a (libgio-2.0.so.0)
#4  0x7f7e617da645 n/a (libglib-2.0.so.0)
#5  0x7f7e5fa407fc start_thread (libpthread.so.0)
#6  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 28678:
#0  0x7f7e5f7679f9 syscall (libc.so.6)
#1  0x7f7e617f880a g_cond_wait_until (libglib-2.0.so.0)
#2  0x7f7e617872e1 n/a (libglib-2.0.so.0)
   

[Bug 1725546] [NEW] ubuntu.css styling issues - gdm login background inconsistency

[Nathanel Titane]

Public bug reported:

An important factor in staying consistent with the overall aesthetics of
the ubuntu design language would be to disable the use of the noise
texture on gdm to provide a seamless transition from the plymouth boot
splash onto the gdm login. Here is the override provided to fix the
inconsistency in ubuntu.css under the gnome-shell themes directory:

#lockDialogGroup {
  background: #2c001e !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 22:23:07 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  ubuntu.css styling issues - gdm login background inconsistency

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725545] [NEW] ubuntu.css styling issues - gdm user avatar alignment

[Nathanel Titane]

Public bug reported:


The gdm login avatar vertical alignment alignment is off by a couple of
pixels and can be easily fixed by correcting the user icon margin setup
like so using an override in ubuntu.css in the gnome-shell themes
directory:

.framed-user-icon {
  margin: 4px 0px 0px 2px !important;
  padding: 0px 0px 0px 0px !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 22:19:00 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  ubuntu.css styling issues - gdm user avatar alignment

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725487] Re: ubuntu.css styling issues - hot corner ripple box

[Nathanel Titane]

** Summary changed:

- ubuntu.css styling issues
+ ubuntu.css styling issues - hot corner ripple box

** Description changed:

  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the specified
  asset resource:///org/gnome/shell/theme/corner-ripple-ltr.png - this is
  also valid for the rtl asset.
  
  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:
  
  .ripple-box {
-   border-radius: 0px 0px 64px 0px !important;
-   background: #e95420 !important;
-   width:64px !important;
-   height:64px !important;
+   border-radius: 0px 0px 64px 0px !important;
+   background: #e95420 !important;
+   width:64px !important;
+   height:64px !important;
  }
  
  .ripple-box:rtl {
-   border-radius: 0px 0px 0px 64px !important;
-   background: #e95420 !important;
-   width:64px !important;
-   height:64px !important;
- }
- 
- The gdm login avatar alignment is also off by a couple of pixels and can
- be easily fixed by correcting the user icon margin setup like so:
- 
- .framed-user-icon {
-   margin: 4px 0px 0px 2px !important;
-   padding: 0px 0px 0px 0px !important;
- }
- 
- Another important factor in staying consistent with the overall
- aesthetics of the ubuntu design language would be to disable the use of
- the noise texture on gdm to provide a seamless transition from the
- plymouth boot splash onto the gdm login. Here is the override:
- 
- #lockDialogGroup {
-   background: #2c001e !important;
+   border-radius: 0px 0px 0px 64px !important;
+   background: #e95420 !important;
+   width:64px !important;
+   height:64px !important;
  }
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu.css styling issues - hot corner ripple box

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725540] 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/1725540/+attachment/4980735/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725540/+attachment/4980745/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725540

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725534] Re: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

[Apport retracing service]

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

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 #1716208, 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/1725534/+attachment/4980682/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1716208
   epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725533] 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/1725533/+attachment/4980669/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725533/+attachment/4980678/+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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1725533

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess\n"]

[Treviño]

Extensions installed?

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

Title:
  gnome-shell crashed with SIGTRAP in object_instance_finalize from
  js::Class::doFinalize ["Finalizing proxy for an object that's
  scheduled to be unrooted: Gio.Subprocess\n"]

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725524] 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/1725524/+attachment/4980568/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725524/+attachment/4980577/+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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1725524

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725520] 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/1725520/+attachment/4980554/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725520/+attachment/4980563/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725520

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  connecting to a WPA-enterprise network from gnome-shell opens up the
  "Networks" panel instead of the Wi-Fi panel

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

[Launchpad Bug Tracker]

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

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

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

[Launchpad Bug Tracker]

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

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

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

[QkiZ]

I dont have Wayland session choice, even on Intel gfx card.

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Egmont Koblinger]

Ubuntu's gnome-terminal has patch, originating from Red Hat, with the
title "Extra padding around transparent terminals in Wayland". Just by
its name it's truly suspicious, but I don't have time now to verify if
that's causing this terrible look. Anyway, as said, it's probably
irrelevant.

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Bug Watch Updater]

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

** Changed in: mutter
   Importance: Unknown => Medium

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Egmont Koblinger]

Geez... indeed. I can confirm that look with vte and gnome-terminal
Ubuntu packages. It looks awful.

I'm using vte and gnome-terminal from git (the rest is stock 17.10).
They don't have this visual problem, but the shrinkage is there. So
probably it's irrelevant.

Also, Ubuntu's vte & gnome-terminal packages look okay under Unity 7.

Not sure by the way if it's something that's been fixed in vte/g-t since
(I can't recall anything like that) or it's caused by an Ubuntu patch
(that would be my primary guess).

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725507] [NEW] keyboard shortcut to lock screen doesn't work on 17.10

[Tessa]

Public bug reported:

After upgrading to Ubuntu 17.10, the keyboard shortcut to lock the
screen (by default, Win-L) doesn't lock the screen anymore. If I go into
the keyboard shortcuts settings panel and change it, whatever I change
it to does nothing, either. However, the icon in the gnome login menu in
the top right does still work, so screen lock isn't entirely broken.

Not sure what component actually controls this, so I'm filing under
gnome-shell, since it seems like the thing that'd interpret keyboard
hotkeys.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 20 15:59:58 2017
DisplayManager: lightdm
InstallationDate: Installed on 2016-07-08 (468 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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


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

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

Title:
  keyboard shortcut to lock screen doesn't work on 17.10

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725371] Re: 17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower window

[Scott Stensland]

** Description changed:

  It's very handy to send any open Ubuntu application window to below all
- other open windows (it says open yet now occluded) by clicking mouse
+ other open windows (it stays open yet now occluded) by clicking mouse
  middle button on window title bar (opposite of left mouse click to bring
  to focus front) ... this works fine on all Ubuntu 17.10 applications
  except fails on Ubuntu 17.10's file explorer nautilus 3.26.0 which has a
  non-standard looking title bar.
  
  This behavior continues to be OK on all other 17.10 applications...
  Nautilus worked on previous Ubuntu releases  ... I hope other apps
  refrain from using this new window behavior
  
  Any ideas on why nautilus breaks this convention? Or how to fix it?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct 20 10:53:51 2017
  InstallationDate: Installed on 2017-05-17 (155 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-07-30 (81 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

Title:
   17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower
  window

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Paul]

Literally one pixel beyond the edges of the window. I've attached a
screenshot that I hope illustrates this.

You see two windows which were auto-placed by the window manager. If
they didn't have scroll bars, they wouldn't overlap, but they do, by one
pixel. Depending on which window is in the foreground, the rightmost
pixel of the scroll bar is either below or above the other window.

The bottommost pixel of the scroll bar extending below the window is
evident in both cases.

** Attachment added: "scrollbar_beyond_window_boundary.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/4980480/+files/scrollbar_beyond_window_boundary.png

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725487] Re: ubuntu.css styling issues

[Nathanel Titane]

Thanks for your response Jeremy.

I filed all three issues in a same report since all three refer to the
same styling file (ubuntu.css) under the gnome-shell themes folder.

If it's a must I'll separate the report later on.

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

Title:
  ubuntu.css styling issues

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Egmont Koblinger]

Paul, what do you mean by "scroll bars extending one pixel past the
right and bottom edges"??

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725495] Re: gedit crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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 #1570938, 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/1725495/+attachment/4980382/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gedit crashed with SIGSEGV in g_closure_invoke()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725487] Re: ubuntu.css styling issues

[Jeremy Bicha]

I think the GDM login screen texture was intentional for Ubuntu 17.10.

Please file separate bugs for separate issues. I count 3 separate issues
here (the ripple, the login avatar alignment, the login texture).

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

Title:
  ubuntu.css styling issues

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Paul]

@egmont-gmail Do the other affected terminals also have scroll bars
extending one pixel past the right and bottom edges, the way gnome-
terminal has?

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725491] [NEW] Application icons disappear after waking PC up from sleep

[Vasya Pupkin]

Public bug reported:

Application icons (Telegram, Dropbox, etc) disappear after waking PC up
from sleep. Applications are still running, but icons are gone.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 00:49:13 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Application icons disappear after waking PC up from sleep

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725487] [NEW] ubuntu.css styling issues

[Nathanel Titane]

Public bug reported:

Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
hot-corner' as true, the colour of the ripple is still blue (Adwaita
default scheme) since the compiled shell theme still uses the specified
asset resource:///org/gnome/shell/theme/corner-ripple-ltr.png - this is
also valid for the rtl asset.

I have solved the issue by appending an override to match the current
ubuntu.css overrides as follows:

.ripple-box {
  border-radius: 0px 0px 64px 0px !important;
  background: #e95420 !important;
  width:64px !important;
  height:64px !important;
}

.ripple-box:rtl {
  border-radius: 0px 0px 0px 64px !important;
  background: #e95420 !important;
  width:64px !important;
  height:64px !important;
}

The gdm login avatar alignment is also off by a couple of pixels and can
be easily fixed by correcting the user icon margin setup like so:

.framed-user-icon {
  margin: 4px 0px 0px 2px !important;
  padding: 0px 0px 0px 0px !important;
}

Another important factor in staying consistent with the overall
aesthetics of the ubuntu design language would be to disable the use of
the noise texture on gdm to provide a seamless transition from the
plymouth boot splash onto the gdm login. Here is the override:

#lockDialogGroup {
  background: #2c001e !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:25:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  ubuntu.css styling issues

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

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

So, as thinking on this, I must say, maybe this is my mis-interpretation
of the problem. Maybe not the colour prompt causes this, but if I use a
newer (or ssh into a newer) ubuntu box versus ssh into an older version
(in both cases ssh in the window only changes the situation of
"shrinking" if the window title is modified to reflect this, ie like
username@machine1:~ changes into username@machine2:~ because of the
ssh). I really feel bad not to be able to express this in a sane way,
but it's kind of odd issue for me at least. Just changing PS1 does not
change the situation for me either.

Ok, now it's even more odd, just trying to test it ... Now window
shrinks by TWO lines not only one, and the behaviour I tried to describe
above seems not to apply at all :-O I don't know what I can say, maybe
this is a more complex issue and my assumption was only true for the
given case when I last tested it ...Sorry about that.

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

[Paul]

I use dash to dock rather than dash-to-panel but am now running the
command and will try and get an output for you.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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() (dash-to-panel specific?)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)

[drunckoder]

That's an essential feature that should never be abandoned. I'm facing
similar issues like Dmitriy did. Are there ways to patch or downgrade
Nautilus? It's working perfectly in 17.04

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

Title:
  Drop interactive_search.patch (type-ahead search)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1164016] Re: restore type-ahead find

[drunckoder]

I can confirm there's an issue again on Ubuntu 17.10

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

Title:
  restore type-ahead find

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

[LGB [Gábor Lénárt]]

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

I don't know how to tell, but it seems the bug happens when the prompt
has effect on the title of the window. What I mean here: opening a
gnome-terminal with a colourful PS1 causes this. However if I ssh into
another machine which does update the title of the window and the prompt
does not use colour, the shrinking stops if I try fullscreen/back cycles
again ... If I ssh into a machine which does have this "new" colour
prompt then it continues ... If I ssh into a machine which does not
effect the title bar, it does not effect the strange behaviour though.
So, what I can think about there is some connection about the window bar
title updating by the prompt (???) sorry, I have really no idea hot it
happens :-O

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712921] Re: enabling networkd appears to eat up entropy

[Mathieu Trudel-Lapierre]

There's a bit of netplan in that too.

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

** Changed in: nplan (Ubuntu Artful)
   Status: New => In Progress

** Changed in: nplan (Ubuntu Artful)
   Importance: Undecided => Critical

** Changed in: nplan (Ubuntu Artful)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  enabling networkd appears to eat up entropy

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697146] Re: Unable to use apport to report any bugs prior to the first software update

[Brian Murray]

I just installed the final release of Artful, without choosing to
install updates from the network, and /var/lib/apt/lists is full and I
am able to use 'ubuntu-bug apport' without having to run a software
update.

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

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

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

Title:
  Unable to use apport to report any bugs prior to the first software
  update

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725479] [NEW] systemd-udevd crashes writing ISO with usb-creator-gtk

[Dario Menin]

Public bug reported:

At the end of the writing process, systemd-udevd crashes, i see this in
dmesg:

[ 1934.273458] INFO: task systemd-udevd:298 blocked for more than 120 seconds.
[ 1934.273462]   Tainted: G   OE   4.10.0-37-generic 
#41~16.04.1-Ubuntu
[ 1934.273464] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1934.273466] systemd-udevd   D0   298  1 0x0004
[ 1934.273468] Call Trace:
[ 1934.273474]  __schedule+0x232/0x700
[ 1934.273475]  schedule+0x36/0x80
[ 1934.273477]  schedule_preempt_disabled+0xe/0x10
[ 1934.273478]  __mutex_lock_slowpath+0x193/0x290
[ 1934.273480]  mutex_lock+0x2f/0x40
[ 1934.273482]  __blkdev_get+0x6f/0x400
[ 1934.273483]  blkdev_get+0x129/0x330
[ 1934.273485]  blkdev_open+0x82/0xd0
[ 1934.273487]  do_dentry_open+0x208/0x310
[ 1934.273488]  ? blkdev_get_by_dev+0x50/0x50
[ 1934.273489]  vfs_open+0x4c/0x70
[ 1934.273491]  ? may_open+0x9b/0x100
[ 1934.273492]  path_openat+0x2ac/0x1430
[ 1934.273494]  do_filp_open+0x91/0x100
[ 1934.273496]  ? __alloc_fd+0x46/0x170
[ 1934.273498]  do_sys_open+0x12d/0x280
[ 1934.273500]  SyS_open+0x1e/0x20
[ 1934.273502]  entry_SYSCALL_64_fastpath+0x1e/0xad
[ 1934.273503] RIP: 0033:0x7f915b83bc60
[ 1934.273504] RSP: 002b:7ffccbefa178 EFLAGS: 0246 ORIG_RAX: 
0002
[ 1934.273505] RAX: ffda RBX: 55baf1f7e760 RCX: 7f915b83bc60
[ 1934.273506] RDX: 55baf1422592 RSI: 000a0800 RDI: 55baf1f6dcc0
[ 1934.273507] RBP:  R08: 0073 R09: 0003
[ 1934.273507] R10:  R11: 0246 R12: 
[ 1934.273508] R13: 55baf1f7e760 R14: 7ffccbefa0f0 R15: 

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 20 22:46:10 2017
InstallationDate: Installed on 2016-02-21 (606 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=UUID=9ada941b-b897-4db2-94f4-db4646410ed0 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-28 (479 days ago)
dmi.bios.date: 09/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78T-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

** Attachment added: "crash log found in 
/var/crash/_lib_systemd_systemd-udevd.0.crash"
   https://bugs.launchpad.net/bugs/1725479/+attachment/4980243/+files/crash.txt

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

Title:
  systemd-udevd crashes writing ISO with usb-creator-gtk

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Gustavo Milczwski]

I installed Ubuntu 17.10 and the bug isn't there :)

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

[Treviño]

So this is mostly triggered by extensions (and considering how things are done, 
we can't prevent them).
Or some wrong JS code which we didn't identified yet.

Crash for users using dash-to-panel is fixed (I've proposed the fix
upstream https://github.com/jderose9/dash-to-panel/pull/263), for the
others, gjs_dumpstack's are welcome, or we need to wait some debugging
bits to be there.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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() (dash-to-panel specific?)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723774] Re: gnome-software assert failure: *** Error in `/usr/bin/gnome-software': malloc() (gs_plugin_action_stop)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-software assert failure: *** Error in `/usr/bin/gnome-software':
  malloc() (gs_plugin_action_stop)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725456] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

[Apport retracing service]

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

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 #1724439, 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/1725456/+attachment/4980077/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => In Progress

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

Title:
  Thumbnails too small in 'open file' dialog nautilus

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Treviño]

pullasuti, do you have a *.crash file in /var/crash/ related to gnome-
shell?

Please attach them mentioning here the versions of gnome-shell and
libmutter you're using in your systems (mostly for recording them for
later times).

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

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

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

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

Public bug reported:

After not touching my notebook since 30th September (where I did the
dist-upgrade to artful and installed all available updates), I did all
available updates today (20th October) and the system didn't boot after
that.

The last message I see is "Reached target Bluetooth". Before that, there
are several failed services. GDM doesn't come up.

After logging in on tty2, I saw that the root partition was mounted
read-only. Inspecting the messages of e.g. systemd-resolved shows that
it didn't start because of the read-only filesystem. After remounting it
fw, I was able to restart the daemons and could also start GDM and login
fine.

My fstab shows:

UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4errors
=remount-ro 0   1


The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 20 21:46:36 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-26 (451 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre x360 Convertible
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
dmi.bios.date: 09/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.43
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 81A1
dmi.board.vendor: HP
dmi.board.version: 33.76
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug artful

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

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725436] 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/1725436/+attachment/4979889/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725436/+attachment/4979899/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725436

Title:
  gnome-shell crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725438] Re: nautilus crashed with SIGSEGV in nautilus_file_get_search_fts_snippet()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in
  nautilus_file_get_search_fts_snippet()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725434] Re: epiphany crashed with signal 5 in __libc_start_main()

[Apport retracing service]

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

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 #1721922, 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/1725434/+attachment/4979867/+files/CoreDump.gz

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  epiphany crashed with signal 5 in __libc_start_main()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725427] 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/1725427/+attachment/4979810/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725427/+attachment/4979819/+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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1725427

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

[Grzegorz Daniluk]

Same problem on Intel integrated gfx card. I have 4k monitor connected
over DP-1 (to have 4k @ 60Hz). In my case after the crash all apps
(Google Chrome, terminal, ...) are killed. Additionally scaling-factor
and refresh rate are set to incorrect values. Scaling-factor is set to 1
and refresh rate is lowered to 30Hz.

Scaling-factor can be fixed with "gsettings set
org.gnome.desktop.interface scaling-factor 2" However there is no way to
set fixed refresh rate to 60Hz. I have to reboot whole system. So
basically after "blank screen" system has to rebooted.

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

Title:
  Screen blanking and/or screen lock crashes gnome-shell user session on
  wayland - Ubuntu 17.10 beta

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725433] Re: evolution-addressbook-factory-subprocess crashed with SIGSEGV in i18n::phonenumbers::RegExp::FullMatch()

[Apport retracing service]

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

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 #1723375, 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/1725433/+attachment/4979855/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory-subprocess crashed with SIGSEGV in
  i18n::phonenumbers::RegExp::FullMatch()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725422] Re: gnome-shell crashed with signal 5 immediately upon booting to Unity desktop

[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/1725422/+attachment/4979766/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725422/+attachment/4979775/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725422

Title:
  gnome-shell crashed with signal 5 immediately upon booting to Unity
  desktop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725405] 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/1725405/+attachment/4979637/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725405/+attachment/4979646/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725405

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725434] [NEW] epiphany crashed with signal 5 in __libc_start_main()

[Peter Paulsen]

Public bug reported:

It started it self along with Firefox and Chromium when I clicked the
web-link in Synaptic.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: epiphany-browser 3.26.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 20 20:36:24 2017
ExecutablePath: /usr/bin/epiphany
InstallationDate: Installed on 2017-04-08 (195 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: epiphany http://www.gpick.org
ProcEnviron:
 LANGUAGE=de_DE
 TERM=unknown
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: epiphany-browser
StacktraceTop:
 ?? ()
 __libc_start_main (main=0x55b4f9289670, argc=2, argv=0x7ffda997c2e8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffda997c2d8) at ../csu/libc-start.c:308
 ?? ()
Title: epiphany crashed with signal 5 in __libc_start_main()
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

** Affects: epiphany-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  epiphany crashed with signal 5 in __libc_start_main()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1697021] Re: no pointer on startup

[themusicgod1]

still does this, same mouse different computer running
artful/gnome/weyland/gdm3

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

** Tags added: artful

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

Title:
  no pointer on startup

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723772] Re: Shell crashes when left unattended

[Thiago Benites]

There are some news about the problem. It is better now, but still
weird. When I go to the hibernation I can come back and the windows are
not closed anymore, but when I move a windows or close it the screen
flares and so stay it, until I restart the computer.

I got Ubuntu 17.10 on my laptop and I don't have this problem, it works
fine. There's a little detail that can be helpful. When I start the
hibernation there are some seconds until the LED from monitor starts to
blink. If I try to come back before the LED blinks so it works fine
further. Just when the monitor in fact in stand by is I got the problem.

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Thiago Benites (79benites)

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

Title:
  Shell crashes when left unattended

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1723772] Re: Shell crashes when left unattended

[Thiago Benites]

Hello,

I tried what you asked, but wasn't so successful. Only the first one could
be sent. The other files show always an error.

The one it worked is called: _usr_bin_nautilus.1000.crash

The generated link is the following: https://bugs.launchpad.net/ubuntu/+sou
rce/nautilus/+filebug/bdb2a650-b5c2-11e7-8007-
68b5996a96c8?field.title=nautilus+crashed+with+SIGSEGV+in+g_type_check_inst
ance_is_a%28%29

Thanks,


Am Freitag, den 20.10.2017, 07:42 + schrieb Daniel van Vugt:
> Please have a look in /var/crash for .crash files.
> 
> For each crash FILENAME run:  ubuntu-bug /var/crash/FILENAME.crash
> 
> And then add a comment here linking to the newly created bugs.
> 
> ** Summary changed:
> 
> - Hibernation
> + Shell crashes when left unattended
> 
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
> 
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Invalid
> 
> ** No longer affects: linux (Ubuntu)
>

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

Title:
  Shell crashes when left unattended

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725416] [NEW] Elantech touch pad device not detected/working properly

[Christian González]

Public bug reported:

I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some
quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly
- especially the "natural scrolling" mode was working well. As I saw
under Ubuntu Gnome 17.04, the corresponding setting in gnome-control-
center "Natural scrolling" just targets the mouse and has no effect on
the touchpad.

I can see the touchpad using "xinput list":
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad  id=14   [slave  pointer  (2)]
⎜   ↳ Logitech Performance MX   id=12   [slave  pointer  (2)]

alongside my Logitech mouse on a Unifying receiver.

Is there any chance that this touchpad is detected? Or should I forget about 
that (WONTFIX) as Xorg is already unsupported?
ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if 
Wayland is starting using nouveau...
Thanks.
What else do you need from me?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 20:20:04 2017
InstallationDate: Installed on 2016-11-27 (327 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Elantech touch pad device not detected/working properly

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

[acllos]

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

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

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

Title:
  connecting to a WPA-enterprise network from gnome-shell opens up the
  "Networks" panel instead of the Wi-Fi panel

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725402] 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/1725402/+attachment/4979612/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725402/+attachment/4979621/+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 Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1725402

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1537146] Re: gnome-termnial visual glitch: 100% transparent

[themusicgod1]

cannot reproduce on 17.10 artful

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

Title:
  gnome-termnial visual glitch: 100% transparent

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725395] [NEW] screen resolution detected is incompatible with UHD tv

[Paolo Devoti]

Public bug reported:

It was fine with 17.04 and all latest updates but after upgrade to 17.10
there is an issue.

At boot the UHD tv on hdmi is complaining that 720x480 60Hz is
unsupported and screen is displaying nothing.

With another monitor connected on display port looks like the higher
resolutions on hdmi are not handled properly.

VGA is an RX480.

After setting a viable resolution for the UHD tv 1920x1080 it is usable.

After reboot the login screen is still detected at the unworkable
720x480.

Blindly doing a login makes the new display setting to get applied and
it works.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 19:21:10 2017
ExecutablePath: /usr/bin/nautilus-desktop
InstallationDate: Installed on 2017-10-15 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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


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

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

Title:
  screen resolution detected is incompatible with UHD tv

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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: ((unsigned int) number < g

[pullasuti]

Now when I switch my display back on again, I see my desktop and open
windows for a short while, and then am immediately kicked out of the
session. Before the entire desktop would die, now I'm just back at user
select screen.

On two separate systems.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, 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))

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725384] [NEW] On touch screens, the apps icon in the dock does not open when touched

[Juan Pablo Lozano]

Public bug reported:

I have an Bangho AERO 1104 with touch screen, when I try to open the
application drawer from the applications icon in the dock, it does not
open.

1)- Ubuntu 17.10 Artful Aardvark 64 bit
2)- gnome-shell-extension-ubuntu-dock_0.7
3)- What should happen is that touching the applications icon in the dock, 
opens the application drawer.
4)- Instead, what has happened is that absolutely nothing happened

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


** Tags: dock extension gnome-17.10

** Description changed:

  I have an Bangho AERO 1104 with touch screen, when I try to open the
  application drawer from the applications icon in the dock, it does not
  open.
  
- 1)- Ubuntu 17.10 Artful Aardvark
+ 1)- Ubuntu 17.10 Artful Aardvark 64 bit
  2)- gnome-shell-extension-ubuntu-dock_0.7
  3)- What should happen is that touching the applications icon in the dock, 
opens the application drawer.
  4)- Instead, what has happened is that absolutely nothing happened

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

Title:
  On touch screens, the apps icon in the dock does not open when touched

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725389] [NEW] 'authentication required to change privacy settings' you don't actually need to authenticate

[themusicgod1]

Public bug reported:

Setup : 
* 2 users.  one of them has sudo access, the one i'm logged into (gnome/weyland 
default in artful desktop) doesn't
* ubuntu 17.10 artful 
* gnome-control-center:
  Installed: 1:3.26.1-0ubuntu4 
* redshift:
  Installed: 1.11-1ubuntu1

Went to settings->privacy->location settings and changed to location
services = on and then hit the 'x' on the 'location services' window.
it did not change from 'off' to 'on' on the 'privacy' window, however
when i restarted redshift (which until that point had not been working)
redshift immediately started working.  (This suggests to me that until
that point location services was, in fact off, and when i turned it on,
it was turned on).  However, a few seconds later the authorization
prompt came up, graying the screen asking to authenticate to make
changes to my privacy settings(the change which was already made and
working, as evidenced both by working redshift and the fact that if I
went into privacy settings, I would see location services 'in use'
instead of 'off')

"Authentication Required"
"To change your privacy settings you need to authenticate..."

I hit 'escape', and it reopened, I hit 'escape' and it went away, for
about 3 minutes.

Then it came back.  It would continue to come back, prompting me twice
every about 3 minutes until I gave the password to the user (that was
not logged in).

This seems broken.   If authentication is required to enable location
services...it shouldn't work without authentication.  If authentication
is *not* required to enable location services...it shouldn't nag you
twice every ~3 minutes until you acquiesce.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 13:21:04 2017
InstallationDate: Installed on 2017-04-18 (184 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)

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


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

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

Title:
  'authentication required to change privacy settings' you don't
  actually need to authenticate

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725364] 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/1725364/+attachment/4979321/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725364/+attachment/4979331/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725364

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725368] 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/1725368/+attachment/4979373/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1725368/+attachment/4979382/+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 Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1725368

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Stuardo -StR- Rodríguez]

I was not able to find  bug #1631434.

** This bug is no longer a duplicate of private bug 1631434

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

Title:
  gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Apport retracing service]

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

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 #1725271, 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/1725366/+attachment/4979343/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725371] [NEW] 17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower window

[Scott Stensland]

Public bug reported:

It's very handy to send any open Ubuntu application window to below all
other open windows (it says open yet now occluded) by clicking mouse
middle button on window title bar (opposite of left mouse click to bring
to focus front) ... this works fine on all Ubuntu 17.10 applications
except fails on Ubuntu 17.10's file explorer nautilus 3.26.0 which has a
non-standard looking title bar.

This behavior continues to be OK on all other 17.10 applications...
Nautilus worked on previous Ubuntu releases  ... I hope other apps
refrain from using this new window behavior

Any ideas on why nautilus breaks this convention? Or how to fix it?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Oct 20 10:53:51 2017
InstallationDate: Installed on 2017-05-17 (155 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2017-07-30 (81 days ago)
usr_lib_nautilus: dropbox 2015.10.28

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


** Tags: amd64 apport-bug artful

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

Title:
   17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower
  window

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725347] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Apport retracing service]

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

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 #1631434, 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/1725347/+attachment/4979216/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723554] Re: Highlight border flickers in Overview when you hover mouse away from & over window

[Jesse]

@Daniel, thanks for the corrections.

I submitted an upstream bug to GNOME bugzilla, bug #789258.

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

** Tags added: artful

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

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725346] Re: gnome-terminal-server crashed with SIGSEGV

[Apport retracing service]

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

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 #1664613, 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/1725346/+attachment/4979206/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-terminal-server crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725362] [NEW] Network icon shows question mark after connected to wifi, not wifi radio strength icon

[Jesse]

Public bug reported:

BEHAVIOR
After I successfully connect to a wifi network, the network icon in the system 
tray (at the top-right) shows a question mark over the radio strength symbol 
(even though the Internet connect is working fine). After about 3-5 minutes, it 
disappears and the radio symbol shows the signal strength.

EXPECTED BEHAVIOR
For the question mark to not be showing if the connection is successful and 
there is valid Internet access, I suppose.

BUG DISCOVERED USING
Ubuntu 17.10
GNOME 3.26.1
Xorg 1.19.5
Nvidia 384.90 proprietary driver
Linux kernel 4.13.0-16-generic
Panda USB wireless N wifi adapater, connected to a 5.0ghz linksys wireless 
router (E2500)

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


** Tags: artful

** Tags added: artful

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

Title:
  Network icon shows question mark after connected to wifi, not wifi
  radio strength icon

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Jeremy Bicha]

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

Title:
  Gnome web urlbar very slow to show typed input

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725362] Re: Network icon shows question mark after connected to wifi, not wifi radio strength icon

[Jesse]

Screenshot is available upon request.

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

Title:
  Network icon shows question mark after connected to wifi, not wifi
  radio strength icon

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725332] 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/1725332/+attachment/4979136/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: terminal gets smaller when maximized and then restored

[Egmont Koblinger]

@Marius, Ubuntu 17.10 uses gnome-shell by dfault, but unity is still
available.

Actually I'm using unity7 on 17.10, and this bug isn't present there.
However, I can confirm the bug on gnome-shell + wayland.

Interestingly, trying a couple of terminal emulators (xfce4-terminal,
mate-terminal) some are buggy, some are not; and when double clicking on
the title, some maximize with an animation and some maximize without. No
clue why this difference in animation is there, and no clue if it's
relevant.

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

Title:
  terminal gets smaller when maximized and then restored

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725330] Re: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

[Apport retracing service]

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

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 #1631434, 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/1725330/+attachment/4979124/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs