[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore
I can confirm that this works but my printer (WF-3250) is not in the list. Experimentation is required. Work Force produces 25 blank sheets for the test print but the WF printers seem to work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1536353 Title: [regression] Printer drivers install is broken as lsb package is not available anymore Status in cups-filters package in Ubuntu: Confirmed Status in epson-inkjet-printer-escpr package in Ubuntu: Fix Released Status in lsb package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Invalid Bug description: Starting with Xenial, lsb compatibility packages were dropped (besides lsb-release and lsb-base): lsb (9.20150826) unstable; urgency=low * Drop all the LSB compatibility packages besides lsb-release and lsb-base - Drop packages-availability checking in lsb-release - Truncate README.Debian to a minimum - Document this in lsb-base.NEWS.Debian * Change the versioning number to avoid any ambiguity; use joeyh's version.date, with version being Debian next stable's -- Didier Raboud Wed, 26 Aug 2015 12:00:00 +0200 The problem is that downloadable printer drivers (like the ones from Openprinting, but also from other available providers) that are suggested when installing a printer on Ubuntu depends on lsb, which is not available anymore: epson-inkjet-printer-201106w: Dépend: lsb (>=3.2) but it is not installable This triggers a regression where it is not possible to setup a printer this way (downloading a driver where no local driver is available) anymore. I see two possible solutions: - Add a proper replaces field to one of the remaining lsb-* packages, to hopefully fix missing lsb package (maybe it would be useful to also replace other compability packages that are not built anymore). - Re-introduce LSB compatibility packages, but that might be an overkill. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
I am trying to boot from a 16.04 live USB and it is hanging up when I say "Install Ubuntu" or "Try Ubuntu without installing". Will there be a new ISO released with the fix? -- 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/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop
Hi @Thomas, Yes, the user said he updated the device to 10.1 firs off all and then he noticed the GPS indicator behaviour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1573168 Title: [Frieza] Location service fails to start cleanly, entering restart loop Status in location-service package in Ubuntu: Confirmed Bug description: See http://makeagif.com/i/QlHXU7 for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1573168/+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 1565469] Re: GPS Denied without reason
Hi @Thomas, Thanks for opening that bug but this one also affects Frieza, screenshot attached sent by the user. ** Attachment added: "Ubuntu_Here.JPG" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565469/+attachment/4646103/+files/Ubuntu_Here.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1565469 Title: GPS Denied without reason Status in Canonical System Image: Incomplete Status in Oxide: New Status in location-service package in Ubuntu: Confirmed Bug description: You're using the GPS, and without reason, it stops. It doesn't return more positions. If you cancel the route and set a new one, a popup will tell you that the GPS is denied. I experienced this in OSM (From Alan) too. You know uNav is not freeze because you can drag the map. rc-proposed in Nexus 4 and BQ E4.5. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565469/+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 1572357] Re: filelight crashed with SIGSEGV in operator&() on closing lid
There have been several notorious bugs throghout Qt 5.4, 5.5 and 5.6 development cycles that cause these kinds of crashes when monitors change or "disappear". Most Qt 5.6 fixes have been backported to the Ubuntu's Qt 5.5 version in 16.04 LTS, so it would be useful to upgrade to 16.04 LTS and see if the behavior would be better now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1572357 Title: filelight crashed with SIGSEGV in operator&() on closing lid Status in qtbase-opensource-src package in Ubuntu: New Bug description: Closing the laptop lid (HP Probook 6470b) causes Qt-based programmes to crash. Similar bug reports: vlc - https://bugs.launchpad.net/bugs/1572313 texmaker - https://bugs.launchpad.net/bugs/1520826 ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: filelight 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 20 02:35:11 2016 ExecutablePath: /usr/bin/filelight InstallationDate: Installed on 2014-12-04 (502 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: filelight SegvAnalysis: Segfault happened at: 0x7fa5a81f4271 <_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+2961>: mov0x28(%rax),%rax PC (0x7fa5a81f4271) ok source "0x28(%rax)" (0x0028) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: filelight StacktraceTop: QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 Title: filelight crashed with SIGSEGV in QWidgetPrivate::drawWidget() UpgradeStatus: Upgraded to wily on 2016-02-05 (74 days ago) UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare scanner sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1572357/+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 1574045] Re: Can't install account-plugin-google; kaccounts-providers already provides /usr/share/accounts/providers/google.provider
** Changed in: kaccounts-providers (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1574045 Title: Can't install account-plugin-google; kaccounts-providers already provides /usr/share/accounts/providers/google.provider Status in Online Accounts: Account plugins: New Status in kaccounts-providers: Fix Released Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: Fix Released Bug description: I installed Kubuntu 16.04, later tried to install unity with `sudo apt-get install unity` which has a dependency (unity-scope-gdrive) requiring account-plugin-google and that wouldn't install since '/usr/share/accounts/providers/google.provider' is already provided by kaccounts-providers: $ sudo apt-get install unity Reading package lists... Done Building dependency tree Reading state information... Done unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: unity-scope-gdrive : Depends: account-plugin-google but it is not going to be installed $ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: account-plugin-google The following NEW packages will be installed: account-plugin-google 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 250 not fully installed or removed. Need to get 0 B/3,368 B of archives. After this operation, 29.7 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 214947 files and directories currently installed.) Preparing to unpack .../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ... Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack .../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ... Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 23 11:09:16 2016 InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) SourcePackage: account-plugins UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1574045/+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 1574443] [NEW] Hibernate option didn't come back
Public bug reported: Following the ubuntu wiki's instructions on how to enable hibernate in 16.04 resulted in no change. I created a file /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla with the following contents and rebooted my computer: [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.hibernate-multiple-sessions ResultActive=yes I have 5.8 GiB RAM, a 7.5GiB swap partition, my swap and ext4 root FS are LVM, and suspending to RAM does work. My computer could hibernate in 14.04. I ran "ubuntu-bug" in a terminal to get to here and this happened: "(python3:24337): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Connection refused 1462 cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory (kde-open5:25075): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Connection refused Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: lvmetad is not active yet, using direct activation during sysinit Ubuntu: clean, 343058/37339136 files, 11545047/149335040 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 24 23:49:25 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:227f] InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/Linux-Ubuntu_Root_LV ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227F dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd12/19/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227F:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Sun Apr 24 15:37:08 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13908 vendor SDC xserver.version: 2:1.18.3-1ubuntu2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug hibernate kubuntu xenial ** Package changed: xorg (Ubuntu) => ubuntu ** Description changed: Following the ubuntu wiki's instructions on how to enable hibernate in 16.04 resulted in no change. I created a file /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla with the following contents and rebooted my computer: [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate;org.freedesktop.login1.hibernate-multiple-sessions ResultActive=yes I have 5.8 GiB RAM, a 7.5GiB swap partition, my swap and ext4 root FS are LVM, and suspending to RAM does work. My computer could hibernate in
[Touch-packages] [Bug 1494555] Re: package ca-certificates 20150426ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
[Expired for ca-certificates (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ca-certificates (Ubuntu) Status: Incomplete => Expired -- 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/1494555 Title: package ca-certificates 20150426ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in ca-certificates package in Ubuntu: Expired Bug description: no ProblemType: Package DistroRelease: Ubuntu 15.10 Package: ca-certificates 20150426ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic i686 ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Fri Sep 11 00:06:56 2015 DuplicateSignature: package:ca-certificates:20150426ubuntu1:bloqué en boucle sur le traitement des actions différées (« triggers »), abandon ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2015-09-10 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150622) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: ca-certificates Title: package ca-certificates 20150426ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1494555/+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 1572061] Re: login sessions hangs in lxc
Hi, it's an intermittent error meaning it only occurs on rare occasions on the containters. I am rather sure it's pam or apparmor who is the issue here though. I received the login prompt during the incident but it hangs after password. Valid for both imaps and ssh protocols ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:3e:e9:2c:b6 inet addr:192.168.60.1 Bcast:192.168.60.255 Mask:255.255.255.0 inet6 addr: fe80::216:3eff:fee9:2cb6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:122486 errors:0 dropped:1809 overruns:0 frame:0 TX packets:45613 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:54922882 (54.9 MB) TX bytes:44895323 (44.8 MB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:425 errors:0 dropped:0 overruns:0 frame:0 TX packets:425 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:69808 (69.8 KB) TX bytes:69808 (69.8 KB) This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto br0 iface br0 inet static bridge_ports eno1 address 192.168.60.250 netmask 255.255.255.0 network 192.168.60.0 broadcast 192.168.60.255 gateway 192.168.60.252 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.60.4 dns-search bjornes.net -- 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/1572061 Title: login sessions hangs in lxc Status in lxc package in Ubuntu: Incomplete Bug description: login to lxc container hangs after login prompt. This happends to randomly lxc container while other containers on same host work as expected. Several protocols affected, ssh, dovecot & smtp for example. DNS config is ok. lxc-attach -n name works and I'm able to reach outside network, do resolving etc. if I do a lxc-stop and start the container works again. after a day or two samething occurs again to a random container on the same host. Could it be some kind of apparmor blocking ? HostOs Description:Ubuntu 16.04 LTS Release:16.04 network mode iface br0 inet static bridge_ports eno1 address x.x.x.x netmask 255.255.255.0 network x.x.x.x broadcast x.x.x.x gateway x.x.x.x dns-nameservers x.x.x.x dns-search domain.com lxc-os ubuntu xenial & debian jessie configured with static ip best regards Bjorn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1572061/+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 1542001] Re: Arrow key within a text field should not move to next component
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- 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/1542001 Title: Arrow key within a text field should not move to next component Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity8 package in Ubuntu RTM: Confirmed Bug description: using keyboard/arrow keys in the store: when user reaches the end of the final written word hit right arrow on keyboard and screen moves to the next section. Similarly When navigating text field with arrow keys, arrow keys cause pagination to occur I understand this may be the default in Qt but not the desired UX behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542001/+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 1473668] Re: [MX4] Photos are blurry and underexposed in low light conditions
I seem to have similar issues with the M10 tablet camera. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1473668 Title: [MX4] Photos are blurry and underexposed in low light conditions Status in Canonical System Image: In Progress Status in camera-app package in Ubuntu: In Progress Bug description: Hello, photos taken by MX4 are blurry and underexposed. First one is really annoying, I can't take even one good sharp photo and I don't know why. Second one is maybe because of bad synchronization time of flashing and taking shot; I think that because, when I record video with lamp, everything is great, problem is only for photos. I know that smartphones are not great for night photos, but I've used before worse and cheaper low-end phones with no-name lens and photos was significantly better. Please tell me, if you need more information. I will try to provide them. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473668/+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 1559304] Re: nvidia 361 drivers cause unresponsive machine
Same issue here on XPS 15-9530. I fixed it by switching to the nvidia 364 drivers from the graphics driver ppa: sudo apt-get purge nvidia-361 sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-364 A full system restart (twice for some reason, power down on the second try) was required to get everything working. -- 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/1559304 Title: nvidia 361 drivers cause unresponsive machine Status in xorg package in Ubuntu: Confirmed Bug description: Running Ubuntu Gnome 16.04 Beta1. Installing the proprietary drivers (either the tested or the updates) one results in: the splash screen goes away, revealing all the console output (with mostly green OKs) and the console log-in. This whole thing then flashes on and off and the system seems a little too upset to receive keyboard input. There is no mouse. The only way out is a hard reset, or if networking got started you can sometimes SSH in and issue a shutdown that way. The Nvidia driver is 361.28-0ubuntu1 It's a Dell xps-15 9550 with the UHD 4k screen. *-display description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:127 memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915_bpo latency=0 resources: irq:126 memory:db00-dbff memory:7000-7fff ioport:f000(size=64) To restore the system I have to boot to root console from the grub menu and then remove the nvidia stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:31:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 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.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xs
[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded
** Changed in: apt (Ubuntu) Assignee: (unassigned) => brad (bradmiller200593) -- 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/1558331 Title: message "The repository is insufficiently signed by key (weak digest)" is poorly worded Status in apt package in Ubuntu: Fix Released Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1572061] Re: login sessions hangs in lxc
Hi, when I simply do sudo lxc-create -t download -n kjell -B zfs -- -d debian -r jessie -a amd64 the resulting container works for me. I can apt-get install openssh- server and log in. However, your configuration file shows 'br0' is in use. Please show how br0 is configured on the host. Please show 'ifconfig -a' output in the container. -- 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/1572061 Title: login sessions hangs in lxc Status in lxc package in Ubuntu: Incomplete Bug description: login to lxc container hangs after login prompt. This happends to randomly lxc container while other containers on same host work as expected. Several protocols affected, ssh, dovecot & smtp for example. DNS config is ok. lxc-attach -n name works and I'm able to reach outside network, do resolving etc. if I do a lxc-stop and start the container works again. after a day or two samething occurs again to a random container on the same host. Could it be some kind of apparmor blocking ? HostOs Description:Ubuntu 16.04 LTS Release:16.04 network mode iface br0 inet static bridge_ports eno1 address x.x.x.x netmask 255.255.255.0 network x.x.x.x broadcast x.x.x.x gateway x.x.x.x dns-nameservers x.x.x.x dns-search domain.com lxc-os ubuntu xenial & debian jessie configured with static ip best regards Bjorn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1572061/+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 1574425] [NEW] Installing nvidia-361 leaves me unable to log in
Public bug reported: I have never successfully gotten the nvidia drivers to work properly. Before I used nvidia-304 because that seemed to be the only driver other than Nouveau that worked... the other nvidia drivers just give me a black screen With nvidia-361 I get a different outcome: I get to the login screen, and when I try to log in, it kicks me back out to the login screen. The only thing that I can do to resolve this is Ctrl-Alt-F1, log in, and try to undo anything that I just broke. So there are a number of things that look wrong in the logs, and I am willing to provide any necessary information, or try things. Version: Ubuntu 16.04 LTS apt-cache policy nvidia-361: Installed and Candidate: 361.42-0ubuntu2 Version table: *** 361.42-0ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Apr 24 22:16:46 2016 DistUpgraded: 2016-04-24 07:38:36,778 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.2.0-35-generic, x86_64: installed bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2015-09-28 (209 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=cda70297-42ac-43e6-aeb2-8ce418cd09cd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Sun Apr 24 22:09:57 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6125 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574425 Title: Installing nvidia-361 leaves me unable to log in Status in xorg package in Ubuntu: New Bug description: I have never successfully gotten the nvidia drivers to work properly. Before I used nvidia-304 because that seemed to be the only driver other than Nouveau that worked... the other nvidia drivers just give me a black screen With nvidia-361 I get a different outcome: I get to the login screen, and when I try to log in, it kicks me back out to the login screen. The only thing that I can do to resolve this is Ctrl-Alt-F1, log in, and try to undo anything that I just broke. So there are a number of things that look wrong in the logs, and I am willing to provide any necessary information, or try things. Version: Ubuntu 16.04 LTS apt-cache policy nvidia-361: Installed and Candidate: 361.42-0ubuntu2 Version table: *** 361.42-0ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/restricted amd64 Pac
[Touch-packages] [Bug 1569292] Re: Can't join to AD domain
** Package changed: realmd (Ubuntu) => packagekit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1569292 Title: Can't join to AD domain Status in realmd: New Status in packagekit package in Ubuntu: In Progress Bug description: realm -v join int.domainname.com --user login * Resolving: _ldap._tcp.int.domanname.com * Performing LDAP DSE lookup on: 192.168.xx.xx * Performing LDAP DSE lookup on: 192.168.xx.xx * Successfully discovered: int.domainname.com Password for login: * Unconditionally checking packages * Resolving required packages From here nothing happens. It doesn't go any further. journalctl -b realmd shows: [...] Apr 12 13:02:49 ls-mysql57 realmd[946]: Sending TCP Netlogon request Apr 12 13:02:49 ls-mysql57 realmd[946]: Searching for (objectClass=*) Apr 12 13:02:49 ls-mysql57 realmd[946]: Received TCP Netlogon response Apr 12 13:02:49 ls-mysql57 realmd[946]: * Successfully discovered: int.domainname.com Apr 12 13:02:49 ls-mysql57 realmd[946]: * Successfully discovered: int.domainame.com Apr 12 13:02:53 ls-mysql57 realmd[946]: Using 'r209.955' operation for method 'Join' invocation on 'org.freedesktop.realmd.KerberosMembership' interface Apr 12 13:02:53 ls-mysql57 realmd[946]: Registered cancellable for operation 'r209.955' Apr 12 13:02:53 ls-mysql57 realmd[946]: holding daemon: current-invocation Apr 12 13:02:53 ls-mysql57 realmd[946]: ** (realmd:946): CRITICAL **: realm_invocation_get_cancellable: assertion 'invocation != NULL' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: (realmd:946): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: * Unconditionally checking packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Unconditionally checking packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Resolving required packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Resolving required packages Apr 12 13:02:53 ls-mysql57 realmd[946]: realm_invocation_get_cancellable: assertion 'invocation != NULL' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: CreateTransaction call Apr 12 13:02:53 ls-mysql57 realmd[946]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: SetHints call Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve (262144, ['sssd-tools', 'sssd', 'libnss-sss', 'libpam-sss', 'adcli']) Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve completed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () It works in 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: realmd 0.16.2-2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 12 13:08:33 2016 SourcePackage: realmd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/realmd/+bug/1569292/+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 1569292] [NEW] Can't join to AD domain
You have been subscribed to a public bug: realm -v join int.domainname.com --user login * Resolving: _ldap._tcp.int.domanname.com * Performing LDAP DSE lookup on: 192.168.xx.xx * Performing LDAP DSE lookup on: 192.168.xx.xx * Successfully discovered: int.domainname.com Password for login: * Unconditionally checking packages * Resolving required packages >From here nothing happens. It doesn't go any further. journalctl -b realmd shows: [...] Apr 12 13:02:49 ls-mysql57 realmd[946]: Sending TCP Netlogon request Apr 12 13:02:49 ls-mysql57 realmd[946]: Searching for (objectClass=*) Apr 12 13:02:49 ls-mysql57 realmd[946]: Received TCP Netlogon response Apr 12 13:02:49 ls-mysql57 realmd[946]: * Successfully discovered: int.domainname.com Apr 12 13:02:49 ls-mysql57 realmd[946]: * Successfully discovered: int.domainame.com Apr 12 13:02:53 ls-mysql57 realmd[946]: Using 'r209.955' operation for method 'Join' invocation on 'org.freedesktop.realmd.KerberosMembership' interface Apr 12 13:02:53 ls-mysql57 realmd[946]: Registered cancellable for operation 'r209.955' Apr 12 13:02:53 ls-mysql57 realmd[946]: holding daemon: current-invocation Apr 12 13:02:53 ls-mysql57 realmd[946]: ** (realmd:946): CRITICAL **: realm_invocation_get_cancellable: assertion 'invocation != NULL' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: (realmd:946): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: * Unconditionally checking packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Unconditionally checking packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Resolving required packages Apr 12 13:02:53 ls-mysql57 realmd[946]: * Resolving required packages Apr 12 13:02:53 ls-mysql57 realmd[946]: realm_invocation_get_cancellable: assertion 'invocation != NULL' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: CreateTransaction call Apr 12 13:02:53 ls-mysql57 realmd[946]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: SetHints call Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve (262144, ['sssd-tools', 'sssd', 'libnss-sss', 'libpam-sss', 'adcli']) Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: call Resolve completed Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () Apr 12 13:02:53 ls-mysql57 realmd[946]: packages: signal: Changed () It works in 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: realmd 0.16.2-2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 12 13:08:33 2016 SourcePackage: realmd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: realmd Importance: Undecided Status: New ** Affects: packagekit (Ubuntu) Importance: Medium Assignee: Seyeong Kim (xtrusia) Status: In Progress ** Tags: amd64 apport-bug sts xenial -- Can't join to AD domain https://bugs.launchpad.net/bugs/1569292 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit 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
Re: [Touch-packages] [Bug 1571500] Re: serial-getty@.service does not configure baud rate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/24/2016 04:15 AM, Martin Pitt wrote: > My understanding is that this unit isn't meant to configure baud > rates but merely start getty on the requested one. In a world > before systemd there was nothing that changed them by default > either. Normally you set the baud rate on the kernel command line > (https://www.kernel.org/doc/Documentation/kernel-parameters.txt) > or just rely on the kernel driver's default. I'd say that at least a comment in that script is in order to let people reading it know that this setting has no effect unless they change the switch, or that they should use another, preferred mechanism for setting the baud rate instead. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJXHX22AAoJEBB5UWFcu6UWAdoH/Rrkwu1P+tQknxpSBUlEZaQR 2iuo9nmKANbVYZXVwSFq1UEb9aUWZ9GPoNQsh2eoBN9zOLojCM1c45e2wmKuOy7o ecKjwXvNZwILUbpgyS+qKdddWK3dPhY518B0DEdUXOkvlvmRUd+GbAibHQc8FJdu XJX3STOAa78wfPM7b4tqGr+ljnqeezPDdm0A5QXDCSc9SxGX5LOHE0JssHF8VDy3 sfKVbSFxeijDKVqA2vl7jG1YcTtv+A6YVpskWDE6vU0i1KatKyIy0K3M76C1uhub IdAlWYE4/QuadJqBbu7bnRMHFrkU2GNbmZSODK9fyHjBukT81PvARUNUBW/ioSY= =ZBAJ -END PGP SIGNATURE- -- 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/1571500 Title: serial-getty@.service does not configure baud rate Status in systemd package in Ubuntu: Invalid Bug description: I want to add a console port on a Ubuntu machine to be able to access it from a terminal server. This machine has no serial port but lots of USB ports (like most nowadays). I use a USB-to-serial adapter to have the ttyUSB0 up and listening. I copied /lib/systemd/system/serial-getty@.service to /lib/systemd/system/serial-getty@ttyUSB0.service and set the speed to 57600 +++ [Service] ExecStart=-/sbin/agetty --keep-baud 57600 %I $TERM +++ the service status shows the right speed +++ $ sudo systemctl status serial-getty@ttyUSB0.service ● serial-getty@ttyUSB0.service - Serial Getty on ttyUSB0 Loaded: loaded (/lib/systemd/system/serial-getty@ttyUSB0.service; enabled; vendor preset: enabled) Active: active (running) since 月 2016-04-18 14:07:30 JST; 58min ago Docs: man:agetty(8) man:systemd-getty-generator(8) http://0pointer.de/blog/projects/serial-console.html Main PID: 3017 (agetty) CGroup: /system.slice/system-serial\x2dgetty.slice/serial-getty@ttyUSB0.service └─3017 /sbin/agetty --keep-baud 57600 ttyUSB0 vt220 +++ Even so, I can't log in from the serial port at a speed other than 9600... With such settings I shouldn't even be able to get a right answer at 9600bps, only garbage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1571500/+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 1567389] Re: OpenVPN connections should allow username and password
If possible, show the generated config file and allow for custom edits. A way to verify the config might be crucial to some. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1567389 Title: OpenVPN connections should allow username and password Status in Canonical System Image: In Progress Status in Ubuntu UX: New Status in indicator-network package in Ubuntu: Incomplete Status in ubuntu-settings-components package in Ubuntu: In Progress Bug description: When configuring a VPN connection, there is no "username" field in which to enter one's username (an e-mail address, in my case). -- Reproduce: - Access the VPN settings (Apps Scope-->System Settings-->VPN-->Add Manual Configuration...). - Attempt to enter username. Result: - There is no field in which to enter one's username. Expectation: - To be able to specify a username for one's VPN connection, as per their respective VPN subscription. -- bq Aquaris E5 HD Ubuntu Edition: * OS build number: OTA-10 * Ubuntu Image part: 20160401.1 * Ubuntu build description: Ubuntu 15.04 - armhf (20160401-184657) * Device Image part: 20160329-a9bacdb * Device build description: VEGETA01A-S23A_BQ_L100EN_2011_160401 * Customization Image part: 20160324--36-54-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567389/+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 1574020] Re: Can't use networkmanager from lightdm
Exactly the same as the OP describes happens on my laptop, too. Clean install and all that. Except that before installing Xenial I was using Wily, and that I have Atheros wifi on a Toshiba laptop, which only confirms that "it has nothing to be with the chip", nor with the related modules/drivers. The most obvious guess is it is a permission-related issue, but I don't know where or how to fix it... What "user" handles logged off NetworkManager? O_o -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1574415] [NEW] [16.04] ssh : Bad protocol spec '1'
Public bug reported: After upgrade to 16.04 ssh client will not connect to any host, reporting /home/tj/.ssh/config line 109: Bad protocol spec '1'. The entry is: Host ups-01 Hostname 10.254.0.1 User hostmaster IdentityFile ~/.ssh/id_hostmaster IdentitiesOnly yes Protocol 1 If this were an entry in /etc/ssh/ssh_config and the user had no privileges to edit that file it could create a denial of service to the ssh client (if the user doesn't know how to over-ride the config). It would be helpful if the openssh-client postinst script were to grep the standard config files (including for users) and add a warning to the motd and syslog if any invalidated configuration statements are found. This will especially affect connections to embedded devices - in this case it is an ssh server on a management VLAN in one of several network- attached Uninterruptable Power Supplies that cannot be upgraded, and only support Protocol 1. According to the 16.04 Release Notes protocol 1 requires the openssh- client-ssh1 package with the ssh1 binary. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrade to 16.04 ssh client will not connect to any host, reporting /home/tj/.ssh/config line 109: Bad protocol spec '1'. The entry is: Host ups-01 Hostname 10.254.0.1 User hostmaster IdentityFile ~/.ssh/id_hostmaster IdentitiesOnly yes Protocol 1 - - If this were an entry in /etc/ssh/ssh_config and the user had no privileges to edit that file it could create a denial of service to the ssh client (if the user doesn't know how to over-ride the config). + If this were an entry in /etc/ssh/ssh_config and the user had no + privileges to edit that file it could create a denial of service to the + ssh client (if the user doesn't know how to over-ride the config). It would be helpful if the openssh-client postinst script were to grep the standard config files (including for users) and add a warning to the motd and syslog if any invalidated configuration statements are found. This will especially affect connections to embedded devices - in this - case it is an ssh server on a management VLAN in a network-attached - 32-port switched Cabinet Distribution Unit (CDU) that cannot be - upgraded, and only supports Protocol 1. + case it is an ssh server on a management VLAN in one of several network- + attached Uninterruptable Power Supplies that cannot be upgraded, and + only support Protocol 1. According to the 16.04 Release Notes protocol 1 requires the openssh- client-ssh1 package with the ssh1 binary. -- 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/1574415 Title: [16.04] ssh : Bad protocol spec '1' Status in openssh package in Ubuntu: New Bug description: After upgrade to 16.04 ssh client will not connect to any host, reporting /home/tj/.ssh/config line 109: Bad protocol spec '1'. The entry is: Host ups-01 Hostname 10.254.0.1 User hostmaster IdentityFile ~/.ssh/id_hostmaster IdentitiesOnly yes Protocol 1 If this were an entry in /etc/ssh/ssh_config and the user had no privileges to edit that file it could create a denial of service to the ssh client (if the user doesn't know how to over-ride the config). It would be helpful if the openssh-client postinst script were to grep the standard config files (including for users) and add a warning to the motd and syslog if any invalidated configuration statements are found. This will especially affect connections to embedded devices - in this case it is an ssh server on a management VLAN in one of several network-attached Uninterruptable Power Supplies that cannot be upgraded, and only support Protocol 1. According to the 16.04 Release Notes protocol 1 requires the openssh- client-ssh1 package with the ssh1 binary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1574415/+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 1574079] Re: USB audio device is not recognized after startup in 16.04
** Changed in: fwupd (Ubuntu) Status: Confirmed => Fix Released -- 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/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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 982499] Re: dconf-editor always prints warnings: "Unknown property on "
** Changed in: d-conf (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/982499 Title: dconf-editor always prints warnings: "Unknown property on " Status in d-conf package in Ubuntu: Confirmed Status in d-conf package in Debian: New Bug description: When I start dconf-editor, these four warnings are logged: > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown property on , extends > > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:330: Unknown property on , extends > > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag > > ** (dconf-editor:30049): WARNING **: dconf-schema.vala:401: Unknown tag It doesn't seem to affect operations so I'm setting the initial importance to "Low". This is reproducible for me every time I start dconf-editor from the command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/982499/+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 1526200] Re: Displayport screen goes back and forth in to Power save mode
Mikael Svensson, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags removed: bios-outdated-a10 ** Tags added: latest-bios-a10 ** Changed in: xorg (Ubuntu) Importance: Low => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1526200 Title: Displayport screen goes back and forth in to Power save mode Status in xorg package in Ubuntu: Incomplete Bug description: I have 3 screens including the laptop screen. The one connected to the displayport is going in to power save mode and back in random intervalls. The other screens don't care if the displayport one is going back and forth to power save mode like it does when you unplug the displayport cable. This started last week. I run the software updater last week. I have seen old workarounds that say you should press ctr + alt + F6 but it does not fix the problem. Turning of the hdmi screen in displays does not fix the problem. Unplugging hdmi screen does not fix the problem Unplugging and Plugin the displayport does not fix the problem. The short time the displayport screen is on it flickers and there is some static noise in a few pixels. I will attach more information if you request it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-55.74~14.04.1-generic 3.16.7-ckt19 Uname: Linux 3.16.0-55-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Dec 15 09:04:01 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060d] Subsystem: Dell Device [1028:060d] InstallationDate: Installed on 2014-10-06 (434 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-55-generic root=UUID=8528ac8e-4979-489a-8e14-6e430ed0c83b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/08/2015:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Dec 15 08:41:34 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41055 vendor DEL xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1526200/+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 1167281] Re: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile
** Also affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1167281 Title: "stdin: is not a tty" due to "mesg n" instead of "tty -s && mesg n" in .profile Status in base-files package in Ubuntu: New Status in xen-3.1 package in Ubuntu: Invalid Bug description: Upstreaming from https://bugzilla.wikimedia.org/show_bug.cgi?id=46913 : This used to happen at the start of every Puppet run, because of the line "mesg n" in /root/.profile. The shell provisioner is actually invoked to fix the problem by changing it to "tty -s && mesg n". This fixes the problem for every subsequent run. Still, I'd like to prevent it from appearing even once. Ubuntu could fix this by adding a check to .profile. Also see https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/201884 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1167281/+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 1545510] Re: Ubuntu 14.04 LTS black screen at login screen
I do not know how to do it. I'll have to install again to this recommended test? -- 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/1545510 Title: Ubuntu 14.04 LTS black screen at login screen Status in xorg package in Ubuntu: Expired Bug description: Ubuntu 14.04 LTS black screen at login screen a) I hoped that would normally enter the login screen, without displaying the black screen. b) When I boot Ubuntu, instead of appearing at the login screen, the screen goes black and I can not see anything. c) I turn on the notebook, select Ubuntu, Ubuntu enters but does not show the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 14 09:55:45 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1d72] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-02-12 (2 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ASUSTeK Computer Inc. N53Ta ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=514ec584-4a72-43dc-a56a-332d58a8d1f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53Ta.209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: N53Ta dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53Ta.209:bd12/10/2011:svnASUSTeKComputerInc.:pnN53Ta:pvr1.0:rvnASUSTeKComputerInc.:rnN53Ta:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53Ta dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Feb 14 09:44:01 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1545510/+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 1520564] Re: Xubuntu 15.10 low and poor sound on USB headset
Same problem using Xubuntu 16.04 LTS on VIrtualBox. -- 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/1520564 Title: Xubuntu 15.10 low and poor sound on USB headset Status in alsa-driver package in Ubuntu: Expired Bug description: Running Xubuntu 15.10 64 bits kernel 4.2.0-18 in Oracle Virtualbox 5.0.8. Using a Microsoft USB headset. Sound is very low and if I crank up the volume to the max is sort of audible but distorted and noisy. I have a 14.04 Xubuntu and a 15.04 Xubuntu instance on the same Virtualbox, using the same headset, and the sound is perfect. I also have an Arch instance with kernel 4.2.5-1 on the same Virtualbox and the sonud on that one is also good. This issue seems particular to Xubuntu 15.10. I posted this on the forums about 3-4 weeks ago in the hope that someone may have figured a way to fix this. No answer yet. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cat1274 F pulseaudio CurrentDesktop: XFCE Date: Fri Nov 27 07:27:39 2015 InstallationDate: Installed on 2015-10-31 (26 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1520564/+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 789309] Re: GLX Mac Radeon 9000
ernsteiswuerfel, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- 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/789309 Title: GLX Mac Radeon 9000 Status in xorg package in Ubuntu: Incomplete Bug description: Binary package hint: xorg No Opengl on ati radeon 9000 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-31.61-powerpc 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-powerpc ppc Architecture: powerpc Date: Mon May 30 06:01:51 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release powerpc (20100428) ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: xserver-xorg 1:7.5+5ubuntu1 libgl1-mesa-glx 7.7.1-1ubuntu3 libdrm2 2.4.18-1ubuntu3 xserver-xorg-video-ati 1:6.13.0-1ubuntu5 xserver-xorg-video-nouveau N/A SourcePackage: xorg system: distro: Ubuntu codename: lucid architecture: ppc kernel: 2.6.32-31-powerpc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/789309/+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 1457974] Re: Coloured triangles on screen
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1457974 Title: Coloured triangles on screen Status in xorg package in Ubuntu: Invalid Bug description: After upgrading from 14.10 to 15.04 the Xubuntu login screen is corrupted with triangles and colourful shades (see photo). --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device [1734:110a] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: FUJITSU SIEMENS AMILO Pa 2510 Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/08 dmi.bios.vendor: Phoenix Technologies LTD. dmi.bios.version: 1.08C dmi.board.name: F37 dmi.board.vendor: FUJITSU SIEMENS dmi.chassis.asset.tag: 000 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnPhoenixTechnologiesLTD.:bvr1.08C:bd01/18/08:svnFUJITSUSIEMENS:pnAMILOPa2510:pvr20:rvnFUJITSUSIEMENS:rnF37:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: AMILO Pa 2510 dmi.product.version: 20 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat May 23 22:34:02 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1457974/+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 1446053] Re: Font corruption some characters suddenly not rendered after login or after a period of usage
Robert Tuck, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1446053/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1446053 Title: Font corruption some characters suddenly not rendered after login or after a period of usage Status in xorg package in Ubuntu: Invalid Bug description: This has occurred multiple times on my machine (Dell Inspiron 13 7000 series laptop), it happens without warning. After which time suddenly application windows will fail to render certain characters making everything unreadable. In the past it has happened immediately after login, this time it happened after ~30 minutes usage from a cold boot. See attached screenshot. This doesn't happen for every window, chrome is generally ok, as are the unity launcher. The tools in the system tray and the power off menu are affected, as are nautilus, gedit, and application menus generally. Rolling over labels sometimes causes them to rener properly while the mouse is over them. Terminal is fine There is a workaround which is to change the font antialiasing settings with unity tweak tool, however this isn't a permanent fix - last time it was set to RGBA, so I changed it to Grayscale. This time it happened it was set to Grayscale and I set it to RGBA and it fixes it. I don't know enough to know whether this is a video driver issue, or a problem with gtk or what, so it's possible you may need to recategorise this defect. One other thing that may be useful info is that twiddling the antialiasing drop-down fixes and breaks the font rendering on the fly, when I see this problem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 20 06:39:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0675] InstallationDate: Installed on 2015-04-05 (14 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Inspiron 7348 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=/dev/mapper/LVM_VG1-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 08FH29 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/26/2014:svnDellInc.:pnInspiron7348:pvrA01:rvnDellInc.:rn08FH29:rvrA00:cvnDellInc.:ct10:cvrA01: dmi.product.name: Inspiron 7348 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Apr 20 05:54:03 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19528 vendor
[Touch-packages] [Bug 1518934] Re: Bluetooth page: Missing icon for watches
** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu) ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1518934 Title: Bluetooth page: Missing icon for watches Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Since Bluez5 landed, I can pair the Pebble watch in systemsettings. Only issue: the icon is missing :) http://i.imgur.com/XjnWloP.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1518934/+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 1573396] Re: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1550292 *** https://bugs.launchpad.net/bugs/1550292 ** This bug has been marked a duplicate of bug 1550292 package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- 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/1573396 Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in shared-mime-info package in Ubuntu: Confirmed Bug description: 1)Description:Ubuntu 16.04 LTS Release: 16.04 (actually I was upgrading from 15.10 to 16.04 when it appeared) 2)shared-mime-info: Installed: 1.5-2 Candidate: 1.5-2 Version table: *** 1.5-2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) My computer should update without any problems 4) The problem occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 07:05:38 2016 DuplicateSignature: package:shared-mime-info:1.3-1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-02-07 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1573396/+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 1490183] Re: Dragging a file/folder leaves original icon intact
eezacque, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ ? ** Tags added: wily -- 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/1490183 Title: Dragging a file/folder leaves original icon intact Status in xorg package in Ubuntu: Incomplete Bug description: When dragging a file or folder, the original icon remains in position while dragging, which suggests the file is being copied instead of moved. This original icon disappears when the drag ends. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.2.0-040200rc8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 29 20:31:55 2015 DistUpgraded: 2015-05-05 01:44:42,463 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.1.0-040100-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc6-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2014-10-24 (308 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-040200rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (116 days ago) dmi.bios.date: 06/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) 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.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Aug 29 20:28:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4121 vendor WAC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490183/+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 1518934] [NEW] Bluetooth page: Missing icon for watches
You have been subscribed to a public bug: Since Bluez5 landed, I can pair the Pebble watch in systemsettings. Only issue: the icon is missing :) http://i.imgur.com/XjnWloP.png ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Assignee: Matthieu James (tiheum) Status: Fix Released ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: Confirmed -- Bluetooth page: Missing icon for watches https://bugs.launchpad.net/bugs/1518934 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes 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 1574389] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** This bug is a duplicate of bug 1560797 *** https://bugs.launchpad.net/bugs/1560797 ** This bug has been marked a duplicate of bug 1560797 apt does not configure Pre-Depends: before depending package -- 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/1574389 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: I'm looking for a solution without rollback to 15.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 20:29:14 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574389/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up
Hello, Mathieu! Thank you for looking into this. Unfortunately, the bug is still present. I tested the same setups with the latest Xenial release (which natively includes your fix) and the behavior is the same: the DHCP server receives the request, OFFERs an IP address and ipconfig (from klibc-utils) simply doesn't acknowledge it. Right now, this is a show-stopper for PXE deployments. Please assist us with this issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Fix Released Status in klibc package in Debian: New Bug description: Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't acceptable as a system attempting to PXE boot may be using an alternate port for the network. I have found what looks to be a very similar bug filed for Debian, #584583, which also contains a patch for this issue (under Debian). I have no problems in PXE booting to various Windows, RedHat, Centos, or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot at present. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jun 6 20:22:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" - ** Note the above work-around wont work till - llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. - == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it - onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. + onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. ** Changed in: system76 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1574153] Re: 'Contacts' forces portrait position
I believe this is fixed in >= ota 10 > On Apr 23, 2016, at 11:53 PM, Bob Harvey <1574...@bugs.launchpad.net> wrote: > > Public bug reported: > > On the M10 tablet, running OTA9.5, opening 'contacts' forces you to > turn the device from Landscape to Portrait. > > I would expect the app to honour the device orientation. > > ** Affects: address-book-app (Ubuntu) > Importance: Undecided > Status: New > > -- > You received this bug notification because you are a member of Ubuntu > Apps bug tracking, which is subscribed to address-book-app in Ubuntu. > https://bugs.launchpad.net/bugs/1574153 > > Title: > 'Contacts' forces portrait position > > Status in address-book-app package in Ubuntu: > New > > Bug description: > On the M10 tablet, running OTA9.5, opening 'contacts' forces you to > turn the device from Landscape to Portrait. > > I would expect the app to honour the device orientation. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574153/+subscriptions > > -- > Mailing list: https://launchpad.net/~ubuntu-apps-bugs > Post to : ubuntu-apps-b...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-apps-bugs > More help : https://help.launchpad.net/ListHelp ** Changed in: address-book-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1574153 Title: 'Contacts' forces portrait position Status in address-book-app package in Ubuntu: Invalid Bug description: On the M10 tablet, running OTA9.5, opening 'contacts' forces you to turn the device from Landscape to Portrait. I would expect the app to honour the device orientation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574153/+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 1574079] Re: USB audio device is not recognized after startup in 16.04
** No longer affects: fwupd (Ubuntu) ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Confirmed -- 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/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Confirmed Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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 1572128] Re: $ ubuntu-bug xorg
Hi Tim, Please can you provide some information about what happened, whether the problem is reproducible etc. Please add this information to the Bug Description and also please change the Bug Title. Thanks ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1572128 Title: $ ubuntu-bug xorg Status in xorg package in Ubuntu: Incomplete Bug description: $ ubuntu-bug xorg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 19 05:52:03 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] InstallationDate: Installed on 2014-02-24 (785 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222) MachineType: System76, Inc. Ratel Ultra ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: JGIBX10J.86A.0601.2010..0048 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DH57JG dmi.board.vendor: Intel Corporation dmi.board.version: AAE70930-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrJGIBX10J.86A.0601.2010..0048:bd11/11/2010:svnSystem76,Inc.:pnRatelUltra:pvrratu1:rvnIntelCorporation:rnDH57JG:rvrAAE70930-304:cvn:ct2:cvr: dmi.product.name: Ratel Ultra dmi.product.version: ratu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Apr 2 20:57:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13 vendor ACR xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572128/+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 1574395] [NEW] Accessing quick settings while typing url causes url reset
Public bug reported: Mako R423 Steps to repeat: 1. Type something in browser address bar (dont press enter) 2. Access quick setting drop down or side launcher 3. Return to browser and see that typed characters are no longer. I.e. Have to retype Sometimes i am searching for something that i recevied in a notification. I start typing the search term or url in the address bar then go to quick settinga to double check, but this causes the addrsss bar to reset, and removed the partially typed url. ** 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/1574395 Title: Accessing quick settings while typing url causes url reset Status in webbrowser-app package in Ubuntu: New Bug description: Mako R423 Steps to repeat: 1. Type something in browser address bar (dont press enter) 2. Access quick setting drop down or side launcher 3. Return to browser and see that typed characters are no longer. I.e. Have to retype Sometimes i am searching for something that i recevied in a notification. I start typing the search term or url in the address bar then go to quick settinga to double check, but this causes the addrsss bar to reset, and removed the partially typed url. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1574395/+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 1574389] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1574389 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: I'm looking for a solution without rollback to 15.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 20:29:14 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574389/+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 1564156] Update Released
The verification of the Stable Release Update for llvm-toolchain-3.8 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
This bug was fixed in the package llvm-toolchain-3.8 - 1:3.8-2ubuntu3 --- llvm-toolchain-3.8 (1:3.8-2ubuntu3) xenial; urgency=medium * rules: Allow LLVM tests to fail on i386, we know dropping AVX512 breaks them. llvm-toolchain-3.8 (1:3.8-2ubuntu2) xenial; urgency=medium * drop-avx512-from-skylake.diff: Don't enable AVX512 on Skylake, as it's a server cpu feature and breaks llvmpipe on workstations. (LP: #1564156) -- Timo Aaltonen Thu, 21 Apr 2016 08:16:04 +0300 ** Changed in: llvm-toolchain-3.8 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1574389] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
** Tags removed: need-duplicate-check -- 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/1574389 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: I'm looking for a solution without rollback to 15.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 20:29:14 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574389/+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 1574389] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Public bug reported: I'm looking for a solution without rollback to 15.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 20:29:14 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package 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/1574389 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: I'm looking for a solution without rollback to 15.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 20:29:14 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574389/+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 1560181] Re: [USB-Audio - VX2, playback] Pulseaudio fails to detect card
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1560181 Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an external sound card--A Topping VX2. When plugged in to USB, the device seems to keep Ubuntu from booting properly. It hangs until I remove the USB cord from the device, then Ubuntu boots normally. Once booted, the device can be recognized by Ubuntu, but then seems to nuke PulseAudio, leaving no devices in the Sound Settings. Yes, I have checked this behavior against two Topping VX2 devices, which have identical results. Yes, I have switched out USB cords to test for a bad cord. The VX2 uses Via Technologies VT 1620A USB audio controller. I suspect that this may be the issue. Is this currently supported? Is there a working driver for this? THanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 21 15:27:54 2016 InstallationDate: Installed on 2016-03-15 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio Symptom: audio Symptom_Card: USB-Audio - C-Media USB Audio Device Title: [USB-Audio - VX2, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-A 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.:bvr2101:bd11/26/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1560181/+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 1250875] Re: Lightdm sometimes fails to auto login
I've just seen this on Ubuntu 16.04 on an EeePC and in one start up configuration it always happens and autologin always fails. It seems to be highly dependent on what else is happening as lightdm is starting. When the problem occurs looking at the lightdm log shows that it is trying to log using a normal PAM lightdm session rather than an autologin PAM session. This leads to failure because the account being authenticated has a password and no password is being passed to PAM and the user is intentionally absent from the nopasswdlogin group. Attaching /etc/lightdm/lilghtdm.conf, /var/log/lightdm/lightdm.log and PAM's /var/log/auth.log . ** Attachment added: "lightdm.conf" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645855/+files/lightdm.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+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 1572351] Re: Should remove deletion from mounted-tmp
If mountall is no longer needed, shouldn't it be removed on upgrade? Or perhaps it should Conflict with systemd so that it is removed after migration? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1572351 Title: Should remove deletion from mounted-tmp Status in mountall package in Ubuntu: New Bug description: Now that systemd is cleaning /tmp (via /usr/lib/tmpfiles.d/tmp.conf), we should remove all the /tmp cleanup code from /etc/init/mounted- tmp.conf. Leaving it in is redundant and confusing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mountall 2.54ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .run.mount.utab: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 19 20:20:33 2016 InstallationDate: Installed on 2012-10-07 (1290 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=/dev/mapper/internal-root_crypt ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: Upgraded to xenial on 2016-04-09 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1572351/+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 1250875] Re: Lightdm sometimes fails to auto login
** Attachment added: "auth.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645857/+files/auth.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+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 1250875] Re: Lightdm sometimes fails to auto login
** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+attachment/4645856/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+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 1512129] Re: Headphones not detected at startup
Underlying issue appears to be fixed now. No regression on upgrade to Xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1512129 Title: Headphones not detected at startup Status in alsa-utils package in Ubuntu: New Status in kubuntu-meta package in Ubuntu: New Bug description: The headphones are not detected if they are plugged in before the system starts up. To get sound out of my headphones, I need to unplug the headphones and plug them back in again. After this, sound is sent to the headphones. Reproducible: always Steps to reproduce: 1. Plug in headphones 2. Switch on computer, log into Kubuntu 3. Attempt to play sound in any application, no sound produced. 4. Unplug and replug headphones 5. Sound works Expected behaviour: At step 3, sound should be output through the headphones. The problem seems to be in alsamixer: when starting Kubuntu the headphone volume is set to zero and the headphones are muted. Re- plugging the headphones will unmute the headphones in alsamixer and set to an audible volume. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Nov 1 19:43:09 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-31 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1512129/+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 1574347] Re: WiFi network list disappears from network manager applet
also for me if you go into system settings, and go into network I can you still see the wifi network list. -- 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/1574347 Title: WiFi network list disappears from network manager applet Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347/+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 1574371] [NEW] Launching pre-install Amazon app on Ubuntu 16.04 causes the webbrowser-app to start but it flashes uncontrollably until quit
Public bug reported: I have recently found that when launching the pre-installed Amazon app on Ubuntu 16.04 that it launches the webbrowser-app which flashes uncontrollably until quit. When running it in Terminal with "unity- webapps-runner --amazon --app-id=ubuntu-amazon-default" the first output was: ** (unity-webapps-runner:2246): WARNING **: Could not get a proper accuracy from Geoclue (NONE) ** Message: Launching webapp container for url 'http://www.amazon.com/?tag=u1webapp-20' and app_id 'ubuntu-amazon-default (command line 'webapp-container --app-id='ubuntu-amazon-default' --webapp --enable-back-forward http://www.amazon.com/?tag=u1webapp-20') After which it went back to '$', but then started giving more output and did so until I quit the browser which flashed uncontrollably and could not be made to do anything or display any pages: OpenGL Warning: glXCreatePbuffer not implemented by Chromium Invalid webapp webapp definition: homepage not found or fails predicate isString Could not open manifest file: "/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json" qml: Loading webview on /home/tester/.local/share/ubuntu-amazon-default Invalid webapp webapp definition: homepage not found or fails predicate isString Could not open manifest file: "/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json" QQmlExpression: Expression file:///usr/share/webbrowser-app/webcontainer/WebApp.qml:272:25 depends on non-NOTIFYable properties: unity::action::qml::ActionManager::globalContext qml: Loaded 5 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-mobile.js qml: Start browsing file:///usr/share/webbrowser-app/webcontainer/ContentPickerDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webcontainer/ContentDownloadDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/Downloader.qml:22:1: module "Ubuntu.DownloadManager" is not installed file:///usr/share/webbrowser-app/Downloader.qml:23:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/Downloader.qml:22:1: module "Ubuntu.DownloadManager" is not installed file:///usr/share/webbrowser-app/Downloader.qml:23:1: module "Ubuntu.Content" is not installed qml: Loaded 5 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js [0424/203404:ERROR:layer_tree_host_impl.cc(2263)] Forcing zero-copy tile initialization as worker context is missing [0424/203404:ERROR:buffer_manager.cc(361)] [.CommandBufferContext.Context-For-Testing-0x558d4431d000]GL ERROR :GL_INVALID_ENUM : glBufferData: <- error from previous GL command [0424/203408:ERROR:texture_manager.cc(2278)] [.CommandBufferContext.RenderCompositor-0x369c907eec00]GL ERROR :GL_INVALID_ENUM : glTexImage2D: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_ENUM : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2113)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::ctor: was unhandled [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command [0424/203408:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x369c907ee180]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinde
[Touch-packages] [Bug 1574364] Re: Mouse disappears after suspend and unsuspend
*** This bug is a duplicate of bug 1568604 *** https://bugs.launchpad.net/bugs/1568604 ** This bug has been marked a duplicate of bug 1568604 Mouse cursor lost when unlocking with Intel graphics -- 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/1574364 Title: Mouse disappears after suspend and unsuspend Status in xorg package in Ubuntu: New Bug description: When the computer is suspended (from within xfce), and then woken up again, the mouse cursor disappears. CTRL+ALT+F1 CTRL+ALT+F2 makes it appear again. The machine has not been installed from scratch, but rather updated from 15.10. This doesn't seem to be hardware-specific; I have the same issue both on a rather recent desktop box and an eight year old notebook. Both have Intel graphics, though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 24 21:08:30 2016 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: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574364/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
HI! Would this bug cause my system to crash when using an external monitor via HDMI? I can attach and use the monitor no problem UNTIL I suspend and/or detach and reattach the monitor, in which case the whole system crashes i.e.) screen freezes, keyboard, touchpad and network are all unresponsive and I have no choice but to hard boot. I've installed all the toolchain debs found here: http://koti.kapsi.fi/~tjaalton/skl/build2 and my system still crashes with the external monitor (as described above). Some system specs: Asus Zenbook UX305CA -EHM1 CPU: Intel® Core™ m3-6Y30 CPU @ 0.90GHz × 4 GPU: Intel® HD Graphics 515 (Skylake GT2) Thanks! -- 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/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Committed Status in System76: Fix Committed Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note the above work-around wont work till llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 924224] Re: LightDM package fails to remove if lightdm user is in use
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/924224 Title: LightDM package fails to remove if lightdm user is in use Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Vivid: Won't Fix Status in lightdm source package in Wily: Fix Released Bug description: Ubuntu 11.04. apt-get uninstall lightdm ot an 'Error 8', then the crash report appeared. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 2.6.38-13.54-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 AptOrdering: lightdm: Purge Architecture: i386 Date: Tue Jan 31 08:40:27 2012 ErrorMessage: el subproceso instalado el script post-removal devolvió el código de salida de error 1 InstallationMedia: Macbuntu-iso - Release i386 SourcePackage: lightdm Title: package lightdm (not installed) failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/924224/+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 1568485] [isc-dhcp/trusty] possible regression found
As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of isc-dhcp from trusty-proposed was performed and bug 1574226 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and add the tag "bot-stop-nagging" to bug 1574226 (not this bug). Thanks! ** Tags added: verification-failed -- 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/1568485 Title: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Wily: Confirmed Bug description: Get this logged on a fully upgraded 64 desktop (proposed archive enabled) kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log" pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 12:23:56 2016 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1568485/+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 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes
In reply to Simon Fels (sorry for the long delay - I put the keyboards aside to focus on other things). The "Apple Wireless Keyboard" are model A1016 105-key, including a numeric keypad. Issue still affects 16.04. >From 16.04 attaching a bluetoothd debug log whilst trying to pair with the A1016. It reflects using tj@T300CHI:~$ bluetoothctl [NEW] Controller 34:02:86:FC:AD:59 T300CHI [default] [NEW] Device 00:0A:95:44:37:11 Apple Wireless Keyboard [NEW] Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 34:02:86:FC:AD:59 Discovering: yes [NEW] Device 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [CHG] Device 00:0A:95:44:37:11 LegacyPairing: yes [CHG] Device 00:0A:95:44:37:11 RSSI: -43 [bluetooth]# pair 00:0A:95:44:37:11 Attempting to pair with 00:0A:95:44:37:11 [agent] PIN code: 412054 Failed to pair: org.bluez.Error.ConnectionAttemptFailed [CHG] Device 00:1F:3A:E0:0A:AF RSSI: -66 Notice that the "[agent] PIN code: 412054" message doesn't appear until I press the A1016 keyboard's Enter key once. I then type the prompted PIN followed by Enter on the A1016 keyboard. Sometimes I get three prompts to enter PIN codes (each PIN different) before it fails. ** Attachment added: "bluetoothd debug log trying to pair A1016" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490347/+attachment/4645819/+files/bluetoothd-debug-A1016-pair-attempt.log ** Summary changed: - [Regresision] 15:10 - Cannot pair with devices using PIN codes + [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes -- 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/1490347 Title: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes Status in Bluez Utilities: New Status in bluez package in Ubuntu: Triaged Status in bluez source package in Wily: Triaged Bug description: Bluez 5.3 does not have support for pairing with devices (such as keyboards) that use a PIN code for pairing. A mouse pairs correctly. From my research it seems as if the ChromeOS project developed patches to fix this and they are supposed to have been included in Bluez 5.4 (that statement dated April 2013) but I've not yet identified them. "The agent's implementation in bt_console/bluetoothctl upstream is incomplete, missing some functions like DisplayPincode." https://code.google.com/p/chromium/issues/detail?id=222661 Along with the loss of Headset profiles meaning VoIP applications can no longer use HSP/HFP profiles (requiring functionality yet to land in Ofono) this cripples the use of Bluetooth for much else than A2DP or mouse input. Attempting to pair with, for example, an Apple Wireless Keyboard that pairs and works correctly with 14.04 LTS, fails totally on 15.10. The mouse shown below is already paired, connected, and working. $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48 [bluetooth]# pair 00:0A:95:4B:BD:C2 Attempting to pair with 00:0A:95:4B:BD:C2 >>> at this point nothing is happening >>> so I press Enter on the keyboard and... [agent] PIN code: 791166 >>> I type 791166 Enter and ... [agent] PIN code: 237744 >>> I type 237744 Enter and... [agent] PIN code: 358866 >>> I type 358866 Enter and... Request PIN code [agent] Enter PIN code: 1234 >>> I type 1234 Enter on the keyboard and 1234 at the prompt... Failed to pair: org.bluez.Error.AuthenticationFailed This cycle repeats in various permuations. Sometimes the final "Request PIN code" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+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 1574004] Re: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- 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/1574004 Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: In Progress Bug description: upgrade to 16.04 failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 14:34:45 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (281 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4174P5G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET57WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4174P5G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4174P5G dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574004/+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 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop
I have the M10 tablet on OTA10.1. The Location indicator is blinking on and off, making the mail indicator shift from left to right. If I pull down the 'notifications curtain' for the location, the slide switch and legend for 'location detection' are blinking too. I installed the SensorStatus app and that shows no values at all for GPS results. There does not appear to be any way to display satellite lock, constalation, or ephemeris age. Here Maps reports 'Can't find your location' ; uNav says 'GPS denied'; those seem to be different to what Llamas.JM reported in comment 8. Much more like Sergi reports in comemnt 5,7 The tablet was delivered with OTA9.5 and location services worked before I applied the update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1573168 Title: [Frieza] Location service fails to start cleanly, entering restart loop Status in location-service package in Ubuntu: Confirmed Bug description: See http://makeagif.com/i/QlHXU7 for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1573168/+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 1574364] [NEW] Mouse disappears after suspend and unsuspend
Public bug reported: When the computer is suspended (from within xfce), and then woken up again, the mouse cursor disappears. CTRL+ALT+F1 CTRL+ALT+F2 makes it appear again. The machine has not been installed from scratch, but rather updated from 15.10. This doesn't seem to be hardware-specific; I have the same issue both on a rather recent desktop box and an eight year old notebook. Both have Intel graphics, though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 24 21:08:30 2016 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: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: When the computer is suspended (from within xfce), and then woken up again, the mouse cursor disappears. CTRL+ALT+F1 CTRL+ALT+F2 makes it appear again. The machine has not been installed from scratch, but rather updated from 15.10. + + This doesn't seem to be hardware-specific; I have the same issue both on + a rather recent desktop box and an eight year old notebook. Both have + Intel graphics, though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 24 21:08:30 2016 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. + 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: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) -- 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/1574364 Title: Mouse disappears after suspend and unsuspend Status in xorg package in Ubuntu: New Bug description: When the computer is suspended (from within xfce), and then woken up again, the mouse cursor disappears. CTRL+ALT+F1 CTRL+ALT+F2 makes it appear again. The machine has not been installed from scratch, but rather updated from 15.10. This doesn't seem to be hardware-specific; I have the same issue both on a rather recent desktop box and an eight year old notebook. Both have Intel graphics, though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 24 21:08:30 2016 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: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574364/+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 1574004] Re: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
We don't really expect /var/log/udev to be a directory (nothing in Ubuntu creates it like that), but we should of course not fail the upgrade due to that. I committed a simple fix to http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu- xenial&id=d133b04 . This is only relevant for xenial, this transitional code will be dropped entirely in yakkety. ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1574004 Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: In Progress Bug description: upgrade to 16.04 failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 14:34:45 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (281 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4174P5G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET57WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4174P5G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4174P5G dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574004/+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 1574118] Re: M10 tablet has phone app
It has a mesasging app too, had to remove that as well. Ought not to be installed when I get it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1574118 Title: M10 tablet has phone app Status in address-book-app package in Ubuntu: New Bug description: M10 tablet, delivered with 15.04 OTA9.5 Fireza, has a phone app.you can even dial a number, but it complains of having 'no network'. Hardly surprising. It has no sim, and no cellphone radio. The phone appp needs to be uninstalled when you can't use it. Sloppy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574118/+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 1574001] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** This bug is a duplicate of bug 1560797 *** https://bugs.launchpad.net/bugs/1560797 ** This bug has been marked a duplicate of bug 1560797 apt does not configure Pre-Depends: before depending package -- 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/1574001 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: Very, very messy upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sat Apr 23 00:35:33 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-09-25 (941 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574001/+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 1574004] Re: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1574004 Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: In Progress Bug description: upgrade to 16.04 failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 14:34:45 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-16 (281 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 4174P5G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET57WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4174P5G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4174P5G dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574004/+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 1574295] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** This bug is a duplicate of bug 1560797 *** https://bugs.launchpad.net/bugs/1560797 ** This bug has been marked a duplicate of bug 1560797 apt does not configure Pre-Depends: before depending package -- 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/1574295 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: New Bug description: Upgrading from Ubuntu 15.10 to 16.04LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 21:38:29 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2015-11-11 (164 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574295/+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 1574249] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** This bug is a duplicate of bug 1560797 *** https://bugs.launchpad.net/bugs/1560797 ** This bug has been marked a duplicate of bug 1560797 apt does not configure Pre-Depends: before depending package -- 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/1574249 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: systemd was not installed at upgrade to 16.04 xenial xerus, neither other package depending of it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 12:13:32 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2016-02-16 (67 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574249/+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 1574247] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
*** This bug is a duplicate of bug 1560797 *** https://bugs.launchpad.net/bugs/1560797 ** This bug is no longer a duplicate of bug 1574001 package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv ** This bug has been marked a duplicate of bug 1560797 apt does not configure Pre-Depends: before depending package -- 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/1574247 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: New Bug description: when ever system start system failure occur ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sun Apr 24 16:19:49 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2016-01-13 (101 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574247/+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 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default
In case anyone's interested in knowing why setting net/ipv6/conf/all/use_tempaddr=2 no longer changes the value of pre- existing interfaces (thus ensuring privacy extensions are disabled by default for physical interfaces configured through /etc/network/interfaces), it's because http://kernel.ubuntu.com/git/ubuntu/ubuntu- trusty.git/commit/?id=c999e7dff4570e4c28a0953e7189c0c31343ce62 was dropped from the Ubuntu kernel packages starting with Utopic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1068756 Title: IPv6 Privacy Extensions enabled on Ubuntu Server by default Status in cloud-init package in Ubuntu: Triaged Status in procps package in Ubuntu: Confirmed Bug description: Ubuntu 12.04 LTS and Ubuntu 12.10 server images both ship with the IPv6 Privacy Extensions enabled (as defined in RFC 4941[0]). Not only are they enabled, but these addresses are preferred over addresses obtained using SLAAC. While is may be considered a reasonable default on an image being used on a personal computer, it's not something that is sane to have enabled by default in a server environment. Having this extension enabled can wreak havoc if you are expecting a specific IPv6 address when you know the MAC addresses of your systems beforehand. The file that is responsible for causing this to be defaulted to enabled is: "/etc/sysctl.d/10-ipv6-privacy.conf". This file appears to be part of the procps package (as per the output of 'dpkg -S') and contains the following: # IPv6 Privacy Extensions (RFC 4941) # --- # IPv6 typically uses a device's MAC address when choosing an IPv6 address # to use in autoconfiguration. Privacy extensions allow using a randomly # generated IPv6 address, which increases privacy. # # Acceptable values: #0 - don’t use privacy extensions. #1 - generate privacy addresses #2 - prefer privacy addresses and use them over the normal addresses. net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 In short, IPv6 privacy extensions should not be enabled by default when deploying an Ubuntu server image. In a server environment you should be able to reliably determine your IPv6 address based on the MAC address of the system. Thank you for taking the time to look in to this as well as consider changing the default behavior of Ubuntu server. -Tim Heckman [0] http://tools.ietf.org/html/rfc4941 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+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 1050715] Re: package libgweather-common 3.4.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
** Changed in: libgweather (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1050715 Title: package libgweather-common 3.4.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured Status in libgweather package in Ubuntu: Incomplete Bug description: --- ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libgweather-common 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Fri Sep 14 03:25:11 2012 ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) PackageArchitecture: all SourcePackage: libgweather Title: package libgweather-common 3.4.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to precise on 2012-09-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1050715/+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 1574347] Re: WiFi network list disappears from network manager applet
Easier workaround: sudo systemctl restart network-manager.service -- 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/1574347 Title: WiFi network list disappears from network manager applet Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347/+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 1574249] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1574249 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: systemd was not installed at upgrade to 16.04 xenial xerus, neither other package depending of it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 12:13:32 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2016-02-16 (67 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574249/+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 1492088] Re: juju bootstrap fails inside a wily container
** Changed in: juju-core
Status: Triaged => Fix Released
--
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/1492088
Title:
juju bootstrap fails inside a wily container
Status in juju-core:
Fix Released
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Running juju 1.24.5 and attempting to do a local bootstrap inside a
wily container fails with the following:
[DEBUG: 09-03 20:49:56, container.py:139] Error with command: [Output]
'2015-09-03 20:49:35 INFO juju.cmd supercommand.go:37 running juju
[1.24.5-wily-amd64 gc]
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:109 Made
dir /home/ubuntu/.cloud-install/juju/environments
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
checking state port
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:245
checking API port
2015-09-03 20:49:35 INFO juju.provider.local environprovider.go:38
opening environment "local"
2015-09-03 20:49:35 DEBUG juju.container.kvm kvm.go:71 kvm-ok output:
INFO: /dev/kvm exists
KVM acceleration can be used
2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
"10.0.6.1" as address for "lxcbr0"
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:308
writing jenv file
2015-09-03 20:49:35 DEBUG juju.environs.configstore disk.go:432
writing jenv file to /home/ubuntu/.cloud-
install/juju/environments/local.jenv
2015-09-03 20:49:35 INFO juju.network network.go:194 setting prefer-
ipv6 to false
2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Bootstrapping environment
"local"
2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:98
environment "local" supports service/machine networks: false
2015-09-03 20:49:35 DEBUG juju.environs.bootstrap bootstrap.go:100
network management by juju enabled: true
2015-09-03 20:49:35 DEBUG juju.provider.local environ.go:325 found
"10.0.6.1" as address for "lxcbr0"
2015-09-03 20:49:35 INFO juju.cmd cmd.go:113 Starting new instance for
initial state server
2015-09-03 20:49:35 INFO juju.environs.bootstrap bootstrap.go:184
newest version: 1.24.5.1
2015-09-03 20:49:36 INFO juju.environs.bootstrap bootstrap.go:212
picked bootstrap tools version: 1.24.5.1
2015-09-03 20:49:36 INFO juju.cmd cmd.go:113 Building tools to upload
(1.24.5.1-wily-amd64)
2015-09-03 20:49:36 DEBUG juju.environs.sync sync.go:304 Building
tools
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:122 looking
for: juju
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:161 checking:
/usr/bin/jujud
2015-09-03 20:49:36 INFO juju.environs.tools build.go:167 found
existing jujud
2015-09-03 20:49:36 INFO juju.environs.tools build.go:177 target: /tmp
/juju-tools782467678/jujud
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:232 forcing
version to 1.24.5.1
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
entry: &tar.Header{Name:"FORCE-VERSION", Mode:436, Uid:0, Gid:0,
Size:8, ModTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
AccessTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)},
ChangeTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}
2015-09-03 20:49:36 DEBUG juju.environs.tools build.go:38 adding
entry: &tar.Header{Name:"jujud", Mode:493, Uid:0, Gid:0,
Size:67623560, ModTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Typeflag:0x30, Linkname:"",
Uname:"ubuntu", Gname:"ubuntu", Devmajor:0, Devminor:0,
AccessTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)},
ChangeTime:time.Time{sec:63576910176, nsec:90190527,
loc:(*time.Location)(0x2c9b140)}, Xattrs:map[string]string(nil)}
2015-09-03 20:49:42 INFO juju.environs.sync sync.go:323 built tools
1.24.5.1-wily-amd64 (13769kB)
2015-09-03 20:49:42 INFO juju.cmd cmd.go:113 Installing Juju agent on
bootstrap instance
2015-09-03 20:49:42 DEBUG juju.cloudconfig.instancecfg
instancecfg.go:521 Setting numa ctl preference to false
2015-09-03 20:49:42 INFO juju.provider.local environ.go:156 local
provider; disabling refreshing OS updates.
2015-09-03 20:49:42 INFO juju.provider.local environ.go:162 local
provider; disabling OS upgrades.
Logging to /home/ubuntu/.cloud-install/juju/local/cloud-init-
output.log on remote host
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Bootstrapping Juju machine agent
Reading package
[Touch-packages] [Bug 1574351] [NEW] package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other
Public bug reported: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+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 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: New Bug description: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+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 1574079] Re: USB audio device is not recognized after startup in 16.04
** Changed in: fwupd (Ubuntu) Status: Confirmed => Fix Released -- 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/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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 1574347] Re: WiFi network list disappears from network manager applet
Same here. It does the same if the steps to reproduce (2) + (3) are replaced with suspend/wake up. -- 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/1574347 Title: WiFi network list disappears from network manager applet Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347/+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 1574347] Re: WiFi network list disappears from network manager applet
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1574347 Title: WiFi network list disappears from network manager applet Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347/+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 1574347] [NEW] WiFi network list disappears from network manager applet
Public bug reported: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574347 Title: WiFi network list disappears from network manager applet Status in network-manager package in Ubuntu: New Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed o
[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled
I have an A8 3820 AMD cpu (HD 6550 graphics) I have the same problem. First I want to say that I have been booting a usb hdd since 16.04 alpha. when I booted kernal 4.4.0-10 no problem, but I then booted to 4.4.0-12 that's when the problem started. Then I waited for the release of 16.04, there was no change. I just booted the live dvd using nomodset option and the screen showed an error "no ums support on radeon module." I don't have any other driver installed except what's in the kernel. -- 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: Radeon won't work with KMS enabled Status in xorg package in Ubuntu: New Bug description: I have a Radeon HD 5770 GPU. After upgrading to Xenial today and ensuring the xorg radeon driver was enabled, my machine will no longer boot to a usable state. After selecting default Ubuntu option from GRUB menu, both monitor lose signal input and the keyboard becomes unresponsive. Sometimes the machine will reboot on its own, most of the time I have to hard reset. If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the machine will boot but the radeon driver will not load. Attempting to load radeon driver with `sudo modprobe radeon modeset=1` after booting with modesetting off results in the same fail state explained above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds] CompositorRunning: None Date: Sat Apr 9 20:02:22 2016 DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990] InstallationDate: Installed on 2013-12-29 (832 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago) dmi.bios.date: 04/29/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0519 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Sat Apr 9 19:49:46 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+
[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10
Thanks, Colin! I listed openssh, because it is listed as affected in bug #201786, having status "Confirmed". It may be wrong there, too, or the maintainers had a reason to confirm it. If it helps, have a look at bug #201786. Regards, Rüdiger -- 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/1567250 Title: ssh signin problem since OTA-10 Status in Canonical System Image: Confirmed Status in Ubuntu Terminal App: Incomplete Status in gnome-keyring package in Ubuntu: New Status in indicator-network package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: Not sure if this is a terminal or image issue, but here goes. Since the update last night to OTA-10 I cannot ssh to a server anymore. Error message: "Agent Admitted Failure To Sign Using The Key" On server side and client side nothing changed to the user settings or keys. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+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 1574244] Re: Can't login to Feedly.com with google account on Browser
Upd. It works for WebApp ** Description changed: Steps to reproduce: 1. open http://feedly.com 2. click login (right left coner) 3. Login with Google credentials Feedly tries to redirect back, but with no luck. + It is really sucks as my m10 quite useless for me - feedly is my basic + news stream :( - It is really sucks as my m10 quite useless for me - feedly is my basic news stream :( + Upd: Redirect after login works in WebApp (check newly baked simple + feedlywebapp.nox app), so it is definitely bug in browser with (popup + window) redirect support + ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.12+15.04.20160401-0ubuntu1 Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Sun Apr 24 14:02:16 2016 InstallationDate: Installed on 2016-04-08 (15 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160408-215827) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1574244 Title: Can't login to Feedly.com with google account on Browser Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1. open http://feedly.com 2. click login (right left coner) 3. Login with Google credentials Feedly tries to redirect back, but with no luck. It is really sucks as my m10 quite useless for me - feedly is my basic news stream :( Upd: Redirect after login works in WebApp (check newly baked simple feedlywebapp.nox app), so it is definitely bug in browser with (popup window) redirect support ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.12+15.04.20160401-0ubuntu1 Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Sun Apr 24 14:02:16 2016 InstallationDate: Installed on 2016-04-08 (15 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160408-215827) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1574244/+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 1574340] [NEW] package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrading from 14.04 to 16.04 sysv-rc failed to install on my Dell M3800 Developer Edition laptop. Reinstalled 14.04 from Dell's restoration partition, did a dist-upgrade, and tried to upgrade again but had the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sysv-rc 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 00:48:58 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) ** Affects: sysvinit (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1574340 Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in sysvinit package in Ubuntu: New Bug description: Upgrading from 14.04 to 16.04 sysv-rc failed to install on my Dell M3800 Developer Edition laptop. Reinstalled 14.04 from Dell's restoration partition, did a dist-upgrade, and tried to upgrade again but had the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sysv-rc 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 00:48:58 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1574340/+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 1574338] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 14:19:22 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-04-21 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click (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 click in Ubuntu. https://bugs.launchpad.net/bugs/1574338 Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in click package in Ubuntu: New Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 14:19:22 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-04-21 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1574338/+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 1574334] [NEW] Unable to use apport-bug, apport-collect on Ubuntu 12.04.5 with all updates installed
Public bug reported: I have Ubuntu 12.04.5 amd64 with all installed updates. Root filesystem does not have errors. debsums does not report any changes of system components. Steps to reproduce: run apport-collect or apport-bug Expected resutls: apport-collect or apport-bug work normally Actual results: ERROR: Could not import module, is a package upgrade in progress? Error: No module named packaging.version So I can't use neither apport-bug nor apport-collect. What should I do? Is it a bug? ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: precise ** Tags added: precise -- 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/1574334 Title: Unable to use apport-bug, apport-collect on Ubuntu 12.04.5 with all updates installed Status in apport package in Ubuntu: New Bug description: I have Ubuntu 12.04.5 amd64 with all installed updates. Root filesystem does not have errors. debsums does not report any changes of system components. Steps to reproduce: run apport-collect or apport-bug Expected resutls: apport-collect or apport-bug work normally Actual results: ERROR: Could not import module, is a package upgrade in progress? Error: No module named packaging.version So I can't use neither apport-bug nor apport-collect. What should I do? Is it a bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1574334/+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 1574333] [NEW] LVM-based server does not boot with kernel 4.4 (but works with 4.2)
Public bug reported: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal with the following text : lvmetad is not active yet, using direct activation during sysinit Scannig for Btrfs flesystems _ Actually my set-up is lvm based, and the correponding lines of the output of a mount command are /dev/mapper/clio-root on / type btrfs (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based server does not boot with kernel 4.4 (but works with 4.2) Status in lvm2 package in Ubuntu: New Bug description: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal with the following text : lvmetad is not active yet, using direct activation during sysinit Scannig for Btrfs flesystems _ Actually my set-up is lvm based, and the correponding lines of the output of a mount command are /dev/mapper/clio-root on / type btrfs (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+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 1574251] Re: Resuming from screen lock with a multimonitor setup causes all windows to migrate to the "primary screen"
I have tried another configuration. This time, only the ASUS is active. And on "wake up", the laptop screen activates before the OS realizes that "oh no, this is not it, in fact only the other screen is active". -- 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/1574251 Title: Resuming from screen lock with a multimonitor setup causes all windows to migrate to the "primary screen" Status in xorg package in Ubuntu: New Bug description: Hardware: * Dell M3800; builtin screen is a 15", 1920x1080 screen; * an external display connected via HDMI, brand ASUS, same resolution; * the configuration via settings is that the screen on the laptop is on the left and the ASUS screen on the right. The bug did not appear with 15.10; only starting with 16.04 did this start to happen. This is a laptop with a nVidia chipset, and it doesn't matter whether I use nouveau or the proprietary nVidia driver. When the screen locks after inactivity, or I lock it explicitly, and then some time later (for some definition of "later") log back in, all windows have migrated to the laptop screen. This is annoying since it means I have to move all the windows over again. I am not sure what details I should give. I only noticed that compared to 15.10 which did not exhibit the bug, the ASUS screen takes longer to "wake up" again... My hunch here is that the HDMI port was deactivated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 24 14:43:24 2016 DistUpgraded: 2016-04-23 03:26:23,168 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] InstallationDate: Installed on 2015-07-16 (282 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=b8f6e64b-30d4-4621-8885-8079631fbd0e ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: Error: unable to create the OpenGL context UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/08/2015:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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: Sat Apr 23 19:16:20 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscrib
[Touch-packages] [Bug 1574325] [NEW] [GA-880GM-UD2H, Nvidia GPU 10 HDMI/DP, Digital Out, HDMI] No sound at all
Public bug reported: Hi ! I did an update, upgrade from 14.04 LTS to 16.04 LTS... And from this I don't have sound no more... It has happen yet before, but I don't konw why... I had to reinstall the system completly, but now I don't want... So, is there a solution to get the sound back please ? Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fuji 1559 F pulseaudio /dev/snd/controlC0: fuji 1559 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 12:20:29 2016 InstallationDate: Installed on 2016-03-22 (33 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GF100 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fuji 1559 F pulseaudio /dev/snd/controlC0: fuji 1559 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [GA-880GM-UD2H, Nvidia GPU 10 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1574325 Title: [GA-880GM-UD2H, Nvidia GPU 10 HDMI/DP, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi ! I did an update, upgrade from 14.04 LTS to 16.04 LTS... And from this I don't have sound no more... It has happen yet before, but I don't konw why... I had to reinstall the system completly, but now I don't want... So, is there a solution to get the sound back please ? Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fuji 1559 F pulseaudio /dev/snd/controlC0: fuji 1559 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 12:20:29 2016 InstallationDate: Installed on 2016-03-22 (33 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GF100 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fuji 1559 F pulseaudio /dev/snd/controlC0: fuji 1559 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [GA-880GM-UD2H, Nvidia GPU 10 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago) dmi.bios.date: 04/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://la
[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm
I have this problem too. I also had the problem of the WiFi not working in Unity, I would enter the WiFi password and nothing happened. After I installed Gnome desktop, which I use, I was able to enter the WiFi password by clicking on the WiFi icon, opening Wi-Fi Settings, next to my hub was a configure icon, I set the password in there under the Security tab. Now I can connect without problems in both Unity and Gnome desktops. Mine was a fresh install Compaq CQ58 laptop. I still can't choose a WiFi at the login screen, but once logged in I'm okay now. -- 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/1574020 Title: Can't use networkmanager from lightdm Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1574001] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Experienced the same problem when upgrading from 15.10. Had to do apt- get install -f systemd to force the upgrade from 225-1ubuntu9.1 to 229-4ubuntu4 (of systemd and systemd-sysv). -- 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/1574001 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: Confirmed Bug description: Very, very messy upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sat Apr 23 00:35:33 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-09-25 (941 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574001/+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 1549849]
Oh, I didn't know they were subvariants :) I've dropped them from our llvm-3.8 for now at least.. -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1549849]
(In reply to Jose Fonseca from comment #6) > It's not the first time LLVM misidentifies modern CPUs. > > I thought that all the logic in > src/gallium/auxiliary/gallivm/lp_bld_misc.cpp for setting +/-foo mattrs > would save us from this sort of grief. For features we already know about (I think I even mentioned that back then, hoping it wouldn't be a problem)... If I look at the list of skylake features, I'd nearly bet the winner is avx512 (and/or any subvariant). -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1549849]
llvm-3.8 misdetects skylake features, this is fixed in 3.9-snapshot.. -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1549849]
(In reply to Timo Aaltonen from comment #8) > Actually it wasn't avx512, that was the first one I tried :) It's enabled > also on 3.7 and that version works fine. Only one that was added in 3.8 is > PKU, but dropping just that didn't help. > > I did try dropping all non-client features (AVX512, CDI, DQI, BWI, VLX, PKU) > and that worked. Maybe one of CDI/DQI/BWI/VLX is somewhat broken on 3.8? Which is why I said "or any subvariant" ;-). ERI, CDI, PFI, DQI, BWI, VLX are all avx512 variants (omg naming???), though that skylake in the llvm 3.8 list doesn't suport ERI and PFI. I'm not sure, but probably dropping avx512 manually when a enhanced variant still gets enabled won't do anything. I don't think PKU would matter (but no guarantee...). I suppose we should explicitly disable all of them via mattrs too (not that it's a battle we can win, there will be some extensions at some point...). -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1549849]
Actually it wasn't avx512, that was the first one I tried :) It's enabled also on 3.7 and that version works fine. Only one that was added in 3.8 is PKU, but dropping just that didn't help. I did try dropping all non-client features (AVX512, CDI, DQI, BWI, VLX, PKU) and that worked. Maybe one of CDI/DQI/BWI/VLX is somewhat broken on 3.8? -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1549849]
It's not the first time LLVM misidentifies modern CPUs. I thought that all the logic in src/gallium/auxiliary/gallivm/lp_bld_misc.cpp for setting +/-foo mattrs would save us from this sort of grief. On the other hand, I suppose that actually knowing the exact CPU model allows it to better model instruction latency/throughput. -- 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/1549849 Title: 11.2.0-rc1: llvmpipe tests fail if built on skylake Status in Mesa: Confirmed Status in mesa package in Ubuntu: Triaged Bug description: if built on broadwell all is well. 11.1 was fine, so it's a regression in 11.2.x To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1549849/+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 1574324] [NEW] pulseaudio crashes when connecting to bluetooth headphones
Public bug reported: 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. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Verbose dump of Pulseaudio" https://bugs.launchpad.net/bugs/1574324/+attachment/4645691/+files/pulseverbose.log -- 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 Status in pulseaudio package in Ubuntu: New 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 1574322] [NEW] "webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory" error when attempting to launch webbr
Public bug reported: I have recently found that on Ubuntu 16.04 (in a 64-bit VirtualBox VM) that the webbrowser-app application does not start when launched from the launcher (it flashes for a little bit but then stops and does nothing else). If I however try to launch it from Terminal I get: webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory This may be related to bug #1573762 but note that this was in a VM and that I have Intel drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 17:08:51 2016 InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1574322 Title: "webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory" error when attempting to launch webbrowser-app Status in webbrowser-app package in Ubuntu: New Bug description: I have recently found that on Ubuntu 16.04 (in a 64-bit VirtualBox VM) that the webbrowser-app application does not start when launched from the launcher (it flashes for a little bit but then stops and does nothing else). If I however try to launch it from Terminal I get: webbrowser-app: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory This may be related to bug #1573762 but note that this was in a VM and that I have Intel drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 17:08:51 2016 InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1574322/+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 1574073] Re: Networking does not work after reboot
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574073 Title: Networking does not work after reboot Status in network-manager package in Ubuntu: New Bug description: 16.04 for about 1-2 weeks there has been an issue that restarting ubuntu means all networking devices no longer function until full shutdown and power on (power-cycle) event. I keep meaning to report it (2 weeks now), so apologies for not reporting sooner. It seems the devices are not even mapped in /dev so it could be init, however I have forced re-generation of this and it has not remitted the issue. I have also tried restarting networking service which has no effect, likely due to the device not being mapped. lspci does have details of the networking devices that are not present in /dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574073/+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
