[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
** Description changed: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an unused Intel GPU). WORKAROUNDS (you only need one): * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf * Disable integrated graphics/GPU in your BIOS * Add

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with

[Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile

2019-06-19 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556439 Title: pulseaudio crashed with SIGA

[Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-06-19 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663528 Title: pulseaudio assert failure: pulseau

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
Oops. It appears upstream already fixed this bug. And we removed their fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you revert that revert then the bug is fixed. ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gdm3 (Ubu

[Bug 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

2019-06-18 Thread Daniel van Vugt
It looks like commit 4762aa45d9ea2f5146a135eda6b840bf3964b317 is the fix here. Not sure. It's not in any official PulseAudio release yet. ** Description changed: + https://errors.ubuntu.com/problem/7c4e21254b37e5f76989d357fb6cea8b0784b14c +

[Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile

2019-06-18 Thread Daniel van Vugt
It looks like commit 59d264ac56d644f626251daa44ef7b39a9a9fe03 was the fix for this. ** Bug watch added: freedesktop.org Bugzilla #103752 https://bugs.freedesktop.org/show_bug.cgi?id=103752 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=103752 Importance:

[Bug 1833349] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:setup_transport_and_stream

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from

[Bug 1760729] Re: pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from setup_transport_and_stream() [bluez]

2019-06-18 Thread Daniel van Vugt
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760729 Title: pulseaudio crashed during playback with SIGABRT in set_nonblock() from

[Bug 1833350] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:source_process_msg

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from

[Bug 1833351] Re: /usr/bin/pulseaudio:6:set_nonblock:pa_make_fd_nonblock:setup_stream:setup_stream:sink_process_msg

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1760729 *** https://bugs.launchpad.net/bugs/1760729 ** This bug has been marked a duplicate of bug 1760729 pulseaudio crashed during playback with SIGABRT in set_nonblock() from pa_make_fd_nonblock() from setup_stream() [bluez] from

[Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile

2019-06-18 Thread Daniel van Vugt
No crashes since we upgraded to PulseAudio 12, which means no crashes in Ubuntu 18.10 onward. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu

[Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-06-18 Thread Daniel van Vugt
** Description changed: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 + https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it

[Bug 1833344] Re: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: asserzione \"mixer\" non riuscita.

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 ** This bug has been marked a duplicate of bug 1663528 pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. -- You received this bug

[Bug 1833343] Re: /usr/bin/pulseaudio:pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertiva \342\200\234mixer\342\200\235 falhou.

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1663528 *** https://bugs.launchpad.net/bugs/1663528 ** This bug has been marked a duplicate of bug 1663528 pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. -- You received this bug

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Card archived: https://trello.com/c/gn0J5Qgb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Thanks Pat. That seems to confirm the 'regression-update' tag here. Although I wouldn't be able to debug and fix the mutter change because I can't reproduce the bug, using VMware. Mine just works :/ It sounds like good progress is being made in the kernel anyway. So I think a fix there would be

[Bug 1833045] Re: Ubuntu on Wayland login option is missing on random boots in VMware

2019-06-18 Thread Daniel van Vugt
This bug _only_ affects bionic. But I am happy to say "Won't Fix". ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu

[Bug 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.

2019-06-18 Thread Daniel van Vugt
The information we have here is based on what you said in comment #3: When I press on the keyboard then a = a s= s d = refresh Can you elaborate on that? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of

[Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height

2019-06-18 Thread Daniel van Vugt
That's a Launchpad bug. Nothing is fixed. The bug was rejected and closed, which Launchpad misinterprets as "Fix Released": https://gitlab.gnome.org/GNOME/gnome-shell/issues/1332 ** No longer affects: gnome-shell -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2019-06-18 Thread Daniel van Vugt
This looks like a common crash in 18.04. Not hugely common, but I don't think we could say no. I just don't know when/if such an update to 18.04 will get done. ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Bionic)

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1788428, so it is being marked as such. Please

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 ** This bug is no longer a duplicate of bug 1833098 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 Which is presently a duplicate of bug 1788429... ** This bug has been marked a duplicate of bug 1788429 gnome-shell crashed with SIGSEGV in g_file_get_parent → _st_theme_resolve_url →

[Bug 1833324] Re: /usr/bin/gnome-shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1762235 *** https://bugs.launchpad.net/bugs/1762235 ** This bug has been marked a duplicate of bug 1762235 gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() -- You received this bug notification

[Bug 1762235] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy()

2019-06-18 Thread Daniel van Vugt
Tracking in: https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 ** Description changed: - - + https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5

[Bug 1833265] Re: computer takes ages to start

2019-06-18 Thread Daniel van Vugt
The main problem I can see here is that your kernel graphics driver keeps crashing, which always starts with: [ 66.888620] vblank wait timed out on crtc 1 ** Summary changed: - laptop reported that there is a problem + computer takes ages to start ** Package changed: xorg (Ubuntu) => linux

[Bug 1833263] Re: /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument

2019-06-18 Thread Daniel van Vugt
This doesn't seem to be exactly the same issue as bug 1762235 so they should probably be separate for now. ** This bug is no longer a duplicate of bug 1762235 gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy() ** Summary changed: -

[Bug 213149] Re: pulseaudio breaks on switching from tty7 to tty [1-6] (in and out of Gnome)

2019-06-18 Thread Daniel van Vugt
This bug is closed. I suggest if there is any problem you want fixed in current or future Ubuntu releases then please create a fresh bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1717453]

2019-06-18 Thread Daniel van Vugt
In progress: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717453 Title: Shell menus (panel, dock, window) font size does not match

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-18 Thread Daniel van Vugt
3 (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with

[Bug 1833189] Re: drivers are installed but not working

2019-06-18 Thread Daniel van Vugt
It appears the kernel (or the modeset driver) can't detect your monitor's EDID via the VGA cable. And an EDID is required to know the supported resolution. Without it you will be stuck in 1024x768. Please try a different VGA cable, or simply unplugging and replugging it. If you still have a

[Bug 1832943] Re: Ghost of an app window (like Firefox) is visible in the AO search background

2019-06-17 Thread Daniel van Vugt
** Summary changed: - When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background + Ghost of an app window (like Firefox) is visible in the AO search background ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Tags added: visual-quality **

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-17 Thread Daniel van Vugt
** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() + gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_paint_equal() **

[Bug 1350410] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from atk_object_notify_state_change()

2019-06-17 Thread Daniel van Vugt
** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() + gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from atk_object_notify_state_change() ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1833098 *** https://bugs.launchpad.net/bugs/1833098 Thanks. We can track this in bug 1833098 now. ** This bug has been marked a duplicate of private bug 1833098 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-17 Thread Daniel van Vugt
Yes it makes sense if the shell crashes then very likely you have no Xorg server to run xrandr against :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722886 Title: Include logs, monitors.xml and

[Bug 1825727] Re: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_css_gadget_set_state() from gtk_switch_state_flags_changed()

2019-06-17 Thread Daniel van Vugt
** Description changed: + https://errors.ubuntu.com/problem/b9099237efc0ed3a713ac34e260c33a215c4599d + Crashes when updating extensions using gnome-tweaks on Gnome 3.32+ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1

[Bug 1833058] Re: /usr/bin/gnome-shell-extension-prefs:11:gtk_css_gadget_set_state:gtk_switch_state_flags_changed:g_cclosure_marshal_VOID__UINTv:_g_closure_invoke_va:g_signal_emit_valist

2019-06-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1825727 *** https://bugs.launchpad.net/bugs/1825727 ** This bug has been marked a duplicate of private bug 1825727 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-17 Thread Daniel van Vugt
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Changed in: mutter (Ubuntu) Importance: Undecided =

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
Thanks. Unfortunately that page is showing an unreadable stack trace. It also says that the gnome-shell binary file has changed (update installed) since the crash occurred so it can't be retraced/reported. Please reproduce the crash again and repeat the steps from comment #2. -- You received

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832856 Title: Gnome-shell crashes frequently in gnome-

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The status for mutter will remain incomplete till someone tries the suggestion from comment #31. Sorry, I still can't reproduce this bug myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138

[Bug 1833045] [NEW] Ubuntu on Wayland login option is missing on random boots in VMware

2019-06-17 Thread Daniel van Vugt
Public bug reported: Ubuntu on Wayland login option is missing on random boots in VMware. This seems to be a persistent problem with Ubuntu 18.04, but seems to have been fixed at least in 19.04. In 18.04 where the bug does exist, upgrading the kernel to 5.1 doesn't seem to help. This looks and

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The problem I mentioned in comment #15 is now logged as bug 1833045. It's clearly different to this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on

[Bug 48734] Re: Home permissions too open

2019-06-17 Thread Daniel van Vugt
** Changed in: ubuntu-rtm Status: New => Won't Fix ** Changed in: ubuntu-rtm Status: Won't Fix => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/48734 Title: Home

[Bug 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size

2019-06-17 Thread Daniel van Vugt
Fix in progress: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717453 Title: Shell menus (panel, dock, window) font size does not

[Bug 1832946] Re: Gnome Shell performance decreases as the number of running apps increases

2019-06-17 Thread Daniel van Vugt
Note that not all performance improvements will ever make it into Ubuntu 18.04. If you want higher performance right now then please use Ubuntu 19.04 instead. And Ubuntu 19.10 will be even faster (_after_ it gets mutter 3.33.3 or later). Do you find that Ubuntu 19.04 has this same bug? **

[Bug 1826516] Re: bluetooh mouse lag when use bluetooth hedphones

2019-06-16 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826516 Title:

[Bug 1751144] Re: xorg

2019-06-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively"

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
The attached RfKill.txt seems to suggest that Bluetooth is only turned off in software. So maybe this is just a gnome-shell GUI bug, or gnome- bluetooth. To confirm this, please try turning it on by running this command in a terminal: rfkill unblock 0 ** Also affects: gnome-shell (Ubuntu)

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
If the above command doesn't work then I would next focus on a possible kernel problem in: [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) ** Summary changed: - Bluetooth not working + Intel 8260 Bluetooth

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Daniel van Vugt
Pat, Re comment #19, your crash (hang) reports there seem to show the gnome- shell process behaving normally (in poll) and not stuck at all. That doesn't tell us much but it would support the theory in comment #31. ** Summary changed: - Login screen never appears on vmwgfx but installing kernel

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it

2019-06-16 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Eoan) Status: New => Invalid ** Changed in: mutter (Ubuntu Bionic) Status: New => Incomplete ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-16 Thread Daniel van Vugt
Indeed there was a kernel update to 18.04 around the same time as the mutter update which I thought was causing this bug. ** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Bionic) ** No longer affects: mutter (Ubuntu Eoan) ** Also affects: linux (Ubuntu Eoan)

[Bug 1832959] Re: Wrong cursor size after screensaver

2019-06-16 Thread Daniel van Vugt
** Tags added: cursor hidpi ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Wrong cursor size after screensaver + [hidpi] Cursor is too small after screensaver ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received

[Bug 1832943] Re: When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background

2019-06-16 Thread Daniel van Vugt
Can you please reword that? I don't understand (and can't see in the video) what the problem is here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1832946] Re: Gnome Shell works the worst after I will launch some apps

2019-06-16 Thread Daniel van Vugt
It sounds like you're trying to describe general frame skipping and performance degradation as more apps are opened. Can you please put the problem into words so we can be sure what the problem is you are reporting? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags

[Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1800196 *** https://bugs.launchpad.net/bugs/1800196 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1800196, so it is being marked as such. Please

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
It appears this crash is in: /home/gjm/.local/share/gnome- shell/extensions/wsmat...@martin.zurowietz.de which is not part of Ubuntu, so we can't handle it here. Sorry. I suggest you uninstall that extension to avoid the crash. ** Summary changed: - Gnome-shell crashes frequently +

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows →

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-16 Thread Daniel van Vugt
Thanks. Since gnome-shell provides all the graphics (even the lock screen), this bug is now assigned to gnome-shell only. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** No longer affects: gdm3 (Ubuntu) --

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Summary changed: - gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows meta_workspace_list_windows + gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() -- You received this

[Bug 1753884] Re: session logout after suspend

2019-06-16 Thread Daniel van Vugt
Unfortunately we can't backport a fix which we don't know the location of. And I don't see any links to a patch here. Also, we generally don't support/patch gnome-shell on Ubuntu releases older than 18.04. Anyway, this bug is closed and we can't be sure you are experiencing the exact same issue.

[Bug 1759008] Re: Revert automatic suspend by default for bionic?

2019-06-16 Thread Daniel van Vugt
This bug is closed. If you have any issues at all then please open a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? To manage

[Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zwp_relative_point

2019-06-16 Thread Daniel van Vugt
** Tags removed: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746656 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-16 Thread Daniel van Vugt
I'm not sure monitors.xml is any more useful than the xrandr output we already get... unless xrandr output is missing from crash bugs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722886 Title:

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
Looking at hungboot.txt I am starting to think maybe the login screen ('gnome-shell' process) is actually running in Wayland mode but failing to display. That would explain a lot... Pat, can you please reproduce the bug again and while it is happening: 1. SSH into the VM. 2. Run 'pidof

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
I have been trying to reproduce this bug in VMware but have not been able to. Ubuntu 18.04 always starts up with a login screen successfully for me. What it does not do successfully is offer the "Ubuntu on Wayland" option most of the time. So I expect that's the same root cause as this bug.

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
Jussi, That sounds like maybe a different bug. Although "commenting out the Wayland" is also not what you need to do. You need to change: #WaylandEnable=false to: WaylandEnable=false If that doesn't fix the problem for you then you have a different bug. In that case please open a new bug

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Are you able to make another video without Firefox running? ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Also, before locking the screen please open a Terminal window and run 'top' then take a screenshot of the window and attach it to this bug. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this

[Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 > Shell works slowly with efforts also without Firefox launching. Yes, we know. But that's not an exact bug as much as an observation that performance is poor. For the type of issues you describe I have

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but setting

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Also, does the bug still occur if you close Firefox before locking the screen? If not then this may be related to bug 1832816. ** Summary changed: - Ubuntu 19.10 (alpha) lockscreen freezes + Locking and unlocking the screen is slow and stuttery ** Tags added: performance -- You received this

[Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 ** Summary changed: - Ubuntu 19.10 Gnome Desktop works with freezes and efforts + Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube -- You received this bug notification because

[Bug 1832816] Re: Ubuntu 19.10 Gnome Desktop works with freezes and efforts

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 It appears the problem is probably that your web browser is using all the CPU power to display YouTube's auto-playing front page. Because our web browsers don't support hardware video decoding (LP:

[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-06-14 Thread Daniel van Vugt
The bug is marked as "fix released" so as far as we know the issue is closed. If you still experience problems then please open a new bug by running: ubuntu-bug gnome-shell and mention that it seems to be related to bug 1812266. -- You received this bug notification because you are a member

[Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes

2019-06-14 Thread Daniel van Vugt
Also, does the bug still occur if you disable this? AutomaticLoginEnable=true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Ubuntu 19.10 (alpha) lockscreen freezes To manage

[Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes

2019-06-14 Thread Daniel van Vugt
Can you confirm you are not using any gnome-shell extensions? ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Nvidia 430.26 behaves a bit differently. It just fails to start as non- root and gives reasons: [ 897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) ... [ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 897.470] (EE)

[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling

2019-06-13 Thread Daniel van Vugt
** Tags added: hidpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831161 Title: App-switcher icons too small with hidpi monitor and 1.25 scaling To manage notifications about this bug go to:

[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-13 Thread Daniel van Vugt
** Tags added: hidpi ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1370 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370 Importance: Unknown Status: Unknown -- You

[Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)

2019-06-13 Thread Daniel van Vugt
Also, just a reminder: If anyone is using a multi-GPU desktop machine then please see bug 1705369 instead. ** Summary changed: - Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) + Ubuntu login screen sometimes doesn't appear on a single

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
Two years later... I am reviewing this bug again today. I can confirm it's still in Ubuntu 19.10. And I can confirm that comment #19 was right. See comment #19. ** Summary changed: - Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) + Ubuntu boots to blank

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
-black +blank Because on Ubuntu 19.10 it's purple. Still the same bug though. ** Summary changed: - Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) + Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) ** Tags

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
Comment #116 appears to be linking to the wrong bug. That link is for nvidia-drm.modeset=1 and this bug is specifically about when you don't have that set, like the default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
** No longer affects: gdm3 (Debian) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Not yet. I am just untangling more Nvidia bugs today. Also, I forgot to mention that you CAN run Xorg+Nvidia and see your monitors as non-root. But only after you have started and stopped Xorg as root beforehand. Something gets remembered, maybe in $HOME somewhere? -- You received this bug

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-06-13 Thread Daniel van Vugt
In a more pure development environment, I can confirm this bug without needing hybrid GPUs, or gdm3. Just the Nvidia driver and Xorg results in no outputs/monitors detected: $ xrandr Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384 To work around the problem I need to run Xorg

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
Also, it sounds like the root cause here is the same as bug 1769857. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
For a full list of reasons to not use nvidia-drm.modeset=1 right now, please see: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

2019-06-13 Thread Daniel van Vugt
Sounds like the root cause here is the same as bug 1716857. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not

[Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 even though WaylandEnable=false is set

2019-06-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1716857 *** https://bugs.launchpad.net/bugs/1716857 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1716857, so it is being marked as such. Please

[Bug 1800465] Re: Vulkan error when using NVIDIA-Prime

2019-06-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1769857 *** https://bugs.launchpad.net/bugs/1769857 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769857, so it is being marked as such. Please

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-06-13 Thread Daniel van Vugt
** Tags added: nvidia-drm.modeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
It appears this crash is not very common, suggesting it might be related to some extension(s). You seem to have installed: 'weatherinthecl...@jasonlg1979.github.io' 'gpa...@gnome-shell-extensions.gnome.org' 'sound-output-device-choo...@kgshank.net' so please try uninstalling those completely,

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
The attached file JournalErrors.txt suggests the GPaste extension might be the most suspicious extension: яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 == яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837e650 I

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
Yes, that does seem to be the problem, most likely. The only calls to 'get_child_meta' in gnome-shell are in environment.js, which seems to be called from the GPaste extension per the above comment. I recommend uninstalling the GPaste extension. -- You received this bug notification because you

  1   2   3   4   5   6   7   8   9   10   >