[Bug 1855415] Re: cannot enable esm-infra for ubuntu 14, amd 64
This bug is now handled in the respective upstream repository here: https://github.com/canonical/ubuntu-advantage-client/issues/954 They plan to improve the behaviour described here, but as of 2020-06 haven't yet. So status "Fix Released" is not exactly true right now … ** Bug watch added: github.com/canonical/ubuntu-advantage-client/issues #954 https://github.com/canonical/ubuntu-advantage-client/issues/954 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855415 Title: cannot enable esm-infra for ubuntu 14, amd 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1855415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848549] [NEW] Gimp crashed randomly while using the stamp tool
Public bug reported: Not sure how helpful this will be, but GIMP instructed me to do these steps when it crashed. So here is the bug report. I was using the stamp tool on a relatively small (~800x1200 px) JPG image (without having added a transparency channel, if that is relevant). It worked for some time without any issue, until suddenly GIMP crashed on me. My system as per `lsb_release -rd`: ``` Description:Ubuntu 19.04 Release:19.04 ``` GIMP was installed from the latest available 19.04 package. Bug information as supplied in the GIMP crash dialog: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.60.4 (compiled against version 2.58.1) using GdkPixbuf version 2.38.1 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Aborted Stack trace: ``` # Stack traces obtained from PID 25593 - Thread 25593 # [New LWP 25595] [New LWP 25596] [New LWP 25597] [New LWP 25598] [New LWP 25599] [New LWP 25602] [New LWP 25603] [New LWP 25604] [New LWP 25605] [New LWP 25681] [New LWP 5641] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7ffc2f6673d0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7fc053dffe00 (LWP 25593) "gimp"__libc_read (nbytes=256, buf=0x7ffc2f6673d0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fc053659700 (LWP 25595) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fc052e58700 (LWP 25596) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fc052657700 (LWP 25597) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fc0508a3700 (LWP 25598) "gmain" 0x7fc055ae9729 in __GI___poll (fds=0x5585cc812710, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 6Thread 0x7fc04be12700 (LWP 25599) "gdbus" 0x7fc055ae9729 in __GI___poll (fds=0x5585cc82af10, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7fc035305700 (LWP 25602) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fc034b04700 (LWP 25603) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fc02700 (LWP 25604) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7fc02f7fe700 (LWP 25605) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7fc0137fe700 (LWP 25681) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fc0117fa700 (LWP 5641) "paint"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 12 (Thread 0x7fc0117fa700 (LWP 5641)): #0 0x7fc055aef2e9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fc055dd393f in g_cond_wait () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x5585cb17ecdd in () #3 0x7fc055db187d in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc055bce182 in start_thread (arg=) at pthread_create.c:486 ret =
[Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Ok, I meant "still present in Ubuntu 19.04" in the last comment :D Also worth mentioning: the "sudo modprobe i2c-i801" fix also restores the two-finger-tap right clicking behavior, which was also broken alongside two-finger scrolling. But there was no three-finger-tapping instead, so unlike the case how two-finger-scrolling broke. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
For Robin (brobert420), who in comment #69: > Commenting out blacklist i2c_i801 did end with mouse not working at all after > wakeup […]. I got an L440. Ubuntu 18.04 4.19rc1 I had the same problem with a ThinkPad T440s on Ubuntu 19.10 beta. (Just that there was no blacklist entry in /etc/modprobe.d/blacklist.conf so I used "modprobe i2c_i801" instead.) However, when I instead use the module name with a "-" instead of "_": modprobe i2c-i801 then it works immediately to restore two-finger scrolling, and two- finger scrolling keeps working after a suspend-and-resume cycle. In other news, this bug is still present in Ubuntu 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823683] Re: qterminal emulation type should be "default"
Thanks for testing! And yes, your're right. I tried installing qterminal in a fresh Ubuntu 19.10 installation, and also on my Ubuntu 18.10 system with: sudo apt purge qterminal && sudo apt install qterminal Both times, it would start with emulation type "default", as it should. So maybe I indeed just forgot what I did with qterminal before reporting this. Bit of an embarrassment :S Can be closed as invalid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823683 Title: qterminal emulation type should be "default" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1823683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823683] [NEW] qterminal emulation type should be "default"
Public bug reported: Currently after installing qterminal, its configuration settings are as follows: $TERM is "xterm-256color" and emulation type is "linux". This is a mismatch, as the key escape codes differ between the two (see output of "infocmp xterm-256color" vs. "infocmp linux"). As a result, the F1-F5 hotkeys will not work when starting a CLI program like byobu or mc in qterminal. I was advised by the qterminal maintainer that emulation type should be set to "default" initially, as only this one is in active development and the other emulation types will be eventually deprecated. For details, see: https://github.com/lxqt/qterminal/issues/551 -- System information: lsb_release -rd Description:Ubuntu 18.10 Release:18.10 apt-cache policy qterminal qterminal: Installed: 0.9.0-3ubuntu3 Candidate: 0.9.0-3ubuntu3 Version table: *** 0.9.0-3ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: qterminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823683 Title: qterminal emulation type should be "default" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1823683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814407] Re: gnome-terminal thinks it is byobu (under LXQt)
I should have included the file as well. Unlike for you, /usr/share/applications/byobu.desktop was a file on my system and not a symlink. And the content was different: cat /usr/share/byobu/desktop/byobu.desktop.old [Desktop Entry] Name=Byobu Terminal Comment=Advanced Command Line and Text Window Manager Icon=byobu Exec=gnome-terminal --app-id us.kirkland.terminals.byobu --class=us.kirkland.terminals.byobu -e byobu Type=Application Categories=GNOME;GTK;System;Utility;TerminalEmulator; StartupWMClass=us.kirkland.terminals.byobu X-GNOME-Gettext-Domain=byobu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814407 Title: gnome-terminal thinks it is byobu (under LXQt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1814407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814407] [NEW] gnome-terminal thinks it is byobu (under LXQt)
Public bug reported: This is a very similar case to "gnome-terminal thinks it's Byobu Terminal", see https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1512498 . Just that this time it does not affect the default Ubuntu desktop environment, but only LXQt, the Lubuntu 18.10 desktop environment which I installed on top of Ubuntu 18.10. (Since the byobu package is the same for Ubuntu, I though this would be the best place to report.) When typing gnome-terminal into the LXQt launcher (Alt+F2), gnome- terminal will appear with the byobu icon on it, and when executing gnome-terminal from there, byobu terminal will start instead. When moving the desktop file /usr/share/applications/byobu.desktop away, this behavior is instantly fixed. lsb_release -rd Ubuntu 18.10 apt-cache policy byobu 5.127-0ubuntu1 ** Affects: byobu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814407 Title: gnome-terminal thinks it is byobu (under LXQt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1814407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1230031] Re: dbus-daemon consumes 100% cpu without reason
To #11 Nicholas, I tried the solution Reuben proposed in #10 and installed the dbus trusty packages on Ubuntu 13.10 saucy. Since then, the problem with high CPU load has not appeared again (about a week now). So it seems to work. In particular, I installed the following: dbus_1.6.18-0ubuntu3_amd64.deb dbus-1-dbg_1.6.18-0ubuntu3_amd64.deb dbus-1-doc_1.6.18-0ubuntu3_all.deb dbus-x11_1.6.18-0ubuntu3_amd64.deb libdbus-1-3_1.6.18-0ubuntu3_amd64.deb libdbus-1-3_1.6.18-0ubuntu3_i386.deb libdbus-1-dev_1.6.18-0ubuntu3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1230031 Title: dbus-daemon consumes 100% cpu without reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1230031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
