[Touch-packages] [Bug 1629370] Re: PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1
You can use my surname: Florent
And thanks again for you quick help!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1629370
Title:
PKINIT fails with PKCS#11 middlware that implements PKCS#1 V2.1
Status in krb5 package in Ubuntu:
Confirmed
Bug description:
Problem: can't do PK-INIT with a smartcard PKCS#11 middleware that
implements PKCS#1 v2.10
$ kinit -E name.surname@something@REALM
-> fails
Diagnostic using PKCS11-SPY from OpenSC:
16: C_Sign
2016-09-16 14:31:53.265
[in] hSession = 0x6bc3a70e
[in] pData[ulDataLen] 0931e898 / 33
30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3
0.0...+.
0010 5A 2B F8 78 C0 FD CD 87 EE 25 08 C2 DD AA 50 3D
Z+.x.%P=
0020 DC .
Returned: 32 CKR_DATA_INVALID
The signing algorithm is SHA1. However the Data Formatting is
incorrect:
30 1F 30 07 06 05 2B 0E 03 02 1A 04 14 17 07 D3 5A 2B F8 78 C0 FD CD
87 EE 25 08 C2 DD AA 50 3D DC
instead it should be:
30 21 30 09 06 05 2B 0E 03 02 1A 05 00 04 14 17 07 D3 5A 2B F8 78 C0 FD CD 87
EE 25 08 C2 DD AA 50 3D DC
See the PKCS#1 paper (page 43) https://tools.ietf.org/html/rfc3447
Extract:
"
1. For the six hash functions mentioned in Appendix B.1, the DER
encoding T of the DigestInfo value is equal to the following:
MD2: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 02 05 00 04
10 || H.
MD5: (0x)30 20 30 0c 06 08 2a 86 48 86 f7 0d 02 05 05 00 04
10 || H.
SHA-1: (0x)30 21 30 09 06 05 2b 0e 03 02 1a 05 00 04 14 || H.
"
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: krb5-pkinit 1.12+dfsg-2ubuntu5.2
Uname: Linux 3.13.0-68-generic x86_64
Architecture: amd64
Date: Fri Sep 30 12:49:09 CEST 2016
ProcEnviron:
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: krb5-pkinit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1629370/+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 1638432] Re: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured
*** This bug is a duplicate of bug 1635280 *** https://bugs.launchpad.net/bugs/1635280 ** This bug has been marked a duplicate of bug 1635280 [ BUG 541595 IS BACK ] package is already installed and configured -- 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/1638432 Title: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured Status in systemd package in Ubuntu: New Bug description: I dont know much about this issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu11 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 Date: Tue Nov 1 21:18:17 2016 DuplicateSignature: package:udev:229-4ubuntu11 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package udev is already installed and configured InstallationDate: Installed on 2016-10-07 (26 days ago) InstallationMedia: It MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2330 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.14 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd09/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096E13405E00050360180:rvnHewlett-Packard:rn2330:rvr99.14:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E13405E00050360180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638432/+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 1584894] Re: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU
** Summary changed: - unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU + unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU ** Changed in: mir Status: Confirmed => In Progress ** Changed in: mir Milestone: None => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584894 Title: unity-system-compositor (or any Mir server) crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter and QEMU Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Bug description: (separated from bug 1118903) unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter --- can not login to Unity8 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Mon May 23 19:20:43 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-05-19 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.5 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.68-1 version.lightdm: lightdm 1.19.0-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584894/+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 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
Only one file can be attached at once, so here is the second file (when audio works again). ** Attachment added: "debug_audio.log.3" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+attachment/4770948/+files/debug_audio.log.3 -- 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/1320020 Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I can get perfect sound through headphones, and the kernel recognizes the internal speaker, but nothing is ever played through it. I have personally tested a pair of earbuds to make sure that sound could play through the headphone port, and that isn't a problem. The sound driver just refuses to recognize the existence of the speaker, even though the kernel does. I wouldn't be surprised if the last upstream update had something to do with it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio CurrentDesktop: GNOME Date: Thu May 15 18:07:52 2014 InstallationDate: Installed on 2014-01-29 (106 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago) dmi.bios.date: 03/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0M7CYJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1470 dmi.product.version: A05123 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+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 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
I am encountering the same issue, Attached are 2 files from alsa- info.sh. I use Ubuntu 16.04 - Dell XPS-15, and I DO NOT dual boot windows. Summary: 1) Initially audio works fine. 2) Plug headphones in jack, Speaker audio stops and headphone works. 3) Unplug headphone, Speaker will not work 4) Plug headphone back in, it won't work either (at some times) 5) Unplug headphones. 6) Put laptop into sleep, Speaker audio will work again (Also at some times I had to repeat this step multiple times). debug_audio.log.1 - Is when it is not working debug_audio.log.3 - When it started to work after sleeping and waking up my laptop ** Attachment added: "debug_audio.log.1" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+attachment/4770947/+files/debug_audio.log.1 -- 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/1320020 Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I can get perfect sound through headphones, and the kernel recognizes the internal speaker, but nothing is ever played through it. I have personally tested a pair of earbuds to make sure that sound could play through the headphone port, and that isn't a problem. The sound driver just refuses to recognize the existence of the speaker, even though the kernel does. I wouldn't be surprised if the last upstream update had something to do with it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio CurrentDesktop: GNOME Date: Thu May 15 18:07:52 2014 InstallationDate: Installed on 2014-01-29 (106 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago) dmi.bios.date: 03/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0M7CYJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1470 dmi.product.version: A05123 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+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 1637037] Re: Printer stops mid-job; thereafter, USB mouse fails
*** This bug is a duplicate of bug 1630063 *** https://bugs.launchpad.net/bugs/1630063 ** This bug has been marked a duplicate of bug 1630063 specific USB devices disconnect and don't reconnect -- 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/1637037 Title: Printer stops mid-job; thereafter, USB mouse fails Status in cups package in Ubuntu: New Bug description: I am not sure, but I believe I have not printed anything since my install of Lubuntuy 16.10 last week. I printed something from LibreOffice Calc, and it got only partway, and the printer stopped printing. I then noticed that the mouse (USB) had stopped working - I thought the batteries had co-incidentally failed, but fresh batteries accomplished nothing. I had to shut down. The next time, feeling that the print function of Calc was faulty, I exported the file as .pdf, and printed from Document Viewer (Evince). It got just about as far, and stopped, and the mouse failed again. The next time, I was printing something from Firefox, and it got most of the way through that, but it stopped, and the mouse failed again. By now, I had "installed" and activated PointerKeys, and with it, I was (slowly and painfully) able to have the terminal do lsusb and cut-n-paste the output to leafpad and save. Some website suggested one could "reboot" the USB system, but I apparently failed to understand or apply the knowledge to success (or the procedure did not somehow apply to my current OS). Rebooting sometimes (always?) does NOT fix the problem - Shutdown so far has. When things are good, there are a lot more items in lsusb than when the mouse was not working. When the mouse did not work: scott@scott-ASUS-M2N68-AM-PLUS:~$ lsusb Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub When the mouse works: scott@scott-ASUS-M2N68-AM-PLUS:~$ lsusb Bus 001 Device 006: ID 7392:7622 Edimax Technology Co., Ltd Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0a12:1004 Cambridge Silicon Radio, Ltd Bus 002 Device 003: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver Bus 002 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 002 Device 002: ID 0a05:7211 Unknown Manufacturer hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Syslog shows some stuff that may show the problem happening: Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2798.923885] usb 2-1.4: new full-speed USB device number 8 using ohci-pci Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064011] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=5511 Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064014] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064016] usb 2-1.4: Product: Deskjet F300 series Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064017] usb 2-1.4: Manufacturer: HP Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.064018] usb 2-1.4: SerialNumber: CN647B623804KH Oct 26 16:55:32 scott-ASUS-M2N68-AM-PLUS root: loading HP Device 002 008 Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: [2039]: error: Failed to create /root/.hplip Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: io/hpmud/musb.c 2183: [2039] hpmud_make_usb_uri() bus=002 dev=008 Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS /hp-config_usb_printer: io/hpmud/musb.c 2281: hpmud_make_usb_uri() uri=hp:/usb/Deskjet_F300_series?serial=CN647B623804KH bytes_read=49 Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.793120] usblp 2-1.4:1.1: usblp2: USB Bidirectional printer dev 8 if 1 alt 0 proto 2 vid 0x03F0 pid 0x5511 Oct 26 16:55:33 scott-ASUS-M2N68-AM-PLUS kernel: [ 2799.793150] usbcore: registered new interface driver usblp Oct 26 16:57:53 scott-ASUS-M2N68-AM-PLUS hpcups[2108]: prnt/hpcups/Lidil.cpp 586: CupeInteger1 = [3] Oct 26 16:57:53 scott-ASUS-M2N68-AM-PLUS hpcups[2108]: prnt/hpcups/Lidil.cpp 587: CupeInteger2 = [1] Oct 26 16:57:53 scott-ASUS-M2N68-AM-PLUS hpcups[2108]: prnt/hpcups/Lidil.cpp 588: PrintMode Index = [6] Oct 26 16:57:53 scott-ASUS-M2N68-AM-PLUS hpcups[2108]: prnt/hpcups/Lidil.cpp 600: Print Mode = [PlainNormalGrayK] Oct 26 16:57:53 scott-ASUS-M2N68-AM-PLUS hp[2109]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Oct 26 16
[Touch-packages] [Bug 1341890] Re: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
I have the same problem that has Tobias in my Asus X550L. The internal microphone only work when the boost is set to 0, but with a low volume and high noise. Here is the link for the information that I get with alsa-info.sh http://www.alsa-project.org/db/?f=37b426e58cd6c599e3cee05a22a928d5cd1c18d8 Regards. -- 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/1341890 Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341890/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Tags added: patch -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1618423] Re: Modesetting driver cannot handle different display resolutions for two monitors
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors Status in xorg package in Ubuntu: Expired Bug description: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of the desktop, except for the unity launcher and unity top bar. Anything that leaves the top quarter leaves trails and flickers awfully (see attached image, which shows everything except the flickering). I also tried it with the laptop on 2560x1440 (I had to add it manually because of a a separate bug where the modesetting driver limits the max vertical refresh frequency of default modelines to 60 Hz) and exactly the same thing happens (although the geometry isn't one quarter any more). It works fine with the intel driver, but not the modesetting driver, so it seems to be an xserver issue rather than a unity issue. It also works fine if I set both monitors to 1920x1080. The modesetting driver seems to struggle with setting resolutions. When I first log into the desktop, it takes a good 5 seconds longer than the intel driver to set up the screens, and for a while it looks like I have a 640x480 screen (judging by the huge mouse pointer I get). Given this bug and the vertical refresh bug, maybe yakkety shouldn't default to the modesetting driver? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 30 19:26:06 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-9136-generic, x86_64: installed bbswitch, 0.8, 4.7.2-040702-generic, x86_64: installed nvidia, 367-367.44, 4.4.0-9136-generic, x86_64: installed nvidia, 367-367.44, 4.7.2-040702-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.7.2-040702-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-07-24 (36 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1618423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages
[Touch-packages] [Bug 1609520] Re: Cannot login after logout
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1609520 Title: Cannot login after logout Status in xorg package in Ubuntu: Expired Bug description: If I logout and login again it doesn't work and brings me back to the login screen (lightdm). This is only the case if I use the nvidia graphics card of my laptop (via prime-select), using the intel card, I can logout and login again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 3 19:14:59 2016 InstallationDate: Installed on 2016-05-18 (76 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1609520/+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 1619320] Re: problems after 16 install
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1619320 Title: problems after 16 install Status in xorg package in Ubuntu: Expired Bug description: not sure im new to this ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Sep 1 07:03:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-95-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-34-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] Subsystem: IBM 82945G/GZ Integrated Graphics Controller [1014:030e] InstallationDate: Installed on 2016-07-31 (32 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=168e743a-3325-4e07-91fa-1664f7ecb3d1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2006 dmi.bios.vendor: IBM dmi.bios.version: 2EKT37AUS dmi.board.name: IBM dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn82121YU:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct3:cvr: dmi.product.name: 82121YU dmi.product.version: ThinkCentre M52 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 31 16:32:12 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9890 vendor HWP xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619320/+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 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev
This bug was fixed in the package lxc - 2.0.5-0ubuntu3 --- lxc (2.0.5-0ubuntu3) zesty; urgency=medium * Also skip lxc-test-ubuntu on zesty (LXC still doesn't support squashfs cloud images) -- Stéphane Graber Fri, 21 Oct 2016 22:40:14 -0400 ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1620313 Title: stop using hardening-wrapper, obsoleted by recent dpkg-dev Status in firefox package in Ubuntu: Fix Released Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in hardening-wrapper package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in pidgin package in Ubuntu: Fix Released Status in proftpd-dfsg package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in hardening-wrapper package in Debian: Fix Released Bug description: stop using hardening-wrapper, obsoleted by recent dpkg-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1620313/+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 1638447] [NEW] package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: Try installing neowim (https://github.com/neovim/neovim/wiki/Installing- Neovim) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dbus 1.10.6-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 10:41:59 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-06-07 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: dbus Title: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1638447 Title: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in dbus package in Ubuntu: New Bug description: Try installing neowim (https://github.com/neovim/neovim/wiki /Installing-Neovim) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dbus 1.10.6-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 10:41:59 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-06-07 (148 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: dbus Title: package dbus 1.10.6-1ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1638447/+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 1623666] Re: iOS10 will not connect to Ubuntu
Nikos, patch didn't work. I commented in https://gitlab.com/gnutls/gnutls/issues/145 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1638437] [NEW] package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: failure during update and seem to have led to a complete system crash before or was from after a complete system crash which also had failures during update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Wed Nov 2 03:11:24 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check xenial -- 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/1638437 Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: failure during update and seem to have led to a complete system crash before or was from after a complete system crash which also had failures during update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Wed Nov 2 03:11:24 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 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/1638437/+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 1638432] [NEW] package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured
Public bug reported: I dont know much about this issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu11 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 Date: Tue Nov 1 21:18:17 2016 DuplicateSignature: package:udev:229-4ubuntu11 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package udev is already installed and configured InstallationDate: Installed on 2016-10-07 (26 days ago) InstallationMedia: It MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2330 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.14 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd09/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096E13405E00050360180:rvnHewlett-Packard:rn2330:rvr99.14:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E13405E00050360180 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1638432 Title: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured Status in systemd package in Ubuntu: New Bug description: I dont know much about this issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu11 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 Date: Tue Nov 1 21:18:17 2016 DuplicateSignature: package:udev:229-4ubuntu11 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package udev is already installed and configured InstallationDate: Installed on 2016-10-07 (26 days ago) InstallationMedia: It MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package udev 229-4ubuntu11 failed to install/upgrade: package udev is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2330 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.14 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd09/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096E13405E00050360180:rvnHewlett-Packard:rn2330:rvr99.14:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E13405E00050360180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638432/+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 1285444] Re: Login Successful, Desktop Never Loads
I still have not run into this once since upgrading to 16.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
PS: Restarting network-manager an reconnecting to the VPN works around the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
I think I am observing a regression caused by this fix: after
disconnecting/reconnecting a VPN connection, DNS resolution is broken.
Here are the details:
- VPN is set up as OpenVPN with split-tunneling ("Use this connection
only for resources on its network" is checked). The VPN's DNS domain is
ozone.caligrafix.cl, and the DNS server is 192.168.0.2. The local (non-
VPN) DNS server is 192.168.50.2.
- Right after boot, and after connecting to the VPN for the first time,
I can ping a host on the VPN's network (ping
somehost.ozone.caligrafix.cl)
- If I disconnect and reconnect to the VPN, I cannot ping the same host
by name (I get Name or service not known). I can ping it by IP.
Strangely enough, dnsmask says it does use the VPN's resolver, as shown
by this syslog extract:
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: setting upstream servers from DBus
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.50.2#53(via
wlan0)
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for
domain ozone.caligrafix.cl
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for
domain 1.8.10.in-addr.arpa
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for
domain 0.168.192.in-addr.arpa
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: reading /etc/resolv.conf
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: using nameserver 127.0.1.1#53
^C
gpothier@tadzim3:~$ ping somehost.ozone.caligrafix.cl
ping: somehost.ozone.caligrafix.cl: Name or service not known
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1592721
Title:
Don't write search domains to resolv.conf in the case of split DNS
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Fix Released
Bug description:
[Impact]
All VPN users meaning to use split-tunnelling in a situation where leaking
DNS data to the internet about what might be behind their VPN is undesirable.
[Test case]
1) connect to VPN
2) Use dig to request a name that should be on the VPN
3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only
gone through the VPN nameservers (only its request number should have increased
by one)
4) Use dig to request a name off-VPN, such as google.com.
5) Verify (kill -USR1 again) that the request has caused the non-VPN
nameserver request number to increase, and that the VPN number has not
increased.
It is easier to verify this when there is as little traffic as
possible on the system, to avoid spurious DNS requests which would
make it harder to validate the counters.
[Regression potential]
This change modifies the way in which DNS nameservers and search domains are
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and
intended to be used to resolve all network requests (which is typically not the
case for split-tunnelling) or if the public network is intended to always
resolve all requests while the VPN still provides search domains, one might
observe incorrect behavior.
Possible failure cases would include failure to resolve names
correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
to the incorrect values (if the wrong nameserver is used).
---
Currently, NM will write all search domains to both any DNS-handling
plugins running, and also to resolv.conf / resolvconf; in all cases.
The issue is that doing so means that in the split-DNS case on VPNs,
you might get a negative response from all nameservers, then a new
request by glibc with the search tacked on, to nameservers again,
which might cause DNS requests for "private" resources (say, on the
VPN) to be sent to external, untrusted resolvers, or for DNS queries
not meant for VPN nameservers to be sent through the VPN anyway.
This is fixable in the case where we have a caching plugin running
(such as dnsmasq). dnsmasq will already know about the search domains
and use that to limit queries to the right nameservers when a VPN is
running. Writing search domains to resolv.conf is unnecessary in this
case.
We should still write search domains if no caching gets done, as we
then need to expect glibc to send requests as it otherwise would.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1638167] Re: Thin grey lines on a white background look inconsistent and provide poor contrast
I suspect we also have rendering bugs (textures not displayed as pixel aligned) in the browser which might make some icons appear more blurred than they should. Certainly that seems to be the issue in bug 1606489. So that part is less a design problem and more the implementation. -- 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/1638167 Title: Thin grey lines on a white background look inconsistent and provide poor contrast Status in Canonical System Image: New Status in Ubuntu UX: In Progress Status in webbrowser-app package in Ubuntu: Incomplete Bug description: The top area of the browser window is really just a series thin grey lines on a white background. This is poor design for a few reasons: 1. Grey and white don't contrast very well, especially thin strips of grey on white. 2. The grey outlines and symbols are inconsistent in thickness and colour: 2.1. The X icon is thinner than the + icon beside it, which is a different consistency again to the < button below it. 2.2. The rounded grey outline around the address is slighly thicker (blurred?) compared to the grey outline delineating the tabs. 3. Those vision impaired will have a very hard time. 4. Even those who are not vision impaired will be cognitively slowed by having to interpret the fine grey lines rather than areas of greater contrast. 5. It looks unprofessional. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638167/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Patch added: "isc-dhcp debdiff" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770861/+files/isc-dhcp.debdiff -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
I'm attaching debdiffs for initramfs-tools, isc-dhcp, and open-iscsi. The combination (along with cloud-initramfs-tools and cloud-init -- see bug 1621615) seem to work with maas in IPv4, IPv6, and dual stack (booting IPv4 and IPv6), when added to yakkety-proposed. ** Patch added: "debdiff for initramfs-tools" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770859/+files/initramfs-tools.debdiff -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Patch added: "open-iscsi debdiff" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770860/+files/open-iscsi.debdiff -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
All of the debdiffs need to be rolled into zesty, and backported to yakkety, xenial. ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => In Progress ** Changed in: isc-dhcp (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: isc-dhcp (Ubuntu Yakkety) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: open-iscsi (Ubuntu Yakkety) Status: Fix Released => In Progress -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
all 3 debdiffs need to land in zesty, and be backported to yakkety and xenial for SRU. -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
attached debdiff needs to roll forward into zesty. ** Changed in: initramfs-tools (Ubuntu) Status: Fix Released => In Progress -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Is anybody able to reproduce my findings on Xenial with pulse from my PPA, i.e trying to select A2DP doesn't work, but when you manually kill and restart pulse A2DP works? I just tried on yakkety with another bluetooth controller with pulse from zesty and I didn't even need to select A2DP, it was selected and worked... Something weird is going on here, so I think I will push the fix for this bug through such that people can actually use their devices, and try and track this profile issue down. Not even sure its a race at this point... -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: In Progress Status in pulseaudio source package in Yakkety: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1635817] Re: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1635817 Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.2 Status in console-setup package in Ubuntu: Confirmed Bug description: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.2 ProblemType: Package DistroRelease: Kali 2016.2 Package: console-setup-linux 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 22 06:04:53 2016 DuplicateSignature: package:console-setup-linux:1.108ubuntu15.2 Unpacking console-setup-linux (1.152) over (1.108ubuntu15.2) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.152_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.2 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.2 InstallationDate: Installed on 2016-10-21 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10kali1 apt 1.2.12~ubuntu16.04.1 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1635817/+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 1638398] Re: Theme assets (checkboxes, troughs, etc.) are blurry in hidpi
I chatted briefly with Daniel Fore of elementary, and he provided some more details. In the elementary GTK theme, we use @2x assets for anything that cannot be done via GtkCSS. This means we provide pixel-doubled assets: https://github.com/elementary/stylesheet/tree/master/gtk-3.0/assets. This ensures crisp rendering on 2x displays. For the Ubuntu themes, this would mean we'd need to render out pixel doubled raster assets from the original source vectors if possible, or redraw the assets pixel doubled if there are not vector sources. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1638398 Title: Theme assets (checkboxes, troughs, etc.) are blurry in hidpi Status in ubuntu-themes package in Ubuntu: New Bug description: Ambiance appears to provide lodpi raster assets, which means all of these bits of the theme are not rendered crisply on hidpi displays. It would be best to redraw these assets with GtkCSS to enable crisp interface scaling, or at least find a way to provide vector or 2x assets. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1638398/+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 1638398] [NEW] Theme assets (checkboxes, troughs, etc.) are blurry in hidpi
Public bug reported: Ambiance appears to provide lodpi raster assets, which means all of these bits of the theme are not rendered crisply on hidpi displays. It would be best to redraw these assets with GtkCSS to enable crisp interface scaling, or at least find a way to provide vector or 2x assets. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1638398 Title: Theme assets (checkboxes, troughs, etc.) are blurry in hidpi Status in ubuntu-themes package in Ubuntu: New Bug description: Ambiance appears to provide lodpi raster assets, which means all of these bits of the theme are not rendered crisply on hidpi displays. It would be best to redraw these assets with GtkCSS to enable crisp interface scaling, or at least find a way to provide vector or 2x assets. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1638398/+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 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
So what can be done to get a version with this fix into Trusty? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline Status in bash package in Ubuntu: Fix Released Status in bash package in Debian: Fix Released Bug description: Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 The Debian bug includes complete reproduction case. Basically: with .inputrc containing set revert-all-at-newline On Go back in the commandline history, edit a command, then submit a different command (may be empty) Such as: $ ls something $ Attached diff is confirmed to fix the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Feb 17 15:49:30 2015 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405 [Test Case] Adapted from the Debian bug report: 1. echo "set revert-all-at-newline on" > bug.inputrc 2. INPUTRC=bug.inputrc bash 3. echo hello 4. ^P^U^N^M [Hold down control and type "punm".] Bash should die immediately with SIGABRT. [Regression Potential] Relatively low. The change has no effect at all unless _rl_revert_all_lines() is called, which only happens if revert-all-at-newline is set, and then only when a newline is typed. So, the potential for regression is essentially zero for non-interactive shells and for anyone not using revert-all-at-newline (which is not the default). Further, this change appeared upstream and in both Debian and Ubuntu over a year ago, so it's had plenty of public testing. lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates over history entries, reverting changes to each history entry. This patch causes entry->data, which points to the per-entry undo list, to be cleared before reverting edits rather than after. At first glance, this shouldn't make any difference. However, it prevents rl_do_undo() from replacing the history entry with one reflecting the change. Otherwise, the entry gets freed, leaving _rl_revert_all_lines() with an invalid pointer. _Not_ having an invalid pointer and double-free certainly can't be worse than the current situation. Since we're avoiding is making the pointer invalid rather than not doing the free, the chance of a new leak is pretty much nonexistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+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 1638395] [NEW] Unable to locate remote printer when printing
Public bug reported: My printer (EPSON Stylus Photo RX520) is connected to a Yakkety station called "paris" which is the printing server. Printing is fine from the server. When i configure another Yakkety station to print via this server, the printer is detected OK via dnssd, the driver is installed OK. But i can't print. I get the following message "Unable to locate printer "paris.local"." I used to work on xenial but the connection was through ipps. I tried to configure the connection as in xenial, to no avail ... What i did: add "192.168.1.4 paris.local" in /etc/hosts remove printer from cups, reinstalled it and i finally was able to print on the remote printer! Don't know if this problem is related to cups or avahi ... Ubuntu 16.10 cups 2.2.0-2 What i expected to happen: printing successful What happened: client cannot locate remote printer, add to add a line in /etc/hosts to make it work ** 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/1638395 Title: Unable to locate remote printer when printing Status in cups package in Ubuntu: New Bug description: My printer (EPSON Stylus Photo RX520) is connected to a Yakkety station called "paris" which is the printing server. Printing is fine from the server. When i configure another Yakkety station to print via this server, the printer is detected OK via dnssd, the driver is installed OK. But i can't print. I get the following message "Unable to locate printer "paris.local"." I used to work on xenial but the connection was through ipps. I tried to configure the connection as in xenial, to no avail ... What i did: add "192.168.1.4 paris.local" in /etc/hosts remove printer from cups, reinstalled it and i finally was able to print on the remote printer! Don't know if this problem is related to cups or avahi ... Ubuntu 16.10 cups 2.2.0-2 What i expected to happen: printing successful What happened: client cannot locate remote printer, add to add a line in /etc/hosts to make it work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638395/+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 1638388] Re: NetworkManager wont start at system boot
The bug report was generated on a migrated system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638388 Title: NetworkManager wont start at system boot Status in network-manager package in Ubuntu: New Bug description: From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478034710 Die 01 Nov 2016 22:11:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638388/+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 1638391] Re: NetworkManager wont apply configuration for all users at boot
The bug report was generated on a migrated system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638391 Title: NetworkManager wont apply configuration for all users at boot Status in network-manager package in Ubuntu: New Bug description: NetworkManager seems to ignore flag "Use this configuration for all users". The networkconfiguration is applied only for the one user who created it, not globally and this configuration is not applied at system boot! To have the system initialize network you'll have to log on with the user whom created the network configuration. Connect automaticly with this network: yes All users can use this network: yes Device: enp4s0 MTU: automatic WakeOnLAN: ON IPv4: dhcp IPv6: dhcp Network configuration at boot: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if some user logs in: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if the user whom created the network configuration logs in: # ifconfig enp4s0Link encap:Ethernet Hardware Adresse 30:65:ec:34:10:2d inet Adresse:192.168.6.46 Bcast:192.168.6.255 Maske:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:11232 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:9933 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX-Bytes:8388681 (8.3 MB) TX-Bytes:2078949 (2.0 MB) Interrupt:17 loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) I am seeing this by some systems migrated from Ubuntu 14.04.5 to 16.04.1 and by some systems newly installed from DVD with 16.04.1 or 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:27:16 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478035610 Die 01 Nov 2016 22:26:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2
[Touch-packages] [Bug 1638391] [NEW] NetworkManager wont apply configuration for all users at boot
Public bug reported: NetworkManager seems to ignore flag "Use this configuration for all users". The networkconfiguration is applied only for the one user who created it, not globally and this configuration is not applied at system boot! To have the system initialize network you'll have to log on with the user whom created the network configuration. Connect automaticly with this network: yes All users can use this network: yes Device: enp4s0 MTU: automatic WakeOnLAN: ON IPv4: dhcp IPv6: dhcp Network configuration at boot: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if some user logs in: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if the user whom created the network configuration logs in: # ifconfig enp4s0Link encap:Ethernet Hardware Adresse 30:65:ec:34:10:2d inet Adresse:192.168.6.46 Bcast:192.168.6.255 Maske:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:11232 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:9933 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX-Bytes:8388681 (8.3 MB) TX-Bytes:2078949 (2.0 MB) Interrupt:17 loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) I am seeing this by some systems migrated from Ubuntu 14.04.5 to 16.04.1 and by some systems newly installed from DVD with 16.04.1 or 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:27:16 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478035610 Die 01 Nov 2016 22:26:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638391 Title: NetworkManager wont apply configuration for all users at boot Status in network-manager package in Ubu
[Touch-packages] [Bug 1623143] Re: Linux container does not take same cpu configuration as kernet's hosts
** Package changed: linux (Ubuntu) => lxc (Ubuntu) ** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1623143 Title: Linux container does not take same cpu configuration as kernet's hosts Status in lxc package in Ubuntu: Triaged Bug description: When I configured cpu affinity on a ubuntu 16.04 with kernel version "4.4.0-36-generic" on a host containing 3 cpus: on /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0" update-grub reboot The output of "cat /proc/self/status" : ubuntu@ubuntu:~$ cat /proc/self/status . . . Cpus_allowed: 6 Cpus_allowed_list:1-2 Mems_allowed: ,0001 Mems_allowed_list:0 voluntary_ctxt_switches: 0 nonvoluntary_ctxt_switches: 1 When I create an lxd container in this host using these commands: lxc launch ubuntu:14.04 my-ubuntu And access to this container using: lxc exec my-ubuntu -- /bin/bash The output of "cat /proc/self/status" : . . . Cpus_allowed: 7 Cpus_allowed_list:0-2 Mems_allowed: ,0001 Mems_allowed_list:0 voluntary_ctxt_switches: 0 nonvoluntary_ctxt_switches: 4 Result: Container's process doesn't take same configuration as host's process. Host process use 2 cpus: Cpus_allowed_list: 1-2 Container process use 3 cpus: Cpus_allowed_list: 0-2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Tue Sep 13 18:36:29 2016 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-08-04 (40 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/username--vg-root ro isolcpus=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1623143/+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 1638388] [NEW] NetworkManager wont start at system boot
Public bug reported: >From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478034710 Die 01 Nov 2016 22:11:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638388 Title: NetworkManager wont start at system boot Status in network-manager package in Ubuntu: New Bug description: From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxE
[Touch-packages] [Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x
** Changed in: lxc (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1635639 Title: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x Status in juju-ci-tools: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Xenial: Fix Released Status in lxc source package in Yakkety: Fix Released Status in lxc source package in Zesty: Fix Released Bug description: ## SRU paperwork ### Rationale LXC 2.0.5 added support for Seccomp on the s390x architecture for those kernels that support it. Unfortunately the personality handling for s390x is wrong and results in the profile being setup twice, causing a failure to start the container. This effectively means that LXC 2.0.5 fails out of the box on s390x. ### Test case With LXC: - lxc-start -n some-container -F With LXD: - lxc start some-container ### Regression potential Our own testing shows that the fix works perfectly fine. The code change itself only affects s390x (under ifdef) so can't possibly affect the other architectures. The worst that can happen should this fix be wrong is either status quo (container won't start) or having the container start without seccomp support (status quo when compared to 2.0.4). ## Original bug report The s390x host used to Juju testing spontaneously broke today. The disk filled up, we restarted so that we could remove unused kernels. We discovered that lxc1 cannot create containers any more. $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x $ sudo lxc-start -o lxc.log -n curtis lxc-start: tools/lxc_start.c: main: 344 The container failed to start. lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. $ cat lxc.log lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15 lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 - failed loading seccomp policy lxc-start 20161020121833.069 ERRORlxc_start - start.c:__lxc_start:1313 - failed to initialize the container lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:344 - The container failed to start. lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:346 - To get more details, run the container in foreground mode. lxc-start 20161020121838.075 ERRORlxc_start_ui - tools/lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options. # sinzui: checking when s390x seccomp support was added to the # kernel, to see if it's just a missing config in our kernel that'd fix that # cleanly or if we'd need it backported to 4.4 which would be a bit more # annoying # sinzui: config-4.4.0-45-generic is what you're running right? # stgraber uname-a says 4.4.0-45-generic # stgraber> sinzui: you can workaround it by putting a file # with lxc.seccomp= # in /usr/share/lxc/config/common.conf.d/, that should get you going again WORK AROUND for LXC 1 # on the s390x-slave sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf # Advised to stgraber to add this file after seeing lxc-start fail with # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp. lxc.seccomp= To manage notifications about this bug go to: https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1623143] [NEW] Linux container does not take same cpu configuration as kernet's hosts
You have been subscribed to a public bug: When I configured cpu affinity on a ubuntu 16.04 with kernel version "4.4.0-36-generic" on a host containing 3 cpus: on /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="isolcpus=0" update-grub reboot The output of "cat /proc/self/status" : ubuntu@ubuntu:~$ cat /proc/self/status . . . Cpus_allowed: 6 Cpus_allowed_list: 1-2 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:0 nonvoluntary_ctxt_switches: 1 When I create an lxd container in this host using these commands: lxc launch ubuntu:14.04 my-ubuntu And access to this container using: lxc exec my-ubuntu -- /bin/bash The output of "cat /proc/self/status" : . . . Cpus_allowed: 7 Cpus_allowed_list: 0-2 Mems_allowed: ,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:0 nonvoluntary_ctxt_switches: 4 Result: Container's process doesn't take same configuration as host's process. Host process use 2 cpus: Cpus_allowed_list: 1-2 Container process use 3 cpus: Cpus_allowed_list:0-2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-36-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Tue Sep 13 18:36:29 2016 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-08-04 (40 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/username--vg-root ro isolcpus=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU ** Affects: lxc (Ubuntu) Importance: High Assignee: Christian Brauner (cbrauner) Status: Triaged ** Tags: amd64 apport-bug kernel-da-key xenial -- Linux container does not take same cpu configuration as kernet's hosts https://bugs.launchpad.net/bugs/1623143 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. -- 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 1297800] Re: During upgrades, new certificates will be added. Please choose those you trust.
reason: sudo dpkg-reconfigure ca-certificates Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1297800 Title: During upgrades, new certificates will be added. Please choose those you trust. Status in ca-certificates package in Ubuntu: Expired Bug description: While upgrading ca-certificates from version 20111211 to 20130906ubuntu0.12.04.1 I got the following dialog: │ During upgrades, new certificates will be added. Please choose those you trust. │ │ │ │ New certificates to activate: │ │ │ │[ ] mozilla/Actalis_Authentication_Root_CA.crt │ │[ ] mozilla/Buypass_Class_2_Root_CA.crt │ │[ ] mozilla/Buypass_Class_3_Root_CA.crt │ │[ ] mozilla/CA_Disig_Root_R1.crt │ │[ ] mozilla/CA_Disig_Root_R2.crt │ │[ ] mozilla/China_Internet_Network_Information_Center_EV_Certificates_Root.crt │ │[ ] mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt │ │[ ] mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt│ │[ ] mozilla/EC-ACC.crt │ │[ ] mozilla/EE_Certification_Centre_Root_CA.crt │ │[ ] mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2011.crt │ │ │ │ │ │ │ Is it really reasonable to expect most users to know what to do with this and what the fallout is of making incorrect choices? I know my mom certainly would not have a clue about what to do with this. Hell, I am a software and network engineer and I don't know which of the above I should trust and what the fallout of not trusting some/all of them. And in reality, I need (way) more information that is presented in that dialog to make a decision about any one of those certificate/CAs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1297800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history - patch
Precise is soon EOL anyway, so non-essential changes are not worth it. I have sponsored the accountsservice debdiff to the trusty queue. Please unsubscribe ubuntu-sponsors again. ;) ** No longer affects: gnome-control-center (Ubuntu Xenial) ** No longer affects: unity-control-center (Ubuntu Xenial) ** Also affects: accountsservice (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: accountsservice (Ubuntu Trusty) Status: New => In Progress ** Changed in: accountsservice (Ubuntu Trusty) Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Trusty: In Progress Status in accountsservice source package in Xenial: In Progress Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1638135] Re: package libdbus-glib-1-2 0.106-1 [modified: usr/share/doc/libdbus-glib-1-2/NEWS.gz usr/share/doc/libdbus-glib-1-2/README usr/share/doc/libdbus-glib-1-2/changelog.Deb
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-glib in Ubuntu. https://bugs.launchpad.net/bugs/1638135 Title: package libdbus-glib-1-2 0.106-1 [modified: usr/share/doc/libdbus- glib-1-2/NEWS.gz usr/share/doc/libdbus-glib-1-2/README usr/share/doc /libdbus-glib-1-2/changelog.Debian.gz usr/share/doc/libdbus- glib-1-2/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdbus-glib-1-2/README', which is different from other instances of package libdbus-glib-1-2:i386 Status in dbus-glib package in Ubuntu: New Bug description: not exactly sure how this happened. Also my wifi devixe drivers keep uninstall or not functioning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdbus-glib-1-2 0.106-1 [modified: usr/share/doc/libdbus-glib-1-2/NEWS.gz usr/share/doc/libdbus-glib-1-2/README usr/share/doc/libdbus-glib-1-2/changelog.Debian.gz usr/share/doc/libdbus-glib-1-2/copyright] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: libdbus-glib-1-2: Install libdbus-glib-1-2: Configure libdbus-glib-1-2: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Oct 31 15:37:59 2016 DpkgTerminalLog: Preparing to unpack .../libdbus-glib-1-2_0.106-1_i386.deb ... Unpacking libdbus-glib-1-2:i386 (0.106-1) over (0.100.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libdbus-glib-1-2_0.106-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdbus-glib-1-2/README', which is different from other instances of package libdbus-glib-1-2:i386 DuplicateSignature: package:libdbus-glib-1-2:0.106-1 [modified: usr/share/doc/libdbus-glib-1-2/NEWS.gz usr/share/doc/libdbus-glib-1-2/README usr/share/doc/libdbus-glib-1-2/changelog.Debian.gz usr/share/doc/libdbus-glib-1-2/copyright] Unpacking libdbus-glib-1-2:i386 (0.106-1) over (0.100.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libdbus-glib-1-2_0.106-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libdbus-glib-1-2/README', which is different from other instances of package libdbus-glib-1-2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libdbus-glib-1-2/README', which is different from other instances of package libdbus-glib-1-2:i386 InstallationDate: Installed on 2016-10-22 (9 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: dbus-glib Title: package libdbus-glib-1-2 0.106-1 [modified: usr/share/doc/libdbus-glib-1-2/NEWS.gz usr/share/doc/libdbus-glib-1-2/README usr/share/doc/libdbus-glib-1-2/changelog.Debian.gz usr/share/doc/libdbus-glib-1-2/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdbus-glib-1-2/README', which is different from other instances of package libdbus-glib-1-2:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-glib/+bug/1638135/+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 1173915] Re: initctl continuously takes 100% of CPU
Happens on Ubuntu 16.10 (fresh install, Compiz fallback session) after a few
hours of uptime.
htop reports 100% usage of one CPU for the command
/sbin/initctl emit indicator-services-start
which goes on indefinitely. Tracing (with only this initctl process
around) yields similar to #5
$ sudo strace -p `pidof initctl`
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
[endless repeat]
/var/log/upstart is empty and dmesg/kern.log/syslog don't help.
The random battery drain is annoying (especially during presentations),
and apt purging upstart depends on a little too much for comfort.
Suggestions?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1173915
Title:
initctl continuously takes 100% of CPU
Status in upstart package in Ubuntu:
Confirmed
Bug description:
Many programs are fairly slow to start on my computer, despite it
being relatively new (core i5). Suspecting a heavy CPU usage, I
started gnome-system-monitor: all processes were displayed at 0% CPU,
but the overall load was 1.33; 1.33; 1.34.
Using the "top" command, however, revealed the real CPU use, with the
"initctl" process taking 100%CPU, even 1 hour after startup.
I upgraded to roaring ringtail before checking this but the symptoms
were the same with quantal quetzal, so there is a fair chance the
causes were identical.
Regards
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: upstart 1.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Sun Apr 28 13:04:05 2013
ExecutablePath: /sbin/initctl
InstallationDate: Installed on 2012-12-15 (133 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
SourcePackage: upstart
UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
UpstartBugCategory: System
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1173915/+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 1637815] Re: compiz error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1637815 Title: compiz error Status in xorg package in Ubuntu: New Bug description: compiz error after upgrading to ubuntu 16.10. Possible hacking issues directed at my operating system. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.98 Mon Sep 19 17:31:03 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 30 10:54:34 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-43-generic, x86_64: installed bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed nvidia-340, 340.98, 4.4.0-43-generic, x86_64: installed nvidia-340, 340.98, 4.8.0-26-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848f] InstallationDate: Installed on 2016-09-18 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd01/06/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Oct 30 10:16:35 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputEee PC WMI hotkeys KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1630297] Re: open window titles not shown in launcher menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630297 Title: open window titles not shown in launcher menu Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: webbrowser-app with multi-window support just landed and works in unity8 the launcher icon shows dots representing the windows, but when right clicking on the launcher icon I expected to see the window titles in the menu (like unity7) but these are not shown To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630297/+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 1451096] Re: wrong rsyslog dependency in ubuntu-minimal
As of 16.10 ubuntu-minimal "Recommends: rsyslog" which I thin is still wrong but not as bad as dependency. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1451096 Title: wrong rsyslog dependency in ubuntu-minimal Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: According to dependencies of ubuntu-minimal rsyslog is considered to be part of minimal supported system. With the switch to systemd it's obsolete: the journald is shipped and running anyway and it already provides secure logging by default. IT would be better to remove rsyslog from ubuntu-minimal dependencies (and, ideally, from default install as well) and enables "ForwardToSyslog=no" in /etc/systemd/journald.conf - the users who are willing to install advanced legacy logging will still be able to do that just fine, but really does not belong to the bare-minimum system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451096/+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 1582421] Re: removing upstart breaks user login
16.10 is slightly better in this regard - at least login is possible when upstart is purged, but the fact that it's still installed by default is alarming: did they forgot to fix smth again? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1582421 Title: removing upstart breaks user login Status in ubuntu-meta package in Ubuntu: New Bug description: After "apt remove upstart" it's impossible to login into user's session via lightdm on xubuntu 16.04 - I thought we've finally ditched that junk, how come it still breaks the system on removal? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1582421/+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 1443052] Re: User accounts login history showing incorrect history
** Patch added: "FixLogoutTimesInLogin-HistoryTrusty.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/accountsservice/+bug/1443052/+attachment/4770694/+files/FixLogoutTimesInLogin-HistoryTrusty.debdiff ** Summary changed: - User accounts login history showing incorrect history + User accounts login history showing incorrect history - patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Re: User accounts login history showing incorrect history
The patch does not seem to be compatible with the version of accountsservice on Precise, however I have adapted it for Trusty and tested it in a VM and it works. So here is a debdiff for it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history - patch Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1443052] Re: User accounts login history showing incorrect history
** No longer affects: unity-control-center (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: Impact --- Logout times for users are correct if user logs off and then shutdown from GDM, however logout times are wrong if user shutdowns directly from the user session, because DEAD_PROCESS record is missing in that case and BOOT_TIME record is used instead. Therefore the logout time will be shown in the login-history (in the gnome-control-center) just before the next login time rather than when the logout actually occurred. Test case -- 1. Make sure that you have turned on and logged into the machine and then turned off from the user session several times with enough distance between them for you to tell that the timestamps are correct. 2. Check that after applying the patch that the timestamps show the correct times for the logins and logouts and not what is described in the Impact section above. Regression potential I have not encountered any regressions while testing this patch. -- Original description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1637801] Re: Incorrect Russian translation of "apt list --upgradeable" results
Thanks for letting us know, Julian. That will hopefully bring more up- to-date translations, installed by apt in /usr/share/locale, into Xenial. I'm going to follow up why gettext ignores the apt.mo files in /usr/share/locale-langpack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1637801 Title: Incorrect Russian translation of "apt list --upgradeable" results Status in Ubuntu Translations: Invalid Status in apt package in Ubuntu: Fix Committed Status in gettext package in Ubuntu: New Bug description: bor@bor-Latitude-E5450:~$ apt list --upgradeable Вывод списка… Готово build/неизвестно 20161025 all [может быть обновлён до: 20151105] In Russian this means "version 20161025 can be upgraded TO version 20151105) While original English says exactly opposite: bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable Listing... Done build/unknown 20161025 all [upgradable from: 20151105] Literal translation (that does not require serious phrase change) would probably be "может быть обновлен с" although it sounds also artificial, as in Russian subject is package that is being updated (currently installed), not new version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 30 09:39:47 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (485 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1637801/+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 1638348] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubun
Public bug reported: No details available ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Tue Nov 1 15:05:03 2016 ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1638348 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg- turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: No details available ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Tue Nov 1 15:05:03 2016 ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1638348/+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 1439687] Re: Can not report bug: SSL Certificate Verify Failure
This bug still exists in Ubuntu 16.10. LC_ALL=C apt-cache policy apport-gtk apport-gtk: Installed: 2.20.3-0ubuntu8 Candidate: 2.20.3-0ubuntu8 Version table: *** 2.20.3-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1439687 Title: Can not report bug: SSL Certificate Verify Failure Status in apport package in Ubuntu: Confirmed Status in whoopsie package in Ubuntu: Invalid Bug description: I called apport with apport-bug linux, because I wanted to report a kernel bug. However I could not send the logs to launchpad because of the following error message: Distribution: Kubuntu 15.04 64 Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439687/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
There is a Xenial test kernel with the original fix and a pick of commit c5868f8. Can you give this test kernel a test? It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/ I'm in the process of building a Trusty test kernel as well and will post a link to it when it's ready. ** No longer affects: e2fsprogs (Ubuntu) ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** No longer affects: e2fsprogs (Ubuntu Trusty) ** No longer affects: e2fsprogs (Ubuntu Vivid) ** No longer affects: e2fsprogs (Ubuntu Xenial) ** No longer affects: e2fsprogs (Ubuntu Yakkety) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
This appears to be the same error message you were getting when you originally opened the bug, is that correct? You are just now getting it with other btrfs operations now? There may be some additional commits that are needed. I'll build a Xenial and Trusty test kernel for testing. ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High ** Changed in: linux (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+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 1638345] [NEW] avahi-daemon crashes multiple times an hour
Public bug reported: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) ** Affects: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: New Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1637633] Re: Can 't log in ubuntuone account with plugin
OK. That is not using ubuntuone-credentials. I've moved the bug to gnome-software as the issue is there. Thanks. ** Package changed: ubuntuone-credentials (Ubuntu) => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1637633 Title: Can 't log in ubuntuone account with plugin Status in gnome-software package in Ubuntu: Confirmed Bug description: When i want to login in my ubuntuone account with a plugin it show me "Incorrect password or email", but everything works when i login in web, because my login(email) and password are correct. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: account-plugin-ubuntuone 15.11+16.10.20160920 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 23:33:50 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-10-22 (6 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntuone-credentials UpgradeStatus: Upgraded to yakkety on 2016-10-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1637633/+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 1451808] Re: apport-collect error: No module named PyQt5.QtCore
I'm having the same problem in Kubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1451808 Title: apport-collect error: No module named PyQt5.QtCore Status in apport package in Ubuntu: Confirmed Bug description: In kubuntu vivid, apport reacts as follows: apport-collect 1451277 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 5 14:35:33 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451808/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Triaged Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Released Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
strace of ssh gitlab.com ** Attachment added: "strace-ssh.log" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+attachment/4770653/+files/strace-ssh.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: New Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
/etc/default/locale is attached. ** Attachment added: "locale" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+attachment/4770648/+files/locale -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: New Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
/etc/environment is attached. ** Attachment added: "environment" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+attachment/4770650/+files/environment -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: New Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1638338] [NEW] Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
Public bug reported: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re-run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: openssh-client yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: New Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Y
[Touch-packages] [Bug 1638337] [NEW] Progress bar is shown after opening new window
Public bug reported: What happened: 1) Open the webbrowser-app 2) Navigate to a website, note that the progress bar goes blue, shows progress and disappears 3) Open a new tab, notice there is no progress bar 4) Open a new window 5) Notice that you are on the new tab view, but there is a grey progress bar shown with no progress Note: if you open another tab, navigate to a website. The progress bar functions and disappears, then if you go back to the first tab the progress bar is now hidden. What I expected to happen: At step 5 when viewing the new tab view in the new window, that the progress bar is not shown. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1638337 Title: Progress bar is shown after opening new window Status in webbrowser-app package in Ubuntu: New Bug description: What happened: 1) Open the webbrowser-app 2) Navigate to a website, note that the progress bar goes blue, shows progress and disappears 3) Open a new tab, notice there is no progress bar 4) Open a new window 5) Notice that you are on the new tab view, but there is a grey progress bar shown with no progress Note: if you open another tab, navigate to a website. The progress bar functions and disappears, then if you go back to the first tab the progress bar is now hidden. What I expected to happen: At step 5 when viewing the new tab view in the new window, that the progress bar is not shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1638337/+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 1616079] Re: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1616079 Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out Status in pulseaudio package in Ubuntu: Confirmed Bug description: No sound in speakers or in headphones after upgrade to ubuntu 16.04. No devices shown in Sound settings -> Play sound through Previously in ubuntu 14.04 sound works good. sglukhov@Galvatron:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Aug 23 16:24:58 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-01-25 (210 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to xenial on 2016-07-05 (49 days ago) dmi.bios.date: 11/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 00DTF3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd11/09/2015:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn00DTF3:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7270 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1616079/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Triaged Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Released Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Triaged Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+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 1614226] Re: package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High -- 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/1614226 Title: package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk-3-bin 3.18.9-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 16 09:49:41 2016 ErrorMessage: subprocess new pre-installation script returned error exit status 2 InstallationDate: Installed on 2016-08-10 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: gtk+3.0 Title: package libgtk-3-bin 3.18.9-1ubuntu3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 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/1614226/+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 1606159] Re: Battery not recognized on HP Pavilion Detachable X2 10-N123NF
** Changed in: upower (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1606159 Title: Battery not recognized on HP Pavilion Detachable X2 10-N123NF Status in upower package in Ubuntu: Confirmed Bug description: After a clean install of xenial on HP Pavilion Detachable X2 10-N123NF, the battery is not "seen" at all. It doesn't appear in Ubuntu's "energy" tab. # acpi No support for device type: power_supply However...: # lshw -class power USB *-battery description: Lithium Ion Battery product: O02033X vendor: 333-42-D7 physical id: 1 version: 02/07/2026 serial: 01794 02/07/2026 slot: Primary capacity: 33060mWh configuration: voltage=3.8V *-power UNCLAIMED description: OEM Define 1 product: OEM Define 5 vendor: OEM Define 2 physical id: 2 version: OEM Define 6 serial: OEM Define 3 capacity: 42mWh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi-support 0.142 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 25 10:55:19 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: acpi-support UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1606159/+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 1583182] Re: error on 01ifupdown script
** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1583182 Title: error on 01ifupdown script Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: When bring the interface up or down I see this message on the logs May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. May 18 10:03:36 count0 NetworkManager[791]: [1463576616.8466] dispatcher: (29) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Tracing the problem I see that the call to /usr/sbin/fanctl is done with incorrect parameters. If I execute /etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down I get this error run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1 ubuntu-fan is doing the call in following way /usr/sbin/fanctl net "$MODE" "$IFACE" and the parameters passed by ubuntu-fan are $MODE=stop $IFACE=enp2s0 but fanctl expect other parameters as showed on the script's header -- details lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 18 10:50:24 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-76f79dfb13e0 proto kernel scope link src 172.18.0.1 linkdown 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.8 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH br-76f79dfb13e0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 br-76f79dfb13e0 0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68 /org/freedesktop/NetworkManager/ActiveConnection/1 docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 e5f99f7d-532f-4c52-8749-c78afa9271dd /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 ee3ec6ee-7242-4956-9d19-20ccb19c5fe5 /org/freedesktop/NetworkManager/ActiveConnection/8 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1583182/+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 1623666] Re: iOS10 will not connect to Ubuntu
Nikos, I will try your patch this evening and report back (it is morning for me right now so I must work). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1624211] Re: Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624211 Title: Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card Status in network-manager package in Ubuntu: Confirmed Bug description: When resuming from sleep or coming out of hibernation and sometimes when disabing and reenabling the wireless card (using Fn + the corresponding key), network-manager will stop recognizing that there's a wireless card in my laptop. The bluetooth applet and the card themselves still work. I can still connect to the same network it was connected before putting it to sleep/hibernate (because it's a known network and it does so automatically) but network-manager won't display anything regarding me having a wireless card, displaying the icon and information I would expect if I were connected using an ethernet cable. A workaround consists in restarting the network-manager service using systemctl sudo service network-manager restart or sudo systemctl restart network-manager.service The system is a Dell Vostro 5470 running a fresh installation of Ubuntu 16.04.1. If I recall correctly, this also happened with Ubuntu 14.04.4 too. BIOS version is A12 (the latest). I've seen several people with problems like this one that were solved by restarting network-manager (a quick Googling shows a handful of such cases). This can be a huge turn off for a newcomer. Some people also suggested creating a systemd service to restart the network-manager service when resuming, etc. but since this bug also occurs when disabling/reenabling the card, it might have another cause that's unrelated to resuming from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 16 01:26:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-10 (6 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.248 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 That's no moon! 1 2a59043a-02a4-4da0-ab5c-3c89c52bd15f /org/freedesktop/NetworkManager/ActiveConnection/1 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624211/+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 1624503] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: fontconfig (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1624503 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: got error while upgrading from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Sep 16 22:48:53 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-04-02 (167 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-09-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1624503/+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 1614806] Re: This package breaks "ark" rar support
** Changed in: shared-mime-info (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1614806 Title: This package breaks "ark" rar support Status in shared-mime-info package in Ubuntu: Confirmed Bug description: So i was told here: https://bugs.kde.org/show_bug.cgi?id=367535 this mav be a package bug in ubuntu xenial, which i confirmed. There are links to the upstream issue, which is already fixed, and a bugfix that i would gladly wish you backport. Description:KDE neon User Edition 5.7 Release:16.04 shared-mime-info: Installed: 1.5-2ubuntu0.1 Candidate: 1.5-2ubuntu0.1 Version table: *** 1.5-2ubuntu0.1 500 500 http://do.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.5-2 500 500 http://do.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1614806/+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 1623666] Re: iOS10 will not connect to Ubuntu
Only assign yourselves to bugs just before starting working on them. ** Changed in: libimobiledevice (Ubuntu) Assignee: per (eura) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu
The affected hardware is non-core. ** Changed in: libimobiledevice (Ubuntu) Importance: High => Medium ** Changed in: gnutls28 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2
Jeffrey Walton (noloader) wrote on 2015-05-12: #17 This can now be closed due to USN-2606-1 (http://www.ubuntu.com/usn/usn-2606-1/). Good work. I'm glad to see TLS 1.2 is now available to LTS. - O It does work on Apache now. Does it work on nginx also? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1256576 Title: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2 Status in openssl package in Ubuntu: Fix Released Bug description: The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0. A wireshark trace shows the version of OpenSSL used by Ubuntu does not support TLS 1.2. According to the change logs, TLS 1.2 support was added 14 March 2012. The change log can be found at http://www.openssl.org/news/changelog.html, and the TLS additions can be found under the heading "Changes between 1.0.0h and 1.0.1". $ ldd /usr/lib/x86_64-linux-gnu/libssl.so linux-vdso.so.1 => (0x7fffd9d84000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f1e0691e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000) /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000) *** OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ (http://www.openssl.org/support/faq.html): 8. How does the versioning scheme work? After the release of OpenSSL 1.0.0 the versioning scheme changed. Letter releases (e.g. 1.0.1a) can only contain bug and security fixes and no new features. Minor releases change the last number (e.g. 1.0.2) and can contain new features that retain binary compatibility. Changes to the middle number are considered major releases and neither source nor binary compatibility is guaranteed. ** By the way, its nearly impossible to file a bug report through the launch pad. The maze that's been created is impossible to navigate, and its worse than one of those phone menu systems. I had to look up the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job to the designers of the system. Its probably the same idiots who thought a tablet manager was a great idea on the desktop.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1256576/+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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Changed in: dialer-app (Ubuntu)
Status: New => Fix Committed
** Changed in: messaging-app (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-filemanager-app
Status: Fix Committed => Fix Released
** Changed in: ubuntu-terminal-app (Ubuntu)
Status: New => Fix Released
** Changed in: history-service (Ubuntu)
Status: New => In Progress
--
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/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in Ubuntu File Manager App:
Fix Released
Status in address-book-app package in Ubuntu:
Fix Committed
Status in dialer-app package in Ubuntu:
Fix Committed
Status in history-service package in Ubuntu:
In Progress
Status in indicator-bluetooth package in Ubuntu:
New
Status in indicator-keyboard package in Ubuntu:
New
Status in indicator-location package in Ubuntu:
New
Status in indicator-messages package in Ubuntu:
New
Status in indicator-network package in Ubuntu:
New
Status in indicator-power package in Ubuntu:
New
Status in indicator-session package in Ubuntu:
New
Status in indicator-sound package in Ubuntu:
New
Status in indicator-transfer package in Ubuntu:
New
Status in messaging-app package in Ubuntu:
Fix Released
Status in ubuntu-system-settings package in Ubuntu:
Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
Fix Released
Status in ubuntu-touch-session package in Ubuntu:
New
Status in unity-scope-scopes package in Ubuntu:
New
Status in unity-scopes-api package in Ubuntu:
In Progress
Status in unity-scopes-shell package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Fix Released
Status in webbrowser-app package in Ubuntu:
Fix Released
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2
TLSv1.2 was re-enabled in Ubuntu 12.04 LTS in May 2015, so if you install all the updates, you should be getting it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1256576 Title: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2 Status in openssl package in Ubuntu: Fix Released Bug description: The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0. A wireshark trace shows the version of OpenSSL used by Ubuntu does not support TLS 1.2. According to the change logs, TLS 1.2 support was added 14 March 2012. The change log can be found at http://www.openssl.org/news/changelog.html, and the TLS additions can be found under the heading "Changes between 1.0.0h and 1.0.1". $ ldd /usr/lib/x86_64-linux-gnu/libssl.so linux-vdso.so.1 => (0x7fffd9d84000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f1e0691e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000) /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000) *** OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ (http://www.openssl.org/support/faq.html): 8. How does the versioning scheme work? After the release of OpenSSL 1.0.0 the versioning scheme changed. Letter releases (e.g. 1.0.1a) can only contain bug and security fixes and no new features. Minor releases change the last number (e.g. 1.0.2) and can contain new features that retain binary compatibility. Changes to the middle number are considered major releases and neither source nor binary compatibility is guaranteed. ** By the way, its nearly impossible to file a bug report through the launch pad. The maze that's been created is impossible to navigate, and its worse than one of those phone menu systems. I had to look up the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job to the designers of the system. Its probably the same idiots who thought a tablet manager was a great idea on the desktop.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1256576/+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 1637633] Re: Can 't log in ubuntuone account with plugin
Yes in the gnome-software. System ask me to login with Ubuntu SSE when I try to install/remove any snap package. Please see the screen below. ** Attachment added: "Login_error.png" https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1637633/+attachment/4770631/+files/Login_error.png ** Changed in: ubuntuone-credentials (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1637633 Title: Can 't log in ubuntuone account with plugin Status in ubuntuone-credentials package in Ubuntu: Confirmed Bug description: When i want to login in my ubuntuone account with a plugin it show me "Incorrect password or email", but everything works when i login in web, because my login(email) and password are correct. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: account-plugin-ubuntuone 15.11+16.10.20160920 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 28 23:33:50 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2016-10-22 (6 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntuone-credentials UpgradeStatus: Upgraded to yakkety on 2016-10-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1637633/+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 1638167] Re: Thin grey lines on a white background look inconsistent and provide poor contrast
We have a new visual design for the browser currently being implemented. The style of the new tabs will rely less on contrasts as the selected tab takes on a different shape. We are also trying to add a divider at the bottom of the chrome to help make it more distinct. Andrew Hayzen will investigate it. As for the differences in icons, this is something I'll have Matthieu James look at in the icon theme. ** Changed in: ubuntu-ux Status: New => In Progress -- 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/1638167 Title: Thin grey lines on a white background look inconsistent and provide poor contrast Status in Canonical System Image: New Status in Ubuntu UX: In Progress Status in webbrowser-app package in Ubuntu: Incomplete Bug description: The top area of the browser window is really just a series thin grey lines on a white background. This is poor design for a few reasons: 1. Grey and white don't contrast very well, especially thin strips of grey on white. 2. The grey outlines and symbols are inconsistent in thickness and colour: 2.1. The X icon is thinner than the + icon beside it, which is a different consistency again to the < button below it. 2.2. The rounded grey outline around the address is slighly thicker (blurred?) compared to the grey outline delineating the tabs. 3. Those vision impaired will have a very hard time. 4. Even those who are not vision impaired will be cognitively slowed by having to interpret the fine grey lines rather than areas of greater contrast. 5. It looks unprofessional. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638167/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
@unrud: Thanks for the tests. Also tested on 16.04.1 live - interestingly, the devices seem to be on /dev/i2c-9 there. However, I think even SMBus isn't at fault. Digging through the logs I noticed I forgot to check the dmesg logs - seems like sometimes the BIOS touches the amp for some reason: [6.980350] i801_smbus :00:1f.3: BIOS is accessing SMBus registers [6.980358] i801_smbus :00:1f.3: Driver SMBus register access inhibited The issue is rather random (sometimes stays even after a restart, sometimes doesn't appear after sleep), but it appears that when BIOS stays away, init-headphone works. -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+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 1256576] Re: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2
Marc Deslauriers (mdeslaur) wrote on 2013-12-02: Unfortunately, because of the large number of sites which incorrectly handled TLS v1.2 negotiation, we had to disable TLS v1.2 on the client. Marc Deslauriers (mdeslaur) wrote on 2014-12-08:#15 Apache2 in 12.04 supports TLSv1.2 just fine, I've been running test scripts against it. Hi Marc, I'm running 12.04 and nginx. Is TLSv1.2 enabled on my config? We are updating to 16.04 but need a quick fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1256576 Title: Ubuntu 12.04 LTS: OpenSSL downlevel version is 1.0.0, and does not support TLS 1.2 Status in openssl package in Ubuntu: Fix Released Bug description: The long term support version of Ubuntu 12.04 provides OpenSSL 1.0.0. A wireshark trace shows the version of OpenSSL used by Ubuntu does not support TLS 1.2. According to the change logs, TLS 1.2 support was added 14 March 2012. The change log can be found at http://www.openssl.org/news/changelog.html, and the TLS additions can be found under the heading "Changes between 1.0.0h and 1.0.1". $ ldd /usr/lib/x86_64-linux-gnu/libssl.so linux-vdso.so.1 => (0x7fffd9d84000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x7f1e0691e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1e0655e000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f1e06359000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1e06142000) /lib64/ld-linux-x86-64.so.2 (0x7f1e06f6d000) *** OpenSSL 1.0.1 is compatible with 1.0.0. From the OpenSSL FAQ (http://www.openssl.org/support/faq.html): 8. How does the versioning scheme work? After the release of OpenSSL 1.0.0 the versioning scheme changed. Letter releases (e.g. 1.0.1a) can only contain bug and security fixes and no new features. Minor releases change the last number (e.g. 1.0.2) and can contain new features that retain binary compatibility. Changes to the middle number are considered major releases and neither source nor binary compatibility is guaranteed. ** By the way, its nearly impossible to file a bug report through the launch pad. The maze that's been created is impossible to navigate, and its worse than one of those phone menu systems. I had to look up the URL to file at http://www.cryptopp.com/wiki/Talk:Linux. Great job to the designers of the system. Its probably the same idiots who thought a tablet manager was a great idea on the desktop.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1256576/+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 1499943] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1499943 Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in gconf package in Ubuntu: Confirmed Bug description: I get the message on startup ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gconf2 3.2.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Thu Sep 24 17:30:33 2015 DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2014-05-02 (511 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: gconf Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1499943/+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 1617583] Re: Ubuntu 16.04 system freeze xorg libglx.so
I have updated/upgraded my fresh XUbuntu install and no more trouble with new updated libglx.so With Ubuntu, freeze (media player totem) is not resolved, as Sebastien with last updated BIOS P1.70 -- 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/1617583 Title: Ubuntu 16.04 system freeze xorg libglx.so Status in xorg package in Ubuntu: Incomplete Bug description: System freezes after random time, sometimes after hours, sometimes not. When freeze, need to switch off power. No freezes any more after removing /usr/lib/xorg/modules/extensions/libglx.so. I dind't find anything in system logs. System was upgraded from 14.04 LTS to 16.04 TLS. With 14.04 no freezes. Other linux running well (double boot). Tried a few things before finding cause, e. g. disabling swap, changed from KDE to LXDE, I also tried kernels 4.6.0 and 4.6.5. System info: Ubuntu 16.04.1 LTS (prio installed as Kubuntu 14.04) xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2.3 $ sudo lshw -numeric -C display *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:F31] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:91 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) What information should I provide? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Aug 27 16:13:39 2016 InstallationDate: Installed on 2015-01-15 (589 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: xorg-server UpgradeStatus: Upgraded to xenial on 2016-08-01 (25 days ago) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: * Setting up X socket directories... [210G [204G[ OK ] Loading the saved-state of the serial devices from /etc/serial.conf Running 0dns-down to make sure resolv.conf is ok...done. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-08-01 23:20:00,705 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-35-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1849:0f31] InstallationDate: Installed on 2015-01-15 (596 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:246:5: QML ListView: Binding loop detected for property "currentIndex" MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=b810fade-4df5-4817-8741-167986a495dd ro noplymouth vga=792 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Tags: xenial third-party-packages ubuntu Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-08-01 (32 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/31/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: Q1900-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Fille
[Touch-packages] [Bug 1638310] [NEW] package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I don't know, I was updating Lubuntu and the system suggested to type a command on the terminal. I typed it and the system redirected me here...probably some issues with updating? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CrashReports: 0:1000:1000:560591:2016-10-26 12:18:57.473241227 +0200:2016-10-26 12:18:55.568439605 +0200:/var/crash/_usr_bin_pcmanfm.1000.crash 600:0:0:131741:2016-11-01 15:29:28.891740322 +0100:2016-11-01 15:29:29.891740322 +0100:/var/crash/whoopsie.0.crash 664:1000:1000:0:2016-11-01 15:01:49.421866752 +0100:2016-11-01 15:01:49.421866752 +0100:/var/crash/_usr_lib_notification-daemon_notification-daemon.1000.upload 640:1000:1000:1279808:2016-11-01 15:01:48.417867183 +0100:2016-11-01 15:01:49.417867183 +0100:/var/crash/_usr_lib_notification-daemon_notification-daemon.1000.crash 640:1000:1000:18146:2016-10-27 21:00:39.801043272 +0200:2016-10-28 10:42:48.702032989 +0200:/var/crash/_usr_share_hplip_upgrade.py.1000.crash Date: Tue Nov 1 15:29:29 2016 DuplicateSignature: package:whoopsie:0.2.24.6ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-12-23 (1408 days ago) InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: whoopsie Title: package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2015-03-01 (610 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1638310 Title: package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in whoopsie package in Ubuntu: New Bug description: I don't know, I was updating Lubuntu and the system suggested to type a command on the terminal. I typed it and the system redirected me here...probably some issues with updating? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: whoopsie 0.2.24.6ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CrashReports: 0:1000:1000:560591:2016-10-26 12:18:57.473241227 +0200:2016-10-26 12:18:55.568439605 +0200:/var/crash/_usr_bin_pcmanfm.1000.crash 600:0:0:131741:2016-11-01 15:29:28.891740322 +0100:2016-11-01 15:29:29.891740322 +0100:/var/crash/whoopsie.0.crash 664:1000:1000:0:2016-11-01 15:01:49.421866752 +0100:2016-11-01 15:01:49.421866752 +0100:/var/crash/_usr_lib_notification-daemon_notification-daemon.1000.upload 640:1000:1000:1279808:2016-11-01 15:01:48.417867183 +0100:2016-11-01 15:01:49.417867183 +0100:/var/crash/_usr_lib_notification-daemon_notification-daemon.1000.crash 640:1000:1000:18146:2016-10-27 21:00:39.801043272 +0200:2016-10-28 10:42:48.702032989 +0200:/var/crash/_usr_share_hplip_upgrade.py.1000.crash Date: Tue Nov 1 15:29:29 2016 DuplicateSignature: package:whoopsie:0.2.24.6ubuntu3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-12-23 (1408 days ago) InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: whoopsie Title: package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2015-03-01 (610 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1638310/+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 1585278] Re: Browser window does not fill the screen width when starting
** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: unity8 (Ubuntu) Status: New => Fix Committed -- 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/1585278 Title: Browser window does not fill the screen width when starting Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: Fix Committed Status in webbrowser-app package in Ubuntu: Fix Committed Bug description: bq M10 rc-proposed r112 When staring Browser app in landscape first I see splash screen, then the Browser window which is squared and then the complete Browser window with tabs opened. For the beter UX the second step should be skipped or that window should take the full width of the tablet. Screenshot of the problem attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1585278/+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 1638301] [NEW] systemctl start auto-completion it's not working
Public bug reported: When i try to auto-complete the "systemctl start " the following error message is shown in bash: Unit org.freedesktop.network1.busname could not be found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:42:37 2016 InstallationDate: Installed on 2015-06-20 (499 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System Vostro 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GG0VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Vostro 3450 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Summary changed: - systemctl start command shows a error message on "auto-complation" + systemctl start auto-completion it's not working -- 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/1638301 Title: systemctl start auto-completion it's not working Status in systemd package in Ubuntu: New Bug description: When i try to auto-complete the "systemctl start " the following error message is shown in bash: Unit org.freedesktop.network1.busname could not be found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:42:37 2016 InstallationDate: Installed on 2015-06-20 (499 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System Vostro 3450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0GG0VM dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Vostro 3450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1638245] [NEW] Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package
Thanks, I will try that. Maybe tomorrow, but you might be able to reproduce this by creating a symlink in user home to a directory in another partition (ext 4 or ntsf) and secondly going into that dir by clicking the symlink, and thirdly trying to delete any file there (no subfolder). On Tue, 1 Nov 2016 at 14:01, Iain Lane wrote: > On Tue, Nov 01, 2016 at 10:48:08AM -, Launchpad Bug Tracker wrote: > > So I was wondering if Ubuntu devs can leave out that particular patch > > when building this package for Ubuntu - if it doesn't cause more harm, > > which I doubt. > > The patch is there for a reason - otherwise you can't delete on > overlayfs. > > I have asked in a few places for specific steps I can follow from a > clean install in a VM to reproduce this problem so that I can try to fix > it. Nobody has yet given me them. > > Can you provide that? > > -- > Iain Lane [ i...@orangesquash.org.uk ] > Debian Developer [ la...@debian.org ] > Ubuntu Developer [ la...@ubuntu.com ] > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1638245 > > Title: > Files in the root of a folder on another partition symlinked to user's > home cannot be moved to trash because of a patch in this package > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+subscriptions > -- Sent from a mobile device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638245 Title: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package Status in glib2.0 package in Ubuntu: New Bug description: I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1. I've reported this bug (or marked as "it affects me") in a couple of other places before I've finally discovered that this is the package that's causing this problem, which unfortunately has been around for a couple of years now. This bug has been reported upstream as well, but it's just taking very very long to arrive at a decision and take action it seems. Apparently one of the patches (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix- trashing-on-overlayfs.patch/) which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz) to the original package which is here (https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz) is the root cause of this annoying problem. As I prefer keeping one patition for the root filesystem (/), one partition for user settings (/home) and one partition for user data (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which are simply symlinked to my home folder for ease of use, I cannot move any file to the trash in the root of these folders when I access them from my home folder or nautilus sidebar. This problem doesn't affect folders at all, nor any other files in subfolders, etc. So I was wondering if Ubuntu devs can leave out that particular patch when building this package for Ubuntu - if it doesn't cause more harm, which I doubt. Otherwise, I would appreciate if I could learn how to do it myself: how can I (as an end-user) compile the contents of "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on- overlayfs.patch"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245/+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 1638283] Re: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc
I can't find an edit button; the command I quoted above is incorrect. The corrected one is: rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dr1* libgl1-mesa-dri-lts-utopic-dbg: Installed: (none) Candidate: 10.3.2-0ubuntu1~trusty2 Version table: 10.3.2-0ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages libgl1-mesa-dri-lts-trusty-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-vivid: Installed: (none) Candidate: 10.5.9-2ubuntu1~trusty2 Version table: 10.5.9-2ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-quantal: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-utopic: Installed: (none) Candidate: 10.3.2-0ubuntu1~trusty2 Version table: 10.3.2-0ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages libgl1-mesa-dri: Installed: 10.1.3-0ubuntu0.6 Candidate: 10.1.3-0ubuntu0.6 Version table: *** 10.1.3-0ubuntu0.6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1.0-4ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-experimental-dbg: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-experimental: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-lts-saucy-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-raring: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-saucy: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-wily: Installed: (none) Candidate: 11.0.2-1ubuntu4~trusty1 Version table: 11.0.2-1ubuntu4~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-dbg: Installed: (none) Candidate: 10.1.3-0ubuntu0.6 Version table: 10.1.3-0ubuntu0.6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 10.1.0-4ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-raring-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-lts-quantal-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libgl1-mesa-dri-dev: Installed: (none) Candidate: (none) Version table: libgl1-mesa-dri-lts-xenial: Installed: (none) Candidate: 11.2.0-1ubuntu2~trusty1 Version table: 11.2.0-1ubuntu2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-wily-dbg: Installed: (none) Candidate: 11.0.2-1ubuntu4~trusty1 Version table: 11.0.2-1ubuntu4~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-trusty: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages libgl1-mesa-dri-lts-vivid-dbg: Installed: (none) Candidate: 10.5.9-2ubuntu1~trusty2 Version table: 10.5.9-2ubuntu1~trusty2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages rrogers@rrogers-desktop:~/tmp$ -- 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/1638283 Title: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1
[Touch-packages] [Bug 1638283] [NEW] libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/d
Public bug reported: This resulted from trying to install libgli from http://packages.ubuntu.com/trusty/i386/libgl1-mesa-dri/download Presumably, it's the wrong package? Following the instructions below: ubuntu-bug mesa failed reporting that it wasn't installed. Well that was because the installation was what failed. rrogers@rrogers-desktop:~/tmp$ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dri* N: Unable to locate package libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb N: Couldn't find any package by regex 'libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb' Ray ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Oct 31 17:16:07 2016 DpkgTerminalLog: Preparing to unpack .../libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb ... Unpacking libgl1-mesa-dri:i386 (10.1.3-0ubuntu0.6) over (10.1.0-4ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 InstallationDate: Installed on 2016-10-19 (12 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict trusty -- 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/1638283 Title: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1 -mesa-dri/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa- dri:i386 Status in mesa package in Ubuntu: New Bug description: This resulted from trying to install libgli from http://packages.ubuntu.com/trusty/i386/libgl1-mesa-dri/download Presumably, it's the wrong package? Following the instructions below: ubuntu-bug mesa failed reporting that it wasn't installed. Well that was because the installation was what failed. rrogers@rrogers-desktop:~/tmp$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 rrogers@rrogers-desktop:~/tmp$ apt-cache policy libgl1-mesa-dri* N: Unable to locate package libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb N: Couldn't find any package by regex 'libgl1-mesa-dri_10.1.0-4ubuntu5_i386.deb' Ray ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Oct 31 17:16:07 2016 DpkgTerminalLog: Preparing to unpack .../libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb ... Unpacking libgl1-mesa-dri:i386 (10.1.3-0ubuntu0.6) over (10.1.0-4ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_10.1.3-0ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.6 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different fro
[Touch-packages] [Bug 1638287] [NEW] When transferring focus to a ListView, the first listitem doesn't get a visual highlight until focus is given to the second listitem by down arrow
Public bug reported: Scenario: The webbrowser has an address bar which the user types into, then they press the down arrow to select a suggestion. What happened: 1) The app is started and the user focuses the addressbar 2) The user may type something then presses the down arrow 3) Focus is lost from the address bar and given to the listview, however there is no visual indicator 4) Press down arrow again 5) Notice that the 2nd listitem now has a visual highlight What I expected to happen: At step 3 for the first listitem to have a visual highlight Note that if you press the up arrow after navigating to the 2nd listitem, the 1st then does show an indicator. An example app of this issue can found here: https://code.launchpad.net/~ahayzen/+junk/keyboard-focus-issue-listitem ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1638287 Title: When transferring focus to a ListView, the first listitem doesn't get a visual highlight until focus is given to the second listitem by down arrow Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Scenario: The webbrowser has an address bar which the user types into, then they press the down arrow to select a suggestion. What happened: 1) The app is started and the user focuses the addressbar 2) The user may type something then presses the down arrow 3) Focus is lost from the address bar and given to the listview, however there is no visual indicator 4) Press down arrow again 5) Notice that the 2nd listitem now has a visual highlight What I expected to happen: At step 3 for the first listitem to have a visual highlight Note that if you press the up arrow after navigating to the 2nd listitem, the 1st then does show an indicator. An example app of this issue can found here: https://code.launchpad.net/~ahayzen/+junk/keyboard-focus-issue-listitem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1638287/+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 1297800] Re: During upgrades, new certificates will be added. Please choose those you trust.
Oh no, I'm stuck now. I got this dialogue, and pressed enter thinking it would select all certs. It seems to have selected NO certs to trust! Now I have a certs.pem file with only my own cert! >> You can check your current setting by doing: debconf-show ca- certificates Yes, I can confirm on my system, a-certificates/trust_new_crts: ask so how do I CHANGE that setting? How do I re-run certbot and get a complete certs file now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1297800 Title: During upgrades, new certificates will be added. Please choose those you trust. Status in ca-certificates package in Ubuntu: Expired Bug description: While upgrading ca-certificates from version 20111211 to 20130906ubuntu0.12.04.1 I got the following dialog: │ During upgrades, new certificates will be added. Please choose those you trust. │ │ │ │ New certificates to activate: │ │ │ │[ ] mozilla/Actalis_Authentication_Root_CA.crt │ │[ ] mozilla/Buypass_Class_2_Root_CA.crt │ │[ ] mozilla/Buypass_Class_3_Root_CA.crt │ │[ ] mozilla/CA_Disig_Root_R1.crt │ │[ ] mozilla/CA_Disig_Root_R2.crt │ │[ ] mozilla/China_Internet_Network_Information_Center_EV_Certificates_Root.crt │ │[ ] mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt │ │[ ] mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt│ │[ ] mozilla/EC-ACC.crt │ │[ ] mozilla/EE_Certification_Centre_Root_CA.crt │ │[ ] mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2011.crt │ │ │ │ │ │ │ Is it really reasonable to expect most users to know what to do with this and what the fallout is of making incorrect choices? I know my mom certainly would not have a clue about what to do with this. Hell, I am a software and network engineer and I don't know which of the above I should trust and what the fallout of not trusting some/all of them. And in reality, I need (way) more information that is pres
[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnutls28 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1638268] [NEW] certbot-auto claims parse error in apache config, but doesn't tell me which line
Public bug reported:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
...
The error was: PluginError(('There has been an error in parsing the file
(%s): %s', u'/etc/apache2/sites-available/mycrazydomainname.com',
u'Syntax error'),)
Ok, well, it would be super-helpful to know which line had the syntax error,
that's a file with hundreds of lines modrewrite rules, tls protocol specifier
lines, comments... What doesn't it like?
** Affects: ca-certificates (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1638268
Title:
certbot-auto claims parse error in apache config, but doesn't tell me
which line
Status in ca-certificates package in Ubuntu:
New
Bug description:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
...
The error was: PluginError(('There has been an error in parsing the
file (%s): %s', u'/etc/apache2/sites-available/mycrazydomainname.com',
u'Syntax error'),)
Ok, well, it would be super-helpful to know which line had the syntax error,
that's a file with hundreds of lines modrewrite rules, tls protocol specifier
lines, comments... What doesn't it like?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1638268/+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 1638270] [NEW] carkit bluetooth reboots ubuntu touch on Nexus4 when switched on/off a couple of times
Public bug reported: My bluetooth car hands free system reboots my Nexus4 phone when set to auto reconnect and then the ignition switch is turned on and off a couple of times. The carkit is recognized as "comf_comp_V12b". I am using the Aquarius image (though it previously occurs with the standard Nexus4 image). I am dual booting with Android. What other information can I give to help find the problem? Thanks bluetoothctl --version 5.41 uname -a Linux ubuntu-phablet 3.4.0-7-mako #1-Ubuntu SMP PREEMPT Thu Sep 3 15:30:20 UTC 2015 armv7l armv7l armv7l GNU/Linux hciconfig -a hci0: Type: Primary Bus: SPI BD Address: BC:F5:AC:47:69:30 ACL MTU: 1024:6 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:0 acl:0 sco:0 events:167 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'Nexus 4' Class: 0x5c Service Classes: Rendering, Capturing, Object Transfer, Telephony Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x0 LMP Version: 4.0 (0x6) Subversion: 0x7d3 Manufacturer: Qualcomm (29) bluetoothctl [NEW] Controller BC:F5:AC:47:69:30 Nexus 4 [default] [NEW] Device 00:16:73:21:50:AE comf_comp V12b unity8.log: [2016-11-01:12:21:50.790] qtmir.mir: SessionListener::stopping - this= SessionListener(0xb02d92fc) session= 0x10fde84 g_dbus_connection_real_closed: Remote peer vanished with error: Error receiving message: Connection reset by peer (g-io-error-quark, 44). Exiting. [2016-11-01:12:21:50.802] qtmir.mir: SessionListener::stopping - this= SessionListener(0xb02d92fc) session= 0x10e3d44 [2016-11-01:12:21:52.655] qtmir.mir: SessionListener::stopping - this= SessionListener(0xb02d92fc) session= 0xad03408c [2016-11-01:12:21:52.695] qtmir.screens: Destroying ScreenWindow 0x16d9f58 [2016-11-01:12:21:52.989] qtmir.surfaces: MirSurfaceManager::~MirSurfaceManager - this= qtmir::MirSurfaceManager(0x127f740, name = "qtmir::SurfaceManager") bluez-mpris-proxy.log.1: Bluetooth Adapter /org/bluez/hci0 removed org.bluez disappeared org.bluez appeared Bluetooth Adapter /org/bluez/hci0 found player core.ubuntu.media.Service at :1.42 found org.bluez appeared Bluetooth Adapter /org/bluez/hci0 found player core.ubuntu.media.Service at :1.34 found Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' qml: Page_QMLTYPE_44(0x12ce3f0, "systemSettingsPage")"System Settings": 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. BrightnessItem::BrightnessItem(const QVariantMap&, QObject*) ubuntu.widi.supported: 0 2016-11-01 13:23:59,230 - WARNING - file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/1.3/PageStack.qml:230:9: QML PageWrapper: Could not assign value: QVariant(QVariantMap, QMap()) to property: "pluginOptions" 2016-11-01 13:23:59,558 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:255:17: QML Label: Possible anchor loop detected on horizontal anchor. 2016-11-01 13:23:59,559 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:255:17: QML Label: Possible anchor loop detected on horizontal anchor. 2016-11-01 13:23:59,619 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:296:25: QML ActivityIndicator: file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActivityIndicatorStyle.qml:24 Invalid property assignment: "implicitHeight" is a read-only property application-legacy-ubuntu-system-settings-.log.1.gz: 2016-11-01 13:23:59,633 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/bluetooth/PageComponent.qml:251: TypeError: Property 'adapterName' of object Bluetooth(0x16171b0) is not a function 2016-11-01 13:23:59,821 - WARNING - Last frame took 44 ms to render. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1638270 Title: carkit bluetooth reboots ubuntu touch on Nexus4 when switched on/off a couple of times Status in bluez package in Ubuntu: New Bug description: My bluetooth car hands free system reboots my Nexus4 phone when set to auto reconnect and then the ignition switch is turned on and off a couple of times. The carkit is recognized as "comf_comp_V12b". I am using the Aquarius image (though it previously occurs with the standard Nexus4 image). I am dual booting with Android. What other information can I give to help find the problem? Thanks bluetoothctl --version 5.41 uname -a L
[Touch-packages] [Bug 1638271] [NEW] package python3 3.5.1-3 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 127
Public bug reported: Ao iniciar e logar no sistema ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 09:30:59 2016 ErrorMessage: sub-processo script pre-removal instalado retornou estado de saída de erro 127 InstallationDate: Installed on 2016-09-12 (49 days ago) InstallationMedia: SARDU RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 127 UpgradeStatus: Upgraded to xenial on 2016-11-01 (0 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1638271 Title: package python3 3.5.1-3 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 127 Status in python3-defaults package in Ubuntu: New Bug description: Ao iniciar e logar no sistema ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 09:30:59 2016 ErrorMessage: sub-processo script pre-removal instalado retornou estado de saída de erro 127 InstallationDate: Installed on 2016-09-12 (49 days ago) InstallationMedia: SARDU RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 127 UpgradeStatus: Upgraded to xenial on 2016-11-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1638271/+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
Good news: I have a had a small eureka moment that results my computer fully booted with graphics hardware fully accelerated. Bad news: it is still a workaround -- I still can't push power button and boot up normally. Here is the workaround sequence -- it requires another computer that can ssh in: 1. Computer in OFF state, press power. 2. At boot select screen, press `e` and edit kernel line by appending `modprobe.blacklist=radeon` 3. Press `F10` to boot 4. At login screen, click gear icon in upper right and select `Suspend` 5. After computer is in suspended state, press any key to awaken. 6. The display does not "reawaken" and still appears off. 7. From another computer, ssh into the first. 8. Issue `sudo service lightdm stop` 9. Issue `sudo modprobe radeon`. This should succeed! \o/ 10. Issue `sudo service lightdm start` Now the computer should be using correct drm drivers and have full resolution display. Furthermore, Suspend and Wake work successfully. I discovered this using ubuntu mainline kernel 4.8.0-rc5 but have verified it works with mainline 4.8.6 and also with 4.4.0-45. Unfortunately, I am also using the oibaf/graphics-drivers PPA with more recent mesa and libdrm drivers. I plan to test again after removing the PPA but it may take a while. If anyone with this problem is still watching, I'd be curious to hear if my workaround steps work for you. -- 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
[Touch-packages] [Bug 1637387] Re: Online accounts and snap login integration
** Changed in: ubuntuone-credentials (Ubuntu) Assignee: (unassigned) => Rodney Dawes (dobey) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1637387 Title: Online accounts and snap login integration Status in ubuntuone-credentials package in Ubuntu: In Progress Status in unity-scope-snappy package in Ubuntu: In Progress Bug description: Currently, one has to log in manually via "snap login" from the terminal in order to install snaps. We need this login to be integrated into online accounts such that logging into your ubuntu one account authenticates you with snapd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1637387/+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 1638167] Re: Thin grey lines on a white background look inconsistent and provide poor contrast
@vanvugt can you attached screenshots of what page you are referring to and narrow or wide mode? -- 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/1638167 Title: Thin grey lines on a white background look inconsistent and provide poor contrast Status in Canonical System Image: New Status in Ubuntu UX: New Status in webbrowser-app package in Ubuntu: Incomplete Bug description: The top area of the browser window is really just a series thin grey lines on a white background. This is poor design for a few reasons: 1. Grey and white don't contrast very well, especially thin strips of grey on white. 2. The grey outlines and symbols are inconsistent in thickness and colour: 2.1. The X icon is thinner than the + icon beside it, which is a different consistency again to the < button below it. 2.2. The rounded grey outline around the address is slighly thicker (blurred?) compared to the grey outline delineating the tabs. 3. Those vision impaired will have a very hard time. 4. Even those who are not vision impaired will be cognitively slowed by having to interpret the fine grey lines rather than areas of greater contrast. 5. It looks unprofessional. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638167/+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 1638256] [NEW] ifup fail when use MTU small than 68
Public bug reported: ifup failed when we set a static MTU small than 68, and when we change the static configuration and try to run ifdown and then ifup, the interface still with the old MTU and both of ifup and ifdown command fail. when we change the MTU manually by ip tool and then change it in the /etc/network/interfaces to be 1500 the interface get back to work. root:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety root:~# uname -r 4.8.0-26-generic scenario: set the MTU static to 67 root:~# ifdown ens2 root:~# ifup ens2 root:~# ifdown ens2 RTNETLINK answers: No such device root:~# ifup ens2 RTNETLINK answers: No buffer space available Failed to bring up ens2. root:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). auto ens2 iface ens2 inet static address 21.3.5.16 mtu 67 ## change MTU static to 1500 root:~# vim /etc/network/interfaces root:~# ifdown ens2 ifdown: interface ens2 not configured root:~# ifup ens2 RTNETLINK answers: No buffer space available Failed to bring up ens2. root:~# ip link set ens2 mtu 1500 root:~# ifup ens2 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1638256 Title: ifup fail when use MTU small than 68 Status in ifupdown package in Ubuntu: New Bug description: ifup failed when we set a static MTU small than 68, and when we change the static configuration and try to run ifdown and then ifup, the interface still with the old MTU and both of ifup and ifdown command fail. when we change the MTU manually by ip tool and then change it in the /etc/network/interfaces to be 1500 the interface get back to work. root:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety root:~# uname -r 4.8.0-26-generic scenario: set the MTU static to 67 root:~# ifdown ens2 root:~# ifup ens2 root:~# ifdown ens2 RTNETLINK answers: No such device root:~# ifup ens2 RTNETLINK answers: No buffer space available Failed to bring up ens2. root:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). auto ens2 iface ens2 inet static address 21.3.5.16 mtu 67 ## change MTU static to 1500 root:~# vim /etc/network/interfaces root:~# ifdown ens2 ifdown: interface ens2 not configured root:~# ifup ens2 RTNETLINK answers: No buffer space available Failed to bring up ens2. root:~# ip link set ens2 mtu 1500 root:~# ifup ens2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1638256/+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
