[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
Issue was due to .XCompose beeing too long (40K Lines). [mirror for the file](https://github.com/rvaiya/keyd/blob/master/data/keyd.compose) (careful, `cat` does not display it fully, use `vim`) GTK3 could handle it without issue. GTK4 crash in the unexpected mannger described above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: New Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
culprit seems to be keyd https://github.com/rvaiya/keyd/issues/537 ** Bug watch added: github.com/rvaiya/keyd/issues #537 https://github.com/rvaiya/keyd/issues/537 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: New Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
here is the list of gtk4 package installed on my machine, maybe there is something wrong with them ? $ apt list | grep -i "gtk4\|gtk-4" awf-gtk4/jammy 2.5.0-5 amd64 fcitx5-frontend-gtk4/jammy 5.0.12-1 amd64 gir1.2-gtk-4.0/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed,automatic] gir1.2-gtk-4.0/jammy-updates 4.6.6+ds-0ubuntu1 i386 gir1.2-javascriptcoregtk-4.0/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] gir1.2-javascriptcoregtk-4.0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 gir1.2-javascriptcoregtk-4.1/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 gir1.2-javascriptcoregtk-4.1/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 gir1.2-xdpgtk4-1.0/jammy 0.6-2 amd64 gtk-4-examples/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed] gtk-4-examples/jammy-updates 4.6.6+ds-0ubuntu1 i386 gtk-4-tests/jammy-updates 4.6.6+ds-0ubuntu1 amd64 gtk-4-tests/jammy-updates 4.6.6+ds-0ubuntu1 i386 ibus-gtk4/jammy 1.5.26-4 amd64 ibus-gtk4/jammy 1.5.26-4 i386 libdbusmenu-gtk4/jammy 16.04.1+18.10.20180917-0ubuntu8 amd64 libfm-gtk4/jammy 1.3.2-1 amd64 libgtk-4-1/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed,automatic] libgtk-4-1/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-bin/jammy-updates 4.6.6+ds-0ubuntu1 amd64 libgtk-4-bin/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-common/jammy-updates,jammy-updates,now 4.6.6+ds-0ubuntu1 all [installed,automatic] libgtk-4-dev/jammy-updates,now 4.6.6+ds-0ubuntu1 amd64 [installed] libgtk-4-dev/jammy-updates 4.6.6+ds-0ubuntu1 i386 libgtk-4-doc/jammy-updates,jammy-updates 4.6.6+ds-0ubuntu1 all libgtk-4-media-gstreamer/jammy-updates 4.6.6+ds-0ubuntu1 amd64 libgtk-4-media-gstreamer/jammy-updates 4.6.6+ds-0ubuntu1 i386 libjavascriptcoregtk-4.0-18/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] libjavascriptcoregtk-4.0-18/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.0-bin/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.0-bin/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libjavascriptcoregtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libjavascriptcoregtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libportal-gtk4-1/jammy 0.6-2 amd64 libportal-gtk4-dev/jammy 0.6-2 amd64 libportal-tests-gtk4/jammy,jammy 0.6-2 all librust-gtk4-macros-dev/jammy 0.3.1-1 amd64 librust-gtk4-sys-dev/jammy 0.3.1-1 amd64 libswt-cairo-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-glx-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-gtk-4-java/jammy 4.20.0-2 amd64 libswt-gtk-4-jni/jammy 4.20.0-2 amd64 libswt-webkit-gtk-4-jni/jammy 4.20.0-2 amd64 libwebkit2gtk-4.0-37/jammy-updates,jammy-security,now 2.38.6-0ubuntu0.22.04.1 amd64 [installed,automatic] libwebkit2gtk-4.0-37/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.0-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.0-doc/jammy-updates,jammy-updates,jammy-security,jammy-security 2.38.6-0ubuntu0.22.04.1 all libwebkit2gtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.1-0/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 libwebkit2gtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 amd64 libwebkit2gtk-4.1-dev/jammy-updates,jammy-security 2.38.6-0ubuntu0.22.04.1 i386 python3-wxgtk4.0/jammy 4.0.7+dfsg-13build1 amd64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted.
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
it seems to be an issue with gtk 4. $ sudo apt install gtk-4-examples $ gtk4-demo-application the demo app gives me the same error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
the message above says `fix released`. Where can I find the fix ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2027571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
I do not have a ` ~/.config/gtk-4.0/Compose file` file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GTK+: Unknown Status in gtk4 package in Ubuntu: New Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2027571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007317] [NEW] PCI/internal sound card not detected
Public bug reported: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007317 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: After updating Ubuntu 22.04.1 LTS from kernel 5.15.0-58 to 5.15.0-60 all audio in and out was lost. Using grub to boot to the previous kernel (5.15.0-58) restored proper audio functionality. So the problem appears to be associated with the new kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:rreed 1481 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 17:07:09 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to jammy on 2022-06-27 (232 days ago) dmi.bios.date: 09/18/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: Z370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd09/18/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370NWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370N WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993651] [NEW] Schema validator reports the wrong child element as missing
Public bug reported:
Here's the repro script:
#!/usr/bin/env python3
import sys
from lxml import etree
XSD = """\
http://www.w3.org/2001/XMLSchema;>
"""
XML = """\
Guido
TechnicalBackup
"""
print("%-20s: %s" % ('Python', sys.version_info))
print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION))
print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION))
print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION))
print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION))
print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION))
schema = etree.XMLSchema(etree.fromstring(XSD))
doc = etree.fromstring(XML)
if not schema.validate(doc):
print(schema.error_log)
# END OF REPRO SCRIPT
Here's the output:
Python : sys.version_info(major=3, minor=10, micro=6, releaselevel='final',
serial=0)
lxml.etree : (4, 9, 1, 0)
libxml used : (2, 9, 14)
libxml compiled : (2, 9, 14)
libxslt used : (1, 1, 35)
libxslt compiled : (1, 1, 35)
:1:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'Person': Missing
child element(s). Expected is ( Role ).
# END OF OUTPUT
It's clear from examining the schema and the XML document being
validated that adding a second Role element is not necessary, and would
do nothing to make the document valid. The correct assessment of the
validation is that the required Details child element is missing.
** Affects: libxml2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1993651
Title:
Schema validator reports the wrong child element as missing
Status in libxml2 package in Ubuntu:
New
Bug description:
Here's the repro script:
#!/usr/bin/env python3
import sys
from lxml import etree
XSD = """\
http://www.w3.org/2001/XMLSchema;>
"""
XML = """\
Guido
TechnicalBackup
"""
print("%-20s: %s" % ('Python', sys.version_info))
print("%-20s: %s" % ('lxml.etree', etree.LXML_VERSION))
print("%-20s: %s" % ('libxml used', etree.LIBXML_VERSION))
print("%-20s: %s" % ('libxml compiled', etree.LIBXML_COMPILED_VERSION))
print("%-20s: %s" % ('libxslt used', etree.LIBXSLT_VERSION))
print("%-20s: %s" % ('libxslt compiled', etree.LIBXSLT_COMPILED_VERSION))
schema = etree.XMLSchema(etree.fromstring(XSD))
doc = etree.fromstring(XML)
if not schema.validate(doc):
print(schema.error_log)
# END OF REPRO SCRIPT
Here's the output:
Python : sys.version_info(major=3, minor=10, micro=6, releaselevel='final',
serial=0)
lxml.etree : (4, 9, 1, 0)
libxml used : (2, 9, 14)
libxml compiled : (2, 9, 14)
libxslt used : (1, 1, 35)
libxslt compiled : (1, 1, 35)
:1:0:ERROR:SCHEMASV:SCHEMAV_ELEMENT_CONTENT: Element 'Person':
Missing child element(s). Expected is ( Role ).
# END OF OUTPUT
It's clear from examining the schema and the XML document being
validated that adding a second Role element is not necessary, and
would do nothing to make the document valid. The correct assessment of
the validation is that the required Details child element is missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1993651/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 > For me, on Ubuntu 22.04, when I try to save a file, and then try to rename that file, As soon as I start typing, it moves to the Search field in the File Save As dialog. Me too. This makes the Save As dialog almost unusable as the filename box loses focus on every character typed. I am using i3 window manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This issue is still existing after the fresh installation on raspberry pi 4 8GB desktop. ** Attachment added: "Screenshot from 2022-05-25 00-06-30.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+attachment/5593004/+files/Screenshot%20from%202022-05-25%2000-06-30.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1955594] Re: "Show Applications" does not permit scrolling through installed apps.
Daniel, I have found an additional clue in the "no scrolling in the Apps menu" issue when the display fractional scaling is set to 125%. After a lot more mucking about with the settings, I found that the problem appears only when I use a specific setting is enabled in the Universal Access control panel. In that control panel, you have the option to "Always Show Universal Access Menu" - which puts the Universal Access menu item up in the menu bar. When I enable "Large Text" in that menu bar item, that is when the 125% fractional scaling setting causes the Applications window to stop scrolling. Interestingly, when you go to the Universal Access control panel and set "Large Text" it causes in-app text to be scaled up, but when you go to the Universal Access item up in the menu bar and set "Large Text" it causes menu bar text and text under icons to increase in size, but doesn't affect in-app text size. I expect this is normal behavior, but only setting "Large Text" in the menu bar item causes this issue. I know this a bit convoluted. I hope the info I have provided is understandable. Bob Reed Get BlueMail <https://bluemail.me/download> for Linux Daniel van Vugt wrote: ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New ** Summary changed: - "Show Applications" does not permit scrolling through installed apps. + "Show Applications" does not permit scrolling through installed apps when scale == 125% -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1955594 <https://bugs.launchpad.net/bugs/1955594> Title: "Show Applications" does not permit scrolling through installed apps when scale == 125% Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When I select "Show Applications" to view all installed apps in Gnome on Ubuntu 20.04.3 LTS, the window does not allow me to scroll through the installed applications. After doing some testing, I discovered that this is related to me having "Fractional Scaling" enabled with a setting of 125% in the display settings. I am using a 4K display and use this setting to make windows and text appear larger on the screen. If I set the scaling to 100% or simply disable Fractional Scaling, I am able to scroll through the list of installed apps normally. All other fractional scaling settings (100%, 150%, 175% and 200%) work perfectly. Only 125% is affected. For reference, my display resolution is set to 3840x2180 @ 60Hz. It is kind of late in the life of this release to do much about this, but I thought I should pass this info along. Bob Reed Westminster, Maryland USA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1955594/+subscriptions <https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1955594/+subscriptions> -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1955594 Title: "Show Applications" does not permit scrolling through installed apps when scale == 125% Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When I select "Show Applications" to view all installed apps in Gnome on Ubuntu 20.04.3 LTS, the window does not allow me to scroll through the installed applications. After doing some testing, I discovered that this is related to me having "Fractional Scaling" enabled with a setting of 125% in the display settings. I am using a 4K display and use this setting to make windows and text appear larger on the screen. If I set the scaling to 100% or simply disable Fractional Scaling, I am able to scroll through the list of installed apps normally. All other fractional scaling settings (100%, 150%, 175% and 200%) work perfectly. Only 125% is affected. For reference, my display resolution is set to 3840x2180 @ 60Hz. It is kind of late in the life of this release to do much about this, but I thought I should pass this info along. Bob Reed Westminster, Maryland USA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1955594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1955594] Re: "Show Applications" does not permit scrolling through installed apps.
Daniel, I tried what you suggested and found that disabling the Ubuntu Dock extension does resolve the scrolling issue at 125% scale. Robert Reed Get BlueMail <https://bluemail.me/download> for Linux Daniel van Vugt wrote: Please try disabling 'Ubuntu Dock' in the Extensions app. Then please Super+A. Does the bug still occur at 125% scale? ** Tags added: xrandr-scaling ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1955594 <https://bugs.launchpad.net/bugs/1955594> Title: "Show Applications" does not permit scrolling through installed apps. Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I select "Show Applications" to view all installed apps in Gnome on Ubuntu 20.04.3 LTS, the window does not allow me to scroll through the installed applications. After doing some testing, I discovered that this is related to me having "Fractional Scaling" enabled with a setting of 125% in the display settings. I am using a 4K display and use this setting to make windows and text appear larger on the screen. If I set the scaling to 100% or simply disable Fractional Scaling, I am able to scroll through the list of installed apps normally. All other fractional scaling settings (100%, 150%, 175% and 200%) work perfectly. Only 125% is affected. For reference, my display resolution is set to 3840x2180 @ 60Hz. It is kind of late in the life of this release to do much about this, but I thought I should pass this info along. Bob Reed Westminster, Maryland USA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955594/+subscriptions <https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955594/+subscriptions> -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1955594 Title: "Show Applications" does not permit scrolling through installed apps. Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I select "Show Applications" to view all installed apps in Gnome on Ubuntu 20.04.3 LTS, the window does not allow me to scroll through the installed applications. After doing some testing, I discovered that this is related to me having "Fractional Scaling" enabled with a setting of 125% in the display settings. I am using a 4K display and use this setting to make windows and text appear larger on the screen. If I set the scaling to 100% or simply disable Fractional Scaling, I am able to scroll through the list of installed apps normally. All other fractional scaling settings (100%, 150%, 175% and 200%) work perfectly. Only 125% is affected. For reference, my display resolution is set to 3840x2180 @ 60Hz. It is kind of late in the life of this release to do much about this, but I thought I should pass this info along. Bob Reed Westminster, Maryland USA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1950324] Re: after upgrade today I cannot copy paste file from one folder to another
Daniel: Thank you for the email; thank you for taking an interest in my bug and helping me. I may need to edit my original description based on the following (if editing is allowed). I believe my problem is different than 1948008 because I am able to copy from the Desktop and then paste back to the Desktop. I am not able to copy a file from the Desktop to another folder (e.g., cannot copy to Documents, Downloads, Pictures, USB-Thumb-drive, etc.); Paste is greyed out. Likewise I am unable to copy from any other folder and paste to the Desktop. If I open the desktop as a folder (Show Desktop in Files) then I can copy a file from the desktop folder to another folder. Likewise I can copy a file from another folder to the desktop folder. Note: I can copy/paste files between other folders (e.g. copy a file from Documents to Downloads and vice-versa); my bug only affects the Desktop. Note: I recently installed gnome-tweaks; I then changed the Workspaces from "Dynamic Workspaces" to "Static Workspaces"; number of Workspaces: 4. Today I changed it back to Dynamic (default). It did not correct bug. I may have changed something else in gnome-tweaks. On 11/10/21 8:06 PM, Daniel van Vugt wrote: > Are you copying/pasting to or from the desktop? If so then this is bug > 1948008. > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1950324 Title: after upgrade today I cannot copy paste file from one folder to another Status in gnome-shell package in Ubuntu: Incomplete Bug description: I select "Copy" a file in one folder (e.g., Pictures); select another folder (e.g., USB Thumb-drive or Documents or any other folder) and the word "Paste" is greyed-out (not accessible). As such I cannot do a File Copy-Paste. Problem occurred shortly after doing a requested update (about 200 Meg required). Rebooted computer; no help. Never had this problem before. Running Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 07:28:27 2021 InstallationDate: Installed on 2021-09-28 (41 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1065126]
(In reply to Rachel Martin from comment #195) > (In reply to NolanK from comment #193) > > Just to set the record straight: The fork you mentioned did NOT fix this bug. > If fixed bug 1690395 with the (hacky) fix suggested in bug 1690395 comment > #13. We agree 100% with the statement from bug 1690395 comment #31. Bug 135636 is similar to this bug where many unrelated tickets are dumped into a decades old open wontfix ticket. Have you fixed or are you planning on fixing PGP? Once these political bugs are addressed, I'm sure the OS distros will drop TB for BB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1065126]
This bug isn’t an enhancement and it’s never getting fixed so it should be closed as WONTFIX instead of leaving it open for 13 years. Add this defect to list of pull requests for when FF is forked to a more community version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I understand, thanks Rik. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I downloaded Kubuntu daily build for 2021-04-09 and put the iso on a thumb drive I am using the 'safe graphics' option needed by my system. The on screen display of the initial file check process, with option to skip, still doesn't show. A splash screen eventually shows and flickers a few times before the screen with 'try live' and 'install now' buttons appears. I can now successfully access with the 'live screen' option, also the 'install now' button works. I successfully installed Kubuntu Hippo via the 'install now' button. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to:
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Will the mesa fix be available on a daily build? I would like to test it on my hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Committed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Having installed Ubuntu Hippo Beta [or a recent daily build version] successfully as in post #32 it is possible to install the Kubuntu desktop over it resulting in a working version of Kubuntu Hippo. I suppose this could be seen as a workaround to install a working Kubuntu 2104. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I've tried, out of interest, an install of Ubuntu (which incidentally also carries the mesa files) from recent daily builds and also of the recently released beta. Ubuntu is not displaying the behaviour that appears with Kubuntu. It is possible to transfer the iso to a usb stick, run it from there in safe graphics mode and do an install to a partition on the PC. As we know at this time this is not possible for Kubuntu. I post this thinking it might be relevant. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions --
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Opinion Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Opinion Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately what Rik is experiencing on a "live session" in his virtual machine with intel graphics using an unnecessary 'safe graphics' mode is slightly different to my necessary use of 'safe graphics' to unsuccessfully boot from a thumbdrive containing the iso. I'm sorry I am not a bug hunter, I am not aware of the protocols. All I can repeat is that a thumb drive containing either a current daily build or the recent beta does not boot correctly. I would guess in my untutored way that some change to the boot process occurred during March. Up until then I had performed test installs without a hitch. I would be happy to give any assistance/info I can but my programming experience is severely limited. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
"malloc(): unaligned tcache chunk detected" does not appear on my PC. I am trying to install from an iso of hippo on a thumb drive. The boot fails before any 'live session' appears. I am not trying to install from a live session, boot fails before that point. I do not think this is the same as the bug reported here. Rik it appears is attemptig to boot from a live session of some sort. My installation breaks down before reaching this point. The iso in the daily build was not failing until some time in March. It has not been right since. There were a number of updates on a regular basis in March. The change is in the boot process rather than in actual installation as the installation has not been begun at the point the bug occurs. I'm no programmer but I can see that installation has not been offered, let alone begun when things go astray. Please review any conclusions so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Is there somewhere or somehow I can test your modified version of Kubuntu by downloading it and attempting an install Rik? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It is possible on my PC to install Ubuntu2104beta without encountering this behaviour and I can successfully install the Ubuntu flavour. This bug does happen with the Kubuntu beta and I find it is impossible to install the Kubuntu flavour from the beta iso. It is worth noting that mesa is present in both Ubuntu and Kubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
This is to confirm that kubuntu-21.04-beta-desktop-amd64.iso fails as an installation media on my PC. I have nvidia graphics, amd m/board and am using 'safe graphics' when attempting to boot up the installation media from a thumb drive. The usual "Installation failed" message is displayed. If more info would help please give me any further instructions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I'm adding the following, so searches of this symptom will also find this thread: Once the bug is triggered, it also repeatably affects LibreOffice Calc - if you click-select a worksheet tab or drag-select a set of cells then release mouse, it enters drag-and-drop mode, and (strangely) draws a thick border around the selection, which you cannot undo or reformat. I can exit DND mode with ESC. And temporarily remove the problem with the xinput solution, but I agree with #53 that disabling touch screen is insufficient - you need to re-enable too. System details: Lenovo Yoga 3 Pro with ATML1000:00 03EB:8A10 touch screen 20.04.1-Ubuntu (although this bug has been affecting previous versions for me) Linux kernel 5.8.0-48-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
kubuntu hirsute daily build 21-03-28 also fails if safe graphics mode is used on a machine with nVidia graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I should repeat, I am performing the installation using 'Safe Graphics' mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I have attempted to install from kubuntu hirsute daily build 21-03-22 kubuntu hirsute daily build 21-03-23 kubuntu hirsute daily build 21-03-24 each version the insstallation fails. Incidentally I noticed another change. While the daily builds were installing correctly a procedure appeared on screen, this no longer happens. After booting the installation media, a self check ran with an on screen display showing the stages the check was passing through. The word Kubuntu appeared on screen and this display was beneath it. Since the installation began to fail, the file check no longer shows and although the word Kubuntu appears it disappears shortly after. As it changed when installation began to fail, maybe there is a connection? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It turns out I don't have my latest successful installation of Kubuntu Hirsute. I did a successful install of Ubuntu Hirsute to confirm whether it was only the Kubuntu version that was affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
My nvidia graphics card needs safe mode, but generally installations proceed without problems. The Hirsute daily builds were installing without a hitch until recently. I'll check my most recent successful installation and see if I can find a version number. It was after this that the bug appeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
correction tp post #11: I just re-attempted installing from thumb drive on my hardware with ISO 2021-03-23 crash as with ISO 2021-03-22 and earlier I have nVidia graphics [using safe mode install option] my hardware is home built PC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
crash on my hardware with ISO 2021-03-23 no error message appears now I just get a black screen mouse pointer visible -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately iso 20210322 is producing a crash on my hardware. [see bug 1920712] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
successfully create a thumb drive from: hirsute-desktop-amd64.iso 2021-03-21 05:492.7GDesktop image for 64-bit PC (AMD64) computers (standard download) boot from thumb drive: "Installation failed - KDialog \n The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Installation cannot proceed. I don't have the know how to be able to investigate, unfortunately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I don't know what mutter is or if it's responsible but since automatic update of 20.04 on Thursday, I believe, at the next bootup the screen has a black border around the usual screen display, i.e. shrunken desktop. NVideo card used. Search sent me here but for font size issues. Please keep me informed if this is your doing and how to fix it. Nothing seems to fix it but the Phillips Monitor is full screen when it comes on with Phillips banner so I suggest it is being done inside the box! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914147]
In reply to "when", I never experienced this problem up to and including 84.0.2. I first got this problem in 85.0, and still get it in 85.0.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: [upstream] Firefox 85 hangs at startup Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: In Progress Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1910480
Title:
no audio on fresh install kubuntu groovy
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
on installing Kubuntu Groovy 'no output or input devices found'
sound appears to be disabled
running ubuntu-debug -s audio does produce sound in both headphone channels
in first part of test but no sound in second part
sound is recognised and working okay if Kubuntu Focal is installed
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob1071 F pulseaudio
bob1074 F pipewire-media-
/dev/snd/controlC1: bob1074 F pipewire-media-
/dev/snd/seq: bob1070 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jan 7 03:19:48 2021
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_Jack: SPDIF Out, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: None of the above
Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99FX PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: 7354844-001
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MBB-895908
dmi.product.sku: SKU
dmi.product.version: 1.0
dmi.sys.vendor: NOVATECH LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
When I submitted this report I wasn't aware that this issue had been mentioned in the Release Notes (which weren't available at the time) ...that means this report is not required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: New Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910539] Re: Cannot set scale of screen
This is screenshot after clicking apply (to access print screen had to click keep changes button too) ** Attachment added: "After click on apply" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+attachment/5450246/+files/Screenshot%20from%202021-01-07%2020-52-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910538] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910538/+attachment/5450200/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1910539] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910539/+attachment/5450223/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I'll also add that this problem is still present in kernel 5.8 (no matter if you use "modesetting" or "intel" driver for the Braswell GPU. My current setup: System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal Machine: Type: Desktop System: ASUSTeK product: E410 v: 0703 serial: Mobo: ASUSTeK model: E410 v: Rev 1.xx serial: UEFI: ASUSTeK (Licensed from AMI) v: 0703 date: 07/07/2017 CPU: Topology: Quad Core model: Intel Celeron N3150 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 12800 Speed: 1008 MHz min/max: 480/2080 MHz Core speeds (MHz): 1: 721 2: 1179 3: 2081 4: 2080 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:22b1 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (BSW) v: 4.6 Mesa 21.0.0-devel (git-7de1468 2021-01-01 focal-oibaf-ppa) compat-v: 3.0 direct render: Yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@tonypanduru I'd like to share a slightly improved workaround on this for those still dealing with the issue. The core problem seems to be that the mouse cursor can go into a negative X position by one pixel when moved to the far left of the screen. With either the now obsolete intel proprietary driver or the current intel modesetting driver, this causes issues (exact symptoms are different for each, but seem to be from the same root cause). My previous workaround got by this by scaling the entire desktop to 99.99% of its former size. This prevented the cursor from getting to the -1 X position, but came at a cost of lost performance and some screen tearing in videos and games. This was due to a bilinear filter being applied by xrandr to the whole desktop to accommodate the slight re- size. The following command avoids this issue and instead merely shifts the entire desktop right one pixel. It still works around the issue, but seems to avoid the overhead of resizing the whole desktop (which preserves display integrity and performance). xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1 It would be nice to get a root cause fix for this, but this workaround seems to do the trick with very little downside. As before, replace the "HDMI-3" with the name of your active display (found by running xrandr with no options) and place the command in your ~/.xprofile (or make a startup app entry in your desktop manager). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1898599] Re: Add user, who start with number, failed
syslog: Add users who start with a number failed: Oct 5 17:05:10 ubuntu accounts-daemon[8794]: adduser: Please enter a username m atching the regular expression configured Oct 5 17:05:10 ubuntu accounts-daemon[8794]: via the NAME_REGEX[_SYSTEM] config uration variable. Use the `--force-badname' Oct 5 17:05:10 ubuntu accounts-daemon[8794]: option to relax this check or reco nfigure NAME_REGEX. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1898599 Title: Add user, who start with number, failed Status in gnome-control-center package in Ubuntu: New Bug description: commandline works: sudo useradd -d /home/4Syno -m 4Syno sudo passwd 4Syno ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 17:35:52 2020 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898599] [NEW] Add user, who start with number, failed
Public bug reported: commandline works: sudo useradd -d /home/4Syno -m 4Syno sudo passwd 4Syno ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 17:35:52 2020 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Auswahl_854.png" https://bugs.launchpad.net/bugs/1898599/+attachment/5417979/+files/Auswahl_854.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1898599 Title: Add user, who start with number, failed Status in gnome-control-center package in Ubuntu: New Bug description: commandline works: sudo useradd -d /home/4Syno -m 4Syno sudo passwd 4Syno ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 17:35:52 2020 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
I am also having this issue on a brand new laptop (Ryzen 5 4500), however the dead mouse pointer is there from a fresh reboot. It is left over from the login screen and remains there once the system has logged in. If I logout, the 'dead' mouse becomes the only one on the login screen, yet loging back in causes it to freeze while a second pointer becomes active. Very strange behaviour! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Same issue with GU502GU with Mint or Pop OS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
PS. I double-checked that there were no nautilus processes hanging around before removing nautilus-image-converter. And I double-checked that the features of nautilus-image-converter were no longer showing within nautilus before backtracing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
Done `sudo apt remove nautilus-image-converter`. Still crashes the same (tried first without gdb, then with). backtrace attached (produced as before). ** Attachment added: "gdb backtrace output for nautilus bug #1887315" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5394326/+files/gdb-nautilus2020-07-20.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
Do you want/need me to remove any of the extension packages, or can you take it from here? Regarding where to post my feedback on the DebuggingProgramCrash instructions, I was really looking for some way to give feedback to the authors of the wiki page, not a discussion forum. I've emailed the person who last edited the page, but I was expecting a more systematic way to collect wiki feedback. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
Att'd: nautilus extensions installed. The only one I'm aware of having explicitly installed is nautilus-image-converter (and of course nautilus-dbgsym). ** Attachment added: "nautilus extensions installed re. bug #1887315" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393608/+files/20200717-ra-nautilus-extensions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
gdb output attached. When overtyping the search field in nautilus within gdb, it didn't crash in the same way: the nautilus window hung (whereas without gdb nautilus crashed). So I did -C in gdb as instructed. But then I got [Wait / Force Quit] over the nautilus window and gdb had become unresponsive, with the nautilus process as a defunct child. So, I killed gdb, ran it again, and this time, once I had got nautilus in its hung state, I completed the gdb output without using -C. PS. I would like to give review comments on the DebuggingProgramCrash instructions. I had to guess what was meant on a number of points. Where's the appropriate place to post a review? ** Attachment added: "gdb output for nautilus bug #1887315" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+attachment/5393586/+files/gdb-nautilus.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
I'm following the instructions to upload a backtrace. I've disable apport, but I've floundered on step 1 of Generating the backtrace. "1. Please ensure you have packages with debug symbols installed. You can do this by following the instructions at DebuggingProgramCrash." Can you give more specific instructions for this case? I can't find a nautilus package with debug symbols installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: Incomplete Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] Re: Nautilus crashes while over-typing search term on remote smb file system
Another way to type into the search field over a remote share that makes nautilus crash: type the first character (incorrectly), backspace, then re-type. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: New Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887315] [NEW] Nautilus crashes while over-typing search term on remote smb file system
Public bug reported: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when typing a search term after having explicitly cleared the search field, but before nautilus has displayed the full contents of the directory again (about 150 files). I have not had nautilus crash when over-typing the search field for a local file system, whether ntfs or ext3. ==Related bugs== Bug #1795028 seems to be identical, and claims to have been fixed in package nautilus - 1:3.26.4-0~ubuntu18.04.2 but it does not appear to be fixed in 3.36.3 under Ubuntu 20.04. Hopefully this report explains more precisely how to reproduce the crash. ==Crash Reports== A typical crash report from my system is here: https://errors.ubuntu.com/oops/2dd9aa90-c462-11ea-9e47-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:03:59 2020 InstallationDate: Installed on 2020-06-03 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887315 Title: Nautilus crashes while over-typing search term on remote smb file system Status in nautilus package in Ubuntu: New Bug description: ==Impact== nautilus crashes while typing the term to search a remote directory within an NT file system over the smb protocol. The problem may affect other remote file systems or protocols, but I have only tested these. Repeatable. ==How to repeat== 1. Open Nautilus 2. In the sidebar, click Other Locations 3. Type smb://example/share into the 'Connect to server' field or select an existing share URI 4. Click Connect 5. Optionally, when the contents of the share appears, select any depth of sub-directories. 6. Click the search icon and type a search string 7. Once the search results have returned, without closing the search box, select the previous search term and over-type another search term. Nautilus crashes. Typically, prior to the window disappearing the graphics freezes within the search field showing both the previous and the current search terms on top of each other. Often it is necessary to kill the nautilus process and/or reboot the smb daemon on the remote machine before being able to use the smb share again. Before typing a second search term, if instead of over-typing, you delete the selection either i) with the key; or ii) clicking the (x) to clear the field; or iii) clicking the search icon twice to remove and reinstate the search field; it is possible to search for a second term without crashing. It is possible that the crash depends on how fast the search term is typed, because nautilus starts searching as you type. I have tried to paste a search term over an existing term, which usually seems to work without crashing. On the other hand, I have had nautilus crash when
[Desktop-packages] [Bug 1882864] [NEW] [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all
Public bug reported: It used to work just fine but after some update/change audio only works via HDMI but not through the built-in speaker or audio port anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 11:50:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-24 (836 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-09-09 (639 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 049W7N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnLatitude5280:pvr:rvnDellInc.:rn049W7N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5280 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1882864 Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: It used to work just fine but after some update/change audio only works via HDMI but not through the built-in speaker or audio port anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 11:50:21 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-24 (836 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Latitude 5280, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-09-09 (639 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 049W7N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnLatitude5280:pvr:rvnDellInc.:rn049W7N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I can confirm that the problem is present with both the intel and the modesetting driver on Braswell systems. The exact symptoms differ for each, but in both cases it is triggered when the mouse touches the left limit of the screen. With modesetting, it seems to "stick" until you move the mouse away from the left side. With intel, touching the left side starts a flickering that persists even after you move the mouse away. Mainly, just the mouse cursor flickers, but the whole screen will flicker when doing graphics intensive tasks like fullscreen video or gaming. Sometimes, the mouse flicker can be so bad it becomes nearly invisible. I have made full report on the bug report thread opened by Salvatore. The good news is I found a workaround, you can use xrandr to scale the display to 0.x0. and this prevents the issues in both intel and modesetting. This can be done in your .xprofile in your home directory to take effect at login. It does come with a slight performance penalty, but it's preferable to the glitching that happens otherwise (at least until someone fixes the regression). xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0. Replace "HDMI-3" with the name of your display (can be found by running xrandr with no options). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1879593] [NEW] show applications sub-menu missing labels on last line
Public bug reported: Boot Ubuntu 20.04 login click "Show Applications" grid button in lower left Scroll to bottom Click "utilities" to open sub-menu scroll to bottom Notice that the labels on the last line are mostly hidden - see screenshot Close menu Open Screenshot app Try menu, again, will be correct this time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 21:36:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-16 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of sub-menu with last line labels not showing properly" https://bugs.launchpad.net/bugs/1879593/+attachment/5374360/+files/Screenshot%20from%202020-05-15%2021-13-05.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1879593 Title: show applications sub-menu missing labels on last line Status in gnome-shell package in Ubuntu: New Bug description: Boot Ubuntu 20.04 login click "Show Applications" grid button in lower left Scroll to bottom Click "utilities" to open sub-menu scroll to bottom Notice that the labels on the last line are mostly hidden - see screenshot Close menu Open Screenshot app Try menu, again, will be correct this time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 21:36:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-16 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847650] Re: When dock is on the right hand side it covers the 'page dots' on the 'all applications' icon view
There is a screenshot of this in https://bugs.launchpad.net/bugs/1878712 if that helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1847650 Title: When dock is on the right hand side it covers the 'page dots' on the 'all applications' icon view Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Steps to duplicate: 1. Set Ubuntu Dock to be on the right hand side of the screen. 2. Click on the 'Show Applications' button which will be at the bottom-right of the screen. 3. When all of the application icons appear, you will notice that the 'dots' which can be clicked for switch from one page of icons to another are on the right of the screen underneath the Ubuntu dock. As such they cannot be clicked on. Expected result: Can the dots either move to the left of the screen (where there is no dock) or at least moved to a place where the dock does not obscure them? Whilst this may not appear to be a major issue, I am running this on a laptop using only a trackpad, and switching from one page of icons to another is a but hit and miss as often a gentle swipe on my track pad moves me two pages in either direction. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 10 19:16:05 2019 InstallationDate: Installed on 2019-09-23 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to eoan on 2019-09-27 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] Re: App grid has too many page dots on right
Bug 1878712 opened for related but separate bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: App grid has too many page dots on right Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Focal: Fix Committed Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878712] [NEW] Show Applications menu dots on right hidden behind dock
Public bug reported: With the gnome dock on the right, clicking the "Show Applications" button (matrix of 9 dots at bottom right), brings up a matrix of applications. On the right there are two or more dots, one for each page of the menu. But the dots are behind the dock on the right, and cannot be seen (mostly) and cannot be clicked. Picture attached. One dot can be faintly seen between the Mail and Help icons. Another dot is behind the help icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 18:46:45 2020 InstallationDate: Installed on 2020-04-04 (40 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of hidden dots" https://bugs.launchpad.net/bugs/1878712/+attachment/5371740/+files/Screenshot%20from%202020-05-14%2018-42-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1878712 Title: Show Applications menu dots on right hidden behind dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: With the gnome dock on the right, clicking the "Show Applications" button (matrix of 9 dots at bottom right), brings up a matrix of applications. On the right there are two or more dots, one for each page of the menu. But the dots are behind the dock on the right, and cannot be seen (mostly) and cannot be clicked. Picture attached. One dot can be faintly seen between the Mail and Help icons. Another dot is behind the help icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 18:46:45 2020 InstallationDate: Installed on 2020-04-04 (40 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1878712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] Re: App grid has too many page dots on right
Fixed! gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 all [installed,automatic] When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There are now correctly two dots on the right to match the two pages, and clicking on the dots works properly. I will open a new bug report - if the dock is on the right, the dots are hidden behind the dock. I do not remember if that happened before. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: App grid has too many page dots on right Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Focal: Fix Committed Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875037] Re: Turning off high contrast does not revert the desktop icons' appearance
The purpose of the setting is to change the desktop view. Changing the setting should force a display refresh. So I'm not sure I would change the status to "Invalid". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1875037 Title: Turning off high contrast does not revert the desktop icons' appearance Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: When going to Settings -> Universal Access and selecting "High Contrast" to view the difference in appearance, then switching "High Contrast" to off, the icons do not return to their normal appearance. I did not find a place in this bug submission interface to submit attachments or I would show you screen capture of the changes in the icon appearance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:48:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) [1458:d000] InstallationDate: Installed on 2020-03-31 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) MachineType: Gigabyte Technology Co., Ltd. H370 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: H370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875037] [NEW] Display Bug
Public bug reported: When going to Settings -> Universal Access and selecting "High Contrast" to view the difference in appearance, then switching "High Contrast" to off, the icons do not return to their normal appearance. I did not find a place in this bug submission interface to submit attachments or I would show you screen capture of the changes in the icon appearance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:48:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) [1458:d000] InstallationDate: Installed on 2020-03-31 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) MachineType: Gigabyte Technology Co., Ltd. H370 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: H370N WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370NWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Altered_appearance.png" https://bugs.launchpad.net/bugs/1875037/+attachment/5360327/+files/Altered_appearance.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875037 Title: Display Bug Status in xorg package in Ubuntu: New Bug description: When going to Settings -> Universal Access and selecting "High Contrast" to view the difference in appearance, then switching "High Contrast" to off, the icons do not return to their normal appearance. I did not find a place in this bug submission interface to submit attachments or I would show you screen capture of the changes in the icon appearance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 10:48:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop) [1458:d000] InstallationDate: Installed on 2020-03-31 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) MachineType: Gigabyte Technology Co., Ltd. H370 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=8d24e3f8-c08c-444a-8467-4f9473fa4a22 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade
[Desktop-packages] [Bug 1870847] Re: Show Applications has too many dots on right
Managed to get errors when clicking the dots. See end of journalctl attached. Like: Apr 05 18:15:38 rharoldenvy gnome-shell[1786]: value "-0.000122" of type 'gfloat' is invalid or out of range for property 'margin-bottom' of type 'gfloat' ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+attachment/5347371/+files/dots-journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1870848/+attachment/5347366/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] Re: Show Applications blanks bottom 2/3 of bottom screen
Adding journalctl ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+attachment/5347370/+files/screen-part-blank-journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1870848/+attachment/5347368/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1870848/+attachment/5347367/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1870848/+attachment/5347369/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] Re: Show Applications blanks bottom 2/3 of bottom screen
apport information ** Tags added: apport-collected ** Description changed: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu22 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-04 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: gnome-shell 3.36.0-2ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1870848/+attachment/5347365/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in gnome-shell package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1870847] Re: Show Applications has too many dots on right
Thanks for looking at this. I do not see any messages in journalctl that happen when I open and close the menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1870847/+attachment/5347360/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1870847/+attachment/5347362/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] Re: Show Applications has too many dots on right
apport information ** Tags added: apport-collected ** Description changed: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu22 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-04 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: gnome-shell 3.36.0-2ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1870847/+attachment/5347359/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1870847/+attachment/5347363/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1870847/+attachment/5347361/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in gnome-shell package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: gnome-shell 3.36.0-2ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870848] [NEW] Show Applications blanks bottom 2/3 of bottom screen
Public bug reported: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1870848/+attachment/5346680/+files/Screenshot%20from%202020-04-04%2018-48-23.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870848 Title: Show Applications blanks bottom 2/3 of bottom screen Status in nautilus package in Ubuntu: New Bug description: When I connect an external monitor (HDMI), and arrange it above the laptop monitor (same resolution), and click "Show Applications" button in lower left, the "Frequent" and "All" buttons are near the top of the laptop screen instead of at the bottom, and the matrix of applications is blanked out (the bottom 2/3 of the laptop screen). If I start typing, I can see the top half of the icons that match what I am typing. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:49:18 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1870848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] [NEW] Show Applications has too many dots on right
Public bug reported: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description:Ubuntu Focal Fossa (development branch) Release:20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1870847/+attachment/5346677/+files/Screenshot%20from%202020-04-04%2018-44-10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in nautilus package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870847] Re: Show Applications has too many dots on right
Typo - "there are 8 dots" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870847 Title: Show Applications has too many dots on right Status in nautilus package in Ubuntu: New Bug description: When I click the "Show Applications" button in the lower left, it brings up a matrix of application icons, which takes a page and a half. There should be two dots on the right to match the two pages, but instead there are * dots. Moving up and down, the first and second dots highlight to show which page I am on. But only the top dot, and the bottom two, can be clicked on to change the page. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 final beta April 3 nautilus: Installed: 1:3.36.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:35:20 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1870847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868128] [NEW] (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24)
Public bug reported: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-05 (560 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.70:bd01/24/2014:svnTOSHIBA:pnSatelliteC55t-A:pvrPSCFJU-00T00J:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Durban-Curiosity 10S/10SG dmi.product.name: Satellite C55t-A dmi.product.version: PSCFJU-00T00J dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 27 12:22:02 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868128 Title: (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) Status in xorg package in Ubuntu: New Bug description: trying to reinstall my Ubuntu 18.04 on my Toshiba Satelite 64 bus laptop. I have a loaded flash drive but I keep getting an error message as follows, (Error ID: OOPS-f9a25a1047f367bba335ebdf6c9c0a24) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 19 08:43:35 2020 DistUpgraded: 2018-09-05 15:50:48,221 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated Graphics Controller [1179:fa22] InstallationDate: Installed on 2017-04-18 (1065 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite C55t-A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=1be49583-6218-4da2-9204-c5ae2ac5cebd ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg
[Desktop-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
This fixed my problem. I am reinstalling VirtualBox 6.1.4 and the command "sudo ln -fs gcc-8 /usr/bin/gcc" solve the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Status in backport-iwlwifi-dkms source package in Eoan: Fix Released Status in gcc-9 source package in Eoan: Won't Fix Status in linux source package in Eoan: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Confirmed Status in nvidia-graphics-drivers-430 source package in Eoan: Fix Released Status in virtualbox source package in Eoan: Won't Fix Status in xtables-addons source package in Eoan: Won't Fix Bug description: [SRU Justification for backport-iwlwifi-dkms] [Impact] FTBFS against v5.3 kernels on Eoan/Focal. [Fix] * Backport fix from upstream commit f47729b94e11 (backport: rename ktime_get_boot_ns for v5.3+). * Also updates -fcf-protection=none usage for bug 1830961. [Test Case] Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal. [Regression Risk] Low. There is no functional changes in comparison to 7906-0ubuntu1. original bug description Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
@unusedusername I found a snippet somewhere that helped me do things when my lid is closed (or rather when the session is locked). Since your laptop switches to airplane mode something is detecting it so maybe this helps. Put this in a script and run it, then close lid and open lid. Do you get any output? #!/bin/sh iface=org.freedesktop.login1.Session dbus-monitor --system --profile "type=signal,interface=$iface" 2>/dev/null | while read type stamp sender dest path intf member; do case "$member" in *Lock) date echo LOCKED at $stamp ;; *Unlock) date echo UNLOCKED at $stamp ;; *) esac done If it works you could even insert a suspend command and run this in the background to avoid having to use the mouse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
I am running the latest beta of 18.04 with upgrades. Since installation I try to log in the gdm screen and receive the message, "Sorry, that didn't work. Please try again." I get the same message when I try to log in to Update Manager. The app and gdm screen launch if I enter my password again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I have a bug since the recent updates on Ubuntu 18.04 (post 10th March): when the user password contains a circumflex accent, like "û", access is denied even if password entered is correct and I stay blocked in a loop at gdm login screen - error message (translated from French): "Sorry, it doesn't work, please try again". Even after modifying it on recovery mode with passwd without û, it stays blocked. Only way to solve it is to reinstall. Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Steps to reproduce : I did a fresh and new install with 18.04 daily iso from 21st March, formatting / and /home with following user password: Ubuntu42 At startup, I could log successfully both on Xorg and Wayland sessions. Then I modified and tested those passwords, with all of them I could again boot and connect, on Xorg and Wayland: ArchLinux43 LinuxMint@28 KDENeon=51 Fedora_1984 But the last one made me blocked at the gdm login screen: Debianû74 Here unable to modify it on recovery session, error message in French: "erreur de manipulation du jeton d'authentification". Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but F2, F3... F12 freezes it! I only can update in chroot with lie USB. I had to again format and reinstall, with a password without any circumflex accent. How and when I discovered it : On 10th March, I ran since many weeks the alpha version of Ubuntu 18.04, with a password having a "û" inside, which had always worked fine. I did an update, cumulating the last 3 weeks before. On next startup, when I typed my password, both on Xorg and Wayland sessions, no error message but no desktop, nothing appeared but a few seconds later I was back on login screen. I could well log in on terminal (Ctrl Alt F2) or chroot with a live USB, and do the last updates in the next days, but nothing changed. On console, if I ran "startx" I got the message "timeout in locking authority file" and "fatal server error: cannot open log file ./local/share/xorg/Xorg.0.log Both / and /home were not full - more than 60% space available, verified with df -Th ; echo ; df -Ti I tried to reinstall Ubuntu with daily live of 15th March, formatting / but not /home as it was protected by ecryptfs and I didn't save some files, using same user name and password, still blocked. So I copied the /home and .Private folders to another disk to try later recover them, reinstall again, formatting both / and /home, always with my usual password having a "û" (I verified French language, keyboard with French activated, upper case, symbols... OK). This time, again both for Xorg or Wayland sessions, at gdm login I did not success to connect, I got an error message "Désolé ça n'a pas fonctionné, veuillez réessayer", I tried to modify the password in recovery mode, with no special characters nor accents, but still blocked at gdm. And no terminal available with Ctrl Alt F2... On 23rd March, I re-reinstalled all Ubuntu, formatting / and /home, this time with daily iso from 21st March, but with a modification: to avoid any misconfiguration with languages on live USB, I chose a very easy password, only with normal letters and numbers. On startup, yes, finally I could log at gdm on default Xorg session and enter desktop ! I went to my user configuration, changed to put my usual password (with an "û"), and bam, back to the future, still blocked at gdm screen on restart, either on Xorg or Wayland, Ctr Alt F2 not working. It made me understand that the bug came from a special character in my password, then I tried the different ones explained on top of this report to discover it was "û". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1758563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f
Thank you. On Tue, 2018-03-27 at 08:41 +, Daniel van Vugt wrote: > We hope the fix for bug 1746874 (released last night) will help to > figure this out. > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Triaged Bug description: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755040] [NEW] amarok crashes when mouse leaves window
Public bug reported: Application: amarok (2.8.0) KDE Platform Version: 4.14.34 Qt Version: 4.8.7 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: I have a dual monitor setup. When Amarok is in full screen on one monitor and when mouse moves to the other monitor amarok crashes every time. This behavior started after performing an apt dist-upgrade which upgraded plasma packages to 4:5.12.3-0ubuntu1~ubuntu17.10~ppa1 The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50c8d86e00 (LWP 8272))] Thread 1 (Thread 0x7f50c8d86e00 (LWP 8272)): [KCrash Handler] #6 PrettyTreeDelegate::paint (this=0x2d68a980, painter=0x7fffd6c64f70, option=..., index=...) at /build/amarok-qMTIuP/amarok-2.8.0/src/widgets/PrettyTreeDelegate.cpp:172 #7 0x7f50c6c22555 in QTreeView::drawRow (this=0x2d674050, painter=painter@entry=0x7fffd6c64f70, option=..., index=...) at itemviews/qtreeview.cpp:1685 #8 0x7f50c8851be9 in Amarok::PrettyTreeView::drawRow (this=, painter=0x7fffd6c64f70, option=..., index=...) at /build/amarok-qMTIuP/amarok-2.8.0/src/widgets/PrettyTreeView.cpp:86 #9 0x7f50c6c25ef8 in QTreeView::drawTree (this=this@entry=0x2d674050, painter=painter@entry=0x7fffd6c64f70, region=...) at itemviews/qtreeview.cpp:1438 #10 0x7f50c6c29b76 in QTreeView::paintEvent (this=0x2d674050, event=0x7fffd6c65670) at itemviews/qtreeview.cpp:1270 #11 0x7f50c66fc930 in QWidget::event (this=this@entry=0x2d674050, event=event@entry=0x7fffd6c65670) at kernel/qwidget.cpp:8775 #12 0x7f50c6ac665e in QFrame::event (this=0x2d674050, e=0x7fffd6c65670) at widgets/qframe.cpp:557 #13 0x7f50c6bebfc3 in QAbstractItemView::viewportEvent (this=this@entry=0x2d674050, event=event@entry=0x7fffd6c65670) at itemviews/qabstractitemview.cpp:1644 #14 0x7f50c885216b in Amarok::PrettyTreeView::viewportEvent (this=0x2d674050, event=0x7fffd6c65670) at /build/amarok-qMTIuP/amarok-2.8.0/src/widgets/PrettyTreeView.cpp:225 #15 0x7f50c6179a16 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x1384cc0, receiver=receiver@entry=0x2d67dee0, event=event@entry=0x7fffd6c65670) at kernel/qcoreapplication.cpp:1065 #16 0x7f50c66a601c in QApplicationPrivate::notify_helper (this=this@entry=0x1384cc0, receiver=receiver@entry=0x2d67dee0, e=e@entry=0x7fffd6c65670) at kernel/qapplication.cpp:4566 #17 0x7f50c66acf76 in QApplication::notify (this=this@entry=0x7fffd6c67700, receiver=receiver@entry=0x2d67dee0, e=e@entry=0x7fffd6c65670) at kernel/qapplication.cpp:4356 #18 0x7f50c78d104a in KApplication::notify (this=0x7fffd6c67700, receiver=0x2d67dee0, event=0x7fffd6c65670) at ./kdeui/kernel/kapplication.cpp:311 #19 0x7f50c61798ad in QCoreApplication::notifyInternal (this=0x7fffd6c67700, receiver=receiver@entry=0x2d67dee0, event=event@entry=0x7fffd6c65670) at kernel/qcoreapplication.cpp:955 #20 0x7f50c66f6f97 in QCoreApplication::sendSpontaneousEvent (event=0x7fffd6c65670, receiver=0x2d67dee0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #21 QWidgetPrivate::drawWidget (this=this@entry=0x2d67df10, pdev=pdev@entry=0x2d424820, rgn=..., offset=..., flags=flags@entry=4, sharedPainter=sharedPainter@entry=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5599 #22 0x7f50c66f79a7 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x2d67d390, pdev=pdev@entry=0x2d424820, siblings=..., index=, rgn=..., offset=..., flags=4, sharedPainter=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5808 #23 0x7f50c66f6b26 in QWidgetPrivate::drawWidget (this=this@entry=0x2d67d390, pdev=pdev@entry=0x2d424820, rgn=..., offset=..., flags=flags@entry=4, sharedPainter=sharedPainter@entry=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5652 #24 0x7f50c66f79a7 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x2d5d9170, pdev=pdev@entry=0x2d424820, siblings=..., index=, rgn=..., offset=..., flags=4, sharedPainter=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5808 #25 0x7f50c66f6b26 in QWidgetPrivate::drawWidget (this=this@entry=0x2d5d9170, pdev=pdev@entry=0x2d424820, rgn=..., offset=..., flags=flags@entry=4, sharedPainter=sharedPainter@entry=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5652 #26 0x7f50c66f79a7 in QWidgetPrivate::paintSiblingsRecursive (this=this@entry=0x2d643200, pdev=pdev@entry=0x2d424820, siblings=..., index=, rgn=..., offset=..., flags=4, sharedPainter=0x0, backingStore=0x2d4bf240) at kernel/qwidget.cpp:5808 #27 0x7f50c66f6b26 in QWidgetPrivate::drawWidget (this=this@entry=0x2d643200, pdev=pdev@entry=0x2d424820, rgn=..., offset=..., flags=flags@entry=4, sharedPainter=sharedPainter@entry=0x0, backingStore=0x2d4bf240) at
[Desktop-packages] [Bug 1753719] [NEW] gnome-calculator won't launch
Public bug reported: package: gnome-calculator release: 17.10 package version: gnome-calculator: Installed: 1:3.25.92-0ubuntu1 Candidate: 1:3.25.92-0ubuntu1 Version table: *** 1:3.25.92-0ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status I expected the calculator to open instead it crashed: ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1)) Aborted (core dumped) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1753719 Title: gnome-calculator won't launch Status in gnome-calculator package in Ubuntu: New Bug description: package: gnome-calculator release: 17.10 package version: gnome-calculator: Installed: 1:3.25.92-0ubuntu1 Candidate: 1:3.25.92-0ubuntu1 Version table: *** 1:3.25.92-0ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status I expected the calculator to open instead it crashed: ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1)) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1753719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
This is reported as a bug in Gnome's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=778662 ** Bug watch added: GNOME Bug Tracker #778662 https://bugzilla.gnome.org/show_bug.cgi?id=778662 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744425] [NEW] htmldoc no longer handles PNG images correctly
Public bug reported: I have a workstation purchased from system76. My disk failed and they build a new disk with 16.04 on it. I had 16.04 on the previous disk, altho maybe a few months old. I installed htmldoc with apt-get, and now when I convert an HTML file that references a PNG image, the image is very faint an virtually unreadable. The basic features are there, and the size is about right, but the image is very bad. Something in the latest 16.04 seems to have broken htmldoc! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: htmldoc 1.8.27-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 19 20:14:23 2018 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: htmldoc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: htmldoc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to htmldoc in Ubuntu. https://bugs.launchpad.net/bugs/1744425 Title: htmldoc no longer handles PNG images correctly Status in htmldoc package in Ubuntu: New Bug description: I have a workstation purchased from system76. My disk failed and they build a new disk with 16.04 on it. I had 16.04 on the previous disk, altho maybe a few months old. I installed htmldoc with apt-get, and now when I convert an HTML file that references a PNG image, the image is very faint an virtually unreadable. The basic features are there, and the size is about right, but the image is very bad. Something in the latest 16.04 seems to have broken htmldoc! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: htmldoc 1.8.27-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 19 20:14:23 2018 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: htmldoc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htmldoc/+bug/1744425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730410] Re: Window full-screen size when Firefox starts
Same thing occurs for me using Ubuntu 17.10 with xorg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1730410 Title: Window full-screen size when Firefox starts Status in firefox package in Ubuntu: Confirmed Bug description: With Ubuntu 17.10 Wayland (64 bits AMD), Firefox opens always with the window in full-screen size. If you reduce the size before closing it, next time, it will open in full-screen size. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpaul 1618 F pulseaudio /dev/snd/controlC0: jpaul 1618 F pulseaudio /dev/snd/controlC1: jpaul 1618 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 15:49:44 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-04-30 (554 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.0.254 dev wlp4s6 proto static metric 600 169.254.0.0/16 dev wlp4s6 scope link metric 1000 192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-7494d4c2-9262-44e6-8fb2-3ca0d2161203 Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RelatedPackageVersions: adobe-flashplugin 1:20171025.1-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-7494d4c2-9262-44e6-8fb2-3ca0d2161203 bp-80a96d18-eeb9-455f-b7c6-046ac2160509 bp-8e0dc06d-4cc6-4ab7-8618-421d12160508 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to artful on 2017-10-23 (14 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd11/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1730410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728187] Re: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10)
I have the same issue. My desperate workaround is to pull the USB plug and reinsert it. That seems to reset the tablet and make it work again, but the problem returns after a few minutes. Another workaround is to flip the pen and use the eraser end, which buys a bit more time before having to pull the plug again. It was flawless before the 17.10 upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1728187 Title: Wacom pointer disappears completely, after using the tablet for few seconds (Ubuntu 17.10) Status in libwacom package in Ubuntu: Confirmed Bug description: I recently upgraded to Ubuntu 17.10(gnome, Wayland, 4.10.0-37-generic). The Wacom tablet works fine for few seconds while drawing, and then the pointer would suddenly disappears. I can still use the tablet to draw stuff, but there is no visible pointer on screen, so I am doing it blindly. Just so you know the mouse pointer appears separately and works fine. If you need additional info, just send me the set of commands I need to run. Thanks!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1728187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725007] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1717085 *** https://bugs.launchpad.net/bugs/1717085 Public bug reported: The computer used is a Lenovo X230 and the upgrade was from Ubuntu Mate 17.04 to Ubuntu Mate 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 21:08:49 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-02-24 (237 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725007 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: The computer used is a Lenovo X230 and the upgrade was from Ubuntu Mate 17.04 to Ubuntu Mate 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 21:08:49 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-02-24 (237 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping
-networking-common_2.48.2-1~ubuntu16.04.1_all.deb ... Unpacking glib-networking-common (2.48.2-1~ubuntu16.04.1) over (2.40.0-1ubuntu0.1) ... Preparing to unpack .../glib-networking_2.48.2-1~ubuntu16.04.1_amd64.deb ... Unpacking glib-networking:amd64 (2.48.2-1~ubuntu16.04.1) over (2.40.0-1ubuntu0.1) ... Preparing to unpack .../python-libproxy_0.4.11-5ubuntu1_all.deb ... Unpacking python-libproxy (0.4.11-5ubuntu1) over (0.4.11-0ubuntu4) ... Selecting previously unselected package libpcre16-3:amd64. Preparing to unpack .../libpcre16-3_2%3a8.38-3.1_amd64.deb ... Unpacking libpcre16-3:amd64 (2:8.38-3.1) ... Selecting previously unselected package libhybris-common1. Preparing to unpack .../libhybris-common1_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhybris-common1 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libhardware2. Preparing to unpack .../libhardware2_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhardware2 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libmedia1. Preparing to unpack .../libmedia1_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libmedia1 (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libhybris. Preparing to unpack .../libhybris_0.1.0+git20151016+6d424c9-0ubuntu7_amd64.deb ... Unpacking libhybris (0.1.0+git20151016+6d424c9-0ubuntu7) ... Selecting previously unselected package libevdev2:amd64. Preparing to unpack .../libevdev2_1.4.6+dfsg-1_amd64.deb ... Unpacking libevdev2:amd64 (1.4.6+dfsg-1) ... Preparing to unpack .../libwacom2_0.22-1~ubuntu16.04.1_amd64.deb ... Unpacking libwacom2:amd64 (0.22-1~ubuntu16.04.1) over (0.8-1) ... Preparing to unpack .../libwacom-common_0.22-1~ubuntu16.04.1_all.deb ... Unpacking libwacom-common (0.22-1~ubuntu16.04.1) over (0.8-1) ... Selecting previously unselected package libinput-bin. Preparing to unpack .../libinput-bin_1.6.3-1ubuntu1~16.04.1_amd64.deb ... Unpacking libinput-bin (1.6.3-1ubuntu1~16.04.1) ... Selecting previously unselected package libinput10:amd64. Preparing to unpack .../libinput10_1.6.3-1ubuntu1~16.04.1_amd64.deb ... Unpacking libinput10:amd64 (1.6.3-1ubuntu1~16.04.1) ... Preparing to unpack .../libqt5dbus5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5dbus5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Preparing to unpack .../libqt5network5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5network5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Preparing to unpack .../libqt5gui5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ... Unpacking libqt5gui5:amd64 (5.5.1+dfsg-16ubuntu7.5) over (5.2.1+dfsg-1ubuntu14.3) ... Selecting previously unselected package libdouble-conversion1v5:amd64. Preparing to unpack .../libdouble-conversion1v5_2.0.1-3ubuntu2_amd64.deb ... Unpacking libdouble-conversion1v5:amd64 (2.0.1-3ubuntu2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... (Reading database ... 370499 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing xul-ext-unity (3.0.0+14.04.20140416-0ubuntu1.14.04.1) ... Removing xul-ext-websites-integration (2.3.6+13.10.20130920.1-0ubuntu1.2) ... Removing libunity-webapps0:amd64 (2.5.0~+16.04.20160201-0ubuntu1) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+14.04.20140428-0ubuntu1) ... Removing webbrowser-app (0.23+14.04.20140428-0ubuntu1) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: gnome-menus -> desktop-file-utils packages' pending triggers which are or may be unresolvable: hicolor-icon-theme: /usr/share/icons/hicolor gnome-menus: /usr/share/applications doc-base: /usr/share/doc-base udev: /lib/udev/hwdb.d libc-bin: ldconfig bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications E: Sub-process /usr/bin/dpkg returned an error code (1) bob@Bob-PC:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1610517 Title: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping Status in hicolor-icon-theme package in Ubuntu: Confirmed Bug description: While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04 something like a post-install hook apparently triggered looping. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architect
[Desktop-packages] [Bug 1632183] Re: saned not find scanner that scanimage -L finds
As I understand it, this is an upstream design choice. saned doesn't let users select which scanners to share, it just shares any scanners that it can see. I think if network scanners were shared, then 2 saned instances on the same network get into a loop sharing the same scanner(s) recursively. Nothing in the SaneDaemonTutorial points out this issue and it certainly wasn't clear to me from the saned manpage that this would be a problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1632183 Title: saned not find scanner that scanimage -L finds Status in sane-backends package in Ubuntu: Confirmed Bug description: When running scanimage -L on a remote system no scanner is found. when running scanimage -L on local system (where saned is run) finds the scanners. when running scaned in debug mode I can see the remote system request a list of scanner but no list is returned to scanimge -L. This tell me the network setups are working and access control is also working. It just does not find the scanner under saned but finds it under scanimage -L I have remove saned stuff from systemd so I can run saned by hand output from scanimage on local system (where saned is run) root@cups:~# scanimage -L device `hpaio:/net/HP_Color_LaserJet_CM2320nf_MFP?ip=192.168.1.238' is a Hewlett-Packard HP_Color_LaserJet_CM2320nf_MFP all-in-one device `hpaio:/net/Photosmart_Prem_C410_series?zc=HPF3B712' is a Hewlett-Packard Photosmart_Prem_C410_series all-in-one device `hpaio:/net/photosmart_prem_c410_series?ip=192.168.1.31=false' is a Hewlett-Packard photosmart_prem_c410_series all-in-one root@cups:~# output from saned with debug turned on: root@cups:~# saned -d128 [saned] main: starting debug mode (level 128) [saned] read_config: searching for config file [saned] read_config: data port range: 1 - 10100 [saned] read_config: done reading config [saned] saned (AF-indep+IPv6) from sane-backends 1.0.25git starting up [saned] do_bindings: trying to get port for service "sane-port" (getaddrinfo) [saned] do_bindings: [1] socket () using IPv6 [saned] do_bindings: [1] setsockopt () [saned] do_bindings: [1] bind () to port 6566 [saned] do_bindings: [1] listen () [saned] do_bindings: [0] socket () using IPv4 [saned] do_bindings: [0] setsockopt () [saned] do_bindings: [0] bind () to port 6566 [saned] do_bindings: [0] bind failed: Address already in use [saned] run_standalone: spawning Avahi process [saned] run_standalone: waiting for control connection [saned] saned_avahi_callback: AVAHI_CLIENT_S_RUNNING [saned] saned_create_avahi_services: adding service 'saned' [saned] saned_avahi_group_callback: service 'saned' successfully established [saned] handle_connection: processing client connection [saned] check_host: detected an IPv4-mapped address [saned] check_host: access by remote host: :::192.168.1.141 [saned] check_host: remote host is not IN_LOOPBACK nor IN6_LOOPBACK [saned] check_host: local hostname: cups [saned] check_host: local hostname(s) (from DNS): cups.mlb.org [saned] check_host: local hostname(s) (from DNS): (null) [saned] check_host: local hostname(s) (from DNS): (null) [saned] check_host: remote host doesn't have same addr as local [saned] check_host: opening config file: /etc/hosts.equiv [saned] check_host: can't open config file: /etc/hosts.equiv (No such file or directory) [saned] check_host: opening config file: saned.conf [saned] check_host: config file line: `# saned.conf' [saned] check_host: config file line: `# Configuration for the saned daemon' [saned] check_host: config file line: `' [saned] check_host: config file line: `## Daemon options' [saned] check_host: config file line: `# Port range for the data connection. Choose a range inside [1024 - 65535].' [saned] check_host: config file line: `# Avoid specifying too large a range, for performance reasons.' [saned] check_host: config file line: `#' [saned] check_host: config file line: `# ONLY use this if your saned server is sitting behind a firewall. If your' [saned] check_host: config file line: `# firewall is a Linux machine, we strongly recommend using the' [saned] check_host: config file line: `# Netfilter nf_conntrack_sane connection tracking module instead.' [saned] check_host: config file line: `#' [saned] check_host: config file line: `data_portrange = 1 - 10100' [saned] check_host: config file line: `' [saned] check_host: config file line: `' [saned] check_host: config file line: `## Access list' [saned] check_host: config file line: `# A list of host names, IP addresses or IP subnets (CIDR notation) that' [saned] check_host: config file line: `# are permitted to use local SANE devices. IPv6 addresses must be enclosed' [saned] check_host: config file line: `# in brackets, and
[Desktop-packages] [Bug 245716] Re: file-roller puts temporary files in the home dir instead of /tmp
I've switched to Xarchiver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/245716 Title: file-roller puts temporary files in the home dir instead of /tmp Status in File Roller: Confirmed Status in file-roller package in Ubuntu: Triaged Status in file-roller package in Arch Linux: New Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy file-roller file-roller: Installed: 3.12.2-0ubuntu1 Candidate: 3.12.2-0ubuntu1 Version table: *** 3.12.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens a tarball with file- roller, and without extracting the file, open it (ex. open PDF file with evince) the file-roller utilizes /tmp for this. 4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , where * is a changing folder name. If one logs out, or kills the file-roller process via: kill PID the temp files are left behind. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 245716] Re: file-roller puts temporary files in the home dir instead of /tmp
** Also affects: file-roller (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/245716 Title: file-roller puts temporary files in the home dir instead of /tmp Status in File Roller: Confirmed Status in file-roller package in Ubuntu: Triaged Status in file-roller package in Arch Linux: New Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy file-roller file-roller: Installed: 3.12.2-0ubuntu1 Candidate: 3.12.2-0ubuntu1 Version table: *** 3.12.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens a tarball with file- roller, and without extracting the file, open it (ex. open PDF file with evince) the file-roller utilizes /tmp for this. 4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , where * is a changing folder name. If one logs out, or kills the file-roller process via: kill PID the temp files are left behind. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299604] Re: evolution keeps asking for password
It's been more than 3 years that this bug started, and it is still not fixed!!! I had this problem in Ubuntu from 15.04 all the way to 17.04, and now in SolydK where it is even worse because none of the 10 possible ways to get gnome-keyring-deamon to start on login to work!!! I have tried every workaround offered, and although one or the other works here or there, it is completely inconsistant as to what will and will not work at any given time, and once you found a "Solution" you update the OS or something, and it fails again, then you can try every freakin' option all over again!! Its easier to break into the World Bank and crack the safe! If no one is capable of fixing the problem, then why not just change the way it works (doesn't work) all together: Dump the freaking gnome keyring dependancy completely, and make evolution remember passwords on it's own without it! It would have many advantages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1299604 Title: evolution keeps asking for password Status in evolution package in Ubuntu: Confirmed Status in evolution package in Fedora: New Bug description: Hi, I have connected my evolution to mail server (imap) and it asks EVERY time after login for password to that email account. It do not remember it, even when I tick "remember using keyring". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 23:00:38 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684293] [NEW] Reading text file corrupted
Public bug reported: Not sure, but it looks like text data is being displayed multiple times in the text window in an overlapping way, such that the contents of the text file cannot be seen. However, if one does "select" on any area of the file, the contents, under the selected area, does show up... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gedit 3.22.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 17:07:11 2017 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-02-09 (1165 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1684293 Title: Reading text file corrupted Status in gedit package in Ubuntu: New Bug description: Not sure, but it looks like text data is being displayed multiple times in the text window in an overlapping way, such that the contents of the text file cannot be seen. However, if one does "select" on any area of the file, the contents, under the selected area, does show up... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gedit 3.22.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 17:07:11 2017 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-02-09 (1165 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1684293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
