[Bug 1789577] Re: An Unresponsive Window Freezes the Whole Desktop
** Changed in: mutter Status: Unknown => Confirmed ** Changed in: mutter Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1789577 Title: An Unresponsive Window Freezes the Whole Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1789577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790384] Re: Unable to return from lock screen
Please: 1. Reproduce the problem again, and then 2. Log into a VT (Ctrl+Alt+F4) 3. Save the latest system log by running: journalctl -b > journal.txt 4. As soon as you can after that, attach the file 'journal.txt' from your home directory to this bug. ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1790384 Title: Unable to return from lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1552792] Re: gnome software leaves dependencies installed
** Changed in: packagekit (Ubuntu Cosmic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790362] Re: Login screen can't appear when using GNOME on my ubuntu 18.04
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 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 1727356, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) ** This bug is no longer a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) ** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) -- 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/1790362 Title: Login screen can't appear when using GNOME on my ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789962] Re: gnome-shell segfaults in Wayland when display is turned off while Kodi running
Thanks for your efforts. It sounds like the GUI version of apport is broken or at least not able to give us the information we want. Please try using 'apport-cli' in a terminal instead, which should then print the URL of the bug report. ** 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/1789962 Title: gnome-shell segfaults in Wayland when display is turned off while Kodi running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Will do Daniel. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789822] Re: Colour profile deactivated after interrupted screen fade-out
Using GNOME 3.29 on Ubuntu 18.10 it appears this bug is fixed. I'm not sure about Ubuntu 18.04 but do recommend you upgrade to 18.04 ASAP anyway since it is our latest long term release that will be getting the most GNOME fixes. ** Changed in: colord (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: lightdm (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: colord (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: lightdm (Ubuntu) Status: New => Fix Released ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- 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/1789822 Title: Colour profile deactivated after interrupted screen fade-out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1789822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789749] Re: Virtual desktops are shown in the middle of screen in GNOME Shell
Discussion continues upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/517 ** Description changed: - https://gitlab.gnome.org/GNOME/mutter/issues/285 + https://gitlab.gnome.org/GNOME/gnome-shell/issues/517 --- Hi, since I use Ubuntu 18.04 with GNOME Shell I see that the virtual desktops panel is shown in the middle of screen when I drag a file to the Activities corner. I didn't see this behavior in 17.10, so it's really strange for me. I really like gnome-session, but I drag a lot of files through Activities, so to not see the bug I'm forced to use the Ubuntu session (now communitheme). Yes, it's really annoying. I share a file to show how is the bug. I'm using: -Ubuntu 18.04 64-bit. -GNOME 3.28.2 (provided by official repos). -Linux 4.15.0-33-generic (but I saw the bug in all previous kernels released Ubuntu 18.04). I saw the bug in two different GPUs: -[AMD/ATI] RV630/M76 [Mobility Radeon HD 2600] with Mesa and free Radeon driver provided by official repos. -MSI NVIDIA GTX 1050 with official proprietary driver. I think is a general bug. -- 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/1789749 Title: Virtual desktops are shown in the middle of screen in GNOME Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789577] Re: An Unresponsive Window Freezes the Whole Desktop
** Bug watch added: GNOME Bug Tracker #786114 https://bugzilla.gnome.org/show_bug.cgi?id=786114 ** Also affects: mutter via https://bugzilla.gnome.org/show_bug.cgi?id=786114 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/273 + https://bugzilla.gnome.org/show_bug.cgi?id=786114 + + --- + When debugging UI Applications, this application becomes naturally unresponsive when reaching an execution breakpoint. As a consequence, I see the "Force Quit or Wait" dialog, which freezes the whole desktop. I have no idea why that is, but it is super annoying. - And this is of course not only the case when debugging, but happens as well for a "normal" application freeze. Why does a frozen application should immediately require my attention, no matter what else I am doing? Why does this require my whole desktop to freeze and wait for my input? + And this is of course not only the case when debugging, but happens as well for a "normal" application freeze. Why does a frozen application should immediately require my attention, no matter what else I am doing? Why does this require my whole desktop to freeze and wait for my input? Sometimes I just notice a desktop freeze and dont know whats going on until I find this stupid "Quit or Wait" dialog. Super annoying. Please make this window not freeze everything else, nothing is so important that the whole desktop should freeze to force input. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 10:00:02 2018 DistUpgraded: 2018-08-22 12:49:08,163 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 530 [17aa:222e] - NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] + Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 530 [17aa:222e] + NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] InstallationDate: Installed on 2017-12-15 (256 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20EQS00600 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-08-22 (6 days ago) dmi.bios.date: 06/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET69W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS00600 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET69W(1.42):bd06/28/2017:svnLENOVO:pn20EQS00600:pvrThinkPadP50:rvnLENOVO:rn20EQS00600:rvrNODPK:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS00600 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 -- 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/1789577 Title: An Unresponsive Window Freezes the Whole Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1789577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
No the issue is not fixed yet. Please put any relevant comments in the upstream bug where the developers will see them: https://gitlab.gnome.org/GNOME/gnome-shell/issues/501 -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM
Thanks. Your journal.txt is showing the nvidia driver thinks the display was disconnected a few minutes after boot. So normally I would say that's a bad monitor connection (check your cables) or a driver bug. However the first message here also suggests the blackout was triggered by the system suspending and resuming. So please check your screensaver and power management settings... ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (II) systemd-logind: got resume for 13:68 ago 31 21:39:08 ubuntu-ryzen systemd-journald[416]: Suppressed 524 messages from session-3.scope ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): connected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): Ancor Communications Inc VX229 (DFP-1): 600.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: disconnected ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (--) NVIDIA(GPU-0): ago 31 21:39:08 ubuntu-ryzen /usr/lib/gdm3/gdm-x-session[1829]: (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select" Unfortunately this is not a gnome-shell bug and the nvidia driver version 396 is not supported yet because it's not released yet (https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-396). So we can keep discussing it here, but don't have a supported software component to blame right now. Hence the status is "Invalid". :( ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1785834 Title: Screen randomly turns black minutes after successfully login with GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1785834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
Moved to gtk, per upstream. ** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: Opinion => New ** No longer affects: gnome-terminal (Ubuntu) ** Description changed: + https://gitlab.gnome.org/GNOME/gtk/issues/1303 + + --- + Ubuntu 17.10, Wayland session. In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right- arrow` moves the cursor one word to the left and to the right. In Xorg this works, no matter which key you press first (ctrl or arrow). In wayland, you have to press the ctrl key first, otherwise, the cursor will not move. # How to reproduce: type some words in gnome terminal press `left-arrow` key, wait for the cursor to move and, and press `ctrl`. # What happens The cursor first moves one character per "tick", and stops immediately when you press `ctrl`. # What should happen The cursor first moves one character per "tick", and starts moving one word per "tick" when you press `ctrl`. -- 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/1720213 Title: Word moving with left-arrow-ctrl broken in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1720213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789693] Re: Format volume requires a volume label
Good, the details are important. Thank you -- 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/1789693 Title: Format volume requires a volume label To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1789693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
I installed Ubuntu 18.10 gjs and libgjs0g 1.53.3-1 (of Ubuntu 18.10) to
Ubuntu 18.04. It seems that the memory leak lives forever...
Memory usage started from 170MB, and after two hours is over 360MB.
[image: Képernyőkép erről: 2018-09-02 23-46-44.png]
chris pollock <1672...@bugs.launchpad.net> ezt írta (időpont: 2018. aug.
20., H, 16:51):
> This is:
> apt-cache policy gnome-shell
> gnome-shell:
> Installed: 3.28.2-0ubuntu0.18.04.1
> Candidate: 3.28.2-0ubuntu0.18.04.1
>
> apt-cache policy evolution
> evolution:
> Installed: 3.28.1-2
> Candidate: 3.28.1-2
>
> lsb_release -crid
> Distributor ID: Ubuntu
> Description:Ubuntu 18.04.1 LTS
> Release:18.04
> Codename: bionic
>
> uname -a
> Linux localhost 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC
> 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> Aug 20 08:46:13 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 19537920/16986112/-2551808, res+swap =
> 14004224/11452416/-2551808
> Aug 20 08:46:19 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16916480/16908288/-8192, res+swap = 11382784/11374592/-8192
> Aug 20 08:46:58 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16908288/16908288/0, res+swap = 11374592/11374592/0
> Aug 20 08:47:29 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16908288/16912384/4096, res+swap = 11378688/11378688/0
> Aug 20 08:47:59 localhost evolution.desktop[2662]: Memory pressure relief:
> Total: res = 16912384/16912384/0, res+swap = 11378688/11378688/0
>
> Not sure if this pertains to this bug at all. I noticed the above every
> few minutes in my syslog after upgrading to 18.04.1 last week.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672297
>
> Title:
> gnome-shell uses lots of memory, and grows over time
>
> Status in GNOME Shell:
> Confirmed
> Status in gjs package in Ubuntu:
> Fix Released
> Status in gjs source package in Bionic:
> In Progress
>
> Bug description:
> Upstream:
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
>
> ---
>
> gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
> almost 2 GiB.
>
> user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
> /usr/bin/gnome-shell
>
> strace output is voluminous; here is a representative sample:
>
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\231\n\10\0\n\0
> \0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
> \0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5,
> revents=POLLOUT}])
> writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11,
> events=POLLIN}, {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,
> events=POLLIN}, {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32,
> events=POLLIN}, {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38,
> events=POLLIN}, {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43,
> events=POLLIN}], 15, 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource
> temporarily unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11,
> events=POLLIN}, {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,
> events=POLLIN}, {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32,
> events=POLLIN}, {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38,
> events=POLLIN}, {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43,
>
[Bug 1790369] Re: GIMP single window f11 should go fullscreen but does not work
Problem occurs also in multiple windows mode and also with GIMP 2.8.22 in Ubuntu 18.04 Bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1790369 Title: GIMP single window f11 should go fullscreen but does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1790369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790384] [NEW] Unable to return from lock screen
Public bug reported: Yesterday I upgraded from Ubuntu 16.4 LTS to Ubuntu 18.4 LTS. Now, whenever my computer goes to the lock screen (either by manually locking, or timeout), I cannot return. I see the date/time and notifications on the lock screen, I can drag up or press a key to see the password prompt. I can type my password and submit it either by pressing enter or clicking 'Next'. However, once I submit my password, authentication fails. Then if I try again, it doesn't accept any keystrokes, even if I click the password field. I CAN try again if I click Cancel. However, authentication always fails. I can "pause"/sleep my computer (using the menu in the upper right) and return, but I'm still in an endless login loop. Rebooting from this screen is not an option (except via power cycling the computer). If I choose to "log in as another user", then click myself, I get a mostly-empty screen: It has the status bar at the top and is the classic ubuntu purple, but otherwise blank. But at this point all I can do is reboot (shutdown/reboot is available from here) or choose another user. i.e. I still can't return to my current session. Please help! This is driving me nuts: I have to reboot every time I want to use my computer after a 5+ minute pause. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 2 12:19:49 2018 InstallationDate: Installed on 2016-04-11 (874 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-09-02T12:13:20.375057 ** 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/1790384 Title: Unable to return from lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790384/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790369] [NEW] GIMP single window f11 should go fullscreen but does not work
Public bug reported: Started GIMP from terminal I have the following messages: corrado@corrado-HP-p4-cc-0813:~$ gimp Gtk-Message: 18:00:17.419: Failed to load module "canberra-gtk-module" Missing fast-path babl conversion detected, Implementing missing babl fast paths accelerates GEGL, GIMP and other software using babl, warnings are printed on first occurance of formats used where a conversion has to be synthesized programmatically by babl based on format description *WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double" *WARNING* missing babl fast path(s): "cairo-ARGB32" to "R'G'B'A u8" GIMP started single window mode, I hit f11 to go fullscreen but I see just a sign 'do not stop' I opened the problem to gitlab: https://gitlab.gnome.org/GNOME/gimp/issues/2138 and i was suggested to open this problem to Ubuntu. corrado@corrado-HP-p4-cc-0813:~$ apt policy gimp gimp: Installed: 2.10.6-2 Candidate: 2.10.6-2 Version table: *** 2.10.6-2 500 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-HP-p4-cc-0813:~$ inxi -Fx System:Host: corrado-HP-p4-cc-0813 Kernel: 4.17.0-9-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.29.90 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) 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: 4.6 Wh condition: 21.3/21.5 Wh (99%) 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: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 798 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 798 2: 799 3: 798 4: 799 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.1 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.5 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.17.0-9-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 v: 2.3LK-NAPI 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 driver: rt2800pci v: 2.3.0 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 8.06 GiB (1.7%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 8.05 GiB (25.8%) 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: 42.0 C mobo: 42.0 C Fan Speeds (RPM): N/A Info: Processes: 200 Uptime: 1h 44m Memory: 3.79 GiB used: 1.19 GiB (31.4%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 4.4.19 inxi: 3.0.22 corrado@corrado-HP-p4-cc-0813:~$ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gimp 2.10.6-2 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 2 18:01:26 2018 InstallationDate: Installed on 2018-08-13 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180813) SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Screenshot from 2018-09-02 08-38-03.png" https://bugs.launchpad.net/bugs/1790369/+attachment/5183746/+files/Screenshot%20from%202018-09-02%2008-38-03.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1790369 Title: GIMP single window f11 should go fullscreen but does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1790369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130722] Re: [ffe] Restore a traditional menu under Unity
On ubuntu 16.04, after some recent software update (NO dist upgrade) this has regressed again together with a bunch of other crap that was fixed ages ago. Please reopen, and for fuck's sake can you be more careful and avoid fixed bugs reappearing periodically?? -- 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/1130722 Title: [ffe] Restore a traditional menu under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1130722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085122] Re: Keyring unlocker doesnt allow to write in unity
** Also affects: gnome-keyring Importance: Undecided Status: New -- 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/1085122 Title: Keyring unlocker doesnt allow to write in unity To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1085122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
sudo kbd_mode -s fixed the problem (again) for me. -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790362] [NEW] Login screen can't appear when using GNOME on my ubuntu 18.04
Public bug reported: login screen doesn't appear on my Ubuntu 18.04 when using GNOME as my main desktop environment sudo dpkg-reconfigure gdm3 more details in this link https://bugs.launchpad.net/gnome-shell/+bug/1727356 my system specs CPU Intel® Core™2 Duo CPU E8500 @ 3.16GHz × 2 GPU Intel® G33 memory 3.8 GB please investigate this issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Sep 2 13:48:16 2018 InstallationDate: Installed on 2018-07-04 (60 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-08-17 (16 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-09-02T13:28:04.747435 ** 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/1790362 Title: Login screen can't appear when using GNOME on my ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790360] [NEW] [wayland] Fullscreen games offset after switching back to them from an app in the same workspace
Public bug reported: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the game down by the size of the GNOME Shell top bar and to the right by the size of the Ubuntu Dock. Test Case = 1. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 2. Press Alt-Tab or click a dock icon to switch to another window in the same workspace and then press Alt-Tab or click the dock icon to switch back to the game. The game should display and function normally. Workaround == Switch apps again using any method. Other Info == This is a duplicate of #1732245 which has been reported on Ubuntu 17.10 which reached it's end-of-life on July 19, 2018. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 2 14:36:29 2018 InstallationDate: Installed on 2018-07-10 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- 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/1790360 Title: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758497] Re: evince-thumbnailer crashed with SIGSEGV in tcache_get()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1758497 Title: evince-thumbnailer crashed with SIGSEGV in tcache_get() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1758497/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
