[Touch-packages] [Bug 2017692] [NEW] can't connect to zsys daemon after upgrading from 22.10 to 23.04
Public bug reported: After upgrading from 22.10 to 23.04, I'm getting the following message: ERROR couldn't connect to zsys daemon: connection error: desc = "transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused" Setting up initramfs-tools (0.142ubuntu2) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.142ubuntu2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-20-generic cryptsetup: ERROR: Couldn't resolve device UUID=e50c063b-1ed9-45fc-9626=dcc95195a4ef W: initramfs-tools configuration sets RESUME=UUID=e50c063b-1ed9-45fc-9626-dcc95195a4ef W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/nvme0n1p2 I: (UUID=30b393bc-1995-4f6a=9989-3a9e385fbd9d) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 update-initramfs: failed for /boot/initrd.img-6.20-20-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Error connecting: Could not connect: Connection refused ERROR couldn't connect to zsys daemon: connection error: desc = "transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused E: Sub-process /usr/bin/dpkg returned an error code (1) [root /boot]# I have a script for freeing up space on zfs: % zfs list -r -t snapshot -o name,used,referenced,creation bpool/BOOT | tail -n +2 | head -n -5 | head -5 | cut -c 35-40 | xargs -n 1 /usr/bin/sudo zsysctl state remove --system But, when I run this script, I get the messages: level=error msg="couldn't connect to zsys daemon: connection error: desc = "\\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" level=error msg="couldn't connect to zsys daemon: connection error: desc = "\\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" level=error msg="couldn't connect to zsys daemon: connection error: desc = "\\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" level=error msg="couldn't connect to zsys daemon: connection error: desc = "\\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" level=error msg="couldn't connect to zsys daemon: connection error: desc = "\\"transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused\"" I tried restarting zsysd.service: % systemctl restart zsysd.service Job for zsysd.service failed because the control process exited with error code. See "systemctl status zsysd.service" and "journalctl -xeu zsysd.service" for details. % systemctl status zsysd.service * zsysd.service - ZSYS daemon service Loaded: loaded (/lib/systemd/system/zsysd.service; static) Active: failed (Result: exit-code) since Mon 2023-04-24 22:38:31 PDT; 2min 51s ago TriggeredBy: * zsysd.socket Process: 54726 ExecStart=/sbin/zsysd (code=exited, status=1/FAILURE) Main PID: 54726 (code=exited, status=1/FAILURE) CPU: 539ms systemd[1]: Starting zsysd.service - ZSYS daemon service... zsysd[54726]: level=error msg="Couldn't register grpc server: couldn't create new authorizer: dial unix /var/run/dbus/system_bus_socket: connect: connection refused" systemd[1]: zsysd.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: zsysd.service: Failed with result 'exit-code'. systemd[1]: Failed to start zsysd.service - ZSYS daemon service. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Package changed: network-manager (Ubuntu) => zfs-linux (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/2017692 Title: can't connect to zsys daemon after upgrading from 22.10 to 23.04 Status in zfs-linux package in Ubuntu: New Bug description: After upgrading from 22.10 to 23.04, I'm getting the following message: ERROR couldn't connect to zsys daemon: connection error: desc = "transport: Error while dialing dial unix /run/zsysd.sock: connect: connection refused" Setting up initramfs-tools (0.142ubuntu2) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.142ubuntu2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-20-generic cryptsetup: ERROR: Couldn't resolve device UUID=e50c063b-1ed9-45fc-9626=dcc95195a4ef W: initramfs-tools configuration sets RESUME=UUID=e50c063b-1ed9-45fc-9626-dcc95195a4ef W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/nvme0n1p2 I:
[Touch-packages] [Bug 1900910] Re: Xorg freeze after closing lid and Suspend
The same thing happens when I lock my screen. When I come back, the power has shut off. Pressing the power button starts what looks like a power-up, but it ends up with just a black screen. None of the keys seem to do anything. I have to power-cycle my laptop to get it to work again. -- 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/1900910 Title: Xorg freeze after closing lid and Suspend Status in xorg package in Ubuntu: New Bug description: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (1085 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1900910/+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 1900910] [NEW] Xorg freeze after closing lid and Suspend
Public bug reported: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (1085 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1900910 Title: Xorg freeze after closing lid and Suspend Status in xorg package in Ubuntu: New Bug description: Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid. I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44 Uname: Linux 5.4.0-7642-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 14:25:22 2020 DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript:
[Touch-packages] [Bug 1855565] [NEW] After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up
Public bug reported: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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.31 Sun Oct 27 02:19:35 UTC 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:26:22 2019 DistUpgraded: 2019-11-14 14:45:51,508 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-14 (23 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 eoan third-party-packages ubuntu ** Attachment added: "screenshot showing taskbar with corrupted fonts" https://bugs.launchpad.net/bugs/1855565/+attachment/5310605/+files/Screenshot%20from%202019-12-07%2017-26-57.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/1855565 Title: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up Status in xorg package in Ubuntu: New Bug description: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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.31 Sun Oct 27
[Touch-packages] [Bug 1855565] Re: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up
** Attachment added: "screenshot showing popup asking for sudo password" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855565/+attachment/5310629/+files/Screenshot%20from%202019-12-07%2017-27-46.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/1855565 Title: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up Status in xorg package in Ubuntu: New Bug description: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/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.31 Sun Oct 27 02:19:35 UTC 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:26:22 2019 DistUpgraded: 2019-11-14 14:45:51,508 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-14 (23 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1855565/+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 1838836] Re: network-manager needs to be restarted frequently
Till Kamppeter (till-kamppeter) wrote on 2019-08-06: asking me to post the full log. I did on 8/08. Nothing has happened on this list for two months. Is there no solution to this problem? -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0:
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
It's still broken, even though I haven't received any suggestions on what to try. Sometimes the network is lost when resuming after suspend, sometimes, just because it feels like it. ** Changed in: network-manager (Ubuntu) Status: Expired => 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Network shutdown still happens in Ubuntu 19.10. -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0:
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Here's the syslog, starting at the point where I have a connection to a local wifi, and then I have a failed switch to the other local wifi. (I am sending this after capturing the log, and restarting the network- manager service.) Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3253] device (wlp62s0): disconnecting for new activation request. Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3253] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3255] manager: NetworkManager state is now DISCONNECTING Aug 8 10:01:22 serval whoopsie[2549]: [10:01:22] offline Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3316] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=11238 uid=1010 result="success" Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3317] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6d08 i resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6c70 i resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 556db14b6bd0 i resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1934 (7f9b93d75dc0 @ 80) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6d18 i resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6c80 i resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 556db14b6be0 i resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216) Aug 8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncNMState@resource:///org/gnome/shell/ui/status/network.js:1934:9 Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1842 (7f9b93d75790 @ 138) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6bf8 i resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f9bb45b90d0 @ 25) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1815 (7f9b93d75700 @ 111) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1842:9 Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
I tried disabling the power saver (#3). If I change networks, then no wifi is found. -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
What should I look for in the log? -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0:
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
I get: wifi.powersave = 3 -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-SIGNAL-CHANGE above=0
[Touch-packages] [Bug 1838836] [NEW] network-manager needs to be restarted frequently
Public bug reported: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise= txrate=0 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5688] manager: NetworkManager state is now DISCONNECTED Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5692] device (wlp62s0): Activation: starting connection 'ATT964' (1574892b-31aa-43ae-a67a-bd732876e327) Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5700] sup-iface[0x55d1a0552930,wlp62s0]: connection disconnected
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I'm getting this error on Ubuntu 17.10: W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) I have a user _apt, and it owns /var/lib/update-notifier/package-data- downloads/partial/ It looks like the problems are 2-fold: 1. The double-slash in '/root/.synaptic/tmp//tmp_cl' is equivalent to /tmp_cl, isn't it? That doesn't exist, and probably shouldn't. The double-slash should probably be a single slash. 2. Why is _apt supposed to be able to access anything in /root? If /root/.synaptic/tmp is a special case, then somebody or some program needs to change its ownership. Right now it's: drwx-- 2 root root /root/.synaptic/tmp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1585464] [NEW] package udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Mysterious death during upgrade from 15.10 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10 Uname: Linux 4.2.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules Date: Tue May 24 17:52:48 2016 DuplicateSignature: package:udev:225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service]:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-02 (1118 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-05-25 (0 days ago) dmi.bios.date: 10/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1585464 Title: package udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Mysterious death during upgrade from 15.10 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10 Uname: Linux 4.2.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules Date: Tue May 24 17:52:48 2016 DuplicateSignature: package:udev:225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service]:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-02 (1118 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 [modified: lib/systemd/system/lvm2.service] failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-05-25 (0 days ago) dmi.bios.date: 10/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585464/+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 1585406] [NEW] package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Died during upgrade from 15.10 x86-64. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10 Uname: Linux 4.2.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules Date: Tue May 24 16:29:40 2016 DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-02 (1118 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago) dmi.bios.date: 10/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1585406 Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Died during upgrade from 15.10 x86-64. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10 Uname: Linux 4.2.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules Date: Tue May 24 16:29:40 2016 DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-02 (1118 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago) dmi.bios.date: 10/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585406/+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 1506612] [NEW] pdfimages extracts black rectangles instead of the images
Public bug reported: When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images, two of which are black rectangles. If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that looks correct. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: poppler-utils 0.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 15 12:36:10 2015 InstallationDate: Installed on 2013-05-02 (896 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Sample pdf file" https://bugs.launchpad.net/bugs/1506612/+attachment/4496036/+files/Z.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1506612 Title: pdfimages extracts black rectangles instead of the images Status in poppler package in Ubuntu: New Bug description: When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images, two of which are black rectangles. If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that looks correct. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: poppler-utils 0.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 15 12:36:10 2015 InstallationDate: Installed on 2013-05-02 (896 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1506612/+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 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
It's been 25 days since I upgraded to 15.04, and I still don't have a working ethernet! ** Package changed: network-manager (Ubuntu) = network-manager -- 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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in NetworkManager: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1452119/+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 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
See the attached /var/log/syslog. Configuration of ethernet fails: May 22 15:10:33 bonobo NetworkManager[1053]: error [1432332633.395458] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 10.0.0.0/22 via 10.0.1.1 dev eth0 metric 100 mss 0 src user: Unspecific failure May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) failed May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: ip-config - failed (reason 'config-failed') [70 120 4] May 22 15:10:33 bonobo NetworkManager[1053]: warn Activation (eth0) failed for connection 'Auto Ethernet' May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: failed - disconnected (reason 'none') [120 30 0] May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): deactivating device (reason 'none') [0] ** Attachment added: syslog file https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+attachment/4402722/+files/syslog -- 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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in network-manager package in Ubuntu: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+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 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
See the attached /var/log/syslog. Configuration of ethernet fails: May 22 15:10:33 bonobo NetworkManager[1053]: error [1432332633.395458] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 10.0.0.0/22 via 10.0.1.1 dev eth0 metric 100 mss 0 src user: Unspecific failure May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) failed May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: ip-config - failed (reason 'config-failed') [70 120 4] May 22 15:10:33 bonobo NetworkManager[1053]: warn Activation (eth0) failed for connection 'Auto Ethernet' May 22 15:10:33 bonobo NetworkManager[1053]: info Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): device state change: failed - disconnected (reason 'none') [120 30 0] May 22 15:10:33 bonobo NetworkManager[1053]: info (eth0): deactivating device (reason 'none') [0] ** Attachment added: syslog file https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+attachment/4402693/+files/syslog -- 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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in network-manager package in Ubuntu: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+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 1452119] Re: ethernet interface broken after upgrade from 14.10 to 15.04
I think this is a network manager issue. ** Package changed: unity-control-center (Ubuntu) = network-manager (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/1452119 Title: ethernet interface broken after upgrade from 14.10 to 15.04 Status in network-manager package in Ubuntu: New Bug description: After upgrading, the ethernet connection doesn't connect. If I run ifconfig with the ethernet unplugged, I get: % ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:293047 errors:0 dropped:1 overruns:0 frame:0 TX packets:341795 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75754614 (75.7 MB) TX bytes:77108082 (77.1 MB) Interrupt:38 With the ethernet plugged in, I get: % ifconfig eth0 Link encap:Ethernet HWaddr 00:90:f5:c7:69:b7 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:293286 errors:0 dropped:1 overruns:0 frame:0 TX packets:342195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75797513 (75.7 MB) TX bytes:77249665 (77.2 MB) Interrupt:38 The differences in the outputs are that (a) RUNNING, (b) packets received and transmitted after plugging it in, although no ip address is reported. % lspci -nnk | grep -iEA3 (ethernet|network) 03:00.0 Ethernet controller [0200]: JMicron Technology Corp. JMC250 PCI Express Gigabit Ethernet Controller [197b:0250] (rev 05) Subsystem: CLEVO/KAPOK Computer Device [1558:7100] Kernel driver in use: jme 03:00.1 System peripheral [0880]: JMicron Technology Corp. SD/MMC Host Controller [197b:2392] (rev 90) -- 04:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] [8086:0091] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN [8086:5201] Kernel driver in use: iwlwifi 05:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technology Corp. IEEE 1394 Host Controller [197b:2380] (rev 30) If I run % sudo ifconfig eth0 down % sudo ifconfig eth0 up System Settings/Network/Wired show the interface activate briefly, then go back to the disconnected state. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 5 10:38:15 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-05-02 (733 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-26 (8 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452119/+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 1282294] Re: Cannot open pixbuf loader module file
This happened to me when trying to upgrade from 14.10 to 15.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: Cannot open pixbuf loader module file Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
This bug hits me every time apt-get upgrades to a new release of the kernel. The first reboot after upgrading would always fail. A 2nd reboot would always work. This time, after upgrading to 3.16.0-28-generic x86_64, subsequent reboots end up in the same state. If I open a console, it says the networking service is working but ifconfig doesn't showeth0 and network names e.g., Google.com, are unknown. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd-shim package in Ubuntu: In Progress Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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
