[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
Discovered this upstream bug report: https://gitlab.gnome.org/GNOME/gdm/-/issues/714 Allegedly the problem affects fonts that don't provide the oddball ratio character GNOME insists on using for the clock colon, including the default Ubuntu font. This can also cause the colon to render incorrectly depending on which fonts are installed on the system and what the GNOME interface font is set to. I'm going to try the Cantarell font (the upstream GNOME default font, I think) and see if it resolves the issue. ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #714 https://gitlab.gnome.org/GNOME/gdm/-/issues/714 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
I've been seeing it too in 20.04 (Focal), using NVIDIA binary drives and Xorg. I usually see it on the top bar (has happened several times over the past couple of days) but I've also seen it at least once on the lock screen. It seems that moving the mouse pointer over the time corrects it temporarily until the glitch next happens. I could run an apport-collect command on this bug if anybody is still interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1882291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925682] [NEW] “Test disk” option fails with kernel panic due to insufficient QEMU RAM allocation
Public bug reported: I used usb-creator-gtk to write “ubuntu-20.04.2.0-desktop-amd64.iso” from releases.ubuntu.com to a 4 GB USB stick, upon which I was given the option to test the disk. The ISO file is uncorrupted and matches the SHA256sum given on the site. When I attempted the test, the virtualized system failed to boot, apparently because the VM was given only 512 MB of RAM which is insufficient to start Ubuntu. The main error was as follows: Initramfs unpacking failed: write error Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. [...] Full output can be seen in the QEMU screenshot I attach. I found that usb-creator-gtk launched QEMU as follows: qemu-system-x86_64 -enable-kvm -m 512 -hda /dev/sde I could reproduce the failure by launching this command in the host manually with the USB stick still connected. If I used the following command instead, the VM booted the Ubuntu ISO successfully: qemu-system-x86_64 -enable-kvm -m 2048 -hda /dev/sde Thus the problem seems to be that usb-creator does not launch QEMU with an appropriate -m option. Steps to reproduce: 1. Download the Ubuntu ISO ubuntu-20.04.2.0-desktop-amd64.iso 2. Use usb-creator-gtk to write the file to the USB device 3. When prompted, click Test Disk Result: The guest kernel panic shown in the attached screenshot Expected: A successful boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: usb-creator-gtk 0.3.7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 22 15:03:51 2021 ExecutablePath: /usr/bin/usb-creator-gtk InstallationDate: Installed on 2021-03-18 (35 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterpreterPath: /usr/bin/python3.8 ProcEnviron: LC_TIME=root.UTF-8 PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: usb-creator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Kernel panic in QEMU guest" https://bugs.launchpad.net/bugs/1925682/+attachment/5491109/+files/Screenshot%20from%202021-04-22%2014-53-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925682 Title: “Test disk” option fails with kernel panic due to insufficient QEMU RAM allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1925682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821364] Re: xfce4 install on Ubuntu 18.04 has no polkit agent
I hit this upon manually installing Xfce4 after a fresh Ubuntu 20.04 installation. And even though Thunar has a Recommends for policykit-1-gnome, it nonetheless was not installed when Thunar was installed for some reason, and I had to install it manually anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821364 Title: xfce4 install on Ubuntu 18.04 has no polkit agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1821364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745259] Re: light-locker crashed with signal 5
It appears what's going on (in my observed case, at least) is that the xfce4 package depends on xfce4-session, which pulls in light-locker as a Recommends, which in turn pulls in lightdm as a dependency. And when Xfce searches for a screen locker to use, it seems to discover light- locker first and tries to use it, which fails if lightdm is not in use. light-locker then signals the SIGTRAP “crash” (from the light-locker source code, this appears to be an intentional as a means of signaling that an error occurred). So, the workaround appears to be either to use lightdm as the display manager instead, or to manually configure Xfce to use a different screen locker, or to manually remove the light-locker package and install, for instance, xfce4-screensaver (which is not installed by default from the xfce4 or xfce4-goodies metapackages) so that Xfce finds and uses it instead. Then, upon restarting Xfce, screen locking appears to work properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745259 Title: light-locker crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1745259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745259] Re: light-locker crashed with signal 5
After installing the xfce4 packages in Ubuntu 20.04 and starting a xfce4 session from the default bootup login screen, I immediately get a similar crash notification. If I launch light-locker from a terminal, I get the following output: $ light-locker ** (light-locker:26216): ERROR **: 19:33:17.519: Environment variable XDG_SESSION_PATH not set. Is LightDM running? zsh: trace trap (core dumped) light-locker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745259 Title: light-locker crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1745259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
I disagree with closing this as “WORKSFORME”. Just because core Firefox plastered over the problem does not mean it's not an issue for other cases. I have at least one Firefox add-on that continues to display unreadable text because this bug causes the CSS InfoBackground and InfoText values in styles to result in white-on-white text colors. It will even affect websites that happen to style themselves in these colors (example demo: https://artific.com/library/css-2-system- colors.html). Who knows what other software might also be affected. I have just tried the patch posted here and can confirm that the issues I describe are definitely caused by this bug. The themes are clearly broken and should be fixed. An explicit background *and* foreground color should always be specified. There is no guarantee the background image/effect will be used by a given application, and relying on it is only asking for random usability problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478173 Title: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816768] Re: nvidia module fails to build
I'm seeing the same sort of compilation errors for the VirtualBox modules also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816768 Title: nvidia module fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816768] Re: nvidia module fails to build
I get the same with Nvidia, as well as the VirtualBox modules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816768 Title: nvidia module fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1816768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I just discovered this the hard way. I happened to have speedtest.net opened in an unfocused Chromium tab on an inactive workspace and spent quite a bit of time going through a wild goose chase trying to figure out why my previously reliable DPMS/screen-locking setup suddenly flat- out refused to work at all. This was just running in the i3 window manager; no Gnome or KDE, nothing fancy. Closing the tab involved, or Chromium altogether, makes it work again. The closest upstream bug I could find is https://bugs.chromium.org/p/chromium/issues/detail?id=654659 , but it appears to have been basically ignored by the developers. It seems that Chromium has issues with inhibiting power management too aggressively. So aggressively I'd almost call it abusive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522675] Re: Warning messages about unsandboxed downloads
The command is lowercase “chown”, without the “(1)”. The general syntax would be “chown ”. You'll normally need superuser privileges to change owners on system files and directories, activated by adding the command “sudo” before the “chown” (separated by a space). The “(1)” refers to which section in the manual pages, or “manpages”, the command is described in. A common way to get help on a command is to run “man ”; for instance, you can execute “man chown” to get the manpage on the chown command. (To exit, type the letter q; more info here: https://help.ubuntu.com/community/man) The manual pages are divided into numbered sections by categories. Occasionally, there is more than one manpage with the same name, and the section number has to be included in the “man” command to indicate which is desired (for instance, “man 1 printf” gives the page on the shell command “printf”, but “man 3 printf” gives the page on the “printf” library call for C programming). You can get a manpage on “man” itself with “man man” (or just read it online here: http://manpages.ubuntu.com/manpages/xenial/man1/man.1.html). Under “DESCRIPTION”, there's a list of the manpage sections and their numbers, if you're curious. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522675] Re: Warning messages about unsandboxed downloads
^ Setting the owner of the /var/lib/update-notifier/package-data- downloads/partial directory to “_apt” on my 16.04 box is what I did to get rid of the error. I believe I've occasionally run into a few similar messages about other APT “partial” directories scattered around in /var, too; in those cases, the solution was the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
I also haven't personally encountered any further OOM issues on my home desktop (used daily) with 4.4.0.63. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607535] Re: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts
Thanks for providing information on working around the Content-Range errors here. The daily cron spam and inability to properly install the affected packages was getting annoying, and the solution is not particularly obvious to a casual user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607535 Title: ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
I thought it might be helpful to anyone still having this problem (where the fix hasn't been backported yet) to mention that the workaround is described in Bug #1607535 (essentially, delete the affected partial download files in /var/lib/update-notifier/package-data- downloads/partial/ and then try reinstalling again). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657567 Title: "Content-Range: */" on non-416 responses considered invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Don't forget that the earlier kernels are affected by Bug #1647400, which does something even worse (hang the system). I've verified that it affected my particular system before 4.4.0-59, and it may explain a couple of lockups I had previously experienced during normal operation when using previous kernels. -59 fixes the bug but introduces the permature OOM kill issue; if it weren't for the kernels currently in proposed (assuming they indeed fix this bug), I wouldn't really have a reliable kernel at all to use. With the 4.4.0-59 kernel, I got hit with two unexplained OOM kills, each occurring within about 3 days of uptime. I then tested the -62 kernel in proposed for just under 14 days and didn't see any OOM kills, and I've now been testing -63 for a couple of days and haven't any issues yet. However, it might help if anyone has an idea how the OOM kill bug might be reliably reproduced. “5 working days” isn't very long to reliably be sure the problem is solved otherwise; it took more than half that time upon upgrading to -59 for me to hit the bug by chance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654392] Re: growisofs -speed parameter has no effect
Thanks for the response and sorry for the delay! I actually don't burn optical discs very often anymore and needed to wait for another opportunity to arise (my discs are DVD+R which don't work with simulated writing, and I didn't want to waste them in order to test). With -speed=1, growisofs still writes at maximum speed (16x). However, with xorrecord, the speed control works fine. Thanks for suggesting those tools; my GNU/Linux burning knowledge has been out of date for a while and I lost track of all the forks. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654392 Title: growisofs -speed parameter has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1654392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730159] Re: ffmpeg library configuration mismatch
I get this, too. It *seems* to work fine anyway, but it sure looks scary. And ffmpeg is already a ridiculously verbose program as it is *without* spewing a full-page of incomprehensible gobbledegook on every single invocation. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730159 Title: ffmpeg library configuration mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg-extra/+bug/730159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot
I got hit by this too a while back. I don't expect a simple system upgrade to break my system. I ended up having to continue using an out- of-date kernel for some time as a result. It's still not fixed with nvidia-367 and 4.4.0-59-generic. But manually editing /etc/default/grub and removing "splash" from the GRUB_CMDLINE_LINUX_DEFAULT options, followed by executing update-grub2, does allow my system to boot with 4.4.0-59 (I didn't have to use "nomodeset"). I consider myself lucky. If this really affects *everyone* who simply uses the official Nvidia drivers, then I'm tempted to feel that these updates are not being tested adequately before release. I really hope that this testing will improve once this gets fixed, because things like this encourage users to leave their systems out of date and possibly risk security issues just to ensure that they at least *work*. It certainly doesn't encourage *me* to update my system very often (and I'm bad enough about that as it is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638990 Title: nvidia-367 with kernel 4.4.0-45-generic won't boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654392] [NEW] growisofs -speed parameter has no effect
Public bug reported: growisofs apparently ignores the -speed parameter when burning a DVD ISO regardless of the given value or the supported writing speeds. ——— $ dvd+rw-mediainfo /dev/dvd INQUIRY:[HP ][DVD Writer 1270d][GH24] GET [CURRENT] CONFIGURATION: Mounted Media: 1Bh, DVD+R Media ID: MBIPG101/R05 Current Write Speed: 16.0x1385=22160KB/s Write Speed #0:16.0x1385=22160KB/s Write Speed #1:12.0x1385=16620KB/s Write Speed #2:8.0x1385=11080KB/s Write Speed #3:6.0x1385=8310KB/s Speed Descriptor#0:00/2295103 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty "Next" Track: 1 Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB ROM Compatibility LBA: 270336 READ CAPACITY: 0*2048=0 $ growisofs -speed 12 -dvd-compat -Z /dev/dvd=dvd1.iso Executing 'builtin_dd if=dvd1.iso of=/dev/dvd obs=32k seek=0' /dev/dvd: "Current Write Speed" is 16.4x1352KBps. 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% 0/4621449216 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0% […] 4328620032/4621449216 (93.7%) @15.6x, remaining 0:20 RBU 100.0% UBU 99.3% 4393402368/4621449216 (95.1%) @14.0x, remaining 0:16 RBU 100.0% UBU 99.3% 4466507776/4621449216 (96.6%) @15.8x, remaining 0:10 RBU 100.0% UBU 99.0% 4527161344/4621449216 (98.0%) @13.1x, remaining 0:06 RBU 100.0% UBU 15.4% 4601151488/4621449216 (99.6%) @16.0x, remaining 0:01 RBU 60.5% UBU 99.0% builtin_dd: 2256576*2KB out @ average 10.4x1352KBps /dev/dvd: flushing cache /dev/dvd: closing track /dev/dvd: closing disc /dev/dvd: reloading tray ——— Same result with -speed=8 or -speed 8: Instead of using the specified speed (listed as supported by dvd+rw-mediainfo), it uses 16x instead. With the same media and drive, setting speed *does* when using wodim (e.g., `wodim -v -dao speed=8 dvd1.iso` does write at 8x), so it isn't simply a drive/media issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: growisofs 7.1-11 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jan 5 14:31:16 2017 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.4 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu4 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.4 InstallationDate: Installed on 2016-04-11 (268 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: dvd+rw-tools UpgradeStatus: Upgraded to xenial on 2016-04-26 (254 days ago) ** Affects: dvd+rw-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654392 Title: growisofs -speed parameter has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/1654392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614419] [NEW] Examples section in manpage is illegible due to bad formatting
Public bug reported: As can be seen on http://manpages.ubuntu.com/manpages/xenial/man1/udevil.1.html , there's a problem with the formatting under the EXAMPLES section. Instead of each example being on a separate line, the entire block is jumbled together into a paragraph-sized mess. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udevil 0.4.4-1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: i3 Date: Thu Aug 18 03:07:39 2016 InstallationDate: Installed on 2016-04-11 (128 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: udevil UpgradeStatus: Upgraded to xenial on 2016-04-26 (113 days ago) ** Affects: udevil (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614419 Title: Examples section in manpage is illegible due to bad formatting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udevil/+bug/1614419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605101] [NEW] Writer: Up and down keys move cursor to random line positions instead of directly up or down
Public bug reported: Immediately after writing some text in Writer, using the up and down keyboard keys to move the text cursor results in the cursor moving to unpredictable horizontal positions on the adjacent line (or in rare cases, even *several* lines away) instead of in the expected position, directly above or below. I tried it with a new user and fresh ~/.config/libreoffice profile, running in Unity, and could still reproduce the problem. 1. Open LibreOffice and start a new Writer document. 2. Type several lines of text uninterrupted and then, without ending the paragraph, attempt to move the cursor one line up with the keyboard 3. Contrast resulting cursor behavior to that of virtually every other word processor and text editor (it usually ends up anywhere except directly one line up or down, often appearing at the very end or beginning of the line or somewhere entirely different instead). 4. Repeatedly pressing up or down immediately after this may make the inconsistent movement more obvious (it starts to behave normally, and then after more text is typed it jumps around incorrectly again with up/down movement). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Jul 21 02:07:30 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-04-11 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-04-26 (85 days ago) XsessionErrors: (process:5806): indicator-sound-WARNING **: volume-control-pulse.vala:744: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory (gnome-software:5821): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered (gnome-software:5821): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered cinnamon-session[5571]: WARNING: t+24.67429s: Could not launch application 'telepathy-indicator.desktop': Unable to start application: Failed to execute child process "telepathy-indicator" (No such file or directory) (cinnamon:5773): Cjs-WARNING **: JS ERROR: TypeError: this.actor is null ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605101 Title: Writer: Up and down keys move cursor to random line positions instead of directly up or down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1605101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529647] Re: [SRU] Always backport newer versions to trusty-updates
My experience agrees. I've found it imperative to upgrade the script on a regular basis to ensure it keeps working. YouTube messes with stuff all the time, and it's rarely long before an outdated version breaks. I had to abandon using the official package and just maintain my own local copy (fortunately, ‘youtube-dl -U’ makes this pretty quick and painless). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529647 Title: [SRU] Always backport newer versions to trusty-updates To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1529647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 452313] Re: Unclutter causes text input cursor to blink in unfocused windows
It took me forever to track this problem to unclutter. It was driving me crazy (the cursor blinking gave me false cues as to which window was focused and regularly caused me to begin typing in unintended windows). Another solution might be to use a rewrite of unclutter that uses X's xfixes extensions rather than the sneaky hacks the original unclutter uses: https://github.com/Airblader/unclutter-xfixes I built and have been trying it for about a week and haven't encountered any more cursor blink weirdness. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/452313 Title: Unclutter causes text input cursor to blink in unfocused windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/452313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1231588] Re: Running unclutter without "-noevent" causes focus problems for Firefox and Thunderbird
I was being driven up the wall with this problem for a long time (even in a non-Ubuntu distro) and couldn't for the life of me figure out what was going on until someone mentioned Unclutter! (I was blaming the window manager, GUI toolkits, etc.--I never would have suspected unclutter.) It does indeed seem to cause problems. I sort of worry that -noevent could potentially cause other problems, though. Apparently unclutter uses a lot of funky hacks to do its work which causes weird things to happen in general. There's a rewrite of it using the x11-xfixes extension which looks like a much cleaner solution: https://github.com/Airblader/unclutter-xfixes I found it fairly easy to build, and so far I haven't seen any problems or weird behavior while using it. It would be nice if it could be considered for inclusion in the Ubuntu repos. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1231588 Title: Running unclutter without "-noevent" causes focus problems for Firefox and Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1231588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 435831] Re: unclutter shouldn't be enabled by default
I think I have to agree. I wasn't expecting it to be enabled for all users, and it took me a while to discover that it was getting launched twice and why (because I had already added it to my startup manually with the options I wanted). I can appreciate trying to make it easy for the average user to figure out how to use it given that it lacks a GUI, but auto-launching it globally forces it on users who might not want it and also gets in the way of users launching it with their own command-line options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/435831 Title: unclutter shouldn't be enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/435831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313732] Re: Impossible to report a bug about samba-tool without answering inadequate questions
I hit this today, and it absolutely infuriates me. Indeed, the questions have either no valid answers or ask things I could not possibly know. And I consider myself a reasonably experienced user. All I know is that I tried to apply security updates and it told me something happened. It withheld all the details until I gave up on the questions and cancelled, and the whole thing closed **without once giving me a single clue what the problem was**. I still have no idea what issue it was trying to report or whether Samba is now usable, etc. I really hate useless messages that say “an error occurred” with no details, but refusing to give any information at all while simultaneously demanding it from the user takes the cake. I am amazed to find something so user-hostile in a bug-reporting tool. This isn't a good way to get bug reports, and it probably isn't a very good way to encourage users *not* to simply give up and permanently disable the bug reporter *and* system updates altogether! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313732 Title: Impossible to report a bug about samba-tool without answering inadequate questions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1313732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237955] Re: update-manager should forewarn about reboot needed
Duplicate of #658169? I agree; I'm often don't find it obvious that any of the updates in the list will require a reboot, and it's annoying to install the updates only to have it tell me I need to reboot when I currently can't and having to continue running in an unstable/glitchy half-updated state as a result. It should indicate whether a reboot will be required beforehand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237955 Title: update-manager should forewarn about reboot needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1237955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470235] Re: PolicyKit high memory usage
This happened to me, too. I installed Multi-Core System Monitor for just a moment and noticed the steadily growing memory usage. Worse, removing the applet did not stop the leak. The leak didn't stop until the next system reboot (presumably restarting polkitd would have also worked, but I didn't try it since I wasn't sure how safe it was). But since there's no way to know if this was the trigger for the original bug report or earlier commenters, perhaps the MCSM case should be opened as a separate, specific bug against policykit? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574070] Re: Celestia or not Celestia
Same problem here. Yet they're apparently referenced and downloadable here: https://launchpad.net/ubuntu/xenial/+search?text=celestia and appear to work. Some kind of bug/glitch in the repos? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574070 Title: Celestia or not Celestia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/celestia/+bug/1574070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522675] Re: /root/.synaptic/ not created due to locking status
I just now found a very similar message from the update-notifier cronjob: /etc/cron.daily/update-notifier-common: Get:1 http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160407.1.orig.tar.gz [27.0 MB] Fetched 27.0 MB in 1min 11s (378 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160407.1.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160407.1.orig.tar.gz Installing from local file /var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20160407.1.orig.tar.gz Flash Plugin installed. So, apparently not unique to Synaptic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: /root/.synaptic/ not created due to locking status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522675] Re: /root/.synaptic/ not created
For the Synaptic message complaining about /var/cache/apt/archives/partial, setting the owner of that directory to _apt seems to avoid it, based on my tests in a VirtualBox VM of Wily upgraded to Xenial. I haven't (yet) encountered an error complaining about /root/.synaptic/[…]. It seems really bizarre that it would insist on some system user being able to access something in root's home directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: /root/.synaptic/ not created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446760] Re: sddm and lightdm can run at the same time
I believe I hit this today in 15.10 (testing in VirtualBox). I installed kbuntu-desktop, and it asked which display manager I wanted to use. I just wanted to use the existing one, which I assume was lightdm. So I selected lightdm, and it set up sddm anyway. On boot up, the login screen freaked out, constantly flickering between lightdm and sddm. Both responded to password input, and when I launched Cinnamon, there were two sessions loaded on the same screen at the same time, two panels, one desktop session obscuring the other in a “picture-in-picture” fashion. The mouse did not register properly, there was massive graphical distortion, the system was unusable, and it completely froze after a minute or two until I finally managed to disable one of the DMs. IMO, this is pretty severe. A non-technical user would be absolutely hopeless if this happened to them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446760 Title: sddm and lightdm can run at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1446760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539934] Re: Load thin Kernel Modules in initramfs for support on boot
I was able to use this hook to get Ubuntu 15.10 installed and running from a thin LVM volume in a VirtualBox VM. However, the lvm2-monitor service seems wonky if started from the initramfs, strange errors like: --tpool: event registration failed: 2561:11 libdevmapper-event-lvm2thin.so dlopen failed: /lib/x86_64-linux-gnu /device-mapper/libdevmapper-event-lvm2thin.so: cannot open shared object file: No such file or directory even though the library is both in the root fs and the initrd. Leaving dmeventd and its libraries out of the initramfs seems to allow it to function normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539934 Title: Load thin Kernel Modules in initramfs for support on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1539934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855473]
I think I'm still seeing the bug as described in Comment 29 on KDE 4.12.4 (Arch Linux). In my case, I navigate to a particular folder, navigate away to a higher directory or via the sidebar, come back, and extract an archive using the RMB menu—the newly created file(s)/dir(s) do not appear without a manual refresh. If I retest by restarting Dolphin and go directly to that dir and try again, it works fine. By navigating away and coming back, I reproduce it. Anyone else able to reproduce it this way? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855473 Title: File list not updated in dolphin To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/855473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549696] Re: missing textures for planets
Apparently affects 10.04 LTS also. It's pretty sad that I had to search the bug list just to figure out why half the textures were not working and verify that it wasn't a graphics driver/card issue. There is no excuse for deliberately breaking a package by hiding half of the files elsewhere, not add any dependencies, not include any notice in the description, and make trouble for the Celestia developers who get the blame for something that is not their fault. If Ubuntu could not use a reasonable licensing policy, then it would have made much more sense to put the entire Celestia package, UNBROKEN, into the non-free repo, or to give some kind of conspicuous notice when installing the package. I don't see how it's remotely reasonable for someone to take significant time away from other work fixing bugs and such in the distro to go over *every single file* in some random, relatively obscure package, and single out *individual* files not to include in the package, without any regard whatsoever for whether these files are important to the package, and without making it clear to the users installing the package that this was done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549696 Title: missing textures for planets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/celestia/+bug/549696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986492]
Created attachment 82817 ~/.kde4/share/config/plasma-desktop-appletsrc file that seems to trigger bug -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeplasma-addons in Ubuntu. https://bugs.launchpad.net/bugs/986492 Title: when amarok started no icon in SystemTray To manage notifications about this bug go to: https://bugs.launchpad.net/ir-plasma-widgets/+bug/986492/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 986492]
I just got bit by this. Non-KDE tray icons missing. Everything was fine after an update, then system crashed, I rebooted, then the tray was messed up. Removing and readding it didn't help. As mentioned above, removing plasma-desktop-appletsrc brought them back to normal. I'll attach my broken plasma-desktop-appletsrc in case someone wants to try to debug. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeplasma-addons in Ubuntu. https://bugs.launchpad.net/bugs/986492 Title: when amarok started no icon in SystemTray To manage notifications about this bug go to: https://bugs.launchpad.net/ir-plasma-widgets/+bug/986492/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 883459]
I still have the problem described in Comment 54 in KDE 4.9.3. Maildir, POP3. I have three messages that keep appearing in inbox every time I try to move, mark as read, or delete them. I also get a ton of “Maildir '' for collection '' is invalid” when I change folders. Anything I can do to try to figure out what's going on? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in Ubuntu. https://bugs.launchpad.net/bugs/883459 Title: KMail duplicates emails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/883459/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
