[Bug 1754218] Re: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected
** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=794167 Importance: Unknown Status: Unknown ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1754218 Title: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1754218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754244] [NEW] [bionic] evolution-source-registry always using 100% cpu
Public bug reported:
evolution-source-registry is using 100% CPU after login and never stops,
it continues to do so after kill/respawn or reboot. This started
sometime after upgrade to bionic and has been consistent for the last
couple of weeks.
Looking at the process with perf, it seems that it is looping calling
poll() via g_main_context_poll() via g_main_context_iterate in a hard
loop. In strace you can also see poll being called about 10,000
times/second.
poll([{fd=3, events=POLLIN}, {fd=11, events=POLLIN}], 2, 0) = 0
(Timeout)
gdb backtrace for the main thread reflected in the attached out.svg -
setting a breakpoint g_main_context_iterate is being called continually
but we never exit from g_main_loop_run.
(gdb) bt
#0 0x7f6e1ce30150 in g_main_context_iterate (context=0x55ca494d18c0,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ../../../../glib/gmain.c:3840
#1 0x7f6e1ce30662 in g_main_loop_run (loop=0x55ca4949f580) at
../../../../glib/gmain.c:4099
#2 0x7f6e1df22710 in dbus_server_run_server (server=0x55ca494df1a0
[ESourceRegistryServer]) at ./src/libebackend/e-dbus-server.c:247
#3 0x7f6e19502dae in ffi_call_unix64 () at
/usr/lib/x86_64-linux-gnu/libffi.so.6
#4 0x7f6e1950271f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#5 0x7f6e1d10ab4d in g_cclosure_marshal_generic_va
(closure=0x55ca494d8ab0, return_value=0x7ffd34330e10, instance=,
args_list=, marshal_data=, n_params=0,
param_types=0x0) at ../../../../gobject/gclosure.c:1604
#6 0x7f6e1d10a1a6 in _g_closure_invoke_va (closure=0x55ca494d8ab0,
return_value=0x7ffd34330e10, instance=0x55ca494df1a0, args=0x7ffd34330ec0,
n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
#7 0x7f6e1d1256df in g_signal_emit_valist (instance=0x55ca494df1a0,
signal_id=, detail=,
var_args=var_args@entry=0x7ffd34330ec0)
at ../../../../gobject/gsignal.c:3300
#8 0x7f6e1d125e0f in g_signal_emit
(instance=instance@entry=0x55ca494df1a0, signal_id=,
detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447
#9 0x7f6e1df22a1d in e_dbus_server_run (server=0x55ca494df1a0
[ESourceRegistryServer], wait_for_client=0) at
./src/libebackend/e-dbus-server.c:441
#10 0x55ca473cec0c in main (argc=, argv=) at
./src/services/evolution-source-registry/evolution-source-registry.c:233
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.27.90-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon
znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 8 13:28:39 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/evolution/evolution-source-registry
ProcEnviron:
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: evolution-data-server
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: evolution-data-server (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
** Description changed:
evolution-source-registry is using 100% CPU after login and never stops,
it continues to do so after kill/respawn or reboot. This started
sometime after upgrade to bionic and has been consistent for the last
couple of weeks.
Looking at the process with perf, it seems that it is looping calling
poll() via g_main_context_poll() via g_main_context_iterate in a hard
loop. In strace you can also see poll being called about 10,000
times/second.
poll([{fd=3, events=POLLIN}, {fd=11, events=POLLIN}], 2, 0) = 0
(Timeout)
gdb backtrace for the main thread reflected in the attached out.svg -
setting a breakpoint g_main_context_iterate is being called continually
but we never exit from g_main_loop_run.
+ (gdb) bt
+ #0 0x7f6e1ce30150 in g_main_context_iterate (context=0x55ca494d18c0,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
+ at ../../../../glib/gmain.c:3840
+ #1 0x7f6e1ce30662 in g_main_loop_run (loop=0x55ca4949f580) at
../../../../glib/gmain.c:4099
+ #2 0x7f6e1df22710 in dbus_server_run_server (server=0x55ca494df1a0
[ESourceRegistryServer]) at ./src/libebackend/e-dbus-server.c:247
+ #3 0x7f6e19502dae in ffi_call_unix64 () at
/usr/lib/x86_64-linux-gnu/libffi.so.6
+ #4 0x7f6e1950271f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
+ #5 0x7f6e1d10ab4d in g_cclosure_marshal_generic_va
(closure=0x55ca494d8ab0, return_value=0x7ffd34330e10, instance=,
args_list=, marshal_data=, n_params=0,
param_types=0x0) at ../../../../gobject/gclosure.c:1604
+ #6 0x7f6e1d10a1a6 in _g_closure_invoke_va (closure=0x55ca494d8ab0,
return_value=0x7ffd34330e10, instance=0x55ca494df1a0, args=0x7ffd34330ec0,
n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
+ #7 0x7f6e1d1256df in g_signal_e
[Bug 1754218] Re: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected
I have reported it at https://bugzilla.gnome.org/show_bug.cgi?id=794167. ** Bug watch added: GNOME Bug Tracker #794167 https://bugzilla.gnome.org/show_bug.cgi?id=794167 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1754218 Title: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines after the latest round of updates when shutting down or restarting from whisker menu. 'shutdown (-r) now' works without an error. The most commonly reported 'fix' for this problem is purging old kernels. I just reinstalled 18.3 Cinnamon 64 from scratch on one and then installed all the updates. There were only 2 kernels. I removed 4.10 4.13.0-36 is the only one installed. It did not fix the problem. I did not have the problem before the last round of updates. Also on another computer with 18.2 which has not been turned on for a while I never had the problem until I just installed updates. It is using 4.10.0-33 kernel. 4.8.0.53, 4.10.0-33, and 4.13.0-36 are installed. I had no problem with on two 18.3 XFCE 64 bit machines. One I last used/updated Sunday 3/4 or another I just updated (including latest kernel) as of 3/8/18 0245Z. All computers are set for autologin. I tried turning autologin off on one Cinnamon but that had no effect. It appears there is something in the recent updates for Cinnamon that is causing this problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/608162 Title: GNOME Keyring Daemon stops panel's shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754218] Re: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected
Rocko, Please report the issue to the gdm developers here: https://bugzilla.gnome.org/enter_bug.cgi?product=gdm and then let us know the new bug ID. ** Summary changed: - gdm shows blank login screen on primary monitor when two monitors are connected + [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected ** Tags added: multi-monitor regression ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1754218 Title: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754227] Re: [bionic] gnome-disks crashed when reformatting FAT partition with SIGSEGV in udisks_partition_table_get_type_()
*** This bug is a duplicate of bug 1750289 *** https://bugs.launchpad.net/bugs/1750289 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 #1750289, 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/1754227/+attachment/5072614/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072616/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072619/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072620/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072621/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072622/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754227/+attachment/5072623/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1750289 gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_() ** 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-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1754227 Title: [bionic] gnome-disks crashed when reformatting FAT partition with SIGSEGV in udisks_partition_table_get_type_() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1754227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754218] Re: gdm shows blank login screen on primary monitor when two monitors are connected
** Summary changed: - gdm turns off the primary (login) monitor when two monitors are connected + gdm shows blank login screen on primary monitor when two monitors are connected ** Description changed: I normally have a second monitor plugged into my laptop. Recently in Ubuntu 18.04 (this is a regression that has happened in the last week or - so), when I boot the laptop I get presented with a blank login screen. - (The external monitor just shows the background screen, so it looks as - if gdm3 has hung or crashed.) + so), when I boot the laptop I get presented with a blank login screen - + there is a mouse pointer, but the screen is just black instead of + displaying the user names and top status bar. (The external monitor just + shows the background screen, so it looks as if gdm3 has hung or + crashed.) - If I unplug the external monitor, gdm turns the primary screen back on + If I unplug the external monitor, gdm draws the login screen correctly and I can log in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 10:59:11 2018 InstallationDate: Installed on 2017-08-16 (203 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2017-11-17 (110 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1754218 Title: gdm shows blank login screen on primary monitor when two monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754225] [NEW] The display settings in gnome-control-center are annoying to use for multiple monitors
Public bug reported: Adjusting display settings for multiple monitors in gnome-shell in Ubuntu 17.10/18.04 is really annoying due to its user-unfriendly operation: 1. When you select a resolution, you have to go and look for the small close button in the resolution selection window's titlebar and manually close the resolution selection window. It should close the window automatically when you select the resolution. 2. When you change the scaling (eg from 200% to 100%), it always resets the monitor layout to left-right. So if you have already changed it to above/below and then you change the scaling from 200% to 100% for the primary monitor, the layout resets to left-right and you have to change it back again. 3. The default in X11 when it forgets the monitor settings is to set native resolutions on both monitors. In X11, if the laptop monitor is 4K and the external monitor say 1920x1080, in X11 it inexplicably sets both to scale to 200%, so the text etc on the external monitor is gigantic. (IIRC, it doesn't have this problem in Wayland - it will set the 4K to 200% and the external to 100%.) 4. In case 3, when I change the 4K display to 1920x1020 and then change the scaling from 200% to 100%, the 'Apply' button disappears so it's impossible to select the new configuration. (It seems that it considers these different configurations to be equivalent, perhaps because they have both been divided by two?) This is made worse by the fact that normally g-c-c remembers settings for different monitors (ie resolutions and display layouts for different monitors), but it completely forgets when either: a) You switch between Wayland and X11; b) At apparent random intervals, particularly if you change monitors (eg from a 1920x1080 one to a 1680x1050 one). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 11:05:49 2018 InstallationDate: Installed on 2017-08-16 (203 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-17 (110 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1754225 Title: The display settings in gnome-control-center are annoying to use for multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754225/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754218] [NEW] gdm turns off the primary (login) monitor when two monitors are connected
Public bug reported: I normally have a second monitor plugged into my laptop. Recently in Ubuntu 18.04 (this is a regression that has happened in the last week or so), when I boot the laptop I get presented with a blank login screen. (The external monitor just shows the background screen, so it looks as if gdm3 has hung or crashed.) If I unplug the external monitor, gdm turns the primary screen back on and I can log in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 10:59:11 2018 InstallationDate: Installed on 2017-08-16 (203 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2017-11-17 (110 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1754218 Title: gdm turns off the primary (login) monitor when two monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754210] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1754210/+attachment/5072537/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072539/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072542/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072543/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072544/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072545/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754210/+attachment/5072546/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1754210 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753078] Re: gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer()
This looks like a new crash nobody has reported before. It also looks like it might be crashing in some kind of CPU-monitoring shell extension. Please try removing/disabling your non-standard gnome-shell extensions. Please also let us know which system/CPU-monitoring shell extension(s) you are using and where they came from. ** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s() ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1753078 Title: gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754077] Re: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1754077 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1754077 Title: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 Great, thanks. This is now a duplicate of bug 1724439. ** 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() -- 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/1753658 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754199] [NEW] Mounted Volume ICON not displayed on desktop
Public bug reported: Have several NFS volumes that I mount and unmount. Have always seen the volume ICON show up on the desktop and the nautilus shortcut panel but this is no longer occurring in 18.04. The mount is available. Have verified that the tweaks-ui setting is ON for mounted volumes. Believe this was ok in earlier daily builds. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 19:17:45 2018 InstallationDate: Installed on 2018-03-05 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1754199 Title: Mounted Volume ICON not displayed on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
The attachment "Patch for Bionic Beaver 18.04 LTS, it fixes the problem" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754154] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1754154/+attachment/5072158/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072160/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072164/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072165/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072166/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072167/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754154/+attachment/5072168/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1754154 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/1754154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754088] Re: gnome-software crashed with SIGSEGV in g_type_check_instance()
*** This bug is a duplicate of bug 1752645 *** https://bugs.launchpad.net/bugs/1752645 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 #1752645, 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/1754088/+attachment/5071873/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071875/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071879/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071880/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071881/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071882/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754088/+attachment/5071883/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1752645 ** 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-software in Ubuntu. https://bugs.launchpad.net/bugs/1754088 Title: gnome-software crashed with SIGSEGV in g_type_check_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
How are you closing RhythmBox? The program is not actually closed if music is playing and you press the X on the top right corner. Usually I had to do CTRL+Q if I wanted to actually shut it down. Can you try this? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
It's a shame there is no way to vote for things here, and instead weight seems given to bugs with a large number of comments / activity. The current version of nautilus, which is the very core of Ubuntu, is broken. Search is not the same as navigation. I do not want to search my files when I know exactly where the file I want is - I want to go to it. There are full time Ubuntu developers. This should not be waiting for a user to contribute a patch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753599] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753599/+attachment/5070259/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070261/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070264/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070265/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070266/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070267/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753599/+attachment/5070268/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753599 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/1753599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
I attached patch from ArchLinux AUR (https://aur.archlinux.org/packages /xorg-server-bug865/, https://aur.archlinux.org/cgit/aur.git/tree /freedesktop-bug-865.patch?h=xorg-server-bug865 ). This patch is stable and reliable. ArchLinux users are happy with it. It fixes current bug on Ubuntu Bionic Beaver 18.04 LTS. I have tested it with keyboard layout switcher on GNOME (DESKTOP_SESSION="ubuntu") and MATE desktop (DESKTOP_SESSION="mate"). Please kindly review it and consider applying it before official final release of 18.04 LTS. I'm ready to test proposed packages which (I hope) you would create. As the result Ubuntu users will be as happy as ArchLinux's users. ** Patch added: "Patch for Bionic Beaver 18.04 LTS, it fixes the problem" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1245473/+attachment/5072326/+files/freedesktop-bug-865.patch -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754172] [NEW] NetworkManager breaks OpenVPN configuration on connection
Public bug reported: A previously working OpenVPN configuration stopped connecting, with nm- openvpn complaining about wrong options: mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8258] audit: op="connection-activate" uuid="e3553582-0f39-404f-bd71-4dc6b92992de" name="Router.Michal" pid=6735 uid=1000 result="success" mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8337] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: Started the VPN service, PID 26187 mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8421] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: Saw the service appear; activating connection mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8611] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN plugin: state changed: starting (3) mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8615] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN connection: (ConnectInteractive) reply received mar 07 22:35:45 michal-laptop nm-openvpn[26190]: Options error: If you use one of --cert or --key, you must use them both mar 07 22:35:45 michal-laptop nm-openvpn[26190]: Use --help for more information. mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8648] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN plugin: failed: connect-failed (1) mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8651] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN plugin: failed: connect-failed (1) mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8658] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN plugin: state changed: stopping (5) mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8660] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN plugin: state changed: stopped (6) mar 07 22:35:45 michal-laptop NetworkManager[3172]: [1520458545.8680] vpn-connection[0x55e59e3be750,e3553582-0f39-404f-bd71-4dc6b92992de,"Router.Michal",0]: VPN service disappeared The config, however, includes correct ca/cert/key stanzas: ca=ca.crt cert=michal.crt key=michal.key The attached screenshot shows a related breakage in the GUI, after making the correct certificate/key file selections, and saving the config, the config file gets broken indeed: ca=ca.crt cert=ca.crt # no key entry at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-openvpn 1.8.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 22:32:57 2018 SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to bionic on 2018-02-07 (28 days ago) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1754172 Title: NetworkManager breaks OpenVPN configuration on connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1754172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754169] [NEW] [Bionic] Nautilus crashes when a file is opened with gedit
Public bug reported: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Summary changed: - Nautilus crashes when a file is being opened with gedit when right-clicking it + [Bionic] Nautilus 3.27.92 crashes when a file is being opened with gedit when right-clicking it ** Summary changed: - [Bionic] Nautilus 3.27.92 crashes when a file is being opened with gedit when right-clicking it + [Bionic] Nautilus 3.27.92 crashes when a file is opened with gedit by right-clicking it ** Description changed: See title. ==Steps to reproduce== - 1) Open nautilus + 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse a location with a textfile (eg. /home/user/.thunderbird 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) - 2) Browse a location with a textfile (eg. /home/user/.thunderbird + 2) Browse a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) - 2) Browse a location with a textfile (eg. /home/user/.thunderbird ) + 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) 3) Right click a textfile (eg. profiles.ini 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) Installatio
[Bug 1754169] Re: [Bionic] Nautilus crashes when a file is opened with gedit
** Description changed: See title. ==Steps to reproduce== 1) Open nautilus (currently 3.26.2 in bionic) 2) Browse to a location with a textfile (eg. /home/user/.thunderbird ) - 3) Right click a textfile (eg. profiles.ini + 3) Right click a textfile (eg. profiles.ini) 4) Choose gedit from the list (probably default), click ok. 5) Nautilus crashes, gedit doesn't come up ==Expected result== Nautilus doesn't crash, gedit comes up and lets you edit the file ==Why (probably) a gedit regression== When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.27.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Mar 7 22:13:00 2018 InstallationDate: Installed on 2018-02-23 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754169 Title: [Bionic] Nautilus crashes when a file is opened with gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754169] Re: [Bionic] Nautilus crashes when a file is opened with gedit
** Summary changed: - [Bionic] Nautilus 3.27.92 crashes when a file is opened with gedit by right-clicking it + [Bionic] Nautilus crashes when a file is opened with gedit ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1754169 Title: [Bionic] Nautilus crashes when a file is opened with gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753843] Re: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1551406 *** https://bugs.launchpad.net/bugs/1551406 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 #1551406, 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/1753843/+attachment/5071092/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071094/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071098/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071099/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071100/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071101/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753843/+attachment/5071102/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1551406 ** 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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1753843 Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1753843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
It is not a Gnome issue, it is an Ubuntu issue: https://bugzilla.gnome.org/show_bug.cgi?id=794159#c1 -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753571] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753571/+attachment/5070174/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070176/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070180/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070181/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070182/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070183/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753571/+attachment/5070184/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753571 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
@adpsimpson-gmail there is already #181: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753537] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753537/+attachment/5070077/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070079/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070082/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070083/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070084/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070085/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753537/+attachment/5070086/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753537 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/1753537/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754050] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1754050/+attachment/5071743/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071745/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071748/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071749/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071750/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071751/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754050/+attachment/5071752/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1754050 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/1754050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753024] Re: gjs-console crashed with SIGSEGV in JS_GetContextPrivate()
*** This bug is a duplicate of bug 1751194 *** https://bugs.launchpad.net/bugs/1751194 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 #1751194, 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/1753024/+attachment/5067609/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067611/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067614/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067615/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067616/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067617/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753024/+attachment/5067618/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1751194 ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1753024 Title: gjs-console crashed with SIGSEGV in JS_GetContextPrivate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1753024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753529] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753529/+attachment/5070053/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070055/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070059/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070060/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070061/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070062/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753529/+attachment/5070063/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753529 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/1753529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753014] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753014/+attachment/5067562/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067564/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067568/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067569/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067570/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067571/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753014/+attachment/5067572/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753014 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753014/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753131] Re: gnome-shell crashes occasionally (libmutter)
Thanks, I've applied the workaround. My /var/crash is currently empty, I'll follow your advice when the crash occurs again. -- 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/1753131 Title: gnome-shell crashes occasionally (libmutter) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754024] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1741119 *** https://bugs.launchpad.net/bugs/1741119 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 #1741119, 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/1754024/+attachment/5071652/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071654/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071657/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071658/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071659/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071660/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754024/+attachment/5071661/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1741119 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1754024 Title: gnome-software crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753658] Re: Xorg crash
Went to the other bug and saw it is already public now. -- 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/1753658 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753658/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] [NEW] Rhythmbox stays running in the background after quit
Public bug reported: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753075] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753075/+attachment/5067963/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067965/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067968/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067969/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067970/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067971/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753075/+attachment/5067972/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753075 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/1753075/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
Here is the link: https://bugzilla.gnome.org/show_bug.cgi?id=794159 However, is it really a Gnome bug? After all, after I installed ubuntu- gnome-desktop it was ok. Sounds, like the missing ubuntu-gnome-desktop did it, didn't it? ** Bug watch added: GNOME Bug Tracker #794159 https://bugzilla.gnome.org/show_bug.cgi?id=794159 -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753672] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1753672/+attachment/5070489/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070491/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070495/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070496/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070497/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070498/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753672/+attachment/5070499/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1753672 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/1753672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753912] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** 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/1753912/+attachment/5071272/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071274/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071277/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071278/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071279/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071280/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753912/+attachment/5071281/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724439 gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753912 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/1753912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753913] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1505409, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1753913/+attachment/5071282/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071284/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071287/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071288/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071289/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071290/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1753913/+attachment/5071291/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1753913 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
> Oh I see why: most of us cannot change back the status of the bug once it has been changed to "fix released" (which is stupid, too). If that is genuinely the reason (and this bug has been marked as "Fix Released" since Jan 2014, so it seems correct), then is it not time to raise a new bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754069] Re: bug 1164016 has regressed
> 'Released' is a dev decision, not a user one. Then why am I allowed to change the status TO "fix released"?? Anyway, regarding the issue. > What you request is an upstream design choice, which we possibly get with > 3.28. > So nothing can be made on old releases as they only get 'security' fix and > backport sometimes. What the fuck are you talking about? The upstream design decision (to have type-ahead do a full search within all subfolder instead of just a selection in the current tab) was already correctly deemed to be idiotic by Ubuntu, and some patch was applied so that, in Ubuntu, we would have the sane behavior instead of the idiotic one decided upstream. You simply need to do that again in the new version of Ubuntu (on, I guess, a newer version of Nautilus). -- 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/1754069 Title: bug 1164016 has regressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754069] Re: bug 1164016 has regressed
(and as usual I can't even edit my own comments, so here comes an additional comment to correct a typo): > stupidity that the upstream developer have demonstrated *developerS -- 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/1754069 Title: bug 1164016 has regressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754069] Re: bug 1164016 has regressed
But actually I wonder why Ubuntu still keeps Nautilus as the file explorer, given the level of stupidity that the upstream developer have demonstrated. In the last year, I have seen nothing but completely retarded design decision and regressions that degrade usability beyond the unthinkable, and not a simple improvement. Is shitty Nautilus really the best that there is available? -- 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/1754069 Title: bug 1164016 has regressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754056] Re: assign shutdown command to sleep button fails 17.10 and 18.04
- added package gnome-settings-daemon - I should mention that I tried to figure out the key-code by using XEV, but it does not work ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1754056 Title: assign shutdown command to sleep button fails 17.10 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1754056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754077] Re: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
It happens is LTS 16.04.1 -- 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/1754077 Title: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754069] Re: bug 1164016 has regressed
'Released' is a dev decision, not a user one. What you request is an upstream design choice, which we possibly get with 3.28. So nothing can be made on old releases as they only get 'security' fix and backport sometimes. https://bugzilla.gnome.org/show_bug.cgi?id=681871#c58 ** Bug watch added: GNOME Bug Tracker #681871 https://bugzilla.gnome.org/show_bug.cgi?id=681871 ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- 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/1754069 Title: bug 1164016 has regressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754056] [NEW] assign shutdown command to sleep button fails 17.10 and 18.04
You have been subscribed to a public bug: Hi, I'm running a GigaByte Brix with a wireless Logitech K400 Keyboard. The said keyboard features a "power off" button that is interpreted by Ubuntu as "Sleep" for some reason. On the 17.04 release it was possible to simply assign the shutdown command to this button and everything was fine. With 17.10 and 18.04 LTS (beta) the behaviour of this button can not be changed. If I try to assign my shutdown command and press the button, my system immediately enters suspend mode. Even if I try to simply read out the key code of the button it will directly go to suspend. Will there be a way of getting back the behaviour of 17.04 so that I can freely choose what this button does? Thanks! ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- assign shutdown command to sleep button fails 17.10 and 18.04 https://bugs.launchpad.net/bugs/1754056 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754077] [NEW] (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
Public bug reported: Some times gnomeshell just gets stuck and crashes. I keep sending the bug reports automatically with the tool, and updating the system, but the issue is still there. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1754077 Title: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754069] [NEW] bug 1164016 has regressed
Public bug reported: I'm opening this because I can't change back the status of issue 1164016 back from "fix released" (which is so stupid by the way: IF I can change the status from any other status, why shouldn't I be able to change it from "fix released"? Nonsense) https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016 Many users have reported the bug is back on 17.10. I can't think of any reason why it should take more than a few minutes to fix it back for 17.10, other than maybe nobody among the people who were responsible for the fix have noticed yet. Feel free to mark this as duplicate *after* you reopen #1164016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 7 16:29:37 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1607 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages xenial ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1754069 Title: bug 1164016 has regressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
@109 this is already known to be the wrong behavior. It was introduced long ago by the hopelessly stupid Nautilus people, and patched by Ubuntu to reestablish the old sensible behavior, but something must have gone wrong in the latest release and so the idiocy has resurfaced. What I don't understand is how it can be taking so long to fix again. Oh I see why: most of us cannot change back the status of the bug once it has been changed to "fix released" (which is stupid, too). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754058] [NEW] blinking background in gnome-terminal
Public bug reported: blinking background in gnome-terminal in Ubuntu 18.04 alpha. Package: gnome-terminal Version: 3.27.92-1ubuntu1 # Reproduction 1. Place the application after gnome-terminal 2. unfocusing gnome-terminal A. Application window focus change B. Stop mouse. I regret that I do not know how to reproduce it. It seems that it does not appear in the display capture # workaround Preferences > Profile 「システムテーマから透過を使用する」 unchecked. (Disable background transparent) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "blinking gnome-terminal background when window focus change" https://bugs.launchpad.net/bugs/1754058/+attachment/5071786/+files/vokoscreen-2018-03-07_23-37-10.mkv -- 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/1754058 Title: blinking background in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1754058/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753741] Re: /usr/lib/gvfs/gvfsd-google:11:on_show_processes_reply:g_task_return_now:g_task_return:g_task_return_new_error:show_processes_reply
** Changed in: gvfs Status: Incomplete => Confirmed -- 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/1753741 Title: /usr/lib/gvfs/gvfsd- google:11:on_show_processes_reply:g_task_return_now:g_task_return:g_task_return_new_error:show_processes_reply To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1753741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565359] Re: high cpu usage when idle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1565359 Title: high cpu usage when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1565359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722779] Re: Xorg session exits on login if nvidia modeset=1
*** This bug is a duplicate of bug 1752083 *** https://bugs.launchpad.net/bugs/1752083 ** This bug has been marked a duplicate of bug 1752083 Name "org.gnome.Mutter.DisplayConfig" does not exist -- 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/1722779 Title: Xorg session exits on login if nvidia modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1722779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750969] Re: gnome-disks (11) udisks_partition_table_get_type_ → finish_cb → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist
** Changed in: gnome-disk-utility Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1750969 Title: gnome-disks (11) udisks_partition_table_get_type_ → finish_cb → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1750969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752882] Re: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable
This bug was fixed in the package systemd - 237-3ubuntu4 --- systemd (237-3ubuntu4) bionic; urgency=medium * systemd-sysv-install: fix name initialisation. Only initialise NAME, after --root optional argument has been parsed, otherwise NAME is initialized to e.g. `enable', instead of to the `unit-name`, resulting in failures. (LP: #1752882) -- Dimitri John Ledkov Mon, 05 Mar 2018 09:57:58 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752882 Title: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753998] [NEW] Characters Snap shouldn't need 'home' plug
Public bug reported: The GNOME Characters snap adds the 'home' plug. I don't think the app needs access to files in the home directory, so please try removing this permission. ** Affects: gnome-characters (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1753998 Title: Characters Snap shouldn't need 'home' plug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1753998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Any further progress on these issues? -- 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/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
The old behaviour was one of the power features of Nautilus for a person that uses keyboard navigation. The new behaviour is dramatically different and frankly doesn't work as well for many use cases. Lets say I want to quickly navigate to ~/code/myproject/module/__init__.py. 1. I switch to Nautilus which shows my home folder A. With the old behaviour: c ENTER m ENTER m ENTER __i ENTER B. With the new behaviour: __init__.py, and it shows me tons of __init__.py located in my home folder and all subdirectories 2. Trying to use the new behaviour and still achieve my goal I try this: i) module/__init__.py, no hit ii) module __init__.py, no hit So, currently I see no way of navigating to the intended file without alot of hassle or reaching for the mouse. A big regression for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
The old behaviour was one of the power features of Nautilus for a person that uses keyboard navigation. The new behaviour is dramatically different and frankly doesn't work as well for many use cases. Lets say I want to quickly navigate to ~/code/myproject/module/__init__.py. 1. I switch to Nautilus which shows my home folder A. With the old behaviour: c ENTER m ENTER m ENTER __i ENTER B. With the new behaviour: __init__.py, and it shows me tons of __init__.py located in my home folder and all subdirectories 2. Trying to use the new behaviour and still achieve my goal I try this: i) module/__init__.py, no hit ii) module __init__.py, no hit So, currently I see no way of navigating to the intended file without alot of hassle or reaching for the mouse. A big regression for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743976] Re: gnome-shell is wasting CPU repainting unchanging panels
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1743976 Title: gnome-shell is wasting CPU repainting unchanging panels To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1743976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
You can use that url directly https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-control-center -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
** Description changed: - https://gitlab.gnome.org/GNOME/mutter/issues/55 - - --- - es2gears_wayland sticks to 119 FPS on a 59.95Hz display $ es2gears_wayland EGL_VERSION = 1.4 (DRI2) vertex shader info: fragment shader info: info: 597 frames in 5.0 seconds = 119.138 FPS 600 frames in 5.0 seconds = 119.880 FPS 598 frames in 5.0 seconds = 119.481 FPS 600 frames in 5.0 seconds = 119.952 FPS 600 frames in 5.0 seconds = 119.880 FPS 600 frames in 5.0 seconds = 119.880 FPS 596 frames in 5.0 seconds = 119.105 FPS $ es2gears_x11 EGL_VERSION = 1.4 (DRI2) vertex shader info: fragment shader info: info: 315 frames in 5.0 seconds = 62.837 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 300 frames in 5.0 seconds = 60.000 FPS 301 frames in 5.0 seconds = 60.008 FPS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mesa-utils-extra 8.4.0-1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Mar 6 16:39:18 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller [8086:041a] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller [17aa:30a1] InstallationDate: Installed on 2017-12-12 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=f9fe7460-9c41-4d4a-8376-e5ceb57bbec8 ro quiet splash vt.handoff=1 SourcePackage: mesa-demos UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070502/+files/BootLog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070503/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070504/+files/Dependencies.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070505/+files/DpkgLog.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070506/+files/JournalErrors.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070507/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070508/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070509/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070510/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070511/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+attachment/5070512/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/mesa-demos/+bug/1753677/+att
[Bug 1753776] Re: Graphics corruption in login animation to Xorg sessions
That's probably irrelevant. intel-microcode is a firmware update for your CPU (sometimes you will see kernel log messages telling you it's needed). But this bug occurred without any change in the 'intel-microcode' package so I think it's irrelevant here. -- 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/1753776 Title: Graphics corruption in login animation to Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753861] Re: Renaming file in password protected archive results in file being deleted from the archive
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: file-roller (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1753861 Title: Renaming file in password protected archive results in file being deleted from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1753861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
** Changed in: mesa Status: Unknown => Confirmed ** Changed in: mesa Importance: Unknown => Medium -- 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/1753677 Title: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1753677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753776] Re: Graphics corruption in login animation to Xorg sessions
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Confirmed ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Invalid => Confirmed -- 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/1753776 Title: Graphics corruption in login animation to Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
New upstream: https://bugs.freedesktop.org/show_bug.cgi?id=105376 ** Bug watch added: freedesktop.org Bugzilla #105376 https://bugs.freedesktop.org/show_bug.cgi?id=105376 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=105376 Importance: Unknown Status: Unknown ** Changed in: mesa-demos (Ubuntu) Status: New => Confirmed -- 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/1753677 Title: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1753677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753776] Re: Graphics corruption in login animation to Xorg sessions
I don't have intel-microcode installed, should I install it? May I add some log to help? thanks corrado@corrado-p7-bb-0305:~$ apt policy intel-microcode intel-microcode: Installed: (none) Candidate: 3.20180108.1+really20171117.1 Version table: 3.20180108.1+really20171117.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages corrado@corrado-p7-bb-0305:~$ -- 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/1753776 Title: Graphics corruption in login animation to Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
