Seems to be related to glib 2.80:
https://gitlab.gnome.org/GNOME/gimp/-/issues/10785
From a comment on a duplicate issue
(https://gitlab.gnome.org/GNOME/gimp/-/issues/11427) the fix will be in
GIMP 2.10.38.
** Bug watch added: gitlab.gnome.org/GNOME/gimp/-/issues #10785
/org/mate/desktop/sound/input-feedback-sounds actually fixed it for me
(not /org/gnome).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970047
Title:
GTK file open dialog hangs Chrome/Brave
To
input-feedback-sounds was already set to 'false' for me - explicitly
setting it unfortunately did not seem to make a difference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970047
Title:
GTK
I tried running google-chrome against "stock" gtk-3 built similar to
follows:
sudo apt build-dep libgtk-3-0
apt source libgtk-3-0
cd gtk+3.0-3.24.33
quilt pop -a
rm debian/patches/series
rm debian/*.symbols
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -uc -us -d -j16
Also tried building with
Also seeing this on various versions of the official google-chrome .deb
(99, 100, 101) on 22.04/amd64 (MATE Desktop, Xorg + nvidia proprietary
470.103.01, marco window manager + compton compositor).
Browser is unresponsive to any input events after downloading a file or
printing to file (i.e.
Also affected by this with BTRFS filesystem on EFI. The patch which
introduced the behavior change was titled quick-boot-lvm.patch, not
slow-boot-btrfs.patch ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe it had to do with the patch debian/patches/quick-boot-
lvm.patch as described here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1800722
Here's what I wrote in a comment (#12) there a couple days ago:
Seeing a regression here on 18.10/amd64 with 2.02+dfsg1-5ubuntu8.1 using
Seeing a regression here on 18.10/amd64 with 2.02+dfsg1-5ubuntu8.1 using
EFI+btrfs boot volume. No LVM used, just GPT on NVMe.
Regardless of my settings in /etc/default/grub, the boot wait is now 30
seconds.
Relevant settings:
GRUB_HIDDEN_TIMEOUT=1
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=0
another fix for this applet: mate-bluetooth-sendto is getting passed double
quotes via sendto_callback in applet/main.c
this is causing obex-client to try to send to 00:00:00:00:00:00 instead of the
intended mac. dbus shows:
method call sender=:1.81 - dest=org.openobex.client serial=10 path=/;
** Patch added: don't remove xdg autostart entries
https://bugs.launchpad.net/linuxmint/+bug/1005649/+attachment/3624901/+files/xdg-autostart.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
a couple more fixes, these relate to mate-user-share receiving files
over bluetooth.
in mate-user-share/src/user_share.c, the wrong variable is being passed as a
gsettings pointer to the disabled_timeout_callback.
this only shows up if '/org/mate/desktop/file-sharing/enabled' isn't set (eg.
nevermind on the notification error, for some reason notification-daemon wasn't
starting on my system. works fine :)
-matt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005649
Title:
bluetooth
hey,
this issue came up and was fixed in ubuntu gnome a while ago, see #429523
the fix is in
https://launchpad.net/ubuntu/+archive/primary/+files/gnome-bluetooth_2.30.0-1ubuntu2.diff.gz
(sloppy) patch is attached against debian-packages.git
confirmed working w/patch on Ubuntu 12.10 / mate 1.6
thanks. the patch mentioned, 86b1e8dd83cbb0fcbf3d61d2b461df8be1f528cf,
currently available at https://patchwork.kernel.org/patch/485751/ fixes the
issue. i've attached the patch also.
-matt
** Patch added: x86: Make relocatable kernel work with new binutils
thanks jools. hopefully this won't be an issue in natty. i'll find out in the
next week.
-matt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673236
Title:
maverick toolchain producing unbootable
yes, this is still an issue. i've been compiling kernels in a lucid
chroot as noted in previous posts. this issue did not present itself
using squeeze/amd64 and compiling 2.6.36.2. it may be limited to 32bit
x86.
-matt
--
You received this bug notification because you are a member of Ubuntu
also, i'm a little unclear as to why this was marked as being invalid,
without any comment or explanation. if it's not a problem with binutils,
please explain why, and what is necessary to have upstream vanilla
kernels build properly.
thanks,
-matt
** Changed in: binutils (Ubuntu)
hey jamie,
thanks for bringing those changes to light. please do post the patch.
-matt
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i tested with debian experimental (2.20.90.20101105-1) in lucid chroot
with same results.
i've attached a very minimal .config for 2.6.36 that results in a hang
at 'Calibrating delay loop...' when run like: qemu -cpu coreduo -m 512M
-kernel arch/x86/boot/bzImage -s
unsetting CONFIG_RELOCATABLE
this actually seems to be directly related to the maverick binutils
package, binutils_2.20.51.20100908-0ubuntu2_i386.deb
replacing lucid's binutils with this inside a chroot causes the same
boot failures with CONFIG_RELOCATABLE=y, when used alongside the rest of
lucid's toolchain.
-matt
--
further investigation shows that maverick binutils is more likely the
culprit than maverick gcc.
** Package changed: gcc-4.4 (Ubuntu) = binutils (Ubuntu)
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification
brief testing of natty's binutils_2.20.90.20101105-0ubuntu1_i386.deb
shows the bug is also present there.
-matt
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a member of Ubuntu
Bugs, which
after some further narrowing of kernel config, it appears that
'CONFIG_RELOCATABLE=y' is causing the kernel to become unbootable with
maverick's 32bit toolchain. unsetting this parameter produces a bootable
kernel on maverick. again, lucid toolchain produces bootable kernels
with or without
Public bug reported:
Binary package hint: gcc-4.4
when attempting to compile recent vanilla kernels from source (2.6.35.7,
2.6.35.8, 2.6.36), the resulting bzImages all hang at the same point in
the boot process. this doesn't seem to be an error with the kernel
config or source, because using
** Attachment added: 2.6.36 .config resulting in hanging kernel
https://bugs.launchpad.net/bugs/673236/+attachment/1728348/+files/.config
--
maverick toolchain producing unbootable (hanging) kernels
https://bugs.launchpad.net/bugs/673236
You received this bug notification because you are a
michel that is a great solution and worked for me (separate /var
filesystem).
there is one thing missing though:
mkdir /.ureadahead/debugfs
-matt
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member
*** This bug is a duplicate of bug 404218 ***
https://bugs.launchpad.net/bugs/404218
initial tests with '0.12.8-0ubuntu6' indicate that the problem is now
fixed in the repos.
-matt
--
Music residing on GVFS mounted SMB shares won't be imported
https://bugs.launchpad.net/bugs/559658
You
*** This bug is a duplicate of bug 404218 ***
https://bugs.launchpad.net/bugs/404218
i rebuild rhythmbox, with the patch applied, and the i386 .deb produced
imported my library without issue. no segfaults encountered here.
-matt
--
Music residing on GVFS mounted SMB shares won't be
i've checked the gnome bugzilla and there doesn't seem to be anything
regarding this issue posted there. if someone already has a gnome
bugzilla account, maybe they could post some info on this bug there. the
url is https://bugzilla.gnome.org/simple-bug-guide.cgi?product=rhythmbox
or, if the bug
still exists in 0.12.8-0ubuntu4
-matt
--
Music residing on GVFS mounted SMB shares won't be imported
https://bugs.launchpad.net/bugs/559658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
i can verify this in 10.04/i386 desktop. smb:// uris seem to work
without issue in totem, however in rhythmbox, nothing happens. i've
attached what is likely a redundant rb-debug.txt.
i see that '0.12.8-0ubuntu4' is pending, but i don't see any mention of
this issue in the changes made there.
31 matches
Mail list logo
