[Touch-packages] [Bug 1120526] Re: dbus session file contains wrong DBUS_SESSION_BUS_ADDRESS
almost 2 years later still have the problem:
$ (env; cat ~/.dbus/session-bus/$(cat /var/lib/dbus/machine-id)-0 )|awk -F','
'/^DBUS_SESSION_BUS_ADDRESS/ {print $1}'
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-jYz33365w2
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Xjd2ntrMtE
two lines should be equal.
dbus-x11 1.6.18-0ubuntu4.3
$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1120526
Title:
dbus session file contains wrong DBUS_SESSION_BUS_ADDRESS
Status in dbus package in Ubuntu:
Confirmed
Bug description:
DBUS_SESSION_BUS_ADDRESS set in my environment does not equal to the
same variable stored in a session file:
alex@ubuntu:~$ export | sed -nr 's/.*(DBUS.*$)/\1/p';cat
~/.dbus/session-bus/*-0|grep ^DBUS_SESSION_BUS_ADDRESS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Bu4OYHdSFn,guid=f7abf2c2b9d6766557e8af8751165edd
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-NbHVDbZxgk,guid=2f3019531be02ea75556ae3451165edd
(only one file exist in the ~/.dbus/session-bus).
In 12.04 they were the same
This bug prevent dbus-send command to work if started by a cron.
dbus-x11 - 1.6.4-1ubuntu4
alex@ubuntu:~$ lsb_release -rd
Description: Ubuntu 12.10
Release: 12.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1120526/+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 1407400] [NEW] WLAN interface throughput drops thanks to NetworkManager
Public bug reported: Here I have a pic of the wifi periodic drops http://i.imgur.com/JhRVP8F.png. Server is connected to the router per LAN. I'm connecting to the server through the router's WLAN. Bytes are transferred in one direction using nc. The graph at the top is the CPU load on the router, another one below is the router's wlan1(5GHz) iface throughput in MB/s. I thought that the router is guilty so I measured cpu and wlan iface statistics on the router. But it turned out that the problem lies on the client side and on the NetworkManager to be precise. As these drops happens exactly with 120s periodicity I assume that it's the background station scanning nm does even when connected to a station! To prove that the nm is to blame I deactivated it and activated the wlan iface manually. And here is how it looks like without nm - http://i.imgur.com/UWdUg4y.png I consider this bug as major. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1407400 Title: WLAN interface throughput drops thanks to NetworkManager Status in network-manager package in Ubuntu: New Bug description: Here I have a pic of the wifi periodic drops http://i.imgur.com/JhRVP8F.png. Server is connected to the router per LAN. I'm connecting to the server through the router's WLAN. Bytes are transferred in one direction using nc. The graph at the top is the CPU load on the router, another one below is the router's wlan1(5GHz) iface throughput in MB/s. I thought that the router is guilty so I measured cpu and wlan iface statistics on the router. But it turned out that the problem lies on the client side and on the NetworkManager to be precise. As these drops happens exactly with 120s periodicity I assume that it's the background station scanning nm does even when connected to a station! To prove that the nm is to blame I deactivated it and activated the wlan iface manually. And here is how it looks like without nm - http://i.imgur.com/UWdUg4y.png I consider this bug as major. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1407400/+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 1522922]
(In reply to Mika Kahola from comment #54) > These patches apply to drm-intel-nightly kernel which is a development tree > for i915 driver. You can clone the git repository from > > https://01.org/linuxgraphics/documentation/development/source-code > > and apply these patches on top of it. I'm afraid, this is the only option at > the moment to get these issues fixed. Eventually, these patches will be > upstreamed as fixes. well, eventually means it could take halve a year until we got those patches which makes our computers useless. I can also add that on my computer I cannot enable vesa mode and i915.modeset=0 option makes the screen black, i.e. bricks it. Reverting two patches for the ubuntu's 4.2.0.19 kernel like it was described above doesn't help either. I tried to figure out how to apply your patch onto 4.2.0.19 but it seems like training staff was moved out of the intel_dp.c and some files are missing completely, so no luck. Cloning the 1Gigabyte git repo like you suggest would also mean that I'd need to compile drm driver code with the kernel version that in that repo too right? Or I can copy the gpu/drm/i915 over to my kernel version and it'll work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1522922 Title: Screen flickering in Intel i915 driver Status in Nouveau Xorg driver: Incomplete Status in libdrm package in Ubuntu: Confirmed Bug description: There's an upstream bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen flickering when using the Intel i915 builtin driver (at resolutions lower than the maximal one). I think that it will be fixed in newer kernel versions, but for the time being, as reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as personally tested) reverting those two commits fixes the problem. Would that be possible to release a fixed version for the 4.2.0 stream? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bettini1378 F pulseaudio /dev/snd/controlC1: bettini1378 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 4 19:01:00 2015 HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9 InstallationDate: Installed on 2015-05-08 (210 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1522922/+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 1522922]
patch https://patchwork.freedesktop.org/patch/66697/ DOESN'T solve the
flickering problem on my computer.
What I did:
1. installed generic kernel and headers from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2015-12-24-wily/
2. get the sources from the git://anongit.freedesktop.org/drm-intel branch
drm-intel-nightly (commit number: ec0382c73cb1adc972bebdd94afad3f0ea117114)
3. applied the patch https://patchwork.freedesktop.org/patch/66697/
4. compiled the i915 driver and installed it:
mykern=${1:-$(uname -r)}
cp /usr/src/linux-headers-$mykern/Module.symvers .
# Prep tree
cp /boot/config-$mykern ./.config
make oldconfig
make prepare
make modules_prepare
# Build only the needed directories
make SUBDIRS=drivers/gpu/drm/i915 modules
[ -s /lib/modules/$mykern/kernel/drivers/gpu/drm/i915/i915.ko.orig ] || sudo cp
/lib/modules/$mykern/kernel/drivers/gpu/drm/i915/i915.ko{,.orig}
sudo cp drivers/gpu/drm/i915/i915.ko
/lib/modules/$mykern/kernel/drivers/gpu/drm/i915/
5. reboot
But. Now with the kernel 4.4.xx if I run 'xset dpms force off' just
after the boot then the flicker is gone.
grep of the last boot syslog:
$ grep drm /tmp/syslog
Dec 24 11:29:49 chrome kernel: [2.028119] [drm] Initialized drm 1.1.0
20060810
Dec 24 11:29:49 chrome kernel: [2.066980] [drm] Memory usable by graphics
device = 4096M
Dec 24 11:29:49 chrome kernel: [2.066985] [drm] Replacing VGA console driver
Dec 24 11:29:49 chrome kernel: [2.067495] [drm] Supports vblank timestamp
caching Rev 2 (21.10.2013).
Dec 24 11:29:49 chrome kernel: [2.067498] [drm] Driver supports precise
vblank timestamp query.
Dec 24 11:29:49 chrome kernel: [2.067501] [drm] failed to find VBIOS tables
Dec 24 11:29:49 chrome kernel: [2.210886] [drm] Initialized i915 1.6.0
20151218 for :00:02.0 on minor 0
Dec 24 11:29:49 chrome kernel: [2.211478] fbcon: inteldrmfb (fb0) is
primary device
Dec 24 11:29:49 chrome kernel: [3.021978]
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to enable
link training
Dec 24 11:29:49 chrome kernel: [3.025516] [drm:intel_dp_start_link_train
[i915]] *ERROR* failed to start channel equalization
Dec 24 11:29:49 chrome kernel: [3.206466] i915 :00:02.0: fb0:
inteldrmfb frame buffer device
Dec 24 11:30:13 chrome kernel: [ 29.162270]
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to enable
link training
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1522922
Title:
Screen flickering in Intel i915 driver
Status in Nouveau Xorg driver:
Incomplete
Status in libdrm package in Ubuntu:
Confirmed
Bug description:
There's an upstream bug reported here
https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen
flickering when using the Intel i915 builtin driver (at resolutions
lower than the maximal one).
I think that it will be fixed in newer kernel versions, but for the
time being, as reported here
https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as
personally tested) reverting those two commits fixes the problem.
Would that be possible to release a fixed version for the 4.2.0
stream?
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-19-generic 4.2.0-19.23
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bettini1378 F pulseaudio
/dev/snd/controlC1: bettini1378 F pulseaudio
CurrentDesktop: KDE
Date: Fri Dec 4 19:01:00 2015
HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9
InstallationDate: Installed on 2015-05-08 (210 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Dell Precision M3800
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic
root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.2.0-19-generic N/A
linux-backports-modules-4.2.0-19-generic N/A
linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago)
dmi.bios.date: 08/17/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: Dell Precision M3800
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Dell Precision
[Touch-packages] [Bug 1522922]
> think Mika is on the right track, having solved the initial problem > (persistent flickering) by modifying the eDP link training. The remaining > problem is that the flickering recurs when the display resumes from sleep. in my case flickering occur just after reboot (and this is not the same flickerin art like in the video). Then I need to run 'xset dpms force off' command in the terminal at least once or many times until flickering is gone. Afterwards I see no flickering any longer even if it resumes from sleep. I can add that on the same hardware chromiumos works flawlessly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1522922 Title: Screen flickering in Intel i915 driver Status in Nouveau Xorg driver: Incomplete Status in libdrm package in Ubuntu: Confirmed Bug description: There's an upstream bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen flickering when using the Intel i915 builtin driver (at resolutions lower than the maximal one). I think that it will be fixed in newer kernel versions, but for the time being, as reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as personally tested) reverting those two commits fixes the problem. Would that be possible to release a fixed version for the 4.2.0 stream? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bettini1378 F pulseaudio /dev/snd/controlC1: bettini1378 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 4 19:01:00 2015 HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9 InstallationDate: Installed on 2015-05-08 (210 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1522922/+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 1522922]
> https://patchwork.freedesktop.org/patch/69394/ > https://patchwork.freedesktop.org/patch/69395/ > https://patchwork.freedesktop.org/patch/69396/ > > flux242 seems to have a clock recovery issue. This fix may provide a > solution for that as well. three patches above (without the https://patchwork.freedesktop.org/patch/66697/) do not help -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1522922 Title: Screen flickering in Intel i915 driver Status in Nouveau Xorg driver: Incomplete Status in libdrm package in Ubuntu: Confirmed Bug description: There's an upstream bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen flickering when using the Intel i915 builtin driver (at resolutions lower than the maximal one). I think that it will be fixed in newer kernel versions, but for the time being, as reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as personally tested) reverting those two commits fixes the problem. Would that be possible to release a fixed version for the 4.2.0 stream? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bettini1378 F pulseaudio /dev/snd/controlC1: bettini1378 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 4 19:01:00 2015 HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9 InstallationDate: Installed on 2015-05-08 (210 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1522922/+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 1650848] [NEW] Move evolution specific deps out of the bluez-obex
Public bug reported: I do not have eveolution installed so why do I have evolution-data- server-common and libedataserver-1.2-22 installed on my system? the package to fix is bluez-obexd I'm on Ubuntu 16.10 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1650848 Title: Move evolution specific deps out of the bluez-obex Status in bluez package in Ubuntu: New Bug description: I do not have eveolution installed so why do I have evolution-data- server-common and libedataserver-1.2-22 installed on my system? the package to fix is bluez-obexd I'm on Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1650848/+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 1685193] [NEW] [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log
Public bug reported:
this is rather weird problem but after upgrading to the 17.04 the pm-
powersave script I start by a udev rule stopped working. After debuggin
a bit I found a place that causes the error. In the /usr/lib/pm-utils
/pm-functions there's the init_logfile function that called exec to
redirect script's output to the /var/log/pm-powersave.log. And it fails
to do so because root (under which the script is started) has no
permission to write to anything under the /var/log/
Inside of that functions I added additional logging to prove that
1. the script is started under root
2. the file /var/log/pm-powersave.log exist and it has 644 permissions
3. the root can read from /var/log/*
4. /var permissions are 755, /var/log permissions are 775
If the script is started with 'sudo /usr/sbin/pm-powersave true' then it
works!
So what could this be? Could the apparmor prevent udevd to write to
/var/log ?
Temporary solution is to write to /tmp/pm-powersave.log
How to reproduce:
1. add the following rule to /etc/udev/rules.d/test.rules
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
2. create /usr/sbin/testudev script and make it executable
#!/usr/bin/env bash
logger "testudev: I'm: $(whoami)"
echo test >> /var/log/testudev.log
3. Plug and unplug the power plug. Check the syslog:
Apr 21 13:17:06 chrome root: testudev: I'm: root
Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev false'
failed with exit code 1.
** 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/1685193
Title:
[17.04] systemd-udevd. Scripts started by a rule won't write to
/var/log
Status in systemd package in Ubuntu:
New
Bug description:
this is rather weird problem but after upgrading to the 17.04 the pm-
powersave script I start by a udev rule stopped working. After
debuggin a bit I found a place that causes the error. In the /usr/lib
/pm-utils/pm-functions there's the init_logfile function that called
exec to redirect script's output to the /var/log/pm-powersave.log. And
it fails to do so because root (under which the script is started) has
no permission to write to anything under the /var/log/
Inside of that functions I added additional logging to prove that
1. the script is started under root
2. the file /var/log/pm-powersave.log exist and it has 644 permissions
3. the root can read from /var/log/*
4. /var permissions are 755, /var/log permissions are 775
If the script is started with 'sudo /usr/sbin/pm-powersave true' then
it works!
So what could this be? Could the apparmor prevent udevd to write to
/var/log ?
Temporary solution is to write to /tmp/pm-powersave.log
How to reproduce:
1. add the following rule to /etc/udev/rules.d/test.rules
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
2. create /usr/sbin/testudev script and make it executable
#!/usr/bin/env bash
logger "testudev: I'm: $(whoami)"
echo test >> /var/log/testudev.log
3. Plug and unplug the power plug. Check the syslog:
Apr 21 13:17:06 chrome root: testudev: I'm: root
Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev
false' failed with exit code 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685193/+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 1685193] Re: [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log
what are the intentions?
systemd power management huh? Which of these problems has already been
solved since 15.10 then:
1. System doesn't react on the power supply plugged/unplugged events
2. Lid close events are handled by the systemd by default and not by the
xfce4-power-manager
3. System doesn't execute pm-utils hooks on sleep/resume events, i.e when the
power cord is unplugged all powertop's tunable should be in GOOD state. Are
they?
--
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/1685193
Title:
[17.04] systemd-udevd. Scripts started by a rule won't write to
/var/log
Status in systemd package in Ubuntu:
Confirmed
Bug description:
this is rather weird problem but after upgrading to the 17.04 the pm-
powersave script I start by a udev rule stopped working. After
debuggin a bit I found a place that causes the error. In the /usr/lib
/pm-utils/pm-functions there's the init_logfile function that called
exec to redirect script's output to the /var/log/pm-powersave.log. And
it fails to do so because root (under which the script is started) has
no permission to write to anything under the /var/log/
Inside of that functions I added additional logging to prove that
1. the script is started under root
2. the file /var/log/pm-powersave.log exist and it has 644 permissions
3. the root can read from /var/log/*
4. /var permissions are 755, /var/log permissions are 775
If the script is started with 'sudo /usr/sbin/pm-powersave true' then
it works!
So what could this be? Could the apparmor prevent udevd to write to
/var/log ?
Temporary solution is to write to /tmp/pm-powersave.log
How to reproduce:
1. add the following rule to /etc/udev/rules.d/test.rules
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
2. create /usr/sbin/testudev script and make it executable
#!/usr/bin/env bash
logger "testudev: I'm: $(whoami)"
echo test >> /var/log/testudev.log
3. Plug and unplug the power plug. Check the syslog:
Apr 21 13:17:06 chrome root: testudev: I'm: root
Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev
false' failed with exit code 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685193/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I'm not sure if setting negative priority really solves the dns leaks problem because I'm on 17.10 and I do have dns leaks. If I'm connected to my ISP over a LTE network and the connection is unstable then it could happen that DNS queries will be sent over my ISP network and not over my VPN connection. The only solution that works for me currently is sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop Put the following line in the [main] section of your /etc/NetworkManager/NetworkManager.conf: dns=default Delete the symlink /etc/resolv.conf rm /etc/resolv.conf Restart network-manager sudo service network-manager restart Caution! Be aware that disabling systemd-resolvd might break name resolution in VPN for some users - according to the original thread https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved- in-ubuntu -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Fix Released Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
I dream of a world where after next lts upgrade my samba shares are still mountable! This isn't the first time, you know -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Bug description: 1) Release $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2) Package $ apt-cache policy libglib2.0-bin libglib2.0-bin: Installed: 2.64.1-1 Candidate: 2.64.1-1 Version table: *** 2.64.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected to happen The path should be mounted at /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/ 4) What happened instead: Error Message: gio: smb://192.168.178.1/PathName/: Location is not mountable 5) Long description / explanation Since some years, I mount a Windows drive with gio mount smb://192.168.178.1/PathName After upgrading from 19.04 to 20.04 beta, this does not work any more, I get the error message gio: smb://192.168.178.1/PathName/: Location is not mountable ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglib2.0-bin 2.64.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Apr 12 12:43:53 2020 InstallationDate: Installed on 2019-02-17 (420 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: glib2.0 UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+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 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages
no, it is an issue because packages are marked for automatic removal: x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput So you suggest to install all those packages extra afterwards instead of simply getting dependencies sorted out in the first place? so, I still think that xorg should not depend on apport - it simply doesn't belong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905775 Title: Uninstalling python3-apporrt should not uninstall xorg packages Status in xorg package in Ubuntu: New Bug description: ``` sudo apt purge python3-apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna python3-problem-report python3-requests python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: python3-apport* xorg* xserver-xorg* 0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded. After this operation, 1,070 kB disk space will be freed. Do you want to continue? [Y/n] ^C ``` so, apparently dependencies aren't correctly set, because I don't want to send no problem reports but still want to use xorg subsystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905775/+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 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages
i've just checked debian xorg package dependencies and no it doesn't depend on that problem reporting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905775 Title: Uninstalling python3-apporrt should not uninstall xorg packages Status in xorg package in Ubuntu: New Bug description: ``` sudo apt purge python3-apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna python3-problem-report python3-requests python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: python3-apport* xorg* xserver-xorg* 0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded. After this operation, 1,070 kB disk space will be freed. Do you want to continue? [Y/n] ^C ``` so, apparently dependencies aren't correctly set, because I don't want to send no problem reports but still want to use xorg subsystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905775/+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 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages
*** This bug is a duplicate of bug 1899971 *** https://bugs.launchpad.net/bugs/1899971 well, based on the reply from Timo Aaltonen it seems like there's canonical politics involved so, i purged python3-apport and reinstalled only 2 packages: sudo apt install xserver-xorg-core xserver-xorg-input-libinput x11-apps x11-session-utils xinput xinit x11-apps could be installed extra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905775 Title: Uninstalling python3-apporrt should not uninstall xorg packages Status in xorg package in Ubuntu: New Bug description: ``` sudo apt purge python3-apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna python3-problem-report python3-requests python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: python3-apport* xorg* xserver-xorg* 0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded. After this operation, 1,070 kB disk space will be freed. Do you want to continue? [Y/n] ^C ``` so, apparently dependencies aren't correctly set, because I don't want to send no problem reports but still want to use xorg subsystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905775/+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 1905775] Re: Uninstalling python3-apporrt should not uninstall xorg packages
ah, it's the other way around with dependencies. So, apparently xorg should not depend on problem reporting. I think the only reason they put this dependency there is because otherwise they would have to add it to every -desktop task. And no, I want to purge all packages related to apport, not only disable it. Thanks, Brian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1905775 Title: Uninstalling python3-apporrt should not uninstall xorg packages Status in xorg package in Ubuntu: New Bug description: ``` sudo apt purge python3-apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libglu1-mesa libxfont2 python3-certifi python3-chardet python3-idna python3-problem-report python3-requests python3-requests-unixsocket python3-urllib3 x11-apps x11-session-utils xinit xinput xserver-common xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: python3-apport* xorg* xserver-xorg* 0 upgraded, 0 newly installed, 3 to remove and 61 not upgraded. After this operation, 1,070 kB disk space will be freed. Do you want to continue? [Y/n] ^C ``` so, apparently dependencies aren't correctly set, because I don't want to send no problem reports but still want to use xorg subsystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1905775/+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
