[Bug 2060304] [NEW] JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Public bug reported: Related to #1988393. It also affects Jammy and no fix was provided to Jammy. ** Affects: gjs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2060304 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2060304/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Still seeing the same in recent jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I had the same problem with a Thunderbolt audio device and BT. I removed .config/pulse and started working fine again. Not sure if it will fail, but for the moment is working. -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I installed Ubuntu 20.04 5 days ago (using the daily iso) and works fine with Quadro P3200 Mobile and default proprietary drivers installed. I installed it setting up the user with autologon from the installer. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874223] [NEW] Gnome-Shell search does not work
Public bug reported: Gnome-shell search does not work. When I open the menu using "Meta" key on keyboard, and I write anything, no results are displayed. I noted errors on gnome-shell journal (see attached logs): Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:59:54 2020 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1874223 Title: Gnome-Shell search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874223] Re: Gnome-Shell search does not work
** Attachment added: "journalctl_gnome-shell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874223/+attachment/5357870/+files/journalctl_gnome-shell.txt -- 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/1874223 Title: Gnome-Shell search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1874223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873768] [NEW] Gnome Network Settings wrong position of texts
Public bug reported: The text boxes of a network connection details is wrong placed and one text box is over another, see screenshot. NOTE: 100% scale on display. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 11:14:14 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot-20200420111445-972x806.png" https://bugs.launchpad.net/bugs/1873768/+attachment/5357078/+files/Screenshot-20200420111445-972x806.png -- 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/1873768 Title: Gnome Network Settings wrong position of texts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759150] [NEW] systemd stopped resolving after back from suspend
Public bug reported: I noted it after back from suspend, but could happens on other conditions: systemd-resolved stopped resolving. $ host google.com 127.0.0.53 Using domain server: Name: 127.0.0.53 Address: 127.0.0.53#53 Aliases: Host google.com not found: 2(SERVFAIL) But resolved service is active without problems. ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 11822 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─11822 /lib/systemd/systemd-resolved Mar 27 09:28:01 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:06 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:28:42 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:07 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:29:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:32 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:30:37 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:10 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. Mar 27 09:38:15 myhostname systemd-resolved[11822]: Got packet on unexpected IP range, refusing. I checked the network traffic: 09:38:15.476106 IP 10.66.57.54.48901 > 127.0.0.53.53: 7013+ A? google.com. (28) 09:38:15.476205 IP 127.0.0.53.53 > 127.0.0.1.48901: 7013 ServFail [0q] 0/0/0 (12) And resolv service works fine: $ systemd-resolve google.com google.com: 216.58.214.174 -- Information acquired via protocol DNS in 7.2ms. -- Data is authenticated: no ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 27 09:34:21 2018 InstallationDate: Installed on 2018-02-16 (38 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookPro11,4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0177.B00.1708080033 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: I noted it after back from suspend, but could happens on other conditions: systemd-resolved stopped resolving. - - + $ host google.com 127.0.0.53 Using domain server: Name: 127.0.0.53 Address: 127.0.0.53#53 - Aliases: + Aliases: Host google.com not found: 2(SERVFAIL) - + But resolved service is active without problems. ● systemd-resolved.service - Network Name Resolution -Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) -Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago - Docs: man:systemd-resolved.service(8) -https://www.freedesktop.org/wiki/Software/systemd/resolved - https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers - https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients - Main PID: 11822 (systemd-resolve) -Status: "Processing requests..." - Tasks: 1 (limit: 4915) -CGroup: /system.slice/systemd-resolved.service -└─11822 /lib/systemd/systemd-resolved + Loaded: loaded
[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
Seems that it is could be a duplicated of #1723362 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1102958] [NEW] totem-plugin-viewer crashed with SIGSEGV in totem_embedded_play()
Public bug reported: 1) Open http://carreteras.webcindario.com/ 2) Click on pause (any video) 2.1) Wait few seconds. 3) Click on play (step 2 video) 3.1) Wait few seconds. 4) Close the firefox tab - Totem crash. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CrashCounter: 1 Date: Tue Jan 22 12:56:33 2013 ExecutablePath: /usr/lib/totem/totem-plugin-viewer InstallationDate: Installed on 2012-11-02 (80 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/totem/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --referrer http://carreteras.webcindario.com/ --mimetype video/x-msvideo SegvAnalysis: Segfault happened at: 0x7f5f387ebd27 totem_embedded_play+103:mov 0x8(%rax),%rcx PC (0x7f5f387ebd27) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rcx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer0.10 StacktraceTop: totem_embedded_play (emb=0x7f5f39910870, error=optimised out) at totem-plugin-viewer.c:479 _g_closure_invoke_va (closure=0x7f5f39a89c70, return_value=0x0, instance=0x7f5f39938000, args=0x703d6228, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840 g_signal_emit_valist (instance=0x7f5f39938000, signal_id=optimised out, detail=0, var_args=var_args@entry=0x703d6228) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211 g_signal_emit (instance=optimised out, signal_id=optimised out, detail=optimised out) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3356 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: totem-plugin-viewer crashed with SIGSEGV in totem_embedded_play() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk kismet libvirtd lpadmin plugdev sambashare src sudo vboxusers ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace quantal third-party-packages ** 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 gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1102958 Title: totem-plugin-viewer crashed with SIGSEGV in totem_embedded_play() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1102958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1102952] Re: totem-plugin-viewer crashed with SIGSEGV in _g_closure_invoke_va()
*** This bug is a duplicate of bug 1102958 *** https://bugs.launchpad.net/bugs/1102958 ** This bug has been marked a duplicate of private bug 1102958 ** 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 gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1102952 Title: totem-plugin-viewer crashed with SIGSEGV in _g_closure_invoke_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1102952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 805376] Re: gnome-control-center crashed with SIGSEGV in refresh_ui()
I just opened google-chrome, then try to change the Proxy Settings from google chrome advanced settings. The it crashed 2 seconds after Network manager was displayed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/805376 Title: gnome-control-center crashed with SIGSEGV in refresh_ui() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/805376/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210090] Re: evolution google calendar doesn't work with private calendars
I add to this bug ... when you tried to add some private calendars from the same google account it doesn't work. -- evolution google calendar doesn't work with private calendars https://bugs.launchpad.net/bugs/210090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 58093] I lost the control of the desktop when screen saver run
Public bug reported: Binary package hint: gnome-screensaver When I open a session with rdesktop and the screen saver (gnome- screensaver or xscreensaver or xlock) run, I lost the control of the mouse and keyboard (but I can do Ctrl+Alt+F1 and the TTY/1 works OK). I can kill the screen saver process and return to the desktop, but I only see the desktop, without the keyboard and mouse. So, I can't do nothing. To check it: 1) Open a rdesktop session 2) Block the computer or, wait the screen saver 3) Try to do any thing NOTE: My screensaver lock the screen with password, I don't test it without the password lock. Thank's ** Affects: gnome-screensaver (Ubuntu) Importance: Untriaged Status: Unconfirmed -- I lost the control of the desktop when screen saver run https://launchpad.net/bugs/58093 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 58093] Re: I lost the control of the desktop when screen saver run
I use Ubuntu Desktop Dapper (6.06) with all updates. -- I lost the control of the desktop when screen saver run https://launchpad.net/bugs/58093 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
