[Bug 1793925] [NEW] a phantom onscreen keyboard appears that I cannot use
Public bug reported: when I enable screen keyboard either thru a keyboard shortcut or via the universal access menu there is a transparent square where the onscreen keyboard should be. Clicking on it does nothing. I also tried building the latest caribou with the same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caribou-antler 0.4.21-5 [modified: usr/lib/caribou/antler-keyboard usr/lib/python3/dist-packages/caribou/antler/antler_settings.py usr/share/dbus-1/services/org.gnome.Caribou.Antler.service usr/share/glib-2.0/schemas/org.gnome.antler.gschema.xml] ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 19:16:13 2018 InstallationDate: Installed on 2017-05-16 (494 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: caribou UpgradeStatus: Upgraded to bionic on 2018-09-01 (21 days ago) ** Affects: caribou (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1793925 Title: a phantom onscreen keyboard appears that I cannot use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1793925/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Following upstream suggestion ** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config (Ubuntu) -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793918] Re: Setting to enable suspend on lid-close with external monitors attached
** Description changed: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems - to have no effect anymore and seems to be removed in the current scheme. + to have no effect anymore and seems to be removed in the current scheme + (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. - - As a realy bad workaround I now prevent gsd-power from beeing loaded at - all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course - this have some unwanted side effect but better to have no suspend on - lid-close. -- 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/1793918 Title: Setting to enable suspend on lid-close with external monitors attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1793918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
>From the upstream report: "A possible explanation would be that gnome-settings-daemon is not handling one of the keys that it should be handling. And gnome-settings-daemon also disables the kernels handling of the RFKill keys at the same time. What you could do: Check which key is emitted using "xev" Check the low level key that is fired using "evemu-record" (you'll need to try different input devices) To be honest, the most likely explanation is that the following xkeyboard-config bugfix has not been merged into ubuntu yet: https://bugs.freedesktop.org/show_bug.cgi?id=100970, patch https://patchwork.freedesktop.org/patch/155965/ which should be in 2.24." And: "Just to make this clear. The above means that this is likely a downstream bug in Ubuntu which needs to upgrade (or patch) xkeyboard-config. i.e. if "XF86RFKill" is not mapped, then xkeyboard-config is outdated and the symptoms you describe fit perfectly." The "xev" output that I get is: KeyPress event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ** Bug watch added: freedesktop.org Bugzilla #100970 https://bugs.freedesktop.org/show_bug.cgi?id=100970 -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1571147] Re: package systemd-shim 9-1bzr2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** This bug has been marked a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug is no longer a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1571147 Title: package systemd-shim 9-1bzr2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1571147/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641438] Re: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** This bug is no longer a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641438 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793918] [NEW] Setting to enable suspend on lid-close with external monitors attached
Public bug reported: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme. This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. As a realy bad workaround I now prevent gsd-power from beeing loaded at all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course this have some unwanted side effect but better to have no suspend on lid-close. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Description changed: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme. This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. + + As a realy bad workaround I now prevent gsd-power from beeing loaded at + all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course + this have some unwanted side effect but better to have no suspend on + lid-close. -- 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/1793918 Title: Setting to enable suspend on lid-close with external monitors attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1793918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
As per analysis result in upstream report ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => New -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
In the upstream report for gnome-shell (https://gitlab.gnome.org/GNOME /gnome-shell/issues/555) some analysis steps were kindly provided. It seems that the actual cause is that gnome-settings-daemon's rfkill plugin fails to turn on airplane mode. Following the instructions, I can turn it on with the suggested test command: gdbus call --session --dest org.gnome.SettingsDaemon.Rfkill \ --object-path /org/gnome/SettingsDaemon/Rfkill \ --method org.freedesktop.DBus.Properties.Set \ org.gnome.SettingsDaemon.Rfkill AirplaneMode '' '' turns if off again. -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
Is this a bug in mutter that has been fixed ? As I'm wondering why this bug is still open for xdg-desktop-portal-gtk and if it can be closed ? -- 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/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793898] [NEW] Segfault (or weired action) when editing listview
Public bug reported: There is a video about bug: https://www.dropbox.com/s/cbrqbvxot8hfzh0/Valgrinding%20glade.mp4?dl=0 Full valgrind report: https://gist.github.com/v1993/8da84531b09594fb204b2c66cd882fa8 When mess begins, I usually get segfault when running without valgrind. Some bugs/leaks can be gtk+ and not glade ones. I use XUbuntu 18.04 with cinnamon, glade 3.22.1-1. ** Affects: glade-3 (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glade-3 in Ubuntu. https://bugs.launchpad.net/bugs/1793898 Title: Segfault (or weired action) when editing listview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade-3/+bug/1793898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630566] Re: Original message is not quoted when replying
And then it was working again after logout. Sorry. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/630566 Title: Original message is not quoted when replying To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/630566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630566] Re: Original message is not quoted when replying
Some years since this was fixed. Evolution was working just fine, then today when I click on Reply, the message body is completely empty. This happens with both HTML and Plain Text messages. Evolution 3.28.5 on Ubuntu 18.04 Any other info required, please ask and I will provide. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/630566 Title: Original message is not quoted when replying To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/630566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792807] Re: Login screen freeze
I've solved it for me now with a new graphics card. Couldn't bare the nomodeset anymore knowing there was an alternative solution. Imagine how much I am attached to Ubuntu to rather buy a new graphics card then to switch to another OS ;-). We can keep it open if you want further investigation and it might help with others. For me personally it is solved with the new graph card, so it can be closed as well. Up to you :-) -- 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/1792807 Title: Login screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIA happens right after logging out and getting in again. But GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. Thank you for fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIABut GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Sorry, I pressed wrong key!!! I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIA happens right after logging out and getting in again. But GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. Thank you for fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792208] Re: nautilus 3.30 for cosmic in universe repro
*** This bug is a duplicate of bug 1786492 *** https://bugs.launchpad.net/bugs/1786492 No, sorry. We're not going to offer two different versions of nautilus in the Ubuntu package archives. Someone could make it available in a PPA. ** This bug has been marked a duplicate of bug 1786492 Update to nautilus 3.28 or newer -- 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/1792208 Title: nautilus 3.30 for cosmic in universe repro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792208/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto I was assuming that this should also work with sddm (on Kubuntu), but apparently not out of the box. Is there already something to test there? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Proposed solution:
As the stacktrace below shows the problem is caused by module
cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by
default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture
2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error
is not set to NULL by the call to cogl_error_free (because the parameter is a
copy).
Then module tries to allocate a slice with max_waste -1. This also fails,
causing error "Sliced texture size of 2560 x 1024 not possible with max waste
set to -1".
Module cogl_set_error complains about the skip_error not being NULL with
message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at
cogl_texture_new_with_size, that in this way tries to free the same memory
twice. This causes the crash "double free or corruption (fasttop)", unless by
accident the same memory-address is allocated again.
To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
unsigned int height,
CoglTextureFlags flags,
CoglPixelFormat internal_format)
{
CoglTexture *tex;
CoglError *skip_error = NULL;
_COGL_GET_CONTEXT (ctx, NULL);
if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
(cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
{
/* First try creating a fast-path non-sliced texture */
tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));
_cogl_texture_set_internal_format (tex, internal_format);
if (!cogl_texture_allocate (tex, _error))
{
cogl_error_free (skip_error);
skip_error = NULL;
This solution is tested and solves the problem during startup and for right
corner click.
Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
#0 0xb7ef9d41 in __kernel_vsyscall ()
#1 0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at
../sysdeps/unix/sysv/linux/internal-signals.h:84
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#2 0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#3 0xb6a382b6 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb7996077 ,
sa_sigaction = 0xb7996077 }, sa_mask = {__val = {3080956952,
3060745084, 3080120357, 3217787880, 3060745084, 3217788000, 32868, 20347328, 0,
28984448, 2237142784, 3060745084, 3080120310, 3080956952, 3080956952,
3217788408, 1024, 31097824, 3080018485, 3060691022, 16, 3060756628, 0, 3, 4096,
3065078356, 2, 3066019840, 4096, 3217788168, 3064530671, 0}}, sa_flags = 4096,
sa_restorer = 0x3}
sigs = {__val = {32, 0 }}
#4 0xb6a9074c in __libc_message (action=do_abort, fmt=) at
../sysdeps/posix/libc_fatal.c:181
ap =
fd = 2
list =
nlist =
cp =
written =
#5 0xb6a975dd in malloc_printerr (str=str@entry=0xb6ba525c "double free or
corruption (fasttop)") at malloc.c:5336
#6 0xb6a98e6f in _int_free (av=, p=,
have_lock=) at malloc.c:4216
idx = 6
old =
old2 =
size =
fb =
nextchunk =
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#7 0xb7954290 in g_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#8 0xb7938c53 in g_error_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#9 0xb66d7058 in cogl_error_free (error=0x16cba70) at cogl-error.c:45
#10 0xb66db62c in cogl_texture_new_with_size (width=2560, height=1024,
flags=COGL_TEXTURE_NO_SLICING, internal_format=COGL_PIXEL_FORMAT_RGBA__PRE)
at deprecated/cogl-auto-texture.c:121
tex = 0x1da83e0
skip_error = 0x16cba70
ctx =
#11 0xb6e9a618 in clutter_offscreen_effect_real_create_texture
(effect=0x23c3b00,
[Bug 1793873] [NEW] document in \Templates does not show up on right click in Nautilus
Public bug reported: A Text Document (empty one) in \Templates does not show up on right click in Nautilus, I tried many locations. michal:~$ ls -ltr ~/Templates/ total 0 -rw-r--r-- 1 michal michal 0 Sep 14 08:49 text I just see in Right click: New Folder Paste Select All Properties Open in Terminal Restore Missing Files... I have michal@Beast:~$ apt list | grep nautil clamtk-nautilus/bionic,bionic,bionic,bionic 5.25-1 all easytag-nautilus/bionic,bionic 2.4.3-4 amd64 gir1.2-nautilus-3.0/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed,automatic] libnautilus-extension-dev/bionic 1:3.26.3-0ubuntu4 amd64 libnautilus-extension1a/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus-admin/bionic,bionic,bionic,bionic 1.1.3-1 all nautilus-compare/bionic,bionic,bionic,bionic,now 0.0.4+po1-1 all [installed] nautilus-data/bionic,bionic,now 1:3.26.3-0ubuntu4 all [installed] nautilus-dropbox/bionic 2015.10.28-1ubuntu2 amd64 nautilus-emblems/bionic,bionic,bionic,bionic 0.3.1-3 all nautilus-extension-brasero/bionic,bionic 3.12.1-4ubuntu2 amd64 nautilus-extension-burner/bionic,bionic 3.0.4-0ubuntu1 amd64 nautilus-extension-gnome-terminal/bionic-updates,now 3.28.2-1ubuntu1~18.04.1 amd64 [installed,automatic] nautilus-filename-repairer/bionic,bionic 0.2.0-1 amd64 nautilus-gtkhash/bionic,bionic 1.1.1-2 amd64 nautilus-hide/bionic,bionic,bionic,bionic 0.2.3-2 all nautilus-ideviceinfo/bionic,bionic 0.1.0-0ubuntu14 amd64 nautilus-image-converter/bionic,bionic 0.3.1~git20110416-2 amd64 nautilus-owncloud/bionic,bionic,bionic,bionic 2.4.1+dfsg-1 all nautilus-script-audio-convert/bionic,bionic,bionic,bionic 0.3.1.1-0ubuntu6 all nautilus-script-collection-svn/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-debug/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-manager/bionic,bionic,bionic,bionic 0.0.5-0ubuntu5 all nautilus-scripts-manager/bionic,bionic,bionic,bionic 2.0-1 all nautilus-sendto/bionic,now 3.8.6-2 amd64 [installed] nautilus-share/bionic,now 0.7.3-2ubuntu3 amd64 [installed] nautilus-wipe/bionic,bionic 0.3-1 amd64 nitroshare-nautilus/bionic,bionic,bionic,bionic 0.3.3-1 all python-nautilus/bionic,bionic,now 1.1-6 amd64 [installed,automatic] rabbitvcs-nautilus/bionic,bionic,bionic,bionic 0.16-1.1 all seahorse-nautilus/bionic,bionic 3.11.92-2 amd64 subliminal-nautilus/bionic,bionic,bionic,bionic 1.1.1-2 all tortoisehg-nautilus/bionic,bionic,bionic,bionic 4.5.2-0ubuntu1 all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 06:45:44 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-27 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-03 (18 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793873 Title: document in \Templates does not show up on right click in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793873/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1742542] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1742542 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760499] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1760499 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736512] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1736512 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1737501] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1737501 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1737501/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791502] Re: libpam-mount : copy problem with small files
Hi, This bug affects others Linux distributions like Fedora 28 Workstation, Manjaro XFCE Edition (17.1.12). Could it be a GTK library problem ? Kind regards. -- 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/1791502 Title: libpam-mount : copy problem with small files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792208] Re: nautilus 3.30 for cosmic in universe repro
** Tags added: upgrade-software-version -- 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/1792208 Title: nautilus 3.30 for cosmic in universe repro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792208/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769838] Re: Input source options does not work on Bionic with gnome-flashback
Hi Łukasz, now it should be better. ** Description changed: [Impact] * An explanation of the effects of the bug on users and: Setting the 'Input Source Options' to 'Allow different sources for each window' does not work. * justification for backporting the fix to the stable release: This is a bug in Ubuntu Bionic's version of gnome-flashback (3.28) (because the GUI lets the user change the input source option but the backend does nothing) [Test Case] * detailed instructions how to reproduce the bug - Set Input Source Options to Allow different sources for each window in gnome-control-center -> Region & Language -> Options - Realize that if you set different layouts for different windows it does not change automatically when changing windows. [Regression Potential] - * discussion of how regressions are most likely to manifest as a result - of this change: + * Metacity now ignores its own events when predicting focus changes. Its + own events are recognized by comparing timestamps and serial numbers. If + something potentially goes wrong, it can either not ignore its own + events, or ignore external events. In both cases the focus prediction + will be broken. Also there could be potentially a race condition, but + the patch protects against it by making a dummy request with bumped + serial number. (Note: the second metacity patch is an amendment for the + first one, so the previous analysis applies to both patches.) - This bug itself is a regression, because it was working in Ubuntu - Trusty. + * GNOME-Flashback has some new code for handling per-window input + sources. The change_per_window_source() function returns early if the + sources_per_window option (obtained from GSettings: org.gnome.desktop + .input-sources per-window) is false. As that option is false by default, + in the default configuration most of the new code won't be executed at + all. The potential breakage may happen if it is set to true. Such + potential breakage includes: wrong input sources handling (it was wrong + before anyway), gnome-flashback crashes. The patches are already applied + in Cosmic, and currently no crashes are reported against the Cosmic + version of gnome-flashback on errors.ubuntu.com. [Other Info] This needs fixes in both gnome-flashback and metacity. Here are the relevant commits in gnome-3-28 branches: https://gitlab.gnome.org/GNOME/metacity/commit/b96341dabffc3589 (ensure that we ignore our own focus events for focus predictions) https://gitlab.gnome.org/GNOME/metacity/commit/9956d376d38d0ad6 (fix problems with focus tracking) https://gitlab.gnome.org/GNOME/gnome-flashback/commit/3c4c6ecddef48cd5 (implement per window input sources) The gnome-session-flashback dependency on metacity will be bumped. ** Summary changed: - Input source options does not work on Bionic with gnome-flashback + Per-window input sources option does not work on Bionic with gnome-flashback -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1769838 Title: Per-window input sources option does not work on Bionic with gnome- flashback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1769838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
I'm finding the same symptoms from gnome-shell, relatively high cpu use by gnome-shell with all extenstions deisabled (if I turn on extensions the cpu usages is ridiculous high, in the range of 20-50%). I checked strace as above and am finding the same high number of errors from the recvmsg call: strace: Process 1321 detached % time seconds usecs/call callserrors syscall -- --- --- - - 39.281.151799 7168623145929 recvmsg 24.300.712624 14 52590 poll 12.080.354380 9 41109 ioctl 8.010.234871 12 18865 writev 6.370.186740 7 26188 write 4.180.122557 5 23811 getpid 2.650.077663 7 11653 read 1.260.036853 5 7852 mprotect -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
