[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
Upstream is against changing mutter for this, so "Won't Fix" to mutter. But the fix for gdm3 has landed and that's enough to resolve the bug. ** Changed in: gdm3 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Status: In Progress => Won't Fix -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833899] nautilus crashed with SIGSEGV
Stacktrace: No stack. StacktraceSource: StacktraceTop: ThreadStacktrace: ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1833899 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833899] [NEW] nautilus crashed with SIGSEGV
Public bug reported: just logged in. no apps started. corrado@corrado-HP-p4-ee-0618:~$ inxi -Fx System:Host: corrado-HP-p4-ee-0618 Kernel: 5.0.0-17-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 11.3 Wh condition: 19.9/19.5 Wh (102%) model: 13-42 OA03031 status: Discharging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 898 2: 898 3: 898 4: 898 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.5 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.0.0-17-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 6.89 GiB (1.5%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 6.88 GiB (22.0%) fs: ext4 dev: /dev/sda4 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 30.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 207 Uptime: 7m Memory: 3.78 GiB used: 1.01 GiB (26.7%) Init: systemd runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.34 corrado@corrado-HP-p4-ee-0618:~$ ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 23 20:57:41 2019 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-06-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190618) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash eoan need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1833899 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Being duped here with a more specific bug, i.e 19.10 optimus hardware No login to ubuntu session possible with gdm, lightdm is ok Maybe a few comments. This bug orig. suggests that one could actually login on optimus hardware with nvidia-drm.modeset=1 thru gdm. That was once the case, it no longer is in 19.10. The only session available is a wayland one because it falls back to Intel. As far as why users set nvidia-drm.modeset=1? I'd suggest the majority do so on optimus machines to be able to use nvidia without tearing. For the most part none have any interest in wayland even though wayland would solve tearing. Why?, because no (or virtually none) optimus machine has ever been able to use wayland & nvidia drivers. Not in the last couple of years, not now. While I don't have a desktop machine I do have a laptop with nvidia GPU only. In that case (19.04) with nvidia-drm.modeset=1 it presents and logs into a wayland session but llvmpipe only. It does work ok in a ubuntu session. Maybe I'll give it a try with 19.10 though on this machine there is no tearing so xorg is fine, currently any positives, if any, of wayland are outweighed by it's negatives. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832693] Re: System auto suspend again during resuming
My workaround prints gsd-power[3124]: temporary_unidle_done_cb is trying to do inhibited job ** Attachment added: "workaround.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272635/+files/workaround.log -- 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/1832693 Title: System auto suspend again during resuming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832693] Re: System auto suspend again during resuming
** Attachment added: "workaround.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272634/+files/workaround.log -- 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/1832693 Title: System auto suspend again during resuming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832693] Re: System auto suspend again during resuming
@Sebastien Thank you for your response. It is "Ubuntu 18.04.2". I've found the root cause of this problem last week. In plugins/power /gsd-power-manager.c, handle_wake_up_screen enables temporary_unidle_done_cb to run after 15 seconds before system enters suspend. In most cases, temporary_unidle_done_cb will be removed by idle_became_active_cb right after resuming so it won't cause any trouble. In my case, after resuming, somehow temporary_unidle_done_cb is triggered before idle_became_active_cb meanwhile previous_idle_mode is still sleep mode, so it calls idle_set_mode to sleep again although has been inhibited. I've tried to put a workaround, letting temporary_unidle_done_cb to check if inhibit_suspend_taken to be true and not to execute idle_set_mode. It does solve this problem but seems not the right way to fix it. I added some wrapper to log the caller, hope it is easy to understand. ** Attachment added: "faillog7.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272633/+files/faillog7.log -- 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/1832693 Title: System auto suspend again during resuming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833832] Re: NVIDIA kernel module fails with KMS on optimus hardware
*** This bug is a duplicate of bug 1716857 *** https://bugs.launchpad.net/bugs/1716857 The errors in the attached journal log show this is the same as what I recently described in: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418/+bug/1716857/comments/36 ** This bug has been marked a duplicate of bug 1716857 nvidia-drm.modeset=1 results in no monitors detected by Xorg -- 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/1833832 Title: NVIDIA kernel module fails with KMS on optimus hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency)
** Tags added: disco -- 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/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833508] Re: the system woke up and has not proper desktop image
If you are using Nvidia then this is bug 1809407. Also... 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 1833508 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. -- 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/1833508 Title: the system woke up and has not proper desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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()
Yes that theming.js around like 479 (on bionic) looks like a candidate
for calling the offending `meta_workspace_list_windows`:
_dockIsNear: function() {
if (this._dockActor.has_style_pseudo_class('overview'))
return false;
/* Get all the windows in the active workspace that are in the primary
monitor and visible */
let activeWorkspace = global.screen.get_active_workspace();
let dash = this._dash;
let windows =
activeWorkspace.list_windows().filter(function(metaWindow) {
return metaWindow.get_monitor() === dash._monitorIndex &&
metaWindow.showing_on_its_workspace() &&
metaWindow.get_window_type() != Meta.WindowType.DESKTOP;
});
--
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/1832869
Title:
gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
meta_display_list_windows → meta_workspace_list_windows →
ffi_call_SYSV → ffi_call()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
*** This bug is a duplicate of bug 1831161 *** https://bugs.launchpad.net/bugs/1831161 ** This bug has been marked a duplicate of bug 1831161 App-switcher icons too small with hidpi monitor and 1.25 scaling -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832436] Re: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) ** No longer affects: ubuntu -- 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/1832436 Title: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822515] Re: Touchscreen input doesn't rotate with the screen
It's true that commit f9d6627fe03f68a132501a488f73e08080018115 is released in mutter version 3.32.2 already. Which is also fix released in eoan already. ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/581 Importance: Unknown Status: Unknown -- 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/1822515 Title: Touchscreen input doesn't rotate with the screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1822515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831144] Re: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #865 https://gitlab.gnome.org/GNOME/gnome-shell/issues/865 -- 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/1831144 Title: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1831144/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833858] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1822195 *** https://bugs.launchpad.net/bugs/1822195 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 #1822195, 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/1833858/+attachment/5272511/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272513/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272516/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272517/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272518/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272519/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1833858/+attachment/5272520/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1822195 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1833858 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833858/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827843] Re: App grid is missing pages of icons
Hi any idea what could be causing this problem? The problem still persists by the way.. Thanks. -- 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/1827843 Title: App grid is missing pages of icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
