[Bug 2033939] Re: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is established
** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2033939 Title: RDP remote desktop connection stopped working using mstsc from windows 11. tcpdump on ubuntu shows SYN packet coming and RESET being responded but no connection is established To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2033939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057842] Re: FFe: freedp2 -> freerdp3 in main
gnome-remote-desktop-45 is not compatible with mutter-46. All you need to do is use a system with the NVIDIA driver, run g-r-d-45 with mutter-46 and you either run into a black screen, or you might see an initial frame but no updates (freezed screen). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057842 Title: FFe: freedp2 -> freerdp3 in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2057842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970994] Re: /usr/libexec/gnome-remote-desktop-daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3
To provide some context, when this crash can happen: It can happen, after attempting to start a remote desktop session, when the screen is locked. In such case, g-s directly refuses the start request and therefore the lifetime of the rdpgfx thread in FreeRDP is very short. The journal message for this looks like this: `Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited` Now, the error here is, that FreeRDP does not correctly wait for the rdpgfx thread to be created and this can lead to in this situation, that the rdpgfx thread is not teared down, when stopping the session, which can can lead to segfaults, like in this report or to memory corruption. Personally, I was not able to reproduce the error. However, with the help of the journal entries I was able to find this cause. https://github.com/FreeRDP/FreeRDP/pull/7836 takes care of the problem. Sessions, that are not locked, should not be affected by this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970994 Title: /usr/libexec/gnome-remote-desktop- daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1970994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
Note: 2.7.0 does **NOT** contain https://github.com/FreeRDP/FreeRDP/pull/7836 (which should fix https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970994), because 2.7.0 was released before that MR was created and merged. So you have to either apply https://github.com/FreeRDP/FreeRDP/pull/7836 manually on top of the 2.7.0 build or build from the stable-2.0 branch at a recent commit, depending on what is more convenient for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)
I don't think a package recommendation is the right thing here. Instead, the package containing fuse3 and fusermount3 should here be a package dependency of the gnome-remote-desktop package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970411 Title: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1970411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
As for the RDP connection problem, please provide enough information. If you have an updated system, then your FreeRDP build should contain the NTLM fixes. Jeremy afaik backported them to Ubuntu in https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1968577. Meanwhile, FreeRDP-2.7.0 was released, and distros should update to that version. If you have your system updated (and therefore should have the NTLM fixes), then the issue is either you provided the wrong credentials or an error in the client. Without providing the information, which client and which client settings are used, there is nothing, that can be said here. Please the follow the official help: https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html It contains a section about recommended clients and client settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
To be honest, the issue description is insufficient and the crash file useless. The stacktrace does not contain any debug symbols and for the "sometimes shows screen garbage before disconnecting" part, a screenshot would be needed, because the screen content is not just garbage. It has a pattern, and that is a wrong DRM format modifier. It may not be obvious for the user, but developers don't have a glass ball in front of them to see what happens on the other side of the screen, so a screenshot can be super helpful. I found similar stacktraces in Ubuntus error tracker. Problem with Ubuntus error tracker is that a lot stacktraces cannot be retrieved and therefore leave only a single line of calls, where only the library name is shown. And this is also here the case. However, the issue could be fixed upstream and is fixed in the current master branch of g-r-d, due to kind help of a person in https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96. Personally, I don't have an arm64 device, which is why this issue could never been detected. And without that help in form of testing patches and providing the stacktrace with debug symbols, the issue would still exist. The crash itself is kinda interesting, because it appears, that some instructions are completed in a different order on arm64. It was fixed in https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/bdc8d63bddf2ebb0da97e9277267b7398e49710e and https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/b7b0597ba59072b718a78760c2732e64e080b4bf. Then, to the part, what is here referred to as 'garbled content': A screenshot for this is provided here: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96#note_1435877 Without the screenshot, I wouldn't been able to have that modifier guess. So, please, for future reports provide screenshots for such things. The issue here is that g-r-d always expected explicit DRM format modifiers. However, it is an implicit modifier here. There is no such flag to indicate that and as a result the `DRM_FORMAT_MOD_INVALID` modifier is used to indicate an implicit modifier. It is a weird thing though: In a screencast, submitting this specific modifier means, that an implicit modifier is used, while graphics APIs use this to indicate an error. However, using `DRM_FORMAT_MOD_INVALID` as modifier was never a problem with other drivers, like Intel and so it was unnoticed. The issue was fixed in https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/60244e96333fbeabfee9c1a0e5ce56590dbb313d and https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/d9923317f0b60621f0aeb219f4d10612a2178e63. I'll ask Jonas to push another release tag (might be 42.1.1). 42.1 was pushed saturday, but does not contain these fixes. Personally, I see this issue as severe, but I am not one, who can push tags in g-r-d. So, I can only ask Jonas to push one. In any case, Ubuntu can also build g-r-d from the master branch until commit https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/d9923317f0b60621f0aeb219f4d10612a2178e63 to push the fix to Ubuntu here. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #96 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/96 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969619] Re: RDP Sharing appears on by default in jammy
While the fix here is correct, the assumptions in this issue are wrong. I wrote an explanation of this issue in https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/1970039/comments/7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970039] Re: cannot disable Remote Desktop in Ubuntu 22.04
Yeah, this issue here is a duplicate of the bug mentioned in comment 6. Jeremy
submitted a patch, which sufficiently fixed the issue in
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1286 (it
should technically check for other aspects too), but for now it is sufficient.
Follow-ups should use an upstream report or MR for this.
Just to note: What people confuses here is the state of what the switch
represents and therefore leads to the wrong conclusions above.
Just because g-r-d is running, does not mean it listens on some ports for
connections, nor that it starts any of the server backends (RDP or VNC).
Before Jeremys change, the state in g-c-c represented, whether the g-r-d
service is enabled and running. However, the backends have their own 'enabled'
settings (default: false ('off')). Also, the RDP backend won't be started by
g-r-d, when the server cert and private keyfile are missing.
These are generated, when the switch in g-c-c is switched to 'on'.
The reason, why this issue was not apparent initially was that due a recent
systemd change, g-r-d did not start automatically, when the service was enabled.
This was fixed in
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd380dffc108e5c7f77c81fbaa271ec7b,
but lead to this issue here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970039
Title:
cannot disable Remote Desktop in Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970039/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930297] Re: Clipboard sharing is disabled when using RDP backend
Marco, Jeremy, while this issue is fixed. You need to adjust the .deb pkg to depend on Fuse3. Currently, it is not done and therefore crashes for some people: https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f This was also reported in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=998846. ** Bug watch added: Debian Bug tracker #998846 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998846 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930297 Title: Clipboard sharing is disabled when using RDP backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1930297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why
This was fixed in https://bugs.launchpad.net/ubuntu/+source/gnome- control-center/+bug/1968518 ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966432] Re: audio crackling on usb sound card
I'm having similar issues on my Linux Mint 20.3. My onboard sound card (detected as USB Audio) is now broken. The sound coming out is just popping in and out and crackling. My Mainboard is the Z590 AORUS ULTRA. According to the spec sheet, this board used the "Realtek® ALC4080 codec", whatever that means. Hope this helps. I reverted back to 5.13.0-35 and my audio is working again. FYI SPDIF and 5.1 Surround also did never work with this sound chip / mainboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966432 Title: audio crackling on usb sound card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964976] Re: gnome-remote-desktop is not listening on port 5900, no sign of why
Me (upstream g-r-d) already predicted this, as soon as I saw that Ubuntu ships mixed versions (gnome-control-center-41 (g-c-c) for GNOME 42 (that's unsupported upstream and as seen here breaks things)). For GNOME 42, we finally switched over to the RDP backend in g-r-d. As a result the UI in g-c-c has been redesigned (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1205#note_1393775). To not also unintentionally listen on VNC in the background without the notice of the user, the gsettings were adjusted, so that each g-r-d backend has its internal switch (default: off). You can check that by checking both g-r-d's and g-c-c's version. Upstream we make sure that things won't break in the major version. This means that all components need to have the same major version (i.e. g-r-d-42 + g-c-c-42 + ...-42). Minor versions are just bugfix releases. Jeremy and Marco of the Ubuntu Desktop Team are already aware of this from our discussion on IRC. It's up to Ubuntu now to act. The remote desktop is not the only thing that breaks here downstream due to mixed versions. According to Marco, Ubuntus decision would either be to backport the g-r-d UI changes or adjust their g-c-c build to use VNC again. Some more info on the RDP backend in 42: https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/issues/26#note_1396166 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #26 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964976 Title: gnome-remote-desktop is not listening on port 5900, no sign of why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1964976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Good afternoon, This also effects the https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.iso image. Currently I can boot debian arm64 UEFI ISOs and Fedora, but not the Jammy cd image using PI uefi. Any idea when this fix will be incorporated on the ISO so can do further testing? Kind regards, Pascal van Dam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942691] Re: linux-modules remove rpi_poe_fan module after reboot
I will give a full example in thursday. The issue is still there. In proza: If I do not put the module in /etc/initramfs-tools/modules the module will not be there after a reboot (e.g. remove from the filesystem). And this is so for a lot of the other modules. I am booting from iSCSI and even the NFS modules are gone. As far as I know this wasn't the case in previous version. Behaviour has been detected in: 20.04, 21.04 and 21.10 Apologies for the delay Kind regards, Pascal ** Changed in: linux-raspi (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942691 Title: linux-modules remove rpi_poe_fan module after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761140] Re: [SRU] dpkg eror processing package nova-compute
** Also affects: nova (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761140 Title: [SRU] dpkg eror processing package nova-compute To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1761140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942691] [NEW] linux-modules remove rpi_poe_fan module after reboot
Public bug reported: When installing linux-modules-5.11.0-1016-raspi 5.11.0-1016.17 I do get the rpi_poe_fan module and can modprobe or insmod it. I can even find it under the relevant path in /lib/modules. After a reboot it appears that the module has been removed. Why? ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942691 Title: linux-modules remove rpi_poe_fan module after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934527] Re: Window switching with Alt-Tab stops working after a while
*** This bug is a duplicate of bug 1933996 *** https://bugs.launchpad.net/bugs/1933996 I believe that the bug is related to Wayland. It can be fixed by not using it as described here: https://askubuntu.com/questions/1349544/alttab-stops-working-after-a- while-in-ubuntu-21-04/1359821#1359821 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934527 Title: Window switching with Alt-Tab stops working after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940771] [NEW] Alt+Tab not working
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute The command "apt-cache policy pkgname" as you requested does not work.^^ Here, Alt+Tab is not working despite being configured. Switching windows directly would work, it's just the switch windows directly which doesn't. Somebody else has already described the exact bug on stackoverflow -- and I have *exactly* the same issue! https://askubuntu.com/questions/1349544/alttab-stops-working-after-a- while-in-ubuntu-21-04 Please fix this, that's very annoying... ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940771 Title: Alt+Tab not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1940771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892448] Re: ceph 15.2.3-0ubuntu0.20.04.2 collides with ceph-deploy 2.0.1-0ubuntu1
Hi, I'm not really following this bug report anymore, and I won't test this, but thanks for (most likely) fixing the issue. On a more general note, a question to Canonical: Why does a commercial distro even bother to have things like "-proposed" repos or a bug tracker if it takes 9-10 months to fix an issue *this* trivial in a supposedly supported package, in the most current supposedly supported distro release? And why should people even bother to write bug reports at all? Other people manage to conceive and give birth to a child during the timespan it takes Canonical to simply delete a file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892448 Title: ceph 15.2.3-0ubuntu0.20.04.2 collides with ceph-deploy 2.0.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1892448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
I used 5.8.0-50 and had the same bug, now I upgraded to 5.8.1-050801 and the bug disappeared -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924778] [NEW] Xorg buggy
Public bug reported: After boot and login the screen flashes and when i open i.e. Firefox i can see the desktop icons flashing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 17:28:13 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-02-21 (53 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20ARS20N00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d09e8852-af20-45ea-8147-e76491467e1b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.release: 2.54 dmi.bios.vendor: LENOVO dmi.bios.version: GJETA4WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARS20N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:br2.54:efr1.14:svnLENOVO:pn20ARS20N00:pvrThinkPadT440s:rvnLENOVO:rn20ARS20N00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARS20N00 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924778 Title: Xorg buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923305] [NEW] LibreOffice 6.4 OpenType Features unusable
Public bug reported: When using OpenType features (Format - Character - Feature) from a capable font like EB Garamond 12, LibreOffice automatically enables a fractional style, which essentially makes all numerics unusable, and there's no obvious way to disable this in the GUI once you've opened the Features dialog. There are two workaround, as all OpenType features get disabled when selecting another font, and back again. And, of course, one can remove :frac=1 manually from the font name field. This has however been fixed in LibreOffice 7.0 onward, but somehow wasn't cherrypicked into 6.4.x, even though the change seems trivial: https://github.com/LibreOffice/core/commit/d28c9d56df8a2629321bda116a6d2dcfa587d160 Please consider including this cherrypick in a future package for Ubuntu Focal. The patch won't apply directly due to a filename typo getting corrected, which needs to be uncorrected in the patch: vcl/source/font/OpenTypeFeatureDefinitionList.cxx vcl/source/font/OpenTypeFeatureDefinitonList.cxx ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923305 Title: LibreOffice 6.4 OpenType Features unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1923305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922436] [NEW] v38 of pixman causes segfault for some SVGs
Public bug reported: libpixman crashes for some SVGs with: python[XXX]: segfault at XX ip XX sp XX error 4 in libpixman-1.so.0.38.4[XXX] The problem (incl. reproducible example) is described here: https://github.com/Kozea/CairoSVG/issues/319 ** Affects: pixman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922436 Title: v38 of pixman causes segfault for some SVGs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1922436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION
I'm also experiencing this bug, with Win 10 and TB78.6.0 (32 bits). Many occurences of : BEGIN:VALARM ACTION:DISPLAY TRIGGER;VALUE=DURATION:-P2D DESCRIPTION:Description par défaut Mozilla X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame ter with an illegal type for property: VALUE=DURATION END:VALARM Some events disappear when I close, then reopen TB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907004] [NEW] upgrade to 20.04 from 18.04 error
Public bug reported: Impossible d'évaluer la mise à niveau Un problème insoluble est survenu lors du calcul de la mise à niveau. Cela a probablement été causé par : * des paquets logiciels non officiels qui ne proviennent pas d’Ubuntu. Veuillez utiliser la commande « ppa-purge » du paquet « ppa-purge » afin de supprimer les paquets d’un dépôt PPA Launchpad, puis essayez de relancer la mise à niveau. Si rien de tout cela ne s'applique, signalez ce bogue à l'aide de la commande « ubuntu-bug ubuntu-release-upgrader-core » dans un terminal. Si vous souhaitez analyser le problème par vous-même, les fichiers journaux contenus dans le répertoire « /var/log/dist-upgrade » contiennent les informations sur la mise à niveau. Plus précisément, veuillez consulter les journaux « main.log » et « apt.log ». ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 22:59:37 2020 InstallationDate: Installed on 2018-05-03 (948 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-06 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages ** Attachment added: "apt.log" https://bugs.launchpad.net/bugs/1907004/+attachment/5441514/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907004 Title: upgrade to 20.04 from 18.04 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1907004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1901368] Re: Still not possible to update to Ubuntu 20.04 from 18.04
*** This bug is a duplicate of bug 1898152 *** https://bugs.launchpad.net/bugs/1898152 Hi! Since I uninstalled gnuradio-dev I was able to install Ubuntu 20.04 LTS. Thank you very much! Pascal Note: this issue was concerning my bug messages # 1901368, # 1900287, # 1900286. Thank you! Le 20-11-02 à 16 h 34, Brian Murray a écrit : > *** This bug is a duplicate of bug 1898152 *** > > https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1898152data=04%7C01%7C%7C0fe39fcd367240fa37b408d87f77f5c4%7C84df9e7fe9f640afb435%7C1%7C0%7C637399500479994744%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=tbrZIcTIKZxtUvOYSsJ5gghnIWV51kH21I3gw%2BDSY1E%3Dreserved=0 > > ** This bug has been marked a duplicate of bug 1898152 > upgrade fails to calculate if gnuradio-dev is installed > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901368 Title: Still not possible to update to Ubuntu 20.04 from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901368] [NEW] Still not possible to update to Ubuntu 20.04 from 18.04
Public bug reported: Not possible to calculate for the upgrade. Not sure what is still giving this problem. Thank you! Details: Description:Ubuntu 18.04.5 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 22:20:56 2020 InstallationDate: Installed on 2015-06-19 (1954 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-25 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901368 Title: Still not possible to update to Ubuntu 20.04 from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900287] [NEW] Can't upgrade to Ubuntu 20.04 LTS
Public bug reported: I just wrote here a few minutes ago about this problem but now I do the report again after unchecking all other software sources PPA and rebooting the computer and still not able to upgrade from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. Thank you for improving Ubuntu for a better experience soon! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 17:17:07 2020 InstallationDate: Installed on 2015-06-19 (1947 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-17 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900287 Title: Can't upgrade to Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900286] [NEW] Can't upgrade to Ubuntu 20.04 LTS
Public bug reported: I can't upgrade from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS I even tried to uncheck all "other software" list because it says it came from launchpad other ppa or something similar. Even after unchecking all of them I tried again and had always an error similar one but without a lot of details. Please improve the upgrade feature soon for a better experience. Thank you! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 16:55:34 2020 InstallationDate: Installed on 2015-06-19 (1947 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120425-15:28 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-17 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900286 Title: Can't upgrade to Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896774] [NEW] Headphone output stopped working after perfoming dist-upgrade
Public bug reported: Find the update log attached (dpkg.log) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 15:32:02 2020 InstallationDate: Installed on 2018-01-11 (986 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago) dmi.bios.date: 07/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "update log_23_09_20.txt" https://bugs.launchpad.net/bugs/1896774/+attachment/5413513/+files/update%20log_23_09_20.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896774 Title: Headphone output stopped working after perfoming dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1896774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892448] [NEW] ceph 15.2.3-0ubuntu0.20.04.2 collides with ceph-deploy 2.0.1-0ubuntu1
Public bug reported: On an Ubuntu 20.04 installation with the focal-proposed repos enabled and both the ceph/ceph-base/ceph-* packages (which are in main) and the ceph-deploy package (which is in universe) installed, the upgrade from ceph 15.2.3-0ubuntu0.20.04.1 to ceph 15.2.3-0ubuntu0.20.04.2 breaks with the following error message: dpkg: error processing archive /var/cache/apt/archives/ceph-base_15.2.3-0ubuntu0.20.04.2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man8/ceph-deploy.8.gz', which is also in package ceph-deploy 2.0.1-0ubuntu1 I wasn't even able to solve this by trying to uninstall/purge ceph- deploy using apt-get or aptitude - instead, I had to resort to dpkg --remove --force-remove-reinstreq ceph-deploy I think this is a bug in ceph 15.2.3-0ubuntu0.20.04.2, more specifically in the packaging of ceph-base 15.2.3-0ubuntu0.20.04.2, which probably shouldn't contain the man page for ceph-deploy since it doesn't seem to contain any other ceph-deploy files either. ** Affects: ceph (Ubuntu) Importance: Undecided Status: New ** Description changed: - On an Ubuntu 20.04 installation with the focal-proposed repo enabled and - both the ceph/ceph-base/ceph-* packages (which are in main) and the + On an Ubuntu 20.04 installation with the focal-proposed repos enabled + and both the ceph/ceph-base/ceph-* packages (which are in main) and the ceph-deploy package (which is in universe) installed, the upgrade from ceph 15.2.3-0ubuntu0.20.04.1 to ceph 15.2.3-0ubuntu0.20.04.2 breaks with the following error message: dpkg: error processing archive /var/cache/apt/archives/ceph-base_15.2.3-0ubuntu0.20.04.2_amd64.deb (--unpack): - trying to overwrite '/usr/share/man/man8/ceph-deploy.8.gz', which is also in package ceph-deploy 2.0.1-0ubuntu1 + trying to overwrite '/usr/share/man/man8/ceph-deploy.8.gz', which is also in package ceph-deploy 2.0.1-0ubuntu1 I wasn't even able to solve this by trying to uninstall/purge ceph- deploy using apt-get or aptitude - instead, I had to resort to dpkg --remove --force-remove-reinstreq ceph-deploy - - I think this is a bug in ceph 15.2.3-0ubuntu0.20.04.2, more specifically in the packaging of ceph-base 15.2.3-0ubuntu0.20.04.2, which probably shouldn't contain the man page for ceph-deploy since it doesn't seem to contain any other ceph-deploy files either. + I think this is a bug in ceph 15.2.3-0ubuntu0.20.04.2, more specifically + in the packaging of ceph-base 15.2.3-0ubuntu0.20.04.2, which probably + shouldn't contain the man page for ceph-deploy since it doesn't seem to + contain any other ceph-deploy files either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892448 Title: ceph 15.2.3-0ubuntu0.20.04.2 collides with ceph-deploy 2.0.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1892448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885159] Re: Firefox 78.0 RC hangs at startup on Ubuntu 16.04
Confirming the fix actually works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885159 Title: Firefox 78.0 RC hangs at startup on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885372] [NEW] package python3-aptdaemon.gtk3widgets 1.1.1+bzr982-0ubuntu32.1 failed to install/upgrade: installed python3-aptdaemon.gtk3widgets package post-installation script subprocess return
Public bug reported: ubuntu a signalé une erreur et a continué à fonctionner ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-aptdaemon.gtk3widgets 1.1.1+bzr982-0ubuntu32.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 27 14:44:34 2020 DuplicateSignature: package:python3-aptdaemon.gtk3widgets:1.1.1+bzr982-0ubuntu32.1 Setting up python3-aptdaemon.gtk3widgets (1.1.1+bzr982-0ubuntu32.1) ... Segmentation fault (core dumped) dpkg: error processing package python3-aptdaemon.gtk3widgets (--configure): installed python3-aptdaemon.gtk3widgets package post-installation script subprocess returned error exit status 139 ErrorMessage: installed python3-aptdaemon.gtk3widgets package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2020-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: aptdaemon Title: package python3-aptdaemon.gtk3widgets 1.1.1+bzr982-0ubuntu32.1 failed to install/upgrade: installed python3-aptdaemon.gtk3widgets package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aptdaemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885372 Title: package python3-aptdaemon.gtk3widgets 1.1.1+bzr982-0ubuntu32.1 failed to install/upgrade: installed python3-aptdaemon.gtk3widgets package post-installation script subprocess returned error exit status 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1885372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883197] Re: Headset not working
I just upgrade to pulseaudio:amd64 1:13.99.1-1ubuntu3.3 and I don't have the issue anymore :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883197 Title: Headset not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883197] Re: Headset not working
When running `alasactl monitor` and plugging the headset and choose "Headphones", I see the following logs line ``` node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE ``` and when I plug it and select "Headset" I see the following log lines ``` node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE ``` The only difference is when selecting "Headphones" 3 more lines are added ``` node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE ``` But after several plugin/plugout (about a dozen of time) I only see the following log lines regardless of choosing "Headphones" or "Headset" but still no audio coming out to the Headset when choosing "Headset". ```node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #11 (2,0,0,Capture Source,0) VALUE node hw:0, #11 (2,0,0,Capture Source,0) VALUE ``` ** Description changed: - When I plug the headset in and when the gnome "Select Audio Devices" - popup and select "Headset" (rather than Headphones), the sound doesn't - go through. But when I select "Headphones" it does. But I then need to - manually select the Headset mic in the sound settings to have my headset - working properly. This issue appear in 20.04. I didn't had this issue - before I upgrade from 19.10 (and previous releases). + When I plug the headset in and when the gnome "Select Audio Devices" pop-up and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. + The only way I can get sound coming through the Headset is by choosing "Headphones" and manually select the Headset mic in the sound settings to have my headset working properly. This issue appears in 20.04. I didn't have this issue before I upgrade from 19.10 (and previous releases). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pascal274918 F.... pulseaudio - /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pascal274918 F pulseaudio + /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Bla
[Bug 1883197] [NEW] Headset not working
Public bug reported: When I plug the headset in and when the gnome "Select Audio Devices" popup and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. But I then need to manually select the Headset mic in the sound settings to have my headset working properly. This issue appear in 20.04. I didn't had this issue before I upgrade from 19.10 (and previous releases). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883197 Title: Headset not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882208] [NEW] undefined symbol: JLI_StringDup
Public bug reported: Apparently there is an issue with the libjli. I get the following error: /usr/lib/jvm/java-11-openjdk-amd64/bin/java: symbol lookup error: /usr/lib/jvm/java-11-openjdk-amd64/bin/java: undefined symbol: JLI_StringDup validate java command: /usr/lib/jvm/java-11-openjdk- amd64/bin/java. I also tried openjdk-8-jre-headless which works absolutely without such an error. Additionally the opfficial OpenJDK package (https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux- x64_bin.tar.gz) works without any issues. So this seems to be caused by the Ubuntu package. Ubuntu release: 18.04 Package version: 11.0.7+10-2ubuntu2 ** Affects: openjdk-lts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882208 Title: undefined symbol: JLI_StringDup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1882208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
Dear Ubuntu kernel package "maintainers", it seems like you have somehow managed to push *again* a kernel with this broken patch into the bionic- proposed repo - this time, it's kernel 5.4.0-31. Are you doing this on purpose? Kernel 5.4.0-33 with two reverted patches *for this specific bug* and *no other changes* has been out for a whole week now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
It seems like the patch you committed to fix this bug causes the overlay module to crash on one of my Ubuntu 18.04 machines. When using linux-generic 5.3.0-52.46, as soon as my gitlab-runner tries to start up a Docker container, dmesg spits out the stuff you can see in the "dmesg-excerpt.txt" attachment. Downgrading to linux-generic 5.3.0-51.44 solves the issue. I haven't bisected this, but looking at the git commit history, your patch looks like the obvious culprit to me. https://kernel.ubuntu.com/git/ubuntu/ubuntu- eoan.git/log/?h=Ubuntu-5.3.0-52.46 ** Attachment added: "dmesg excerpt showing the overlay module crashing" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+attachment/5366880/+files/dmesg-excerpt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875370] [NEW] Add "AmbientCapabilities=CAP_NET_BIND_SERVICE" to systemd unit file
Public bug reported: Please add the line "AmbientCapabilities=CAP_NET_BIND_SERVICE" to the [Service] section of coturn.service so that coturn can bind to ports <1024. See also upstream bug https://github.com/coturn/coturn/issues/421 ** Affects: coturn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875370 Title: Add "AmbientCapabilities=CAP_NET_BIND_SERVICE" to systemd unit file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1875370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874413] Re: openssl 1.1.1f-1ubuntu2 breaks some TLS connections
*** This bug is a duplicate of bug 1864689 *** https://bugs.launchpad.net/bugs/1864689 This might be a duplicate of bug #1864689 "openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689 https://github.com/openssl/openssl/issues/11236 pub.orcid.org is probably running CentOS 8 or RHEL 8 (educated guess based upon the HTTP Server header "nginx/1.16.1"). ** Bug watch added: github.com/openssl/openssl/issues #11236 https://github.com/openssl/openssl/issues/11236 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874413 Title: openssl 1.1.1f-1ubuntu2 breaks some TLS connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1874413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874413] Re: openssl 1.1.1f-1ubuntu2 breaks some TLS connections
** Description changed: On a machine with Ubuntu 20.04 and all available updates installed - (including openssl and libssl openssl 1.1.1f-1ubuntu2): + (including openssl and libssl1.1 1.1.1f-1ubuntu2): user@host:~$ curl 'https://pub.orcid.org/' curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure - - On the same machine, but with the openssl and libssl packages downgraded - to version 1.1.1c-1ubuntu4 from Ubuntu 19.10: + On the same machine, but with the openssl and libssl1.1 packages + downgraded to version 1.1.1c-1ubuntu4 from Ubuntu 19.10: user@host:~$ curl -I 'https://pub.orcid.org/' HTTP/1.1 302 Found Server: nginx/1.16.1 Date: Thu, 23 Apr 2020 09:34:38 GMT Location: https://pub.orcid.org/v3.0/ Transfer-Encoding: chunked Connection: Keep-Alive Set-Cookie: X-Mapping-fjhppofk=EDEB8B375DA428655747278237992826; path=/ - I've also checked this with machines running other distros (OpenWRT and Archlinux), and with those distros, the error occurs neither with - OpenSSL/libssl 1.1.1f nor with OpenSSL/libssl 1.1.1g. This leads me to - assume that the backported patch for CVE-2020-1967 in openssl/libssl 1.1 - .1f-1ubuntu2 is broken. + OpenSSL/libssl1.1 1.1.1f nor with OpenSSL/libssl1.1 1.1.1g. This leads + me to assume that the backported patch for CVE-2020-1967 in + openssl/libssl1.1 1.1.1f-1ubuntu2 is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874413 Title: openssl 1.1.1f-1ubuntu2 breaks some TLS connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1874413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874413] [NEW] openssl 1.1.1f-1ubuntu2 breaks some TLS connections
Public bug reported: On a machine with Ubuntu 20.04 and all available updates installed (including openssl and libssl openssl 1.1.1f-1ubuntu2): user@host:~$ curl 'https://pub.orcid.org/' curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure On the same machine, but with the openssl and libssl packages downgraded to version 1.1.1c-1ubuntu4 from Ubuntu 19.10: user@host:~$ curl -I 'https://pub.orcid.org/' HTTP/1.1 302 Found Server: nginx/1.16.1 Date: Thu, 23 Apr 2020 09:34:38 GMT Location: https://pub.orcid.org/v3.0/ Transfer-Encoding: chunked Connection: Keep-Alive Set-Cookie: X-Mapping-fjhppofk=EDEB8B375DA428655747278237992826; path=/ I've also checked this with machines running other distros (OpenWRT and Archlinux), and with those distros, the error occurs neither with OpenSSL/libssl 1.1.1f nor with OpenSSL/libssl 1.1.1g. This leads me to assume that the backported patch for CVE-2020-1967 in openssl/libssl 1.1 .1f-1ubuntu2 is broken. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874413 Title: openssl 1.1.1f-1ubuntu2 breaks some TLS connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1874413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490935]
I fully agree with ben.bucksch' comment: it is good practice to keep a trace of trace of what the original Subject line showed. Sometimes I like to edit the email itself to add comments/annotations to make the content more (re-)usable for myself. In that case I explicitly indicate (eg. by 'keyword' like "_ANNOTATIONS") that this was an entry added after receiving the email. This feature is not 'comfortably' provided by all my favorite mail-clients though ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490935 Title: it is not possible to modify email subject To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/490935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221138] Re: package linux-image-3.5.0-39-generic 3.5.0-39.60~precise1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
I didn't see this recurring in newer releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221138 Title: package linux-image-3.5.0-39-generic 3.5.0-39.60~precise1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191893] Re: Typo in ddtp-translations (this is not a joke)
Still there in Ubuntu Focal: Package: ddtp-translations Version: 20190415.1 ** Changed in: ddtp-translations (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191893 Title: Typo in ddtp-translations (this is not a joke) To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1191893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480525] Re: Typo in assaultcube: "pased"
Ubuntu Focal now has assaultcube 1.2.0.2.1-2 from debian ** Changed in: ddtp-ubuntu Status: Triaged => Fix Released ** Changed in: assaultcube (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480525 Title: Typo in assaultcube: "pased" To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1480525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"
Still there in focal: Package: unity-scopes-runner Version: 7.1.4+19.04.20190319-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268210 Title: unity-scopes-runner: Typo in package description: "scoped" To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1268210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254476] Re: Typo in package : dooble - string #7553
The dooble package was deleted on 2017-04-01 by Steve Langasek unmaintained; LP: #1605237 ** Changed in: ddtp-ubuntu Status: Triaged => Fix Released ** Changed in: dooble (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254476 Title: Typo in package : dooble - string #7553 To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1254476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667344] Re: spelling error in Package indicator-transfer-download-manager
The package was deleted on 2017-08-24 by Steve Langasek obsoleted product, incompatible with Qt5.9; LP: #1712874 ** Changed in: ddtp-ubuntu Status: Triaged => Fix Released ** Changed in: indicator-transfer (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667344 Title: spelling error in Package indicator-transfer-download-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1667344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Thank you Olivier for your effort and the information you provided me 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/1850529 Title: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1850529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672139]
Such "feature" of tracing the containing folder is felt by many to be an almost trivial necessity for people managing their bookmarks ... While waiting for the solution in Firefox.. I discovered "Pale Moon" which offers this feature quite nicely ... I don't know how to put an image in this window, hence I share this Dropbox-link for an illustration: https://www.dropbox.com/s/iw3trcmmh44plr5/Bookmark%20Containing%20Folder%20%2B%20Patch.jpg?dl=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672139 Title: Add "Open Enclosing Folder" context menu to search results of bookmarks in the Library window (link to view/open containing folder, parent folder button) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1672139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
Are there any updates regarding this patch? Personally I am using Fedora 30 right now on my ThinkPad L380 Yoga and have the same problem with MAC Passthrough. The Dock I am using is a Lenovo USB-C Dock (vid_17ef pid_a359). I guess it uses the same RTL8153 chip as the thunderbolt dock. I would appreciate it if you could publish the source patches, as there is only the ubuntu kernel binary. Thank you in advance for the help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] Re: screen frozen after reboot
Back to my computer I applied step 2 as suggested and got : whoopsie-id: e3a8dbc9dbb2e9589754eb397d8ff19924a7bec147827c8e2333de7493dcd433a7cacae13de6185804843502331b4626bb6de5038cc1a182ec3b3aa4ed9c2130 which give the following line: 2019-07-18 07:072019-07-19 20:07 UTCCrash xserver-xorg-core with the link: https://errors.ubuntu.com/oops/8d8b8168-aa67-11e9-b233-fa163e102db1 I will now try step 4 but have to reboot with wayland... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] Re: screen frozen after reboot
Generated the prevboot.txt (see attached). I did not find any file related to wayland crash in /var/crash. I did find though an xorg crash file dated from this morning. I sent it through ubuntu-bug though I was not asked a bug number (I am not sure it worked). I do not really understand what happened this morning as the xorg config ended up working. I don't know if this new fact may help solving the issue or is rather disturbing... ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+attachment/5277936/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1836805/+attachment/529/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1836805/+attachment/528/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] Re: screen frozen after reboot
A boot with 5.0.0-13 (available in boot menu after install) rather than default 5.0.0-20 provided the same symptoms. I changed /etc/gdm3/custom.conf to boot with xorg and ... it did work. I was able to run apport-collect. I guess I will stay in this configuration. Don't hesitate to tell me if you need me to run more tests to help solving this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] Re: screen frozen after reboot
apport information ** Tags added: apport-collected ** Description changed: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-07-15 (2 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gdm3 3.32.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 + Tags: disco + Uname: Linux 5.0.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1836805/+attachment/527/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836805] [NEW] screen frozen after reboot
Public bug reported: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "bug_info.txt" https://bugs.launchpad.net/bugs/1836805/+attachment/5277530/+files/bug_info.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803808]
Isn't bug 15894 a duplicate of this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803808 Title: wireshark crashed with SIGSEGV in QIcon::~QIcon() under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/wireshark/+bug/1803808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799946] Re: OpenJFX-11 does not work with OpenJDK-8
This bug also effects the greenfoot project. Since the PPA ppa:webupd8team/java is discontinued, there is no way to run greenfoot under Ubuntu. I'm a teacher and it would be very helpful to have an openjfx-8 package so that i can run greenfoot. ``` $ greenfoot Exception in thread "main" java.lang.NoClassDefFoundError: javafx/application/Application at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at bluej.Boot.main(Boot.java:193) Caused by: java.lang.ClassNotFoundException: javafx.application.Application at java.net.URLClassLoader.findClass(URLClassLoader.java:382) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 13 more ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799946 Title: OpenJFX-11 does not work with OpenJDK-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1799946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799946] Re: OpenJFX-11 does not work with OpenJDK-8
ok. This works: ``` sudo apt install openjfx=8u161-b12-1ubuntu2 libopenjfx-java=8u161-b12-1ubuntu2 libopenjfx-jni=8u161-b12-1ubuntu2 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799946 Title: OpenJFX-11 does not work with OpenJDK-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1799946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828032] [NEW] install didnt succeed to write grub to /dev/sda
Public bug reported: at the end of install on an usb drive, grub-installer failed on master disk i dont have more information ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Tue May 7 13:56:45 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828032 Title: install didnt succeed to write grub to /dev/sda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1828032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823053] [NEW] wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco
Public bug reported: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: eap eduroam libssl openssl peap tls1.3 tlsv1.3 ttls wpa wpa-enterprise wpasupplicant -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823053 Title: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1823053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197362] Re: typo in string #12048
Fixed since ubuntu cosmic ** Changed in: ddtp-ubuntu Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197362 Title: typo in string #12048 To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1197362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480525] Re: Typo in assaultcube: "pased"
Still there in 1.2.0.2+dfsg1-0ubuntu4 in ubuntu disco. ** Changed in: ddtp-ubuntu Status: In Progress => Triaged ** Changed in: ddtp-ubuntu Assignee: Simon Vall (hellosimonvall) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480525 Title: Typo in assaultcube: "pased" To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1480525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085355] Re: Typo in lxsession-edit package description
Still there in 0.5.3-2ubuntu1 in ubuntu disco, please merge from debian. ** Tags added: needs-debian-merge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085355 Title: Typo in lxsession-edit package description To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1085355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814167] [NEW] package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer.
Public bug reported: problem with ubuntu 16.04 on an external disk, read only. Then i used grub-customizer. now i try to do again the updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: poppler-utils 0.41.0-0ubuntu1.11 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: poppler-utils: Configure cups: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 31 21:55:37 2019 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2019-01-11 (20 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: poppler Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814167 Title: package poppler-utils 0.41.0-0ubuntu1.11 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1814167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811382] [NEW] While EFI/Boot and EFI/ubuntu is already present in EFI System Partition grub-installer failed
Public bug reported: I was trying to install Bionic 18.04.1 on my Laptop from a bootable USB stick. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Fri Jan 11 07:34:34 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811382 Title: While EFI/Boot and EFI/ubuntu is already present in EFI System Partition grub-installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1811382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806170] [NEW] impossible de passer a la version 16
Public bug reported: voir fichier joint ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.10 ProcVersionSignature: Ubuntu 4.4.0-139.165~14.04.1-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CrashDB: ubuntu Date: Sat Dec 1 09:21:15 2018 InstallationDate: Installed on 2015-08-07 (1211 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2018-12-01 (0 days ago) VarLogDistupgradeAptlog: Log time: 2018-12-01 09:18:05.147050 Log time: 2018-12-01 09:19:07.103947 Log time: 2018-12-01 09:20:33.241433 Log time: 2018-12-01 09:21:46.899064 VarLogDistupgradeTermlog: mtime.conffile..etc.update.manager.release.upgrades: 2018-11-30T15:37:20.509752 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806170 Title: impossible de passer a la version 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1806170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
UBUNTU 18.04 LTS, same Problem. The workaround helped me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805168] [NEW] grub-installer failed during a re-install of bionic beaver 18.04
Public bug reported: After a first installation in dualboot with Windows10 and two weeks of Linux use and some updates, I lost grub-menu and Ubuntu18.04 refused to start even from the uefi entry in the bios boot menu. So I tried to reinstall the root partition (ext4, formatted, 21 Gb), keeping "/Home" partition. Finally grub installation missed. Description:Ubuntu 18.04.1 LTS Release:18.04 Linux ubuntu 4.15.0-29-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Mon Nov 26 15:50:20 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805168 Title: grub-installer failed during a re-install of bionic beaver 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1805168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802674] Re: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04
Well, my Launchpad PPA is currently back to fully working. After rebuilding libgphoto2 2.5.16 (the Bionic 18.04 version) I found another missing library link: dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/ dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.16/konica_qm150.so contains an unresolvable reference to symbol exif_data_new_from_data: it's probably a plugin dpkg-shlibdeps: warning: 1 similar warning has been skipped (use -v to see it) That's the libexif library here missing in the build. I did update anew my debian/rules files in my PPA, since I did a backport of this version for Xenial 16.04. A side note here is that the debian/rules file looks poorly maintained by Debian. They apparently add libraries link by editing the CFLAGS and CXXFLAGS ... Though there is dedicated commands to do so. They missed as well a: include /usr/share/dpkg/buildflags.mk and the fully functional --parallel build with the right parameters. tested with -j12 (processor cores) and working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802674 Title: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1802674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802674] Re: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04
Well, I did find a working fix to apply in debian/rules.
# Add missing math libraray for linking in gphoto2
# (automatic math library linking was dropped by GCC years ago)
export DEB_LDFLAGS_MAINT_APPEND := -lm
I did add as well all available processor cores in parallel build, and
Optimization O3 instead of -O2.
However it would better if upstream would update its own configure.ac
file ...
Here is the portion of the log showing no sign of unresolved
dependencies:
make[1]: Leaving directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
debian/rules override_dh_makeshlibs
make[1]: Entering directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
dh_makeshlibs -plibgphoto2-6 -X/usr/lib/x86_64-linux-gnu/libgphoto2/
dh_makeshlibs -plibgphoto2-port12 -X/usr/lib/x86_64-linux-gnu/libgphoto2_port/
make[1]: Leaving directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
debian/rules override_dh_shlibdeps
make[1]: Entering directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
make[1]: Leaving directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
dh_installdeb -O--parallel
debian/rules override_dh_gencontrol
make[1]: Entering directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
dh_gencontrol
dpkg-gencontrol: warning: Depends field of package libgphoto2-port12-dbgsym:
unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: Depends field of package libgphoto2-6-dbgsym: unknown
substitution variable ${shlibs:Depends}
dh_gencontrol -plibgphoto2-6 -- -Vudev-hotplug='udev (>= 201)'
make[1]: Leaving directory
'/home/ubuntu-xenial/pascal/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
dh_md5sums -O--parallel
dh_builddeb -O--parallel
It would be nice for Ubuntu to update the build in all supported
releases.
The rebuild will be available in my PPA soon:
https://launchpad.net/~anton+/+archive/ubuntu/photo-video-apps
However beware that this PPA is yet NOT to be added on any system as
it's still unstable and miss some dependencies i.e. if installing a
package you will be faced with a partial upgrade which in turn will
remove some of your already installed apps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802674
Title:
libgphoto2 builds lacks a link to the math library in all Ubuntu
releases since at least Xenial 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtpaint/+bug/1802674/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802674] Re: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04
pow is indeed part as well of the math library for the 'power of' function. as well as roundf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802674 Title: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtpaint/+bug/1802674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802674] [NEW] libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04
Public bug reported: Background: With all recent versions of GCC on GNU/Linux systems like Ubuntu, when you use the math library, you have to explicitly link to it. I am currently using Xenial 16.04 and did a recompile of source package libgphoto2. Then I got warnings fromdpkg-shlibdeps. make[1]: Entering directory '/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9' dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/ dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/ptp2.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all) dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/stv0680.so contains an unresolvable reference to symbol pow: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sonix.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/digigr8.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/mars.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sierra.so contains an unresolvable reference to symbol roundf: it's probably a plugin make[1]: Leaving directory '/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9' I am quite sure that sqrt is the square root function from the math library. Usually, at least with GCC version newer than ~ 2013 you have to append a -lm to link against the math library. Obviously this isn't the case: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE -DLOCALEDIR=\"/usr/share/locale\" -DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c -fPIC -DPIC -o .libs/libgphoto2_la-gphoto2-filesys.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE -DLOCALEDIR=\"/usr/share/locale\" -DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c -fPIE -o libgphoto2_la-gphoto2-filesys.o >/dev/null 2>&1 at the end we should see -c gphoto2-filesys.c -fPIE -lm -o libgphoto2_la-gphoto2-filesys.o >/dev/null 2>&1 I did check in the official Ubuntu repository and you did get the same warnings: dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/ dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sierra.so contains an unresolvable reference to symbol roundf: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/ptp2.so contains an unresolvable reference to symbol log2: it's probably a plugin dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v to see them all) dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/digigr8.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/mars.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sonix.so contains an unresolvable reference to symbol sqrt: it's probably a plugin dpkg-shlibdeps: warning: debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/stv0680.so contains an unresolvable reference to symbol pow: it's probably a plugin make[1]: Leaving directory '/«PKGBUILDDIR»' It looks like the switch from GCC to NOT automatically link the math library was never dealt with, even in the latest Ubuntu releases ... I am no a configure.ac specialist and don't know exactly what to do in debian/rules to correct the problem. Either way may be upstream
[Bug 1777474] Re: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates
Can somebody please have a look at this? Booting an ISO and checking if HTTPS works, or simply adding a certain deb package to the default installer ISO shouldn't really be rocket science. ** Changed in: debian-installer (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777474 Title: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1777474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787258] Re: 3.13.0-155.205 Kernel Panic - divide by zero
Tested on a few AWS instances that wouldn't boot on 3.13.0-155.205 and they are now back to normal after upgrading to 3.13.0-156.206. Thanks for the quick fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787258 Title: 3.13.0-155.205 Kernel Panic - divide by zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786677] Re: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s)
Hi, I put you unwillingly into cross-issues ( https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532 ), but that maybe enlighten useful behaviors of apparmarmor and libvirt. Root causes for this ticket and the other one reopening were my mistakes, not bugs. Thanks again for your inputs: thorough references, features behavior and code snippets, I learnt a lot and gained more autonomy with the OS from those discussions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786677 Title: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
Hi Christian,
This is a false-positive reopening of this issue indeed. Still, it may
contain useful bits.
The error occurrence I forwarded is now solved, thanks to what you
advised on a side-subject at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/comments/6
.
When producing stacktrace in here (
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/comments/28 ),
the root cause was that I appended this snippet at the end of
'/etc/apparmor.d/abstractions/libvirt-qemu':
--
{dev,run}/shm/ rw,
{dev,run}/shm/* rw,
--
This was a mistake to add those rules, since I should have edited the
existing ones (that you stated at
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/comments/6
).
In the end, I kinda duplicated the '{dev,run}/shm' rules when producing the
error. With the following diff + a reload of the AppArmor profile, the error
vanished:
--
$ sudo diff /etc/apparmor.d/abstractions/libvirt-qemu
~/.sys/bak-custom/etc/apparmor.d/abstractions/libvirt-qemu
56c56,57
< /{dev,run}/shm r,
---
> /{dev,run}/shm rw,
> /{dev,run}/shm/* rw,
--
What I did was just moving the 2 lines initially appended to the files,
in order to overwrite the existing rules.
A few asserts when the error was produced:
- None of 'sudo systemctl reload apparmor', 'sudo systemctl restart apparmor'
or 'sudo systemctl status apparmor' (in sequence) returned or shew an error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Title:
Unable to set AppArmor profile [...] no such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
(sorry for spamming multiple-posts) When the error occurs, 'dmesg' outputs: -- [ 1835.178954] audit: type=1400 audit(1534455163.959:121): apparmor="DENIED" operation="change_profile" info="label not found" error=-2 profile="/usr/sbin/libvirtd" name="libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8" pid=4930 comm="libvirtd" -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
I reproduce the same on 18.04 LTS:
Log when starting a KVM VM with 'virt-manager':
--
Error starting domain: internal error: Process exited prior to exec: libvirt:
error : unable to set AppArmor profile
'libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8' for '/usr/bin/kvm-spice': No
such file or directory
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: Process exited prior to exec: libvirt: error :
unable to set AppArmor profile 'libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8'
for '/usr/bin/kvm-spice': No such file or directory
--
But the AppArmor profiles exist:
--
$ sudo ls -lah /etc/apparmor.d/libvirt/libvirt-*
-rw-r--r-- 1 root root 293 août 16 23:04
/etc/apparmor.d/libvirt/libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8
-rw-r--r-- 1 root root 1,8K août 16 23:05
/etc/apparmor.d/libvirt/libvirt-a1937a46-2b13-41bd-998b-27ee9a8209a8.files
$
--
I checked paths the VM relies on (CD-ROM ISOs absolute paths) and they
contain no whitespaces.
Tell me if the virt-manager VM XML file is needed for troubleshooting.
A troubleshooting sequence I tried, with no positive result:
1/ Deeply-deleting '*ibvir*' in '/etc/apparmor.d'
2/ Reinstalling the 'libvirt-bin' and its dependencies (incl.
'libvirt-daemon-system'), by providing the 'confmiss' DPKG flag: it restored
anything libvirt-related in '/etc/apparmor.d'
2.b/ Did 1/ and 2/ for the 'qemu-kvm' and 'virt-manager' packages also
3/ Reloaded the 'apparmor' systemd daemon
4/ Rebooted machine
5/ Reloaded daemons ('daemon-reload'), the 'libvirtd' and 'qemu-kvm' systemd
daemons
6/ Retried to start the VM
Could a dependency package be the cause of it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Title:
Unable to set AppArmor profile [...] no such file or directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
I forgot to mention the VM never triggered AppArmor errors with 16.04.x LTS. I never checked if AppArmor was really running by the way (this is not a production host, only a developer machine). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786677] Re: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s)
Maybe not a false-positive: https://www.reddit.com/r/VFIO/comments/8o13i4/cant_start_vm_with_lookingglass_shared_memory/e1kp9s2 In there, people installed kind of an add-on to libvirt. This add-on requires a file in the '/dev/shm' shared-memory. With a properly running AppArmor, that new file gets denied by default (libvirt-qemu tries to create the file, and its AppArmor profile denies so). But it seems most people there encountered no denial from AppArmor. It may be that their AppArmor failed to start, in the same way as mine did. All in all, this is about tweaking libvirt. These users probably installed non-defaults packages/sources as I did, what does not fit a long-term support usage. We broke TOS! ;) A story to forget then :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786677 Title: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786677] Re: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s)
In fact, I got that '/dev/shm/foo' file denied too, on localhost, as soon as I fixed the AppArmor daemon through your advices. When I filled the bug initially, that file was living flawlessly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786677 Title: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787258] Re: 3.13.0-155.205 Kernel Panic - divide by zero
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787258 Title: 3.13.0-155.205 Kernel Panic - divide by zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787258] Re: 3.13.0-155.205 Kernel Panic - divide by zero
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787258 Title: 3.13.0-155.205 Kernel Panic - divide by zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786677] Re: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s)
Hi Christian, Also thanks for input, and sorry for wasting your time: it's probably a false-positive issue, to reject. I went too quick and proceeded before reading the 2 troubleshooting commands you advised. But well, I think I did the same in a less precise manner: -- $ sudo ls -lah /etc/apparmor.d/local/usr.sbin.libvirtd ls: cannot access '/etc/apparmor.d/local/usr.sbin.libvirtd': No such file or directory $ sudo aptitude reinstall libvirt-daemon-system The following packages will be REINSTALLED: libvirt-daemon-system 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 80,7 kB of archives. After unpacking 0 B will be used. Get: 1 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libvirt-daemon-system amd64 4.0.0-1ubuntu8.3 [80,7 kB] Fetched 80,7 kB in 0s (162 kB/s) Preconfiguring packages ... (Reading database ... 198730 files and directories currently installed.) Preparing to unpack .../libvirt-daemon-system_4.0.0-1ubuntu8.3_amd64.deb ... Unpacking libvirt-daemon-system (4.0.0-1ubuntu8.3) over (4.0.0-1ubuntu8.3) ... Setting up libvirt-daemon-system (4.0.0-1ubuntu8.3) ... virtlockd.service is a disabled or a static unit, not starting it. virtlockd.socket is a disabled or a static unit, not starting it. Setting up libvirt-daemon dnsmasq configuration. Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.3) ... $ sudo ls -lah /etc/apparmor.d/local/usr.sbin.libvirtd -rw-r--r-- 1 root root 0 août 16 19:27 /etc/apparmor.d/local/usr.sbin.libvirtd $ -- Since the file was statically bundled in a repository package in 16.04.x LTS, I didn't think it could be a generated asset. Well, this would mean that: - The 'libvirt-daemon-system' package was installed when I started the upgrade process from 16.04.x LTS - It got updated/upgraded during the upgrade process, but not purged-then-installed (I'm not sure if the later option should have happened) What I can assert: - I used a libvirt PPA a year ago, to test newer libvirt features. I'm not on a critical instance. PPA: https://launchpad.net/~jacob/+archive/ubuntu/virtualisation . Those features ran well since then - Before upgrading to 18.04 LTS, a small-week ago, I purged the PPA packages + removed the PPA (both through the 'ppa-purge' command), then installed the related Ubuntu repository packages again, by reinstalling from the top: 'sudo aptitude reinstall qemu-kvm libvirt-bin', that fetched its dependencies as needed. This is probably where I screw up Ubuntu's defaults for libvirt, by mismanaging the PPA - Since I moved to 18.04 LTS, I rely only on Ubuntu's defaults (i.e. main/security/universe/multiverse) packages This probably narrows down to me not using APT properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786677 Title: [bionic] [libvirt-daemon-system] Missing AppArmor configuration file(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
Also present on Lubuntu 18.04 (from a 16.04 upgrade, at least). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
Maybe an hint: - The first network icon has no sections horizontal bar UI-delimiters (e.g. between the 'Wifi' and 'Mobile broadband' sections) - The second network icon has those UI-delimiters -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786242] [NEW] Software Updater List is Blank while there is 943.1 MB of Updates to Download while Returning from an 8 Weeks Vacations
Public bug reported: I am returning from an 8 weeks vacations and my Ubuntu 16.04 system is showing me an empty list of updates while it is telling me there is 943.1 MB of updates to download. When trying to update the system from Synaptic the Mark for Upgrade (right click) is working fine ... One hour ago the same problem was reported on AskUbuntu by another user https://askubuntu.com/questions/1063814/software-updater-shows-empty- list-16-04 Why suddenly the Ubuntu Software Updater is not able to list all the updates ? nor update anything ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: update-manager 1:16.04.13 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Aptdaemon: Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 9 08:56:36 2018 ExecutablePath: /usr/bin/update-manager GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'462' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'467' b'com.ubuntu.update-manager' b'launch-time' b'int64 1533819257' InstallationDate: Installed on 2016-07-31 (739 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Attachment added: "Software Updater.png" https://bugs.launchpad.net/bugs/1786242/+attachment/5173297/+files/Software%20Updater.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786242 Title: Software Updater List is Blank while there is 943.1 MB of Updates to Download while Returning from an 8 Weeks Vacations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1786242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677295] Re: qiv --watch displays corrupt images and reports "libpng error: Read Error"
Should be fixed with qiv 2.3.1 starting with Ubuntu 15.04: 19.07.2011 [tw] when using "--watch" option, make sure pic is not reloaded while still written. ** Changed in: qiv (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677295 Title: qiv --watch displays corrupt images and reports "libpng error: Read Error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qiv/+bug/677295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
** Also affects: linux (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777474] Re: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates
Yes, I can reproduce the issue with that ISO as well. Since I've booted the ISO in a VM with only a serial console and no video card, I've added "console=ttyS0,115200" to the installer kernel's cmdline in GRUB, and cancelled installation as soon as possible to get to the big menu with all the installation steps, so I could select "Execute shell". From there, I've tried downloading a file from an HTTPS site with a valid Let's Encrypt certificate, and got the ominous "ERROR: cannot verify $HOSTNAME's certificate, issued by $CA: Unable to locally verify the issuer's authority." message. So yes, the "official" installer ISO images seem to lack the ca- certificates package 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/1777474 Title: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1777474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
Hello, I also confirm this bug on 2 computers with Kubuntu 16.04. By selecting XRender as the rendering engine everything works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780664 Title: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777474] [NEW] Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates
Public bug reported: When using the netboot ISO (https://ftp.halifax.rwth- aachen.de/ubuntu/dists/bionic/main/installer- amd64/20101020ubuntu543/images/netboot/mini.iso) in the "expert command line mode", the installer asks the user to select between the protocols HTTP, HTTPS and FTP when specifying a mirror server. However, HTTPS mirrors don't work at all since the ISO lacks the "ca-certificates" package. When using the installer in the "non-expert"/"normal" command line mode, even when manually specifying an HTTPS mirror, either HTTP gets used or the mirror server's certificates don't get checked at all (haven't found out yet which of the two possibilities applies). Either way, the ca-certificates package should be included in the netboot iso. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777474 Title: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1777474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
This is issue is still present in Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
