[Touch-packages] [Bug 2085848] [NEW] db5.3: FTBFS in oracular !amd64 because of implicit-int

Public bug reported: The compiler flag "-Wimplicit-int" is causing some configure steps to fail. The corresponding Debian bug report is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084782 This is fixed in Debian sid with: db5.3 (5.3.28+dfsg2-8) unstable; urgency=medium * QA upload

[Touch-packages] [Bug 2085848] Re: db5.3: FTBFS in oracular !amd64 because of implicit-int

Fix backport in https://code.launchpad.net/~tobhe/ubuntu/+source/db5.3/+git/db5.3/+merge/475912 and currently building at https://launchpad.net/~tobhe/+archive/ubuntu/private/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscri

[Touch-packages] [Bug 2085848] Re: db5.3: FTBFS in oracular !amd64 because of implicit-int

** Description changed: - The compiler flag "-Wimplicit-int" is causing some configure steps to fail. - The corresponding Debian bug report is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084782 + [ Impact ] + + * The compiler flag "-Wimplicit-int" is causing some configure steps to + fai

[Touch-packages] [Bug 2081384] [NEW] bluetooth headphones need reconnect after every reboot

Public bug reported: This issue seems to be caused by a recent package update in oracular. Every time I reboot my desktop my bluetooth headset will fail to connect until I manually go through forget device -> new pairing. journalctl says: 23:13:44 desktop bluetoothd[3274]: src/profile.c:ext_conn

[Touch-packages] [Bug 2079970] Re: Debug symbols are unavailable for 3.0.2-0ubuntu1.18 (security update)

Yep, now it worked. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2079970 Title: Debug symbols are unavailable for 3.0.2-0ubuntu1.18 (security update) Status in

[Touch-packages] [Bug 2079970] Re: Debug symbols are unavailable for 3.0.2-0ubuntu1.18 (security update)

Hi Eduardo, Thanks for looking into this issue. Unfortunately, the file http://ddebs.ubuntu.com/dists/jammy-updates/main/binary-amd64/Packages still lists 3.0.2-0ubuntu1.17 as version for libssl3-dbgsym. The timestamp of the file is 2024-08-23 00:44, so I guess it wasn't updated/synced. Or maybe i

[Touch-packages] [Bug 2079970] [NEW] Debug symbols are unavailable for 3.0.2-0ubuntu1.18 (security update)

Public bug reported: The latest debug symbols (libssl3-dbgsym) available are for 3.0.2-0ubuntu1.17. Since they have a hard dependency on that version of the library, the installation currently fails with: libssl3-dbgsym : Depends: libssl3 (= 3.0.2-0ubuntu1.17) but 3.0.2-0ubuntu1.18 is to be ins

[Touch-packages] [Bug 2064284] [NEW] apparmor.service fails because of invalid config

Public bug reported: After upgrading to noble apparmor.service fails on my machine with the following log message: Apr 30 14:28:42 shodan apparmor.systemd[1739]: Restarting AppArmor Apr 30 14:28:42 shodan apparmor.systemd[1739]: Reloading AppArmor profiles Apr 30 14:28:42 shodan apparmor.systemd[

[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

> Was it it more than a red line in systemctl status output? Does it have annoying logging behaviour or break some other service if it isn't running? Red lines and an avoidable boot delay while trying to restart and failing a bunch of times. -- You received this bug notification because you are

[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

I don't think that's enough since it also gets pulled in by ubuntu- desktop and ubuntu-desktop-minimal as recommends. It would also be nice if we found a solution that fixes the issue on existing installations since upgrades from mantic to noble will trigger the bug. -- You received this bug noti

[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

Looking at the diff between mantic and noble I think the regression was cause by a change to pd-mapper.service.in for https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

Can confirm that this is was a major annoyance on my m2 air after upgrading to noble. it seems like this worked better in previous releases. Looking at my logs it seems like it was already installed on mantic but didn't cause startup problems. I think it gets pulled in by being in Recommends for ub

[Touch-packages] [Bug 2054609] Re: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1

The reason for the crash is that ntp uses an outdated OpenSSL API to use MD5 despite it normally being blocked in FIPS mode. This particular API has been deprecated with OpenSSL 3 which we ship in Jammy. This could be mitigated by switching to a newer OpenSSL API, but ntp also seems to be on lif

[Touch-packages] [Bug 2057927] [NEW] lxd vga console throws "Operation not permitted" error

Public bug reported: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to appar

[Touch-packages] [Bug 2056593] Re: [FFE] FIPS compatibility patches

Adding a few more details as requested by Adrien. I used lxd to run the autopkgtest, in particular: # Build lxd image /usr/bin/autopkgtest-build-lxd ubuntu-daily:noble # Run autopkgtest -s --apt-pocket=proposed ./openssl_3.0.13-1ubuntu2.dsc -- lxd autopkgtest/ubuntu/noble/amd64 It is qu

[Touch-packages] [Bug 2056593] Re: [FFE] FIPS compatibility patches

As promised, here are some more details on how I tested: - been running autopkgtest locally and made sure they pass (log attached) - installed it on my local development machine to see if anything breaks - tested the upgrade in a lxd container, made sure openssl speed works and does the right thin

[Touch-packages] [Bug 2056593] Re: [FFE] FIPS compatibility patches

** Attachment added: "apt install log from fresh noble lxd container" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2056593/+attachment/5754146/+files/openssl_3.0.13-1ubuntu2_install.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, w

[Touch-packages] [Bug 2056593] [NEW] [FFE] FIPS compatibility patches

Public bug reported: We have an open MR with a handful of FIPS compatibilty changes we wore hoping to get into 24.04. The main purpose of the changes is to detect whether the kernel is running in FIPS mode and adjust the behavior of the library accordingly by loading the correct provider backend a

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

The detected regression looks like a false-positive caused by another dependency. The reported error is `/bin/sh: 1: python: not found` which does not seem to be caused by the changes in libunwind. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, whi

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

I have installed libunwind=1.6.2-0ubuntu1.1 on my 16K page arm machine and verified that the xorg crash is indeed fixed with this version. To make sure it also does not negatively affect other hardware configurations I also tested on my amd64 desktop and found that everything still works without re

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

New diff as requested by @tsimonq2. I changed the version to 1.6.2-0ubuntu1.1 and added a DEP-3 header instead of taking the unmodified patch from lunar as I did previously. ** Patch removed: "kinetic-fix" https://bugs.launchpad.net/ubuntu/kinetic/+source/libunwind/+bug/2004039/+attachment/564

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

** Description changed: [ Impact ] - * On kernels with page size > 4K xorg (and presumably other applications -relying on libunwind) crashes on startup. This affects anyone -running the official arm64 generic-64k kernel or custom non 4k kernels -(as used by e.g. apple silicon). +

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

** Description changed: - The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. - This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. + [ Impact ] - Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

Attached is a debdiff with the backported fix from lunar ** Patch added: "kinetic-fix" https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+attachment/5643674/+files/libunwind_1.6.2-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch s

[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

** Also affects: libunwind (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: libunwind (Ubuntu Jammy) ** Also affects: libunwind (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu T

[Touch-packages] [Bug 2004039] [NEW] libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes

Public bug reported: The libunwind version we ship in kinetic crahes on arm64 platforms with page sizes > 4k. This was fixed in libunwind upstream. The fix made it into the debian version synced to lunar. Debian bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026217 Upstream co

[Touch-packages] [Bug 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks

** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973642 Title: [REGRESSION] Unable to connec

[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

I don't know much about dropbear but from your explanation it does indeed sound like this is an upstream OpenSSH bug that should be reported at https://bugzilla.mindrot.org/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ope

[Touch-packages] [Bug 1971992] Re: openssl rmd160 digest broken

** Changed in: openssl (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in

[Touch-packages] [Bug 1971992] Re: openssl rmd160 digest broken

Hey Jan, thanks for the report. This has been discussed upstream at https://github.com/openssl/openssl/issues/16994. OpenSSL 3 has deprecated RIPEMD160 and thus moved them to the legacy provider according to the official openssl migration guide at https://www.openssl.org/docs/manmaster/man7/migr

[Touch-packages] [Bug 1971992] Re: openssl rmd160 digest broken

** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in opens

[Touch-packages] [Bug 1958538] Re: Extreme Screen flickering when setting a non-native resolution

** Summary changed: - Extreme Screen flickering when non native resolution + Extreme Screen flickering when setting a non-native resolution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpa

[Touch-packages] [Bug 1958538] [NEW] Extreme Screen flickering when non native resolution

Public bug reported: As soon I set the screen resolution to non native (4k laptop display) the screen begins to flicker and horizontal/vertical lines appear. (See attached image) Interestingly this happens only to the internal screen, external monitors work fine. Also during boot (supposedly when

[Touch-packages] [Bug 1940304] [NEW] package openssh-client 1:8.2p1-4ubuntu0.2 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Public bug reported: Occurred during Software Update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-client 1:8.2p1-4ubuntu0.2 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 C

[Touch-packages] [Bug 1814938] Re: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed

hey there, I have the exact same problem, but I couldn't find a solution yet. I included the edid file using the script given above: lsinitramfs /boot/initrd.img-5.11.0-25-generic | grep edid usr/lib/firmware/edid usr/lib/firmware/edid/edid.bin my grub config looks like this: cat /etc/default/g

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

I've managed to make the subwoofer work with some caveats, I've made a short guide here: https://gist.github.com/BXZ/48cd8173807676a1402cf4bc7928c0c0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https

[Touch-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

*** This bug is a duplicate of bug 1849859 *** https://bugs.launchpad.net/bugs/1849859 It doesn't seem to me that this is really a duplicate of bug #1849859. At least the reported symptoms are not identical. In any case, has anybody found a workaround for this? -- You received this bug noti

[Touch-packages] [Bug 1847510] [NEW] python3 distutils reports path which is not in sys.path for /usr/local prefix

*** This bug is a duplicate of bug 1814653 *** https://bugs.launchpad.net/bugs/1814653 Public bug reported: sysconfig.distutils.get_python_lib() reports the path '/usr/local/lib/python3/dist-packages' for the prefix '/usr/local'. This does not match the path '/usr/local/lib/python3.6/dist-pa

[Touch-packages] [Bug 362570] Re: Python distutils installs into 'site-packages' instead of 'dist-packages' when a prefix is set

** Changed in: python3-defaults (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/362570 Title: Python distutils installs in

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

> (Odds are that whatever causes it to be recreated later in boot would be > blocked by cloud-init waiting.) But that's not happening. The instance does boot normally, the only service degraded is cloud-init and there is no significant delay either. So conversely, if I put a loop into cloud-init

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

I may be missing the point, but the symlink in question is eventually recreated, does that tell us anything? This here > Dan had put a udevadm settle in this spot like so > > def get_size(filename) >util.subp(['udevadm', 'settle']) >os.open() looks to me like the event queue should be

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

** Changed in: cloud-init Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-i

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

@daniel-thewatkins, I'm not convinced that this bug is invalid for cloud-init. After reading through all of this again, I still don't understand, what guarantee there is that when `udevadm settle` is called, all relevant events have already been queued. Copying udevadm over, and with that suppress

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

When I say unorthodox, I mean I copied the binary ;) So that should narrow it down quite a bit. Unless there is more funniness involved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

Oh, good observation, Dan. Yes, it was happening on Cosmic and later. But I cannot say when it started. Now in a moment of despair I tried something very unorthodox: I copied udevadm from Bionic to the Eoan image and ran the tests again. Look and behold, all pass. ** No longer affects: linux-azure

[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd

I can confirm as well, 237-3ubuntu10.25 fixes the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart of

[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd

This bug also affects my company. Please integrate the fix soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart o

[Touch-packages] [Bug 1785063] Re: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

Also affects me. I attached the alsa-info.txt created by Alsainfo: https://wiki.ubuntu.com/Audio/AlsaInfo ** Attachment added: "alsa-info.txt.dbLPPYkDup" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1785063/+attachment/5257861/+files/alsa-info.txt.dbLPPYkDup -- You received thi

[Touch-packages] [Bug 1822270] [NEW] Debconf readline frontend does not show options

Public bug reported: AFFECTED RELEASE: Bionic PACKAGE VERSION: debconf - 1.5.66 DESCRIPTION: When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so de

[Touch-packages] [Bug 1804417] Re: runuser doesn't authenticate PAM modules

As a workaround we now use the following configuration as the maintainer suggested to us: # cat /etc/pam.d/runuser #%PAM-1.0 authsufficient pam_rootok.so session requiredpam_localuser.so Which works as well: # runuser domainuser runuser: cannot open session: Permi

[Touch-packages] [Bug 1804417] [NEW] runuser doesn't authenticate PAM modules

Public bug reported: We use the pam_localuser.so PAM module to authenticate only local users for root to become. Because we don't want that root can become a domain user (as we use sssd with ad integration). This works well with the su program, but fails with runuser. We added the following in

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

For me it works after installing apt 1.2.9 and libapt-pkg5.0_1.2.29_amd64.deb When i now run apt update && apt upgrade, it tells me that libapt-pkg5.0 was kept back. If i now run apt install -f it will install libapt-pkg5.0:amd64 (1.5.1) -- You received this bug notification because you are a m

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

The problem occured after upgrading to: libapt-pkg5.0:amd64 (1.5.1) apt (1.2.29) It works well wit apt 1.2.10 and libapt 1.2.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1

[Touch-packages] [Bug 1782951] [NEW] package policykit-1 0.105-20 failed to install/upgrade: new policykit-1 package pre-installation script subprocess returned error exit status 1

Public bug reported: I am new to ubuntu so i have no idea whats going on ProblemType: Package DistroRelease: Ubuntu 18.04 Package: policykit-1 0.105-20 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0u

[Touch-packages] [Bug 1781852] [NEW] package libgconf-2-4:amd64 3.2.6-4ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Public bug reported: I don know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgconf-2-4:amd64 3.2.6-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 15 16:49:3

[Touch-packages] [Bug 1779658] [NEW] Dropping to shell twice crashes system

Public bug reported: If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and repeat once more: Expected result: - Normal functioning X session Real result: - No interaction with the system possible anymore. Pro

[Touch-packages] [Bug 1760824] [NEW] mlx4 modprobe dep not needed by default

Public bug reported: My machine: Ubuntu 16.04.4 Xenial 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Changes were made in bug [1] to fix an issue where mlx4_en was not loaded. The following change was added: cat /etc/modprobe.d/mlx4.conf # mlx4_co

[Touch-packages] [Bug 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

Must have had a brain freeze or something, I rebuild my initramfs with belo and it worked after boot. update-initramfs -k `uname -r` -c The point that the default /etc/modprobe.d/mlx4.conf should be removed still stands, I'll report a new bug to kmod I guess. -- You received this bug notificati

[Touch-packages] [Bug 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

Ping, this migt be causing issue when using the mlx4 driver today. Ubuntu 16.04 Xenial 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux The following file is no longer needed, mlx4_core and mlx4_en will be loaded properly automatic cat /etc/modprobe.

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

We are also affected by this suddenly after systemd upgrade the network was gone, had to go in via serial console. We are only using networkd because Martin Pitt said in the run-up to the 16.04 release that networkd would be supported and to be used in the next LTS release. # networkctl IDX LINK

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

We got hit by this as well. Some Ceph nodes lost all networking. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan

[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

Confirming the fix. Thanks! Before: Sep 19 18:10:39 s1264 systemd-networkd[28308]: [/etc/systemd/network/eth0.network:18] Interface label is not valid or too long, ignoring assignment: eth0:1 Sep 19 18:10:39 s1264 systemd-networkd[28308]: Enumeration completed Sep 19 18:10:39 s1264 systemd-netw

[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

** Summary changed: - Xenial: Please merge upstream fix for networkd to "accept colons in network interface names" + Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names" -- You received this bug notification because you are a member of Ubuntu Tou

[Touch-packages] [Bug 1714933] [NEW] Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"

Public bug reported: PR: https://github.com/systemd/systemd/pull/5117 issue: https://github.com/systemd/systemd/issues/4057 Before the networkd from 231 was backported, it was possible to use interface alias names that contained a colon, e.g. eth0:1. This is commonly used to make legacy tools li

[Touch-packages] [Bug 1714531] [NEW] package libssl1.0.0 1.0.2g-1ubuntu11.2 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libssl1.0.0/changelog.Debian.gz« zu überschreiben, w

Public bug reported: Not sure what happened ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl1.0.0 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Sep

[Touch-packages] [Bug 1700472] [NEW] resolvconf cause nss_ldap connection failures while booting

Public bug reported: Ubuntu 16.04.2 LTS resolvconf: 1.78ubuntu4 If the server is configured to use a remote ldap during boot a bunch of this messages appears: sh nss_ldap: could not connect to any LDAP server as [..] - Can't contact LDAP server This appears to be cause by /sbin/resolv

[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

Confirm that as well with clean install of Ubuntu gnome 17.04 yesterday, but maybe can give little support... Before I decided to install I tried via Live-USB Stick and also connected to my google account. Worked like a charm! Login-Screen that opened from Google was the old one! After I install

[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"

I think i have a specification to this issue. First, my system with the same problem at shutdown/reboot, but only in a very special case: Fresh install of Ubuntu Server 16.04.2 LTS CPU: Intel Xeon E3-1245v6 (Kabylake) Mainboard: MSI C236A Workstation/Server Mainboard (model: 7998-012R; latest BI

[Touch-packages] [Bug 1676527] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück

*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 Public bug reported: no clue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-42.45~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

Thanks for bricking our servers: http://i.imgur.com/DFFrSs1.png This fixes it: cat /etc/systemd/system/systemd-networkd.service.d/override.conf [Unit] After=dbus.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syst

[Touch-packages] [Bug 1645257] [NEW] bluetoothd does not notice udev-induced device name change

Public bug reported: Cheers, using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using Bluetooth NAP functionality to connect a device via the system's network connect fails because udev renames the device when it is registered and bluetoothd fails to realize that: Nov 28 10:26:21 fenrir ke

[Touch-packages] [Bug 1216947] Re: cron.daily/standard reports /tmp/lost+found missing

@racb yes, the lost+found checking was removed in cron 3.0pl1-123, but the latest available in precise is 3.0pl1-120: http://packages.ubuntu.com/precise-updates/cron Can we get a newer version out in precise please? -- You received this bug notification because you are a member of Ubuntu Touch s

[Touch-packages] [Bug 1281700] Re: policykit-1 is not aware of groups assigned by pam_group

I am affected by this as well. I want my LDAP users to be able to manage printers. I've tried removing authentication in cupsd.conf, this works for the CUPS interface. But not from 'Printers' in system settings. So instead I've added them to the lpadmin group with the pam mount module, but it is st

[Touch-packages] [Bug 1528668] Re: [regression] Qt.application.active not working correctly

For me, it seems the problem is still there in OTA-9. I reported this bug: https://bugs.launchpad.net/ubuntu-ux/+bug/1512327 which was marked as a duplicate for this one. Since the status is "Fix Released" I was wondering if the fix was released in OTA-9. My System is the following: (I will t

[Touch-packages] [Bug 1527187] [NEW] Unable to hang up outgoing call

Public bug reported: When I make an outgoing call, I am unable to hang up. I can do so only by changing to another app and then return to the dialer-ap. Step to reproduce: 1.) Open the dialer-app 2.) Start an outgoing call 3.) Try to hang up by pushing the hang-up button Then the hang-up button

[Touch-packages] [Bug 1523274] [NEW] nvidia-settings: Couldn't connect to accessibility bus

essibility bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused I am running Xubuntu 15.10 which is an upgraded installation from 15.04 which again is an upgraded installation from 14.10. I hope that's not the root of my problem. Thanks in advance for any help! Greetings

[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

(still) present on Ubuntu 14.04.3 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1266675 Title: newusers error adding more than one user Status in shadow package in Ub

[Touch-packages] [Bug 1501310] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

Thanks, it works just fine with the new 1.0.7-0ubuntu0.6 Best regards Tobias -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1501310 Title: Unable to start containers after

[Touch-packages] [Bug 1501310] [NEW] Unable to start containers after upgrade to 1.0.7-0ubuntu0.5 on trusty

ed to spawn 'blixten' lxc-start: lxc_start.c: main: 342 The container failed to start. lxc-start: lxc_start.c: main: 346 Additional information can be obtained by setting the --logfile and --logpriority options. I had to revert to the older version of LXC to get the containers

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

ok, will you report when they are available on the debs? then i'll redo the backtrace with compiz debug symbols. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1470097 Title:

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

hmm. sorry. no debug symbols for compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 available for vivid. since recompiling compiz on the affected machine will remove the illegal instruction i cannot help you on this any further. -- You received this bug notification because you are a member of Ubuntu T

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

sorry, I forgot to look at the pool. none of them is in the ddebs sorted to dist vivid. fyi the only compiz debug symbol in the debs is compizconfig-backend-kconfig-dbgsym from http://ddebs.ubuntu.com/dists/vivid/universe/binary-amd64/Packages -- You received this bug notification because you

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

ok, found and installed the unity-dbgsym and libnux-4.0-0-dbgsym but that does not change the backtrace, so I assume it's a compiz bug. I followed https://wiki.ubuntu.com/DebuggingCompiz. There they say to install compiz-core-dbgsym compiz-plugins-dbgsym compiz-fusion-plugins-main-dbgsym compiz-

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

>From the added backtrace we get that pextrd is the illegal instruction and therefore schouldnt be used. hmm, I'll try again with installed unity-dbgsym. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https:

[Touch-packages] [Bug 893210]

Created attachment 118207 attachment-25654-0.html Just for the record, the reporter (me) doesn't have access to that PC anymore. On 11 Sep 2015 05:57, wrote: > *Comment # 13 on > bug 42353

[Touch-packages] [Bug 1078704]

Created attachment 118207 attachment-25654-0.html Just for the record, the reporter (me) doesn't have access to that PC anymore. On 11 Sep 2015 05:57, wrote: > *Comment # 13 on > bug 42353

[Touch-packages] [Bug 1470097] Re: Unity does not support cpus without sse4

Bbacktrace of unity crashing due to illegal instruction. ** Attachment added: "Corresponding unity backtrace" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1470097/+attachment/4422445/+files/unity_backtrace.txt -- You received this bug notification because you are a member of Ubuntu T

[Touch-packages] [Bug 1470097] [NEW] Unity does not support cpus without sse4

Public bug reported: Unity uses sse4 instructions which are not available on older celeron or pentium cpus. The instruction being used causing unity to crash is PEXTRD In this case one cannot login into the default unity session. current workaround is to install gnome. ProblemType: Bug DistroR

[Touch-packages] [Bug 1467481] [NEW] Fails silently when no network present

Public bug reported: If no network connection is present and on the additional driver tab one selects a driver that needs to download packages, 'apply changes' fails, reverting to previous setting, without further comment. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: software-properties-

[Touch-packages] [Bug 1464980] Re: protoc can't find shared libaries

protoc works if I compile & install it from latest github source. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1464980 Title: protoc can't find shared libaries Status

[Touch-packages] [Bug 1464980] [NEW] protoc can't find shared libaries

Public bug reported: After a fresh install of the package protobuf-compiler I get the error: > protoc: error while loading shared libraries: libprotoc.so.10: cannot open > shared object file: No such file or directory. in my /usr/lib/x86_64-linux-gnu there is only a libprotoc.so.8 pointing to li

[Touch-packages] [Bug 1426358] [NEW] upgrade of whoopsie fails due to report_crashes=false

Public bug reported: Cheers, I'm using systemd and have set report_crashes=false in /etc/default/whoopsie. The systemctl service $ systemctl status whoopsie.service whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled) Active: fai

[Touch-packages] [Bug 1297302] Re: Orange squares around checkboxes and radio buttons

Just installed Ubuntu 14.10 and the problem is also in that version! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1297302 Title: Orange squares around checkboxes a

[Touch-packages] [Bug 1333554] Re: Translation mistake in watch -n 30 : German

** Changed in: procps (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1333554 Title: Translation mistake in watch -n 30 : Ge

[Touch-packages] [Bug 1297302] Re: Orange squares around checkboxes and radio buttons

I am also affected by this bug. I am currently working on a GTK application which makes testing the GUI very annoying. Thanks to all the people who are fixing this. ** Attachment added: "radio button display error.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1297302/+attac

[Touch-packages] [Bug 1343020] Re: Realtek ALC889A No sound output

ic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tobias 1922 F pulseaudio tobias14404 F pulseaudi

[Touch-packages] [Bug 1343020] Re: Realtek ALC889A No sound output

Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tobias 1922 F pulseaudio tobias14404 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 17 01:29:33 2014 InstallationDate: Installed on 2014-07-16 (0 days ago)

[Touch-packages] [Bug 1343020] [NEW] Realtek ALC889A No sound output

g-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tobias 1922 F