[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
This bug is still valid even in Ubuntu 20.10, but a little different. In my case a popup appears randomly that says something like mic muted / mic unmuted. My solution on any distro starting from Ubuntu 20.04: sudo sed -e '/f20/ s/^#*/#/' -i /lib/udev/hwdb.d/60-keyboard.hwdb sudo systemd-hwdb update In my case it happens in Ideapad 700 15-ISK I have no idea how to report the bug as every time it happens I apply that patch and that's it If this is not the place for this message, please feel free to delete it or ask me to delete it. -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1881453] [NEW] Screen corruption on resize (Android Studio start screen)
Public bug reported: 1) Description:Ubuntu 20.04 LTS Release:20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate
[Touch-packages] [Bug 1881453] Re: Screen corruption on resize (Android Studio start screen)
** Attachment added: "Captura de pantalla de 2020-05-31 04-40-56.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881453/+attachment/5378936/+files/Captura%20de%20pantalla%20de%202020-05-31%2004-40-56.png -- 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/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881453/+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 1513698] Re: $HOME variable set incorrectly inside container
Thanks! For those stumbling with this thing, the manpage do state that the default behaviour is to keep all the external env, and that it may change in the future. http://manpages.ubuntu.com/manpages/trusty/man1/lxc-attach.1.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1513698 Title: $HOME variable set incorrectly inside container Status in lxc package in Ubuntu: New Bug description: I have lxc containers set up as an unprivileged user. When I start my containers, the root user has the $HOME environmental variable set, pointing at the unprivileged user. This is the faulty session: sputnik is the host, lamp2 is the lxc container ruben@sputnik:~$ echo $HOME /home/ruben ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $HOME /home/ruben root@lamp2:/# exit ruben@sputnik:~$ TEST_VAR="THIS IS A TEST" ruben@sputnik:~$ lxc-stop -n lamp2 ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $TEST_VAR root@lamp2:/# echo $HOME /home/ruben at least the $HOME variable is set incorrectly inside the container, whilte TEST_VAR is correcty unset inside. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu in the host: ruben@sputnik:~$ lsb_release LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch in the container: root@lamp2:/# lsb_release No LSB modules are available. this is a trusty container, created with a downloaded template (lxc- create ... -t download) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ruben@sputnik:~$ apt-cache policy lxc lxc: Instalados: 1.0.7-0ubuntu0.9 Candidato: 1.0.7-0ubuntu0.9 Tabla de versión: 1.1.4-0ubuntu1.1~ubuntu14.04.2 0 100 http://mx.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.0.7-0ubuntu0.9 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.7-0ubuntu0.7 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.0.3-0ubuntu3 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The user root should have it's $HOME set to /root inside the container 4) What happened instead The user root has it's $HOME set to the unprivileged user's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1513698/+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 1513698] [NEW] $HOME variable set incorrectly inside container
Public bug reported: I have lxc containers set up as an unprivileged user. When I start my containers, the root user has the $HOME environmental variable set, pointing at the unprivileged user. This is the faulty session: sputnik is the host, lamp2 is the lxc container ruben@sputnik:~$ echo $HOME /home/ruben ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $HOME /home/ruben root@lamp2:/# exit ruben@sputnik:~$ TEST_VAR="THIS IS A TEST" ruben@sputnik:~$ lxc-stop -n lamp2 ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $TEST_VAR root@lamp2:/# echo $HOME /home/ruben at least the $HOME variable is set incorrectly inside the container, whilte TEST_VAR is correcty unset inside. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu in the host: ruben@sputnik:~$ lsb_release LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch in the container: root@lamp2:/# lsb_release No LSB modules are available. this is a trusty container, created with a downloaded template (lxc- create ... -t download) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ruben@sputnik:~$ apt-cache policy lxc lxc: Instalados: 1.0.7-0ubuntu0.9 Candidato: 1.0.7-0ubuntu0.9 Tabla de versión: 1.1.4-0ubuntu1.1~ubuntu14.04.2 0 100 http://mx.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.0.7-0ubuntu0.9 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.7-0ubuntu0.7 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.0.3-0ubuntu3 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The user root should have it's $HOME set to /root inside the container 4) What happened instead The user root has it's $HOME set to the unprivileged user's ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1513698 Title: $HOME variable set incorrectly inside container Status in lxc package in Ubuntu: New Bug description: I have lxc containers set up as an unprivileged user. When I start my containers, the root user has the $HOME environmental variable set, pointing at the unprivileged user. This is the faulty session: sputnik is the host, lamp2 is the lxc container ruben@sputnik:~$ echo $HOME /home/ruben ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $HOME /home/ruben root@lamp2:/# exit ruben@sputnik:~$ TEST_VAR="THIS IS A TEST" ruben@sputnik:~$ lxc-stop -n lamp2 ruben@sputnik:~$ lxc-start -n lamp2 -d ruben@sputnik:~$ lxc-attach -n lamp2 root@lamp2:/# echo $TEST_VAR root@lamp2:/# echo $HOME /home/ruben at least the $HOME variable is set incorrectly inside the container, whilte TEST_VAR is correcty unset inside. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu in the host: ruben@sputnik:~$ lsb_release LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch in the container: root@lamp2:/# lsb_release No LSB modules are available. this is a trusty container, created with a downloaded template (lxc- create ... -t download) 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ruben@sputnik:~$ apt-cache policy lxc lxc: Instalados: 1.0.7-0ubuntu0.9 Candidato: 1.0.7-0ubuntu0.9 Tabla de versión: 1.1.4-0ubuntu1.1~ubuntu14.04.2 0 100 http://mx.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.0.7-0ubuntu0.9 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.7-0ubuntu0.7 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.0.3-0ubuntu3 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The user root should have it's $HOME set to /root inside the container 4) What happened instead The user root has it's $HOME set to the unprivileged user's To manage
[Touch-packages] [Bug 1496119] [NEW] package systemd 225-1ubuntu4 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Tue Sep 15 18:33:04 2015 DuplicateSignature: package:systemd:225-1ubuntu4:los disparadores han entrado en bucle, abandonando ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2015-09-15 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) MachineType: TOSHIBA Satellite C855 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c6ce6a11-3fdf-4131-924a-7909f9fb6604 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu6 SourcePackage: systemd Title: package systemd 225-1ubuntu4 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.60 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.60:bd04/20/2012:svnTOSHIBA:pnSatelliteC855:pvrPSC72U-01600C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C855 dmi.product.version: PSC72U-01600C dmi.sys.vendor: TOSHIBA ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- 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/1496119 Title: package systemd 225-1ubuntu4 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in systemd package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Tue Sep 15 18:33:04 2015 DuplicateSignature: package:systemd:225-1ubuntu4:los disparadores han entrado en bucle, abandonando ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2015-09-15 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) MachineType: TOSHIBA Satellite C855 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c6ce6a11-3fdf-4131-924a-7909f9fb6604 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu6 SourcePackage: systemd Title: package systemd 225-1ubuntu4 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.60 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.60:bd04/20/2012:svnTOSHIBA:pnSatelliteC855:pvrPSC72U-01600C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C855 dmi.product.version: PSC72U-01600C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1496119/+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
