[Bug 2019953] Re: plasma-discover crashes on exit

This hasn't happened in a long time, yes. (And I'm still on 22.04.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019953 Title: plasma-discover crashes on exit To manage notifications about this

[Bug 1964719] Re: GRUB shows up by default, even though GRUB_TIMEOUT=0

you probably can, but you won't be able to enter grub anymore, so I wouldn't recommend it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964719 Title: GRUB shows up by default, even though

[Bug 1968149] [NEW] grub ignores GRUB_TIMEOUT_STYLE when on efi+btrfs

Public bug reported: I'm using grub2, but with a configuration that may be a bit special: 1) I'm using native UEFI boot. 2) I have / formatted using btrfs (and no external /boot). 3) / is contained inside a LUKS volume with just grub on the ESP. (with GRUB_ENABLE_CRYPTODISK=y) Everything works

[Bug 1964719] Re: GRUB shows up by default, even though GRUB_TIMEOUT=0

If I take a look at /boot/grub/grub.cfg I see the lines: function recordfail { set recordfail=1 # GRUB lacks write support for btrfs, so recordfail support is disabled. } So, I guess this is intentional, at least. Are you booting via UEFI or BIOS? I could at least reduced the timeout by

[Bug 1878107] Re: flicker-free boot gets interrupted by GRUB menu

I have the same problem. I guess this relates to https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/425979? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878107 Title: flicker-free boot gets

[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)

Oh, sorry. I had 2.54.3+20.04.1ubuntu0.1 installed, the newer one seems to mostly work. I can log in and snap apps appear in the menu. XDG_DATA_DIRS now contains /var/lib/snapd/desktop twice, but that does not seem to be a major problem. -- You received this bug notification because you are a

[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)

The new snapd release 2.54.3+20.04.1ubuntu0.2 in focal makes this error message go away for me, but it completely broke my (Plasma) desktop session, because XDG_DATA_DIRS was not set before (making something fill it on start; don't know where that happens), but it now contains only

[Bug 1955137] Re: [SRU] 2.54

It would be really nice if someone could take a look at https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022 before this gets widely released to Focal. I guess this part in data/env/snapd.fish.in is the culprit: +# Expand $PATH to include the directory where snappy applications go. +set

[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1

I used the new version on Focal for about a day now and everything seems to work fine. I can see the new users that I haven't seen before and messages are received immediately. I didn't try chatting with any new user or creating a call though. Thanks! -- You received this bug notification

[Bug 1958022] [NEW] fish integration broken in focal

Public bug reported: After upgrading snapd from 2.51.1+20.04ubuntu2 to 2.54.2+20.04 I get the following stacktrace upon each start of the fish shell: /usr/share/fish/vendor_conf.d/snapd.fish (line 3): fish_add_path -aP $snap_bin_path ^ from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish

[Bug 1954902] [NEW] lpoptions cannot change system-wide default printer

Public bug reported: According to "man lpoptions": > When run by the root user, lpoptions gets and sets default options and > instances for all users in the /etc/cups/lpoptions file. Otherwise, > the per-user defaults are managed in the ~/.cups/lpoptions file. According to my

[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1

The messages in the popup in the app are getting more aggressive. Also, new messages are sometimes not received until I restart the application. Is there anything happening here or do I need to switch to a flatpak or snap or something? -- You received this bug notification because you are a

[Bug 1823299] Re: Package out of date

Telegram 2.1.7 in Focal is now also showing this popup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823299 Title: Package out of date To manage notifications about this bug go to:

[Bug 1946655] [NEW] tried to upgrade to new Ubuntu-Version

Public bug reported: I have a tuxedo-laptop running tuxedoOS with manually installed Gnome desktop. TuxedoOS is based on Ubuntu. I got a prompt from the Update Helper, if I want to upgrade my Ubuntu, so I said yes, then, it couldn't find some packages and stopped, asking me to fill out a bug

[Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Thanks for building the packages for focal. I can confirm that this fixes the problem for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on

[Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Thanks for the PPA! I currently don't have an impish system at hand, would it be possible to build it for focal as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read:

[Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Ok, I managed to reproduces this in a clean "ubuntu:latest" docker container. Steps to reproduce are below. During testing, I noticed that I aliased "ssh" to "ssh -K -X", and that "-K" (or equivalently "-o GSSAPIAuthentication=yes") is crucial. This changes the problematic SSH client command to

[Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Thanks Sergio for trying to reproduce this! I'm a bit puzzled, why the bug did not trigger in your case. I'll try to reproduce this in a clean VM as well now. One important thing might be that I tried to login as "root", for which I did not have a Kerberos-Ticket, so a "permission denied" would be

[Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Hello Athos, thanks for looking into this! This is reproducible without Ansible, that was just use-case that brought up the issue. I've further narrowed it down to the following setup: Server: /usr/sbin/sshd -d -p -f /dev/null -o GSSAPIKeyExchange=yes -o GSSAPIAuthentication=yes Client:

[Bug 1938144] [NEW] monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

Public bug reported: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH

[Bug 1923733] [NEW] unbound.service needs network online

Public bug reported: unbound.service in Ubuntu 20.04LTS Focal has insufficient dependencies for the ExecStartPre package-helper root_trust_anchor_update command to reliably succeed, while it depends on network.target that is no guarantee that network is available. While unbound startup succeeds,

[Bug 1918141] Re: nfs-server.service needs name resolution and network online

For nfs-server and the risk of applying the fix to stable releases, this is my take: It won't break anything unless you've done something truly esoteric, and then you're on your own anyway IMHO. It will enable nfs-server to consistently start in configurations using static addressing, which is

[Bug 1918141] Re: nfs-server.service needs name resolution and network online

For this I honestly see no risks of regressions for nfs-server. Also, be aware that on systems using DHCP depending on network.target or network-online.target has the same effect simply due to the inherent ordering of DHCP packets not passing through until the interface is able to pass traffic.

[Bug 1918141] Re: nfs-server.service needs name resolution and network online

OK, getting the network delay got a little bit convoluted as you can't clear dependencies with overrides but instead have to copy the unit file and edit it. I'm no systemd expert so this can probably be improved, but on a focal VM host of ours (KVM/Ganeti) that uses systemd-networkd I needed to

[Bug 1918141] Re: nfs-server.service needs name resolution and network online

First off, nfs-server starts but doesn't export the unresolvable hosts. The failures do show in systemctl status nfs-server. To reproduce in a VM you'll likely need something that causes network.target to be fulfilled but actual network traffic to not be forwarded until a few seconds later when

[Bug 1918141] Re: nfs-server.service needs name resolution and network online

I should note that we have observed this on both 18.04LTS (bionic) and 20.04LTS (focal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and

[Bug 1918141] [NEW] nfs-server.service needs name resolution and network online

Public bug reported: nfs-server.service has insufficient dependencies to start correctly in a setting where the nfs exports list contains DNS host names (not in local hosts file) or netgroups served via network (for example sssd). Typical failures listed by systemctl status nfs-server.service

[Bug 1913878] [NEW] dependency on gir1.2-poppler-0.18 missing

Public bug reported: I installed pympress and it failed to start with the following exception: Traceback (most recent call last): File "/usr/bin/pympress", line 11, in load_entry_point('pympress==1.5.1', 'gui_scripts', 'pympress')() File

[Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

apport information ** Tags added: apport-collected ** Description changed: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using

[Bug 1912673] [NEW] sounds not working on Dell XPS 17 (9700)

Public bug reported: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade,

[Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg

Also affects my Lenovo Thinkpad T480s Notebook -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg To manage notifications about this

[Bug 1894045] Re: modpython support missing from Ganglia

This indeed has to be a packaging bug. The last changelog entry says "Build using python2" but there is no dependency of anything python in the ganglia-monitor package: Depends: libapr1 (>= 1.2.7), libc6 (>= 2.14), libconfuse2 (>= 3.2.1~), libganglia1 (= 3.6.0-7ubuntu4), libpcre3, zlib1g (>=

[Bug 1880393] Re: tootle crashes on start after logging in

Is there a chance to get this backported to focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880393 Title: tootle crashes on start after logging in To manage notifications about this bug go

[Bug 1899286] [NEW] package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 failed to install/upgrade: »installiertes nvidia-kernel-common-450-Skript des Paketes post-installation«-Unterprozess gab d

Public bug reported: Occured after apt update && apt upgrade. System has zfs root partition. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64

[Bug 1887432] Re: configuration file //.config/debconf-kde-helperrc not writable

the following: DEBCONF_DB_OVERRIDE=Pipe{infd:none outfd:none} DISPLAY=:0 DEBIAN_FRONTEND=kde QT_LOGGING_RULES=org.kde.debconf.debug=false PWD=/home/niklas DEBCONF_DB_REPLACE=configdb I'm a bit confused on how this came to be as DebconfProxy._get_debconf_env copies os.environ first. But I couldn't

[Bug 1887432] [NEW] configuration file //.config/debconf-kde-helperrc not writable

Public bug reported: I'm using "aptdcon --refresh" and "aptdcon --full-upgrade" to update my system. I'm getting the following informational message on every upgrade (twice on start and twice on end): debconf-kde-helper - KDialog Configuration file "//.config/debconf-kde-helperrc" not writable.

[Bug 1879150] Re: apport-kde shows 'text' instead of text in message box

** Patch added: "apport-kde.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+attachment/5372882/+files/apport-kde.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879150

[Bug 1879150] [NEW] apport-kde shows 'text' instead of text in message box

Public bug reported: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed:

[Bug 1878695] Re: filelight crashes when switching from root to home

*** This bug is a duplicate of bug 1758629 *** https://bugs.launchpad.net/bugs/1758629 I can't look at bug #1758629 as it is private. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878695 Title:

[Bug 73244] Re: Crash when closing firefox after "open with" and having still opened the file

It was gdebi-gtk, but apparently they fixed the crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/73244 Title: Crash when closing firefox after "open with" and having still opened the file To

[Bug 1665822] Re: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()

(um, I'm on 18.04.4 amd64) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665822 Title: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn() To manage notifications about this bug go to:

[Bug 1665822] Re: fish crashed with SIGSEGV in __GI__IO_wfile_xsputn()

I think I'm affected by the same bug. The weird thing is: I think I only get this when starting Atom but I'm not sure. It sure doesn't crash one of the shells I'm actively using. I just get the "an application on your system has crashed" dialog. $ locale LANG=de_DE.UTF-8 LANGUAGE=

[Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

I think this is really a bug in packagekit. On 18.04 I can also trigger this by just running pkcon get-distro-upgrades in a terminal: Transaction:Getting upgrades Status: Waiting in queue Status: Starting Status: Finished Results: Fatal error: Spawn of helper

[Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

** Patch added: "patch removing pk_backend_get_distro_upgrades and disabling the feature" https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1709699/+attachment/5360831/+files/remove-get-distro-upgrades.patch -- You received this bug notification because you are a member of Ubuntu

[Bug 1869576] [NEW] partition screen shows wrong size below bar

Public bug reported: I was installing Kubuntu 20.04 to an empty (virtual) hard disk. It had the size of about 20GB (as you can see in the drop-down), but the preview show the new system as "1.0 B" which is a bit small. (The installation worked as expected, so that's not a big issue for me.)

[Bug 1869438] [NEW] systemsettings crashes when opening regional settings

Public bug reported: Opening the main regional settings page makes systemsettings crash. The timezone page, the spellcheck page and the formats page work, but the language one does not. user@user-VirtualBox:~$ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:

[Bug 1867949] [NEW] It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions

Public bug reported: The kernel.pid_max sysctl defaults to 32768. This is a very historic limit to provide compatibility with ancient binaries. Moving on to the year 2020 multicore CPU:s for desktops, laptops and servers is the standard, and together with PID randomization wraparound happens

[Bug 73244] Re: Crash when closing firefox after "open with" and having still opened the file

Sorry, missed your last comment. Yes, I can still reproduce this using Firefox 74.0 and Ubuntu 19.10. > Comment https://bugzilla.mozilla.org/show_bug.cgi?id=437767#c7 > by reporter suggests fixed some time ago Sorry my English wasn't clear on that one: I meant "should" in that it ought to be

[Bug 1565950] Re: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled

I just ran into this bug on bionic with a pretty custom configuration. Is there any chance that this can be backported? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565950 Title: Grub 2 fails to

[Bug 1851380] Re: root can lift kernel lockdown

Yes, there are solutions to this that don't expose the whole kernel to root. * This project's kernel module could use DKMS. This could make use of the MOK workflow already present in Ubuntu. * This project's kernel module could be included in the upstream kernel. The last option would be more

[Bug 1851380] Re: root can lift kernel lockdown

So, um, is there a simple way to get this fix into the other affected distributions or do I have to open an issue in each one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851380 Title: root can

[Bug 1769848] Re: wodim no longer works from non-root accounts

Comment #3 suggested to set CDR_FIFOSIZE=6m in /etc/wodim.conf. This did work for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769848 Title: wodim no longer works from non-root accounts To

[Bug 1851380] Re: root can lift kernel lockdown

I can confirm that this bug is fixed in bionic: # echo "x" > /proc/sysrq-trigger Nov 14 20:38:58 panzersperre kernel: sysrq: SysRq : Nov 14 20:38:58 panzersperre kernel: This sysrq operation is disabled from userspace. I don't have a disco or eoan to test. ** Tags removed:

[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot

It also interesting how this bug has been triaged and assigned an importance of "High", yet absolutely nothing has happened for over four years. How come, @cyphermox? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot

@vorlon Please explain how the user is supposed to know which of these network/netboot/whatever installers is supported and which is not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429030 Title:

[Bug 1851380] Re: root can lift kernel lockdown

I'm no expert in either kernel or C programming and I didn't test this patch, but it looks good to me. Also, the resulting code is quite similar to the one Fedora is currently using - they accidentally fixed this bug in

[Bug 1844666] Re: [SRU] [bionic] new upstream microrelease flatpak 1.0.9

For me this message mentions multiple supported versions: flatpak (1.4.2;1.2.5;1.0.9;) So updating from 1.0.8 to 1.0.9 would be enough to be able to update org.freedesktop.Platform.openh264. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

Re: [Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot

> The netboot installer is not the same thing as the mini.iso. The download > page refers to "Network installer". Nowhere does it reference the > mini.iso, > which is clearly not being booted over the network. > Sorry, that was a typo, I meant the network installer. Easy mistake to make since

[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot

> The mini iso is an artifact of the debian-installer package build and is not a supported installer that we reference anywhere on . Now that is some interesting news, and untrue. The netboot installer is referenced in the drop-down menu

[Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

To be clear, my issue was on the 3.13 kernel line, which is supported. Not that it matters for me anymore because I've since upgraded to 18.04 for which doesn't have this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot

This bug caused me a significant amount of time before figuring out how to fix it manually. It should be trivial to fix this on the ISO as well. HOW, AFTER FOUR YEARS, IS THIS NOT FIXED YET??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1621803] Re: package python3-scipy 0.17.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

I encountered the same problem today, but with scipy 0.19.1-2ubuntu1 in Bionic. sudo apt install --reinstall python\*-decorator also solved this for me. @shirayann are you still working on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 682662] Re: pam-auth-update ignores debconf settings

...sorry ^^^ - %s/debconf-get-selections/debconf-set-selections/ of course :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/682662 Title: pam-auth-update ignores debconf settings To manage

[Bug 682662] Re: pam-auth-update ignores debconf settings

This VERY ugly hack works on Ubuntu 18.04... -- /usr/share/pam-config/mkhomedir - Default: yes Priority: 0 Session-Type: Additional Session: required pam_mkhomedir.so skel=/etc/skel umask=0027 apt-get install debconf-utils echo libpam-runtime

[Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

I would rather not have to deliberately bring my system to a broken state just to run apport-collect. Is there anything else I can do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818134 Title:

[Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

I have the same problem with the nvidia driver. Updated shim-signed + dkms installed a while ago, worked fine until kernel upgrade triggered dkms rebuild, then the nvidia driver failed to load, "modprobe: ERROR: could not insert 'nvidia': Package not installed". Uninstalling shim- signed,

[Bug 1818501] Re: kernel BUG at fs/ocfs2/alloc.c:1514

Unfortunately we don't have a dedicated test system here, and I don't really want to test this on the production system... I can confirm that upgrading to the HWE kernel (4.18, which contains the patches) seems to solve the problem. -- You received this bug notification because you are a member

[Bug 1818501] Re: kernel BUG at fs/ocfs2/alloc.c:1514

It should be 63de8bd9328bf2a778fc277503da163ae3defa3c ocfs2: make metadata estimation accurate and clear 71a36944042b7d9dd71f6a5d1c5ea1c2353b5d42 ocfs2: try to reuse extent block in dealloc without meta_alloc -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1818501] Re: kernel BUG at fs/ocfs2/alloc.c:1514

Adding log with apport-collect files is not easily possible due to our security setup, but should not be necessary because all information can be found in the linked debian bug report. Here is our stacktrace of the bug happening: Mär 02 06:25:59 prometheus-lo kernel: [ cut here

[Bug 1818501] [NEW] kernel BUG at fs/ocfs2/alloc.c:1514

Public bug reported: The current bionic kernel (4.15) contains a known bug in the OCFS2 distributed filesystem, which can cause all nodes (!) of a redundant cluster to crash. More information on this bug (including the patch) can be found here:

[Bug 1732949] Re: Calendar functionality broken

It seems to work now (didn't notice since I started using the web interface). IN the meantime, I upgraded to ubuntu 18.10 and this is the version of libsoup that I am using now: Package: libsoup2.4-1 Version: 2.64.1-1 Priority: optional Section: libs Source: libsoup2.4 Origin: Ubuntu I can now

[Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Same Problem seems to occur on my T480s with Thinkpad Ultra Docking station and two external displays. After booting and login, all displays work, but after executing: # xrandr --output DP2-3 --rotate left Display DP2-3 does not display anything any more, even though xrandr claims it should:

[Bug 1732949] Re: Calendar functionality broken

I'm currently facing the same issue on Ubuntu 18.04 and evolution, using the "Online Accounts" eature and Office 365. Installed libsoup version: Package: libsoup2.4-1 Version: 2.62.1-1ubuntu0.1 Source: libsoup2.4 Origin: Ubuntu -- You received this bug notification because you are a member of

[Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

I have the same issue with the current Ubuntu 18.04 kernel 4.15.0-23-generic, and also with ubuntu mainline kernel 4.17.0-041700, using Intel Wireless 8260 (Firmware 34.0.1) in AP mode. Not sure if this is relevant or not: if i reboot the system, the wifi card vanishes completely (even from

[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

New upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/322 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/410636 Title: Right-click should not pre-light first option, too easy to accidentally

[Bug 1683761] Re: undefined symbol: tgetent

Yes, there's a workaround. You can install the package (with the same version) from Debian: https://packages.debian.org/stretch/libnative-platform-jni -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1762034] [NEW] Installer crashes at installing grub

Public bug reported: When i try to install Ubuntu 18.04 ISO via WubiEFI, the Installer crashes at creating the grub boot menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.4 [modified: bin/autopartition-loop bin/user-params] ProcVersionSignature: Ubuntu

[Bug 1745727] Re: Wifi stops working on Del XPS 9360

This has been somehow resolved. $ uname -a Linux laptop 4.15.1-041501-generic #201802031831 SMP Sat Feb 3 18:32:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Many thanks for the support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1748914] [NEW] librocksdb4.1 Invalid Instruction due to wrong compile flag

Public bug reported: According to the upstream GitHub rocksdb uses "-march=native" by default[0] so for portable binaries one has to use "PORTABLE=1 make …". For the librocksdb4.1 package in Ubuntu 16.04 this seems to not have been done. Consequently trying to use this package on an older Xeon

[Bug 1745727] Re: Wifi stops working on Del XPS 9360

I have now tried the 4.15.1 kernel a couple of days can say that the issue still remains, except that I do not get the pcie errors anymore. The good news is that I am pretty confident that this is a firmware issue and will try to upgrade the wifi firmware:

[Bug 1745727] [NEW] Wifi stops working on Del XPS 9360

13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niklas 3554 F pulseaudio CurrentDesktop: GNOME Date: Sat Jan 27 12:

[Bug 1740792] Re: Automatic login still requires user password after suspend/hibernate

To a normal user I'm pretty sure that it would be a UX issue, even though technically it's different between login and unlock, UX wise it isnt. If a user reboots or suspends the computer they wouldn't expect it to behave differently, a lot of people don't even understand the difference between a

[Bug 1743534] [NEW] package is outdated - current version is 0.8.9

Public bug reported: Hyde hasn't been updated it a while - the current upstream version is 0.8.9 since 2015 (see https://pypi.org/project/hyde/#history). Still, Ubuntu ships 0.8.5 for quite a while. It would be great if the package could be updated. ** Affects: hyde (Ubuntu) Importance:

[Bug 1740792] [NEW] Automatic login still requires user password after suspend/hibernate

Public bug reported: Description:Ubuntu 17.10 Release:17.10 gnome-control-center 3.26.2 When I set Ubuntu to automatically login a user the user still has to enter their password when resuming from a suspended session. The only option I can find to fix this is to disable the

[Bug 1738399] [NEW] Wrong package version

Public bug reported: Very minor bug, but it appears the package version number is inconsistent with the actual version number of the software, as evident by the following output. 6.5+svn4324-1 should be 6.6+svn4324-1. $ apt-cache policy smartmontools smartmontools: Installerad: 6.5+svn4324-1

[Bug 1737962] Re: Build failure: cp: cannot stat 'FAQ'

Problem with that is that backportpackage doesn't allow modifying the source before it's being built, so your suggestion doesn't work in my case. So I'll argue that this a bug in the debian/ubuntu packaging since FAQ is removed from upstream and debian/docs still reference it. Why don't you just

[Bug 1737962] [NEW] Build failure: cp: cannot stat 'FAQ'

Public bug reported: I'm trying to build the latest (bionic) package from source using backportpackage on trusty. This is my command line: backportpackage --workdir . --build --dont-sign --source bionic tmux This build fails with the following messages in the end: ... make[1]: Leaving

[Bug 1689299] Re: ssh-agent systemd user service failed to start, trying to set environment in Upstart way.

I don't get why this fix isn't backported to zesty yet since it's such a trivial fix. I spent hours troubleshooting this before finding the cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689299

[Bug 1716432] Re: With dash to dock enabled, title in window is not centred aligned to clock when the window is maximised

You missed a fourth solution: Move the clock to the right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716432 Title: With dash to dock enabled, title in window is not centred aligned to clock

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

I've just experienced this bug on Zesty with duplicity 0.7.06-2ubuntu3. I was doing a full backup when the underlying filesystem disappeared (partly my fault). I remounted it and trying to resume the backup, but duplicity won't start with Traceback (most recent call last): File

[Bug 1389682] Re: man command failed with exit status 3

This bug affects me: $ man man man: command exited with status 3: /usr/lib/man-db/zsoelim | /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | nroff -mandoc -rLL=225n -rLT=225n -Tutf8 $ I think its because I uninstalled all manpages before to save disk

[Bug 918019] Re: Firefox does not use default application to open binary files

I think this is the upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1166691 ** Bug watch added: Mozilla Bugzilla #1166691 https://bugzilla.mozilla.org/show_bug.cgi?id=1166691 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1464064] Re: Ubuntu apt repos are not available via HTTPS

*** This bug is a duplicate of bug 1186793 *** https://bugs.launchpad.net/bugs/1186793 Is this really a duplicate? The other bug is about the update process using HTTP. This bug is about the mirrors not supporting HTTPS. -- You received this bug notification because you are a member of

[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

This is relatively hard to reproduce. It happens sometimes directly after boot and login, sometimes after more than a week uptime. I've simply selected an older kernel at boot (4.8.0-46-generic; the newest one I had installed from Yakkety) and I didn't experience a crash, yet. -- You received

[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

I'm experiencing the same issue for a while now. I think it occurred after I upgraded form Yakkety to Zesty. I'm currently on 4.10.0-21-generic. I think the issue is more likely to happen when I run CPU and / or RAM intensive applications. If this happens, all my screens are stuck. **

[Bug 1683761] Re: undefined symbol: tgetent

It is still weird that this problem doesn't appear with the Debian package. They are both the same version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent

[Bug 1686614] Re: MOTD tross upgrade flag on newer systems

** Package changed: sysvinit (Ubuntu) => update-motd (Ubuntu) ** Summary changed: - MOTD tross upgrade flag on newer systems + MOTD throws upgrade flag on newer systems ** Description changed: Hey, There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 -> - 16.10 -> 17.04.

[Bug 1686614] [NEW] MOTD tross upgrade flag on newer systems

Public bug reported: Hey, There is an error in MOTD on Ubuntu 17.04 after upgrade from 16.04 -> 16.10 -> 17.04. Which tross updateflag from 12.04. This error shows on startup of every ssh session. Last login: to. april 27 01:19:42 CEST 2017 from 2a02::f:fff:AA:BB::be41 on pts/2 Welcome to

[Bug 1683761] Re: undefined symbol: tgetent

I've ran into the same issue. After reading https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322/comments/8, I installed the package from Debian: https://packages.debian.org/sid /libnative-platform-jni. This works only partially. It fails with a different error message: FAILURE: Build

[Bug 1659586] Re: NVIDIA CVE-2016-8826 and CVE-2017-0318

** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Yakkety) ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Xenial) ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Trusty) ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu Precise) -- You received this bug

  1   2   3   4   5   6   7   8   9   10   >