[Bug 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog

[Boyd]

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

I get this with 17.10, i3, and slock.

** Also affects: i3-wm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  desktop contents briefly visible on resume from suspend before lock
  dialog

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

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

[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[Rocko]

Fwiw, this happens every time I turn off the only monitor attached to
the computer, and it loses all unsaved data, so for me it's critical - I
can't use gnome-shell on that computer.

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

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

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

[Daniel van Vugt]

Thanks. That is bug 1731911. Although what you're seeing with your
desktop is gnome-shell committing suicide as a result of Xwayland
crashing, so that is bug 1505409 or bug 1556601.

It would be most useful to you to track the root cause of the problem so
I'll mark this as a duplicate of bug 1731911.

** This bug has been marked a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

[Daniel van Vugt]

Whoops, sorry, you are not the original reporter.

sfc: Please subscribe to bug 1731911 instead.

This bug remains about "intel_do_flush_locked failed: Bad address"

** This bug is no longer a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

[sfc]

Today I got the coredump, but ubuntu-bug cannot upload it, saying
"ValueError ('not enough values to unpack (expected 2, got 1)',)". So I
use "ubuntu-bug xwayland" command, and attached the generated report.
This crash now seems only happens when the system is under load for some
time (in my case high cpu usage).

gdb stacktrace of this coredump, if anything helpful:

Reading symbols from Xwayland...Reading symbols from 
/usr/lib/debug/.build-id/65/efba1189e8c1122d2e74c13bf7e54825c3e367.debug...done.
done.
[New LWP 3455]
[New LWP 3460]
[New LWP 3461]
[New LWP 3462]
[New LWP 3463]
[New LWP 3464]
[New LWP 3465]
[New LWP 3466]
[New LWP 3467]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core -listen 
4 -listen 5 -displayfd'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.
[Current thread is 1 (Thread 0x7f97acaffa80 (LWP 3455))]
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7f97a9b8ff5d in __GI_abort () at abort.c:90
#2  0x555ce6faf13a in OsAbort () at ../../../../os/utils.c:1361
#3  0x555ce6fb4c53 in AbortServer () at ../../../../os/log.c:877
#4  0x555ce6fb5a75 in FatalError (f=f@entry=0x555ce6fbd640 "failed to read 
Wayland events: %s\n") at ../../../../os/log.c:1015
#5  0x555ce6e3b43f in xwl_read_events (xwl_screen=0x555ce8f96a40) at 
../../../../../hw/xwayland/xwayland.c:594
#6  0x555ce6faccb1 in ospoll_wait (ospoll=0x555ce8f8ba20, 
timeout=) at ../../../../os/ospoll.c:412
#7  0x555ce6fa5cbb in WaitForSomething (are_ready=) at 
../../../../os/WaitFor.c:226
#8  0x555ce6f719f3 in Dispatch () at ../../../../dix/dispatch.c:422
#9  0x555ce6f75c90 in dix_main (argc=11, argv=0x7ffce0ab28c8, 
envp=) at ../../../../dix/main.c:287
#10 0x7f97a9b781c1 in __libc_start_main (main=0x555ce6e3aa60 , 
argc=11, argv=0x7ffce0ab28c8, init=, fini=, 
rtld_fini=, stack_end=0x7ffce0ab28b8) at 
../csu/libc-start.c:308
#11 0x555ce6e3aa9a in _start ()


** Attachment added: "apport.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+attachment/5034904/+files/apport.txt

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

Title:
  org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad
  address

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

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

[Bug 1742608] [NEW] systemd sometimes doesn't launch unit files in `~/.config/systemd/user/`

[jappie]

Public bug reported:

I think it's because I have home folder encryption enabled and PAM has
some race condition for launching the systemd --user process.

This is *really* annoying because I launch the emacs daemon like that,
without it I can't start my editor in a muscle memory way.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: kde
Date: Thu Jan 11 15:59:34 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-01-09 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:066d Acer, Inc 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TUXEDO P640RF
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic 
root=UUID=fd57cb1e-dfab-446f-97c8-f08c119c0d6e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06
dmi.board.asset.tag: Tag 12345
dmi.board.name: P640RF
dmi.board.vendor: TUXEDO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TUXEDO
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd09/19/2016:svnTUXEDO:pnP640RF:pvrNotApplicable:rvnTUXEDO:rnP640RF:rvrNotApplicable:cvnTUXEDO:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P640RF
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO

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

Title:
  systemd sometimes doesn't launch unit files in
  `~/.config/systemd/user/`

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

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

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

[Daniel van Vugt]

Thanks. That is bug 1726352 so please discuss it in 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/1714886

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

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

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

[Bug 378592] Re: py-gobject crash on subclasses

[Bug Watch Updater]

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/378592

Title:
  py-gobject crash on subclasses

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

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

[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

[Apport retracing service]

** Tags added: bionic

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

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

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

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

[Bug 1742598] Re: gnome-shell crashed with SIGSEGV

[Apport retracing service]

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

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 #1726352, 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/1742598/+attachment/5034853/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1726352
   gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

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

Title:
  gnome-shell crashed with SIGSEGV

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

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

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

[Rocko]

gnome-shell is definitely still crashing in Bionic whenever I turn off
the only attached monitor, so I've opened bug #1742598 with one of the
crash dumps it generated.

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

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

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

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

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

[jrstravino]

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

** Description changed:

  Artful (17.10) Session logout after screen turned off
  
- Whenever I turn off my screen, the computer (a desktop PC) logs me out
- of my session.
+ Whenever I turn off my screen and then turn it on the problem occurs. the 
computer (a desktop PC) logs me out of my session.
+ When I wake the screen, I get the GDM login screen and a new session opens.
+ The previous session is lost.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 18:08:20 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1510175942
  GsettingsChanges:
-  b'org.gnome.shell' b'enabled-extensions' 
b"['gnome-shell-screens...@ttll.de']"
-  b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'org.gnome.gedit.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'update-manager.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'plexmediamanager.desktop', 'gnome-system-monitor.desktop', 
'transmission-gtk.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'icon-theme' b"'Numix-Square'"
-  b'org.gnome.desktop.interface' b'gtk-theme' b"'Arc-Darker'"
+  b'org.gnome.shell' b'enabled-extensions' 
b"['gnome-shell-screens...@ttll.de']"
+  b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'org.gnome.gedit.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'update-manager.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'plexmediamanager.desktop', 'gnome-system-monitor.desktop', 
'transmission-gtk.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'icon-theme' b"'Numix-Square'"
+  b'org.gnome.desktop.interface' b'gtk-theme' b"'Arc-Darker'"
  InstallationDate: Installed on 2017-12-03 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tux
  ProcEnviron:
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f97ba3992d4 :mov
0x18(%rax),%eax
-  PC (0x7f97ba3992d4) ok
-  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7f97ba3992d4 :mov
0x18(%rax),%eax
+  PC (0x7f97ba3992d4) ok
+  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
+  destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
-  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
-  ?? () from /usr/lib/libgjs.so.0
-  ?? () from /usr/lib/libgjs.so.0
+  meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
+  ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
+  ?? () from /usr/lib/libgjs.so.0
+  ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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/1742540/+subscriptions

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

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

[jrstravino]

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

** Description changed:

  Artful (17.10) Session logout after screen turned off
  
- Whenever I turn off my screen, the computer (a desktop PC) logs me out
- of my session.
+ Whenever I turn off my screen and then turn it on the problem occurs. the 
computer (a desktop PC) logs me out of my session.
+ When I wake the screen, I get the GDM login screen and a new session opens.
+ The previous session is lost.
  
  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Jan  8 18:33:01 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1510175942
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2017-12-03 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/false
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
-  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? ()
-  g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? ()
+  g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

[Bug 1412308] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726026
   gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion 
failed: (window->display->focus_window != window)"]
** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

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

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

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

[Bug 1351011] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726026
   gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion 
failed: (window->display->focus_window != window)"]
** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

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

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

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

[Bug 1362952] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726026
   gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion 
failed: (window->display->focus_window != window)"]
** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

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

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

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

[Bug 1379893] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726026
   gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion 
failed: (window->display->focus_window != window)"]
** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

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

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

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

[Bug 1364791] Re: gnome-shell crashed with SIGABRT in raise()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1726026
   gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion 
failed: (window->display->focus_window != window)"]
** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

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

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

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

[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro

[Daniel van Vugt]

And:
https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message("assertion
  failed: (window->display->focus_window != window)") from
  g_assertion_message_expr() from meta_window_unmanage() from
  handle_other_xevent()

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

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

[Bug 1422253] Re: gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: (window->display->focus_window != window)") from g_assertion_message_expr() from meta_window_unmanage() fro

[Daniel van Vugt]

Also tracking in:
https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7

** Summary changed:

- gnome-shell crashed with SIGABRT in g_assertion_message()
+ gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

** Description changed:

+ https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
+ 
+ ---
+ 
  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic was
  in process of installing programs (downloads were complete & actual
  install was in progress)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
-  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
+  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  meta_window_unmanage () from /usr/lib/libmutter.so.0
-  ?? () from /usr/lib/libmutter.so.0
-  ?? () from /usr/lib/libmutter.so.0
+  g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  meta_window_unmanage () from /usr/lib/libmutter.so.0
+  ?? () from /usr/lib/libmutter.so.0
+  ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Tags added: artful bionic xenial

** Information type changed from Private to Public

** Description changed:

  https://errors.ubuntu.com/problem/868da6d40640c1199f496b7af7e37e54871ed8d7
+ https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5
  
  ---
  
  Was running 3 programs at time of crash, PROGRAM 1. Nautilus with no
  tabs open, PROGRAM 2. Firefox v.34.0 with 3 tabs open (1.
  https://twitter.com/ - 2.
  http://www.scons.org/wiki/FrequentlyAskedQuestions#What_is_SCons.3F -
  PROGRAM 3. http://scons.org/download.php) Synaptic Package Manager ver
  0.81.3 installing Scons & Scons-doc - crash happened while synaptic was
  in process of installing programs (downloads were complete & actual
  install was in progress)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-shell 3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 16 01:20:05 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2015-01-26 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 
(20150120.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   meta_window_unmanage () from /usr/lib/libmutter.so.0
   ?? () from 

[Bug 1726026] Re: gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion failed: (window->display->focus_window != window)"]

[Daniel van Vugt]

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

Looks like this crash is several years old so it's had a few variations.
Now tracking in bug 1422253.

** This bug has been marked a duplicate of bug 1422253
   gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed: 
(window->display->focus_window != window)") from g_assertion_message_expr() 
from meta_window_unmanage() from handle_other_xevent()

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion
  failed: (window->display->focus_window != window)"]

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

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

[Bug 1742594] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

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


** Tags: artful bionic kylin-17.10

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

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

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

[Bug 1742594] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

[Daniel van Vugt]

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

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

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_unmanage

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

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

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

[Daniel van Vugt]

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

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


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

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

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

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Daniel van Vugt]

I'm not sure but you should have seen some text output from that
command. Can you paste it all here?

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1739625] Re: Mouse events pass through pure Wayland windows (that use wl_shell)

[Daniel van Vugt]

Yes and no :)

I believe the "z" prefix means that interface is still unstable and
subject to change. So you might actually be better off staying with
wl_shell which is "stable" and won't change. The fix for this bug will
be in Ubuntu 18.04 soon hopefully, and I think it may probably land in
17.10 too, based on previous updates.

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

Title:
  Mouse events pass through pure Wayland windows (that use wl_shell)

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

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

[Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

[Daniel van Vugt]

Thanks for that. I'm seeing this bug on maybe 2/3 laptops I've tried
with Ubuntu 18.04.

** Tags added: bionic

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

Title:
  Wifi connection status icon shows a "?" when connected

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

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

[Daniel van Vugt]

hamid,

Just run 'journalctl' after logging in. Look through the log carefully
and you'll find two adjacent timestamps that are many seconds apart.
What are those log entries?

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1735986] Re: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

[Lindsay Gaines]

I just installed a fresh install of Ubuntu artful (17.10) yesterday, on
a Dell XPS 13 9630, and am affected by the same issue.

My laptop has a HiDPI built-in display with a resolution of 3200x1800,
and I also connect an external ASUS monitor at work, which has a
resolution of 1920x1080.

The laptop has an integrated Intel graphics card, and the external
display is connected via a USB Type-C hub that has an HDMI output.

The display arrangement was set correctly when I plugged in the external
monitor, except for the positioning of the external display, which I
adjusted.

* Built-in display:
** Resolution: 3200x1800
** Scale: 200%
* External display:
** Resolution: 1920x1080
** Scale: Not shown, but set to 100%

Moving native apps like terminal, settings windows, file explorer across
monitors correctly scales them based on the scale setting of each
monitor. However:

* Chrome, Firefox, PHPstorm (IntelliJ) are always scaled to 200% on both 
monitors
* Moving these windows between monitors does not adjust their scaling
* Maximising a window on the external display does not adjust its scaling

Not sure what commands / log files might be helpful here but I'd be
happy to run any kind of diagnostic necessary.

Thanks for opening this bug.
Lindsay

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

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

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

[Bug 1735986] Re: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

[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/1735986

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

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

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

[Bug 1742542] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1742542/+attachment/5034716/+files/StacktraceSource.txt

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

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

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

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

[Bug 1742542] gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:554
 g_log_default_handler (log_domain=, log_level=, 
message=, unused_data=) at 
../../../../glib/gmessages.c:3051
 default_log_handler (log_domain=log_domain@entry=0x7fdc8ec61b93 "mutter", 
log_level=log_level@entry=6, message=message@entry=0x55f377a95f60 "Connection 
to xwayland lost", data=data@entry=0x0) at ../src/main.c:315
 g_logv (log_domain=0x7fdc8ec61b93 "mutter", log_level=G_LOG_LEVEL_ERROR, 
format=, args=args@entry=0x7ffc9606d690) at 
../../../../glib/gmessages.c:1341
 g_log (log_domain=log_domain@entry=0x7fdc8ec61b93 "mutter", 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7fdc8ec72af0 
"Connection to xwayland lost") at ../../../../glib/gmessages.c:1403

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

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

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

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

[Bug 1742542] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742542/+attachment/5034715/+files/Stacktrace.txt

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

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

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

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

[Bug 1742542] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742542/+attachment/5034717/+files/ThreadStacktrace.txt

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

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

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

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

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

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

[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[jrstravino]

@Andrzej Wojtaszewski
@Daniel van Vugt (vanvugt)


ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
Bug #1742540
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742540

ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash
Bug #1742542
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742542

ubuntu-bug /var/crash/_usr_bin_Xwayland.1000.crash
Bug #1742544
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1742544

ubuntu-bug /var/crash/_usr_bin_Xwayland.121.crash
Bug #1742545
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1742545

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

Title:
  Artful (17.10) Session logout after screen turned off

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

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

[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[jrstravino]

Even when enabled, apport will not upload crash reports to Launchpad for
a stable release (see bug #994921). Instead, crash reports are uploaded
to http://errors.ubuntu.com. To file a report on Launchpad anyway, one
may open the following file via a command line:

gksudo gedit /etc/apport/crashdb.conf
and change:

'problem_types': ['Bug', 'Package'],
to:

# 'problem_types': ['Bug', 'Package'],
Save, close, and try to file the crash report again via:

ubuntu-bug /var/crash/_my_crash_report.crash

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

Title:
  Artful (17.10) Session logout after screen turned off

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

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

[Bug 1742542] [NEW] gnome-shell crashed with signal 5 in g_log_default_handler()

[jrstravino]

Public bug reported:

Artful (17.10) Session logout after screen turned off

Whenever I turn off my screen, the computer (a desktop PC) logs me out
of my session.

Here is a discussion thread with users of similar issue:
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Jan  8 18:33:01 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1510175942
GsettingsChanges:
 
InstallationDate: Installed on 2017-12-03 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: 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/1742542

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

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

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

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

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742540/+attachment/5034660/+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()

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

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/1742540/+subscriptions

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

[Bug 1742540] [NEW] gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

[jrstravino]

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

Public bug reported:

Artful (17.10) Session logout after screen turned off

Whenever I turn off my screen, the computer (a desktop PC) logs me out
of my session.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  9 18:08:20 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1510175942
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['gnome-shell-screens...@ttll.de']"
 b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'firefox.desktop', 'org.gnome.gedit.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'update-manager.desktop', 
'org.gnome.Software.desktop', 'org.gnome.Terminal.desktop', 
'plexmediamanager.desktop', 'gnome-system-monitor.desktop', 
'transmission-gtk.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'icon-theme' b"'Numix-Square'"
 b'org.gnome.desktop.interface' b'gtk-theme' b"'Arc-Darker'"
InstallationDate: Installed on 2017-12-03 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tux
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f97ba3992d4 :  mov
0x18(%rax),%eax
 PC (0x7f97ba3992d4) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/libgjs.so.0
 ?? () from /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash artful

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

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/1742540/+subscriptions

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

[Bug 1292041] Re: Lockscreen doesn't turn off the screen

[gst]

also affected by this. being on 16.04.3

If I manually lock my session then the screen(s) turn off and stay off
(though one is keeping the mouse pointer visible but appart from that
the screen is black at least).

but when system goes idle and automatically lock the session then the
screen(s) turn off (really) but a moment after they turn back on and
then stay on.

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

Title:
  Lockscreen doesn't turn off the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+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

[Francisco]

I am also experiencing this issue, when I click on settings it "loads"
for a few seconds but nothing is displayed.

-- 
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 1739625] Re: Mouse events pass through pure Wayland windows (that use wl_shell)

[Hadrien]

Nice! Good job, Daniel.

I learned with one of your comment that the wl_shell interface is
deprecated. After some search, it seems that zxdg_shell_v6 should be
used instead?

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

Title:
  Mouse events pass through pure Wayland windows (that use wl_shell)

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

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

[Bug 1741632] Re: FW update error: could not find thunderbolt device

[Mario Limonciello]

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

This was reported to me through Github.
https://github.com/dell/thunderbolt-nvm-linux/issues/8

It's already been fixed upstream and I have an SRU bug filed here:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1741509

it's waiting for archive admin to accept.

** This bug has been marked a duplicate of bug 1741509
   Thunderbolt updates on Dell systems fail to apply if nothing connected

** Bug watch added: github.com/dell/thunderbolt-nvm-linux/issues #8
   https://github.com/dell/thunderbolt-nvm-linux/issues/8

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

Title:
  FW update error: could not find thunderbolt device

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

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

[Bug 1741632] Re: FW update error: could not find thunderbolt device

[Will Cooke]

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

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

Title:
  FW update error: could not find thunderbolt device

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

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

[Bug 1742500] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Jeremy Hunt]

Public bug reported:

Tried to update and this is the error I recieved

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 235-3ubuntu3
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
Date: Wed Jan 10 17:47:55 2018
Dmesg:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcInterrupts:
 
ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro
ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: 
sort: cannot read: /proc/modules: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
Title: package systemd 235-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-01-10 (0 days ago)

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


** Tags: amd64 apport-package third-party-packages uec-images xenial

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

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

[Bug 1738503] Re: Cannot Install SNAPS from Gnome-Software Bionic

[Stephen Allen]

I reinstalled (clean install) didn't use previous ~/home as I usually
do. I was thinking some data carried over from another distro may have
corrupted things. I usually keep ~home on a separate partition so I can
/install various distributions on the main drives, all sharing the same
~/home. Never ran into any issues until now. So I'll close this bug,
unless someone else is having the same problem?

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

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

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

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

[Bug 1741632] Re: FW update error: could not find thunderbolt device

[Miguel A. Martinez]

Reproducible via the CLI too

```
fwupdmgr update
Downloading 21.00 for XPS13 9360 Thunderbolt Controller...
Fetching firmware 
https://fwupd.org/downloads/eac3961ba9bd466f6e34d9276c27d524395d7c3c-NN1TN_NVM21.00.cab
Downloading…   []
Updating 21.00 on XPS13 9360 Thunderbolt Controller...
Decompressing… [-   ]
could not find thunderbolt device at 
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0

```

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

Title:
  FW update error: could not find thunderbolt device

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

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

[Bug 1740651] Re: gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

[Egmont Koblinger]

Looks like the bug is in libhime rather than gnome-terminal itself.

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

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

Title:
  gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

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

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

[Bug 869793] Re: Nautilus is very slow when opening folders with many files

[Bao Nguyen]

2018 now and nothing has changed.

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

Title:
  Nautilus is very slow when opening folders with many files

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

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

[Bug 1738503] Re: Cannot Install SNAPS from Gnome-Software Bionic

[Ken VanDine]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => James Henstridge (jamesh)

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

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

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

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

[Bug 1742429] Re: kernel 4.4.0-108 reboot fails

[Joseph Salisbury]

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

** This bug is no longer a duplicate of bug 1742416
   Kernel Panic on shutdown/restart (4.4.0-108.131)
** This bug has been marked a duplicate of bug 1741934
   Kernel trace with xenial 4.4  (4.4.0-108.131, Candidate kernels for PTI fix)

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

Title:
  kernel 4.4.0-108 reboot fails

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

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

[Bug 1742429] Re: kernel 4.4.0-108 reboot fails

[Arne]

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

** This bug has been marked a duplicate of bug 1742416
   Kernel Panic on shutdown/restart (4.4.0-108.131)

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

Title:
  kernel 4.4.0-108 reboot fails

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

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

[Bug 1742429] [NEW] kernel 4.4.0-108 reboot fails

[peterzay]

Public bug reported:

Only workaround is to hold the power button for 5 seconds.

Then reboot into grub, select advanced, and select the previous kernel
104 to get s successful boot.

Could this be Spectre and Meltdown fix related?

ubuntu-bug gedit was used to report this bug.  Please change to correct
package.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jan 10 07:14:23 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-22 (172 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  kernel 4.4.0-108 reboot fails

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

@Daniel

Even
env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug 
/var/crash/_usr_bin_gnome-shell.1000.crash

does not provide needed link.

Are there any system settings that can affect this behavior?

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[RégisC]

No, there's nothing in /var/crash

I also found the bug you are talking about when searching for the error
message. I added myself to the bug mail for 1736011. Thanks for your
help Daniel :)

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1548970] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

[Leon Rozanov]

Suddenly happened after an update and reboot.
Ubuntu 16.04.3 LTS

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

Title:
  gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

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

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

[Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

[Scorpius]

The problem was solved for me when I set `dns=default` in
NetworkManager.conf

```
cat /etc/NetworkManager/NetworkManager.conf 
[main]
plugins=ifupdown,keyfile
; dns=dnsmasq
dns=default

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no
```

P.S. It also solve other DNS problems for me.

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

Title:
  Wifi connection status icon shows a "?" when connected

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

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

[hamid]

vanvugt,

Interesting point you raise there. I consistently see a delay when
logging in, between my password being accepted , screen going blank, and
my desktop wallpaper "zooming" (it grows from the centre of the screen)
in. Not 25 seconds, but in my case closer to 5-10 seconds. Could this be
related?

I'm running 17.10, and X (since Nvidia drivers caused Wayland to be
disabled).

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1741886] ProcEnviron.txt

[Alexey Balmashnov]

apport information

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

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1741886] ProcCpuinfoMinimal.txt

[Alexey Balmashnov]

apport information

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

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Daniel van Vugt]

Or try this:

  env -uDISPLAY -uWAYLAND_DISPLAY ubuntu-bug /var/crash/_usr_bin_gnome-
shell.1000.crash

to force it to use text mode, which eventually will let you see the link
to use.

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

apport information

** Tags added: apport-collected

** Description changed:

  Upon physical disconnect/connect of a monitor (connected via HDMI) shell
  crashes with signal 11.
  
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.2-0ubuntu0.1
  
  
  Expected is that physical disconnect/connect of a monitor will not influence 
the desktop environment.
  
  
  Note that the crash file was generated and according to /var/crash content 
was uploaded, when ubuntu-bug triggered by existence of crash file started up 
and I agreed with it. Pressing "Continue" button in ubuntu-bug did not bring me 
to Launchpad (yet another bug???) for providing details, therefore I've used 
"ubuntu-bug gnome-shell" instead.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:12:14 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-blink' b'false'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2016-01-06 (732 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-09-06 (123 days ago)
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 17.10
+ GsettingsChanges:
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'cursor-blink' b'false'
+  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
+ InstallationDate: Installed on 2016-01-06 (734 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
+ Package: gnome-shell 3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
+ Tags:  artful
+ Uname: Linux 4.13.0-25-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-09-06 (125 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1741886] JournalErrors.txt

[Alexey Balmashnov]

apport information

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

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

OK, thanks. This looks like it:

janv. 10 07:54:48 hephaistos gnome-session[2639]: gnome-session-binary[2639]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de 
l’appel de StartServiceByName pour org.gnome.ScreenSaver : Le délai 
d’attente est dépassé
janv. 10 07:54:48 hephaistos gnome-session-binary[2639]: CRITICAL: Unable to 
create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de 
StartServiceByName pour org.gnome.ScreenSaver : Le délai d’attente est 
dépassé
janv. 10 07:54:48 hephaistos gnome-screensav[2776]: Couldn't get presence 
status: The name org.gnome.SessionManager was not provided by any .service files
janv. 10 07:54:48 hephaistos dbus-daemon[2632]: Successfully activated service 
'org.gnome.ScreenSaver'

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

We can probably merge this with bug 1736011. Just wait and see what the
reporter of that one says.

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login

[Daniel van Vugt]

Alternatively, such freezes are often due to something crashing and the
delay is your system writing a dump/crash file. Do you see any files in
/var/crash ?

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

Title:
  Ubuntu (gnome) freezes temporarily upon login

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

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

[Daniel van Vugt]

dino99,

I believe this error will also cause a 25 second delay (the default dbus
timeout) when logging in. Is that what you experience?

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Daniel van Vugt]

Ah, sorry. Maybe I'm seeing a different interface through ssh. Mine is
text so it never opens a GUI. Maybe try using 'apport-cli' instead?

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1741886] Re: GNOME shell crashes with sig 11 upon monitor disconnect

[Alexey Balmashnov]

Well, I have done what you suggested. Invoking ubuntu-bug on a crash
file creates corresponding upload* files but does not print any links.

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

Title:
  GNOME shell crashes with sig 11 upon monitor disconnect

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

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

[Bug 1740651] Re: gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

[Jean-Baptiste Lallement]

** 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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1740651

Title:
  gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

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

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

[Bug 1738670] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned
** This bug has been marked a duplicate of bug 1742147
   upgrade from 17.10 to 18.04 fails with triggers looping

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1738660] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned
** This bug has been marked a duplicate of bug 1742147
   upgrade from 17.10 to 18.04 fails with triggers looping

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1740997] Re: package systemd 235-3ubuntu2 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned
** This bug has been marked a duplicate of bug 1742147
   upgrade from 17.10 to 18.04 fails with triggers looping

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

Title:
  package systemd 235-3ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1741086] Re: No option to "snap desktop icons to grid" -- FEATURE REQUEST

[Jean-Baptiste Lallement]

** Package changed: ubuntu-meta (Ubuntu) => nautilus (Ubuntu)

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  No option to "snap desktop icons to grid" -- FEATURE REQUEST

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

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

[Bug 1741940] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Jean-Baptiste Lallement]

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

** This bug is no longer a duplicate of bug 1742143
   package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, 
abandoned
** This bug has been marked a duplicate of bug 1742147
   upgrade from 17.10 to 18.04 fails with triggers looping

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1742134] Re: gnome-software crashed with signal 5 in g_cancellable_make_pollfd()

[Jean-Baptiste Lallement]

** 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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1742134

Title:
  gnome-software crashed with signal 5 in g_cancellable_make_pollfd()

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

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

[Bug 1741086] [NEW] No option to "snap desktop icons to grid" -- FEATURE REQUEST

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

It is annoying that I cannot keep my desktop icons perfectly spaced into
a grid fashion, unlike Windows and MacOS which *do* have that option.

Not only annoying, but also not being able to have my icons perfectly
aligned interferes with my productivity level as well, as it can take a
little longer for me to sift through my icons because they are
distributed unevenly across a horizontal and vertical playing field.

The [current] "keep aligned" option only works in a vertical fashion,
and not horizontal.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-desktop 1.404.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
Uname: Linux 4.13.0-21-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan  3 11:49:45 2018
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-desktop
 Importance: Wishlist
 Status: Unknown

** Affects: gnome-shell
 Importance: Wishlist
 Status: Unknown

** Affects: ubuntu-seeds
 Importance: Wishlist
 Status: Unknown

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


** Tags: 17.10 2d 3d amd64 apport-bug artful desktop feature feature-request 
featurerequest gnome gnome-shell gui needswork request ubuntu-desktop 
wayland-session workspace
-- 
No option to "snap desktop icons to grid" -- FEATURE REQUEST
https://bugs.launchpad.net/bugs/1741086
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to nautilus in Ubuntu.

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