[Touch-packages] [Bug 1915226] Re: network-manager continuous inappropriate site surveys
Kroger is conducting a customer satisfaction survey to learn about customers' actual experience during their Kroger store visit. As a token of appreciation from the company, the management is offering 50 fuel points for free to the customers who participated in the survey on the https://kroger-feedback.online/ official site. -- 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/1915226 Title: network-manager continuous inappropriate site surveys Status in network-manager package in Ubuntu: New Bug description: this message is flooding my kernel ring RTW: ERROR [RFK-CHK] RF-K not allowed due to ifaces under site-survey network details are as follows. ~$ ifconfig eno1: flags=4163 mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d323:619a:9114:8f78 prefixlen 64 scopeid 0x20 ether 48:0f:cf:5f:e6:12 txqueuelen 1000 (Ethernet) RX packets 49088 bytes 15509621 (15.5 MB) RX errors 0 dropped 0 overruns 0 frame RTL8811CU0 TX packets 36480 bytes 5212324 (5.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xd100-d102 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 204584 bytes 11022005 (11.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 204584 bytes 11022005 (11.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlx001325ad55e1: flags=4163 mtu 1500 inet 192.168.1.103 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::9a15:f995:c011:c29e prefixlen 64 scopeid 0x20 ether 00:13:25:ad:55:e1 txqueuelen 1000 (Ethernet) RX packets 62335 bytes 9276176 (9.2 MB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 4605 bytes 645037 (645.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1 is through motherboard wlx001325ad55e1 is though USB: Volans VL-UW60-FD using a RTL8811CU chip (see https://www.volans.com.au/product/vl-uw60-fd/) Both cable and wireless connections are working well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 12:06:18 2021 InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev eno1 proto dhcp metric 100 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 metric 600 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1915226/+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 1973240] [NEW] Wireless mouse shows up under `lsusb` list but doesn't control the cursor
Public bug reported: What happens: Wireless mouse shows up under `lsusb` list but doesn't control the cursor. Expected behavior: The mouse controls the cursor. Background: I purchased a "Mini 2.4 GHz Wireless Optical Mini Finger Mouse Mice For Laptop PC Computers" (https://www.ebay.com/itm/283656756166) and plugged it into my laptop. Although this mouse appears under lsusb, it does not control the cursor. Other usb mice work, but not this one. Uniquely, this mouse uses a wireless dongle and some form of laser tracking, while my other peripherals are 'ordinary': a wired laster mouse and usb wired keyboard. Ubuntu version: ``` jacob:~/ $ lsb_release -rd [15:12:52] Description:Ubuntu 20.04.4 LTS Release:20.04 ``` lsusb (with not working, wireless mouse dongle inserted): ``` jacob:~/ $ lsusb [15:13:02] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 016: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` lsusb (with no usb mouse): ``` jacob:~/ $ lsusb [15:13:44] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` lsusb (with working, wired mouse): ``` jacob:~/ $ lsusb [15:14:32] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 017: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ``` dmesg output: - no usb peripherals: [see attatched file `dmesg_no_peripherals.txt`] - wired mouse (works): [see attatched file `dmesg_wired_mouse.txt`] - wireless mouse (doesn't work): [see attatched file `dmesg_wireless_mouse.txt`] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 12 14:58:18 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-107-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-109-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a8] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a8] InstallationDate: Installed on 2020-11-03 (555 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 016: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 16, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 5: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-109-generic root=UUID=51015d56-7d65-470e-9290-eaa3eab354c5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1969816] [NEW] Display dimming despite setting being turned off
Public bug reported: The display is dimming after a few seconds of "inactivity" despite turning off the setting to dim the display. This seems to occur on any power setting and a reboot did not solve the problem. This makes activities such as reading difficult as the display becomes harder to read and I have to interact with the computer more than necessary to keep the screen bright. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 09:56:56 2022 DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware that removing the lock file is not a solution and may break your system., E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a7d] InstallationDate: Installed on 2022-03-29 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 14 5410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) dmi.bios.date: 02/15/2022 dmi.bios.release: 2.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.1 dmi.board.name: 0XPW9D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.1:bd02/15/2022:br2.7:svnDellInc.:pnInspiron145410:pvr:rvnDellInc.:rn0XPW9D:rvrA00:cvnDellInc.:ct10:cvr:sku0A7D: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5410 dmi.product.sku: 0A7D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/1969816 Title: Display dimming despite setting being turned off Status in xorg package in Ubuntu: New Bug description: The display is dimming after a few seconds of "inactivity" despite turning off the setting to dim the display. This seems to occur on any power setting and a reboot did not solve the problem. This makes activities such as reading difficult as the display becomes harder to read and I have to interact with the computer more than necessary to keep the screen bright. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 09:56:56 2022 DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware that removing the lock file is not a solution and may break your system., E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a7d] InstallationDate: Installed on 2022-03-29 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 14 5410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9
[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
Hey guys, I was the one who started the amd chipset rumor. We've been talking about the issue over at https://forum.level1techs.com/t/rodecaster-pro-bad-audio-out-solved- ish/170601. At first I thought it was an amd vs intel issue just due to the hardware I had on hand that worked/didn't work. After someone popped in mentioning their intel device having the issue and a pcie card they bought also having the issue it seems like the issue is with all usb3.2 gen2x2 host controllers, or at least that's my best guess. I picked up a different pcie usb card than the person had trouble with and that was 3.2 gen2x2 capable. I can reproduce the issue on both it, and my motherboard usb ports. However, using a usb3.0 pcie card the issue goes away. One strange thing to me about all of this is that the rodecaster pro is negotiating usb2 480mbps connections, so i'm not sure why a later usb spec would mess with that. It's also worth noting that the issue seems to be related to the usb host controller itself as using ports capable of different speeds/going through usb hubs or directly connecting doesn't change the behavior. I also don't have a usb 3.1 gen2 host controller to test to see if the issue is truly only with usb 3.2 gen2x2 controllers. Debugging any further than that is proving difficult though. I did a diff on both my lsusb and pw-dump output and the only changes in the two were paths/ids which are expected to change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.1
[Touch-packages] [Bug 1945465] [NEW] Can't turn bluetooth on
Public bug reported: When I try to turn on my bluetooth, it simply doesn't turn on. This just came from one day to another. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pc27999 F pulseaudio /dev/snd/pcmC0D0p: pc27999 F...m pulseaudio /dev/snd/controlC1: pc27999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:02:30 2021 InstallationDate: Installed on 2021-06-28 (93 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,1:pvr1.0:sku:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1945465 Title: Can't turn bluetooth on Status in alsa-driver package in Ubuntu: New Bug description: When I try to turn on my bluetooth, it simply doesn't turn on. This just came from one day to another. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pc27999 F pulseaudio /dev/snd/pcmC0D0p: pc27999 F...m pulseaudio /dev/snd/controlC1: pc27999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:02:30 2021 InstallationDate: Installed on 2021-06-28 (93 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,1:pvr1.0:sku:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1945465/+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 1915548] [NEW] package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
Public bug reported: yes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 12 03:11:48 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: db5.3 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: db5.3 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1915548 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in db5.3 package in Ubuntu: New Bug description: yes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 12 03:11:48 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: db5.3 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1915548/+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 1894155] Re: libpam-moudles update failure
$ sudo lsof /var/cache/debconf/config.dat $ sudo kill [pid listed above] then update is successful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1894155 Title: libpam-moudles update failure Status in pam package in Ubuntu: New Bug description: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1894155/+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 1894155] [NEW] libpam-moudles update failure
Public bug reported: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1894155 Title: libpam-moudles update failure Status in pam package in Ubuntu: New Bug description: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1894155/+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 1886697] [NEW] Xorg crash
Public bug reported: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how to search the syslog, but I expect to find something funky around something like "GUI going to sleep". The reason I think it is a true "crash" is, despite being away from my the PC for 1 hr, the job directory is empty. This makes me think the computer processes were halted during the events that lead to the GUI death. I have played with my GPU settings. As per this NVIDIA thread https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock- up/79731/252, I have set my minumum clock speed to 1050mHz. This had been successful up until this point at preventing a different issue not related to this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09: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.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 13:26:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:13a2] InstallationDate: Installed on 2020-05-26 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5a52a344-c840-428b-89b5-b3c2e86fbc43 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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 crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886697 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how
[Touch-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly
This is happening on Wifi and VPN for me... Ethernet works fine. -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Ok, thanks. On Thu, 10 Oct 2019 at 05:51, Launchpad Bug Tracker < 1773...@bugs.launchpad.net> wrote: > This bug was fixed in the package systemd - 237-3ubuntu10.31 > > --- > systemd (237-3ubuntu10.31) bionic; urgency=medium > > [ Dimitri John Ledkov ] > * Add conflicts with upstart and systemd-shim. (LP: #1773859) > * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch > - units: Disable journald Watchdog (LP: #1773148) > * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch > - cryptsetup: add support for sector-size= option (LP: #1776626) > * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch > - systemctl: correctly proceed to immediate shutdown if scheduling > fails > (LP: #1670291) > * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch > - networkd: add support to set IPv6MTUBytes (LP: #1671951) > > -- Balint Reczey Mon, 30 Sep 2019 17:23:17 +0200 > > ** Changed in: systemd (Ubuntu Bionic) >Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Fix Released > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades
[Touch-packages] [Bug 1843819] Re: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%
Here we go. I was able to replace identifying information (that I care about). Hopefully this is what you need. ** Attachment added: "apport.pulseaudio.zetzgvt7.apport" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+attachment/5289595/+files/apport.pulseaudio.zetzgvt7.apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1843819 Title: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50% Status in pulseaudio package in Ubuntu: Incomplete Bug description: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1843819] Re: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%
Ah, I made a typo. Now it's working; however the information it wants to send contains my username which I don't want made public for privacy reasons. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1843819 Title: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50% Status in pulseaudio package in Ubuntu: Incomplete Bug description: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1843819] Re: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%
apport-collect says that I'm not the reporter or that the bug is closed/resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1843819 Title: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50% Status in pulseaudio package in Ubuntu: Incomplete Bug description: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1843819] [NEW] Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50%
Public bug reported: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1843819 Title: Volume scaling is incorrect for Logitech H600 (046d:0a29): alsamixer @ 0% where pulse volume @ 50% Status in pulseaudio package in Ubuntu: New Bug description: When the volume is set to around 50% in PulseAudio (using the Ubuntu Sound preferences screen but cross-checked by simply viewing with pavucontrol) the alsamixer volume is set to 0%. I can see the volume rise quickly as the volume is raised past 50% in the Sound preferences screen. This occurs at least for the Logitech H600 USB device: Bus 001 Device 011: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset] The other audio devices behave "correctly" where 0% is silent and 100% is maximum volume. This confused me because the volume was set to 50% (I'll frequently reset headset volume to 30-50% to protect my ears) and thought audio was broken at first because I wasn't getting any sound at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1843819/+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 1190344] Re: Daemon end of session/greeter pipes not closed
Still seeing this issue with package and tracking FIFO on log in log out
lightdm.x86_64 1.25.0-1.el7
lightdm-gobject.x86_64 1.25.0-1.el7
lightdm-gtk.x86_64 1.8.5-19.el7
lightdm-gtk-common.noarch 1.8.5-19.el7
[root@caeusadm tmp]# lightdm -v
lightdm 1.25.0
[root@caeusadm tmp]# lsof -p 13696 | grep FIFO | wc -l
188
[root@caeusadm tmp]# lsof -p 13696 | grep FIFO | wc -l
190
Increments by 2 for every log in log out and never frees them up.
When it passes open file limit (currently 1024) lightdm crashes and all
users lose session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Precise:
Fix Released
Status in lightdm source package in Trusty:
Fix Released
Status in lightdm source package in Utopic:
Fix Released
Status in lightdm source package in Vivid:
Fix Released
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1811199] [NEW] package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: software center has a lot of issues installing almost everything I have tried so far ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Jan 9 23:21:45 2019 DuplicateSignature: package:ca-certificates:20180409 Processing triggers for systemd (237-3ubuntu10.9) ... dpkg: error processing package openssl (--configure): package is in a very bad inconsistent state; you should ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-01-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1811199 Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in ca-certificates package in Ubuntu: New Bug description: software center has a lot of issues installing almost everything I have tried so far ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Jan 9 23:21:45 2019 DuplicateSignature: package:ca-certificates:20180409 Processing triggers for systemd (237-3ubuntu10.9) ... dpkg: error processing package openssl (--configure): package is in a very bad inconsistent state; you should ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-01-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1811199/+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 1773859] Re: upgrades to 18.04 fail
this package failed to upgrade when is upgrading to ubuntu 18.04, may you help me to resolve this issue -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
I'm on cosmic, upgraded from bionic, and I have the same issue. I had to revert to an X11 session in order to launch slack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.2 To manage notifications
[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Activating service name='org.gnome.GConf' requested by ':1.84' (uid=1000 pid=5586 comm="/snap/slack/9/usr/lib/slack/slack --executed-from =" label="snap.slack.slack (complain)") Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Successfully activated service 'org.gnome.GConf' Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Backtrace: Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x55bab3776c39] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f18b4fcae1f] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f18b1449760] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f18b130e4b1] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f18b122b52a] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f18b122b5ee] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f18b122b6c9] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f18b10f7432] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f18b146335d] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f18b1827e89] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f18b1825c93] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 11: /usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55bab36a3c69] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 12: /usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55bab36a168b] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 13: /usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55bab376561d] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 14: /usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55bab36abbd9] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 15: /usr/bin/Xwayland (glvndGetExports+0xde5) [0x55bab3785f35] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 16: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55bab3740bae] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 17: /usr/bin/Xwayland (InitFonts+0x3b6) [0x55bab3744b36] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f18b4df209b] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 19: /usr/bin/Xwayland (_start+0x2a) [0x55bab36161ea] Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Segmentation fault at address 0x68 Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: Fatal server error: Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Caught signal 11 (Segmentation fault). Server aborting Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,
[Touch-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915
UPDATE: I installed kernel 4.16.7 from http://kernel.ubuntu.com/~kernel- ppa/mainline/ and things get much better. Not as good as it was on 17.10 but largely usable. Some regression in the i915 driver must have occurred in 4.15 and now it's catching up again apparently. -- 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/1765911 Title: Major performance regression from Ubuntu 17.10 with i915 Status in xorg package in Ubuntu: Confirmed Bug description: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765911/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
My WiFi is working perfectly but I'm still getting these messages -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1767322/+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 1767322] [NEW] "Activation of network connection failed" popup shows incessantly
Public bug reported: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in network-manager package in Ubuntu: New Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1767322/+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 1767321] [NEW] Xorg freeze
Public bug reported: In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random intervals. When it resumes, gnome shell's dock flickers as if the problem was caused by it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:02:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze third-party-packages ubuntu wayland-session -- 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/1767321 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: In Ubuntu 18.04, display freezes for ~1-5 seconds at seemingly random intervals. When it resumes, gnome shell's dock flickers as if the problem was caused by it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:02:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor
[Touch-packages] [Bug 1765913] [NEW] Hybrid graphics don't work after resume
Public bug reported: When my laptop resumes from suspend, the secondary GPU (Radeon R7 M265) does not work. Prior to suspend I can use it. After suspend, trying DRI_PRIME=1 glxinfo | grep OpenGL simply fails (see attached file). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:14:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu wayland-session ** Attachment added: "log" https://bugs.launchpad.net/bugs/1765913/+attachment/5124784/+files/log -- 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/1765913 Title: Hybrid graphics don't work after resume Status in xorg package in Ubuntu: New Bug description: When my laptop resumes from suspend, the secondary GPU (Radeon R7 M265) does not work. Prior to suspend I can use it. After suspend, trying DRI_PRIME=1 glxinfo | grep OpenGL simply fails (see attached file). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:14:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079
[Touch-packages] [Bug 1765911] [NEW] Major performance regression from Ubuntu 17.10 with i915
Public bug reported: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance third-party-packages ubuntu wayland-session -- 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/1765911 Title: Major performance regression from Ubuntu 17.10 with i915 Status in xorg package in Ubuntu: New Bug description: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic
[Touch-packages] [Bug 1750198] [NEW] Installed unity 8 on Ubuntu 16.04, however the log in screen crashes when pressing enter after typing password for unity 8-mir that I have installed
Public bug reported: I am running Ubuntu 16.04 LTS 64 Bit, with an Intel HD Graphics 400 (Braswell). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.12+16.04.20160401-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 18 00:53:29 2018 InstallationDate: Installed on 2018-02-03 (14 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1750198 Title: Installed unity 8 on Ubuntu 16.04, however the log in screen crashes when pressing enter after typing password for unity 8-mir that I have installed Status in unity8 package in Ubuntu: New Bug description: I am running Ubuntu 16.04 LTS 64 Bit, with an Intel HD Graphics 400 (Braswell). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.12+16.04.20160401-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 18 00:53:29 2018 InstallationDate: Installed on 2018-02-03 (14 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1750198/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Similar problem but not the same. My system is usable. I log in to whatever account I want and everything looks normal. It's only a problem if I put the cursor over any icon in the launcher or press the super key or when the logout/shutdown dialog or the alt+tab image is supposed to come up. In any of those cases, the launcher and top bar flicker and seem to reset. I can't log out or open or switch programs using the normal methods. I can get by just fine using the terminal but it's interrupting my work flow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubun
[Touch-packages] [Bug 1741468] Re: Broken GUI in Ubuntu MATE Live Session
18.04, bionic beaver testing live session. -- 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/1741468 Title: Broken GUI in Ubuntu MATE Live Session Status in xorg package in Ubuntu: New Bug description: Device: MacBook Air, late 2013 -The toolbar on the top and the bottom loads, but they seem to be images only. -I cannot click on the Applications, Places, System, Firefox, or MATE Welcome, nor the power button on the top bar. -The Bottom bar's show desktop and switch desktop does not click either. -My cursor shows and tracks, but it does not seem to register clicks. This is both with a mouse and a trackpad. -Background image is black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 1741468] [NEW] Broken GUI in Ubuntu MATE Live Session
Public bug reported: Device: MacBook Air, late 2013 -The toolbar on the top and the bottom loads, but they seem to be images only. -I cannot click on the Applications, Places, System, Firefox, or MATE Welcome, nor the power button on the top bar. -The Bottom bar's show desktop and switch desktop does not click either. -My cursor shows and tracks, but it does not seem to register clicks. This is both with a mouse and a trackpad. -Background image is black. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1741468 Title: Broken GUI in Ubuntu MATE Live Session Status in xorg package in Ubuntu: New Bug description: Device: MacBook Air, late 2013 -The toolbar on the top and the bottom loads, but they seem to be images only. -I cannot click on the Applications, Places, System, Firefox, or MATE Welcome, nor the power button on the top bar. -The Bottom bar's show desktop and switch desktop does not click either. -My cursor shows and tracks, but it does not seem to register clicks. This is both with a mouse and a trackpad. -Background image is black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 1733468] [NEW] do-release-upgrade failed to update to systemd 229-4ubuntu21
Public bug reported: This is going from Ubuntu 14 to 16 LTS via do-release-upgrade on DigitalOcean. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Mon Nov 20 22:08:04 2017 DuplicateSignature: package:systemd:229-4ubuntu21:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1312 days ago) InstallationMedia: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: root=LABEL=DOROOT ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.0.1ubuntu2.17 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-11-21 (0 days ago) dmi.bios.date: 11/03/2016 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20161103 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr: dmi.product.name: Droplet dmi.product.version: 20161103 dmi.sys.vendor: DigitalOcean ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages uec-images 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/1733468 Title: do-release-upgrade failed to update to systemd 229-4ubuntu21 Status in systemd package in Ubuntu: New Bug description: This is going from Ubuntu 14 to 16 LTS via do-release-upgrade on DigitalOcean. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Mon Nov 20 22:08:04 2017 DuplicateSignature: package:systemd:229-4ubuntu21:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1312 days ago) InstallationMedia: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: root=LABEL=DOROOT ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.0.1ubuntu2.17 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-11-21 (0 days ago) dmi.bios.date: 11/03/2016 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20161103 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20161103:bd11/03/2016:svnDigitalOcean:pnDroplet:pvr20161103:cvnBochs:ct1:cvr: dmi.product.name: Droplet dmi.product.version: 20161103 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733468/+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 1511975] Re: /lib/systemd/system/console-setup.service has incorrect ExecStart
On my 16.04.3 (keyboard-configuration 1.108ubuntu15.3) the subject line is: ExecStart=/bin/setupcon --save So, it might have already been fixed, but further version range clarification is probably needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1511975 Title: /lib/systemd/system/console-setup.service has incorrect ExecStart Status in console-setup package in Ubuntu: Confirmed Bug description: /lib/systemd/system/console-setup.service as provided by this package (confirmed in vivid and wily) specifies: [Service] Type=oneshot ExecStart=/usr/bin/loadkeys /etc/console-setup/cached.kmap.gz The "ExecStart" line will set the keyboard map but not the font, therefore the font remains at the default VGA font and framebuffer console mode is not enabled. The correct line which will set up both the keyboard map and the font is: ExecStart=/bin/setupcon The complete modified file is attached. I would be willing to submit a pull request on the relevant git repository if someone could point me in the right direction. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: keyboard-configuration 1.108ubuntu5 [modified: lib/systemd/system/console-setup.service] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 31 16:30:27 2015 InstallationDate: Installed on 2015-10-31 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1511975/+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 1717291] [NEW] package unattended-upgrades 0.93.1ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: I noticed that the update/upgrade bugs a bit since I installed a new repertory to vlc. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Thu Sep 14 11:21:32 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 InstallationDate: Installed on 2017-01-30 (227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 UpgradeStatus: Upgraded to zesty on 2017-05-18 (118 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "7"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-03-29T04:08:27.429954 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1717291 Title: package unattended-upgrades 0.93.1ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 Status in unattended-upgrades package in Ubuntu: New Bug description: I noticed that the update/upgrade bugs a bit since I installed a new repertory to vlc. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Thu Sep 14 11:21:32 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 InstallationDate: Installed on 2017-01-30 (227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 UpgradeStatus: Upgraded to zesty on 2017-05-18 (118 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "7"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-03-29T04:08:27.429954 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1717291/+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 1697131] [NEW] ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: After installing Ubuntu 17.04 and updating this occurs every time. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Jun 10 15:20:55 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-10 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1697131 Title: ailed tpackage gconf2-common 3.2.6-3ubuntu7 fo install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: After installing Ubuntu 17.04 and updating this occurs every time. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Jun 10 15:20:55 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-10 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1697131/+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 1677540] Re: corrupted mouse pointer icon
Do you use nvidia? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677540 Title: corrupted mouse pointer icon Status in Canonical System Image: New Status in Mir: New Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 unity8 corrupted mouse pointer icon (see attaches screenshot, the mouse pointer is hovering places/Home on the file manager app, the orange block/square) mostly i see when i run apps with Xmir, maybe stuff that uses SDL, mpv, neverball and it's only the arrow pointer, the rest are not affected, resize arrows etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677540/+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 1653295] Re: Chromium and Chrome flickering
Hi Christopher, Thanks for taking a look into this issue - I've completed some troubleshooting based on your suggestions and have some more information that I hope is useful. I'm running a Chromebook using crouton to run Ubuntu in a chroot. 1. Unfortunately I'm not able to install anything other than a stable LTS on the hardware that exhibits the issue. 2. Removing the xserver-xorg-video-intel package and the conf file appears to have either resolved the issue or decreased it to the point where it is not currently noticeable. I've been running it for a day or so - will update if the issue occurs again. 3. Using UXA appeared to decrease the frequency of the issue similar to the above - however overall performance did suffer with rendering of pages slower, and I believe worse performance in Unity. 4. The issue has occurred across all the Chrome releases I've installed on this hardware (around the last two months) and occurs with the latest stable Chrome release as well. It was present with both xenial 16.04 and 16.04.1 releases. 5. It's an Acer Chromebook 11 - C730 6. Due to running on a Chromebook I'm not able to recompile the kernel - however the issue has occurred across multiple stable ChromeOS releases (from the last two months since this hardware has been running). -- 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/1653295 Title: Chromium and Chrome flickering Status in xorg package in Ubuntu: Incomplete Bug description: Chromium and Chrome 55.0.2883.87 flickering. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 04f2:b490 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashtree=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5fb151de5f21d1172e6c0f68e3f1f582c083a5cd salt=4ce7adaeb24ff98d94fb9bff36a65ac39b743a9ecca5390ad010972810c5697a" noinitrd vt.global_cursor_default=0 kern_guid=f32d8bfa-395b-d240-bbf7-eb409533babd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.bios.version: Google_Gnawty.5216.239.34 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Gnawty.5216.239.34:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launc
[Touch-packages] [Bug 1653295] [NEW] Chromium and Chrome flickering (SNA Xorg issues)
Public bug reported: This is additional debug information as requested for this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1586539 Ubuntu 16.04.1 (xenial) Chrome 55.0.2883.87 Kernel: 3.10.18 X.Org X Server 1.18.4 xorg-server 2:1.18.4-0ubuntu0.2 Current version of pixman: 0.33.6 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 04f2:b490 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashtree=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5fb151de5f21d1172e6c0f68e3f1f582c083a5cd salt=4ce7adaeb24ff98d94fb9bff36a65ac39b743a9ecca5390ad010972810c5697a" noinitrd vt.global_cursor_default=0 kern_guid=f32d8bfa-395b-d240-bbf7-eb409533babd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.bios.version: Google_Gnawty.5216.239.34 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Gnawty.5216.239.34:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1653295 Title: Chromium and Chrome flickering (SNA Xorg issues) Status in xorg package in Ubuntu: New Bug description: This is additional debug information as requested for this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1586539 Ubuntu 16.04.1 (xenial) Chrome 55.0.2883.87 Kernel: 3.10.18 X.Org X Server 1.18.4 xorg-server 2:1.18.4-0ubuntu0.2 Current version of pixman: 0.33.6 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Dev
[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
I have no idea why are you having two bugs for the same issue open. The other bug has been reported over 16 months ago, yet made it into LTS release. Oneliner patch, fixed upstream, 16 month ago. Can we expect the thing released before the long term support is over for Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
Still broken in LTS with 0.8.10ubuntu1.1. Sigh. A oneliner patch. Long term suckage. Fix it, ridiculous. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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 1612013] [NEW] apt search "-package" causes a segfault
Public bug reported: user@hostname:~$ apt search -theme Sorting... Error! Full Text Search... 50% // hangs here until a ^C ^C // hangs for about a second here Segmentation fault (core dumped) // the result ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 10 18:46:40 2016 InstallationDate: Installed on 2014-09-04 (707 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2015-12-22 (232 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: - user@hostname:~$ search -theme + user@hostname:~$ apt search -theme Sorting... Error! - Full Text Search... 50% - ^C - Segmentation fault (core dumped) + Full Text Search... 50% // hangs here until a ^C + ^C // hangs for about a second here + Segmentation fault (core dumped) // the result ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 10 18:46:40 2016 InstallationDate: Installed on 2014-09-04 (707 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2015-12-22 (232 days ago) -- 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/1612013 Title: apt search "-package" causes a segfault Status in apt package in Ubuntu: New Bug description: user@hostname:~$ apt search -theme Sorting... Error! Full Text Search... 50% // hangs here until a ^C ^C // hangs for about a second here Segmentation fault (core dumped) // the result ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 10 18:46:40 2016 InstallationDate: Installed on 2014-09-04 (707 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2015-12-22 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1612013/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Same issue for me, Dell Latitude E5450 running 16.04 with all updates. Wifi is sometimes (~1 in 4 times?) disabled after resume. The fix in post #50 above worked for me. This bug is marked "fixed", what is the accepted fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Fix Released Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1424795] Re: Old libselinux in Precise breaks things in Docker on SELinux-enabled host
I don't have a docker setup anymore -- any other watchers able to test? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1424795 Title: Old libselinux in Precise breaks things in Docker on SELinux-enabled host Status in libselinux package in Ubuntu: Incomplete Bug description: In a Docker container running on an SELinux capable kernel, the fact that /sys is mounted RO is supposed to signal to the container that SELinux is not supported on the inside, so it doesn't try to do things that won't work. The version of libselinux in Ubuntu 12.04 is too old to have the above check, breaking basic functionality like shadow- utils. RHEL 6 had the same problem; their fix was to update libselinux: https://bugzilla.redhat.com/show_bug.cgi?id=1112748 Previously reported downstream: https://github.com/tianon/docker-brew- ubuntu-core/issues/29 Release: Ubuntu 12.04.5 LTS Installed package version: 2.1.0-4.1ubuntu1 Expected results: # useradd test # id -Z id: --context (-Z) works only on an SELinux-enabled kernel Actual results: root@b55e77ab9ef4:/# useradd test useradd: failure while writing changes to /etc/passwd root@b55e77ab9ef4:/# vipw vipw: setfscreatecon () failed: Permission denied vipw: /etc/passwd is unchanged root@b55e77ab9ef4:/# id -Z system_u:system_r:svirt_lxc_net_t:s0:c14,c127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1424795/+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 204536] Re: sound volume always resets to 100% after reboot
Same thing happening to me on Ubuntu 16.04. Sound always resets to only 50% and even worse, it's only the left side. Right side is dropped to 0%. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/204536 Title: sound volume always resets to 100% after reboot Status in One Hundred Papercuts: Invalid Status in pulseaudio package in Ubuntu: Fix Released Bug description: Every time I reboot I get the sound volume back to 100%, but the sound works fine apart from this. It's just *very* annoying to have to reset the volume every time I boot the PC. I set the volume from the volume icon in the system tray. I have two sound cards installed on my system (one on the motherboard and a SB Audigy), but I'm using only the Audigy. Another thing is that the mixer applet often incorrectly shows volume as muted when it's not. I'm using the hardy beta (hardy-desktop-amd64) from march 19th 2008. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/204536/+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 1548669] Re: Wrong profile chosen after wake-up from stand-by
I just discovered that it's not reliably reproducible. Maybe already fixed by an update. I'll report more info when it occurs again. -- 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/1548669 Title: Wrong profile chosen after wake-up from stand-by Status in network-manager package in Ubuntu: New Bug description: When the machine wakes up from stand-by, NetworkManager configures my wired interface with the wrong profile. I have 3 profiles (static, static & DHCP), of which only one (DHCP) is set to "connect automatically". This one profile is NOT the one NM chooses to configure the IF. Please tell me whether i can provide more detailed information to help fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1548669/+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 1548669] Re: Wrong profile chosen after wake-up from stand-by
oops, i forgot the version: Ubuntu Gnome 15.10 64-Bit -- 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/1548669 Title: Wrong profile chosen after wake-up from stand-by Status in network-manager package in Ubuntu: New Bug description: When the machine wakes up from stand-by, NetworkManager configures my wired interface with the wrong profile. I have 3 profiles (static, static & DHCP), of which only one (DHCP) is set to "connect automatically". This one profile is NOT the one NM chooses to configure the IF. Please tell me whether i can provide more detailed information to help fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1548669/+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 1548669] [NEW] Wrong profile chosen after wake-up from stand-by
Public bug reported: When the machine wakes up from stand-by, NetworkManager configures my wired interface with the wrong profile. I have 3 profiles (static, static & DHCP), of which only one (DHCP) is set to "connect automatically". This one profile is NOT the one NM chooses to configure the IF. Please tell me whether i can provide more detailed information to help fix this bug. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1548669 Title: Wrong profile chosen after wake-up from stand-by Status in network-manager package in Ubuntu: New Bug description: When the machine wakes up from stand-by, NetworkManager configures my wired interface with the wrong profile. I have 3 profiles (static, static & DHCP), of which only one (DHCP) is set to "connect automatically". This one profile is NOT the one NM chooses to configure the IF. Please tell me whether i can provide more detailed information to help fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1548669/+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 1365020] Re: option "subject-match" not working
Hi tested today with network-manager 1.0.4-0ubuntu5 Problem still exists. Note: the new Network-manager created the lines "altsubject-matches" and "phase2-altsubject-matches" I tried them an the "subject-match" line. I can still connect with "radius.uni-konstanz.de" (the right name" and "nonsense.foo.bar" which is definitely NOT part of the string. -- 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/1365020 Title: option "subject-match" not working Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager supports checking the radius certificates used within 802.1X Infrastructures. These Options are "subject-match" and "phase2-subject-match". However is these options are set the are read by networkmanager at connection activation, but is silently ignored. Even if the String supplied by this option is known wrong the connection can be established. This is a bis isues within wide spread WPA2-Infrastructures like "eduroam" where SSID on the network is well known. This issue exist in pakage Network-manager 0.9.8.8-0ubuntu7 (amd64) In other distributions like Debian 7.6 (network-mamanger 0.9.4.0-10) the option is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+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 1321958] Re: resize2fs does not start to actually grow an ext4
according to http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42.13 this BUG is fixed in e2fsprogs 1.42.12 or higher. "Fix a 32/64-bit overflow bug that could cause resize2fs to loop forever. (Addresses-Launchpad-Bug: #1321958)" is it possible to backport the newest e2fsprogs package to trusty ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 Status in e2fsprogs package in Ubuntu: Triaged Status in e2fsprogs source package in Trusty: Confirmed Bug description: Ubuntu 14.04 LTS, all proposed updates done Kernel: 3.13.0-24-generic, Package: e2fsprogs 1.42.9-3ubuntu1, System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA I tried to increse the size of an ext4 filesystem. Old size 20TB, wanted new size 28TB. I tried offline resize with "resize2fs -fp /dev/md2" and later online resize using "resize2fs -f /dev/md2". In both cases, after giving the command a rezise2fs process is created that uses nearly 100% cpu according to top, but it does not perform any actual resize. It only prints its version and date and then it does not finish for hours. I had it running for more than a day without finishing: root@marvin:~# resize2fs -f /dev/md2 resize2fs 1.42.9 (4-Feb-2014) There is never more terminal output than that. It looks to me that resize2fs hangs in a endless calcualtion or loop or something similar. Some more info about the filesystem: root@marvin:~# tune2fs -l /dev/md2 tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: data Last mounted on: /media/data01 Filesystem UUID: e3845e15-0336-47ae-8aec-df75acb217c5 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 305225728 Block count: 4883606400 Reserved block count: 0 Free blocks: 22919919 Free inodes: 302894731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 2048 Inode blocks per group: 128 RAID stride: 128 RAID stripe width:640 Flex block group size:16 Filesystem created: Fri Sep 20 19:45:01 2013 Last mount time: Tue May 20 02:14:37 2014 Last write time: Tue May 20 02:14:37 2014 Mount count: 3 Maximum mount count: -1 Last checked: Tue May 20 01:34:05 2014 Check interval: 0 () Lifetime writes: 34 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: 569ec5fc-4d5e-4639-bef3-42cde5fbe948 Journal backup: inode blocks I did also run an filesystem check: root@marvin:~# e2fsck -vfp /dev/md2 2330890 inodes used (0.76%, out of 305225728) 14882 non-contiguous files (0.6%) 949 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 2317190/13041/651 4868171016 blocks used (99.68%, out of 4883606400) 0 bad blocks 1654 large files 2273776 regular files 57105 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 2330881 files The underlying device is an mdadm RAID6 that was grown from 7 to 9 disks. The growing finished without problems before I tried to increase the ext4 size. Solution: The solution for me was to downgrade to e2fsprogs 1.42.8. Then the resize did work and finished within a few minutes. I got the hint to do so in a forum from an user, who had the same problem and solved it with
[Touch-packages] [Bug 1496923] [NEW] kodi crashed
Public bug reported: ## Kodi CRASH LOG ### SYSTEM INFO Date: Thu Sep 17 19:30:56 EAT 2015 Kodi Options: Arch: i686 Kernel: Linux 4.2.0-10-generic #11-Ubuntu SMP Sun Sep 13 11:23:03 UTC 2015 Release: Ubuntu 15.10 (Wily Werewolf) ## END SYSTEM INFO ## ### STACK TRACE # # END STACK TRACE ### # LOG FILE ## 19:30:26 T:2933659648 NOTICE: special://profile/ is mapped to: special://masterprofile/ 19:30:26 T:2933659648 NOTICE: --- 19:30:26 T:2933659648 NOTICE: Starting Kodi from Debian (15.1 Git: (unknown)). Platform: Linux x86 32-bit 19:30:26 T:2933659648 NOTICE: Using Debug Kodi from Debian x32 build 19:30:26 T:2933659648 NOTICE: Kodi from Debian compiled from 15.1+dfsg1-3 by GCC 5.2.1 for Linux x86 32-bit version 4.1.3 (262403) 19:30:26 T:2933659648 NOTICE: Running on Ubuntu Wily Werewolf (development branch) 15.10, kernel: Linux x86 32-bit version 4.2.0-10-generic 19:30:26 T:2933659648 NOTICE: FFmpeg version: 2.7.2-1build1 19:30:26 T:2933659648 NOTICE: Host CPU: Pentium(R) Dual-Core CPU E5300 @ 2.60GHz, 2 cores available 19:30:26 T:2933659648 NOTICE: special://xbmc/ is mapped to: /usr/share/kodi 19:30:26 T:2933659648 NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi 19:30:26 T:2933659648 NOTICE: special://masterprofile/ is mapped to: /home/jacobokello/.kodi/userdata 19:30:26 T:2933659648 NOTICE: special://home/ is mapped to: /home/jacobokello/.kodi 19:30:26 T:2933659648 NOTICE: special://temp/ is mapped to: /home/jacobokello/.kodi/temp 19:30:26 T:2933659648 NOTICE: The executable running is: /usr/lib/kodi/kodi.bin 19:30:26 T:2933659648 NOTICE: Local hostname: jacobokello-OptiPlex-760 19:30:26 T:2933659648 NOTICE: Log File is located: /home/jacobokello/.kodi/temp/kodi.log 19:30:26 T:2933659648 NOTICE: --- 19:30:26 T:2933659648INFO: Selected UPower as PowerSyscall 19:30:26 T:2933659648 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanSuspend 19:30:26 T:2933659648 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanHibernate 19:30:26 T:2933659648 DEBUG: DeviceKit.Power: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.DeviceKit.Disks was not provided by any .service files 19:30:26 T:2933659648INFO: Selected Logind/UPower as PowerSyscall 19:30:26 T:2933659648 DEBUG: LogindUPowerSyscall - inhibit lock taken, fd 11 19:30:26 T:2933659648INFO: Selected UPower as PowerSyscall 19:30:26 T:2933659648 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanSuspend 19:30:26 T:2933659648 ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property CanHibernate 19:30:26 T:2933659648 NOTICE: load settings... 19:30:26 T:2933659648 DEBUG: CSettings: loaded settings definition from special://xbmc/system/settings/settings.xml 19:30:26 T:2933659648 DEBUG: CSettings: loaded settings definition from special://xbmc/system/settings/linux.xml 19:30:26 T:2933659648 DEBUG: PulseAudio: Context authorizing 19:30:26 T:2933659648 DEBUG: PulseAudio: Context setting name 19:30:26 T:2933659648 DEBUG: PulseAudio: Context ready 19:30:26 T:2865601344 DEBUG: PulseAudio: Found Built-in Audio Analog Stereo with devicestring alsa_output.pci-_00_1b.0.analog-stereo 19:30:26 T:2933659648 NOTICE: Found 1 Lists of Devices 19:30:26 T:2933659648 NOTICE: Enumerated PULSE devices: 19:30:26 T:2933659648 NOTICE: Device 1 19:30:26 T:2933659648 NOTICE: m_deviceName : Default 19:30:26 T:2933659648 NOTICE: m_displayName : Default 19:30:26 T:2933659648 NOTICE: m_displayNameExtra: Default Output Device (PULSEAUDIO) 19:30:26 T:2933659648 NOTICE: m_deviceType : AE_DEVTYPE_PCM 19:30:26 T:2933659648 NOTICE: m_channels: FL,FR 19:30:26 T:2933659648 NOTICE: m_sampleRates : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000 19:30:26 T:2933659648 NOTICE: m_dataFormats : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT 19:30:26 T:2933659648 NOTICE: Device 2 19:30:26 T:2933659648 NOTICE: m_deviceName : alsa_output.pci-_00_1b.0.analog-stereo 19:30:26 T:2933659648 NOTICE: m_displayName : Built-in Audio Analog Stereo 19:30:26 T:2933659648 NOTICE: m_displayNameExtra: Line Out (PULSEAUDIO) 19:30:26 T:2933659648 NOTICE: m_deviceType : AE_DEVTYPE_PCM 19:30:26 T:2933659648 NOTICE: m_channels: FL,FR 19:30:26 T:2933659648 NOTICE: m_sampleRates : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000 19:
[Touch-packages] [Bug 1175637] Re: Kernel updates are being marked as manually installed
ben-r-xiao, id2ndr: I think that you are running into bug #1492709 or maybe bug #1439769, neither of which involve unattended-upgades. (These two bugs might be the same thing.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1175637 Title: Kernel updates are being marked as manually installed Status in apt package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Updates to the linux-image-* packages in Precise are being marked as "manually" installed, regardless of the auto/manual flag on the existing kernel packages. This happens when updating packages with apt, aptitude, or unattended-upgrades. I'm running an up-to-date 12.04.2 LTS installed (amd64). I can see that my existing kernels were marked as automatically installed: % apt-mark showauto | grep linux-image linux-image-3.2.0-40-generic linux-image-generic And, after the update was performed by unattended-upgrades last night, the new kernel is marked manual: % apt-mark showmanual | grep linux-image linux-image-3.2.0-41-generic This is a problem, because it renders the fix in this bug, https://bugs.launchpad.net/ubuntu/+source/apt/+bug/923876 (Limit and clean-up kernel images and headers automatically in LTS) ineffective, since apt-get autoremove will not remove packages which are marked as manually installed. I'm running the following package versions: apt: 0.8.16~exp12ubuntu10.10 aptitude: 0.8.16~exp12ubuntu10.10 unattended-upgrades: 0.8.16~exp12ubuntu10.10 aptdaemon: 0.43+bzr805-0ubuntu9 This bug looks similar to https://bugs.launchpad.net/aptdaemon/+bug/1078544, however, I'm running a version of aptdaemon that supposedly has this fix applied. Please let me know if I can provide any other useful information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1175637/+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 1485037] [NEW] Russian words containing the letter ё (yo) are marked as misspelled
Public bug reported: Russian spell-checking dictionary currently marks all words containing Ё/ё as misspelled. However, those words must be considered correctly spelled both with Е/е and with Ё/ё. Russian alphabet contains a letter Ё/ё (pronounced as yoh). When writing, Russian language allows substituting this letter with Е/е (pronounced as yeh). But there are cases when the use of Ё/ё is obligatory, that is, when substituting Ё with Е changes the meaning completely. Here is the current workaround: http://askubuntu.com/questions/625302/how-to-teach-ubuntu-15-04-russian-spelling-system-the-%D1%91-letter There is Russian hunspell dictionary which tolerates Ё/ё in the PPA: ppa:andrew-crew-kuznetsov/xneur-stable Maybe we should replace the current hunspell-ru package with the one provided with the PPA or is there a way to merge them? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hunspell-ru (not installed) ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.2 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 14 18:57:36 2015 InstallationDate: Installed on 2014-12-17 (239 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: hunspell-ru UpgradeStatus: Upgraded to vivid on 2015-07-08 (37 days ago) ** Affects: hunspell-ru (Ubuntu) Importance: Undecided Status: New ** Tags: hunspell-ru -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/1485037 Title: Russian words containing the letter ё (yo) are marked as misspelled Status in hunspell-ru package in Ubuntu: New Bug description: Russian spell-checking dictionary currently marks all words containing Ё/ё as misspelled. However, those words must be considered correctly spelled both with Е/е and with Ё/ё. Russian alphabet contains a letter Ё/ё (pronounced as yoh). When writing, Russian language allows substituting this letter with Е/е (pronounced as yeh). But there are cases when the use of Ё/ё is obligatory, that is, when substituting Ё with Е changes the meaning completely. Here is the current workaround: http://askubuntu.com/questions/625302/how-to-teach-ubuntu-15-04-russian-spelling-system-the-%D1%91-letter There is Russian hunspell dictionary which tolerates Ё/ё in the PPA: ppa:andrew-crew-kuznetsov/xneur-stable Maybe we should replace the current hunspell-ru package with the one provided with the PPA or is there a way to merge them? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hunspell-ru (not installed) ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.2 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 14 18:57:36 2015 InstallationDate: Installed on 2014-12-17 (239 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: hunspell-ru UpgradeStatus: Upgraded to vivid on 2015-07-08 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/1485037/+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 1067434] Re: Sound output device keeps changing when using headphones
Just posting to say That I still have this problem, I'm running the newest linux mint KDE. I don't have pulse audio installed. I had to plug my main sound into the headphone jack. (it's on top of my case, works for me) >uname -a Linux -desktop 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Well looking at the above output I guess i'm still using a 2014-sep build. >lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 17.1 Rebecca Release:17.1 Codename: rebecca So I'm not sure if this is the most recent version or not... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1067434 Title: Sound output device keeps changing when using headphones Status in alsa-driver package in Ubuntu: Expired Bug description: Recently upgraded to 12.10. Having issues with sound when using headphones plugged into the front ports. Something that doesn't happen when booting to windows - so fairly confident it's an Ubuntu issue. When listening to any sound, music, video etc the sound levels jump up and down and click. If I open "sound" from the settings menu when playing videos or music and viewing the "output" tab I can see "headphone - built-in audio disappear and reappear (very quickly) so I'm guessing the system is jumping back to the "analogue output" and back again which is why the sound volume changes and clicks. Worth noting I never used my headphones when 12.04 was installed so not sure if it's this OS or Ubuntu hates my hardware generally. Booted from live cd (usb) to 12.04 and there wasnt any issue. Anyone seen this before? any advice? Sound is built in to motherboard. I have the Gigabyte GA-X58A-UD5. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Tue Oct 16 18:07:44 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-09-29 (17 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1067434/+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 1437814] [NEW] artifacting in some apps
Public bug reported: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description:Ubuntu Vivid Vervet (development branch) Release:15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Displays Setting Dialogue" https://bugs.launchpad.net/bugs/1437814/+attachment/4359654/+files/Selection_004.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1437814 Title: artifacting in some apps Status in ubuntu-themes package in Ubuntu: New Bug description: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1437814/+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 1426609] [NEW] windows jitter after scrolling
Public bug reported: when scrolling through some windows the content will sometimes move up or down a line by itself repeatedly, mousing over the content will stop this effect and sometimes it may not even be the content that was jittering about previously. I am using Ubuntu 14.10 , Installed unity is version 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.47 Thu Feb 19 18:56:03 PST 2015 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 28 12:10:24 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: nvidia, 346.47, 3.16.0-31-generic, x86_64: installed vboxhost, 4.3.20, 3.16.0-29-generic, x86_64: installed vboxhost, 4.3.20, 3.16.0-30-generic, x86_64: installed vboxhost, 4.3.20, 3.16.0-31-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:847a] InstallationDate: Installed on 2014-12-03 (86 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-31-generic root=UUID=9e91e463-342e-4c20-a7e6-550217ed6507 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Feb 28 00:24:20 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1426609 Title: windows jitter after scrolling Status in unity package in Ubuntu: New Bug description: when scrolling through some windows the content will sometimes move up or down a line by itself repeatedly, mousing over the content will stop this effect and sometimes it may not even be the content that was jittering about previously. I am using Ubuntu 14.10 , Installed unity is version 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.47 Thu Feb 19 18:56:03 PST 2015 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat F
[Touch-packages] [Bug 1365020] Re: option "subject-match" not working
tried again with network-manager 0.9.8.8-0ubuntu28 problem still exists. the subject-match line is read by network-manager but has no effect at all. If i created a wpa_suplicant configuration instead the string is verified and the connection will not be established with the wrong string.So i can confirm wpa_supplicant working properly but network-manager is still broken somehow. -- 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/1365020 Title: option "subject-match" not working Status in network-manager package in Ubuntu: Incomplete Bug description: NetworkManager supports checking the radius certificates used within 802.1X Infrastructures. These Options are "subject-match" and "phase2-subject-match". However is these options are set the are read by networkmanager at connection activation, but is silently ignored. Even if the String supplied by this option is known wrong the connection can be established. This is a bis isues within wide spread WPA2-Infrastructures like "eduroam" where SSID on the network is well known. This issue exist in pakage Network-manager 0.9.8.8-0ubuntu7 (amd64) In other distributions like Debian 7.6 (network-mamanger 0.9.4.0-10) the option is working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1365020/+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 1405529] [NEW] computer get passed log in then crashes
Public bug reported: i think its missing a start up file but then again its my gma computer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 24 20:46:34 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a92] InstallationDate: Installed on 2014-11-27 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: HP-Pavilion NY549AA-ABA p6230y ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.03 dmi.board.name: ALOE dmi.board.vendor: FOXCONN dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.03:bd09/11/2009:svnHP-Pavilion:pnNY549AA-ABAp6230y:pvr:rvnFOXCONN:rnALOE:rvr1.01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: NY549AA-ABA p6230y dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Dec 24 13:16:13 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1405529 Title: computer get passed log in then crashes Status in xorg package in Ubuntu: New Bug description: i think its missing a start up file but then again its my gma computer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 24 20:46:34 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a92] InstallationDate: Installed on 2014-11-27 (27 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: HP-Pavilion NY549AA-ABA p6230y ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.03 dmi.board.name: ALOE dmi.board.vendor: FOXCONN dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.03:bd09/11/2009:svnHP-Pavilion:pnNY549AA-ABAp6230y:pvr:rvnFOXCONN:rnALOE:rvr1.01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: NY549AA-ABA p6230y dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
[Touch-packages] [Bug 1301015] Re: Networking does not restart
Unreal!
Does anyone from Canonical understand the impact of this change?
This breaks any and all remote automation!
Please address this issue!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in ifupdown package in Ubuntu:
Confirmed
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service < option > | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case "${1}" in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case "${1}" in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case "${ACTION}" in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
I'm also having this problem. I have just recently upgraded from 14.04 to 14.10 Ubuntu. I am wondering if this could in any way have to do with two administrator users on the same system. My system always has four users and two of them are administrators. I've never had anything like this happen before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid Status in “gdm” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lxdm” package in Ubuntu: Confirmed Status in “policykit-desktop-privileges” package in Ubuntu: Confirmed Bug description: After a new install of 64 bit Ubuntu 13.10 on my second partition, I used dpkg to reinstall all the same packages I had on my 32 bit 13.04 partition. I copied all my home directory files over and updated all the packages. I now find that I don't have permissions to change the network settings; I can't mount my other hard drive or any USB stick using nautilus, or (udisks without using sudo)' I can't run synaptic by clicking on the GUI (I have to go to a terminal and sudo synaptic); etc. I can't find any documentation on the configuration of policykit-desktop-privileges, so I'm filing this bug. For me it appears to be totally broken. Maybe someone can help me out. Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+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
