[Bug 2064656] [NEW] gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every
Public bug reported: After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that gnome-shell was spamming errors at the rate of 12 lines every second: geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead. geg. 02 18:29:20 blynas kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:c6:25:2f:1a:a1:27:08:00 SRC=192.168.1.180 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=30487 PROTO=2 geg. 02 18:29:21 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value geg. 02 18:29:21 blynas gnome-shell[3980]: Using untranslated default instead. My locale is lt_LT.UTF-8, which is relevant. This is caused by a mistaken translation of the quote characters in "'24h'" which is used as the default value for a particular gsettings key. Specifically, this translation: https://translations.launchpad.net/ubuntu/noble/+source/gsettings- desktop-schemas/+pots/gsettings-desktop-schemas/lt/232/+translate. Since I'm a member of the Lithuanian translators team, I've fixed the translation error in translations.launchpad.net, but my gnome-shell will continue to spam multiple errors every second until an updated language- pack-gnome-lt-base is released. (I've also submitted a fixed translation upstream to l10n.gnome.org.) Workaround: run dconf-editor, find /org/gnome/desktop/interface/clock- format, uncheck Use default value, click Apply. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 2 18:25:59 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1786 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-05-02 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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/2064656 Title: gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064656/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2063831] Re: Clicking on bottom half of applications switches to background application
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3451 https://gitlab.gnome.org/GNOME/mutter/-/issues/3451 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3451 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/2063831 Title: Clicking on bottom half of applications switches to background application To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036426] Re: gnome calculator crash on IMF server error
Upstream bug: https://gitlab.gnome.org/GNOME/gnome- calculator/-/issues/359 Upstream says the actual bug is in libsoup: https://gitlab.gnome.org/GNOME/libsoup/-/issues/361. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 ** Also affects: gnome-calculator via https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/libsoup/-/issues #361 https://gitlab.gnome.org/GNOME/libsoup/-/issues/361 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2036426 Title: gnome calculator crash on IMF server error To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/2036426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013652] Re: small thumbnails are generated if you have the screenshots folder open in nautilus
Looking through upstream bug tracker I wonder if this might be caused by https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487#note_1553836? -- 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/2013652 Title: small thumbnails are generated if you have the screenshots folder open in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013652] [NEW] small thumbnails are generated if you have the screenshots folder open in nautilus
Public bug reported: If you have ~/Pictures/Screenshots open in Nautilus and you take new screenshots, some of them will get tiny thumbnails instead of regular size thumbnails. See attached picture of the end result: some images have full size thumbnails, some have tiny ones. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 17:02:09 2023 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'starred']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1300, 971)' InstallationDate: Installed on 2019-06-12 (1387 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (161 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "screenshot of nautilus with varying thumbnail sizes" https://bugs.launchpad.net/bugs/2013652/+attachment/5659588/+files/Ekrano%20nuotrauka%20i%C5%A1%202023-03-31%2017-01-58.png ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2487 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487 -- 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/2013652 Title: small thumbnails are generated if you have the screenshots folder open in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2013652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993904] Re: key binding to launch gnome-control-center doesn't work
This was fixed upstream in version 42.beta: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/371a1260630035724e20972ae5bda7098e2928a7 Ubuntu explicitly reverts that in debian/patches/ubuntu/Revert-media- keys-fix-gnome-settings-desktop-file.patch with the rationale > Ubuntu isn't getting the rename until gnome-control-center 42 Well, 22.10 now has gnome-control-center 43 with the .desktop file rename, so this patch ought to be dropped. -- 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/1993904 Title: key binding to launch gnome-control-center doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993904] [NEW] key binding to launch gnome-control-center doesn't work
Public bug reported: There's a default keybinding of XF86Tools to launch gnome-control- center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no longer works in Ubuntu 22.10. Instead I see this error in my journal: spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not find application 'gnome-control-center.desktop' or '(null)' AFACT gnome-control-center 43 renamed the .desktop file to /usr/share/applications/org.gnome.Settings.desktop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-settings-daemon 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 20:29:29 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1993904 Title: key binding to launch gnome-control-center doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1993904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993797] Re: refreshing the view with F5 forgets the sort order
I suspect upstream commit https://gitlab.gnome.org/GNOME/nautilus/-/commit/c72e6def48e47454d4b620f58c93753a8a1b6a3f fixes this, which would explain why I couldn't reproduce using gnome- nightly. (There are several sorting-related upstream commits after the 43.0 tag.) -- 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/1993797 Title: refreshing the view with F5 forgets the sort order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993797] [NEW] refreshing the view with F5 forgets the sort order
Public bug reported: Steps to reproduce: 1. Open Nautilus 2. Switch to list view 3. Sort by size or mtime by clicking on the relevant heading 4. Press F5 to refresh the view Expectation: - Nautilus remembers the sort order Actual behavior: - the list is now sorted by name (in ascending order) Additional information: - This is a regression since Ubuntu 22.04 LTS - I was unable to reproduce the problem using the org.gnome.NautilusDevel flatpak from gnome-nightly ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 21 12:58:21 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1226 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (0 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1993797 Title: refreshing the view with F5 forgets the sort order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_win
Happened to me today, when I unplugged the USB C cable connecting my ThinkPad to the dock with an external monitor plugged in, and then closed the laptop lid to put it to sleep. journalctl shows ``` geg. 27 15:53:39 blynas gnome-shell[3815]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed geg. 27 15:53:39 blynas gnome-shell[3815]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed geg. 27 15:53:40 blynas systemd-logind[906]: Lid closed. geg. 27 15:53:41 blynas gnome-shell[3815]: ** geg. 27 15:53:41 blynas gnome-shell[3815]: mutter:ERROR:../src/core/window.c:3728:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) geg. 27 15:53:41 blynas gnome-shell[3815]: Bail out! mutter:ERROR:../src/core/window.c:3728:meta_window_update_for_monitors_changed: assertion failed: (!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)) geg. 27 15:53:41 blynas gnome-shell[3815]: GNOME Shell crashed with signal 6 geg. 27 15:53:41 blynas gnome-shell[3815]: == Stack trace for context 0x563285c4a4b0 == ``` Ubuntu 22.04 LTS, Intel video (in case that matters). -- 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/1970917 Title: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor)" in meta_window_update_for_monitors_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
This bug also affects 21.10, FWIW. -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I've seen this three times now on Ubuntu 21.10 (GNOME 40). I don't recall ever seeing it on Ubuntu 20.10. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Filed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4351 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4351 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351 -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930371] [NEW] top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Public bug reported: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I don't know if you need more confirmations, but upgrading to mutter + libmitter from groovy-proposed fixed my chromium problem too. (The only weird bit was how I was unconsensually logged out during the upgrade, but that could've been plymouth or some other package.) -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've just upgraded to groovy and hit this bug. For now I'm using socat as a workaround: socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork unix:/tmp/.X11-unix/X0 This works, but is rather slow (and probably also opens a security hole on multiuser machines). -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_event() from process_sp
Unfortunately I was unable to reproduce the 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault in _filterKeybinding:windowManager.js:1825 from invoke_handler() from process_event() from process_special_modifier_key() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1851528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1870 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870 -- 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/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas ar aplankas
neegzistuoja.
[Current thread is 1 (Thread 0x7f5c91796cc0 (LWP 3417))]
(gdb) bt
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x56068ef0852a in dump_gjs_stack_on_signal_handler ()
#2
#3 0x5606b18aca40 in ?? ()
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
#5 process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220, event=event@entry=0x5606b4c878c0)
at ../src/core/keybindings.c:2005
#6 0x7f5c971ab83e in process_special_modifier_key
(display=display@entry=0x5606900e0020, event=event@entry=0x5606b4c878c0,
window=window@entry=0x56069e5ad220,
modifier_press_only=modifier_press_only@entry=0x5606900e01a8,
resolved_key_combo=resolved_key_combo@entry=0x5606900e0198,
trigger_callback=0x7f5c971a5100 )
at ../src/core/keybindings.c:2051
#7 0x7f5c971ac976 in process_overlay_key (window=0x56069e5ad220,
event=0x5606b4c878c0, display=0x5606900e0020)
at ../src/core/keybindings.c:2151
#8 process_key_event (event=0x5606b4c878c0, window=0x56069e5ad220,
display=0x5606900e0020) at ../src/core/keybindings.c:2228
#9 meta_keybindings_process_event (display=display@entry=0x5606900e0020,
window=window@entry=0x56069e5ad220,
event=event@entry=0x5606b4c878c0) at ../src/core/keybindings.c:2326
#10 0x7f5c971a801c in meta_display_handle_event (event=0x5606b4c878c0,
display=0x5606900e0020) at ../src/core/events.c:358
#11 event_callback (event=0x5606b4c878c0, data=0x5606900e0020) at
../src/core/events.c:479
#12 0x7f5c97368235 in _clutter_event_process_filters ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#13 0x7f5c9737e585 in emit_keyboard_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#14 0x7f5c9721c0e0 in meta_input_device_native_process_kbd_a11y_event
(event=0x5606b4c878c0, device=0x56068fd782b0,
emit_event_func=0x7f5c9737e570 ) at
../src/backends/native/meta-input-device-native.c:1195
#15 0x7f5c9737fa36 in _clutter_process_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#16 0x7f5c97399d08 in _clutter_stage_queue_event ()
from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/mutter-5/libmutter-clutter-5.so.0
#17 0x7f5c9721901c in meta_event_dispatch (g_source=,
callback=, user_data=)
at ../src/backends/native/meta-device-manager-native.c:686
#18 0x7f5c97cf984d in g_main_context_dispatch () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#19 0x7f5c97cf9ad0 in g_main_context_iterate.isra () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#20 0x7f5c97cf9dc3 in g_main_loop_run () from
/tmp/apport_sandbox_6sb0y3pp/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6200.1
#21 0x7f5c971aefe0 in meta_run () at ../src/core/main.c:676
#22 0x56068ef07d85 in main ()
(gdb) frame 4
#4 0x7f5c971a9f11 in invoke_handler (binding=0x56069dc351c0,
event=0x5606b4c878c0, window=0x56069dc351c0, handler=,
display=0x5606900e0020) at ../src/core/keybindings.c:1921
1921../src/core/keybindings.c: Toks failas ar aplankas neegzistuoja.
(gdb) print *binding->handler
$1 = {name = 0x5606b49e5e80 "", func = 0x5606b18aca40, default_func =
0x7f5c5b333f10, data = 0, flags = 0, user_data = 0x5606b10c4e30,
user_data_free_func = 0x7f5c97487c60}
(gdb) print *binding
$2 = {name = 0x5606b49d15d0 "\220T\241\234\006V", combo = {keysym = 50, keycode
= 0, modifiers = META_VIRTUAL_SUPER_MASK},
resolved_combo = {keycodes = 0x5606a0c44d70, len = 1, mask = 64}, flags = 0,
handler = 0x5606b37830b0}
#gnome-shell reactions on IRC:
18:34 looks suspicious
18:35 its as if the looked up binding was freed already and now just
contains garbage
--
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/1851528
Title:
JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
and segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851528] Re: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
The JS traceback points to this line: https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771 (GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I didn't have the time to go hunt for the exact commit that corresponds to the package, instead I extracted the source file with gresource extract /usr/lib/gnome-shell/libgnome-shell.so /org/gnome/shell/ui/windowManager.js, looked up the line, then found the same code in the same function in the current gitlab tree.) The column points to the `binding.get_name()` call. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851528] [NEW] JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault
Public bug reported: I was trying to bring my Firefox window to front by pressing Super+2 (it's my second pinned launcher), and gnome-shell crashed. journalctl shows this: lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 _filterKeybinding@resource:///org/gnome/shell/ui/windowManager.js:1825:43 lapkr. 06 16:38:58 blynas gnome-shell[3417]: GNOME Shell crashed with signal 11 lapkr. 06 16:38:58 blynas gnome-shell[3417]: == Stack trace for context 0x56068fb2e3e0 == I have a crash dump in /var/crash/, but apport thinks it's unreportable because my rygel was out of date. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851528 Title: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0 and segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826550] Re: Fractional scaling options do not appear with multiple monitors
Possibly related to https://gitlab.gnome.org/GNOME/gnome-control- center/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #17 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17 -- 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/1826550 Title: Fractional scaling options do not appear with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1067301] Re: gnome-keyring does not support "ssh-add -c"
The gnome-bugs link is broken. Working links: - https://bugzilla.gnome.org/show_bug.cgi?id=525574 (old bugzilla) - https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5 (new gitlab) ** Bug watch added: bugzilla.gnome.org/ #525574 https://bugzilla.gnome.org/show_bug.cgi?id=525574 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #5 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5 -- 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/1067301 Title: gnome-keyring does not support "ssh-add -c" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1067301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640541] Re: nautilus shows Windows Network but fails to open it
Tried this again on Ubuntu 18.10, and I'm happy to report that almost everything works fine! - "Other locations" in Nautilus shows my Samba server (after a couple of seconds) - I can click on it, get an authentication dialog, then see the shares - I can click on a share and see the files - I can click on a file and discover that Totem is still hilariously broken on Wayland (that's a separate bug) However some things are still broken: - "Other locations" in Nautilus shows a "Windows network" - I can click it and couple of seconds later I get an error dialog saying "Could not access location" (title): "Couldn't get a list of shares from server: No such file or directory" (translating from lt_LT again). gio ls network:/// prints a usage message. gio list network:/// shows dnssd-domain-VARLIUS2._smb._tcp smb-root (VARLIUS2 is the name of my Samba server) gio list smb:/// says gio: smb:///: Location is not a mountpoint (I'm translating back from lt_LT because no amount of LC_ALL=C LANGUAGE=en is giving me English error messages, at best I get ?s instead of UTF-8 characters.) -- 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/1640541 Title: nautilus shows Windows Network but fails to open it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1640541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_
** Attachment added: "after-update-later.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220141/+files/after-update-later.txt -- 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/1648534 Title: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_connection_call_sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_
Saw this crash for the first time. I'm on Ubuntu 18.10. Every time I ask gnome-software to check for updates, the number of open files (watch 'ls /proc/$(pidof gnome- software)/fd') grows by 25, then drops a bit and settles down to 7 higher than it was before. I'm attaching two snapshots of ls -l /proc/$(pidof gnome-software)/fd, before I triggered an update check, and after it told me there were no updates available. ** Attachment added: "before-update.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220140/+files/before-update.txt -- 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/1648534 Title: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_connection_call_sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702071] Re: Search spins forever, returns no results.
This is still a problem on Ubuntu 18.10: - search spins forever - clicking on a category shows a bunch of empty boxes with an ellipsis in it - fetching updates also seems to spin forever journalctl _EXE=/usr/bin/gnome-software shows nothing today; the last log entries were from Nov 9: lapkr. 09 10:49:17 platonas gnome-software[6336]: failed to get updates: Timeout was reached as flatpak took too long to return results lapkr. 09 10:49:26 platonas gnome-software[6336]: failed to get updates: Timeout was reached as flatpak took too long to return results lapkr. 09 10:49:38 platonas gnome-software[6336]: failed to get updates: Timeout was reached as flatpak took too long to return results Killing and restarting gnome-software fixes everything. -- 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/1702071 Title: Search spins forever, returns no results. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1702071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1802524] [NEW] gsd-media-keys spams my journal with GetVSyncParametersIfAvailable() failed!
Public bug reported: My journalctl is full of these: lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.225054:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.227435:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.242628:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.248687:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.258811:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.228289:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.242794:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.379889:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.392316:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:34 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161834.560700:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:34 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161834.575089:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:43 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161843.046966:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:43 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161843.058493:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.250630:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.252612:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.258635:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.258812:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.572135:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.575212:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.591944:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.955126:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.958343:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.974856:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:51 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161851.538471:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:51 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161851.541991:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! In total `journalctl -b
[Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
gconf2 broke my 18.04 -> 18.10 upgrade with dpkg: dependency problems prevent processing triggers for gconf2: gconf2 priklauso nuo psmisc; tačiau: Paketas psmisc dar nekonfigūruotas. dpkg: klaida, apdorojant paketą gconf2 (--configure): dependency problems - leaving triggers unprocessed in a loop until dpkg gave up. Perhaps this is another instance of bug 1780996? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747910] Re: Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29))
*** This bug is a duplicate of bug 1731911 *** https://bugs.launchpad.net/bugs/1731911 This is probably a duplicate of 1728588 (which itself is marked as a duplicate of 1731911). apport-retrace gives me this Xwayland stack trace: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7fce6a322f5d in __GI_abort () at abort.c:90 #2 0x558934f5713a in OsAbort () at ../../../../os/utils.c:1361 #3 0x558934f5cc53 in AbortServer () at ../../../../os/log.c:877 #4 0x558934f5da75 in FatalError (f=f@entry=0x558934f66fa6 "%s") at ../../../../os/log.c:1015 #5 0x558934de2e6c in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:885 #6 0x7fce6c7728ca in wl_log (fmt=) at ../src/wayland-util.c:406 #7 0x7fce6c76e2d8 in display_handle_error (data=, display=0x558935d07e30, object=0x558935d0c300, code=0, message=) at ../src/wayland-client.c:810 #8 0x7fce69c60e18 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #9 0x7fce69c6087a in ffi_call (cif=cif@entry=0x7ffd318ba470, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffd318ba540) at ../src/x86/ffi64.c:525 #10 0x7fce6c771a1b in wl_closure_invoke (closure=, flags=, target=, opcode=0, data=) at ../src/connection.c:935 #11 0x7fce6c76e5b8 in dispatch_event (display=display@entry=0x558935d07e30, queue=) at ../src/wayland-client.c:1310 #12 0x7fce6c76f847 in dispatch_queue (queue=0x558935d07ef8, display=0x558935d07e30) at ../src/wayland-client.c:1449 #13 wl_display_dispatch_queue_pending (display=0x558935d07e30, queue=0x558935d07ef8) at ../src/wayland-client.c:1698 #14 0x7fce6c76f8cc in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1761 #15 0x558934de341b in xwl_read_events (xwl_screen=0x558935cffa40) at ../../../../../hw/xwayland/xwayland.c:598 #16 0x558934f54cb1 in ospoll_wait (ospoll=0x558935cf4a20, timeout=) at ../../../../os/ospoll.c:412 #17 0x558934f4dcbb in WaitForSomething (are_ready=) at ../../../../os/WaitFor.c:226 #18 0x558934f199f3 in Dispatch () at ../../../../dix/dispatch.c:422 #19 0x558934f1dc90 in dix_main (argc=11, argv=0x7ffd318bb4f8, envp=) at ../../../../dix/main.c:287 #20 0x7fce6a30b1c1 in __libc_start_main (main=0x558934de2a60 , argc=11, argv=0x7ffd318bb4f8, init=, fini=, rtld_fini=, stack_end=0x7ffd318bb4e8) at ../csu/libc-start.c:308 #21 0x558934de2a9a in _start () ** This bug has been marked a duplicate of bug 1731911 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() -- 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/1747910 Title: Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747910] [NEW] Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29))
Public bug reported: I switched to a new external monitor at work today. I cannot reproduce the exact sequence of events, but it was basically: plug in external monitor (via DisplayPort), suspend laptop, unplug that monitor and plug in another one, resume laptop. At that point I was staring at the GDM login screen because gnome-shell had crashed on me. (It's hard to understand what happened exactly, from the journal, but it may've been Xwayland that crashed -- I've an Xwayland crash file in /var/crash with a matching timestamp -- but the entire GNOME session died soon afterwards.) Highlights from journalctl: Vas 07 15:04:27 platonas gtimelog[27075]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas gsd-color[3440]: no xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 device found: Failed to find output xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 Vas 07 15:04:27 platonas evolution-alarm[4513]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas update-notifier[5165]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas xdg-desktop-por[5317]: Error 71 (Protokolo klaida) dispatching to Wayland display. Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: Fatal server error: Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) wl_registry@2: error 0: invalid global wl_output (29) Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Unit entered failed state. Vas 07 15:04:27 platonas systemd[4065]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. ... Vas 07 15:04:34 platonas org.gnome.Shell.desktop[4166]: xcb_connection_has_error() grąžino reikšmę "true" ... Vas 07 15:04:34 platonas gnome-shell[4166]: Connection to xwayland lost Vas 07 15:04:34 platonas org.gnome.Shell.desktop[4166]: == Stack trace for context 0x564a010d2000 == ... Vas 07 15:04:35 platonas gnome-session[4081]: gnome-session-binary[4081]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Vas 07 15:04:35 platonas gnome-session-binary[4081]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Vas 07 15:04:35 platonas gnome-session-binary[4081]: Unrecoverable failure in required component org.gnome.Shell.desktop ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Feb 7 15:20:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-10 (515 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (110 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Description changed: I switched to a new external monitor at work today. I cannot reproduce the exact sequence of events, but it was basically: plug in external monitor (via DisplayPort), suspend laptop, unplug that monitor and plug - in another one, resume laptop. At that point I was starting at the GDM + in another one, resume laptop. At that point I was staring at the GDM login screen because gnome-shell had crashed on me. (It's hard to understand what happened exactly, from the journal, but it may've been Xwayland that crashed -- I've an Xwayland crash file in /var/crash with a matching timestamp -- but the entire GNOME session died soon afterwards.) Highlights from journalctl: - Vas 07 15:04:27 platonas gtimelog[27075]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas gsd-color[3440]: no xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 device found: Failed to find output xrandr-Goldstar Company Ltd-LG ULTRAWIDE-316961 - Vas 07 15:04:27 platonas evolution-alarm[4513]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas update-notifier[5165]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas xdg-desktop-por[5317]: Error 71 (Protokolo klaida) dispatching to Wayland display. - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: Fatal server error: - Vas 07 15:04:27 platonas org.gnome.Shell.desktop[4166]: (EE) wl_registry@2: error 0: invalid global wl_output
[Bug 1721577] Re: switch monitor configurations crash-freezes desktop
Upstream bugs that look similar to this one: - https://bugzilla.gnome.org/show_bug.cgi?id=787637 - https://bugzilla.gnome.org/show_bug.cgi?id=788764 ** Bug watch added: GNOME Bug Tracker #787637 https://bugzilla.gnome.org/show_bug.cgi?id=787637 ** Bug watch added: GNOME Bug Tracker #788764 https://bugzilla.gnome.org/show_bug.cgi?id=788764 -- 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/1721577 Title: switch monitor configurations crash-freezes desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages
** Bug watch added: GNOME Bug Tracker #789352 https://bugzilla.gnome.org/show_bug.cgi?id=789352 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=789352 Importance: Unknown Status: Unknown -- 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/1721049 Title: "Got unknown content type text/html" error viewing flatpack packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1721049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
** Bug watch added: GNOME Bug Tracker #751064 https://bugzilla.gnome.org/show_bug.cgi?id=751064 ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=751064 Importance: Unknown Status: Unknown -- 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/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 ** This bug has been marked a duplicate of bug 1288655 terminal gets smaller when maximized and then restored -- 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/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723368] Re: terminal window shrinks by 1 column and 1 row each time it is unmaximised
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 This looks like a duplicate of bug 1288655. ** This bug has been marked a duplicate of bug 1288655 terminal gets smaller when maximized and then restored -- 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/1723368 Title: terminal window shrinks by 1 column and 1 row each time it is unmaximised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
Duplicate of bug 1288655? BTW I cannot confirm that not using colors fixes the issue; even if I set PS1='$ ', I still get shrinkage after repeated maximizing/restoring or fullscreening/restoring. -- 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/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key
This doesn't look like a terminal problem. It looks like a kernel problem -- some input device is spamming fake key press events. It would be useful if you could determine which device is sending these events. I would run `sudo evemu-record`, pick each device in turn, to see if it sees repeating events or not. -- 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/1722298 Title: keyboard autorepeat not happening when I hold down any key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1722298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=780622 Importance: Unknown Status: Unknown -- 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/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1688528] Re: gnome-terminal with screen interprets mouse wheel events as up/down
I've been using this in my ~/.screenrc to tell screen not to switch to the alternate screen, so I can use my scrollback: termcapinfo xterm|xterm-256color ti=\E7\E[?47l:te=\E[H\E[2J\E[?47l This also enables mouse wheel scrolling of the scrollback (as long as you don't turn on 'mousetrack' in your .screenrc). ** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- 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/1688528 Title: gnome-terminal with screen interprets mouse wheel events as up/down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1688391] Re: Highlight of links in terminal is not very smart
** Summary changed: - Highlight of links in terminal is retarded + Highlight of links in terminal is not very smart -- 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/1688391 Title: Highlight of links in terminal is not very smart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion ** Changed in: vte2.91 (Ubuntu) Status: New => Opinion ** Changed in: ubuntu-gnome Status: New => Opinion -- 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/1609009 Title: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1609009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1535169] Re: specify error
What are the steps to reproduce this? When I run gnome-terminal in a terminal window in 17.10 all I get is Warning: DESKTOP_STARTUP_ID not set and no fallback available. This doesn't change if I export PYTHONWARNINGS=all beforehand. -- 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/1535169 Title: specify error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1535169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1605397] Re: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen
I'm unable to reproduce on 17.10 with gnome-shell. -- 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/1605397 Title: gnome-terminal doesn't return to its original size when unsnapping from the side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1605397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637688] Re: Terminal and file manager scrolls inverted
The old way of mouse wheel scrolling was mice would emit discrete button 4 and 5 events, and scrolling was jumpy. The new way of mouse wheel scrolling is via XInput2, you get two additional axes (vertical and horizontal scroll events) that give you more fine-grained positions. This way you can get smooth scrolling with a touchpad. When you remap mouse buttons, this can only affect older applications that do not support smooth mouse wheel scrolling. -- 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/1637688 Title: Terminal and file manager scrolls inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1525579] Re: terminal freezes when I use : run-mozilla.sh
** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- 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/1525579 Title: terminal freezes when I use : run-mozilla.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1525579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1496829] Re: when the set command is passed without any parameters it throws some sort of source code on the screen
`set` is a bash builtin command that displays the names values of all shell variables when invoked without any arguments. Shell functions are implemented as variables, technically (although you cannot see the body of the function with echo $functionname). This is working as designed and has noting to do with gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/1496829 Title: when the set command is passed without any parameters it throws some sort of source code on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1496829/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
Bug 1233205 was a bug in Unity and/or Compiz. Ubuntu 17.10 uses gnome- shell. -- 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/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards
** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Opinion -- 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/1429584 Title: gnome-terminal doesn't set $COLORTERM from 3.14 onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
(Although TBH you're right when you say /etc/profile isn't sourced on Ubuntu -- that's because the default gnome-terminal profile doesn't run the shell as a login shell. There's a checkbox in the profile preferences dialog you can toggle to enable that.) -- 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/1406980 Title: /etc/profile does not get sourced when logging into a terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1406980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1341667] Re: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace
** Changed in: gnome-terminal (Ubuntu) Status: New => Opinion -- 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/1341667 Title: Ctrl+Backspace should send ^W instead of doing the same thing as Backspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1341667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406980] Re: /etc/profile does not get sourced when logging into a terminal window
Ubuntu's default ~/.bashrc (copied over from /etc/skel/.bashrc when you create new user accounts) overrides PS1 when $TERM is xterm*. When you open new terminal windows or tabs, bash sources /etc/bash.bashrc and then ~/.bashrc, and thus your global PS1 setting is overwritten. Do the change in ~/.bashrc instead of in /etc and you'll be fine. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/1406980 Title: /etc/profile does not get sourced when logging into a terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1406980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1356433] Re: detached tabs can not be reattached
Current versions of gnome-terminal (3.24 in Ubuntu 17.10) no longer allow you to detach and reattach tabs via drag and drop. Instead there's a context menu option that lets you detach tabs, but AFAICS there's no way to reattach them back. -- 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/1356433 Title: detached tabs can not be reattached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1356433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 978173] Re: $PATH not being honored
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- 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/978173 Title: $PATH not being honored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/978173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: terminal gets smaller when maximized and then restored
The bug is still present in 17.10. -- 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/1288655 Title: terminal gets smaller when maximized and then restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 932940] Re: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within
This seems fixed? I can open gnome-terminal, run cat, hit Ctrl+F1 and see ^[[1;5P ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Fix Released -- 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/932940 Title: gnome-terminal intercepts ctrl-f1 making it unusable for applications running within To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/932940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 989611] Re: terminal not working properly problem inside usr/bin
** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Incomplete -- 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/989611 Title: terminal not working properly problem inside usr/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/989611/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
I've just noticed that Debian carries a patch for reading the working directory from /proc if OSC 7 was not in use. This patch doesn't have the "let's look for $PWD in the environment" logic that was supposed to fix this bug. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 ** Bug watch added: Debian Bug tracker #712628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712628 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 902679] Re: Alt 1,2,etc does not change terminal page
** Summary changed: - Alt 1,2,etc does to change terminal page + Alt 1,2,etc does not change terminal page -- 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/902679 Title: Alt 1,2,etc does not change terminal page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/902679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 885148] Re: Spurious blank lines in gnome-terminal
I've seen this kind of problem when my disk was full. Since gnome- terminal stores the scrollback buffer in a (deleted) file in /tmp, when the disk fills up, scrollback gets lost. -- 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/885148 Title: Spurious blank lines in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/885148/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 792341] Re: gnome-terminal is sometimes not adding trailing slash when [Tab] used
Tab-completion is implemented by your shell (bash, most likely), not by gnome-terminal. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- 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/792341 Title: gnome-terminal is sometimes not adding trailing slash when [Tab] used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/792341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 282688] Re: patch adds ubuntu specific pref in global namespace
2017 update: - there's no gconf - there's no alternate_screel_scroll preference added by ubuntu patches - but there are some new transparency-related preferences added to the gsettings schema The current patch at https://patches.ubuntu.com/g/gnome-terminal/gnome- terminal_3.24.2-0ubuntu4.patch adds these preferences - use-transparent-background - use-theme-transparency - background-transparency-percent However I believe the same transparency patch is also shipped by Debian and Fedora, so an ubuntu prefix would not be appropriate. Perhaps this bug ought to be closed? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/282688 Title: patch adds ubuntu specific pref in global namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/282688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 263637] Re: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab
This is still a problem in Ubuntu 17.10, if your shell doesn't use OSC 7 to inform gnome-terminal about the current working directory. In theory /etc/profile.d/vte-2.91.sh should set it up automatically, but for some reason that doesn't happen for me. I think that reason is because in Ubuntu gnome-terminal doesn't launch login shells by default, and thus /etc/profile is ignored. I don't know why the commits from 2012 that are supposed to check $PWD do not work any more. Perhaps a newer version removed them, when the OSC 7 was deemed to be the correct solution? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/263637 Title: Gnome-terminal follows symbolic links instead of staying in the current directory when opening a new tab To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/263637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718371] [NEW] Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out"
Public bug reported: This morning unattended-upgrades had a reboot scheduled for 6:30 AM. The reboot process succeeded in turning off all network access but failed to actually reboot. As far as I can tell, this is because Sep 20 06:50:44 fridge systemd[1]: Starting Reboot... Sep 20 06:51:09 fridge systemctl[3886]: Failed to execute operation: Connection timed out Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Main process exited, code=exited, status=1/FAILURE Sep 20 06:53:54 fridge systemd[1]: Failed to start Reboot. Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Unit entered failed state. Sep 20 06:53:54 fridge systemd[1]: systemd-reboot.service: Failed with result 'exit-code'. (Don't ask me why it took 20 minutes to get to this point. Most everything was already shut down by 06:35.) After this the journal shows a few other random-looking service messages Sep 20 07:13:44 fridge systemd[1]: Stopping LVM2 metadata daemon... Sep 20 07:13:44 fridge systemd[1]: Stopped LVM2 metadata daemon. Sep 20 07:51:48 fridge systemd[1]: Started LVM2 metadata daemon. Sep 20 07:51:48 fridge systemd[1]: Stopped target Shutdown. and the end of a cron session that initiated the unattended-upgrade shutdown -r 06:30 call, presumably Sep 20 07:52:54 fridge CRON[1176]: pam_unix(cron:session): session closed for user root and then the machine sat idle waiting for keyboard input, which I provided in the form of Alt+SysRq+S,U,B a few hours later. This has never happened before on this server, which is running Ubuntu 16.04 LTS since November 2016. I haven't tried to reproduce this (yet). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Sep 20 11:10:34 2017 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-96-generic root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-11-07 (316 days ago) dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG33TL dmi.board.vendor: Intel Corporation dmi.board.version: AAD89517-803 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33TL:rvrAAD89517-803:cvn:ct2:cvr: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718371 Title: Reboot hangs forever because /bin/systemctl --force reboot fails with "Failed to execute operation: Connection timed out" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637519] Re: gnome-shell segfaults on resume, leaving my session unlocked
My notes indicate I saw this crash-leaving-helpfully-unlocked-session- after-resume at least 10 times in 16.10, but I don't remember seeing this (and my notes record no crashes) in 17.04. -- 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/1637519 Title: gnome-shell segfaults on resume, leaving my session unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1637519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=758302 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=758302 Importance: Unknown Status: Unknown -- 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/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
I restarted gnome-shell with Alt-F2 r and media keys started working. This is probably a duplicate of one of the other "media keys randomly stop working sometimes" bugs. I was searching for the particular error message and found none -- probably because the error message itself was only added relatively recently (in gnome-settings-daemon 3.20), while upstream tries to figure out what causes this bug. I haven't located the upstream bug report yet. ** Bug watch added: GNOME Bug Tracker #758302 https://bugzilla.gnome.org/show_bug.cgi?id=758302 -- 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/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839958 looks like a similar bug, except my custom shortcuts (e.g. t to launch gnome- terminal) continue to work fine. ** Bug watch added: Debian Bug tracker #839958 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839958 -- 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/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1659517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1659517] [NEW] media keys stopped working: "Could not find accelerator for accel id 123"
Public bug reported: Today after an involuntary reboot (laptop battery ran down) I can no longer use media keys like Mute, Volume Up/Down, PrintScreen. Every time I hit one of those keys I see messages like this in journalctl: Sau 26 11:53:30 platonas gnome-settings-[4972]: Could not find accelerator for accel id 123 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-settings-daemon 3.22.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 26 11:56:17 2017 InstallationDate: Installed on 2016-09-10 (138 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to yakkety on 2016-10-15 (102 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1659517 Title: media keys stopped working: "Could not find accelerator for accel id 123" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1659517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
Upstream thinks this is a GTK+ bug, hence I'm adding gtk+ to this bug. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=767588 Importance: Unknown Status: Unknown ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=767588 Importance: Unknown Status: Unknown ** No longer affects: gnome-terminal ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=769161 Importance: Unknown Status: Unknown -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
Could be https://bugzilla.gnome.org/show_bug.cgi?id=767588? -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
I wonder if this is https://bugzilla.gnome.org/show_bug.cgi?id=769161 or something else ** Bug watch added: GNOME Bug Tracker #769161 https://bugzilla.gnome.org/show_bug.cgi?id=769161 ** Bug watch added: GNOME Bug Tracker #767588 https://bugzilla.gnome.org/show_bug.cgi?id=767588 -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1331864] Re: [Patch] CRASH when dragging a tab and later changing its title
** Bug watch added: GNOME Bug Tracker #730389 https://bugzilla.gnome.org/show_bug.cgi?id=730389 ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=730389 Importance: Unknown Status: Unknown -- 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/1331864 Title: [Patch] CRASH when dragging a tab and later changing its title To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1331864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644102] Re: gnome-terminal crashes when you drab tags from one window to another
*** This bug is a duplicate of bug 1637333 *** https://bugs.launchpad.net/bugs/1637333 This is probably a duplicate of bug 1637333. ** This bug has been marked a duplicate of bug 1637333 gnome-terminal crashes when tab is dragged onto another tab's terminal area -- 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/1644102 Title: gnome-terminal crashes when you drab tags from one window to another To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1644102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644102] [NEW] gnome-terminal crashes when you drab tags from one window to another
Public bug reported: 1. Open a gnome-terminal window with two tabs 2. Open a second window, also with two tabs 3. Drag the 2nd tab of the 2nd window onto the rightmost part of the 1st window 4. Drag the 3rd tab of the 1st window back onto the 2nd window What happens: all terminal windows suddenly close. journalctl shows Lap 23 08:42:02 platonas gnome-terminal-[20261]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Lap 23 08:42:02 platonas gnome-terminal-[20261]: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (container)' failed Lap 23 08:42:02 platonas gnome-terminal-server[20261]: ** Lap 23 08:42:02 platonas gnome-terminal-server[20261]: Gtk:ERROR:/build/gtk+3.0-VoKwSM/gtk+3.0-3.20.9/./gtk/gtkwidget.c:5828:gtk_widget_get_frame_clock: assertion failed: (window != NULL) Lap 23 08:42:02 platonas gnome-terminal-[20261]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Lap 23 08:42:02 platonas gnome-terminal-[20261]: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (container)' failed Lap 23 08:42:05 platonas systemd[5628]: gnome-terminal-server.service: Main process exited, code=dumped, status=6/ABRT Lap 23 08:42:05 platonas systemd[5628]: gnome-terminal-server.service: Unit entered failed state. Lap 23 08:42:05 platonas systemd[5628]: gnome-terminal-server.service: Failed with result 'core-dump'. I've a /var/crash/_usr_lib_gnome-terminal_gnome-terminal- server.1000.crash but no system error dialog presented itself to me yet, so I'm filing this manually. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-terminal 3.20.2-1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 23 08:55:33 2016 InstallationDate: Installed on 2016-09-10 (73 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to yakkety on 2016-10-15 (38 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1644102 Title: gnome-terminal crashes when you drab tags from one window to another To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1644102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640541] Re: nautilus shows Windows Network but fails to open it
I've been unable to get network browsing to work even after installing samba and disabling the firewall. smbtree -N shows other servers and shares on the LAN, but Nautilus just shows the Opening... dialog without making any progress even after several minutes. (Accessing smb://server/share in Nautilus, OTOH, works fine even without apt installing samba and without disabling the firewall. If you know the name of the server and the share.). -- 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/1640541 Title: nautilus shows Windows Network but fails to open it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1640541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640541] [NEW] nautilus shows Windows Network but fails to open it
Public bug reported: 1. Open Nautilus 2. Click 'Other Locations' in the sidebar 3. Click 'Windows Network' Expectation: - a list of local servers with Samba shares Actual result: - nothing happens for a while, then a popup saying "Could not get list of shares from the server: No such file or directory" (I'm translating back from lt_LT) journalctl shows these errors: nautilus[8942]: Called "net usershare info" but it failed: Nepavyko paleisti antrinio proceso „net“ (Toks failas ar aplankas neegzistuoja) gvfsd[5799]: mkdir failed on directory /var/cache/samba: Permission denied gvfsd[5799]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Nepavyko iš serverio gauti viešinių sąrašo: Toks failas ar aplankas neegzistuoja The samba-common package is not installed (nautilus Recommends gvfs- backends which Suggests samba-common). It would be nice if Nautilus asked me to install samba-common via packagekit or something instead of just failing. (Although just 'samba-common' appears to be insufficient; I still can't browse the Windows Network in Nautilus after I 'apt install samba- common'.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 9 18:39:50 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x464+362+407'" InstallationDate: Installed on 2016-09-10 (60 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-15 (25 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1640541 Title: nautilus shows Windows Network but fails to open it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1640541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1418771] Re: gjs-console assert failure: *** Error in `/usr/bin/gjs-console': free(): invalid next size (fast): 0x00007f74a804b240 ***
** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1418771 Title: gjs-console assert failure: *** Error in `/usr/bin/gjs-console': free(): invalid next size (fast): 0x7f74a804b240 *** To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1418771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'
gdb in Ubuntu links against libpython3.4. The Python scripts in /usr/share/glib-2.0/gdb haven't been fully ported to Python 3: the custom iterators should define a '__next__' method alias pointing to 'next'. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdb (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1449389 Title: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1449389/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'
Somewhat-related upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=720635 ** Bug watch added: GNOME Bug Tracker #720635 https://bugzilla.gnome.org/show_bug.cgi?id=720635 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1449389 Title: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1449389/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449389] Re: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator'
Upstream bug with a patch: https://bugzilla.gnome.org/show_bug.cgi?id=749092 ** Bug watch added: GNOME Bug Tracker #749092 https://bugzilla.gnome.org/show_bug.cgi?id=749092 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1449389 Title: Python Exception class 'TypeError' iter() returned non-iterator of type '_iterator' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1449389/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381484] Re: Fails to connect to servers that disable SSLv3
I booted an Ubuntu 12.04 LTS desktop live session with testdrive, apt- get installed xchat-gnome version 1:0.30.0~git20110821.e2a400-0.2ubuntu4.2 and attempted to connect slack.com's IRC gateway. The connection was successful. ** Tags removed: removal-candidate verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1381484 Title: Fails to connect to servers that disable SSLv3 To manage notifications about this bug go to: https://bugs.launchpad.net/xchat-gnome/+bug/1381484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381484] Re: Fails to connect to servers that disable SSLv3
I can confirm that xchat-gnome 0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12.1 from your trusty- proposed works for me. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1381484 Title: Fails to connect to servers that disable SSLv3 To manage notifications about this bug go to: https://bugs.launchpad.net/xchat-gnome/+bug/1381484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381484] Re: Fails to connect to irc.slack.com with an SSL error
xchat-gnome 0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12.1~ppa1 from your PPA works for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1381484 Title: Fails to connect to irc.slack.com with an SSL error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1381484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381484] [NEW] Fails to connect to irc.slack.com with an SSL error
*** This bug is a security vulnerability *** Public security bug reported: slack.com is a chat service with optional IRC integration. Since today I can no longer connect to their IRC gateway using XChat-GNOME. The error is: * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas? which, translated from lt_LT, means * Cannot connect. Error: (336130315) error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Does the server/port really support SSL? I think this is part of the fallout of CVE-2014-3566 (aka POODLE). XChat-GNOME is trying to use the insecure SSL protocol version 3, and Slack, reasonably enough, rejects that. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 15 14:50:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-25 (811 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: xchat-gnome UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago) ** Affects: xchat-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages trusty ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3566 ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1381484 Title: Fails to connect to irc.slack.com with an SSL error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1381484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309419] [NEW] gnome-control-center segfaults on startup on 14.04
Public bug reported: Freshly upgraded to 14.04. Can't launch System Preferences: /usr/bin /gnome-control-center.real segfaults on startup. Here's a backtrace with debug symbols: mg@platonas: ~ $ gdb /usr/bin/gnome-control-center.real GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/bin/gnome-control-center.real...Reading symbols from /usr/lib/debug/.build-id/cd/f1f1cd11687a7829f674776af077f8700f7fd7.debug...done. done. (gdb) run Starting program: /usr/bin/gnome-control-center.real [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffeecf6700 (LWP 14214)] [New Thread 0x7fffee4f5700 (LWP 14215)] (gnome-control-center.real:14208): GLib-GObject-WARNING **: cannot derive 'GnomeControlCenter' from non-fundamental parent type 'CcShell' (gnome-control-center.real:14208): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (gnome-control-center.real:14208): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Program received signal SIGSEGV, Segmentation fault. 0x00409ee1 in gnome_control_center_show (center=0x0, app=0x7cc0f0) at gnome-control-center.c:1470 1470gnome-control-center.c: Toks failas ar aplankas neegzistuoja. (gdb) bt #0 0x00409ee1 in gnome_control_center_show (center=0x0, app=0x7cc0f0) at gnome-control-center.c:1470 #1 0x00407306 in application_command_line_cb (application=0x7cc0f0, command_line=optimized out, shell=0x0) at control-center.c:121 #2 0x71dc2adc in ffi_call_unix64 () at ../src/x86/unix64.S:76 #3 0x71dc240c in ffi_call (cif=cif@entry=0x7fffd750, fn=0x407160 application_command_line_cb, rvalue=0x7fffd6c0, avalue=avalue@entry=0x7fffd660) at ../src/x86/ffi64.c:522 #4 0x760a1bf8 in g_cclosure_marshal_generic (closure=0x7f6f00, return_gvalue=0x7fffd8a0, n_param_values=optimized out, param_values=optimized out, invocation_hint=optimized out, marshal_data=0x0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:1445 #5 0x760a13b8 in g_closure_invoke (closure=0x7f6f00, return_value=0x7fffd8a0, n_param_values=2, param_values=0x7fffd950, invocation_hint=0x7fffd8f0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768 #6 0x760b2d3d in signal_emit_unlocked_R (node=node@entry=0x758a00, detail=detail@entry=0, instance=instance@entry=0x7cc0f0, emission_return=emission_return@entry=0x7fffda20, instance_and_params=instance_and_params@entry=0x7fffd950) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3551 #7 0x760ba6f9 in g_signal_emit_valist (instance=optimized out, signal_id=optimized out, detail=optimized out, var_args=var_args@entry=0x7fffdae8) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3317 #8 0x760bace2 in g_signal_emit (instance=instance@entry=0x7cc0f0, signal_id=optimized out, detail=detail@entry=0) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:3363 #9 0x767f07f3 in g_application_call_command_line (application=0x7cc0f0, arguments=optimized out, options=optimized out, exit_status=0x7fffdcdc) at /build/buildd/glib2.0-2.40.0/./gio/gapplication.c:870 #10 0x767f2436 in g_application_real_local_command_line (application=0x7cc0f0, arguments=0x7fffdce0, exit_status=0x7fffdcdc) at /build/buildd/glib2.0-2.40.0/./gio/gapplication.c:924 #11 0x767f25ab in g_application_run (application=0x7cc0f0, argc=argc@entry=1, argv=argv@entry=0x7fffde38) at /build/buildd/glib2.0-2.40.0/./gio/gapplication.c:2084 #12 0x00407012 in main (argc=1, argv=0x7fffde38) at control-center.c:263 (gdb) thread apply all bt Thread 3 (Thread 0x7fffee4f5700 (LWP 14215)): #0 0x75892fbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x75dd1fe4 in g_main_context_poll (priority=2147483647, n_fds=2, fds=0x7fffe00010c0, timeout=-1, context=0x7fffe8011ac0) at
[Bug 1309419] Re: gnome-control-center segfaults on startup on 14.04
Trying to step through this with gdb. In main(), control-center.c:254 the following statement shell = gnome_control_center_new (); assigns NULL to shell, after emitting a few warnings: (gnome-control-center.real:653): GLib-GObject-WARNING **: cannot derive 'GnomeControlCenter' from non-fundamental parent type 'CcShell' (gnome-control-center.real:653): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (gnome-control-center.real:653): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed which then causes a segfault later, when it's dereferenced. -- 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/1309419 Title: gnome-control-center segfaults on startup on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1309419/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299903] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1299903 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1297271] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1297271 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1297271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301879] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1301879 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1301879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299189] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1299189 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1286805] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1286805 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1286805/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301881] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1301881 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1301881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1286525] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1286525 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1286525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1302585] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1302585 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1302585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1278209] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1278209 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1291984] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1291984 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1291984/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299105] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1299105 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1299105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292128] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1292128 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1292128/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301872] Re: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
*** This bug is a duplicate of bug 1309419 *** https://bugs.launchpad.net/bugs/1309419 ** This bug is no longer a duplicate of bug 1278209 gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() ** This bug has been marked a duplicate of bug 1309419 gnome-control-center segfaults on startup on 14.04 -- 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/1301872 Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1301872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
