[Touch-packages] [Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"
@Dmitry I have tried your workaround from #2, but step 8. (the second hibernate) fails for me with a "Not enough swap space" error message. On my setup I'm using a swapfile on a Btrfs formatted Logical Volume. This worked fine in regards of hibernating on Kubuntu 23.10. -- 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/2057687 Title: systemctl hibernate error: "Call to Hibernate failed: Invalid argument" Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd to 255(255.2-3ubuntu2) hibernate stopped working. Trying to hibernate: systemctl hibernate I get: Call to Hibernate failed: Invalid argument systemctl status systemd-hibernate.service - × systemd-hibernate.service - Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: failed (Result: exit-code) since Tue 2024-03-12 18:48:12 MSK; 1min 33s ago Docs: man:systemd-hibernate.service(8) Process: 4473 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE) Main PID: 4473 (code=exited, status=1/FAILURE) CPU: 5ms мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Starting systemd-hibernate.service - Hibernate... мар 12 18:48:12 ASUSPRO-P3540FA systemd-sleep[4473]: Failed to find location to hibernate to: Invalid argument мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'. мар 12 18:48:12 ASUSPRO-P3540FA systemd[1]: Failed to start systemd-hibernate.service - Hibernate. -- Previous version (254.x) worked: swapfile(on EXT4 fs) is used to hibernate/resume, resume with resume_offset kernel parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2057687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063815] [NEW] No microphone available
Public bug reported: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2063815 Title: No microphone available Status in alsa-driver package in Ubuntu: New Bug description: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2063815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767172] Re: Regression: /etc/modules checked against blacklist or it's really hard to load blacklisted watchdog modules when one really wants one
> I think it's fine. It sounds like there will just be no way to
override package-installed blacklists any more. That's unfortunate, but
it's a very rare situation.
The i6300esb watchdog driver is required for every KVM/qemu virtual
machine with an emulated watchdog
(https://wiki.openstack.org/wiki/LibvirtWatchdog).
Having no easy option to enable that module for virtual machines is a
blocker for having them reset when stuck.
See the following issues to:
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642930
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948040
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009350
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837
** Bug watch added: Debian Bug tracker #1009350
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009350
--
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/1767172
Title:
Regression: /etc/modules checked against blacklist or it's really hard
to load blacklisted watchdog modules when one really wants one
Status in linux package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
Impossible / hard to force the system to load a watchdog module
because it is blacklisted by the kernel auto-generated list of
"watchdog" modules.
/etc/modules used to "just work" before.
e.g. bcm2835_wdt module on arm64
===
Before systemd-modules-load, /etc/init.d/kmod would load modules
directly with "modprobe" (and _not_ "modprobe -b"):
load_module() {
local module args
module="$1"
args="$2"
if [ "$VERBOSE" != no ]; then
log_action_msg "Loading kernel module $module"
modprobe $module $args || true
else
modprobe $module $args > /dev/null 2>&1 || true
fi
}
However, under 18.04, systemd-modules-load will _ignore_ modules that
are manually listed in /etc/modules and process them with the
blacklist (the same as "modprobe -b" would). This means that it is not
possible to manually load modules that are blacklisted (like watchdog
modules):
systemd-238/src/modules-load/modules-load.c:
static int load_module(struct kmod_ctx *ctx, const char *m) {
const int probe_flags = KMOD_PROBE_APPLY_BLACKLIST;
...
default:
err = kmod_module_probe_insert_module(mod,
probe_flags,
NULL, NULL,
NULL, NULL);
if (err == 0)
log_info("Inserted module '%s'",
kmod_module_get_name(mod));
else if (err == KMOD_PROBE_APPLY_BLACKLIST)
log_info("Module '%s' is blacklisted",
kmod_module_get_name(mod));
Blacklists should _not_ be applied by systemd-modules-load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2049630] [NEW] [LE-Beats Studio Pro tilhørende j, playback] Playback problem
Public bug reported: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no problem switching to and from off and a2dp_sink but I can no longer get to the handsfree_head_unit. journalctl -b -f gives the follwing error message when trying to activate the handsfree_head_unit profile: myleno pulseaudio[405145]: Refused to switch profile to handsfree_head_unit: Not connected cut/paste of pacmd command: list-cards: .. . . index: 2 name: driver: owner module: 24 properties: device.description = "Beats Studio Pro tilhørende jan" device.string = "A4:16:C0:63:87:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headphone" bluez.path = "/org/bluez/hci0/dev_A4_16_C0_63_87_DD" bluez.class = "0x240418" bluez.alias = "Beats Studio Pro tilhørende jan" device.icon_name = "audio-headphones-bluetooth" bluetooth.codec = "sbc_xq_453" profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: sinks: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink/#1: Beats Studio Pro tilhørende jan sources: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink.monitor/#2: Monitor of Beats Studio Pro tilhørende jan ports: headphone-output: Headphone (priority 0, latency offset 10 usec, available: unknown) properties: headphone-input: Bluetooth Input (priority 0, latency offset 0 usec, available: no) properties: >>> set-card-profile 2 handsfree_head_unit Failed to set card profile to 'handsfree_head_unit'. >>> set-card-profile 2 a2dp_sink >>> set-card-profile 2 off >>> set-card-profile 2 a2dp_sink ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jan2314 F pulseaudio /dev/snd/controlC0: jan2314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Jan 17 14:58:03 2024 InstallationDate: Installed on 2022-12-08 (404 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: LE-Beats Studio Pro tilhørende j Symptom_Type: Only some of outputs are working Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2022 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76465WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 17ALC6 dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrGLCN46WW:bd03/23/2022:br1.46:efr1.46:svnLENOVO:pn82KV:pvrIdeaPad317ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrIdeaPad317ALC6:skuLENOVO_MT_82KV_BU_idea_FM_IdeaPad317ALC6: dmi.product.family: IdeaPad 3 17ALC6 dmi.product.name: 82KV dmi.product.sku: LENOVO_MT_82KV_BU_idea_FM_IdeaPad 3 17ALC6 dmi.product.version: IdeaPad 3 17ALC6 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2049630 Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no pr
[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 ** Also affects: initramfs-tools Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1970402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028124] [NEW] apt dist-upgrade does not restart package qemu-guest-agent
Public bug reported: When my system Ubuntu 22.04.2 LTS performs apt dist-upgrade (manually or from unattended upgrades) and there is an upadte on package qemu-guest-agent, the agent gets stopped, updated, but is not started. I observed this behaviour on two machines with same result. After I run the apt I see this in syslog, no errors: Jul 19 07:04:02 micro systemd[1]: Stopping QEMU Guest Agent... Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Deactivated successfully. Jul 19 07:04:02 micro systemd[1]: Stopped QEMU Guest Agent. Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Consumed 31min 49.962s CPU time. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/2028124 Title: apt dist-upgrade does not restart package qemu-guest-agent Status in apt package in Ubuntu: New Bug description: When my system Ubuntu 22.04.2 LTS performs apt dist-upgrade (manually or from unattended upgrades) and there is an upadte on package qemu-guest-agent, the agent gets stopped, updated, but is not started. I observed this behaviour on two machines with same result. After I run the apt I see this in syslog, no errors: Jul 19 07:04:02 micro systemd[1]: Stopping QEMU Guest Agent... Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Deactivated successfully. Jul 19 07:04:02 micro systemd[1]: Stopped QEMU Guest Agent. Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Consumed 31min 49.962s CPU time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2028124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004179] Re: neutron-linuxbridge-agent flat network incompatibility with systemd-networkd
> > The fix was revered in bug #1929560, but the behavior will not be reverted > > in newer releases. Therefore, every reload of systemd-networkd will remove > > the physical network interface from neutrons bridge. > > It looks like the patch was backported to stable releases in that bug; not > reverted. Are you saying that that patch is wrong? Or that you want that > behavior still? Looking at the upstream code quickly, things have changed > quite a bit so I am not sure what the current behavior is. Please see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929560/comments/15. > It sounds like a support site would be more appropriate Dan requested these details here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1929560/comments/13 > Also what release are you running? Since the initial report, we upgraded from 18.04 to 20.04. -- We continued to investigate for a solution, and systemd added a KeepMaster= option in v250 (https://github.com/systemd/systemd/commit/57aef9d7373c97d04beb6c5fc268496c3fdcf0a4). Unfortunately, Ubuntu 22.04 only includes systemd v249. Would it be possible to have https://github.com/systemd/systemd/commit/57aef9d7373c97d04beb6c5fc268496c3fdcf0a4 backported to Ubuntu 22.04? -- 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/2004179 Title: neutron-linuxbridge-agent flat network incompatibility with systemd- networkd Status in systemd package in Ubuntu: Incomplete Bug description: We are running an OpenStack installation from Ubuntu's Cloud Archive, and our computer hosts have their network configured with systemd- networkd. For example, a bond and several VLANs on top, including two VLANs used for OpenStack flat networks. We are using neutron- linuxbridge-agent, i.e. no OVS or OVN. Network interface overview: ┌──┐ ┌──┐ ┌──┐ │ eno2 │ │ eno3 │ │ eno4 │ └───┬──┘ └───┬──┘ └───┬──┘ │││ ┌───┴┴┴──┐ │ bond0 │ └─┬───┬─┬┘ │ │ │ ┌───┴──┐ ┌──┴───┐ ┌───┴┐ │ tnet │ │ stor │ │ public │ └──┘ └──┘ └┘ The "public" network is a flat provider network (VLAN) that shall be used by neutron-linuxbridge-agent and nova-compute to attach to virtual machines. "tnet" is used for VXLAN overlay networks, and "stor" for Ceph. The issue is with "public" only. The systemd-networkd configuration sets up all interfaces. We previously used netplan, but missing some needed options. It does use systemd-networkd too, so no relevant change to the problem. Since merging https://github.com/systemd/systemd/pull/17392, systemd- network will remove the master flag from the "public" interface, that neutron-linuxbridge-agent assigned to the bridge for the network, e.g. brq88363244-5f, breaking all network on the flat network. The fix was revered in bug #1929560, but the behavior will not be reverted in newer releases. Therefore, every reload of systemd- networkd will remove the physical network interface from neutrons bridge. Using "bridge_mappings" with nova-compute has never been finished, according to bug #1105488. nova-compute always requires the dynamic bridge, e.g. brq88363244-5f, to be present. @ddstreet asked for a new bug and the network configuration: # /etc/systemd/network/10-eno1.network: [..] # /etc/systemd/network/10-eno2.network: [Match] Name=eno2 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-eno3.network: [Match] Name=eno3 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-eno4.network: [Match] Name=eno4 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-bond0.netdev: [NetDev] Name=bond0 Kind=bond MTUBytes=9000 [Bond] Mode=802.3ad LACPTransmitRate=fast MIIMonitorSec=100ms TransmitHashPolicy=layer3+4 # /etc/systemd/network/10-bond0.network: [Match] Name=bond0 [Link] MTUBytes=9000 [Network] LinkLocalAddressing=no ConfigureWithoutCarrier=yes VLAN=tnet VLAN=stor VLAN=pulic # /etc/systemd/network/10-public.netdev: [NetDev] Name=public Kind=vlan MTUBytes=1500 [VLAN] Id=82 # /etc/systemd/network/10-public.network: [Match] Name=public [Link] MTUBytes=1500 [Network] LinkLocalAddressing=no ConfigureWithoutCarrier=yes # /etc/systemd/network/10-tnet.netdev: [..] # /etc/systemd/network/10-tnet.network: [..] # /etc/systemd/network/10-stor.netdev: [..] # /etc/sys
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian, @Konrad, Ubuntu 22.04 has this fixed. It was fixed in PulseAudio 15, run `pulseaudio --version` to see the version you are running. But HSP sound is still much worse than A2DP sound e.g. if you listen to music. HSP is still mono and limited to a bandwidth of 8 kHz. The scope of this bug was only to support WBS in the Linux stack, so improve HSP sound from even more terrible 4 kHz bandwidth to what it is now. The current limitations are with the Bluetooth specification and the limited data rates that bluetooth offers, so PipeWire is not going to help with that. If you want better two-way sound your options currently are using a wire, or using a proprietary wireless transmission (search for gaming headsets) or Bluetooth codec (there is the FastStream codec, but supporting headsets are extremely rare, I couldn't find anything with a proper mic that I would consider for video calls). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: pulseaudio (Ubuntu) => ddeb-retriever -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2008469 Title: ubuntu jammy debug mirror out of sync Status in ddeb-retriever: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ddeb-retriever/+bug/2008469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: ubuntu-keyring (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2008469 Title: ubuntu jammy debug mirror out of sync Status in pulseaudio package in Ubuntu: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008469] [NEW] ubuntu jammy debug mirror out of sync
Public bug reported: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2-signed (Ubuntu) => ubuntu-keyring (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2008469 Title: ubuntu jammy debug mirror out of sync Status in ubuntu-keyring package in Ubuntu: New Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/2008469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist
What @fargiolas wrote, solved this issue for me on 20.04. Configure watchdog module in /etc/defaults/watchdog The watchdog service loads the module itself on demand. You don't have to load the module yourself then. Seems that the issue can be closed now. -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004179] [NEW] neutron-linuxbridge-agent flat network incompatibility with systemd-networkd
Public bug reported: We are running an OpenStack installation from Ubuntu's Cloud Archive, and our computer hosts have their network configured with systemd- networkd. For example, a bond and several VLANs on top, including two VLANs used for OpenStack flat networks. We are using neutron- linuxbridge-agent, i.e. no OVS or OVN. Network interface overview: ┌──┐ ┌──┐ ┌──┐ │ eno2 │ │ eno3 │ │ eno4 │ └───┬──┘ └───┬──┘ └───┬──┘ │││ ┌───┴┴┴──┐ │ bond0 │ └─┬───┬─┬┘ │ │ │ ┌───┴──┐ ┌──┴───┐ ┌───┴┐ │ tnet │ │ stor │ │ public │ └──┘ └──┘ └┘ The "public" network is a flat provider network (VLAN) that shall be used by neutron-linuxbridge-agent and nova-compute to attach to virtual machines. "tnet" is used for VXLAN overlay networks, and "stor" for Ceph. The issue is with "public" only. The systemd-networkd configuration sets up all interfaces. We previously used netplan, but missing some needed options. It does use systemd- networkd too, so no relevant change to the problem. Since merging https://github.com/systemd/systemd/pull/17392, systemd- network will remove the master flag from the "public" interface, that neutron-linuxbridge-agent assigned to the bridge for the network, e.g. brq88363244-5f, breaking all network on the flat network. The fix was revered in bug #1929560, but the behavior will not be reverted in newer releases. Therefore, every reload of systemd-networkd will remove the physical network interface from neutrons bridge. Using "bridge_mappings" with nova-compute has never been finished, according to bug #1105488. nova-compute always requires the dynamic bridge, e.g. brq88363244-5f, to be present. @ddstreet asked for a new bug and the network configuration: # /etc/systemd/network/10-eno1.network: [..] # /etc/systemd/network/10-eno2.network: [Match] Name=eno2 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-eno3.network: [Match] Name=eno3 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-eno4.network: [Match] Name=eno4 [Network] LinkLocalAddressing=no Bond=bond0 # /etc/systemd/network/10-bond0.netdev: [NetDev] Name=bond0 Kind=bond MTUBytes=9000 [Bond] Mode=802.3ad LACPTransmitRate=fast MIIMonitorSec=100ms TransmitHashPolicy=layer3+4 # /etc/systemd/network/10-bond0.network: [Match] Name=bond0 [Link] MTUBytes=9000 [Network] LinkLocalAddressing=no ConfigureWithoutCarrier=yes VLAN=tnet VLAN=stor VLAN=pulic # /etc/systemd/network/10-public.netdev: [NetDev] Name=public Kind=vlan MTUBytes=1500 [VLAN] Id=82 # /etc/systemd/network/10-public.network: [Match] Name=public [Link] MTUBytes=1500 [Network] LinkLocalAddressing=no ConfigureWithoutCarrier=yes # /etc/systemd/network/10-tnet.netdev: [..] # /etc/systemd/network/10-tnet.network: [..] # /etc/systemd/network/10-stor.netdev: [..] # /etc/systemd/network/10-stor.network: [..] neutron-linuxbridge-agent is configured to use "public" as a flat network, e.g.: # /etc/neutron/plugins/ml2/linuxbridge_agent.ini [linux_bridge] physical_interface_mappings = public:public [..] When everything is started and a VM needs to be connected to the flat network, neutron-linuxbridge-agent creates a dynamic bridge for nova-compute, e.g. brq88363244-5f: 14: public@bond0: mtu 1500 master brqe240c66b-da state UP 59: brqe240c66b-da: mtu 1500 state UP When systemd-networkd is restarted, it will see that "public" is up but has a master assigned. It will be unassigned and break the flat network: 14: public@bond0: mtu 1500 state UP 59: brqe240c66b-da: mtu 1500 state UP What would be the recommended why to configure networking on compute hosts with Ubuntu OpenStack and flat networks? Not using systemd- networkd or netplan at all, but only /etc/network/interfaces? Is there any modern alternative? ** Affects: systemd (Ubuntu) Importance: Undecided Status: 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/2004179 Title: neutron-linuxbridge-agent flat network incompatibility with systemd- networkd Status in systemd package in Ubuntu: New Bug description: We are running an OpenStack installation from Ubuntu's Cloud Archive, and our computer hosts have their network configured with systemd- networkd. For example, a bond and several VLANs on top, including two VLANs used for OpenStack flat networks. We are using neutron- linuxbridge-agent, i.e. no OVS or OVN. Network interface overview: ┌
[Touch-packages] [Bug 1937117] Re: misconfigured networkd may break after networkd restart
> Note that the *proper* way to place eth0 into a bridge while also being under systemd-networkd management is to create a .netdev for the bridge and assign eth0 to it. What is the recommended way for Ubuntu's OpenStack offering that dynamically creates bridges (neutron-linuxbridge-agent)? Not using systemd-network at all, never? -- 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/1937117 Title: misconfigured networkd may break after networkd restart Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] bug 1929560 fixed an error in setting/clearing an interface 'master' during systemd-networkd startup if the interface was already up, however for any users who have been relying on that bug to manually set an interface 'master' for an interface that's otherwise controlled by systemd-networkd, this will break their system by removing the interface from the 'master' on a systemd-networkd restart. For example, if a user has interface 'eth0' configured to be controlled by systemd-networkd, but then manually does 'ip l set dev eth0 master br0' to add it to the 'br0' bridge, previous behavior would leave 'eth0' in the bridge after a systemd-networkd restart, even though it should not be in the bridge based on the systemd- networkd configuration. The new behavior matches systemd-networkd behavior for all other aspects (i.e. networkd removes all addresses, routes, and other settings it doesn't know about or that are different from its configuration), however it breaks users expecting the previous incorrect behavior. [test case] configure systemd-networkd to control an interface that isn't set with any 'master', and start networkd. For example, an instance configured for DHCP. After networkd has started, manually set the interface 'master' to an existing bridge. Restart networkd, and check if the interface still has the bridge 'master' or not. e.g., in a newly created cloud-image container, with normal netplan, check the networkd control of eth0: root@lp1937117-f:~# networkctl list eth0 IDX LINK TYPE OPERATIONAL SETUP 159 eth0 ether routableconfigured create a new bridge and manually place eth0 into it: root@lp1937117-f:~# ip l add dev br0 type bridge root@lp1937117-f:~# ip l set up dev br0 root@lp1937117-f:~# ip l set dev eth0 master br0 root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 now restart systemd-networkd, and check if eth0 remains under br0: root@lp1937117-f:~# systemctl restart systemd-networkd root@lp1937117-f:~# ip l show dev eth0 159: eth0@if160: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:56:f8:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] the main potential is for problems for those with misconfigured systems, relying on specific previous incorrect behavior, specifically interfaces controlled by systemd-networkd in part, but also with manual configuration performed outside of systemd-networkd configuration. [scope] this is needed for bionic and focal to restore the previous incorrect behavior; the correct behavior should remain in impish, and (arguably) should remain in hirsute as well [other info] see bug 1929560 for details of the original bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
Just for completeness, apt-cacher version 3.7.4-1build1 on a Ubuntu 22.04 system. -- 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/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
Hmm, I did find what was causing it. I had a proxy configured for apt pointing at apt-cacher-ng on a local system. When I removed the proxy from the configuration, apt had no issues downloading lists. -- 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/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
The workaround of Heinrich, above, does not resolve the issue for me. -- 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/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
One more log. I also test different upstream DNS server (hetzner.de; Google DNS) but I'm not sure what is wrong here. ** Attachment added: "systemd-resolved.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+attachment/5604817/+files/systemd-resolved.txt -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
Debug log of systemd-networkd Shell script to reproduce it: curl https://raw.githubusercontent.com/opendns/public-domain-lists/master/opendns-random-domains.txt -O curl https://raw.githubusercontent.com/opendns/public-domain-lists/master/opendns-top-domains.txt -L >> opendns-random-domains.txt for i in $(cat opendns-random-domains.txt); do sleep 1; dig +short +dnssec $i @127.0.0.53; done Logs are from 20:00:00 to 00:07:55. Error appeared on 00:07:53. The error comes from kinetic lxd container again, while the jammy lxd still running. Upstream DNS Server is dnsmasq (from LXD). -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : htt
[Touch-packages] [Bug 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
** Attachment added: "systemd-resolved.log.gz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+attachment/5604656/+files/systemd-resolved.log.gz -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
Thanks for your answer. In mean time, I setup 2 additional lxd containers, one running jammy, one running kinetic and I'm hit the error again on kinetic by running dig +dnssec on random DNS names in a loop I follow your instructions, but I used `Environment=SYSTEMD_LOG_LEVEL=debug` to gain log messages. -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
I'm able to assist here, e.g. by enable debugging logs. I need some instructions what I should setup and have to provide here. -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981431] [NEW] systemd-resolved: DNSSEC validation failed: incompatible-server
Public bug reported: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd-resolved ** Description changed: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation
[Touch-packages] [Bug 1979137] [NEW] BT headset - microphone not working
Public bug reported: Hi The BT microphones is not working in Ubuntu / pulseaudio . Have tried several BT headset and none is working in Ubuntu. The Ubuntu guys ask me to open a case here (the case ID from Ubuntu is: 00338011 but here is a summery - I have never had a single one working. The one I have at my hand is * JLab GO Work It is connecting and shows up in the sound settings for the output - and give s sound out but not for the input. I have ad several Jabra from work also not working regarding the microphone. And before - and now - I have a BT set from Sony. Also not working regarding the microphone. All above are working at the Android phones, tables *and* Microsoft systems >From Ubuntu support I did various tests and discussed the problem with the OEM team. Here is a quick summary: - We don't have a list of supported Bluetooth headsets. The main problem here is that only a very limited number of vendors publish their source code and this makes it very difficult to have a compatibility list - The OEM team suggests opening a bug on launchpad for PulseAudio in order to leverage the community support. You can do this by using the link at [1] - The OEM team tested only with one model which is "Lenovo HE05" and it works (I'm waiting for an official confirmation for this. I cannot guarantee!) - During the last few days, I did some tests on my laptop (Dell XPS 15 9500). Actually, I'm using "JBL T450BT" and it works but, if I enable the built-in microphone, the audio quality switches to mono instead of stereo. Another test I did, is to use Pipewire instead of PulseAudio, which will be adopted (presumably) in Ubuntu 22.10 as the default but nothing changes in my own setup. Still, mono instead of stereo when enabling the microphone (If interested you can try to switch to Pipewire on Focal using the link at [2] (note that this is not an official guide and should be used as a reference only) .. .. This workarounds are not suitable for the general use and specific as we - at our firm has to use BT. Any ideas ? Best Jan ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1979137 Title: BT headset - microphone not working Status in pulseaudio package in Ubuntu: New Bug description: Hi The BT microphones is not working in Ubuntu / pulseaudio . Have tried several BT headset and none is working in Ubuntu. The Ubuntu guys ask me to open a case here (the case ID from Ubuntu is: 00338011 but here is a summery - I have never had a single one working. The one I have at my hand is * JLab GO Work It is connecting and shows up in the sound settings for the output - and give s sound out but not for the input. I have ad several Jabra from work also not working regarding the microphone. And before - and now - I have a BT set from Sony. Also not working regarding the microphone. All above are working at the Android phones, tables *and* Microsoft systems From Ubuntu support I did various tests and discussed the problem with the OEM team. Here is a quick summary: - We don't have a list of supported Bluetooth headsets. The main problem here is that only a very limited number of vendors publish their source code and this makes it very difficult to have a compatibility list - The OEM team suggests opening a bug on launchpad for PulseAudio in order to leverage the community support. You can do this by using the link at [1] - The OEM team tested only with one model which is "Lenovo HE05" and it works (I'm waiting for an official confirmation for this. I cannot guarantee!) - During the last few days, I did some tests on my laptop (Dell XPS 15 9500). Actually, I'm using "JBL T450BT" and it works but, if I enable the built-in microphone, the audio quality switches to mono instead of stereo. Another test I did, is to use Pipewire instead of PulseAudio, which will be adopted (presumably) in Ubuntu 22.10 as the default but nothing changes in my own setup. Still, mono instead of stereo when enabling the microphone (If interested you can try to switch to Pipewire on Focal using the link at [2] (note that this is not an official guide and should be used as a reference only) .. .. This workarounds are not suitable for the general use and specific as we - at our firm has to use BT. Any ideas ? Best Jan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1979137/+subscr
[Touch-packages] [Bug 1971992] Re: openssl rmd160 digest broken
Thanks. Not really a bug thus, I need to provide rmd160 digests in some workflow. This is a work-around and a good reason to discuss the issue upstream. -- 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 openssl package in Ubuntu: Won't Fix Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971992] [NEW] openssl rmd160 digest broken
Public bug reported: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- 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 openssl package in Ubuntu: New Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
Can reproduce when booting kubuntu-22.04-desktop-amd64.iso in Virtualbox and on my main installation of Kubuntu 22.04. Happens both on X11 and Wayland session. When I try to go to software-sources via Discover or Muon on the live image (where no user password is set), it simply doesn't launch. Terminal output of 'pkexec software-properties-qt': qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland- xcomposite-glx, xcb. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've also got an Avantree DG80 as a workaround and I can confirm it works with my Trekz OpenComm headset. It supports sounds up to 8 kHz (corresponding to mSBC with a 16 kHz sampling frequency) with the mic enabled, while anything connected directly to Linux bluetooth only goes up to 4 kHz in HSP/HFP mode (CVSD). The sound with mSBC is still noticeably worse than in A2DP mode when listening to music, but a lot better than CVSD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK I printed two files successfully with: jbm@curlew:~/test_set$ lp Truloc-211-Retainer.pdf request id is jbm-2810-314 (1 file(s)) jbm@curlew:~/test_set$ lp IMG_4737x.JPG request id is jbm-2810-315 (1 file(s)) The files are enclosed, together with the subsequent error_log. The Trulocpdf file should be the same one that failed whem sent from Document Viewer. On 2022-03-21 17:44, Till Kamppeter wrote: > I your error_log I have found the following: > > D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error- > document-format-error (client-error-document-format-error) > > This looks like that the printer was not able to work with the data it > received. > > The printer reports that it accepts PWG Raster as the only of the known > data formats used for driverless printing (it supports other formats, > too, but these are formats we cannot generate). Therefore we print in > PWG Raster format. > > It is possible that some printers have firmware bugs, not able to print > certain files in standard format. It is less probable that the PWG > Raster provided by us has problems as otherwise I would have received > many more bug reports. > > Now I need also CUPS error_log output from jobs which succeeded for you > and also I need the files which you have actually sent, both succeeding > and failing files. Could you attach these? > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "IMG_4737x.JPG" https://bugs.launchpad.net/bugs/1964095/+attachment/5571377/+files/IMG_4737x.JPG ** Attachment added: "Truloc-211-Retainer.pdf" https://bugs.launchpad.net/bugs/1964095/+attachment/5571378/+files/Truloc-211-Retainer.pdf ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571379/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK, that worked; file attached. On 2022-03-21 17:26, Till Kamppeter wrote: > Seems that your version of "driverless" is too old, not yet having the " > --std-ipp-uris" option (see also output of "driverless -h"). > > But I have found the URI you need in your error_log. Please run the > following command: > > ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer- > attributes.test > attrs.txt > > and attach attrs.txt. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "attrs.txt" https://bugs.launchpad.net/bugs/1964095/+attachment/5571360/+files/attrs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Tried the below, but it didn't work for me: jbm@curlew:~$ driverless --std-ipp-uris ERROR: Unable to create PPD file: Could not poll sufficient capability info from the printer (--std-ipp-uris, (null)) via IPP! On 2022-03-21 15:36, Till Kamppeter wrote: > Thanks for the files. > > For the "ipptool -tv ..." command do the following: > > Run > > driverless --std-ipp-uris > > You get an URI for your printer in standard IPP format. Please use that > URI for the "ipptool -tv ..." command of my comment above (comment #2) > and attach the attrs.txt here. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Hi Till Kamppeter. Thanks for looking into my bug report. I have replied via Launchpad, but wasn't able to confirm that I managed to attach the files you asked for, so I attach them here, too. --jan On 2022-03-20 17:54, Till Kamppeter wrote: > Could you also attach your file > > /etc/cups/ppd/EPSON_ET_2810_Series.ppd > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571317/+files/error_log ** Attachment added: "jbm-2810.ppd" https://bugs.launchpad.net/bugs/1964095/+attachment/5571318/+files/jbm-2810.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
In response to advice 2022_03_20: jbm@curlew:~/Desktop$ driverless ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ jbm@curlew:~/Desktop$ ipptool -tv ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ get-printer-attributes.test > attrs.test ipptool: Unable to connect to "EPSON ET-2810 Series._ipp._tcp.local" on port 631 - Name or service not known I suppose this might possibly have failed because I have assigned a new name to the printer after the debug report using: lpadmin -p jbm-2810 -v ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ - E -m driverless:ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ Since then I have had good experience printing pdf- and jpg-files from a terminal window using the lp command; printing e-mail and pdf-attachments from Thunderbird also works; printing pdf-files from Document Viewer and jpg-files from Image Viewer fails. jbm@curlew:~/Desktop$ cupsctl --debug-logging Attepted to print a file called "Truloc-211-Retainer.pdf" from Document Viewer to jbm-2810; it appears to be placed in the print queue and toleave the print queue but no print emerges from the printer. I have tried to attach the cups/error_log file and the jbm-2810.ppd file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964095] [NEW] print sent to Epson ET-2810 is not printed
Public bug reported: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: New Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.
[Touch-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!
Is there an official solution to this problem, meanwhile?
I ran into the same problem, but even after reinstalling python3-six,
python3-certifi, python3-requests, python3-idna, and python3-urllib3 I
still can't start software-properties-gtk, getting the message that the
name 'requests_unixsocket' is not defined.
Does anyone have an idea what to try next to get software-properties up
and running again?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
Expired
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
(In reply to Jan Rathmann from comment #15) > For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from > kubuntu-backports-ppa. Please disregard this comment - I totally forgot that I had installed a patched version of exiv2 (with the change described in Comment 4) to workaround the bug, sorry for causing confusion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from kubuntu-backports-ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
The following change in CVE-2021-37620-3.patch is responsible:
--- exiv2-0.27.3.orig/src/tags_int.cpp
+++ exiv2-0.27.3/src/tags_int.cpp
@@ -2865,7 +2865,7 @@ namespace Exiv2 {
}
std::string stringValue = value.toString();
-if (stringValue[19] == 'Z') {
+if (stringValue.at(19) == 'Z') {
stringValue = stringValue.substr(0, 19);
}
for (size_t i = 0; i < stringValue.length(); ++i) {
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
images exported by darktable
Status in Gwenview:
Unknown
Status in exiv2 package in Ubuntu:
New
Status in gwenview package in Ubuntu:
New
Bug description:
Since the recent security update of exiv2, Gwenview crashes when
trying to open image files that got exported by darktable.
Steps to reproduce:
* Make a test installation of Kubuntu 21.04 in VirtualBox
* Install all updates
* Install darktable
* Copy one of the images in /usr/share/wallpapers (or any other image) to
your home directory and open it with darktable
* Within darktable, export a copy of the image (no need to do any actual
modifications)
* Try to open that copy with Gwenview. Gwenview will crash.
I'm attaching a crash report hinting that this is related to exiv2.
Temporary workaround:
If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.
I don't know if the underlying cause is actually some bug in exiv2,
Gwenview or darktable.
Kind regards, Jan
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libexiv2-27 0.27.3-3ubuntu1.5
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Aug 26 15:16:47 2021
InstallationDate: Installed on 2021-08-26 (0 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: exiv2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Relevant terminal output from crash: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 108229 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
CVE-2021-37620-3.patch is responsible. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
** Also affects: gwenview (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752] [NEW] Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Public bug reported: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwenview Importance: Unknown Status: Unknown ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Crash report of Gwenview" https://bugs.launchpad.net/bugs/1941752/+attachment/5520895/+files/gwenview-20210826-153914.kcrash ** Bug watch added: KDE Bug Tracking System #441121 https://bugs.kde.org/show_bug.cgi?id=441121 ** Also affects: gwenview via https://bugs.kde.org/show_bug.cgi?id=441121 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929560] Re: link mac isn't set if already up
Thanks a lot for your work, Dan! Unfortunately, I wasn't able to pick up the new bug from here, sorry for that. (It appears I did not get any notification on your comments, need to check that) The bridges are managed by OpenStack Neutron from Ubuntu cloud archives and with names derived from the network UUID in the cluster database. It might work for a very limited set of bridges, if they do not set different options. AFAIK, OpenStack Neutron is still working on supporting using external bridges (https://bugs.launchpad.net/neutron/+bug/1105488). As we have bridges on VLANs on bonded interfaces (currently managed with systemd-networkd), I will see if I have to replace that all or if there is an option to just have systemd-networkd not set nomaster... Thanks! -- 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/1929560 Title: link mac isn't set if already up Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] if link is already up, configured mac isn't set this also affects the master/nomaster configuration [test case] create .network config for the link, for example: [Match] Name=eth0 [Link] MACAddress=00:16:3e:ff:ff:ff [Network] DHCP=yes make sure the link is already up, and restart systemd-networkd: root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 up root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 down root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:ff:ff:ff brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] any regression would likely result in incorrectly set link mac and/or master, or failure to correctly set mac and/or master [scope] this is needed for g and earlier this is fixed upstream by commit e16e4b3bedc57919b3ecb4096e941709a5d39b8a which is included in v247 so this is fixed already in h and later [other info] this moves the configuration of the link mac and master out of the link_up() function, so this also allows repeated calls to link_up() without reconfiguring the link mac and master. That behavior is useful for the commits for bug 1664844 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938682] [NEW] Flushing is not possible
Public bug reported: In the 5.5.0-1ubuntu1 version of Ubuntu 20.04.2 LTS it is not possible to flush any ip addresses. Test command (executed as root): ip a flush dev lo EOF on netlink Flush terminated Additional version info. ip -V ip utility, iproute2-ss200127 >From looking at a strace output it seems to me like the "dev" parameter is not passed to the correct function. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1938682 Title: Flushing is not possible Status in iproute2 package in Ubuntu: New Bug description: In the 5.5.0-1ubuntu1 version of Ubuntu 20.04.2 LTS it is not possible to flush any ip addresses. Test command (executed as root): ip a flush dev lo EOF on netlink Flush terminated Additional version info. ip -V ip utility, iproute2-ss200127 From looking at a strace output it seems to me like the "dev" parameter is not passed to the correct function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1938682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929560] Re: link mac isn't set if already up
This backport to 18.04 LTS broke all our OpenStack compute nodes. We use systemd-network to configure interfaces etc. and neutron-linuxbridge- agent with some flat networks. In this scenario, the neutron agent creates bridges for the flat networks and assigns them to physical interfaces based on a mapping. The backport now sets nomaster on these interfaces, effectively removing the bridges and cutting of connectivity of all VMs using these flat networks. This happened already when the systemd package was upgraded (and systemd-networkd restarted). Example: ``` 10: flat-net1@data: mtu 1500 qdisc noqueue master brq88363244-5f state UP group default qlen 1000 link/ether b0:22:28:1c:f7:12 brd ff:ff:ff:ff:ff:ff ``` The interface (VLAN here) is created and managed by systemd-networkd, the bridge `brq88363244-5f` is managed by neutron. Of course, systemd- networkd doesn't know anything about the bridge, this wasn't a problem until now, but the latest patch update always sets nomaster to `flat- net1`. We were really surprise by this change in 18.04 LTS. Is there any recommend workaround to have systemd-networkd not set nomaster or do we have to not use systemd-network at all? -- 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/1929560 Title: link mac isn't set if already up Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] if link is already up, configured mac isn't set this also affects the master/nomaster configuration [test case] create .network config for the link, for example: [Match] Name=eth0 [Link] MACAddress=00:16:3e:ff:ff:ff [Network] DHCP=yes make sure the link is already up, and restart systemd-networkd: root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 up root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# ip l set dev eth0 down root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0 root@test-f:/etc/systemd/network# systemctl restart systemd-networkd root@test-f:/etc/systemd/network# ip l show eth0 61: eth0@if62: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:ff:ff:ff brd ff:ff:ff:ff:ff:ff link-netnsid 0 [regression potential] any regression would likely result in incorrectly set link mac and/or master, or failure to correctly set mac and/or master [scope] this is needed for g and earlier this is fixed upstream by commit e16e4b3bedc57919b3ecb4096e941709a5d39b8a which is included in v247 so this is fixed already in h and later [other info] this moves the configuration of the link mac and master out of the link_up() function, so this also allows repeated calls to link_up() without reconfiguring the link mac and master. That behavior is useful for the commits for bug 1664844 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1929560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
i did a fresh install of 21.04, not an upgrade. the same problem. Doesn't seem to be upgrade related. -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930641] [NEW] memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Public bug reported: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.2.6-0ubuntu0.20.04.1 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 focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg package in Ubuntu: New Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zap
Re: [Touch-packages] [Bug 1928385] Re: The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. I kill the higher number PID from a getty, and then my sys
No, this bug was submitted from the GUI. By that point, I'd already killed the second systemd. You could say I have a chicken and egg problem. On Mon, May 17, 2021, 14:30 Dan Streetman <1928...@bugs.launchpad.net> wrote: > I don't see anywhere in your dmesg where systemd is 'running twice', you > probably should attach your boot/journal logs that show the problem. > > ** Changed in: systemd (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1928385 > > Title: > The systemd process runs twice, somehow preventing the system from > getting to proper GUI login screen. I kill the higher number PID from > a getty, and then my system boots properly. > > Status in systemd package in Ubuntu: > Incomplete > > Bug description: > The summary says all. The systemd process runs twice, somehow > preventing the system from getting to proper GUI login screen. My > screen stays dark, I jump to a getty using Alt-F2. I log in on the > terminal, take a list of running processes, I kill the higher number > PID from a getty, and then my system boots properly. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: systemd 245.4-4ubuntu3.6 > ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: XFCE > Date: Thu May 13 22:13:54 2021 > InstallationDate: Installed on 2021-01-15 (118 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) >Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse >Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic > root=UUID=854a0e43-544b-49d8-818f-d285989bdbc1 ro quiet splash vt.handoff=7 > SourcePackage: systemd > SystemdDelta: >[MASKED] /etc/systemd/system/samba-ad-dc.service → > /usr/lib/systemd/system/samba-ad-dc.service >[EXTENDED] /usr/lib/systemd/system/rc-local.service → > /usr/lib/systemd/system/rc-local.service.d/debian.conf >[EXTENDED] /usr/lib/systemd/system/user@.service → > /usr/lib/systemd/system/user@.service.d/timeout.conf > >3 overridden configuration files found. > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/16/2016 > dmi.bios.release: 5.6 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: F4 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: H110M-S2H-CF > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: To Be Filled By O.E.M. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/16/2016:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: To be filled by O.E.M. > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928385/+subscriptions > -- 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/1928385 Title: The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. I kill the higher number PID from a getty, and then my system boots properly. Status in systemd package in Ubuntu: Incomplete Bug description: The summary says all. The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. My screen stays dark, I jump to a getty using Alt-F2. I log in on the terminal, take a list of running processes, I kill the higher number PID from a getty, and then my system boots properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu May 13 22:13:54 2021 InstallationDate: Installed on 2021-01-15 (118 days ag
[Touch-packages] [Bug 1928385] [NEW] The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. I kill the higher number PID from a getty, and then my syste
Public bug reported: The summary says all. The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. My screen stays dark, I jump to a getty using Alt-F2. I log in on the terminal, take a list of running processes, I kill the higher number PID from a getty, and then my system boots properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu May 13 22:13:54 2021 InstallationDate: Installed on 2021-01-15 (118 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=854a0e43-544b-49d8-818f-d285989bdbc1 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2016 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/16/2016:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1928385 Title: The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. I kill the higher number PID from a getty, and then my system boots properly. Status in systemd package in Ubuntu: New Bug description: The summary says all. The systemd process runs twice, somehow preventing the system from getting to proper GUI login screen. My screen stays dark, I jump to a getty using Alt-F2. I log in on the terminal, take a list of running processes, I kill the higher number PID from a getty, and then my system boots properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu May 13 22:13:54 2021 InstallationDate: Installed on 2021-01-15 (118 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c30e Logitech, Inc. UltraX Keyboard (Y-BL49) Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=854a0e43-544b-49d8-818f-d285989bdbc1 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus
[Touch-packages] [Bug 1903890] Re: libffi7 missing from Ubuntu (pip's python3-openssl appears to be built against the wrong version of libffi)
I just upgraded from Ubuntu 20.10 to Ubuntu 21.04.
Thanks to libffi7, Lutris is working again.
---
I downloaded Lutris using the instructions from
https://lutris.net/downloads/
After Installation, I had issues with Lutris and received the error:
```
Fie "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 337, in __init__
self.callback = _ffi.callback(
Download failed: ffi_prep_closure(): bad user_data (it seems that the version
of the libffi library seen at runtime is different from the 'ffi.h' file seen
at compile-time)
```
libffi7 was not available for Ubuntu 20.10.
After the upgrade to 21.04, libffi7 has been installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1903890
Title:
libffi7 missing from Ubuntu (pip's python3-openssl appears to be built
against the wrong version of libffi)
Status in libffi package in Ubuntu:
Fix Released
Status in pyopenssl package in Ubuntu:
Incomplete
Status in libffi source package in Groovy:
Incomplete
Status in pyopenssl source package in Groovy:
Incomplete
Bug description:
Ubuntu groovy and up upgraded to libffi8ubuntu1, thus making Ubuntu
incompatible with 3rd-party binaries that desire to use libffi7.
Let's backport and provide libffi7 runtime library only, for those.
Not sure how that would work with ctypes though.
---
I've just upgraded to Ubuntu 20.10 which comes with python3-openssl
version 19.0.1-2. It breaks (at least some) Python applications that
use the `requests` library to access HTTPS URLS. For instance, this
stack trace (note that I have clipped the first few frames from the
stack as they are proprietary):
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py",
line 76, in get
return request('get', url, params=params, **kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py",
line 61, in request
return session.request(method=method, url=url, **kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line
530, in request
resp = self.send(prep, **send_kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line
643, in send
r = adapter.send(request, **kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/adapters.py", line
439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 670,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 381,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 978,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 342, in
connect
self.ssl_context = create_urllib3_context(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 289, in
create_urllib3_context
context.verify_mode = cert_reqs
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line
438, in verify_mode
self._ctx.set_verify(_stdlib_to_openssl_verify[value], _verify_callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 1119, in
set_verify
self._verify_helper = _VerifyHelper(callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 337, in __init__
self.callback = _ffi.callback(
SystemError: ffi_prep_closure(): bad user_data (it seems that the version of
the libffi library seen at runtime is different from the 'ffi.h' file seen at
compile-time)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1903890/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924757] Re: Ubuntu debug mirror is out of sync
** Package changed: ubuntu => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1924757 Title: Ubuntu debug mirror is out of sync Status in mesa package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official mirror (archive.ubuntu.com), it is not possible to install some debug symbols. For example: apt install mesa-vulkan-drivers-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1924757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic - OS: Kubuntu 20.04.1 LTS - Machine: Dell Latitude 5501 - Headset: Haylou GT1 Plus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906120] [NEW] NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
Public bug reported: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROOT_PATH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROUTERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_SUBNET_MASK=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_TIME_OFFSET=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_WPAD=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: NM_DISPATCHER_ACTION=dhcp4-change Nov 28 06:04:05 drako nm-dispat
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Sorry, comment 60 and comment 61 were intended for bug 1864256. -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Fix Released Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Note: The file /run/NetworkManager/no-stub-resolv.conf does contain the nameservers that are automatically provided by the VPN connection. This solved the issue for me: sudo rm /etc/resolv.d sudo ln -s /run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf I am running Ubuntu Desktop, not Ubuntu Server (if that is relevant). -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Fix Released Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I have this issue as well. However, the instructions given in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/57 do not solve the issue for me. When connecting the strongswan VPN, I see that the /run/systemd/resolve/resolv.conf file is touched (the timestamp of the file changes), but the content does not change. Automatic nor manual DNS servers in the VPN settings do not work. I tested manual modifying the /run/systemd/resolve/resolv.conf by changing the nameserver. This works once, but this change is not persisted, as the file is overwritten each time. using fully up to date: Linux myhost 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Fix Released Status in Ubuntu RTM: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891221] Re: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders
One can specify an alternative path, but it would be nice if the fact that the tool was relocated to a non-default (or at least not-in-$PATH) location was documented somewhere… (Neither its manpage nor the other gdk-pixbuf documentation seems to mention that.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891221 Title: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders Status in gdk-pixbuf package in Ubuntu: Invalid Bug description: Because EOG can't show webp images by default I tried to build https://github.com/aruiz/webp-pixbuf-loader but it complains that it can't find the 'gdk-pixbuf-query-loaders' tool it needs. I assume it should be in the 'libgdk-pixbuf2.0-bin' package, as that does contain a manpage for it, but not the tool itself? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891221] Re: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders
I suppose it might actually be /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0 /gdk-pixbuf-query-loaders in the libgdk-pixbuf2.0-0 package instead. Meaning the actual problem is that it is in a different location than expected by that build file... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891221 Title: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders Status in gdk-pixbuf package in Ubuntu: New Bug description: Because EOG can't show webp images by default I tried to build https://github.com/aruiz/webp-pixbuf-loader but it complains that it can't find the 'gdk-pixbuf-query-loaders' tool it needs. I assume it should be in the 'libgdk-pixbuf2.0-bin' package, as that does contain a manpage for it, but not the tool itself? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891221] [NEW] libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders
Public bug reported: Because EOG can't show webp images by default I tried to build https://github.com/aruiz/webp-pixbuf-loader but it complains that it can't find the 'gdk-pixbuf-query-loaders' tool it needs. I assume it should be in the 'libgdk-pixbuf2.0-bin' package, as that does contain a manpage for it, but not the tool itself? ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891221 Title: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders Status in gdk-pixbuf package in Ubuntu: New Bug description: Because EOG can't show webp images by default I tried to build https://github.com/aruiz/webp-pixbuf-loader but it complains that it can't find the 'gdk-pixbuf-query-loaders' tool it needs. I assume it should be in the 'libgdk-pixbuf2.0-bin' package, as that does contain a manpage for it, but not the tool itself? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
There is a upstream issue: https://github.com/sudo- project/sudo/issues/42 A fixed versions is released, maybe it can be backported to ubuntu. ** Bug watch added: github.com/sudo-project/sudo/issues #42 https://github.com/sudo-project/sudo/issues/42 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container Status in sudo package in Ubuntu: Confirmed Bug description: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1.2 Candidate: 1.8.21p2-3ubuntu1.2 Version table: *** 1.8.21p2-3ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.21p2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1868456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore
Steve, thanks for the hint to the discussion. So if I got this right, I could restore the behaviour of previous Ubuntu versions by setting fs.protected_regular=0. For my personal purpose of backing up files with rsync, I found out that I can also work around this by _not_ using the --inplace option of rsync in my backup script. It seems that I actually don't need to use this option for my usecase, and not using it seems to avoid the scenario where root has to write to files in sticky directories belonging to different users (instead rsync can just make an updated copy and delete the original file). -- 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/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore Status in procps package in Ubuntu: New Bug description: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different than root (e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1873785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873785] Re: Root can't modify files of other users in directories with sticky bit anymore
As additional information, I tested if using the Eoan kernel with Focal would do any difference on this - it didn't, so this seems not to be dependent on the kernel version in Focal. ** Description changed: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) + - Create an empty file with user:group set to anything different than root (e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't modify files of other users in directories with sticky bit anymore Status in pam package in Ubuntu: New Bug description: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different than root (e.g. ubuntu:ubuntu, ubuntu:whoopsie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult:
[Touch-packages] [Bug 1873785] [NEW] Root can't modify files of other users in directories with sticky bit anymore
Public bug reported: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Hello, in Focal the behaviour has changed when a program running as root tries to modify a file which belongs to a user/group other than root in a directory with sticky bit set. I'm not sure if this is a bug or the behaviour is intentional (for certain security reasons). Steps to reproduce: - Boot current Focal daily iso - Open terminal - Create a directory with sticky bit set (chmod o+t; or use an existing directory with sticky bit, e.g. /var/crash ) - Create an empty file with user:group set to anything different that root (e.g. ubuntu:ubuntu, ubuntu:whoospie, ...) - Open the file with nano running as root (sudo nano testfile.txt), write something in it, and try to save it. This won't work and gives a "permission denied" error message. This behaviour is different than in previous Ubuntu versions. In Eoan it is possible to modify the file as root in the scenario described above. I discovered this because after changing my main installation to Eoan I noticed that I got weird error messages from rsync when backing up my root subvolume. In my backup script rsync runs as root, and can't update backed up contents of /var/crash or /var/spool/cups/tmp anymore because it isn't allowed to modify the respective files anymore. For me personally this is a regression compared to previous Ubuntu versions where I never saw such errors during backup. Whether PAM is the appropriate package to report this bug against I'm not sure, so please feel free to assign it to the correct package. - If this is intentional, does anybode have a clue how to work around this + If this is intentional, does anybody have a clue how to work around this for use cases like backup with rsync? Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-runtime 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 20 12:11:32 2020 InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) PackageArchitecture: all SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1873785 Title: Root can't
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
There is an upstream issue in PulseAudio: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/776. ** Bug watch added: PulseAudio #776 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/776 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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 The solution to this problem is here guys: https://askubuntu.com/questions/1186081/xerox-workcentre-6015b-requires- authentication-credentials-required-in- order/1186501#1186501?newreg=b77db8f4e5e742de8a0b4092ad8acac0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1851385 Title: ubuntu 19.10 / print bug : requires authentication Status in cups package in Ubuntu: Confirmed Bug description: Hello, I have 2 computers(one laptop and one desktop) which have a dual boot Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a USB port from my modem on which my computers are connected using Wi- Fi. Since the upgrade of Ubuntu to version 19.10, I cannot print. On both computers I get the same message : [The printer] requires authentication / credentials required in order to print. With Ubuntu 19.04, I had absolutely no problem. I tried with a live USB with Ubuntu 19.04, there is no problem, the printer works. With a Ubuntu live 19.10, it doesn't work. If I plug the printer directly on a USB port on my computer, I get the same error message : [The printer] requires authentication / credentials required in order to print. It's the same behaviour on both computers, no I guess it must be a bug. Anyway I don't know which authentication I could do, with which ID and password ? Thank you very much ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 15:12:07 2019 Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B MachineType: Acer Aspire V5-571 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571 dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: Aspire V5-571 dmi.product.name: Aspire V5-571 dmi.product.sku: Aspire V5-571_072A_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849859] Re: smb printing fails
This helped me to solve the same problem on my computer: https://askubuntu.com/questions/1186081/xerox-workcentre-6015b-requires- authentication-credentials-required-in- order/1186501#1186501?newreg=b77db8f4e5e742de8a0b4092ad8acac0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853440] [NEW] Volume either 0 or 100% on Lenovo X1 Carbon G7
Public bug reported: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info" https://bugs.launchpad.net/bugs/1853440/+attachment/5306861/+files/alsa-info.txt.90cJ4Z1Jmz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in alsa-driver package in Ubuntu: New Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1853440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792027] Re: evince denied access to mimeapps.list
I get this upstream on Debian Stretch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1792027 Title: evince denied access to mimeapps.list Status in apparmor package in Ubuntu: New Bug description: I am receiving the following message in my logs. It appears that the apparmor profile for evince is too strict. Sep 11 14:17:13 bbn-11838 kernel: [275098.499551] audit: type=1400 audit(1536693433.724:1007): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/etc/xdg/mimeapps.list" pid=11797 comm="evince" requested_mask="r" denied_mask="r" fsuid=1832001200 ouid=0 I'm using Ubuntu 18.04. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt show evince Package: evince Version: 3.28.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1792027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832004] [NEW] display hanging after laptop opens lid
Public bug reported: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. E402BA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402BA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402BA 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.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E402BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832004 Title: display hanging after laptop opens lid Status in xorg package in Ubuntu: New Bug description: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. E402BA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402BA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402BA 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:
[Touch-packages] [Bug 1793120] Re: Ubuntu 18.04.1 Desktop install fails to show try or install choice
Tried with ubuntu-18.04.2-desktop-amd64. Same error. -- 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/1793120 Title: Ubuntu 18.04.1 Desktop install fails to show try or install choice Status in systemd package in Ubuntu: New Bug description: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813430] [NEW] fstrim.service should not run inside container
Public bug reported: On LXD containers, the fstrim.service will errored permanently. /sbin/fstrim -av fstrim: /: FITRIM ioctl failed: Operation not permitted The unit file should contain ConditionVirtualization=!container to prevent errors inside containers ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: lxd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1813430 Title: fstrim.service should not run inside container Status in util-linux package in Ubuntu: New Bug description: On LXD containers, the fstrim.service will errored permanently. /sbin/fstrim -av fstrim: /: FITRIM ioctl failed: Operation not permitted The unit file should contain ConditionVirtualization=!container to prevent errors inside containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1813430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications
** Bug watch added: Debian Bug tracker #911148 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 ** Also affects: hash-it via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in Hash-it: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hash-it/+bug/1798861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1801918] Re: storage pool with persistent device names fails
Christian, thank you for pointing me in the right direction. Adding filter = [ "a|/dev/disk/by-path/pci-*|" ] to /etc/lvm/lvm.conf solved this issue. (There is no need to restart any service after changing this file. ;)) You can find the thread on the mailing list under this link: https://www.redhat.com/archives/libvirt-users/2018-October/msg00059.html I'll add a response there soon. Best Regards Jan Am 06.11.18 um 15:48 schrieb Christian Ehrhardt : > I now used: > filter =[ "a|/dev/disk/by-path/virtio-pci-*|" ] > > Now it really is the same way on creation and query. > $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0 > Physical volume "/dev/disk/by-path/virtio-pci-:00:07.0" successfully > created. > $ sudo pvdisplay > "/dev/disk/by-path/virtio-pci-:00:07.0" is a new physical volume of > "30.00 MiB" > --- NEW Physical volume --- > PV Name /dev/disk/by-path/virtio-pci-:00:07.0 > > And with that finally > $ sudo virsh pool-build testpool1 > Pool testpool1 built > > $ sudo virsh pool-start testpool1 > Pool testpool1 started > > I'd still be interested in the mail thread link. > But for your case, if you want to use by-path with LVM you should adapt the > lvm.conf to use (only) these. > > ** Changed in: libvirt (Ubuntu) >Status: Incomplete => Invalid > -- Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95 E-Mail: supp...@artfiles.de | Web: http://www.artfiles.de Geschäftsführer: Harald Oltmanns | Tim Evers Eingetragen im Handelsregister Hamburg - HRB 81478 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1801918 Title: storage pool with persistent device names fails Status in libvirt package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Invalid Bug description: lvm2 tools do not store by-path values in their config. That can drive scripts/tools (like the libvirt case here) mad. Simplified example: $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-:00:07.0 $ sudo /sbin/pvs --noheadings -o pv_name,vg_name /dev/vdc It is NOT using /dev/disk/by-path/virtio-pci-:00:07.0 as instructed, but instead did the mapping to /dev/vdd and keeps that from now on. I know that "inside" lvm all that is done via metadata and it won't matter. But tools around it get confused. Not sure yet if it is a real issue, or just "works as designed". --- started as libvirt issue - keeping old desc below --- I am trying to create a logical volume storage pool with persistent device names for the block devices, because I can't/don't want to ensure that /dev/sd* names are persistent through reboots. virsh # pool-define-as web2067 logical - - /dev/disk/by-path/pci-:18:00.0-scsi-0:2:2:0 web2067 /dev/web2067 virsh # pool-build web2067 These two steps work as expected and the pv and the vg get created, but when I try to start the pool I get the following error: virsh # pool-start web2067 error: Failed to start pool web2067 error: unsupported configuration: cannot find any matching source devices for logical volume group 'web2067' If I do the same steps just with /dev/sdX instead of /dev/disk/by-path/..., the pool gets created correctly. According to the libvirt mailing list /dev and /dev/disk/by-path are supposed to work the same way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1801918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
This still happens on a Dell Latitude E6430 with docking station and two external DVI monitors running Linux Mint 19 (based on Ubuntu Bionic) ii systemd 237-3ubuntu10.3 amd64system and service manager ii systemd-sysv 237-3ubuntu10.3 amd64system and service manager - SysV links Oct 17 08:33:49 l1 systemd[1]: Started Disk Manager. Oct 17 08:33:49 l1 systemd[1]: Reached target Graphical Interface. Oct 17 08:33:49 l1 systemd[1]: Started Stop ureadahead data collection 45s after completed startup. Oct 17 08:33:49 l1 systemd[1]: Starting Update UTMP about System Runlevel Changes... Oct 17 08:33:49 l1 NetworkManager[1312]: [1539718429.0768] manager: sleep: sleep requested (sleeping: no enabled: yes) Oct 17 08:33:49 l1 NetworkManager[1312]: [1539718429.0769] device (wlp3s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Oct 17 08:33:49 l1 NetworkManager[1312]: [1539718429.0774] manager: NetworkManager state is now ASLEEP Oct 17 08:33:49 l1 systemd[1]: Reached target Sleep. Oct 17 08:33:49 l1 systemd[1]: Starting Suspend... Oct 17 08:33:49 l1 systemd[1]: Started Update UTMP about System Runlevel Changes. Oct 17 08:33:49 l1 systemd-sleep[2197]: Suspending system... Oct 17 08:33:49 l1 kernel: [ 30.151723] PM: suspend entry (deep) ...but did NOT happen with the previous version of Linux Mint 18 (based on Ubuntu Xenial). ii systemd 229-4ubuntu21.2 amd64system and service manager ii systemd-shim 9-1bzr4ubuntu1 amd64shim for systemd ii systemd-sysv 229-4ubuntu21.2 amd64 system and service manager - SysV links -- 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/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Same problem for me... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793120] [NEW] Ubuntu 18.04.1 Desktop install fails to show try or install choice
Public bug reported: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2018-08-31 005.jpg" https://bugs.launchpad.net/bugs/1793120/+attachment/5190136/+files/2018-08-31%20005.jpg -- 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/1793120 Title: Ubuntu 18.04.1 Desktop install fails to show try or install choice Status in systemd package in Ubuntu: New Bug description: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
This stupid behavior isn't only inconvinient, -> this really BREAKS FUNCTIONALITY if you work on network resources. Especially in Germany where possible internet speeds in many locations do not exeed well known dialup connection speeds. What happens then is a complete lockup on nautilus while the filelists are queried again from the remote site. This usually takes minutes to complete. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
I have just wasted 16 pages of paper. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Just chiming in to say that, yes, #19 (with or without #24) works for me, too. What I don't get is why this is isn't officially fixed, yet. The solution is pretty clear by now. What/who is the bottleneck here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ 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.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775187] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149220/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1775187] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149226/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775187] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149223/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775187] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149219/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touc
[Touch-packages] [Bug 1775187] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149216/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : to
[Touch-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-11-09 (209 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: LENOVO 20FWCTO1WW + Package: bluez 5.48-0ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + Tags: third-party-packages bionic + Uname: Linux 4.15.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark + _MarkForUpload: True + dmi.bios.date: 06/07/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: R07ET67W (2.07 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20FWCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40705 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T460p + dmi.product.name: 20FWCTO1WW + dmi.product.version: ThinkPad T460p + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 + TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149214/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted befo
[Touch-packages] [Bug 1775187] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149217/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : to
[Touch-packages] [Bug 1775187] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149224/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1775187] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149222/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1775187] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149218/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Pos
[Touch-packages] [Bug 1775187] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149221/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1775187] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149215/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages P
[Touch-packages] [Bug 1775187] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149225/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1775187] [NEW] bluetooth headset gets imitatively disconnected
Public bug reported: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: New Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last e
[Touch-packages] [Bug 1476769]
This bug has been reported against a Fedora version which is already unsuported. In compliance with FESCo decision how to handle EOL of Security issues [1], I am changing the version to '27', the latest supported release. Please check whether this bug is still an issue on the '27' release. If you find this bug not being applicable on this release, please close it. [1] https://pagure.io/fesco/issue/1736 -- 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/1476769 Title: When activating OpenVPN without DHCP6, random traffic will be routed without VPN Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: When activating an OpenVPN without DHCP6 through NetworkManager, random traffic will be routed without VPN if the basic physical network device has IPv6 connectivity but the VPN hasn't. This is a security issue, since a user activating the VPN would expect all go through it. network-manager package version: 0.9.10.0-4ubuntu15.1 Steps to reproduce: 1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn configuration file and import into NetworkManager 2. Make sure your physical networking device has native IPv6 access 3. Activate the VPN in the network settings Expected result: * IPv4 default route through VPN * IPv6 default route absent (as VPN doesn't provide any) Actual result (as I understand the bug report): * IPv4 default route through VPN (good) * IPv6 default route via local gateway (bad) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: openvpn 2.3.2-9ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 21 19:21:50 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1476769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I just tested the thing in #123 and I can only conclude: i am writing this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can only agree to what Thijs says. This sounds like a timing problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
New upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/322 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/410636 Title: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Triaged Bug description: When I right click in nautilus, the context menu appear. If I right click on a menu item, the function of that menu item is performed. This is very annoying, because when the context menu appears, the mouse is at the first menu item, so if you accidentally right click two times, you will surely perform the function of the first menu item! Everytime I right click in desktop, i probably create a new Folder! I think there maybe 2 solutions to this: - To perform the function of a menu item, only left click is allowed. - When the user right click, the context menu will appear at a bit lower position, so the mouse will not be at the first menu item. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/410636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759042] [NEW] apport-bug amd64 artful ubuntu
Public bug reported: apport-bug amd64 artful ubuntu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 Uname: Linux 4.13.0-37-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 26 23:41:42 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:0358] InstallationDate: Installed on 2018-03-09 (17 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-lowlatency root=UUID=a9b9e879-acb5-44e8-ba69-5377b28a36b1 ro recovery nomodeset priority=low Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3027 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3027:bd10/31/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 26 23:31:47 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1759042 Title: apport-bug amd64 artful ubuntu Status in xorg package in Ubuntu: New Bug description: apport-bug amd64 artful ubuntu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 Uname: Linux 4.13.0-37-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 26 23:41:42 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:0358] InstallationDate: Installed on 2018-03-09 (17 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-lowlatency root=UUID=a9b9e879-acb5-44e8-ba69-5377b28a36b1 ro recovery nomodeset priority=low Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3027 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3027:bd10/31/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.s
[Touch-packages] [Bug 1752515] [NEW] package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
Public bug reported: I can't install it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 08:59:56 2018 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2017-11-24 (96 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1752515 Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 Status in util-linux package in Ubuntu: New Bug description: I can't install it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 08:59:56 2018 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2017-11-24 (96 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1752515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615856] Re: cannnot set phase2 peap auth to none
See also: https://bugzilla.gnome.org/show_bug.cgi?id=773126 ** Bug watch added: GNOME Bug Tracker #773126 https://bugzilla.gnome.org/show_bug.cgi?id=773126 -- 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/1615856 Title: cannnot set phase2 peap auth to none Status in network-manager package in Ubuntu: Confirmed Bug description: In my university, they use PEAP auth, with no certificate and phase 2 authentication set to none. On windows and android I am able to set this, however network-manager offers no such option, and I cant connect to that network. I have tried to work around using this: https://ubuntuforums.org/showthread.php?t=1726522 However I could not make it to work. Description: Ubuntu 16.04.1 LTS Release: 16.04 network-manager: Installed: 1.2.0-0ubuntu0.16.04.3 Candidate: 1.2.0-0ubuntu0.16.04.3 Version table: *** 1.2.0-0ubuntu0.16.04.3 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
