[Touch-packages] [Bug 2051358] Re: Start of systemd service on physical network devices using a udev rule has stopped working
After additional investigation our udev rule is installed in the initramfs and
with patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
the associated systemd service is never started when the OS starts.
We have created an initramfs hook script to remove our udev rule and now our
custom systemd service is starting properly when the OS starts.
Is this a side effect of above patch or is it something expected ?
--
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/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
A colleague has rebuilt systemd package by reverting below patch and
everything started working again:
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing us an issue to access network when the machine is
starting.
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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 2051358] Re: Start of systemd service on physical network devices using a udev rule has stopped working
** Description changed:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
- The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
-
- A colleague has rebuilt systemd package by reverting below patch and
- everything started working again
-
- core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
- File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
-
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
-
- This is causing an issue to access network when the machine is starting.
+ The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
- ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
+ ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
+
+ A colleague has rebuilt systemd package by reverting below patch and
+ everything started working again:
+
+ core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
+ File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
+
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
+
+ This is causing us an issue to access network when the machine is
+ starting.
+
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
--
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/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
A colleague has rebuilt systemd package by reverting below patch and
everything started working again:
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing us an issue to access network when the machine is
starting.
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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 2051358] [NEW] Start of systemd service on physical network devices using a udev rule has stopped working
Public bug reported:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical wired
network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
A colleague has rebuilt systemd package by reverting below patch and
everything started working again
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing an issue to access network when the machine is starting.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
** 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/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
A colleague has rebuilt systemd package by reverting below patch and
everything started working again
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing an issue to access network when the machine is
starting.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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 1914056] [NEW] package procps 2:3.3.10-4ubuntu2 [modified: usr/bin/free usr/bin/pgrep usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/
Public bug reported: dpkg: erreur de traitement du paquet procps (--configure) : le paquet procps n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») dpkg: des problèmes de dépendances empêchent la configuration de udev : udev dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet udev (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de bluez : bluez dépend de udev (>= 170-1) ; cependant : Le paquet udev n'est pas encore configuré. dpkg: erreur de traitement du paquet bluez (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups-daemon : cups-daemon dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet cups-daemon (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de initramfs-tools-core : initramfs-tools-core dépend de udev ; cependant : Le paquet udAucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint ev n'est pas encore configuré. dpkg: erreur de traitement du paquet initramfs-tools-core (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de initramfs-tools : initramfs-tools dépend de initramfs-tools-core (= 0.122ubuntu8.17) ; cependant : Le paquet initramfs-tools-core n'est pas encore configuré. dpkg: erreur de traitement du paquet initramfs-tools (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups-core-drivers : cups-core-drivers dépend de cups-daemon (>= 2.1.3-4ubuntu0.11) ; cependant : Le paquet cups-daemon n'est pas encore configuré. dpkg: erreur de traitement du paquet cups-core-drivers (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de cups : cups dépend de cups-core-drivers (>= 2.1.3-4ubuntu0.11) ; cepeAucun rapport « apport » écrit car MaxReports a déjà été atteint Aucun rapport « apport » écrit car MaxReports a déjà été atteint ndant : Le paquet cups-core-drivers n'est pas encore configuré. cups dépend de cups-daemon (>= 2.1.3-4ubuntu0.11) ; cependant : Le paquet cups-daemon n'est pas encore configuré. cups dépend de procps ; cependant : Le paquet procps n'est pas installé. dpkg: erreur de traitement du paquet cups (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de xserver-xorg-core : xserver-xorg-core dépend de udev (>= 149) ; cependant : Le paquet udev n'est pas encore configuré. dpkg: erreur de traitement du paquet xserver-xorg-core (--configure) : problèmes de dépendances - laissé non configuré Des erreurs ont été rencontrées pendant l'exécution : procps udev bluez cups-daemon initramfs-tools-core initramfs-tools cups-core-drivers cups xserver-xorg-core E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2 [modified: usr/bin/free usr/bin/pgrep usr/bin/pwdx usr/bin/skill usr/bin/slabtop usr/bin/tload usr/bin/top usr/bin/uptime usr/bin/vmstat usr/bin/watch] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Feb 1 14:49:19 2021 ErrorMessage: le paquet procps n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») InstallationDate: Installed on 2021-01-28 (3 days ago) InstallationMedia:
[Touch-packages] [Bug 1817338] Re: HDMI sound output not available
I can confirm it works when booting a live 18.10 session. As to tell exactly when it broke, it's kind of hard, but it was near the beginning of february... -- 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/1817338 Title: HDMI sound output not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1817338/+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 1817338] Re: HDMI sound output not available
Ok, trying to rephrase the problem :-) I have a laptop (Thinkpad T430s) hooked on a dock, then an HDMI monitor with embedded speakers (Asus MX27AQ) on the dock. Before upgrading to 19.04 ongoing release, I was able to choose HDMI speaker as sound output, from the sound setting in Gnome shell. Now, I can't get sound on the monitor anymore, only laptop speakers are working. If I choose the HDMI/Displayport option in the gnome sound settings, it wont change anything. When this option is selected, if I click on the test button, it will display a window with "click a speaker to test", but NO speaket to choose from (only the "user" icon). Hopes this is helpful to define the bug more accuratly... -- 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/1817338 Title: HDMI sound output not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1817338/+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 1817338] [NEW] HDMI sound output not available
Public bug reported: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Attachment added: "gnome-control-center not showing configuration options for HDMI" https://bugs.launchpad.net/bugs/1817338/+attachment/5240948/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202019-02-22%2016-24-51.png -- 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/1817338 Title: HDMI sound output not available Status in pulseaudio package in Ubuntu: New Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset I
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
for me the problem is solved with : sudo apt remove pulseaudio reboot -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
@aquina I was just pointing ufw vs firewalld as it is the app (gufw) that drove me here. I also wanted to point out that by adopting Gnome / Systemd / Wayland / ... Ubuntu is now dependant and has to keep up with the new upstream, that tends to be RedHat / Fedora. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago)
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Are there any plans to move forward and try to coordinate applications rewrite/adaptation ? I'm not in love with wayland, but isolating graphical applications for each other seems a legitimate concern (see https://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html for example). Now that Ubuntu has given up on Wayland by default, I'm afraid there is now less incentive for transitioning to the security model wayland wants to impose. So what? Should we use firewalld instead of ufw? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
What happened to this bug? Is it still being addressed? I'm also experiencing the same problem and the solutions above don't work for me :( Ubuntu 16.04.4 LTS NetworkManager 1.2.6 dnsmasq 2.76 -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1636395] Re: dnsmasq not working with OpenVPN
Nicholas @nstommel I'm using dnscrypt-proxy and now I can successfully connect to internet and to vpn server. Thank you! Will test this further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1636395 Title: dnsmasq not working with OpenVPN Status in dnsmasq package in Ubuntu: Confirmed Status in openvpn-systemd-resolved package in Ubuntu: Confirmed Bug description: I'm using OpenVPN configured with Network Manager. My VPN have a DNS server configured by OpenVPN and config pushed by it while connecting. This server is not registered by dnsmasq so domain names are not resolved but pinging by IP address works. When I test name resolving by pointing to DNS server (172.16.1.1) from VPN provider it's works. For example: $ host google.com 172.16.1.1 Using domain server: Name: 172.16.1.1 Address: 172.16.1.1#53 Aliases: google.com has address 172.217.0.174 google.com has IPv6 address 2607:f8b0:400b:807::200e google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. But if I test without pointing DNS server is not working: $ host google.com ;; connection timed out; no servers could be reached My /etc/resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 To repair this bug I have to kill dnsmasq and it's automatically reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1636395/+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 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed
Do you think that this error can break my VPN connection ? I do not know if this is the cause. Here a piece of logs : Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Plugin /usr/lib/pppd/2.4.7/nm-l2tp-pppd-plugin.so loaded. Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Plugin pppol2tp.so loaded. Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: pppd 2.4.7 started by root, uid 0 Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: ((src/devices/nm-device.c:1452)): assertion '' failed Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Using interface ppp0 Dez 05 15:06:16 fgarnier-Latitude-5580 pppd[26238]: Connect: ppp0 <--> Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5766] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/7) Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5940] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Dez 05 15:06:16 fgarnier-Latitude-5580 NetworkManager[973]: [1512482776.5940] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Dez 05 15:06:18 fgarnier-Latitude-5580 NetworkManager[973]: xl2tpd[26237]: control_finish: Connection closed to 194.209.82.248, serial 1 () Dez 05 15:06:18 fgarnier-Latitude-5580 NetworkManager[973]: xl2tpd[26237]: Terminating pppd: sending TERM signal to pid 26238 -- 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/1728378 Title: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed Status in network-manager package in Ubuntu: Confirmed Bug description: This error shows up in boot logs: "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed". Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728378/+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 1663292] [NEW] In zesty, unity scope fails to connect to zeitgeist
Public bug reported: Description:Ubuntu Zesty Zapus (development branch) Release:17.04 Since I installed 17.04 (fresh install), first use of the main unity scope takes a long time (timeout ?). After some time, it works. Looking at the logs in syslog, I've spotted these lines: unity-scope-loa[9221]: daemon.vala:: Error performing search '': Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:50:02 franck-ThinkPad-T430s unity-scope-hom[9210]: unity-master-scope.vala:114: Unable to search scope: 'Le délai d'attente est dépassé' Feb 9 16:50:02 franck-ThinkPad-T430s unity-files-dae[9223]: index.vala:61: Unable to connect to Zeitgeist FTS: Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:51:12 franck-ThinkPad-T430s dbus-daemon[7051]: Failed to activate service 'org.gnome.zeitgeist.Engine': timed out ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zeitgeist (not installed) ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 9 16:55:58 2017 InstallationDate: Installed on 2017-02-01 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1663292 Title: In zesty, unity scope fails to connect to zeitgeist Status in zeitgeist package in Ubuntu: New Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Since I installed 17.04 (fresh install), first use of the main unity scope takes a long time (timeout ?). After some time, it works. Looking at the logs in syslog, I've spotted these lines: unity-scope-loa[9221]: daemon.vala:: Error performing search '': Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:50:02 franck-ThinkPad-T430s unity-scope-hom[9210]: unity-master-scope.vala:114: Unable to search scope: 'Le délai d'attente est dépassé' Feb 9 16:50:02 franck-ThinkPad-T430s unity-files-dae[9223]: index.vala:61: Unable to connect to Zeitgeist FTS: Erreur lors de l'appel de StartServiceByName pour org.gnome.zeitgeist.Engine : Le délai d'attente est dépassé Feb 9 16:51:12 franck-ThinkPad-T430s dbus-daemon[7051]: Failed to activate service 'org.gnome.zeitgeist.Engine': timed out ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zeitgeist (not installed) ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 9 16:55:58 2017 InstallationDate: Installed on 2017-02-01 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1663292/+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 861137] Re: Openssl TLS errors while connecting to SSLv3 sites
** Also affects: python-apns-client (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/861137 Title: Openssl TLS errors while connecting to SSLv3 sites Status in openssl package in Ubuntu: Confirmed Status in python-apns-client package in Ubuntu: New Bug description: I upgraded to Oneiric Ocelot beta1. OpenSSL version is "1.0.0e 6 Sep 2011" Now, when I connect to certain HTTPs servers with wget or curl I get a TLS error. With wget : OpenSSL: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error With curl : curl: (35) error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error In wget, this can be fixed by specifying --secure-protocol=sslv3 option In curl, this can be fixed by specifying -sslv3 option The issue is that the automatic check for the version seems to be failing. This is working fine in Natty systems using older versions of openssl. The impact of this will be in scripts using curl, wget etc. which will start failing after an upgrade. Ubuntu version Description: Ubuntu oneiric (development branch) Release: 11.10 OpenSSL version : OpenSSL 1.0.0e 6 Sep 2011 openssl: Installed: 1.0.0e-2ubuntu2 Candidate: 1.0.0e-2ubuntu2 Version table: *** 1.0.0e-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137/+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 1636137] [NEW] totem-video-thumbnailer needs write access to .cache in 16.10
Public bug reported: Since I upgraded to 16.10, video preview fail in Nautilus, with this message in the logs: audit: type=1400 audit(1477301198.204:99): apparmor="DENIED" operation="mknod" profile="/usr/bin/totem-video-thumbnailer" name="/home/franck/.cache/gstreamer-1.0/registry.x86_64.bin.tmpICLVPY" pid=9142 comm="totem-video-thu" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 12:13:57 2016 InstallationDate: Installed on 2015-10-04 (385 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 24 09:02:31 franck-ThinkPad-T430s dbus[3296]: [system] AppArmor D-Bus mediation is enabled Oct 24 10:38:16 franck-ThinkPad-T430s dbus[3387]: [system] AppArmor D-Bus mediation is enabled Oct 24 11:08:57 franck-ThinkPad-T430s dbus[3396]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (9 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1636137 Title: totem-video-thumbnailer needs write access to .cache in 16.10 Status in apparmor package in Ubuntu: New Bug description: Since I upgraded to 16.10, video preview fail in Nautilus, with this message in the logs: audit: type=1400 audit(1477301198.204:99): apparmor="DENIED" operation="mknod" profile="/usr/bin/totem-video-thumbnailer" name="/home/franck/.cache/gstreamer-1.0/registry.x86_64.bin.tmpICLVPY" pid=9142 comm="totem-video-thu" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 24 12:13:57 2016 InstallationDate: Installed on 2015-10-04 (385 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Oct 24 09:02:31 franck-ThinkPad-T430s dbus[3296]: [system] AppArmor D-Bus mediation is enabled Oct 24 10:38:16 franck-ThinkPad-T430s dbus[3387]: [system] AppArmor D-Bus mediation is enabled Oct 24 11:08:57 franck-ThinkPad-T430s dbus[3396]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to yakkety on 2016-10-14 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1636137/+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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp
Motivation for this new requirement is:
## Why
Each particular network your computer and browser run in has its own set of
network conditions, routers, proxies and MITM situations.
Changing between networks also changes proxies. Intercepting or explicit,
willing or unwilling, HTTP or even HTTPS with custom installed trust-roots.
This makes the web content cache, the cookie store and others to save
contents from one network that is potentially different than what is received
over other networks. It can lead to content pollution and information leaks,
on purpose by malicious actors or just by mistake.
see the details here
https://bug1240932.bmoattachments.org/attachment.cgi?id=8709691
--
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/1628956
Title:
From v49.0, Firefox needs read access to @{PROC}/net/arp
Status in apparmor package in Ubuntu:
New
Bug description:
Since the latest upgrade of Firefox to 49.0, it will need read access
to @{PROC}/net/arp
I don't know what the security implications are, so I don't know if we
want to give read access to explicitely deny it. Both seem to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 29 16:55:21 2016
InstallationDate: Installed on 2015-10-04 (361 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus
mediation is enabled
Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser:
2015-10-05T12:02:05.273141
mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon:
2016-04-13T19:13:25.829679
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628956/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
Another message: audit: type=1400 audit(1476791887.152:118): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.pid" pid=5480 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634416] [NEW] Firefox need access to org.freedesktop.resolve1 ResolvehostName
Public bug reported:
In 16.10, FF 49.0, it seems that Firefox want to use the systemd
resolved service via dbus:
audit: type=1107 audit(1476778477.837:122): pid=3449 uid=105
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/resolve1"
interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
mask="send" name="org.freedesktop.resolve1" pid=9652
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=3909
peer_label="unconfined"
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 10:55:46 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug package-from-proposed yakkety
--
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/1634416
Title:
Firefox need access to org.freedesktop.resolve1 ResolvehostName
Status in apparmor package in Ubuntu:
New
Bug description:
In 16.10, FF 49.0, it seems that Firefox want to use the systemd
resolved service via dbus:
audit: type=1107 audit(1476778477.837:122): pid=3449 uid=105
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/resolve1"
interface="org.freedesktop.resolve1.Manager" member="ResolveHostname"
mask="send" name="org.freedesktop.resolve1" pid=9652
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=3909
peer_label="unconfined"
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 10:55:46 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634416/+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 1634418] [NEW] In 16.10, several apps want write access to /run/systemd/journal/socket
Public bug reported:
Several app try to write into /run/systemd/journal/socket
Maybe this should be an abstraction ?
Firefox:
audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/run/systemd/journal/socket" pid=25552 comm="firefox"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
evince:
audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED"
operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 11:00:02 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug package-from-proposed yakkety
--
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/1634418
Title:
In 16.10, several apps want write access to
/run/systemd/journal/socket
Status in apparmor package in Ubuntu:
New
Bug description:
Several app try to write into /run/systemd/journal/socket
Maybe this should be an abstraction ?
Firefox:
audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/run/systemd/journal/socket" pid=25552 comm="firefox"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
evince:
audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED"
operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 11:00:02 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634418/+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 1634419] [NEW] In 16.10, several apps want write access to /run/systemd/journal/socket
Public bug reported:
Several app try to write into /run/systemd/journal/socket
Maybe this should be an abstraction ?
Firefox:
audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/run/systemd/journal/socket" pid=25552 comm="firefox"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
evince:
audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED"
operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 11:00:02 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug package-from-proposed yakkety
--
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/1634419
Title:
In 16.10, several apps want write access to
/run/systemd/journal/socket
Status in apparmor package in Ubuntu:
New
Bug description:
Several app try to write into /run/systemd/journal/socket
Maybe this should be an abstraction ?
Firefox:
audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/run/systemd/journal/socket" pid=25552 comm="firefox"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
evince:
audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED"
operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 11:00:02 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634419/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile
I'm afraid it won't be enough...: audit: type=1400 audit(1476780672.803:99): apparmor="DENIED" operation="open" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.hosts" pid=5165 comm="dnsmasq" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1634375] [NEW] In 16.10, freshclam tries to access /run/dbus/system_socket
Public bug reported: In 16.10, usr.bin.freshclam profile does not allow access to /run/dbus/system_bus_socket, which freshclam tries to access. apparmor="DENIED" operation="connect" profile="/usr/bin/freshclam" name="/run/dbus/system_bus_socket" pid=3423 comm="freshclam" requested_mask="wr" denied_mask="wr" fsuid=132 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 08:52:16 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1634375 Title: In 16.10, freshclam tries to access /run/dbus/system_socket Status in apparmor package in Ubuntu: New Bug description: In 16.10, usr.bin.freshclam profile does not allow access to /run/dbus/system_bus_socket, which freshclam tries to access. apparmor="DENIED" operation="connect" profile="/usr/bin/freshclam" name="/run/dbus/system_bus_socket" pid=3423 comm="freshclam" requested_mask="wr" denied_mask="wr" fsuid=132 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apparmor 2.10.95-4ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 18 08:52:16 2016 InstallationDate: Installed on 2015-10-04 (379 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634375/+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 1634199] [NEW] In 16.10, LXD won't work with enforced dsnmasq profile
Public bug reported: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1634199 Title: In 16.10, LXD won't work with enforced dsnmasq profile Status in apparmor package in Ubuntu: New Bug description: After upgrading to 16.0, LXD networking stopped working due to enforced dnsmasq profile. audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED" operation="truncate" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1634199/+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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp
Ok, I just asked on firefox-dev mailing list...
--
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/1628956
Title:
From v49.0, Firefox needs read access to @{PROC}/net/arp
Status in apparmor package in Ubuntu:
New
Bug description:
Since the latest upgrade of Firefox to 49.0, it will need read access
to @{PROC}/net/arp
I don't know what the security implications are, so I don't know if we
want to give read access to explicitely deny it. Both seem to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 29 16:55:21 2016
InstallationDate: Installed on 2015-10-04 (361 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus
mediation is enabled
Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser:
2015-10-05T12:02:05.273141
mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon:
2016-04-13T19:13:25.829679
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628956/+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 1628956] [NEW] From v49.0, Firefox needs read access to @{PROC}/net/arp
Public bug reported:
Since the latest upgrade of Firefox to 49.0, it will need read access to
@{PROC}/net/arp
I don't know what the security implications are, so I don't know if we
want to give read access to explicitely deny it. Both seem to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 29 16:55:21 2016
InstallationDate: Installed on 2015-10-04 (361 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus
mediation is enabled
Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser:
2015-10-05T12:02:05.273141
mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 2016-04-13T19:13:25.829679
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
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/1628956
Title:
From v49.0, Firefox needs read access to @{PROC}/net/arp
Status in apparmor package in Ubuntu:
New
Bug description:
Since the latest upgrade of Firefox to 49.0, it will need read access
to @{PROC}/net/arp
I don't know what the security implications are, so I don't know if we
want to give read access to explicitely deny it. Both seem to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 29 16:55:21 2016
InstallationDate: Installed on 2015-10-04 (361 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus
mediation is enabled
Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
[Touch-packages] [Bug 1569316] [NEW] Log flooded with run/dbus/system_bus_socket wr denied
Public bug reported: Since latest upgrade, my logs are flooded with this message : audit: type=1400 audit(1460463960.943:31702): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/dnsmasq" name="run/dbus/system_bus_socket" pid=3448 comm="dnsmasq" requested_mask="wr" denied_mask="wr" fsuid=65534 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 12 14:26:42 2016 InstallationDate: Installed on 2015-10-04 (190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Apr 12 09:42:22 franck-ThinkPad-T430s dbus[2219]: [system] AppArmor D-Bus mediation is enabled Apr 12 12:24:39 franck-ThinkPad-T430s dbus[2318]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium.browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968 mtime.conffile..etc.apparmor.d.usr.bin.chromium.browser: 2015-10-05T12:02:05.273141 mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323 mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403 mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523 mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794 mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1569316 Title: Log flooded with run/dbus/system_bus_socket wr denied Status in apparmor package in Ubuntu: New Bug description: Since latest upgrade, my logs are flooded with this message : audit: type=1400 audit(1460463960.943:31702): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/dnsmasq" name="run/dbus/system_bus_socket" pid=3448 comm="dnsmasq" requested_mask="wr" denied_mask="wr" fsuid=65534 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 12 14:26:42 2016 InstallationDate: Installed on 2015-10-04 (190 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Apr 12 09:42:22 franck-ThinkPad-T430s dbus[2219]: [system] AppArmor D-Bus mediation is enabled Apr 12 12:24:39 franck-ThinkPad-T430s dbus[2318]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium.browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2
[Touch-packages] [Bug 1566944] Re: dnsmasq profile prevents LDX container to launch
In the initial bug report against LXD, S. Graber suggests that maybe "The apparmor dnsmasq profile should only apply to the system wide daemon (/etc/init.d/dnsmasq) and not to other daemons". Not sure what to think about it... -- 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/1566944 Title: dnsmasq profile prevents LDX container to launch Status in apparmor package in Ubuntu: New Bug description: LXD 2.0 has dropped lxcbr0 for lxdbr0 as its default bridge configuration. Since then, having usr.sbin.dnsmasq profile in enforce mode will prevent LXD containers to launch: Apr 6 12:55:06 franck-ThinkPad-T430s kernel: [ 7029.101587] audit: type=1400 audit(1459940106.552:107): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd-bridge/dnsmasq.lxdbr0.leases" pid=22292 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Apr 6 12:55:06 franck-ThinkPad-T430s lxd-bridge.start[22255]: dnsmasq: ne peut ouvrir ou créer le fichiers de baux /var/lib/lxd-bridge//dnsmasq.lxdbr0.leases : Permission non accordée Of course, switching to complain mode works the problem around, but maybe allowing write to /var/lib/lxd-bridge/ would be a good idea (disclaimer: I'm not a security expert). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 6 17:34:12 2016 InstallationDate: Installed on 2015-10-04 (185 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.bin.ping: [modified] modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslog.ng: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium.browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: [modified] mtime.conffile..etc.apparmor.d.bin.ping: 2015-10-05T12:02:58.049761 mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslog.ng: 2015-10-05T12:03:21.918041 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968 mtime.conffile..etc.apparmor.d.usr.bin.chromium.browser: 2015-10-05T12:02:05.273141 mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2015-10-05T11:59:18.903198 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-06T17:25:47.252257 mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323 mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403 mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523 mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794 mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2015-10-05T12:00:17.355879 mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981 mtime.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: 2015-10-05T12:00:35.504091 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1566944/+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 1566944] Re: dnsmasq profile prevents LDX container to launch
Initial LXD bug report: https://github.com/lxc/lxd/issues/1857 -- 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/1566944 Title: dnsmasq profile prevents LDX container to launch Status in apparmor package in Ubuntu: New Bug description: LXD 2.0 has dropped lxcbr0 for lxdbr0 as its default bridge configuration. Since then, having usr.sbin.dnsmasq profile in enforce mode will prevent LXD containers to launch: Apr 6 12:55:06 franck-ThinkPad-T430s kernel: [ 7029.101587] audit: type=1400 audit(1459940106.552:107): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd-bridge/dnsmasq.lxdbr0.leases" pid=22292 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Apr 6 12:55:06 franck-ThinkPad-T430s lxd-bridge.start[22255]: dnsmasq: ne peut ouvrir ou créer le fichiers de baux /var/lib/lxd-bridge//dnsmasq.lxdbr0.leases : Permission non accordée Of course, switching to complain mode works the problem around, but maybe allowing write to /var/lib/lxd-bridge/ would be a good idea (disclaimer: I'm not a security expert). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 6 17:34:12 2016 InstallationDate: Installed on 2015-10-04 (185 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.bin.ping: [modified] modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslog.ng: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium.browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: [modified] mtime.conffile..etc.apparmor.d.bin.ping: 2015-10-05T12:02:58.049761 mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslog.ng: 2015-10-05T12:03:21.918041 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968 mtime.conffile..etc.apparmor.d.usr.bin.chromium.browser: 2015-10-05T12:02:05.273141 mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2015-10-05T11:59:18.903198 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-06T17:25:47.252257 mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323 mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403 mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523 mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794 mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2015-10-05T12:00:17.355879 mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981 mtime.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: 2015-10-05T12:00:35.504091 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1566944/+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 1566944] [NEW] dnsmasq profile prevents LDX container to launch
Public bug reported: LXD 2.0 has dropped lxcbr0 for lxdbr0 as its default bridge configuration. Since then, having usr.sbin.dnsmasq profile in enforce mode will prevent LXD containers to launch: Apr 6 12:55:06 franck-ThinkPad-T430s kernel: [ 7029.101587] audit: type=1400 audit(1459940106.552:107): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd-bridge/dnsmasq.lxdbr0.leases" pid=22292 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Apr 6 12:55:06 franck-ThinkPad-T430s lxd-bridge.start[22255]: dnsmasq: ne peut ouvrir ou créer le fichiers de baux /var/lib/lxd-bridge//dnsmasq.lxdbr0.leases : Permission non accordée Of course, switching to complain mode works the problem around, but maybe allowing write to /var/lib/lxd-bridge/ would be a good idea (disclaimer: I'm not a security expert). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor-profiles 2.10-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 6 17:34:12 2016 InstallationDate: Installed on 2015-10-04 (185 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet splash vt.handoff=7 SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.bin.ping: [modified] modified.conffile..etc.apparmor.d.sbin.klogd: [modified] modified.conffile..etc.apparmor.d.sbin.syslog.ng: [modified] modified.conffile..etc.apparmor.d.sbin.syslogd: [modified] modified.conffile..etc.apparmor.d.usr.bin.chromium.browser: [modified] modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified] modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified] modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified] modified.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: [modified] mtime.conffile..etc.apparmor.d.bin.ping: 2015-10-05T12:02:58.049761 mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535 mtime.conffile..etc.apparmor.d.sbin.syslog.ng: 2015-10-05T12:03:21.918041 mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968 mtime.conffile..etc.apparmor.d.usr.bin.chromium.browser: 2015-10-05T12:02:05.273141 mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2015-10-05T11:59:18.903198 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-06T17:25:47.252257 mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323 mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403 mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523 mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794 mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2015-10-05T12:00:17.355879 mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981 mtime.conffile..etc.apparmor.d.usr.sbin.smbldap.useradd: 2015-10-05T12:00:35.504091 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1566944 Title: dnsmasq profile prevents LDX container to launch Status in apparmor package in Ubuntu: New Bug description: LXD 2.0 has dropped lxcbr0 for lxdbr0 as its default bridge configuration. Since then, having usr.sbin.dnsmasq profile in enforce mode will prevent LXD containers to launch: Apr 6 12:55:06 franck-ThinkPad-T430s kernel: [ 7029.101587] audit: type=1400 audit(1459940106.552:107): apparmor="DENIED" operation="mknod" profile="/usr/sbin/dnsmasq" name="/var/lib/lxd-bridge/dnsmasq.lxdbr0.leases" pid=22292 comm="dnsmasq" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Apr 6 12:55:06 franck-ThinkPad-T430s lxd-bridge.start[22255]: dnsmasq: ne peut ouvrir ou créer le fichiers de baux /var/lib/lxd-bridge//dnsmasq.lxdbr0.leases : Permission non accordée Of course, switching to complain mode works the problem around, but maybe allowing write to /var/lib/lxd-bridge/ would be a good idea (disclaimer: I'm not a security expert). ProblemType: Bug DistroRelease: U
[Touch-packages] [Bug 1551623] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) ** Affects: gconf (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 gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 566914] Re: Bluetooth HID barcode reader drops digits (code128)
In 2016, the problem still exists with some wireless scanner. The exact same thing is happening to me, and I can't find a way to fix it. Help would be welcome if anyone wants to dig onto this subject. -- 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/566914 Title: Bluetooth HID barcode reader drops digits (code128) Status in bluez package in Ubuntu: Confirmed Bug description: Binary package hint: bluez I apologize is if this the wrong place or format for the report. This is my first bug report. An HID bluetooth barcode reader scanning Code128 barcodes (and possibly other symbologies) will drop repeating digits if they are less than 8 digits apart. This does NOT happen if the repeating digits are back to back. Example the number encoded in a code128 barcode then scanned with a bluetooth HID barcode reader: -"1234567890" will properly return "1234567890" -"10" will properly return "10" -"100" will properly return 100 (the repeating zero's are back to back, so no problem) -"1010" will IMPROPERLY return "10" -"10101" will IMPROPERLY return "10" -"101010" will IMPROPERLY return "10" -"1010101" will IMPROPERLY return "10" -"10101010" will IMPROPERLY return "100" (yes 100) The test system has a USB (Anycom or Trendnet) bluetooth USB dongles with an Intermec sf51 bluetooth HID barcode scanner successfully paired (as HID profile) to the Ubuntu system. Using USBMON in debug I can see the all of the proper digits coming across in hex. There are no dropped digits. I then used HCIDump and again saw all the digits coming across without loss. Using Showkey shows the problem I believe. Scanning the barcode "1010" shows this in showkey: keycode 2 press keycode 11 press keycode 2 release keycode 11 release Keycode 2 is "1" and Keycode 11 is "0". More complex numbers better illustrate the problem: Scanning the barcode "L003184192" returns "L00318492". The "1" is missing.This is what appears in showkey (I've added the ASCII letter after the "press" or "release" statement from showkey for this example text): keycode 42 press (shift) keycode 38 press (L) keycode 42 release (shift) keycode 38 release (L) keycode 11 press (0) keycode 11 release (0) keycode 11 press (0) keycode 4 press (3) keycode 2 press (1) keycode 9 press (8) keycode 5 press (4) keycode 10 press (10) keycode 11 release (0) keycode 4 release (3) keycode 2 release (1) keycode 9 release (8) keycode 5 release (4) keycode 10 release (9) keycode 3 press (2) keycode 3 release (2) What looks to be happening is that the missing "1" key is "pressed" at the beginning of the input and is not "released" in time to be "pressed" again. This bug has existed in Ubuntu in all versions I've tried back to 7.10 (and confirmed in 8.10, 9.04 and 10.2 beta). --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: Dell Computer Corporation Dimension 4550 Package: bluez 4.60-0ubuntu8 [modified: lib/udev/rules.d/97-bluetooth.rules] PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=5e6ab2fa-2a8c-430a-89f3-63ffc056c7f8 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic Tags: lucid Uname: Linux 2.6.32-16-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/23/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A08 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA08:bd09/23/2003:svnDellComputerCorporation:pnDimension4550:pvr:rvnDellComputerCorp.:rn:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4550 dmi.sys.vendor: Dell Computer Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:16:38:C9:95:4C ACL MTU: 1017:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1863 acl:29 sco:0 events:45 errors:0 TX bytes:612 acl:10 sco:0 commands:33 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/566914/+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 1499711] Re: System stopped adjusting display settings when a new display is plugged in
Changed to gnome-system-monitor, as I think this is the component driving the display settings changes (but I might be wrong) ** Package changed: ubuntu-settings (Ubuntu) => gnome-system-monitor (Ubuntu) -- 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/1499711 Title: System stopped adjusting display settings when a new display is plugged in Status in gnome-system-monitor package in Ubuntu: New Bug description: Since I upgraded to wily (beta), my laptop stopped adjusting display settings when I dock or undock it (with an external display attached to the docking station), or even when I attached a new display directly on the laptop. Expected result: when I dock my laptop, the system recognizes the new configuration and applies the corresponding display settings Actual result: nothing happens For example, when docked, I have the laptop main display off, and the external monitor on. When I undock, the main display stays off, until I... (see below) To get the setting applied, I have to either: - open the System settings application. No need to change anything, nor to choose Display settings, simply opening the general settings app makes it work. - or: switch to console and back to X (ctrl+alt+F6 / Ctrl+F7) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 25 14:23:55 2015 InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1499711/+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 1499711] Re: System stopped adjusting display settings when a new display is plugged in
Tested with the dock by plugging a display directly on the VGA port: nothing happens, ie I have to go into settings to have the external display recognized. ** Summary changed: - System stopped adjusting display settings when docking/undocking + System stopped adjusting display settings when a new display is plugged in ** Description changed: Since I upgraded to wily (beta), my laptop stopped adjusting display settings when I dock or undock it (with an external display attached to - the docking station). + the docking station), or even when I attached a new display directly on + the laptop. - To get the setting applied, I have to open the System settings - application. No need to change anything, nor to choose Display settings, - simply opening the the general settings app makes it work. + Expected result: when I dock my laptop, the system recognizes the new + configuration and applies the corresponding display settings + + Actual result: nothing happens + For example, when docked, I have the laptop main display off, and the external monitor on. When I undock, the main display stays off, until I... (see below) + + To get the setting applied, I have to either: + - open the System settings application. No need to change anything, nor to choose Display settings, simply opening the general settings app makes it work. + - or: switch to console and back to X (ctrl+alt+F6 / Ctrl+F7) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 25 14:23:55 2015 InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) ** Tags added: regression-release -- 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/1499711 Title: System stopped adjusting display settings when a new display is plugged in Status in ubuntu-settings package in Ubuntu: New Bug description: Since I upgraded to wily (beta), my laptop stopped adjusting display settings when I dock or undock it (with an external display attached to the docking station), or even when I attached a new display directly on the laptop. Expected result: when I dock my laptop, the system recognizes the new configuration and applies the corresponding display settings Actual result: nothing happens For example, when docked, I have the laptop main display off, and the external monitor on. When I undock, the main display stays off, until I... (see below) To get the setting applied, I have to either: - open the System settings application. No need to change anything, nor to choose Display settings, simply opening the general settings app makes it work. - or: switch to console and back to X (ctrl+alt+F6 / Ctrl+F7) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 25 14:23:55 2015 InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1499711/+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 1499711] [NEW] System stopped adjusting display settings when docking/undocking
Public bug reported: Since I upgraded to wily (beta), my laptop stopped adjusting display settings when I dock or undock it (with an external display attached to the docking station). To get the setting applied, I have to open the System settings application. No need to change anything, nor to choose Display settings, simply opening the the general settings app makes it work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 25 14:23:55 2015 InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1499711 Title: System stopped adjusting display settings when docking/undocking Status in ubuntu-settings package in Ubuntu: New Bug description: Since I upgraded to wily (beta), my laptop stopped adjusting display settings when I dock or undock it (with an external display attached to the docking station). To get the setting applied, I have to open the System settings application. No need to change anything, nor to choose Display settings, simply opening the the general settings app makes it work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-lowlatency 4.2.1 Uname: Linux 4.2.0-11-lowlatency x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 25 14:23:55 2015 InstallationDate: Installed on 2014-12-13 (285 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-09-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1499711/+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 1457361] Re: Clipboard clear method crashes and Pushing data straight to clipboard is not working
I can confirm that Clipboard.clear() also consistently crashes my app... worked it around by pushing , but not sure if it will really wipe out my previously pushed data (or if it is a stack...) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1457361 Title: Clipboard clear method crashes and Pushing data straight to clipboard is not working Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: - I tried to call the Clipboard.clear() method, and it crashes my application for 100% sure. - I tried the 2. Pushing data straight to clipboard method on page: https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Clipboard/ it does not work at all. The method 1/3 work fine. I have my test code: https://gitcafe.com/ubuntu/clipboard/tree/master You can check it out by running: git clone https://gitcafe.com/ubuntu/clipboard.git The test phone image is: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 195 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-05-12 14:52:33 version version: 195 version ubuntu: 20150512 version device: 20150210 version custom: 20150508 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457361/+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 420411] Re: vpn connection handshake times out too soon
I just did send a message on NM list to raise this issue: https://mail.gnome.org/archives/networkmanager- list/2015-April/msg7.html -- 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/420411 Title: vpn connection handshake times out too soon Status in network-manager package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager-openvpn NetworkManager only waits 40 seconds for the VPN to come up. This is too short when using a slow connection as for instance a 64kbps GPRS connection. Calling openvpn manually also timeouts sometimes with the default timeout (60s?), but I am able to override it using the connect- timeout option in the configuration file and solve the problem. ProblemType: Bug Architecture: i386 Date: Fri Aug 28 10:55:21 2009 DistroRelease: Ubuntu 9.10 Package: network-manager-openvpn 0.7.1-0ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-7.27-generic SourcePackage: network-manager-openvpn Uname: Linux 2.6.31-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/420411/+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 1432599] Re: Network-manager tries to manage virbr0, which it should not
Here is the feedback I got from the network-manager mailing list: On Thu, 2015-03-19 at 09:18 +0100, Franck Routier (perso) wrote: Hi list, I'm using Ubuntu and just upgraded to (still in development) Vivid. Now I see that network-manager handles my virbr0 bridge (libvirt), which it didn't before. NM will recognize and manage all network interfaces, but that does not mean that NM actually touches the interfaces. If the interface already has a configuration, NM simply assumes the existing configuration and waits for you to tell it to do something. That's a difference from older versions of NM (0.9.8 and earlier) where NM was mostly ignorant of existing configuration. We know that NM 0.9.10 still has a few edge cases where it touches interfaces and shouldn't, but almost all of those have already been fixed in NM 1.0 and later. Dan -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Unknown Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1432599] Re: Network-manager tries to manage virbr0, which it should not
The /etc/NetworkManager/NetworkManager.conf [keyfile] unmanaged-devices=interface-name:virbr0 indeed does the trick. -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Fedora: Unknown Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1434525] Re: Router solicitation blocked, makes network-manager complain
Adding allow router-solicatation and router-advertisement in before6-output seems to solve the problem. It also seems pretty legit as of 4.3.3, 4.4.1 and A7 of http://www.ietf.org/rfc/rfc4890.txt That said, I'm not a networking security expert, this needs reviewing :-) ** Patch added: Allow router sollication before output https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1434525/+attachment/4358616/+files/allow-icmpv6-router-sollication-before-output.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1434525 Title: Router solicitation blocked, makes network-manager complain Status in ufw package in Ubuntu: New Bug description: In Vivid, my syslog is full of complains by network-manager about blocked Router solicitation. In my log, I get things like this: ... Mar 20 12:47:04 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852024.960398] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:04 franck-ThinkPad-T430s kernel: [ 8209.218586] [UFW BLOCK] IN= OUT=wlan0 SRC=fe80::::2677:03ff:fe8a:47a0 DST=ff02:::::::0002 LEN=48 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0 Mar 20 12:47:05 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852025.959574] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:08 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852028.958727] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:09 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852029.958873] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:12 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852032.961342] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:13 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852033.959493] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:16 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852036.960008] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:17 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852037.959215] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:20 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852040.961811] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:21 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852041.958641] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:24 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852044.960743] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:24 franck-ThinkPad-T430s kernel: [ 8229.224325] [UFW BLOCK] IN= OUT=wlan0 SRC=fe80::::2677:03ff:fe8a:47a0 DST=ff02:::::::0002 LEN=48 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0 Mar 20 12:47:25 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852045.958895] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:28 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852048.960527] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. ... and so on. I have read through http://www.ietf.org/rfc/rfc4890.txt but this is a bit tougth, and I like ufw doing the job for me :-). Here is the output of ip6tables --list : Chain INPUT (policy DROP) target prot opt source destination ufw6-before-logging-input all anywhere anywhere ufw6-before-input all anywhere anywhere ufw6-after-input all anywhere anywhere ufw6-after-logging-input all anywhere anywhere ufw6-reject-input all anywhere anywhere ufw6-track-input all anywhere anywhere Chain FORWARD (policy DROP) target prot opt source destination ufw6-before-logging-forward all anywhere anywhere ufw6-before-forward all anywhere anywhere ufw6-after-forward all anywhere anywhere ufw6-after-logging-forward all anywhere anywhere ufw6-reject-forward all anywhere anywhere ufw6-track-forward all anywhere anywhere Chain OUTPUT (policy DROP) target
[Touch-packages] [Bug 1426316] Re: Java applets won't run in Firefox with Apparmor profile activated
Seth, yes this is contradictory. In fact I had many DENIED messages, as
you might have seen here http://askubuntu.com/questions/586611/apparmor-
problem-icedtea-plugin-freezes-firefox-35-0-1
But finally, only adding rw to owner /run/user/*/icedteaplugin-*/* did
the trick for me.
Regarding the other modifications I made, there all are in my
local/usr.bin.firefox:
# Site-specific additions and overrides for usr.bin.firefox.
# For more details, please see /etc/apparmor.d/local/README.
# Allow keyring integration to work
dbus (send,receive)
bus=session
interface=org.freedesktop.DBus.Properties
path=/org/freedesktop/secrets,
dbus (send,receive)
bus=session
interface=org.freedesktop.Secret.Service
path=/org/freedesktop/secrets,
dbus (send,receive)
bus=session
interface=org.freedesktop.Secret.Item
path=/org/freedesktop/secrets/**/*,
dbus (send,receive)
bus=session
interface=org.freedesktop.DBus.Properties
path=/org/freedesktop/secrets/collection/mozilla/*,
dbus (send,receive)
bus=session
interface=org.freedesktop.DBus.Properties
path=/org/freedesktop/secrets/collection/mozilla,
dbus (send,receive)
bus=session
interface=org.freedesktop.Secret.Prompt
path=/org/freedesktop/secrets/prompt/*,
@{HOME}/.cache/mozilla/firefox/**/safebrowsing-to_delete/*.sbstore rw,
deny dbus
interface=org.gtk.vfs.MountTracker,
deny /tmp/.ICE-unix/* rw,
Everything regarding dbus is related to a gnome-keyring-integration plugin I
use (https://github.com/swick/moz-gnome-keyring-integration).
Last two line are here to avoid noisy notifications.
Reagards,
Franck
--
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/1426316
Title:
Java applets won't run in Firefox with Apparmor profile activated
Status in apparmor package in Ubuntu:
New
Bug description:
After activating firefox profile, be it in complain or enforce mode,
no applet will run with OpenJDK.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1426316/+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 1426316] Re: Applets won't run with Apparmor profile activated
Here is my proposed patch.
I'm not an apparmor expert, so this need review, but it works for me(TM).
** Patch added: Add owner /run/user/*/icedteaplugin-*/* rw, to allow java
plugins execution
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1426316/+attachment/4357231/+files/browser-allow-java.diff
** Summary changed:
- Applets won't run with Apparmor profile activated
+ Java applets won't run in Firefox with Apparmor profile activated
--
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/1426316
Title:
Java applets won't run in Firefox with Apparmor profile activated
Status in apparmor package in Ubuntu:
New
Bug description:
After activating firefox profile, be it in complain or enforce mode,
no applet will run.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1426316/+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 1426316] Re: Java applets won't run in Firefox with Apparmor profile activated
** Description changed:
After activating firefox profile, be it in complain or enforce mode, no
- applet will run.
+ applet will run with OpenJDK.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
--
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/1426316
Title:
Java applets won't run in Firefox with Apparmor profile activated
Status in apparmor package in Ubuntu:
New
Bug description:
After activating firefox profile, be it in complain or enforce mode,
no applet will run with OpenJDK.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1426316/+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 1426307] Re: location is inaccurate
I'm affected as well, on a BQ Aquaris (update version 20). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate Status in the base for Ubuntu mobile products: Confirmed Status in location-service package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Location is inaccurate, it thinks that I'm several kilometres away from my actual location, in the middle of the sea. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Fri Feb 27 11:10:42 2015 InstallationDate: Installed on 2015-02-25 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1434525] [NEW] Router solicitation blocked, makes network-manager complain
Public bug reported: In Vivid, my syslog is full of complains by network-manager about blocked Router solicitation. In my log, I get things like this: ... Mar 20 12:47:04 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852024.960398] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:04 franck-ThinkPad-T430s kernel: [ 8209.218586] [UFW BLOCK] IN= OUT=wlan0 SRC=fe80::::2677:03ff:fe8a:47a0 DST=ff02:::::::0002 LEN=48 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0 Mar 20 12:47:05 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852025.959574] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:08 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852028.958727] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:09 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852029.958873] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:12 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852032.961342] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:13 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852033.959493] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:16 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852036.960008] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:17 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852037.959215] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:20 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852040.961811] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:21 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852041.958641] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:24 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852044.960743] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. Mar 20 12:47:24 franck-ThinkPad-T430s kernel: [ 8229.224325] [UFW BLOCK] IN= OUT=wlan0 SRC=fe80::::2677:03ff:fe8a:47a0 DST=ff02:::::::0002 LEN=48 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0 Mar 20 12:47:25 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852045.958895] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (eth0): cannot send router solicitation: -1. Mar 20 12:47:28 franck-ThinkPad-T430s NetworkManager[1134]: error [1426852048.960527] [rdisc/nm-lndp-rdisc.c:241] send_rs(): (wlan0): cannot send router solicitation: -1. ... and so on. I have read through http://www.ietf.org/rfc/rfc4890.txt but this is a bit tougth, and I like ufw doing the job for me :-). Here is the output of ip6tables --list : Chain INPUT (policy DROP) target prot opt source destination ufw6-before-logging-input all anywhere anywhere ufw6-before-input all anywhere anywhere ufw6-after-input all anywhere anywhere ufw6-after-logging-input all anywhere anywhere ufw6-reject-input all anywhere anywhere ufw6-track-input all anywhere anywhere Chain FORWARD (policy DROP) target prot opt source destination ufw6-before-logging-forward all anywhere anywhere ufw6-before-forward all anywhere anywhere ufw6-after-forward all anywhere anywhere ufw6-after-logging-forward all anywhere anywhere ufw6-reject-forward all anywhere anywhere ufw6-track-forward all anywhere anywhere Chain OUTPUT (policy DROP) target prot opt source destination ufw6-before-logging-output all anywhere anywhere ufw6-before-output all anywhere anywhere ufw6-after-output all anywhere anywhere ufw6-after-logging-output all anywhere anywhere ufw6-reject-output all anywhere anywhere ufw6-track-output all anywhere anywhere Chain ufw6-after-forward (1 references) target prot opt source destination Chain ufw6-after-input (1 references) target prot opt source destination ufw6-skip-to-policy-input udp anywhere anywhere udp dpt:netbios-ns ufw6-skip-to-policy-input udp
[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
Here is a bug report, related to the subject: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged, unlike virbr0. ** Bug watch added: GNOME Bug Tracker #731014 https://bugzilla.gnome.org/show_bug.cgi?id=731014 -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5
This also happen with libvirtd apparmor profile in enforce mode: virtual machines (ie sub profiles with libvirt-someUUID) will constantly complain they are denied read access to /dev/shm/lttng-ust-wait-5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1404302 Title: liblttng-ust0 Error opening shm /lttng-ust-wait-5 Status in Platform API: New Status in QT Ubuntu: New Status in ust package in Ubuntu: Confirmed Bug description: Confined apps don't have access to this and continuously produce this error message in stderr: libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) This is printed to the application's log about once every other second and makes it hard to read the application's own debug output. For a better app developer experience this message should be silenced. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1404302/+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 1432599] Re: Network-manager tries to manage virbr0, which it should not
** Description changed: - Since a recent upgrade in vivid, nm is tryoing to manage virbr0. This + Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: - default via 10.0.0.1 dev eth0 proto static metric 1024 - 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 - 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 + default via 10.0.0.1 dev eth0 proto static metric 1024 + 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 + 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1432599] [NEW] Network-manager tries to manage virbr0, which it should not
Public bug reported: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1426316] [NEW] Applets won't run with Apparmor profile activated
Public bug reported:
After activating firefox profile, be it in complain or enforce mode, no
applet will run.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
--
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/1426316
Title:
Applets won't run with Apparmor profile activated
Status in apparmor package in Ubuntu:
New
Bug description:
After activating firefox profile, be it in complain or enforce mode,
no applet will run.
The culprit seems to be:
apparmor=DENIED operation=open
profile=/usr/lib/firefox/firefox{,[^s][^h]}//browser_openjdk
name=/run/user/1000/dconf/user pid=11973 comm=64636F6E6620776F726B6572
requested_mask=wrc denied_mask=wrc fsuid=1000 ouid=1000
The rules that prevent the applets to run belong to Apparmor
abstractions, specifically /etc/apparmor.d/abstractions/ubuntu-
browser.d/java
These rules will be enforced, even when usr.in.firefox is in complain
mode (I don't know why exactly)
Adding write access to the line
owner /run/user/*/icedteaplugin-*/ rw
in /etc/apparmor.d/abstractions/ubuntu-browser.d/java
seems to solve the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: apparmor-profiles 2.8.98-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-31.41-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 27 11:05:20 2015
InstallationDate: Installed on 2014-12-13 (75 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-31-lowlatency
root=/dev/mapper/ubuntu--vg-lv--root ro threadirqs quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog: Feb 27 09:42:45 franck-ThinkPad-T430s dbus[3940]: apparmor=DENIED
operation=dbus_method_call bus=session path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=Hello mask=send
name=org.freedesktop.DBus pid=9748
profile=/usr/lib/firefox/firefox{,*[^s][^h]}//browser_openjdk
peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.traceroute: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2015-02-20T14:58:28.130461
mtime.conffile..etc.apparmor.d.usr.sbin.traceroute: 2015-02-20T15:04:02.437880
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1426316/+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 1293439] Re: Apparmor prevents icedtea-7-plugin from creating necessary files
I'm still stuck... (see
http://askubuntu.com/questions/586611/icedtea-plugin-freezes-firefox-35-0-1-probable-apparmor-problem)
Did the fix land into 14.10 ?
--
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/1293439
Title:
Apparmor prevents icedtea-7-plugin from creating necessary files
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
Apparmor prevents icedtea-7-plugin from creating
/run/user/UID/icedteaplugin-login-random/, needed to work:
Mar 17 10:48:52 ad2 kernel: [2831863.964092] type=1400
audit(1395046132.183:851): apparmor=DENIED operation=mkdir
parent=6425 profile=/usr/lib/firefox/firefox{,*[^s][^h]}
name=/run/user/1000/icedteaplugin-pseudo-7DURO0/ pid=30285 comm
=plugin-containe requested_mask=c denied_mask=c fsuid=1000
ouid=1000
~ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
~ apt-cache policy apparmor
apparmor:
Installed: 2.8.0-0ubuntu31.1
Candidate: 2.8.0-0ubuntu31.1
Version table:
*** 2.8.0-0ubuntu31.1 0
500 http://archive.ubuntu.com/ubuntu/ saucy-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.8.0-0ubuntu31 0
500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: apparmor 2.8.0-0ubuntu31.1
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Mon Mar 17 10:59:53 2014
MarkForUpload: True
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
root=UUID=16001ea5-4e94-44ae-9838-da89b0f3f88e ro
SourcePackage: apparmor
Syslog:
UpgradeStatus: Upgraded to saucy on 2013-09-10 (187 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1293439/+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 1404694] [NEW] Version in 14.10 fails to ssh into virtual devices due to cipher incompatibility
Public bug reported: With ubuntu-sdk from default utopic repositories, testing or deploying to a (virtual) device fails due to some ssh cipher incompatibilities: Connecting to host... SSH connection failure: SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc. Server list was aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com. Device test failed. Upgrading to the version found in ppa:ubuntu-sdk-team/ppa. ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1404694 Title: Version in 14.10 fails to ssh into virtual devices due to cipher incompatibility Status in ubuntu-touch-meta package in Ubuntu: New Bug description: With ubuntu-sdk from default utopic repositories, testing or deploying to a (virtual) device fails due to some ssh cipher incompatibilities: Connecting to host... SSH connection failure: SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc. Server list was aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com. Device test failed. Upgrading to the version found in ppa:ubuntu-sdk-team/ppa. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1404694/+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 1404694] Re: Version in 14.10 fails to ssh into virtual devices due to cipher incompatibility
** Description changed: With ubuntu-sdk from default utopic repositories, testing or deploying to a (virtual) device fails due to some ssh cipher incompatibilities: Connecting to host... SSH connection failure: SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc. Server list was aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com. Device test failed. - Upgrading to the version found in ppa:ubuntu-sdk-team/ppa. + Upgrading to the version found in ppa:ubuntu-sdk-team/ppa solves the + issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1404694 Title: Version in 14.10 fails to ssh into virtual devices due to cipher incompatibility Status in ubuntu-touch-meta package in Ubuntu: New Bug description: With ubuntu-sdk from default utopic repositories, testing or deploying to a (virtual) device fails due to some ssh cipher incompatibilities: Connecting to host... SSH connection failure: SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc. Server list was aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com. Device test failed. Upgrading to the version found in ppa:ubuntu-sdk-team/ppa solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1404694/+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 1394982] Re: ubuntu-emulator fails to create a device: Unable to mount temp dir
*** This bug is a duplicate of bug 1401019 *** https://bugs.launchpad.net/bugs/1401019 ** This bug has been marked a duplicate of bug 1401019 ubuntu-emulator fails to create a device: Unable to mount temp dir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1394982 Title: ubuntu-emulator fails to create a device: Unable to mount temp dir Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Ubuntu 14.10. I am trying to create a device emulator from ubuntu-sdk, but it fails. Trying to do it directly using ubuntu emulator, I get this message: T430s:~$ sudo ubuntu-emulator create utouch Creating utouch from ubuntu-touch/devel revision 243 Downloading... Setting up... Unable to mount temp dir to create system image mount: /home/franck/.local/share/ubuntu-emulator/utouch/ubuntu-system.img is not a block device (maybe try `-o loop'?) Looking at the directory, I get: T430s:~$ ls -l .local/share/ubuntu-emulator/utouch/ total 198736 -rw-r--r-- 1 franck franck 4294967296 nov. 21 14:08 sdcard.img -rw-r--r-- 1 franck franck 3221225472 nov. 21 14:08 ubuntu-system.img To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1394982/+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 1394982] [NEW] ubuntu-emulator fails to create a device: Unable to mount temp dir
Public bug reported: I am trying to create a device emulator from ubuntu-sdk, but it fails. Trying to do it directly using ubuntu emulator, I get this message: T430s:~$ sudo ubuntu-emulator create utouch Creating utouch from ubuntu-touch/devel revision 243 Downloading... Setting up... Unable to mount temp dir to create system image mount: /home/franck/.local/share/ubuntu-emulator/utouch/ubuntu-system.img is not a block device (maybe try `-o loop'?) Looking at the directory, I get: T430s:~$ ls -l .local/share/ubuntu-emulator/utouch/ total 198736 -rw-r--r-- 1 franck franck 4294967296 nov. 21 14:08 sdcard.img -rw-r--r-- 1 franck franck 3221225472 nov. 21 14:08 ubuntu-system.img ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1394982 Title: ubuntu-emulator fails to create a device: Unable to mount temp dir Status in “ubuntu-touch-meta” package in Ubuntu: New Bug description: I am trying to create a device emulator from ubuntu-sdk, but it fails. Trying to do it directly using ubuntu emulator, I get this message: T430s:~$ sudo ubuntu-emulator create utouch Creating utouch from ubuntu-touch/devel revision 243 Downloading... Setting up... Unable to mount temp dir to create system image mount: /home/franck/.local/share/ubuntu-emulator/utouch/ubuntu-system.img is not a block device (maybe try `-o loop'?) Looking at the directory, I get: T430s:~$ ls -l .local/share/ubuntu-emulator/utouch/ total 198736 -rw-r--r-- 1 franck franck 4294967296 nov. 21 14:08 sdcard.img -rw-r--r-- 1 franck franck 3221225472 nov. 21 14:08 ubuntu-system.img To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1394982/+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 1394982] Re: ubuntu-emulator fails to create a device: Unable to mount temp dir
** Description changed: + Ubuntu 14.10. + I am trying to create a device emulator from ubuntu-sdk, but it fails. Trying to do it directly using ubuntu emulator, I get this message: - T430s:~$ sudo ubuntu-emulator create utouch Creating utouch from ubuntu-touch/devel revision 243 Downloading... Setting up... Unable to mount temp dir to create system image mount: /home/franck/.local/share/ubuntu-emulator/utouch/ubuntu-system.img is not a block device (maybe try `-o loop'?) Looking at the directory, I get: T430s:~$ ls -l .local/share/ubuntu-emulator/utouch/ total 198736 -rw-r--r-- 1 franck franck 4294967296 nov. 21 14:08 sdcard.img -rw-r--r-- 1 franck franck 3221225472 nov. 21 14:08 ubuntu-system.img -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1394982 Title: ubuntu-emulator fails to create a device: Unable to mount temp dir Status in “ubuntu-touch-meta” package in Ubuntu: New Bug description: Ubuntu 14.10. I am trying to create a device emulator from ubuntu-sdk, but it fails. Trying to do it directly using ubuntu emulator, I get this message: T430s:~$ sudo ubuntu-emulator create utouch Creating utouch from ubuntu-touch/devel revision 243 Downloading... Setting up... Unable to mount temp dir to create system image mount: /home/franck/.local/share/ubuntu-emulator/utouch/ubuntu-system.img is not a block device (maybe try `-o loop'?) Looking at the directory, I get: T430s:~$ ls -l .local/share/ubuntu-emulator/utouch/ total 198736 -rw-r--r-- 1 franck franck 4294967296 nov. 21 14:08 sdcard.img -rw-r--r-- 1 franck franck 3221225472 nov. 21 14:08 ubuntu-system.img To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1394982/+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
