[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here with Sony WH-1000MX2 with Ubuntu 20.04.1 LTS kernel 5.6.0-1021-oem -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1872926] Re: font scaling
Hello, thanks for the repla. I did some others tries, it work perfectly at font scaling 1.25, so i think is a problem about fractal scaling? -- 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/1872926 Title: font scaling Status in xorg package in Ubuntu: Invalid Bug description: i use font scaling at 1.20 an it doesn't work on skype, chrome, discord whatsdesk etc i need to edit all the launcher to use it ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:43:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2020-04-09 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 04f2:b449 Chicony Electronics Co., Ltd Integrated Camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BWS3MG00 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e64bf22d-6dd2-4ba5-9de7-df6dbf8d2dc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS3MG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BWS3MG00:pvrThinkPadT450s:rvnLENOVO:rn20BWS3MG00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS3MG00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872926/+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 1607038] Re: QCameraImageCapture::supportedResolutions reports incorrect max. resolution on Aquaris E5 HD
Hi. About my "bq Aquaris E4.5 Ubuntu Edition", app AIDA64 in section "Devices" reports: back camera 13.4 mp front camera 8.3 mp ...but "bq Aquaris E4.5 Ubuntu Edition" has: back camera 8.0 mp front camera 5.0 mp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1607038 Title: QCameraImageCapture::supportedResolutions reports incorrect max. resolution on Aquaris E5 HD Status in qtubuntu-camera package in Ubuntu: Confirmed Bug description: Our test device bq Aquaris E5 HD Ubuntu Edition (15.04 OTA-11 / Device Image Part 20160524-63b1875) seems to report 20 MegaPixel resolution for the back camera, and 8 MP for the front camera. While according to the device spec it should have a 13 MP back camera and 5 MP front camera. The issue seems to affect the built-in Camera app as well, since it shoots exactly the same resolution photos. Back camera photos are shot at 5888x3312 pixels, and front camera photos are shot at 3840x2160 pixels. You can verify the issue using e.g. AIDA64 (Devices page), or by simply shooting some photos using the built-in Camera app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-camera/+bug/1607038/+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 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled
I have the same problem after upgrading to 16.04 from 14.04. I am using a Kaveri APU, that is supposed to work with both "radeon" and "amdgpu" drivers. The "radeon" driver doesn't work: after the very initial steps of the bootstrap, the screen goes black, although a may access the system via SSH. Setting "nomodeset" prevents the "radeon" driver to start, reverting back to basic driver. However, the new "amdgpu" driver seems working fine. I managed to fix the issue in the following way: 1. blacklist "radeon", by creating a new file /etc/modprobe.d/blacklist-radeon.conf having a single line "blacklist radeon"; 2. force "amdgpu", by appending to /etc/modules the line "amdgpu"; 3. setting the screen resolution in grub, by uncomment the line GRUB_GFXMODE, e.g. "GRUB_GFXMODE=1280x1024"; 4. create a new file /etc/X11/xorg.conf, having a block Section "Device" Identifier "VideoCard" DriveR "amdgpu" EndSection 5. update initramfs, via "update-initramfs -u -k all" with sudo; 6. update grub configuration, via "update-grub" with sudo. Maybe other user having a GCN-enabled AMD video card may fix the issue in the same way. -- 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/1568429 Title: 1002:68b8 Radeon won't work with KMS enabled Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading to Xenial today and ensuring the xorg radeon driver was enabled, when booting both monitor lose signal input and the keyboard becomes unresponsive. My hardware: 02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990] WORKAROUND: Use one of the following kernel parameters: nomodeset radeon.modeset=0 The machine will boot but the radeon driver will not load. Attempting to load radeon driver with `sudo modprobe radeon modeset=1` after booting with modesetting off results in the same fail state explained above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds] CompositorRunning: None Date: Sat Apr 9 20:02:22 2016 DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990] InstallationDate: Installed on 2013-12-29 (832 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago) dmi.bios.date: 04/29/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0519 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-exper
[Touch-packages] [Bug 1752123] Re: Force 8bit RGB config
** Changed in: mutter (Ubuntu) Status: In Progress => Triaged -- 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/1752123 Title: Force 8bit RGB config Status in cogl package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Triaged Bug description: New mesa supports 10bit RGB configs, and this causes issues with cogl/mutter which get a random EGLConfig that breaks some autopkgtests. To fix this this merge request is needed for mutter https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 and a similar one for cogl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1752123/+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 1752053] Re: nvidia-390 fails to boot graphical display
All the required components should be in Bionic now. I am closing this bug report. Feel free to file a new bug report, if you experience any further problems with the driver. P.S. disabling the discrete GPU (on systems with hybrid graphics) does not work yet, but it will soon. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1731417] Re: Installed network printer removed automatically when turned off
Attached output with printer powered on and bonjour enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed network printer removed automatically when turned off
** Attachment added: "avahi.txt" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5088131/+files/avahi.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed network printer removed automatically when turned off
** Changed in: hplip (Ubuntu) Status: Incomplete => Confirmed ** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed network printer removed automatically when turned off
I can also confirm that if I disable bonjour, the printer no longer gets removed once it's turned off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed network printer removed automatically when turned off
Sorry, I previously attached the output from the run with bonjour disabled. This is with it enabled. ** Attachment added: "avahi.txt" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5090971/+files/avahi.txt ** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed ** Changed in: hplip (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 697498] Re: [Realtek ALC269VB] No sound from internal speakers, but headphone jack works
Hi everyone, I'm just new using Linux. Installed Zorin 12 in my netbook
and I have exactly the same problem with the Realtek ALC269VB, no sound
with the speakers but headphones work well. Thanks in advance for your
help. looking at the alsamixer, the speaker channel is apparently not
connected with the speakers.
The channel of the headphones is muted but once I plug the headphones,
it works well. If I proceed and manually unmute the same headphone
channel without headphones, I can get sound from the speakers. However,
once the pc is rebooted comes back to the same problem.
Big Regards and thanks in advance.
--
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/697498
Title:
[Realtek ALC269VB] No sound from internal speakers, but headphone jack
works
Status in alsa-driver package in Ubuntu:
Fix Released
Bug description:
Following the instructions in this troubleshooting guide:
https://help.ubuntu.com/community/SoundTroubleshooting
I couldn't find my codec (Realtek ALC259) in the list of ALSA-supported
codecs.
Sound does not come out of the internal speakers. However when I plug
headphones into the headphone jack, I can hear sound. This is an Asus
EeePC 1015PEM.
Alsa system configuration dump:
http://www.alsa-project.org/db/?f=f92e22d0373cd586b553b9964d8f6e1d4e86d6b6
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: alsa-base 1.0.23+dfsg-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic i686
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on Jan 5 2011 for kernel 2.6.35-24-generic (SMP).
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tlau 1547 F pulseaudio
/dev/snd/pcmC0D0p: tlau 1547 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 46'
Mixer name : 'Realtek ALC269VB'
Components : 'HDA:10ec0269,1043841c,00100100'
Controls : 11
Simple ctrls : 7
Date: Tue Jan 4 19:56:00 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [Realtek ALC269VB] ALSA test tone not correctly played back
dmi.bios.date: 10/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/27/2010:svnASUSTeKComputerINC.:pn1015PEM:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PEM
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/697498/+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 1731417] Re: Installed network printer removed automatically when turned off
@Till do you have any insight on this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
It seems like the kernel and the nvidia driver weren't built using the
same compiler.
Please, either ssh into your machine, or press CTRL+ALT+F2 and do the
following:
1) Make sure security updates are enabled, and update your system ("apt-
cache policy gcc-5" should report 5.4.0-6ubuntu1~16.04.9 on Xenial)
2) Make sure no driver from NVIDIA's website is installed. If it is,
please uninstall it first.
3) When gcc-5 is updated, re-install the nvidia package from the archive:
sudo apt-get install --reinstall nvidia-384 (or nvidia-340)
4) Restart your computer.
--
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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
16.04)
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
Confirmed
Status in xorg package in Ubuntu:
Confirmed
Bug description:
Running fine with nvidia-384 until this kernel update came along.
When booted into the new kernel, got super low resolution and nvidia-
settings was missing most of its functionality - could not change
resolution.
Rebooted into 4.4.0-112 kernel and all was well.
The root cause of the problem has been found to be installing the -116
kernel without a sufficiently updated version of gcc. In my case, my
system received the gcc update AFTER the kernel update.
Uninstalling the -116 kernel and reinstalling it with the updated
version of gcc solved the problem for me.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45
PST 2017
GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Feb 21 19:23:39 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device [3842:6253]
InstallationDate: Installed on 2015-03-03 (1086 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
MachineType: ASUSTeK COMPUTER INC. M11AD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M11AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: M11AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 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: Wed Feb 21 18:48:14 2018
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Triaged => In Progress ** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: Triaged Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
** Changed in: pulseaudio (Ubuntu Bionic) Status: Triaged => In Progress -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please approve pulseaudio 11.1-1ubuntu7.1 in bionic-proposed. ** Description changed: - As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped - working properly. It was working fine in Jaunty. + SRU Request: + + [Impact] + When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. + + [Test Case] + 1) Enable the -proposed repository, and install the new pulseaudio + + 2) Restart your computer, connect it to a bluetooth device (e.g. a + headset or a speaker), play one or more videos either locally or online, + and see if you can still reproduce the problem. + + [Regression Potential] + Low, as the changes are upstream, and, if anything, it should also fix a memory leak. + + + As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: http
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@Łukasz: I have updated the regression potential part with more details. As a side note, I've been running the code for days, using my Yamaha SRT-1000 (a bluetooth soundbar) with my laptop, and I have yet to see the audio go out of sync, or crackle (which were quite frequent before the changes). This makes bluetooth audio pretty much on par with MacOS. ** Description changed: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. + + Furthermore, the changes only affect the bluez5-device module, in + pulseaudio, and they make the buffer updating logic more conscious of + how things can change when the connection drops. This is unlikely to + affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 puls
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
The packages in bionic-proposed work well here, on my Lenovo Yoga Pro 2 with my Yamaha SRT-1000 soundbar. Sound quality is really good using A2DP, and the audio never goes out of sync when I watch videos, and it doesn't break up when I listen to music. I'm also attaching the output of "apt-cache policy '*pulse*'". ** Attachment added: "installed-packages" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/+attachment/5144156/+files/installed-packages ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
Attaching the debdiff ** Patch added: "systemd_237-3ubuntu10.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777099/+attachment/5154277/+files/systemd_237-3ubuntu10.2.debdiff -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
I have tested the new packages here, and I can confirm that they solve the problem. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: Triaged Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] * It should be possible to change DRM driver without rebooting. * It should be possible to correctly suspend & resume, whilst preserving driver state. * This bug is for userspace/logind fixes, required to get above working. * Related kernel change is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778658 * https://github.com/torvalds/linux/commit/5775b843a619b3c93f946e2b55a208d9f0f48b59 [Test Case] * Test and verify that on machines with Nvidia discrete graphics, one can change performance/power-saving modes without rebooting. [Regression Potential] * There are changes to the fd handling that are passed to logind. At worst, fd to the NVIDIA driver will still be held, and thus one would continue to not be able to switch graphics modes without rebooting. [Other Info] * original bug report: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+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 1762200] Re: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1762200 Title: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: System: Ubuntu 18.04 (08.04.2018 updated) PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m *** I installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm greeter only purple background. greeter in primary(unknown) screen Please check screenshot *** U1804PC:~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05) 09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) 0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) U1804PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1762200/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Triaged Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/175/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
** Changed in: software-properties (Ubuntu) Status: Triaged => In Progress ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
The fix for this bug is in the bazaar branch listed above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1766574] Re: Installation failed if systemd isn't installed: /var/lib/dpkg/info/rsyslog.postinst: 28: /var/lib/dpkg/info/rsyslog.postinst: systemd-tmpfiles: not found
The steps I used to reproduce are: docker run --rm -it ubuntu:bionic /bin/bash then run apt update && apt install rsyslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1766574 Title: Installation failed if systemd isn't installed: /var/lib/dpkg/info/rsyslog.postinst: 28: /var/lib/dpkg/info/rsyslog.postinst: systemd-tmpfiles: not found Status in rsyslog package in Ubuntu: Confirmed Bug description: If you have an image that doesn't have systemd installed, installing rsyslog fails with the following error: /var/lib/dpkg/info/rsyslog.postinst: 28: /var/lib/dpkg/info/rsyslog.postinst: systemd-tmpfiles: not found If I install the systemd package, the rsyslog installation succeeds. This is with with version 8.32.0-1ubuntu3 in bionic. A quick way of reproducing this is to grab the latest docker bionic image and try to install rsyslog in there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766574/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails
The code in my MP was approved. Please merge it, and let's proceed with the SRU. ** Description changed: - When you are in the initial install state, you can easily switch from - the Nouvea drivers to the Nvidia drivers by choosing the option in - "Software and Updates -> Additional Drivers". However, when you attempt - to switch back (by selecting the nouveau option and clicking Apply), and - subsequently reboot, your system will still come up using the Nvidia - drivers, and you will WTF. + SRU Request: + + [Impact] + Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. + + We should make sure to uninstall all its nvidia related dependencies, + not only the meta-package. + + [Test Case] + 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab + + 2) Uninstall the NVIDIA 390 driver + + 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: + + apt-cache policy nvidia-dkms-390 + + The package will be reported as installed, because the current code + didn't remove it. + + [Regression Potential] + Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. + + __ + When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the Additional Drivers tool. But obviously there is no real way for inexperienced users to know this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/175 Title: Using "Software and Updates -> Additional Drivers" to Switch Fails Status in software-properties package in Ubuntu: In Progress Bug description: SRU Request: [Impact] Currently, the Additional Drivers tool uninstalls only the driver package that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that package is only a meta-package. Removing the meta-package will not uninstall the driver. We should make sure to uninstall all its nvidia related dependencies, not only the meta-package. [Test Case] 1) Open the "Software & Updates" app, and select the "Additional Drivers" tab 2) Uninstall the NVIDIA 390 driver 3) Check that, for example, the nvidia-dkms-390 package was uninstalled: apt-cache policy nvidia-dkms-390 The package will be reported as installed, because the current code didn't remove it. [Regression Potential] Relatively low, as the change in behaviour only affects the nvidia driver, and it only causes the Additional Drivers tool to remove dependencies of the meta-package that have the "nvidia" string in their name. __ When you are in the initial install state, you can easily switch from the Nouvea drivers to the Nvidia drivers by choosing the option in "Software and Updates -> Additional Drivers". However, when you attempt to switch back (by selecting the nouveau option and clicking Apply), and subsequently reboot, your system will still come up using the Nvidia drivers, and you will WTF. And then, if you visit Additional Drivers, you will be presented with grayed out options for both nvidia and nouvea, and the only selectable option will be "continue using manually installed driver". The reason for this is that the tool, when reselecting nvidia in the GUI, uninstalls the nvidia-drivers-390 package, but because it's a metapackage (or at least I presume this is the reason), it doesn't uninstall its dependencies, which causes the Additional Drivers tool to believe it's in a non-automanaged state, and the nvidia drivers never actually get uninstalled. You can fix it by doing an apt autoremove and rerunning the
[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+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 1761593] Re: Uninstall left nouveau blacklisted
@Doug: I'm working on the meta-package part for LP: #175 , this is a separate bug report, only about the blacklist file. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+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 1761593] Re: Uninstall left nouveau blacklisted
** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** No longer affects: software-properties (Ubuntu Bionic) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: New Status in nvidia-graphics-drivers-390 source package in Bionic: Triaged Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+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 1731417] Re: Installed printer removed after suspend/resume
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: New Status in hplip package in Ubuntu: New Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1741565] [NEW] package gtk-update-icon-cache (not installed) failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2
Public bug reported: I don't know what happend ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gtk-update-icon-cache (not installed) ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.9 AptOrdering: gtk-update-icon-cache:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jan 5 14:56:46 2018 DpkgHistoryLog: Start-Date: 2018-01-05 14:56:44 Commandline: apt --fix-broken install Requested-By: amartinez (1000) Install: gtk-update-icon-cache:amd64 (3.22.11-0ubuntu3, automatic) ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 InstallationDate: Installed on 2017-03-15 (296 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: gtk+3.0 Title: package gtk-update-icon-cache (not installed) failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1741565 Title: package gtk-update-icon-cache (not installed) failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 Status in gtk+3.0 package in Ubuntu: New Bug description: I don't know what happend ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gtk-update-icon-cache (not installed) ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.9 AptOrdering: gtk-update-icon-cache:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jan 5 14:56:46 2018 DpkgHistoryLog: Start-Date: 2018-01-05 14:56:44 Commandline: apt --fix-broken install Requested-By: amartinez (1000) Install: gtk-update-icon-cache:amd64 (3.22.11-0ubuntu3, automatic) ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 InstallationDate: Installed on 2017-03-15 (296 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: gtk+3.0 Title: package gtk-update-icon-cache (not installed) failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1741565/+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 1731417] Re: Installed printer removed after suspend/resume
The issue persists on bionic ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: New Status in hplip package in Ubuntu: New Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Same behaviour in current Bionic installs (package version is the same as Artful) ** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in ubuntu-font-family-sources package in Ubuntu: In Progress Status in ubuntu-font-family-sources source package in Wily: Triaged Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "access_log" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037376/+files/access_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037377/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "cupsd.conf" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037370/+files/cupsd.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "cups-browsed.conf" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037371/+files/cups-browsed.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "cups-browsed_log" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037378/+files/cups-browsed_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "lpstat-after-print.txt" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037374/+files/lpstat-after-print.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "lpstat-after-add.txt" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037373/+files/lpstat-after-add.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "printers.conf-after-print" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037375/+files/printers.conf-after-print -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
Added all logs. After suspend the printer is gone and lpstat -v reports "No destinations" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Attachment added: "printers.conf" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417/+attachment/5037372/+files/printers.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
AFAICS from the cups-browserd_log, CUPS seems to be removing the printer when avahi doesn't see it anymore (because it's been turned off). This didn't happen before, I would only install the printer once and it'd be there forever. I think only avahi-discovered printers should be automatically removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed printer removed after suspend/resume
** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed ** Changed in: hplip (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1731417] Re: Installed network printer removed automatically when turned off
Updated the bug title, as it's not really related to suspend/resume ** Summary changed: - Installed printer removed after suspend/resume + Installed network printer removed automatically when turned off -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off Status in cups package in Ubuntu: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1793382] [NEW] Add aethercast support in AppArmor file
Public bug reported: Canonical modified the AppArmor policy in order to make authercast work: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz (only the first chunk of the patch is relevant to this issue) This was added to the package we were using in the phone overlay PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+packages?batch=75&memo=75&start=75 Now we need the same in Ubports, but it would be convenient if we added this in Ubuntu, to reduce the delta. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Description changed: Canonical modified the AppArmor policy in order to make authercast work: - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- - phone-overlay/+files/isc- - dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz + https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz + (only the first chunk of the patch is relevant to this issue) This was added to the package we were using in the phone overlay PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+packages?batch=75&memo=75&start=75 Now we need the same in Ubports, but it would be convenient if we added this in Ubuntu, to reduce the delta. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1793382 Title: Add aethercast support in AppArmor file Status in isc-dhcp package in Ubuntu: New Bug description: Canonical modified the AppArmor policy in order to make authercast work: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz (only the first chunk of the patch is relevant to this issue) This was added to the package we were using in the phone overlay PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+packages?batch=75&memo=75&start=75 Now we need the same in Ubports, but it would be convenient if we added this in Ubuntu, to reduce the delta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1793382/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
I have uploaded linux-base_4.5ubuntu1.3 (bionic) and linux- base_4.5ubuntu3.2 (focal). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: In Progress Status in debianutils source package in Bionic: New Status in linux-base source package in Bionic: New Status in debianutils source package in Focal: New Status in linux-base source package in Focal: New Status in debianutils source package in Hirsute: New Status in linux-base source package in Hirsute: In Progress Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1949075] [NEW] Bluetooth headset not autoconnecting on power-on on 21.10
Public bug reported: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.pr
[Touch-packages] [Bug 1949089] [NEW] systemd randomly fails to activate mount units in Ubuntu Core 18
Public bug reported: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc-flip- flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Attachment added: "journald log" https://bugs.launchpad.net/bugs/1949089/+attachment/5536819/+files/journal.log -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
I'm coming with bad news. Today both me and Michael have individually retested both snaps you provided (20211102 and 20211105), and the bug happened with both of them. It's possible that yesterday Michael accidentally used QEMU for his tests, without realizing (and in QEMU it seems that this bug is not reproducible). Here are the spread logs (plus "journalctl -xe") obtained in the 21211105 snap: https://paste.ubuntu.com/p/CnnyXNC2Tt/ -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
> can you provide steps on how this is reproducable then? So far we have not been able to isolate the problem, so the only way so far is to run the spread tests from the snapd directory (from the master branch): spread -debug -repeat 20 google:ubuntu- core-18-64:tests/main/services-disabled-kept-happy -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
An update to the comment above. We have found out a sequence of commands that seems to reproduce the issue reliably: in the spread session started by the command from the comment above, if you type this: systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl daemon-reload # The two commands above are just to ensure that the unit is in the unmounted state systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl daemon-reload systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount' The last command will hang for 90 seconds, after which the job will fail and `journalctl -xe` will show that it failed because systemd timed out while activating a loop device. In reality, the loop device is already there and is available, but somehow the `deamon-reload` operation broke the internal status. If you remove the line with `systemctl daemon-reload` (or, on the other hand, add one such line even after the `stop` command), then everything proceeds normally. I'm EOD now, but tomorrow I'll verify if this happens on classic too. -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Might be related to https://github.com/systemd/systemd/issues/11342 ** Bug watch added: github.com/systemd/systemd/issues #11342 https://github.com/systemd/systemd/issues/11342 -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
One more update: I verified that the steps from comment #17 can be used to reproduce the issue in an Ubuntu Core image started in qemu, and without using the spread. I verified it with the 20211105 image provided by Lukas in https://people.ubuntu.com/~slyon/uc18/ To reproduce it, start the image in QEMU: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=~/Downloads/uc18-20211105+systemd+3G.img,format=raw \ -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on configure it as usual, and install a snap. Then: sudo snap install hello-world sudo systemctl start 'snap-hello\x2dworld-29.mount' sudo systemctl daemon-reload sudo systemctl stop 'snap-hello\x2dworld-29.mount' sudo systemctl start 'snap-hello\x2dworld-29.mount' The last command will hang for 90 seconds, after which the logs (`sudo journalctl -xe`) will say: ``` Nov 15 06:10:20 localhost systemd[1]: dev-loop6.device: Job dev-loop6.device/start timed out. Nov 15 06:10:20 localhost systemd[1]: Timed out waiting for device /dev/loop6. -- Subject: Unit dev-loop6.device has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit dev-loop6.device has failed. -- -- The result is RESULT. Nov 15 06:10:20 localhost systemd[1]: Dependency failed for Mount unit for hello-world, revision 29. -- Subject: Unit snap-hello\x2dworld-29.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit snap-hello\x2dworld-29.mount has failed. -- -- The result is RESULT. Nov 15 06:10:20 localhost systemd[1]: snap-hello\x2dworld-29.mount: Job snap-hello\x2dworld-29.mount/start failed with result 'dependency'. Nov 15 06:10:20 localhost systemd[1]: dev-loop6.device: Job dev-loop6.device/start failed with result 'timeout'. ``` -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thanks Lukas! It's very likely that there are several issues in this area, because while I can confirm that your latest image fixes the reproducer I pasted before (in the Google cloud, too), the spread test failure is still reproducible with the "tests/main/services-disabled- kept-happy" test. I need to have a closer look at this test case, to understand what exact steps snapd is taking, and see if we can again find a reproducer without involving snapd. -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
I still see this in 20.04 -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+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 1942208] Re: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1942208 Title: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers" Status in OEM Priority Project: Confirmed Status in software-properties package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version table: 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942208/+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 1650688] Re: timedatectl set-timezone fails on UC16
** Patch added: "Support-system-image-read-only-etc.patch" https://bugs.launchpad.net/snappy/+bug/1650688/+attachment/5543088/+files/Support-system-image-read-only-etc.patch -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: New Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates the localtime symbolic link with a relative path to the zoneinfo directory, which results in an invalid link. $ sudo timedatectl set-timezone America/Detroit $ sudo timedatectl Local time: Fri 2016-12-16 18:18:49 EST Universal time: Fri 2016-12-16 23:18:49 UTC RTC time: Fri 2016-12-16 23:18:49 Time zone: America/Detroit (EST, -0500) Network time
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
I can confirm that Ratchanan's patches work (well, I only tried the one on timedated, as the one on timedatectl is not essential to fix this bug). But I don't think that it should be treated separately from the existing patch we have, so I'm attaching a refreshed patch which includes Ratchanan's change. Still, we probably want to explore other solutions, since Dan (@ddstreet) is also right that carrying hacks for 7 years is something we should avoid doing. But I don't have many alternative ideas :-( Unfortunately, bind-mounting /etc/writable/localtime over /etc/localtime does not work, because when mounting, the kernel follows all symbolic links, so we end up bind- mounting the timezone file (for example "/usr/share/zoneinfo/Europe/Berlin") on top of itself :-) -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: New Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On
[Touch-packages] [Bug 1949075] Re: Bluetooth headset not autoconnecting on power-on on 21.10
** Tags added: champagne rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1931776] [NEW] package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de
Public bug reported: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 12 11:31:14 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-06-02 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1931776 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: package initramfs-tools 0.136ubuntu6.5 failed to install/: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: intel-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 12 11:31:14 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-06-02 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931776/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Eugene (and others), if you are still affected by this bug, please follow bug 1666285 instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu: Fix Released Status in account-plugins source package in Quantal: Fix Released Status in signon-plugin-oauth2 source package in Quantal: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Fix Released Status in signon-plugin-oauth2 source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1675273] Re: Can't add online account
The "Add account" button should simply show you a list of account providers on the right side of the system settings panel. Then you need to click on one of them, in order to start the account creation. If that does not work, please provide a screenshot. ** Changed in: account-plugins (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1675273 Title: Can't add online account Status in account-plugins package in Ubuntu: Incomplete Bug description: 'add account' does nothing, it's a dead button. Ubuntu 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1675273/+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 1673984] Re: Can not add google account any more (Zesty)
Fix available here, waiting for QA: https://bileto.ubuntu.com/#/ticket/2608 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) Status in Canonical System Image: New Status in signon-ui package in Ubuntu: Confirmed Bug description: After updating Unity-Control-Center to 15.04.0+17.04.20170314-0ubuntu2 and liboxidecore to 1.20.4-0ubuntu1 on Zesty I could not able to add to add Google account. ### How to reproduce: 1. Go online account try adding google account. 2. Infobar will appear for a moment and the it will disappear. Screenshot: https://i.imgur.com/evDPZSv.png 3. The login page doesn't load at all. Running online-accounts-preferences from terminal gives: -- (unity-control-center:7866): credentials-cc-panel-CRITICAL **: cc-credentials-authorization-page.vala:182: Error completing auth session process: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 2 -- Installed Packages (Ubuntu 17.04 32 bit): account-plugin-google: 0.13+17.04.20161206-0ubuntu1 signon-ui-x11: 0.17+17.04.20161109-0ubuntu1 unity-control-center: 15.04.0+17.04.20170314-0ubuntu2 unity-control-center-signon: 0.1.9+16.10.20160825-0ubuntu1 All other packages are up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673984/+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 1676219] Re: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which i
*** This bug is a duplicate of bug 1451728 *** https://bugs.launchpad.net/bugs/1451728 ** This bug has been marked a duplicate of bug 1451728 [master] kde-config-telepathy-accounts package install error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1676219 Title: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services /google-im.service', which is also in package kde-config-telepathy- accounts 4:15.08.2-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: running upgrade ProblemType: Package DistroRelease: Ubuntu 15.10 Package: account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Mar 26 16:15:12 2017 DpkgHistoryLog: Start-Date: 2017-03-26 16:15:00 Commandline: aptdaemon role='role-commit-packages' sender=':1.135' Upgrade: rhythmbox-plugins:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), gir1.2-gst-plugins-base-1.0:amd64 (1.6.0-1ubuntu1, 1.6.3-1ubuntu1), rhythmbox-plugin-magnatune:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), rhythmbox-data:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), rhythmbox-plugin-cdrecorder:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), rhythmbox:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), rhythmbox-plugin-zeitgeist:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), gir1.2-gstreamer-1.0:amd64 (1.6.0-1, 1.6.3-1ubuntu1), account-plugin-google:amd64 (0.12+15.04.20150415.1-0ubuntu2, 0.12+15.10.20150723-0ubuntu1), gir1.2-rb-3.0:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1), librhythmbox-core9:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu3.1) DpkgTerminalLog: Preparing to unpack .../account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb ... Unpacking account-plugin-google (0.12+15.10.20150723-0ubuntu1) over (0.12+15.04.20150415.1-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+15.10.20150723-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1 DuplicateSignature: package:account-plugin-google:0.12+15.04.20150415.1-0ubuntu2:trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1 InstallationDate: Installed on 2015-02-28 (757 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: account-plugins Title: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package kde-config-telepathy-accounts 4:15.08.2-0ubuntu1 UpgradeStatus: Upgraded to wily on 2016-06-11 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1676219/+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 1676893] [NEW] Inform client if ContentHub service is not available
Public bug reported:
An app using the Content Hub QML API might have the need to know whether
service is actually available, in order to fall back to other means if
it isn't.
This is especially relevant for snaps: if the snap uses the content from
ubuntu-app-platform, the QML module of the ContentHub will be available,
but this doesn't guarantee that the CH service is running. It might not
be installed (for example, in another distro), not running or maybe not
reachable due to confinement.
I propose adding a "valid" property to the ContentHub singleton which
would tell whether the service is available.
** Affects: content-hub (Ubuntu)
Importance: Undecided
Assignee: Alberto Mardegan (mardy)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1676893
Title:
Inform client if ContentHub service is not available
Status in content-hub package in Ubuntu:
New
Bug description:
An app using the Content Hub QML API might have the need to know
whether service is actually available, in order to fall back to other
means if it isn't.
This is especially relevant for snaps: if the snap uses the content
from ubuntu-app-platform, the QML module of the ContentHub will be
available, but this doesn't guarantee that the CH service is running.
It might not be installed (for example, in another distro), not
running or maybe not reachable due to confinement.
I propose adding a "valid" property to the ContentHub singleton which
would tell whether the service is available.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+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 1676893] Re: Inform client if ContentHub service is not available
** Changed in: content-hub (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1676893 Title: Inform client if ContentHub service is not available Status in content-hub package in Ubuntu: New Bug description: An app using the Content Hub QML API might have the need to know whether service is actually available, in order to fall back to other means if it isn't. This is especially relevant for snaps: if the snap uses the content from ubuntu-app-platform, the QML module of the ContentHub will be available, but this doesn't guarantee that the CH service is running. It might not be installed (for example, in another distro), not running or maybe not reachable due to confinement. I propose adding a "valid" property to the ContentHub singleton which would tell whether the service is available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+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 1676893] Re: Inform client if ContentHub service is not available
** Changed in: content-hub (Ubuntu) Status: New => In Progress ** Changed in: content-hub (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1676893 Title: Inform client if ContentHub service is not available Status in content-hub package in Ubuntu: In Progress Bug description: An app using the Content Hub QML API might have the need to know whether service is actually available, in order to fall back to other means if it isn't. This is especially relevant for snaps: if the snap uses the content from ubuntu-app-platform, the QML module of the ContentHub will be available, but this doesn't guarantee that the CH service is running. It might not be installed (for example, in another distro), not running or maybe not reachable due to confinement. I propose adding a "valid" property to the ContentHub singleton which would tell whether the service is available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+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 1647834] [NEW] package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
Public bug reported: Manually removed files installed by previous package (15.04) left by aborted update (screen flashing from terminal to graphics ... ?). Rebooted, removed and reinstalled package: seems still problems. Removed package and rebooted: now fine, stop problem (or almost, no more messages about problems). Thanks to all, seem fixed. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Dec 6 11:07:49 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-01-10 (330 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: android-tools (Ubuntu) Importance: Undecided Assignee: Alberto Fusari (albertofusari73) Status: Fix Committed ** Tags: amd64 apport-package yakkety ** Changed in: android-tools (Ubuntu) Status: New => Fix Committed ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) => Alberto Fusari (albertofusari73) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1647834 Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 Status in android-tools package in Ubuntu: Fix Committed Bug description: Manually removed files installed by previous package (15.04) left by aborted update (screen flashing from terminal to graphics ... ?). Rebooted, removed and reinstalled package: seems still problems. Removed package and rebooted: now fine, stop problem (or almost, no more messages about problems). Thanks to all, seem fixed. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Dec 6 11:07:49 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 5 InstallationDate: Installed on 2016-01-10 (330 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1647834/+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 1647946] Re: Latest online accounts breaks unity-scopes-api
This is certainly due to some of the latest changes in online-accounts-api, but the test is wrong and it was working by accident. :-) The test creates an account for the "TestProvider" provider, but there is no TestProvider.provider file in the data/ directory of the tests. Just create such a file: Test provider testprovider ** Changed in: account-plugins Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1647946 Title: Latest online accounts breaks unity-scopes-api Status in Online Accounts: Account plugins: Invalid Status in unity-scopes-api package in Ubuntu: New Bug description: We just got this test failure on zesty: https://jenkins.canonical.com/unity- api-1/job/build-2-binpkg/arch=armhf,release=zesty/1022/consoleFull Search for "OnlineAccountClientTest.service_update_callback" In the log, we see "GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.MethodNotKnown: Authentication method is not known." This test has worked for well over a year and has never failed. Something must have changed outside scopes-api. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1647946/+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 1647603] Re: Add option for semi-transparent keyboard
If this gets implemented, then we could maybe have a transparent keyboard on the lock screen. People have been complaining about it: https://lists.launchpad.net/ubuntu-phone/msg22972.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1647603 Title: Add option for semi-transparent keyboard Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: OK, this is not a real bug, rather a characteristic. But one that can be easily solved, thus I'd like to make a feature request. Especially in the landscape mode, the onscreen keyboard takes up a large portion of the screen. Potentially it can overlap the window where the text is being typed into, so you cannot see what you're typing. This could be VERY easily solved by letting users to set transparency level for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 70% opacity on Ubuntu Touch phone, in landscape windowed mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1647603/+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 1594944] Re: Setup.exec() for existing account type results in blank full screen window
** Changed in: webapps-sprint Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1594944 Title: Setup.exec() for existing account type results in blank full screen window Status in Canonical System Image: Fix Released Status in webapps-sprint: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: If an account already exists, calling Setup.exec() again results in a blank window being overlaid on top of the application which made the request. There is no way to close this window. This API is what the online accounts integration in the scopes API relies upon, to allow logging in to accounts, and so we have come to rely upon this API as well in multiple places, as a means to log into the Ubuntu One account, when it is necessary to do so. However, due to this issue, the only way to reliably present a login window at an appropriate time, is to delete the account when it appears to have been invalidated by the server, and to then present the login window to create a new account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594944/+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 1608246] Re: Does not work button on the headphones to answer call's [Meizu PRO 5]
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1608246 Title: Does not work button on the headphones to answer call's [Meizu PRO 5] Status in Canonical System Image: New Status in dialer-app package in Ubuntu: Confirmed Bug description: Call answer with headset button does not work. Checked on Meizu PRO 5 with OTA-12 and with several wired headset. PS: Works fine on BQ Aquaris e4.5 Ubuntu edition. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1608246/+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 1608246] Re: Does not work button on the headphones to answer call's [Meizu PRO 5]
Here's what I see in the syslog when the button is pressed: Dec 12 17:32:51 ubuntu-phablet repowerd[2423]: DefaultStateMachine: handle_user_activity_changing_power_state Dec 12 17:32:51 ubuntu-phablet kernel: [30240.423231] [0: irq/6-arizona: 1238] [c0] arizona 1-001a: MICDET: 0x7 Dec 12 17:32:51 ubuntu-phablet kernel: [30240.423357] [0: irq/6-arizona: 1238] [c0] arizona 1-001a: Mic button detected Dec 12 17:32:51 ubuntu-phablet kernel: [30240.423416] [0: irq/6-arizona: 1238] [c0] arizona 1-001a: Mic button detected: lvl=1, ffs(lvl)-1=0 Dec 12 17:32:51 ubuntu-phablet kernel: [30240.423488] [0: irq/6-arizona: 1238] [c0] arizona 1-001a: Mic button detected: key=226 Dec 12 17:32:51 ubuntu-phablet repowerd[2423]: DefaultStateMachine: handle_user_activity_extending_power_state Dec 12 17:32:51 ubuntu-phablet kernel: [30240.604666] [0: irq/6-arizona: 1238] [c0] arizona 1-001a: MICDET: 0x403 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1608246 Title: Does not work button on the headphones to answer call's [Meizu PRO 5] Status in Canonical System Image: New Status in dialer-app package in Ubuntu: Confirmed Bug description: Call answer with headset button does not work. Checked on Meizu PRO 5 with OTA-12 and with several wired headset. PS: Works fine on BQ Aquaris e4.5 Ubuntu edition. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1608246/+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 1649523] [NEW] libunity-protocol-private.so cannot be found
Public bug reported: If your snap links (directly or indirectly, for instance via the Ubuntu.UnityWebApps QML module) to the libunity.so library, running it will fail with the following error: "file:///snap/amazon-webapp/x1/share/webbrowser-app/webcontainer /webapp-container.qml:21 plugin cannot be loaded for module \"Ubuntu.UnityWebApps\": Cannot load library /snap/amazon-webapp/x1 /ubuntu-app-platform/usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/UnityWebApps/libUnityWebApps.so: (libunity-protocol- private.so.0: cannot open shared object file: No such file or directory)\n" libunity-protocol-private.so *is* present in the ubuntu-app-platform snap, but it's in a subdirectory which is not in the library path: /usr/lib/x86_64-linux-gnu/libunity/libunity-protocol-private.so.0 (not the "libunity" subdirectory). It looks like (info obtained with "objdump -a -x") libunity.so has this RPATH: RPATH/usr/lib/x86_64-linux-gnu/libunity I'll try to see if using $ORIGIN in libunity helps; if not, we might have to play with LD_LIBRARY_PATH in the ubuntu-app-platform snap. ** Affects: ubuntu-app-platform Importance: Undecided Status: New ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Also affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1649523 Title: libunity-protocol-private.so cannot be found Status in Ubuntu App Platform: New Status in libunity package in Ubuntu: New Bug description: If your snap links (directly or indirectly, for instance via the Ubuntu.UnityWebApps QML module) to the libunity.so library, running it will fail with the following error: "file:///snap/amazon-webapp/x1/share/webbrowser-app/webcontainer /webapp-container.qml:21 plugin cannot be loaded for module \"Ubuntu.UnityWebApps\": Cannot load library /snap/amazon-webapp/x1 /ubuntu-app-platform/usr/lib/x86_64-linux- gnu/qt5/qml/Ubuntu/UnityWebApps/libUnityWebApps.so: (libunity- protocol-private.so.0: cannot open shared object file: No such file or directory)\n" libunity-protocol-private.so *is* present in the ubuntu-app-platform snap, but it's in a subdirectory which is not in the library path: /usr/lib/x86_64-linux-gnu/libunity/libunity-protocol-private.so.0 (not the "libunity" subdirectory). It looks like (info obtained with "objdump -a -x") libunity.so has this RPATH: RPATH/usr/lib/x86_64-linux-gnu/libunity I'll try to see if using $ORIGIN in libunity helps; if not, we might have to play with LD_LIBRARY_PATH in the ubuntu-app-platform snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-platform/+bug/1649523/+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 1649419] Re: unable to install apps from ubuntu store
Hi Daniel, I need to ask you some more information, in order to understand what's going on: 1) Can you please take a screenshot (press both volume UP and volume DOWN buttons at the same time) of the page asking you to confirm access to your account, and attach it to this bug report? 2) Please go to System Settings -> Online Accounts; do you have an UbuntuOne account there? 3) If not, please try creating the account from there. Then head back to the ubuntu store, and try installing an app from there. Does it succeed? And if you go back to the System Settings, is the UbuntuOne account still there? ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1649419 Title: unable to install apps from ubuntu store Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ E5. I do click on install, then I am asked to confirm access to my UbuntuOne account and thats it, back to the install page. I tried several apps with the same negative result. I do have over 4GB free space, so that should not cause trouble. The phone has been rebooted a couple of times i.e. to upgrade to OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+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 1649419] Re: unable to install apps from ubuntu store
Thanks Daniel! This indeed looks like a bug on our side. But I'm surprised that no one else has reported it, so I suspect that somehow your device got itself into a wrong state. I need to ask you one more information, and this might be a bit harder to collect. I'd like you to use "phablet-shell" from a connected desktop (please tell me, if you are not familiar with this tool) and run this command: OAU_LOGGING_LEVEL=2 OAU_DAEMON_TIMEOUT= online-accounts-service > oa.log Then please try to reproduce the bug again (just once), and finally attach the "oa.log" file to this bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1649419 Title: unable to install apps from ubuntu store Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ E5. I do click on install, then I am asked to confirm access to my UbuntuOne account and thats it, back to the install page. I tried several apps with the same negative result. I do have over 4GB free space, so that should not cause trouble. The phone has been rebooted a couple of times i.e. to upgrade to OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+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 1650007] Re: Consider changing Google API key
The OAuth keys for Google are defined in EDS itself (src/modules/ubuntu- online-accounts/google-*.service.in.in). They were registered by me, but I gave access to them to the EDS developers themselves (though I suspect that it was still at the time when Matthew Barnes was the lead developer - I'm not sure Milan has access). Anyway, I just checked the stats and I've verified that we are well below the maximum quota, with no errors reported, for the last 30 days. So I believe that we are fine there, and that we don't need to act on this. I'll leave this bug in incomplete state; if new data emerges that convinces us that we indeed have a problem, we'll address it. ** Package changed: account-plugins (Ubuntu) => evolution-data-server (Ubuntu) ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1650007 Title: Consider changing Google API key Status in evolution-data-server package in Ubuntu: Incomplete Bug description: evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before 3.22.2 had bugs that caused users using Google services to experience daily limit timeouts and authentication errors. Unfortunately, users using older versions are causing those problems for everyone that still uses the affected API key. Therefore GNOME is updating the API key used by GNOME Online Accounts. For more info, see LP: #1649995 and https://bugzilla.gnome.org/774202 - I don't know yet if e-d-s before 3.20 is also affected. I asked but you're welcome to ask the Evolution devs yourself. https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61 - Upstream evolution has two ways to configure a Google account: GNOME Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd way. (I think e-d-s will need to switch to a new Google API key too but that hasn't happened yet.) - For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP: #1639926) to be pushed to yakkety-updates and fully 100% phased before publishing the new key. - Therefore, assuming Ubuntu Online Accounts is affected, I suggest you consider changing the Google API key used in Ubuntu 16.10 and above. Once we figure out if e-d-s needs to be updated for 16.04 (and possibly earlier releases), I believe we'll need to update the key there too. - On the other hand, since we control Ubuntu updates (unlike GNOME which has not control over who uses what version of their stuff) maybe we don't need to change the key after all. Maybe we just need to push the e-d-s SRUs as security updates to ensure people use the fixed versions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1650007/+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 1650555] [NEW] nsswitch.conf configuration doesn't work with mdns hosts
Public bug reported: On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts doesn't work anymore (it used to in xenial) I can resolve names with avahi-resolve but ssh,ping,etc. fail to resolve. After some digging I found out that what's causing it is the "resolve" option in /etc/nsswitch.conf: hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns Changing it to hosts: files mdns4_minimal [NOTFOUND=return] dns (as it was on xenial) makes mDNS work again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Dec 16 15:16:38 2016 InstallationDate: Installed on 2016-10-22 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650555 Title: nsswitch.conf configuration doesn't work with mdns hosts Status in systemd package in Ubuntu: New Bug description: On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts doesn't work anymore (it used to in xenial) I can resolve names with avahi-resolve but ssh,ping,etc. fail to resolve. After some digging I found out that what's causing it is the "resolve" option in /etc/nsswitch.conf: hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns Changing it to hosts: files mdns4_minimal [NOTFOUND=return] dns (as it was on xenial) makes mDNS work again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Dec 16 15:16:38 2016 InstallationDate: Installed on 2016-10-22 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650555/+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 1649419] Re: unable to install apps from ubuntu store
Hi Daniel, thanks for the logs, it's exactly what I needed. I now need some more info, let's hope it's the last bit. >From a phablet-shell console, can you please run these two commands: account-console list Then look at the number next to the ubuntuone account, and type account-console show and attach the output to this bug. Hopefully I won't bother you with more requests. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1649419 Title: unable to install apps from ubuntu store Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ E5. I do click on install, then I am asked to confirm access to my UbuntuOne account and thats it, back to the install page. I tried several apps with the same negative result. I do have over 4GB free space, so that should not cause trouble. The phone has been rebooted a couple of times i.e. to upgrade to OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+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 1649419] Re: unable to install apps from ubuntu store
Thanks Daniel! For some reason the "ubuntuone" service is disabled in the account. This is very weird, it should never happen. Did you ever try installing some siloes from bileto.ubuntu.com or made your system writable and installed something with apt or dpkg on the phone? If you have no idea what I'm talking about, nevermind, then you probably didn't do any of that :-) Please try deleting your account, and let me know if the bug reappears. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1649419 Title: unable to install apps from ubuntu store Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ E5. I do click on install, then I am asked to confirm access to my UbuntuOne account and thats it, back to the install page. I tried several apps with the same negative result. I do have over 4GB free space, so that should not cause trouble. The phone has been rebooted a couple of times i.e. to upgrade to OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+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 1649419] Re: unable to install apps from ubuntu store
Thanks Daniel for explaining the situation! One last question, after which we can then close this bug: can you still see the "com.canonical.payui_payui" application under the ubuntuone account? It should not be there, and indeed I don't see it in my phone or in my tablet. Please report the missing apps as a separate bug -- I recommend filing it here: https://bugs.launchpad.net/canonical-devices-system-image/+filebug and maybe also add unity8-dash as an affected component; it might not be the correct one, but the guys should know where to move it to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1649419 Title: unable to install apps from ubuntu store Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ E5. I do click on install, then I am asked to confirm access to my UbuntuOne account and thats it, back to the install page. I tried several apps with the same negative result. I do have over 4GB free space, so that should not cause trouble. The phone has been rebooted a couple of times i.e. to upgrade to OTA 14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+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 1651938] Re: Owncloud Account doesn't work with Nextcloud 11
Hi Slash, thanks for reporting this bug. As I understand from your logs,
it's not even possible to create a nextcloud account; can you please
confirm this?
Anyway, this looks like a bug in the Nextcloud server implementation:
CSRF is not something that normally affects REST APIs, which are
stateless by definition. When registering the account, we are passing
username and password with every function call.
Please file a bug against Nextcloud, and write here the link to the
report, so that I can comment in case they ask for more information.
For the record, the API we are using when verifying whether the account is
valid is /ocs/v1.php/person/check, which is documented here:
https://www.freedesktop.org/wiki/Specifications/open-collaboration-services/#index4h4
I think they forced the CSRF check on all API, including the public REST
APIs, by mistake.
** Changed in: account-plugins (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1651938
Title:
Owncloud Account doesn't work with Nextcloud 11
Status in account-plugins package in Ubuntu:
Incomplete
Bug description:
Dear,
Since my nextcloud server update i cannot connect anymore to my calendar.
My contacts with syncevolution no problem.
I think i found why, nextcloud reduce the CRSF vulnerability
phablet@ubuntu-phablet:~$ export OAU_LOGGING_LEVEL=2
phablet@ubuntu-phablet:~$ export OAU_DAEMON_TIMEOUT=
phablet@ubuntu-phablet:~$ online-accounts-service
service.cpp 42 requestAccess Got request: QMap(("application",
QVariant(QString, "system-settings") ) ( "pid" , QVariant(uint, 26947) ) (
"provider" , QVariant(QString, "owncloud") ) ( "windowId" , QVariant(uint,
26947) ) )
App ID: "unconfined"
request-manager.cpp 113 runQueue Head: OnlineAccountsUi::Request(0x1d829d8)
mir-helper.cpp 151 session_event_callback Prompt Session state updated to 1
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
ui-server.cpp 103 onDataReady QMap(("code", QVariant(QString, "process") ) (
"data" , QVariant(QVariantMap, QMap(("application", QVariant(QString,
"system-settings") ) ( "pid" , QVariant(uint, 26947) ) ( "provider" ,
QVariant(QString, "owncloud") ) ( "windowId" , QVariant(uint, 26947) ) ) ) ) (
"id" , QVariant(int, 0) ) ( "interface" , QVariant(QString,
"com.ubuntu.OnlineAccountsUi") ) ( "profile" , QVariant(QString, "unconfined")
) )
qml: Page_QMLTYPE_24(0x1973a38)"ownCloud": In Ubuntu.Components 1.3, the use
of Page.title, Page.flickable and Page.head is deprecated. Use Page.header and
the PageHeader component instead.
file:///home/phablet/.local/share/accounts/qml-plugins/owncloud/Main.qml:
File not found
virtual void OnlineAccountsPlugin::Plugin::registerTypes(const char*)
Ubuntu.OnlineAccounts.Plugin
request.cpp 115 setWindow Requesting window reparenting
QWindow::fromWinId(): platform plugin does not support foreign windows.
APP_ID isn't set, the handler ignored
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
qml: Trying host https://server as login:password
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.qml:4:1: QML Main:
Binding loop detected for property "contentHeight"
file:///usr/share/accounts/qml-plugins/owncloud/Main.q
[Touch-packages] [Bug 1652364] Re: package account-plugin-facebook (not installed) failed to install/upgrade: Versuch, »/etc/signon-ui/webkit-options.d/www.facebook.com.conf« zu überschreiben, welches
*** This bug is a duplicate of bug 1565772 *** https://bugs.launchpad.net/bugs/1565772 ** This bug has been marked a duplicate of bug 1565772 [SRU] Allow plugins to decide which username to set on new accounts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1652364 Title: package account-plugin-facebook (not installed) failed to install/upgrade: Versuch, »/etc/signon-ui/webkit- options.d/www.facebook.com.conf« zu überschreiben, welches auch in Paket kaccounts-providers 4:15.12.3-0ubuntu1 ist Status in account-plugins package in Ubuntu: New Bug description: package account-plugin-facebook (not installed) failed to install/upgrade: Versuch, »/etc/signon-ui/webkit- options.d/www.facebook.com.conf« zu überschreiben, welches auch in Paket kaccounts-providers 4:15.12.3-0ubuntu1 ist ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-facebook (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 23 19:16:49 2016 ErrorMessage: Versuch, »/etc/signon-ui/webkit-options.d/www.facebook.com.conf« zu überschreiben, welches auch in Paket kaccounts-providers 4:15.12.3-0ubuntu1 ist InstallationDate: Installed on 2014-12-31 (723 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: account-plugins Title: package account-plugin-facebook (not installed) failed to install/upgrade: Versuch, »/etc/signon-ui/webkit-options.d/www.facebook.com.conf« zu überschreiben, welches auch in Paket kaccounts-providers 4:15.12.3-0ubuntu1 ist UpgradeStatus: Upgraded to xenial on 2016-04-26 (240 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1652364/+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 1656310] Re: google + is not accessible anymore via the browser app
Might be the same as bug 1644585. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1656310 Title: google + is not accessible anymore via the browser app Status in Canonical System Image: Confirmed Status in webbrowser-app package in Ubuntu: In Progress Bug description: Something must have changed in google it used to work flawlessly. Now i have a message saying that this browser is not supported and i cannot see any public google plus sites mako rc proposed vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts
Can some admin please remove the packages from -proposed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1565772 Title: [SRU] Allow plugins to decide which username to set on new accounts Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Released Status in Online Accounts: GNOME Control Center: Fix Released Status in webapps-sprint: Fix Committed Status in account-plugins package in Ubuntu: Fix Released Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in account-plugins source package in Xenial: Fix Committed Status in gnome-control-center-signon source package in Xenial: Fix Committed Status in account-plugins source package in Yakkety: Fix Released Status in gnome-control-center-signon source package in Yakkety: Fix Released Bug description: This bug is related to bug 1547647, even though it makes sense in any case. Currently, the ApOAuthPlugin class in libaccount-plugin gets the username from the SignonIdentity, which in turn gets it from signon- ui, which in the current WebKit1 implementation gets it from the DOM of the login webpage. This is a hack, it's fragile, not trivial to port to the Oxide web engine, and possibly against some providers' guidelines. We should retrieve the username using some REST API provided by the service, and in order to do so we need to extend libaccounts-plugin with some hooks which subclasses can use to get the username. Once we fix this we can also get rid of the files /etc/signon-ui /webkit-options.d/, which are conflicting with those installed by the KDE account plugins packages. SRU information === [Impact] The same file /etc/signon-ui/webkit- options.d/www.facebook.com.conf is installed by the account-plugin- facebook package (used by Unity) and by kaccount-providers (used by KDE). See this bug's duplicates to see actual bug reports. [Test Case] Install both account-plugin-facebook and kaccount- providers and you'll get the conflict. [Regression Potential] Users running KDE will be completely unaffected by this. Users running Unity might see a change when creating accounts in System Settings->Online Accounts: with this bugfix, the account's display name is obtained by making a REST API call to the remote service, rather than by scrapping the DOM of the server webpages (which is a hack, and prone to errors if the providers' webpage changes). The new way of retrieving the username is the proper one, and it's been tested to work reliably. In any case, the worst thing that might happen is that accounts get created with an empty display name, which is mostly an aesthetic problem (the display name is used only for UI purposes). To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1656806] Re: fail to invoke online account creationg from messaging-app
OA is assuming that if a client has security label other than "unconfined", then it's a click and its .application file is only looked for in ~/.local/share/accounts. We should look in all XDG data dirs. ** Project changed: online-accounts-api => ubuntu-system-settings- online-accounts ** Changed in: ubuntu-system-settings-online-accounts Importance: Undecided => High ** Changed in: ubuntu-system-settings-online-accounts Status: New => In Progress ** Changed in: ubuntu-system-settings-online-accounts Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1656806 Title: fail to invoke online account creationg from messaging-app Status in Online Accounts setup for Ubuntu Touch: In Progress Status in messaging-app package in Ubuntu: New Bug description: Using online account API from messaging-app to create a new account fail with the message "invalid application file" . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1656806/+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 1656806] Re: fail to invoke online account creationg from messaging-app
** Also affects: webapps-sprint Importance: Undecided Status: New ** Changed in: webapps-sprint Milestone: None => sprint-29 ** Changed in: webapps-sprint Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: webapps-sprint Status: New => In Progress ** Changed in: webapps-sprint Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1656806 Title: fail to invoke online account creationg from messaging-app Status in Online Accounts setup for Ubuntu Touch: In Progress Status in webapps-sprint: In Progress Status in messaging-app package in Ubuntu: New Bug description: Using online account API from messaging-app to create a new account fail with the message "invalid application file" . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1656806/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Hi Pablo, please file a new bug, providing a screenshot of the authentication dialog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu: Fix Released Status in account-plugins source package in Quantal: Fix Released Status in signon-plugin-oauth2 source package in Quantal: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Fix Released Status in signon-plugin-oauth2 source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1641328] Re: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing
** Tags added: yakkety -- 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/1641328 Title: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing Status in nss-mdns package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: (See also libnss-resolve:amd64 231-9ubuntu1 amd64nss module to resolve names via systemd-resolved) # fresh install of yakkety mtearle@liberation:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety # package details mtearle@liberation:~$ apt-cache policy libnss-resolve libnss-resolve: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages mtearle@liberation:~$ apt-cache policy systemd systemd: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages # attempt to ping VM elsewhere on network with mDNS hostname mtearle@liberation:/etc$ ping bazzavan.local ping: bazzavan.local: Name or service not known # can find both ipv4 and ipv6 addresses for the host mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local bazzavan.localfe80::a00:27ff:fea5:3f51 mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local bazzavan.local172.16.44.48 # can ping it mtearle@liberation:/etc$ ping -c 1 172.16.44.48 PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms --- 172.16.44.48 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms # original ordering mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns # go away and edit /etc/nsswitch.conf # change ordering of resolve and mdns4_minimal mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns # check mdns lookups now work, and it now pings mtearle@liberation:/etc$ ping -c 1 bazzavan.local PING bazzavan.local (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms --- bazzavan.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms # check libnss-resolve is still doing its thing mtearle@liberation:/etc$ ping -c 1 localhost.localdomain PING localhost.localdomain(localhost (::1%1)) 56 data bytes 64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms --- localhost.localdomain ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1641328/+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 1659319] Re: Changing language mid-word results in duplicated words
This seems to happen, more generally, when you edit any word. For example: - type "prin" - select "prince" from the autocompletion - type "s" - select "princes" from the autocompletion and you'll get "princeprinces". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1659319 Title: Changing language mid-word results in duplicated words Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Steps: * switch to En layout * type "bar" * change to Pl layout * type "dz" * select the auto-completed "bardzo" Expected: * "bardzo" is put into the input field Current: * "barbardzo" is put into the input field ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-keyboard 0.100+17.04.20170110-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2 Uname: Linux 4.9.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 25 15:45:00 2017 InstallationDate: Installed on 2016-05-06 (263 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: ubuntu-keyboard UpgradeStatus: Upgraded to zesty on 2016-11-22 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1659319/+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 1641328] Re: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing
Any update on this bug? -- 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/1641328 Title: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing Status in nss-mdns package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: (See also libnss-resolve:amd64 231-9ubuntu1 amd64nss module to resolve names via systemd-resolved) # fresh install of yakkety mtearle@liberation:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety # package details mtearle@liberation:~$ apt-cache policy libnss-resolve libnss-resolve: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages mtearle@liberation:~$ apt-cache policy systemd systemd: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages # attempt to ping VM elsewhere on network with mDNS hostname mtearle@liberation:/etc$ ping bazzavan.local ping: bazzavan.local: Name or service not known # can find both ipv4 and ipv6 addresses for the host mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local bazzavan.localfe80::a00:27ff:fea5:3f51 mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local bazzavan.local172.16.44.48 # can ping it mtearle@liberation:/etc$ ping -c 1 172.16.44.48 PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms --- 172.16.44.48 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms # original ordering mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns # go away and edit /etc/nsswitch.conf # change ordering of resolve and mdns4_minimal mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns # check mdns lookups now work, and it now pings mtearle@liberation:/etc$ ping -c 1 bazzavan.local PING bazzavan.local (172.16.44.48) 56(84) bytes of data. 64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms --- bazzavan.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms # check libnss-resolve is still doing its thing mtearle@liberation:/etc$ ping -c 1 localhost.localdomain PING localhost.localdomain(localhost (::1%1)) 56 data bytes 64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms --- localhost.localdomain ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-mdns/+bug/1641328/+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 1662355] Re: Signon shows up as Safari
We are not trying to pretend that we are Safari :-) But it looks like for some reason our User-Agent string is interpreted by Google as being from Safari. This is actually a fault in Google's servers, but I'll keep this bug open because we might want to find another User-Agent string as a workaround. ** Changed in: signon-ui (Ubuntu) Status: New => Confirmed ** Changed in: signon-ui (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1662355 Title: Signon shows up as Safari Status in signon-ui package in Ubuntu: Confirmed Bug description: Signon UI popped up and asked me to log into Google. After logging in, Google immediately sent me a message asking whether I logged in as Safari, with my public IP (so I have no reason to think it was anyone but me). Is signon-ui spoofing as safari? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 6 22:41:44 2017 InstallationDate: Installed on 2012-09-26 (1594 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2017-01-23 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1662355/+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 1662645] Re: owncloud account does NOT support httpS
** Package changed: ubuntu-system-settings (Ubuntu) => account-plugins (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1662645 Title: owncloud account does NOT support httpS Status in account-plugins package in Ubuntu: New Bug description: Ubuntu 15.04 OTA14 Clean system in the account page there is Ubuntu One and owncloud. When I try to set the URL of my owncloud server httpS://owncloud/owncloud, I get an "invalid URL error" It works fine with http://owncloud but this is not very secure, and this disable access to my owncloud from outside home : firewall allows only httpS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1662645/+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 1662645] Re: owncloud account does NOT support httpS
My owncloud instance is https only, and I could create the owncloud account with no issues. Can you please open a terminal (or SSH connection) in the device and run the following command: OAU_LOGGING_LEVEL=2 OAU_DAEMON_TIMEOUT= online-accounts-service > oa.log Then try creating the account again, and finally type a Ctrl+C on the terminal and attach the oa.log file to this bug (if there are sensitive informations you'd like to hide, replace them with "XXX"). ** Changed in: account-plugins (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1662645 Title: owncloud account does NOT support httpS Status in account-plugins package in Ubuntu: Incomplete Bug description: Ubuntu 15.04 OTA14 Clean system in the account page there is Ubuntu One and owncloud. When I try to set the URL of my owncloud server httpS://owncloud/owncloud, I get an "invalid URL error" It works fine with http://owncloud but this is not very secure, and this disable access to my owncloud from outside home : firewall allows only httpS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1662645/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Yes, please: the original bug got fixed, and the prompt you see might have a totally different cause. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu: Fix Released Status in account-plugins source package in Quantal: Fix Released Status in signon-plugin-oauth2 source package in Quantal: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in evolution-data-server source package in Trusty: Fix Released Status in signon-plugin-oauth2 source package in Trusty: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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
