[Bug 2045948] [NEW] Incorrect time zone detected
Public bug reported: Ubuntu version: 22.04.3 LTS gnome-settings-daemon version: 42.1-1ubuntu2.2 My system is incorrectly setting the time zone to "MST (Denver, United States)" while I am currently in Austin, TX which is CST. geoclue shows the correct latitude/longitude: $ /usr/libexec/geoclue-2.0/demos/where-am-i Geolocation service in use Client object: /org/freedesktop/GeoClue2/Client/7 New location: Latitude:30.376800° Longitude: -97.893500° Accuracy:5000.00 meters Timestamp: Thu 07 Dec 2023 09:36:18 PM MST (1702010178 seconds since the Epoch) which corresponds to Austin, TX. My syslog shows 1000s of assertion errors in gsd-datetime: Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 302 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 1315 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_has_coords: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_city_name: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_country: assertion 'loc != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.14.0-1059.67-oem 5.14.21 Uname: Linux 5.14.0-1059-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 23:57:53 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220425-68+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-05-10 (576 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220425-07:09 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to jammy on 2023-06-15 (175 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2045948 Title: Incorrect time zone detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2045948/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 539243] Re: initial account creation window gives no indication of successful account creation
** Changed in: empathy (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/539243 Title: initial account creation window gives no indication of successful account creation To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/539243/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 576669] Re: Document Viewer has no support for common office document file formats
** Changed in: evince (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/576669 Title: Document Viewer has no support for common office document file formats To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/576669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-control-center Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/655713 Title: Logic needed to disable built in pointing devices when external devices are connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: unity (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Also affects: gnome-screensaver (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 637519] Re: Automatically select the user in GDM if there's only one
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #49 https://gitlab.gnome.org/GNOME/gdm/-/issues/49 ** Changed in: gdm Importance: Wishlist => Unknown ** Changed in: gdm Status: Expired => Unknown ** Changed in: gdm Remote watch: GNOME Bug Tracker #637566 => gitlab.gnome.org/GNOME/gdm/-/issues #49 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/637519 Title: Automatically select the user in GDM if there's only one To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/637519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993308] Re: Update gnome-calendar to 43.1
Hi Jeremy, we keep getting users reporting bugs on 43.0 upstream. Why does 43.1 not show up in https://packages.ubuntu.com/search?keywords=gnome- calendar=names=kinetic=all ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008532] Re: Typing a filename in a nautilus window, and the letters are not in the order I typed them.
This is not strictly a Nautilus bug, it's way bigger than that, it potentially affects all GTK4 applications when the system is under stress. I was told it's an ibus bug rather than GTK, so I filed it here, and I would really appreciate it if your team can help investigate or fix it: https://github.com/ibus/ibus/issues/2486 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008532 Title: Typing a filename in a nautilus window, and the letters are not in the order I typed them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2008532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943488] Re: when typeing too fast in the search line searching stops to work
If this is related to the bug I had filed upstream (linked above), then this should be fixed in Nautilus 43.1 or later. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1731 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1943488 Title: when typeing too fast in the search line searching stops to work To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1943488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991002] [NEW] gimp crashes when adding text
Public bug reported: Going to the text tool and trying to type anything instantly crashes gimp, every time. ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.1 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` /lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3d8)[0x7fe773b0add8] gimp(+0xec78e)[0x556263f4478e] gimp(+0xec84e)[0x556263f4484e] gimp(+0xec8ad)[0x556263f448ad] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fe772c42520] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x7ec0a)[0x7fe773bbdc0a] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(gdk_device_get_state+0x143)[0x7fe773bbdde3] gimp(gimp_device_info_get_device_coords+0x79)[0x5562640daf99] gimp(gimp_device_info_get_event_coords+0x56)[0x5562640db166] gimp(+0x1f9896)[0x556264051896] gimp(+0x1fe99b)[0x55626405699b] gimp(gimp_display_shell_canvas_tool_events+0x91)[0x556264047331] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1434d7)[0x7fe773d434d7] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7fe7731ddd2f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x30b76)[0x7fe7731f9b76] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xbb6)[0x7fe7731faf66] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7fe7731fb7a3] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x26f024)[0x7fe773e6f024] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_widget_send_focus_change+0x95)[0x7fe773e76975] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x27dee6)[0x7fe773e7dee6] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x280f26)[0x7fe773e80f26] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x281193)[0x7fe773e81193] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1434d7)[0x7fe773d434d7] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7fe7731ddd2f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x30564)[0x7fe7731f9564] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xbb6)[0x7fe7731faf66] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7fe7731fb7a3] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x26f024)[0x7fe773e6f024] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_main_do_event+0x54b)[0x7fe773d428bb] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x6716b)[0x7fe773ba616b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x26b)[0x7fe7730e4d1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xaa6f8)[0x7fe7731396f8] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x73)[0x7fe7730e4293] gimp(app_run+0x3fc)[0x556263f49adc] gimp(main+0x362)[0x556263f3f752] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7fe772c29d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7fe772c29e40] gimp(_start+0x25)[0x556263f3f8d5] ``` ** Affects: gimp (Ubuntu) Importance:
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
This one seemed like it refused to wake even enough to draw a black scree, just stayed asleep. I've no idea if this is hlepful ** Attachment added: "refuses_to_wake.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Another purple screen lockup. It's now also more common the system runs how while closed. ** Attachment added: "purple_screen_lockup-8_april.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've still not tried other kernels, in part because ubuntu keeps pushing out new OEM kernels, so I give them all a try, but the same basic problem persist, either gnome-shell gives only a black screen, or else the whole system hangs on the purple screen. I've far more diverse crashes with the latest kernels and the bolt upgrade: https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now more reliably fails unsleep, but I've not yet seen any real crash under 5.14.0-1031-oem. I've still not tried non OWM kernels. ** Attachment added: "black_screen_with_mouse-29_march-b.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5574448/+files/black_screen_with_mouse-29_march-b.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd another crash with a purple screen and no mouse movement, but this time only a 10 minute lid close caused the crash. Awful lot of gdm and gnome-shell errors this time, but not clear the source. ** Attachment added: "purple_no_mouse-23_march.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572272/+files/purple_no_mouse-23_march.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's again waking with a black screen in which only mouse and Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from prior to reboot, probably more relevant than grabbing the actual reboot. Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done. Mär 23 07:09:16 aletheia systemd-logind[1556]: Lid opened. Mär 23 07:09:16 aletheia Tor[1683]: Tor has been idle for 26589 seconds; assuming established circuits no longer work. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: The canary thread is apparently starving. Taking action. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoting known real-time threads. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoted 0 threads. Mär 23 07:09:16 aletheia Tor[1683]: Heartbeat: Tor's uptime is 0:00 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. Mär 23 07:09:16 aletheia systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mär 23 07:09:16 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:09:16 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:09:16 aletheia systemd[1]: Starting Daily apt download activities... Mär 23 07:09:16 aletheia systemd[1]: Starting Refresh fwupd metadata and update motd... Mär 23 07:09:16 aletheia systemd[1]: Starting Message of the Day... Mär 23 07:09:16 aletheia systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs... Mär 23 07:09:16 aletheia systemd[1]: motd-news.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Message of the Day. Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:09:16 aletheia kernel: PM: suspend exit Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress Mär 23 07:09:16 aletheia fwupd[3148]: 06:09:16:0867 FuEngine failed to record HSI attributes: failed to get historical attr: json-glib version too old Mär 23 07:09:16 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Suspend. We compare this semi-locked gnome-shell with a working unsleep from a brief lid close: Mär 23 07:42:19 aletheia kernel: Restarting tasks ... Mär 23 07:42:19 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:42:19 aletheia systemd-logind[1529]: Lid opened. Mär 23 07:42:19 aletheia kernel: done. Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:42:19 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:42:19 aletheia kernel: PM: suspend exit Mär 23 07:42:19 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:42:19 aletheia systemd[1]: Finished Suspend. I wind up with gnome-shell being stuck when "kernel: done" never appears, the "upowerd" line appears twice, and we get the error: Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress I've maybe some early unsleep phase not finishing correctly, which then convinces gsd-power believing that sleep continues? * Irrelevant looking differences: The mei_hdcp comes before the lid opened line. Activities like tor and rt-kit-daemon have not been asleep long enough to be doing restart work. ** Attachment added: "black_screen_with_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572108/+files/black_screen_with_mouse.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Appears nope I've purely a sleep problem, unless all this fwupd playing turnned off hibernate: ``` root@aletheia:/home/jeff/Downloads# systemctl status hibernate.target ● hibernate.target - Hibernate Loaded: loaded (/lib/systemd/system/hibernate.target; static; vendor prese> Active: inactive (dead) Docs: man:systemd.special(7) root@aletheia:/home/jeff/Downloads# systemctl status hybrid-sleep.target ● hybrid-sleep.target - Hybrid Suspend+Hibernate Loaded: loaded (/lib/systemd/system/hybrid-sleep.target; static; vendor pr> Active: inactive (dead) Docs: man:systemd.special(7) ``` -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've found some lenovo firmware oddities too https://github.com/fwupd/firmware-lenovo/issues/210 so I'll poke around there too. ** Bug watch added: github.com/fwupd/firmware-lenovo/issues #210 https://github.com/fwupd/firmware-lenovo/issues/210 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's related to during being suspended: It does not trigger on pressing suspend from the menu bar, waiting briefly, and then pressing keys to wake. It also does not trigger if I close and open the lid less than a minute later. It can now trigger if I close the lid and then reopen the lid 10 minutes later. At this point it arrives at a purple ubuntu login screen, but no responses to keyboard or mouse, and not network presence. Could this be caused by the system changing sleep/suspend mode while sleeping/suspended? Could this be related to /swapfile being only 4 gigs, while main memory is 16 gigs? It's a ThinkPad X1 Carbon Gen 11 running a kernel 5.14.0-1027-oem for a Gen 9 (nothing else exists afaik). I've no idea what OEM kernels change of course, but I can try to figure out changing the kernel. I'll likely need to change something in /etc/default/grub to get access to a grub boot menu to choose kernels. ** Attachment added: "purple_no_mouse_two.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571706/+files/purple_no_mouse_two.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Also the Fn+Ctrl+Alt+F?? keys no longer worked here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd something new this time, after sleep/suspend it returned to the purple login screen, but now nothing worked, no mouse or keyboard. It ran the fan for a little while, so I give it some time to return, but no luck. ** Attachment added: "purple_no_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571532/+files/purple_no_mouse.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
oops alright. I've no gnome-shell reports in /var/crash only another systemd-timesyncd report. I don't think gnome-ghell is crashing, but sometimes just stuck when emerging from suspend. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Is it normal that gnome-session-bin is installed but gnome-session is not installed? I believe this black screen version is different because when switching back with Fn+Ctrl+Alt+F1 it simply returns to the black screen, without any purple password prompt. I suppose another problem must be causing both versions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It now manifests as a black screen with the same behavior, mouse works but no keyboard, except for Fn+Alt+Ctrl+F?? working. I've attacked the output of journalctl but from the current boot since I used killall -HUP gnome-shell, which yes leave some applications running, but not firefox (or tor browser). It's much less common now but this one happened on suspend trigger by the lid being closed. Thanks! :) ** Attachment added: "black_screen_killall_hup_gnomeshell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5570958/+files/black_screen_killall_hup_gnomeshell.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's only the three built in extensions installed. Thanks I'll run journalctl -b-1 > prevboot.txt next time. ls /var/crash/ says _usr_lib_systemd_systemd-timesyncd.102.crash _usr_lib_systemd_systemd-timesyncd.102.upload _usr_lib_systemd_systemd-timesyncd.102.uploaded I only see a similar error on https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a Is the lock screen handled by gnome-shell itself or some outside process like gdm3? If there some signal or whatever I can send to gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930943] [NEW] package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error
Public bug reported: Novice user. submitting report because Ubuntu said I should ProblemType: Package DistroRelease: Ubuntu 20.04 Package: evolution-common 3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 5 11:35:08 2021 ErrorMessage: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error InstallationDate: Installed on 2021-05-27 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: evolution Title: package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1930943 Title: package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1930943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1136644] Re: gedit search function is not practical anymore
While it won't address your UX annoyances, I have filed an issue upstream proposing an approach to make live search faster for big files: https://gitlab.gnome.org/GNOME/gedit/-/issues/398 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1136644] Re: gedit search function is not practical anymore
** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #398 https://gitlab.gnome.org/GNOME/gedit/-/issues/398 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/-/issues/398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905513] [NEW] Mouse does not respect primary/secondary button settings after being disconnected and reconnected.
Public bug reported: After installing 20.04, in the gnome control center I selected the right mouse button to be the primary button. When I unplug the mouse and replug it in, the right mouse button is no longer the primary button. When I look at the gnome control center, the setting says that the right mouse button is the primary button. To get the right button as the primary button I need to click on the GUI control to make the left button primary and then on the same control a second time to make the right button primary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108853~20.04~8bcf10e~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 20:43:26 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-10-04 (2244 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-12 (12 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1905513 Title: Mouse does not respect primary/secondary button settings after being disconnected and reconnected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1616332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1374403] Re: EOG - CMYK jpg colors are saturated and not correct
This bug still exist, 2020 here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1374403 Title: EOG - CMYK jpg colors are saturated and not correct To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1374403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850707] Re: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts
This might be https://gitlab.gnome.org/GNOME/evolution/-/issues/538 ? ** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #538 https://gitlab.gnome.org/GNOME/evolution/-/issues/538 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1850707 Title: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1850707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
Just ran into this same issue with Linux Mint 19.3 with Cinnamon 4.4.8 Using this instruction worked for me also. Burning completed without further issue. cd /usr/bin sudo chmod -v 4711 cdrdao udo chmod -v 4711 wodim sudo chmod -v 0755 growisofs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792085] Re: MTP not working/very slow on Bionic
I was able to fix this on Ubuntu 18.04 (bionic), which comes with libmtp-common=1.1.13 by installing a newer version of libmtp 1.1.16. Now Ubuntu transfers huge numbers of songs between my phone and laptop by simply drag-and-drop in Nautilus. sudo apt install build-essential pkg-config wget libusb-1.0-0-dev libusb-dev wget http://downloads.sourceforge.net/project/libmtp/libmtp/1.1.16/libmtp-1.1.16.tar.gz tar xzf libmtp-1.1.16.tar.gz cd libmtp-1.1.16 ./configure make sudo make install I didn't even have to uninstall the old version, and also no need for android-file-transfer or jmtpfs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849254] [NEW] Noto Sans Mono Bold not available from /etc/fonts/local.conf
Public bug reported: I tried to change my monospace font to "Noto Sans Mono Bold" in /etc/fonts/local.conf but that didn't have an effect so I did a little digging. First I ran $ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config Which succeeded, then: $ fc-list :style=bold | grep -i notosansmono >/usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf: Noto Sans Mono:style=Bold So then: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf | less which seemed to return a normal looking result similar to: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf | less Then I ran: $ fc-match -s "monospace" | grep -i bold >DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" >MathJax_Fraktur-Bold.otf: "MathJax_Fraktur" "Bold" >padmaa-Bold.1.1.ttf: "padmaa-Bold.1.1" "Bold.1.1" >DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique" Which obviously isn't right since it isn't in that list. Also: $fc-match -s "NotoSansMono" | grep -i notosansmono >NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular" My system is up to date and here is my version: $lsb_release -a lsb_release: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $uname -a >Linux 9343 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 >x86_64 x86_64 x86_64 GNU/Linux ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1849254 Title: Noto Sans Mono Bold not available from /etc/fonts/local.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1849254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296872] Re: Charge level and the remaining time are estimated incorrectly for the battery in Logitech Wireless Mouse with Unifying receiver
Bug is still present. Ubuntu 18.04 desktop, upgrade from 16.04.5 Logitech M310, connected using Logitech Unify USB dongle. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1296872 Title: Charge level and the remaining time are estimated incorrectly for the battery in Logitech Wireless Mouse with Unifying receiver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1296872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: unity (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: gnome-screensaver (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725955] Re: "Printer added" notification
Happens to me in 18.04 desktop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1725955 Title: "Printer added" notification To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
After some googling around, in the end I ended up doing this: sudo apt install gnome-calculator sudo snap remove gnome-calculator And now both my keyboard calculator shortcut works as well as the calculator is no longer transparent. I have no idea what snap even is. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
It's hitting me right now. Which kind of info should I be providing? I'm on Ubuntu 18.04 desktop, latest `apt dist upgrade`... ** Attachment added: "screenshot of transparent calc" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+attachment/5242387/+files/calc_back.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799052] [NEW] Application/task bar on left side is visible and operable after screen lock
Public bug reported: Didn't notice this yesterday, but left my machine running over night and this morning when I went to log in, the application bar on the left was visible. I tried clicking on items on the bar and it launched those applications. If someone had a privileged script or app pinned to their task bar, it appears that anyone could launch it. The window isn't visible however. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 09:29:03 2018 ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2017-10-07 (379 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-19 (1 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Screenshot from 2018-10-21 09-23-59.png" https://bugs.launchpad.net/bugs/1799052/+attachment/5203564/+files/Screenshot%20from%202018-10-21%2009-23-59.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1799052 Title: Application/task bar on left side is visible and operable after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 253195] New vacancies in our company
Good day! We considered your resume to be very attractive and we thought the vacant position in our company could be interesting for you. Our firm specializes in online services in the matter of business administration. We cooperate with different countries and currently we have many clients in yours region. Due to this fact, we need to increase the number of our destination representatives' regular staff. Part-time and full-time employment are both currently important. We offer a flat wage from $1500 up to $7000 per month. If you are interested in our offer, please visit our web page. Attention! Accept applications only on this and next week. Respectively submitted Personnel department -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/253195 Title: gnome-dictionary-applet must strip surrounding spaces from input To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-utils/+bug/253195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
I think I'm experiencing the same problem. I installed Ubuntu 18.04 beta last Tuesday. When I power on my computer, the screen blinks 50-53 times over the span of 2-1/2 minutes (this is perfectly reproducible) and then for the rest of the session, everything works flawlessly. After LinuxFest Northwest, I was told to do an apt dist-upgrade and that did not clear the problem. I have two video cards: VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1) I'm not sure what other information would be helpful. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767185] [NEW] Must click logout twice to log out.
Public bug reported: Upgraded from Xenial to Bionic. Now, when I select Logout from the menu (on both Unity and Gnome) I must do so twice before the logout is initiated. Steps: click the menu in the upper right corner click the Logout option Menu closes Click the menu again Click the logout option again Logout dialog appears Expected steps: Same as above, without having to repeat myself. Note I tried this in both Unity and Gnome3 and the results are the same in both. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:58:16 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1767185 Title: Must click logout twice to log out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1767185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
@seb, per discussion via IRC, here are my logs from /var/log/dist- upgrade (upgrade started last night and finally wrapped up this morning after a lot of coffee and swearing). To answer the questions: I started off with 'do-release-upgrade -d' last night and ended up this morning with a reboot into rescue mode and a lot of 'apt-get -f install', 'dpkg --reconfigure -a' and finally an 'apt-get dist-upgrade' (or was it a -f install again?) to get the remaining held 2400+ packages updated. NOW I believe I'm finally updated to Bionic and running again. Also, will asked if I had manually modified anything in /etc/apt/sources.list and the answer is no, all that was handled by the upgrader. ** Attachment added: "xenial-bionic-upgrade-logs.tgz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127748/+files/xenial-bionic-upgrade-logs.tgz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
FWIW, it's entirely possible I had other issues that just also included this one, or just exposed this one where I may not have seen it otherwise. This just happened to be the only one that Apport was able to create and submit. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767145] [NEW] Power status says my battery is fully charged. I'm on a desktop. I have no battery
Public bug reported: Just upgraded to bionic. Gnome says my battery is fully charged. ONly thing is, this isn't a laptop. I have no batter. It is impossible for my battery to be fully charged, since it doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-power-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:38:12 2018 InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "See my non-existent battery's status." https://bugs.launchpad.net/bugs/1767145/+attachment/5127725/+files/gnome-power-panel.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1767145 Title: Power status says my battery is fully charged. I'm on a desktop. I have no battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1767145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Grr... autocorrect on OSX while I wait for Ubuntu to work again (finish upgrading). That should have said "leaving me with a nearly unbootable system." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
FWIW, this error (my bug was marked a duplicate) completely broke my Xenial - Bionic upgrade, leaving me with a nearly unbeatable system. I had to boot into Rescue Mode and do a lot of ctrl-C ing to get around this, and once I thought it had finally installed all the bionic packages, I rebooted into the OS proper, and STILL found it hadn't actually upgraded so I had to run 'apt-get -f install' again to finish the other 2400+ package updates. I spent most of my morning just trying to get back to a bootable system that was only half-way upgraded (lsb-release told me I was in 18.04, name -a said I was still on 4.13 from 16.04.4, and apt said I still had 2400+ packages to update). If I was not an experienced user who knew roughly how to manually kick this stuff to get around broken package updates, I'd have been considerably more upset than I already am. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767129] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1767129 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752430] [NEW] tracker-miner-apps fails when /usr/local/share/applications is a link
Public bug reported: /usr/local/share/applications is a symbolic link on one of my systems because I am using xstow to manage packages in /usr/local. There are valid .desktop files within this linked directory, however. tracker-miner-apps cannot parse this file/link/directory, so it keeps trying forever with high CPU usage, and spewing error messages to syslog. Feb 28 12:55:25 gallium gnome-session[30827]: (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications'' Feb 28 12:55:25 gallium gnome-session[30827]: message repeated 40 times: [ (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications''] I worked around the problem by making /usr/local/share/applications and directory containing symbolic links to .desktop files within the stowed packages. This is what it looks like now: jeffrey@gallium:/usr/local/share/applications$ ls -l total 20 -rw-r--r-- 1 root root 13 Feb 25 20:27 mimeinfo.cache lrwxrwxrwx 1 root root 61 Feb 28 13:14 thinlinc-setup.desktop -> ../../stow/thinlinc/share/applications/thinlinc-setup.desktop lrwxrwxrwx 1 root root 65 Feb 28 13:14 thinlinc-webaccess.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webaccess.desktop lrwxrwxrwx 1 root root 62 Feb 28 13:14 thinlinc-webadm.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webadm.desktop lrwxrwxrwx 1 root root 75 Feb 28 13:12 vncviewer.desktop -> ../../stow/tigervnc-Linux-x86_64-1.6.0/share/applications/vncviewer.desktop After this change tracker-miner-apps seems to be happy. More generally, it's bad and wrong that an indexer can peg the CPU when it has a bug. It should limit rescan attempts to a certain number and then put them on a queue to check infrequently. Would it be just as aggressive if I created a bad .desktop file? An indexer should be as tolerant as possible of bad files, IMO. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker-miner-fs 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 13:26:36 2018 InstallationDate: Installed on 2015-11-19 (832 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) JournalErrors: -- No entries -- ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tracker UpgradeStatus: Upgraded to xenial on 2016-09-17 (528 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1752430 Title: tracker-miner-apps fails when /usr/local/share/applications is a link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1752430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
I've just started getting this on my laptop with a current version of Linux Mint Cinnamon with all the updates. Also if I close my laptop (so it sleeps) when I open it, sometimes the screen just goes blank and even REISUB or REISUO will not work. I've also had to run fschk to fix issues which I think are cause by forcing the shutdown while the screen is blank. Not sure if the blank screen is related to the gnome-keyring- daemon or not, but they both started at the same time. There have been a lot of updates recently with the Intel chip problem, so I have no idea which (if any) have caused the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/608162 Title: GNOME Keyring Daemon stops panel's shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727310] Re: Screen brightness slider isn't working on Acer Aspire v5 571g
I'm experiencing the same. Acer Aspire S7 392. Worked under 17.04, not under 17.10. The only way I can change my screen brightness currently is via the command line: sudo tee /sys/class/backlight/intel_backlight/brightness <<< 200 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727310 Title: Screen brightness slider isn't working on Acer Aspire v5 571g To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726922] Re: gnome-calendar keeps asking for my google password
Here is the workaround for people coming into this bug with Two Factor Auth set. You need to generate an application specific password for the Google acct in "Online Accounts" from this page: https://security.google.com/settings/security/apppasswords Google's full documentation on generating application specific passwords for applications that aren't compatible with MFA: https://support.google.com/accounts/answer/185833?hl=en I saw this as well, and set an app specific password to get around it, but it would be nice if I didn't have to use that workaround. :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1726922 Title: gnome-calendar keeps asking for my google password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
Comment #40 (the two killall commands) did it for me on 14.04.5 64-bits desktop with a Samsung Note 3. THANKS! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984899] Re: right-click menu profile preference not work
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/984899 Title: right-click menu profile preference not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/984899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689819] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 error on bootup
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: new install last night, updated after install and started setting up my new system. rebooted, freze, hard restart, then got this error on booting backup. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 10 07:18:30 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-10 (0 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1689819 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 error on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1689819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687647] [NEW] udev version 232-21ubuntu3 from ports is broken on Zesty s390x
Public bug reported: I'm attempting to install some cert tools on a z/KVM instance of Zesty. This is failing because udev exits with an error during installation. The apt logs show this: Setting up udev (232-21ubuntu3) ... addgroup: The group `input' already exists as a system group. Exiting. cat: '/sys/class/net/eth*/address': No such file or directory dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 and because of that, all other packages up the dependency chain fail to install. Interestingly, this is resolved by installing the older version of udev and libudev1 ubuntu@s1lp9g003:~$ apt-cache policy udev udev: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 libudev1=232-21ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-46-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libudev1 udev 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. 6 not fully installed or removed. Need to get 0 B/1056 kB of archives. After this operation, 3072 B disk space will be freed. Do you want to continue? [Y/n] y dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2 (Reading database ... 99656 files and directories currently installed.) Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ... Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ... dpkg: warning: downgrading libudev1:s390x from 232-21ubuntu3 to 232-21ubuntu2 Preparing to unpack .../libudev1_232-21ubuntu2_s390x.deb ... Unpacking libudev1:s390x (232-21ubuntu2) over (232-21ubuntu3) ... Setting up libudev1:s390x (232-21ubuntu2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Setting up udev (232-21ubuntu2) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (232-21ubuntu3) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up python3-checkbox-support (0.34.0~rc1+git201704041517+pkg52~ubuntu17.04.1) ... Setting up plainbox-provider-resource-generic (0.31.0+git201704241134+pkg28~ubuntu17.04.1) ... Setting up plainbox-provider-checkbox (0.35.0+git201705012258+pkg34~ubuntu17.04.1) ... Setting up plainbox-provider-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Setting up canonical-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Processing triggers for initramfs-tools (0.125ubuntu9) ... update-initramfs: Generating /boot/initrd.img-4.10.0-20-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: vda (). Done. As you can see, once I installed the original zesty version of udev and libudev1, my packages succeeded in completing installation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: s390x CustomUdevRuleFiles: 41-generic-ccw-0.0.0003.rules 41-generic-ccw-0.0.0004.rules 41-generic-ccw-0.0..rules 41-generic-ccw-0.0.0005.rules 41-cio-ignore.rules 41-generic-ccw-0.0.0001.rules 41-generic-ccw-0.0.0002.rules Date: Tue May 2 11:41:16 2017 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcKernelCmdLine: root=/dev/mapper/s1lp9g003_vg-s1lp9g003_lv crashkernel=196M SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-04-13 (18 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug s390x zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687647 Title: udev version 232-21ubuntu3 from ports is broken on Zesty s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1623666] Re: iOS device contents not displayed in Ubuntu
@Sadi Yumuşak (sa-yu) #31: I had the same problem you documented, and found it was because of a conflicting pkg-config. In my case, I had one installed in ~/.linuxbrew/bin/pkg-config, which was picked up in my PATH before /usr/bin/pkg-config. The solution was to temporarily rename the one in my linuxbrew so that the one in /usr/bin was used. @J. McDonald (mcdonald-joseph) #34: You list the commands you've used, but not their output. I suspect that the output of autogen.sh is similar to what sa-yu experienced in his note. The specific error you're seeing from make means that the input file that it expects by default, which is named Makefile, cannot be found. It is the autogen.sh script which produces that Makefile. Its failure is likely due to a problem similar to what sa-yu describes. @Adam Szmigin (smidge) @28: #28 Fine instructions. I confirm that they work on Linux Mint 18.1 x64. Just for clarity, readers should know that the command "$ cd ~/path/to/my/build/dir" shouldn't be taken literally. Instead, it's shorthand for a couple commands like $ mkdir -p ~/build/libimobiledevice $ cd ~/build/libimobiledevice -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1617468] Re: Package contains files in /usr/@DATADIRNAME@/locale
Could someone provide the commands to merge the files into the share directory properly? I think it'll be something like: cd /usr sudo cp -r @DATADIRNAME@/* share But I'm not really an expert and I don't want to experiment. Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1617468 Title: Package contains files in /usr/@DATADIRNAME@/locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1617468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627637] [NEW] bad alloc on large (but not too large) image
Public bug reported:
For this example, I've created an entirely white png (attached to the
bug report) with size 2400 x 36000. I saved it at compression level 9
(or whatever gimp means by that) and in 8-bit RGB. I would expect eog
to be able to display this because 2400 * 36000 * 4 colours is 330 MB,
which is vastly less than the available RAM on my machine. While X
represents window dimensions with 16 bit values, which may perhaps be
signed (I didn't check my host's type definitions), I don't expect eog
to allocate a pixel-to-pixel window for the image. My screen's size is
ample.
This arose because of a real image of the same dimensions, but which I
can't attach here. The behaviour is the same.
jeff@starshine:data_2016-09-01 $ eog /tmp/2400x36000.png
** (eog:26198): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-3UXmMLd2Wv: Connection refused
(eog:26198): Gdk-ERROR **: The program 'eog' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 415 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
133, jeff@starshine:data_2016-09-01 $ ubuntu-bug eog
** (apport-gtk:27057): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-3UXmMLd2Wv: Connection refused
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
jeff@starshine:data_2016-09-01 $
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: eog 3.18.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: i3
Date: Mon Sep 26 10:24:34 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-17 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: eog
UpgradeStatus: Upgraded to xenial on 2016-05-15 (133 days ago)
** Affects: eog (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
** Attachment added: "Opening this image with eog results in a bad allocation
error."
https://bugs.launchpad.net/bugs/1627637/+attachment/4748707/+files/2400x36000.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/1627637
Title:
bad alloc on large (but not too large) image
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1627637/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 938751] Re: jpeg images are washed out or colors are skewed
I had this problem on Ubuntu 14.04. Removing the ICC Profile, as suggested in comment #14, solved the problem for me. I'm also wondering where that profile came from... Why do some users have it and others don't? I don't ever remember intentionally installing or making changes to ICC profiles. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: jpeg images are washed out or colors are skewed To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557194] Re: When deleting an image, view switches to wrong photo
This is not always repeatable, and I haven't yet figured out what causes the bug to appear. When it does happen, it happens consistently in that session, but this could also be related to something in the directory I'm viewing at that time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1557194 Title: When deleting an image, view switches to wrong photo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1557194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557194] [NEW] When deleting an image, view switches to wrong photo
Public bug reported: In Image Viewer (eog 3.10.2-0ubuntu5.1, running Linux Mint 17.3 Rosa, but with the 4.4.0 kernel), I'm noticing a weird behavior when I delete an image from within Image Viewer. I'll be scanning through multiple files (hitting Next, Next, Next) and wanting to delete a few of them. 1. The first time in a session that I delete a photo, no problem. Upon deleting Photo A, the program will automatically advance to the next Photo B. 2. Scan through more photos... Photo C, which I want to keep, then Next again. 3. Now I want to delete some subsequent photo D. I hit the Delete button on the keyboard... 4. It pops up 'Are you sure you want to move "Photo D" to the trash?', which is expected and correct. The bug is that while this dialog is open the viewer goes back to showing photo B. This is very troubling because I wanted to keep photo B. 5. When I hit "Yes", the dialog closes and the program automatically advances to Photo E, the one after Photo D was. (This is correct.) Note that even though the program shows the wrong image while the dialog is open, the correct image (Photo D) is the one that's deleted. ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1557194 Title: When deleting an image, view switches to wrong photo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1557194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
Fair enough. we can count it as "weirdness when running an alpha" :) it's working so I've reset the status to Fix Released now that I understand the underlying mechanics a bit better. Of course, now I'm also seeing the other issue that flocculant mentioned, but as discussed in earlier comments, that's a different bug. ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
Oh, and last but not least, thanks for the suggestions to get the cache properly updated. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
Also, since appstream-util was never installed in the first place, do I need that installed now? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
Hrmmm... appstream-util was not installed (why is that not installed by default, or perhaps it is now but wasn't when I installed Xenial originally a couple weeks ago). Since appstream-util was never installed in the first place, the first thing I did was simply run update-manager to update the cache (isn't that the same action as apt-get update?) That seems to have fixed it... so, are the apt-cache and whatever update-manager is using not the same cache? (I don't tend to use GUI tools, this is Linux, I use CLI stuff and have been using apt for years to maintain and install packages). I also manage this system with landscape, so how does that tie into this? am I now going to need to remember to run update manager before trying to use gnome-software even though the system is kept up to date daily via Landscape? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
tuxpaint: Installed: (none) Candidate: 1:0.9.22-2 Version table: 1:0.9.22-2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages That makes two things from Universe that "should" be there but are not. As far as I can tell, the current gnome-software is still only showing me the things that are already installed, it does NOT show anything that "could be" installed. ** Attachment added: "no-tuxpaing.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+attachment/4585774/+files/no-tuxpaing.png ** Changed in: gnome-software (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1548933] Re: It only shows installed apps, not available ones
What version is this fixed in? gnome-software: Installed: 3.19.91~git20160229.ceb6b9d-0ubuntu1 Candidate: 3.19.91~git20160229.ceb6b9d-0ubuntu1 Version table: *** 3.19.91~git20160229.ceb6b9d-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status bladernr@galactica:~/Downloads$ apt-cache policy emacs emacs: Installed: (none) Candidate: 46.1 Version table: 46.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages And note the screen shot does not show emacs as an installable option. ** Attachment added: "no-emacs" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+attachment/4585768/+files/no-emacs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1548933 Title: It only shows installed apps, not available ones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1548933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1544747] [NEW] No udev persistent rules in Xenial = strange device names for NICs
Public bug reported: Fresh install of Xenial on an intel NUC with 1 onboard GigE and one USB GigE NIC. I was setting up networking for MAAS and discovered that the device names were ridiculous: bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr eno1 Link encap:Ethernet HWaddr ec:a8:6b:fb:9f:66 enx8cae4cff4099 Link encap:Ethernet HWaddr 8c:ae:4c:ff:40:99 In the previous Trusty install on this NUC with the same USB dongle, they were named eth0 and em1. The predictable standard device names. Looking at udevadm: P: /devices/pci:00/:00:19.0/net/eno1 E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1 E: ID_BUS=pci E: ID_MM_CANDIDATE=1 E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection E: ID_MODEL_ID=0x1502 E: ID_NET_DRIVER=e1000e E: ID_NET_LABEL_ONBOARD=en L1U1 E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link E: ID_NET_NAME_MAC=enxeca86bfb9f66 E: ID_NET_NAME_ONBOARD=eno1 E: ID_NET_NAME_PATH=enp0s25 E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD. E: ID_PATH=pci-:00:19.0 E: ID_PATH_TAG=pci-_00_19_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: ID_VENDOR_ID=0x8086 E: IFINDEX=2 E: INTERFACE=eno1 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1 E: TAGS=:systemd: E: USEC_INITIALIZED=5400250 P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099 E: DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099 E: ID_BUS=usb E: ID_MM_CANDIDATE=1 E: ID_MODEL=AX88178 E: ID_MODEL_ENC=AX88178\x20 E: ID_MODEL_FROM_DATABASE=AX88178 E: ID_MODEL_ID=1780 E: ID_NET_DRIVER=asix E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link E: ID_NET_NAME=enx8cae4cff4099 E: ID_NET_NAME_MAC=enx8cae4cff4099 E: ID_NET_NAME_PATH=enp0s29u1u5 E: ID_OUI_FROM_DATABASE=Plugable Technologies E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0 E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0 E: ID_REVISION=0001 E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02 E: ID_SERIAL_SHORT=02 E: ID_TYPE=generic E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class E: ID_USB_DRIVER=asix E: ID_USB_INTERFACES=:00: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass E: ID_VENDOR=ASIX_Elec._Corp. E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp. E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp. E: ID_VENDOR_ID=0b95 E: IFINDEX=3 E: INTERFACE=enx8cae4cff4099 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 /sys/subsystem/net/devices/enx8cae4cff4099 E: TAGS=:systemd: E: USEC_INITIALIZED=8700146 And finally, looking in /etc/udev: bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/* /etc/udev/udev.conf /etc/udev/rules.d: .. . /etc/udev/hwdb.d: .. . There are NO rules at all in udev for persistent names. Not even some samples and defaults. Looking at a completely different Xenial system with a single GigE NIC: bladernr@galactica:~$ ifconfig enp2s0Link encap:Ethernet HWaddr 40:8d:5c:51:5b:0d P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0 E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0 E: ID_BUS=pci E: ID_MM_CANDIDATE=1 E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller E: ID_MODEL_ID=0xe091 E: ID_NET_DRIVER=alx E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link E: ID_NET_NAME_MAC=enx408d5c515b0d E: ID_NET_NAME_PATH=enp2s0 E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD. E: ID_PATH=pci-:02:00.0 E: ID_PATH_TAG=pci-_02_00_0 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros E: ID_VENDOR_ID=0x1969 E: IFINDEX=2 E: INTERFACE=enp2s0 E: SUBSYSTEM=net E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp2s0 E: TAGS=:systemd: E: USEC_INITIALIZED=752502 and again, nothing in the udev rules: bladernr@galactica:~$ ls -a /etc/udev/* /etc/udev/udev.conf /etc/udev/hwdb.d: . .. /etc/udev/rules.d: . .. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 228-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 11 16:36:35 2016 InstallationDate: Installed on 2016-02-10 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed root=UUID=b53bf9e5-5cab-4ebd-98cc-a07ddffe53af ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: RKPPT10H.86A.0032.2014.0303.1322 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D53427RKE dmi.board.vendor: Intel Corporation
[Bug 1294366] Re: Empathy does not open under Ubuntu 14.04 LTS
Same for me. Fixed by installing libwayland-egl1-mesa-lts-vivid. Please add that package as a dependency. ** Changed in: empathy (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1294366 Title: Empathy does not open under Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1294366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867] Re: empathy needs to support OTR encryption
Ick! If telepathy makes doing OTR securely impossible, that's very bad news. We should lobby to remove Empathy and telepathy from Debian stable and Ubuntu then. OTR is critical post Snowden. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1112061] Re: unity forgets focus-follows-mouse setting across update and reboot
Running 14.04. Installed Unity Tweak Tool specifically to let me turn on focus follows mouse. Did so. Multiple times now I discover that it has reset itself back to focus mode click through no action on my part. My best guess it that it can happen mid session, and not just across a reboot, but I haven't yet specifically noted when it happens exactly, nor pinned down a cause. However, when it does happen, the unity tweak tool happily tells me that the mode is back to click instead of mouse. This needs a fix. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1112061 Title: unity forgets focus-follows-mouse setting across update and reboot To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1112061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1388951] Re: gvfsd-sftp crashed with SIGABRT when unmounting dropped sftp connection
*** This bug is a duplicate of bug 896670 *** https://bugs.launchpad.net/bugs/896670 ** This bug has been marked a duplicate of bug 896670 gvfsd-ftp crashed with SIGABRT in g_assertion_message() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1388951 Title: gvfsd-sftp crashed with SIGABRT when unmounting dropped sftp connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1388951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 896670] Re: gvfsd-ftp crashed with SIGABRT in g_assertion_message()
I've been experiencing this bug on Ubuntu 14.04 amd64. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/896670 Title: gvfsd-ftp crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/896670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead
Can someone please close this bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected
Can someone please close this, it is obviously not necessary after all this time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/655713 Title: Logic needed to disable built in pointing devices when external devices are connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1082901] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()
I get this error on Ubuntu 14.04, right after I log in to my desktop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1082901 Title: nautilus crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1082901/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 503372] Re: Evince doesn't retain settings in Lucid
At some point, this bug stopped being an issue for me, but that was several versions ago. In Ubuntu 14.04, I can confirm that I'm still experiencing this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/503372 Title: Evince doesn't retain settings in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/503372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381897] [NEW] Evince will not zoom in with shortcut key in 14.10 Release Candidate?
Public bug reported: Evince shortcut key for zoom-in does not work after I upgraded to 14.10 Release Candidate. I am running an AsusUx301LA with everything upgraded on 14.10 and this still happens. At one point I got it to zoom in with Fn++ but Ctrl++ has never worked. Now Fn++ is never working. Let me know if any other info is needed. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1381897 Title: Evince will not zoom in with shortcut key in 14.10 Release Candidate? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1381897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1381897] Re: Evince will not zoom in with shortcut key in 14.10 Release Candidate?
I realized the issue is that I actually have to hit Ctrl+Shift+= aka Ctrl++. I swore I always just used to hit Ctrl+= and it would zoom in. Anyway to get this functionality back. I use a standard American(USA) laptop keyboard with a function key. It's an Asus UX302LA laptop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1381897 Title: Evince will not zoom in with shortcut key in 14.10 Release Candidate? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1381897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1364789] [NEW] Cannot update or download programs because package libpyzy-1.0-0 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/pyzy/db/open-phrase.db' to '
Public bug reported: I have been having this issue for well over 2 weeks now. I cannot get any upgrades or download any programs in 14.04 because this package is not installed. And I cannot update or find the package to download. So nothing is changing. Please, any help is appreciated. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpyzy-1.0-0 (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 AptOrdering: libpyzy-1.0-0: Install libpyzy-1.0-0: Configure ibus-pinyin: Configure Architecture: amd64 Date: Wed Sep 3 00:52:59 2014 DuplicateSignature: package:libpyzy-1.0-0:(not installed):cannot copy extracted data for './usr/share/pyzy/db/open-phrase.db' to '/usr/share/pyzy/db/open-phrase.db.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/pyzy/db/open-phrase.db' to '/usr/share/pyzy/db/open-phrase.db.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-05-26 (99 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: libpyzy Title: package libpyzy-1.0-0 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/pyzy/db/open-phrase.db' to '/usr/share/pyzy/db/open-phrase.db.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to trusty on 2014-08-11 (23 days ago) ** Affects: libpyzy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libpyzy in Ubuntu. https://bugs.launchpad.net/bugs/1364789 Title: Cannot update or download programs because package libpyzy-1.0-0 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/pyzy/db/open-phrase.db' to '/usr/share/pyzy/db/open- phrase.db.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpyzy/+bug/1364789/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069531] Re: Cannot login to Empathy after setting up Google online account
Killing signonpluginprocess worked for me too. 13.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1069531 Title: Cannot login to Empathy after setting up Google online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1069531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290697] Re: Font rendering is broken
Aibara, you're correct in that my fix is not a perfect solution, but it prevents Gedit from being practically unusable in my opinion. Hopefully someone can find the exact cause and a solution to this problem soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1290697 Title: Font rendering is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290697] Re: Font rendering is broken
Changing 'rgb' to 'rgba' in xsettings fixed the issue in Gedit for me. However, setting to rgba makes other apps render text poorly. After screwing around for hours I did something that fixed that thought, but I'm not 100% sure what it was. I think it was a fontconfig file buried somewhere in my home dir. I removed all instances of fontconfig in my home folder. Lastly, I setup a fonts.conf file to clean up any text that still looked a bit off. With that said, here's a list of steps to try and resolve it 1. Remove (backup first) all instances of fontconfigs in your home directory (I think there was one in ~/.local/share/ ~/.config/) 2. Change rgb to rgba via dconf-editor org.gnome.settings-daemon.plugins.xsettings rgba-order 3. Download fonts.conf attachment and place in ~/.config/fontconfig/ 4. Reboot ** Attachment added: fonts.conf https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+attachment/4088467/+files/fonts.conf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1290697 Title: Font rendering is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290697] Re: Font rendering is broken
Here is a screenshot of the same problem in Synaptic ** Attachment added: Left side font rendered correctly, right side with scrollbar has font rendering problems https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+attachment/4088296/+files/synaptic.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1290697 Title: Font rendering is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1290697] Re: Font rendering is broken
I'm having this issue too. I'm a web developer and use Gedit on a daily basis so this is making life difficult. I did determine a few things though... It only occurs when there is a scrollbar present. When the document is short enough and doesn't require a scrollbar the font renders correctly. The same issue also happens in Synaptic. ** Attachment added: Left side font rendered correctly, right side with scrollbar has font rendering problems https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+attachment/4088295/+files/gedit.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1290697 Title: Font rendering is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1290697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1188393] Re: gimp fires asserts
I think the issue is that I've disabled the global (top of screen) menus in favor of in-window menus. I believe the removed packages are only appmenu-gtk and appmenu-gtk3. This is still a bug, though: either gimp requires those libraries (in which case apt / dpkg should notice) or, more reasonably, it should not (in which case the errors on stderr should not be emitted). I begin to suspect this may not be gimp-specific given the above. Jeff Abrahamson +33 6 24 40 01 57 +44 7920 594 255 http://jeff.purple.com/ http://blog.purple.com/jeff/ On Tue, Sep 17, 2013 at 10:44 AM, Thomas Hotz thomas.h...@gmail.com wrote: Thank you for this bug report. I can't reproduce this bug on Ubuntu 13.04. Am I correct that you upgrade from release to release? InstallationDate: Installed on 2010-03-13 (1181 days ago) InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 (20091028.4) I assume something went wrong here. Have you tried to do an sudo apt- get update sudo apt-get dist-upgrade (if you have not done it by yourself). I'm setting this bug to Incomple until I get a response from you. ** Changed in: gimp (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1188393 Title: gimp fires asserts Status in “gimp” package in Ubuntu: Incomplete Bug description: Gimp, invoked from the commandline with no arguments, fires this assertion hundreds of times. (gimp:10084): Gtk-WARNING **: Failed to load type module: (null) `menu_proxy_module_load': gimp: undefined symbol: menu_proxy_module_load When I do a gaussian blur, I see several like this: `menu_proxy_module_load': /usr/lib/gimp/2.0/plug-ins/blur-gauss: undefined symbol: menu_proxy_module_load (blur-gauss:10089): Gtk-WARNING **: Failed to load type module: (null) There is no evident malfunction of gimp except that a programmer from the past is telling me that something is not as he thought it ought to be. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gimp 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Thu Jun 6 21:40:49 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-03-13 (1181 days ago) InstallationMedia: Ubuntu-Netbook-Remix 9.10 Karmic Koala - Release i386 (20091028.4) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to raring on 2013-04-28 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1188393/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1188393 Title: gimp fires asserts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1188393/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
