[Touch-packages] [Bug 1604429] Re: Inserting an USB mouse disables touchpad input
Confirmed on a laptop. Plugging a USB mouse in stops the Unity8 from responding to the touchpad. Also noteworthy: * The same bug does not occur in Mir demo servers. All devices keep working. * The same bug does not occur with Apple Magic Trackpad (Bluetooth). Interesting this is the second touchpad-only Unity8-only regression recently. See also bug 1604032 ** Package changed: unity (Ubuntu) => unity8 (Ubuntu) ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir Status: New => Invalid ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** Changed in: unity8 (Ubuntu) Status: New => Confirmed ** Summary changed: - Inserting an USB mouse disables touchpad input + Inserting an USB mouse disables touchpad input for Unity8 -- 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/1604429 Title: Inserting an USB mouse disables touchpad input for Unity8 Status in Mir: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: I inserted an USB mouse in my laptop. Now the touchpad does not work. Removing the mouse enables the touchpad again. I'm not sure if that's intended or if it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1604429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604500] Re: please merge keyutils from Debian
** Changed in: keyutils (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1604500 Title: please merge keyutils from Debian Status in keyutils package in Ubuntu: New Bug description: attached debdiff, build ongoing @costamagnagianfranco/locutusofborg- ppa BTW I would try a plain sync, just to check if the testsuite is good or not with new kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1604500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603835] Re: Sometimes url and description of the url do not match in the address bar
** Description changed: In the webbrowser, when entering an address url of a website in the address bar, a list of similar webpages is provided below by auto-completion. The list is composed of url with a description of the address. But sometimes (and quite randomly it seems) the url address and the description do not match at all. - Guess: It seems to happen with websites that I had removed from the - history. + Guess: It seems to happen with websites that I had removed from the history. + Actually, a website that has been suppressed from the history should not appear in the url list no? Mx4 Ota 11 stable -- 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/1603835 Title: Sometimes url and description of the url do not match in the address bar Status in webbrowser-app package in Ubuntu: New Bug description: In the webbrowser, when entering an address url of a website in the address bar, a list of similar webpages is provided below by auto-completion. The list is composed of url with a description of the address. But sometimes (and quite randomly it seems) the url address and the description do not match at all. Guess: It seems to happen with websites that I had removed from the history. Actually, a website that has been suppressed from the history should not appear in the url list no? Mx4 Ota 11 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1603835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604429] Re: Inserting an USB mouse disables touchpad input
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604429 Title: Inserting an USB mouse disables touchpad input Status in Mir: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: I inserted an USB mouse in my laptop. Now the touchpad does not work. Removing the mouse enables the touchpad again. I'm not sure if that's intended or if it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1604429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604429] [NEW] Inserting an USB mouse disables touchpad input
You have been subscribed to a public bug: I inserted an USB mouse in my laptop. Now the touchpad does not work. Removing the mouse enables the touchpad again. I'm not sure if that's intended or if it's a bug. ** Affects: mir Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: input -- Inserting an USB mouse disables touchpad input https://bugs.launchpad.net/bugs/1604429 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 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 1056566] Re: Missing pkgconfig file
On second thought, I guess this is similar to bug 1419267 so re-opening since there is not a turbojpeg .pc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1056566 Title: Missing pkgconfig file Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: Our packages do not contain a turbojpeg.pc file, meaning any pkgconfig-using build script that depends on it being in libjpeg-turbo may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1056566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1056566] Re: Missing pkgconfig file
This should be fixed now: https://launchpad.net/ubuntu/+source/libjpeg-turbo/1.4.2-0ubuntu3 ** Changed in: libjpeg-turbo (Ubuntu) Status: New => Fix Released ** Changed in: libjpeg-turbo (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1056566 Title: Missing pkgconfig file Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: Our packages do not contain a turbojpeg.pc file, meaning any pkgconfig-using build script that depends on it being in libjpeg-turbo may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1056566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369067] Re: symbolic link to libturbojpeg.so missing
*** This bug is a duplicate of bug 1419267 *** https://bugs.launchpad.net/bugs/1419267 ** This bug has been marked a duplicate of bug 1419267 libjpegturbo.so missing from -dev package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1369067 Title: symbolic link to libturbojpeg.so missing Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: On amd64, the missing symlink (libturbojpeg.so -> libturbojpeg.so.0) can lead to the following link error: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libturbojpeg.a(libturbojpeg_la-turbojpeg.o): relocation R_X86_64_32 against `.data' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libturbojpeg.a: error adding symbols: Bad value Manually adding the missing symlink in /usr/lib/x86_64-linux-gnu/ fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1369067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554895] Re: Erratic mouse behaviour
** Tags removed: yakkaty ** Tags added: yakkety -- 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/1554895 Title: Erratic mouse behaviour Status in xorg package in Ubuntu: Incomplete Bug description: I am running Ubuntu 14.04 on a Lenovo Yoga 2 13 and, after a few minutes of working, the mouse pointer goes crazy. It goes to the bottom right corner of the screen and flickers, clicking stuff randomly. * Adding a USB mouse and deactivating the trackpad makes no difference. * Tried Kubuntu 15.10, problem still there. * Tried suggestions in http://ubuntuforums.org/showthread.php?t=2235704 http://ubuntuforums.org/showthread.php?t=2229831&page=2&p=13451930#post13451930 without success also. As mentioned by other users, my laptop is currently unusable. I do not want to switch to Windows but, given the current hardware I have, I do not see how I can resolve this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 9 01:44:53 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-03-07 (2 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2016-05-19 (24 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20344 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10 Tags: trusty ubuntu compiz-0.9 Uname: Linux 4.2.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20160425-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 Jun 12 23:26:25 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1069 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore
The issue was with Epson drivers for printers and some other manufacturers who required lsb for printer install. HP printers are supported via HPLIP which is included in Ubuntu installation. -- 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 lsb: New Status in cups-filters package in Ubuntu: Fix Released Status in epson-inkjet-printer-escpr package in Ubuntu: Fix Released Status in lsb package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Fix Released Status in epson-inkjet-printer-escpr source package in Xenial: Fix Released Status in lsb source package in Xenial: Fix Released Bug description: [SRU justification] Previous releases were compatible with third-party printer drivers provided in LSB package format (and also as .deb packages depending on the lsb package). As of 16.04, because the LSB specifies ABIs for various libraries that are no longer supported in Ubuntu as obsolete, the packages for the lsb modules have been dropped in both Debian and Ubuntu. This includes dropping of lsb-core, which is the component which provides the LSB-mandated ELF loader path - without which no lsb executable will work. This SRU will restore the bare minimum of LSB compatibility necessary to support known third-party LSB printer driver packages on Ubuntu 16.04. [Regression potential] The reintroduced 'lsb' binary package is known to not fully satisfy the requirements for a complete LSB-compliant system. This is a regression vs. Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to Ubuntu 16.04 may have the upgrade succeed without any warning from the package manager. As there are very few lsb packages in use in the wild, this is considered an acceptable regression, especially as this will land before the first 16.04 point release. [Test case] 1. Download the epsion 201106w printer driver package from http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb 2. Install the package and confirm that its dependencies are not satisfiable. 3. Enable xenial-proposed. 4. Install the package again and confirm that the dependencies are satisfied. 5. Verify that /opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter can be run without errors about missing lsb ld.so or missing libraries. 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/lsb/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore
Any printer installation is the problems you confront allow the professional to take a step ahead to fix the driver, install it well and ensure that it is compatible with your computer software and works well. The specialist guide you well how to make over it well. To get quotes for your queries dial toll free number 1-888-924-5460 now OR Visit your website for more details : https://www.vfix365.us/hp ** Also affects: lsb Importance: Undecided Status: New -- 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 lsb: New Status in cups-filters package in Ubuntu: Fix Released Status in epson-inkjet-printer-escpr package in Ubuntu: Fix Released Status in lsb package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: Fix Released Status in epson-inkjet-printer-escpr source package in Xenial: Fix Released Status in lsb source package in Xenial: Fix Released Bug description: [SRU justification] Previous releases were compatible with third-party printer drivers provided in LSB package format (and also as .deb packages depending on the lsb package). As of 16.04, because the LSB specifies ABIs for various libraries that are no longer supported in Ubuntu as obsolete, the packages for the lsb modules have been dropped in both Debian and Ubuntu. This includes dropping of lsb-core, which is the component which provides the LSB-mandated ELF loader path - without which no lsb executable will work. This SRU will restore the bare minimum of LSB compatibility necessary to support known third-party LSB printer driver packages on Ubuntu 16.04. [Regression potential] The reintroduced 'lsb' binary package is known to not fully satisfy the requirements for a complete LSB-compliant system. This is a regression vs. Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to Ubuntu 16.04 may have the upgrade succeed without any warning from the package manager. As there are very few lsb packages in use in the wild, this is considered an acceptable regression, especially as this will land before the first 16.04 point release. [Test case] 1. Download the epsion 201106w printer driver package from http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb 2. Install the package and confirm that its dependencies are not satisfiable. 3. Enable xenial-proposed. 4. Install the package again and confirm that the dependencies are satisfied. 5. Verify that /opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter can be run without errors about missing lsb ld.so or missing libraries. 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/lsb/+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 684522] Re: format error in man page for dotlockfile
[Expired for liblockfile (Ubuntu) because there has been no activity for 60 days.] ** Changed in: liblockfile (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liblockfile in Ubuntu. https://bugs.launchpad.net/bugs/684522 Title: format error in man page for dotlockfile Status in liblockfile package in Ubuntu: Expired Bug description: Binary package hint: liblockfile1 # mandb -c Processing manual pages under /usr/share/man... ... mandb: warning: /usr/share/man/man1/dotlockfile.1.gz: whatis parse for dotlockfile(1) failed dpkg-query -S dotlockfile.1.gz liblockfile1: /usr/share/man/man1/dotlockfile.1.gz So Error in the man file formatting/parsing for the page provided by liblockfile1 apt-cache policy liblockfile1 liblockfile1: Installed: 1.08-4 Candidate: 1.08-4 Version table: *** 1.08-4 0 500 http://archive.ubuntu.com/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status lsb_release -idrc Distributor ID: Ubuntu Description: Ubuntu 10.10 Release: 10.10 Codename: maverick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblockfile/+bug/684522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408159] Re: [messaging] Too easy to delete whole conversation history with a contact
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1408159 Title: [messaging] Too easy to delete whole conversation history with a contact Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Confirmed Bug description: Steps: * open messaging app * drag one of the items on the list to the right * tap on the trash icon Expected: * only today's messages are removed or at least there's a confirmation dialog Current: * whole history of messaging with a contact is removed The fact that conversations are separated by days suggests as if a single item was a conversation within that day. But in fact they're complete conversations just ordered by date (which is actually different than the phone log, which *is* split by date, and removing an item there only affects a day's events). I wonder if it would be better to indeed show multiple entries for a single contact, in each day a message was sent either way, this being a shortcut to a certain message when opening. It feels like this would be better in the long run (imagine many years of messaging history). That might deserve another bug though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: messaging-app 0.1+15.04.20141210-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Wed Jan 7 00:06:35 2015 InstallationDate: Installed on 2014-12-17 (20 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141217-020204) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) --- UX comment & resolution There is an active action of 1. dragging the list item in the conversation overview to the right 2. tapping the delete icon This means that there is already a two step interaction in place before the message is deleted. As an additionally security measure we could introduce an additional confirmation dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1408159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539896] Re: [enhancement] Support Vulkan
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1539896 Title: [enhancement] Support Vulkan Status in Mir: In Progress Status in Ubuntu SDK IDE: Invalid Status in mir package in Ubuntu: New Bug description: full support to the libraries vulkan in mir and in canonical system image. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603080] Re: mirtest-dev provides an incorrect .pc file
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603080 Title: mirtest-dev provides an incorrect .pc file Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: In (e.g. /usr/lib/x86_64-linux-gnu/pkgconfig/mirtest.pc) there are missing library dependencies: -lboost_filesystem -lboost_system To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593655] Re: Servers based on Mir need a hook to execute code when the server is closing
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1593655 Title: Servers based on Mir need a hook to execute code when the server is closing Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: There are multiple ways that a server can be closed because we hook into SIGINT & SIGTERM to stop the Mir server and the client code can call stop() directly. There should be an "on_stop(function)" facility to run client cleanup code before the server shuts down. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1593655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600220] Re: Nested server needs full control over cursor position
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1600220 Title: Nested server needs full control over cursor position Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Unity 8, a nested server of unity-system-compositor, needs full control over the cursor position. Mir doesn't have the needed context information to know how to move or position the cursor in all situations. Only Unity 8 has this information, which lives mainly in its QML scene. Once this is granted Unity 8 can dump its QML cursor implementation and move to use the more performant hardware cursor that mir has access to. Related to bug 1513883. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1600220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569836] Re: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1569836 Title: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: run mir_demo_server with the CanonicalWindowManagerPolicy. Connect a client (like egltriangle). Hit Shift+F11 to transition client to vertmaximized. The titlebar is hidden (or off the top of the screen). It should be shown at the top. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1569836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536279] Re: Mir does not reset key states when paused or resumed
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536279 Title: Mir does not reset key states when paused or resumed Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Bug description: Mir switches away from the current VT when ALT+FXX is pressed. During that key sequence the alt modifier is pressed. While away and mir does not receive the alt release. When you switch back to mir there is a chance that mir is not receiving the alt release either. So switching away and back to mir makes the alt key stick... Proposed solution: - track regular keys in mir::input::Seat or in SurfaceDispatcher - inform client(s) about pause / resume with a focus lost / focus gain event - attach key state to focus event or send separate key state event - adapt gdk/qt backends - fix alt key tracking in unity8 to rely on the provided modifier state To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603091] Re: mir_test_framework::server_platform_path(), mir_test_framework::server_platform() don't support use in a downstream test built against mir-test-assist
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603091 Title: mir_test_framework::server_platform_path(), mir_test_framework::server_platform() don't support use in a downstream test built against mir-test-assist Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: These functions assume the platform path/library is built or installed relative to the executable. This is not the case for a downstream executable being built against an installed version of Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604442] Re: Keyboard stays on screen after leaving an application
Incidentally I did warn that bugs like this could and would happen when we added maliit support for Xmir apps. The shell should still provide a failsafe 'hide-the-OSK' feature upon switching apps if the requisite 'hide' message never came through from the app. -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604442] Re: Keyboard stays on screen after leaving an application
I don't think those revision numbers are "useless". Revisions 386 and 388 do exist: http://system-image.ubuntu.com/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/ So you just need to be sure you're flashing with the same channel and device, and use --revision=X to select which one. -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error
I updated from 14.04 to 16.04. That said, xenial is also affected. Apport error message was shown shortly after login. Apport forwarded me to https://bugs.launchpad.net/bugs/1452849 which duplicates this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447099 Title: /sbin/upstart:indicator-session-unknown-user-error Status in upstart : New Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Vivid: Confirmed Status in upstart source package in Wily: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding upstart. This problem was most recently seen with version 1.13.2-0ubuntu13, the problem page at https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1447099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
** Branch unlinked: lp:mir/0.24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
** Changed in: unity8 (Ubuntu) Status: Confirmed => In Progress -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603114] Re: mir_acceptance_tests.bin: double free or corruption (fasttop)
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603114 Title: mir_acceptance_tests.bin: double free or corruption (fasttop) Status in Mir: Fix Committed Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Bug description: Seen a few times, typical thing seen is a memory issue in the acceptance tests: https://launchpadlibrarian.net/272973212/buildlog_ubuntu-yakkety- i386.mir_0.24.0+16.10.20160714-0ubuntu1_BUILDING.txt.gz 8: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed throwback Error in `/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin': double free or corruption (fasttop): 0x0a1b5e40 CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed throwback 8: === Backtrace: = 8: /lib/i386-linux-gnu/libc.so.6(+0x672d7)[0xf70872d7] 8: /lib/i386-linux-gnu/libc.so.6(+0x6d227)[0xf708d227] 8: /lib/i386-linux-gnu/libc.so.6(+0x6dae1)[0xf708dae1] 8: /usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x18)[0xf72884b8] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZNSt6vectorISt8weak_ptrIN3mir5input11InputDeviceEESaIS4_EED2Ev+0x8b)[0x86213bb] 8: /lib/i386-linux-gnu/libc.so.6(+0x2e933)[0xf704e933] 8: /lib/i386-linux-gnu/libc.so.6(+0x2e98f)[0xf704e98f] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework28InterprocessClientServerTestD1Ev+0x12a)[0x8615eda] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x8352b85] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing4Test11DeleteSelf_Ev+0x28)[0x8647494] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x45)[0x86536f9] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ddff] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestInfo3RunEv+0x13b)[0x86318a7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestCase3RunEv+0x103)[0x8631ffd] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal12UnitTestImpl11RunAllTestsEv+0x2e7)[0x8639a51] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x45)[0x8654bd7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ed4f] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8UnitTest3RunEv+0xc6)[0x86383c2] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework4mainEiPPc+0x3c)[0x82822dc] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(main+0x6d)[0x828250d] 8: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7)[0xf70385f7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x828267e] 8: === Memory map: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
Fix committed to lp:mir/0.24 at revision 3592, scheduled for release in Mir 0.24.0 ** Changed in: mir/0.24 Status: Triaged => Fix Committed ** Changed in: mir (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
** Branch linked: lp:mir/0.24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
Fix committed to lp:mir at revision 3600, scheduled for release in Mir 0.25.0 Fix committed to lp:mir/0.23 at revision 3520, scheduled for release in Mir 0.23.4 Fix MISSING in lp:mir/0.24 for now. ** Changed in: mir Milestone: 0.23.4 => 0.25.0 ** Also affects: mir/0.23 Importance: Undecided Status: New ** Also affects: mir/0.24 Importance: Undecided Status: New ** Changed in: mir Assignee: Mir development team (mir-team) => Daniel van Vugt (vanvugt) ** Changed in: mir Importance: High => Critical ** Changed in: mir/0.23 Importance: Undecided => Critical ** Changed in: mir/0.24 Importance: Undecided => Critical ** Changed in: mir/0.23 Milestone: None => 0.24.0 ** Changed in: mir/0.23 Milestone: 0.24.0 => 0.23.4 ** Changed in: mir/0.24 Milestone: None => 0.24.0 ** Changed in: mir/0.23 Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir/0.24 Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir/0.24 Status: New => Triaged ** Changed in: mir/0.23 Status: New => Fix Committed ** Changed in: mir/0.23 Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mir/0.23 Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Branch unlinked: lp:mir/0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591328] Re: Pointer/cursor input lag in unity8 session
Well it's nice to hear you care about this stuff :) Short term: anpok and unity8 guys are working on lag-free mouse cursor pass-through -> bug 1600220 Longer term: I will need to finish my frame notification work to finally kill all nesting and buffering lag. -- 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/1591328 Title: Pointer/cursor input lag in unity8 session Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Mouse pointer suffers of heavy input lag on my laptop, might also affect tablet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1591328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604638] Re: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1604638 Title: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in python2.7 package in Ubuntu: New Bug description: Recently upgraded from a regularly updated Ubuntu 14.04 LTS to Ubuntu 16.04. I have had a problem with dpkg complaining about struct and then python-minimal. I tried to remove the existing python2.7 packages ( later /usr/lib/python2.7 as well ) and then doing a clean install of python 2.7. I think I might have missed some python2.7 and saw a python2.7.5 doc package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python2.7-minimal 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: python2.7-minimal: Install python2.7: Install python2.7-minimal: Configure python2.7: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 19 18:11:15 2016 DuplicateSignature: package:python2.7-minimal:2.7.12-1~16.04 Setting up python2.7-minimal (2.7.12-1~16.04) ... python2.7: can't open file '/usr/lib/python2.7/py_compile.py': [Errno 2] No such file or directory dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-06-17 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1604638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604638] [NEW] package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Recently upgraded from a regularly updated Ubuntu 14.04 LTS to Ubuntu 16.04. I have had a problem with dpkg complaining about struct and then python-minimal. I tried to remove the existing python2.7 packages ( later /usr/lib/python2.7 as well ) and then doing a clean install of python 2.7. I think I might have missed some python2.7 and saw a python2.7.5 doc package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python2.7-minimal 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: python2.7-minimal: Install python2.7: Install python2.7-minimal: Configure python2.7: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 19 18:11:15 2016 DuplicateSignature: package:python2.7-minimal:2.7.12-1~16.04 Setting up python2.7-minimal (2.7.12-1~16.04) ... python2.7: can't open file '/usr/lib/python2.7/py_compile.py': [Errno 2] No such file or directory dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-06-17 (32 days ago) ** Affects: python2.7 (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1604638 Title: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in python2.7 package in Ubuntu: New Bug description: Recently upgraded from a regularly updated Ubuntu 14.04 LTS to Ubuntu 16.04. I have had a problem with dpkg complaining about struct and then python-minimal. I tried to remove the existing python2.7 packages ( later /usr/lib/python2.7 as well ) and then doing a clean install of python 2.7. I think I might have missed some python2.7 and saw a python2.7.5 doc package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python2.7-minimal 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: python2.7-minimal: Install python2.7: Install python2.7-minimal: Configure python2.7: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 19 18:11:15 2016 DuplicateSignature: package:python2.7-minimal:2.7.12-1~16.04 Setting up python2.7-minimal (2.7.12-1~16.04) ... python2.7: can't open file '/usr/lib/python2.7/py_compile.py': [Errno 2] No such file or directory dpkg: error processing package python2.7-minimal (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: python2.7 Title: package python2.7-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-06-17 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1604638/+subscriptions -- Mailing list: https://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 1604497] Re: Pulseaudio does not start
Could you plesae get a log from PulseAudio as descirbed at https://wiki.ubuntu.com/PulseAudio/Log. Thanks. -- 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/1604497 Title: Pulseaudio does not start Status in pulseaudio package in Ubuntu: New Bug description: I'm using Ubuntu Mate 16.04 with the current updates. When I start the computer, pulseaudio is not working after I've logged in. If I type: start-pulseaudio-x11 from the command line, I get "Connection failure: Connection refused pa_context_connect() failed: Connection refused" and I cannot play any sound. If I type pulseaudio& on the command line, I can get sound in some applications (e.g. Audacity) but not others (e.g. Firefox or other browsers). At some point a command line message appears that says: "E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." I'm not clear why there's a reference to bluez5-util, since I don't have bluetooth on my machine. 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 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 19 17:43:11 2016 InstallationDate: Installed on 2016-05-10 (70 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Z97X-UD3H, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1604497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604509] Re: In the bottom edge component, using preload=true with contentUrl results in an empty page
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1604509
Title:
In the bottom edge component, using preload=true with contentUrl
results in an empty page
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
In the bottom edge component, using preload=true with contentUrl
results in an empty page.
For example the following code 'works' with a red rectangle in the
bottom edge:
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
}
But the following code does not and results in a transparent overlay,
the contentItem appears to stay null.
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
}
Note that using contentComponent does work with preloadContent true or false.
See the linked branch for an example of this not working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604509/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604632] [NEW] Dash filter can't scroll with cursor on dropdown
Public bug reported: In the filter results section of the Dash, there is an issue with the scrolling. It scrolls with the mouse wheel, except when the mouse cursor is on top the Categories and Sources dropdowns. To be able to scroll again, I have to move the cursor off of the dropdowns. Ubuntu 16.04 LTS What I expected to happen: Being able to scroll down anywhere in the filter results section. What happened instead: I cannot scroll when the cursor is on top of the Categories and Sources dropdowns. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Package changed: unity8 (Ubuntu) => unity (Ubuntu) -- 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/1604632 Title: Dash filter can't scroll with cursor on dropdown Status in unity package in Ubuntu: New Bug description: In the filter results section of the Dash, there is an issue with the scrolling. It scrolls with the mouse wheel, except when the mouse cursor is on top the Categories and Sources dropdowns. To be able to scroll again, I have to move the cursor off of the dropdowns. Ubuntu 16.04 LTS What I expected to happen: Being able to scroll down anywhere in the filter results section. What happened instead: I cannot scroll when the cursor is on top of the Categories and Sources dropdowns. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1604632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604622] [NEW] /usr/bin/powerd:11:load_library:find_library:link_image:init_library:find_library
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding powerd. This problem was most recently seen with version 0.16+15.04.20160204.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/17e1415e63afd40ea5a6d0f76375c5e19d769890 contains more details. ** Affects: powerd (Ubuntu) Importance: Undecided Status: New ** Tags: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1604622 Title: /usr/bin/powerd:11:load_library:find_library:link_image:init_library:find_library Status in powerd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding powerd. This problem was most recently seen with version 0.16+15.04.20160204.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/17e1415e63afd40ea5a6d0f76375c5e19d769890 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1604622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604617] [NEW] dhclient does not send fqdn.fqdn for DHCPv6
Public bug reported: ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent in order to work for DHCPv6. This used to be done in Ubuntu, as shown in bugs #991360 and #108862, and all my Windows hosts send it. However this was removed in Ubuntu due to a regression in IPv4 functionality. As IPv6 is more widely deployed these days, this regression in IPv6 should be fixed. This bug is current as of Ubuntu 16.04 LTS. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- 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/1604617 Title: dhclient does not send fqdn.fqdn for DHCPv6 Status in isc-dhcp package in Ubuntu: New Bug description: ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent in order to work for DHCPv6. This used to be done in Ubuntu, as shown in bugs #991360 and #108862, and all my Windows hosts send it. However this was removed in Ubuntu due to a regression in IPv4 functionality. As IPv6 is more widely deployed these days, this regression in IPv6 should be fixed. This bug is current as of Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604611] Re: [webapp-container] Undocumented command line option --no-australia-mode
** Description changed: It has been reported by personnel related to Canonical [1] that webapp- container has a (obviously undocumented) command line option `--no- australia-mode`. [1] https://lists.launchpad.net/ubuntu-phone/msg21542.html Analysis - This option doesn't show up when webapp-container is run with `--help`. - The webapp-container binary doesn't refuse to run when the `--no-australia-mode` option is used. Expected Result --- - Running webapp-container with `--help` should mention and explain the `--no-australia-mode` option (if it exists). - The webapp-container binary should refuse to run with unknown or invalid command line options. See Also - - See bug 1554202 for related information. + - Bug 1554202 for related information. + - Bug 1563398 / comment 11 (Set the front camera as the default for video media requests) -- 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/1604611 Title: [webapp-container] Undocumented command line option --no-australia- mode Status in webbrowser-app package in Ubuntu: New Bug description: It has been reported by personnel related to Canonical [1] that webapp-container has a (obviously undocumented) command line option `--no-australia-mode`. [1] https://lists.launchpad.net/ubuntu-phone/msg21542.html Analysis - This option doesn't show up when webapp-container is run with `--help`. - The webapp-container binary doesn't refuse to run when the `--no-australia-mode` option is used. Expected Result --- - Running webapp-container with `--help` should mention and explain the `--no-australia-mode` option (if it exists). - The webapp-container binary should refuse to run with unknown or invalid command line options. See Also - Bug 1554202 for related information. - Bug 1563398 / comment 11 (Set the front camera as the default for video media requests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1604611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604611] [NEW] [webapp-container] Undocumented command line option --no-australia-mode
Public bug reported: It has been reported by personnel related to Canonical [1] that webapp- container has a (obviously undocumented) command line option `--no- australia-mode`. [1] https://lists.launchpad.net/ubuntu-phone/msg21542.html Analysis - This option doesn't show up when webapp-container is run with `--help`. - The webapp-container binary doesn't refuse to run when the `--no-australia-mode` option is used. Expected Result --- - Running webapp-container with `--help` should mention and explain the `--no-australia-mode` option (if it exists). - The webapp-container binary should refuse to run with unknown or invalid command line options. See Also - See bug 1554202 for related information. ** 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/1604611 Title: [webapp-container] Undocumented command line option --no-australia- mode Status in webbrowser-app package in Ubuntu: New Bug description: It has been reported by personnel related to Canonical [1] that webapp-container has a (obviously undocumented) command line option `--no-australia-mode`. [1] https://lists.launchpad.net/ubuntu-phone/msg21542.html Analysis - This option doesn't show up when webapp-container is run with `--help`. - The webapp-container binary doesn't refuse to run when the `--no-australia-mode` option is used. Expected Result --- - Running webapp-container with `--help` should mention and explain the `--no-australia-mode` option (if it exists). - The webapp-container binary should refuse to run with unknown or invalid command line options. See Also - See bug 1554202 for related information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1604611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604516] Re: errors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). 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/1604516 Title: errors Status in xorg package in Ubuntu: Incomplete Bug description: Errors ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.45.11 Tue May 17 18:25:03 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 19 23:29:42 2016 DistUpgraded: 2016-07-06 20:36:48,274 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.45.11, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.45.11, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:067d] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GK107M [GeForce GT 640M] [1025:067d] InstallationDate: Installed on 2016-03-11 (129 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire M3-581TG ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=33d6299c-51b9-4473-8383-8676d7735358 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-07-06 (13 days ago) dmi.bios.date: 10/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: MA50_HX dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd10/22/2012:svnAcer:pnAspireM3-581TG:pvrV1.13:rvnAcer:rnMA50_HX:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire M3-581TG dmi.product.version: V1.13 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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: Tue Jul 19 23:06:25 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Touch-packages] [Bug 1604583] Re: Crash occurred while system was unattended, installing the KDE before erradicating Gnome - 20160719-1239
*** This bug is a duplicate of bug 1588346 *** https://bugs.launchpad.net/bugs/1588346 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1588346, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1588346 package kde-config-telepathy-accounts (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 -- 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/1604583 Title: Crash occurred while system was unattended, installing the KDE before erradicating Gnome - 20160719-1239 Status in account-plugins package in Ubuntu: New Status in ktp-accounts-kcm package in Ubuntu: New Bug description: Brief description of incident: As the default Gnome Desktop Environment was still present and active, the KDE was being installed using 'apt-get install kubuntu-desktop'. Upon returning to a sleeping screen, tapping the KB/Mouse, the system woke the screen only to display a dialog box triggered to generate a bug report for whatever error occurred during the installation process. System and Package details: Description: Ubuntu 16.04 LTS Release: 16.04 Package ID: kubuntu-desktop Package: Kubuntu Plasma Desktop/Netbook system Installed: 1.338 Candidate: 1.338 Version table: *** 1.338 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Boot to the desktop of Ubuntu 16.04 with the default GNOME desktop environment 2) Open a terminal window 3) Type the following and press the Enter key to submit the command: sudo apt-get install kubuntu-desktop Expected results: KDE package should install without incident. Actual results: KDE package installed, and is still installing, but generated errors triggering the automated creation of this bug report. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kde-config-telepathy-accounts (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Jul 19 12:19:46 2016 DuplicateSignature: package:kde-config-telepathy-accounts:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-06-30 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ktp-accounts-kcm Title: package kde-config-telepathy-accounts (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1604583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.25.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1601810 Title: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay Status in Mir: Fix Committed Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: New Bug description: ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::DescribeTo(std::ostream*) const': /usr/include/gmock/gmock-matchers.h:242: undefined reference to `testing::internal::AnyMatcherImpl const&>::DescribeTo(std::ostream*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' collect2: error: ld returned 1 exit status full log: https://launchpadlibrarian.net/272328456/buildlog_ubuntu-xenial-amd64.mir_0.24.0+16.04.20160711-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1601810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604583] Bug is not a security issue
*** This bug is a duplicate of bug 1588346 *** https://bugs.launchpad.net/bugs/1588346 Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. -- 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/1604583 Title: Crash occurred while system was unattended, installing the KDE before erradicating Gnome - 20160719-1239 Status in account-plugins package in Ubuntu: New Status in ktp-accounts-kcm package in Ubuntu: New Bug description: Brief description of incident: As the default Gnome Desktop Environment was still present and active, the KDE was being installed using 'apt-get install kubuntu-desktop'. Upon returning to a sleeping screen, tapping the KB/Mouse, the system woke the screen only to display a dialog box triggered to generate a bug report for whatever error occurred during the installation process. System and Package details: Description: Ubuntu 16.04 LTS Release: 16.04 Package ID: kubuntu-desktop Package: Kubuntu Plasma Desktop/Netbook system Installed: 1.338 Candidate: 1.338 Version table: *** 1.338 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Boot to the desktop of Ubuntu 16.04 with the default GNOME desktop environment 2) Open a terminal window 3) Type the following and press the Enter key to submit the command: sudo apt-get install kubuntu-desktop Expected results: KDE package should install without incident. Actual results: KDE package installed, and is still installing, but generated errors triggering the automated creation of this bug report. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kde-config-telepathy-accounts (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Jul 19 12:19:46 2016 DuplicateSignature: package:kde-config-telepathy-accounts:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-06-30 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ktp-accounts-kcm Title: package kde-config-telepathy-accounts (not installed) failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1604583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604583] Re: Crash occurred while system was unattended, installing the KDE before erradicating Gnome - 20160719-1239
*** This bug is a duplicate of bug 1588346 ***
https://bugs.launchpad.net/bugs/1588346
Note that you may have hardware issues, too:
[ 103.332068] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 103.332077] ata1.00: BMDMA stat 0x26
[ 103.332083] ata1.00: failed command: WRITE DMA EXT
[ 103.332092] ata1.00: cmd 35/00:98:68:49:90/00:06:1a:00:00/e0 tag 0 dma
864256 out
res 51/84:87:79:4e:90/84:01:1a:00:00/e0 Emask 0x30
(host bus error)
[ 103.332097] ata1.00: status: { DRDY ERR }
[ 103.332101] ata1.00: error: { ICRC ABRT }
[ 103.332112] ata1: soft resetting link
[ 103.524483] ata1.00: configured for UDMA/133
[ 103.524504] ata1: EH complete
Thanks
** Also affects: account-plugins (Ubuntu)
Importance: Undecided
Status: New
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1604583
Title:
Crash occurred while system was unattended, installing the KDE before
erradicating Gnome - 20160719-1239
Status in account-plugins package in Ubuntu:
New
Status in ktp-accounts-kcm package in Ubuntu:
New
Bug description:
Brief description of incident:
As the default Gnome Desktop Environment was still present and active, the
KDE was being installed using 'apt-get install kubuntu-desktop'. Upon returning
to a sleeping screen, tapping the KB/Mouse, the system woke the screen only to
display a dialog box triggered to generate a bug report for whatever error
occurred during the installation process.
System and Package details:
Description: Ubuntu 16.04 LTS
Release: 16.04
Package ID: kubuntu-desktop
Package: Kubuntu Plasma Desktop/Netbook system
Installed: 1.338
Candidate: 1.338
Version table:
*** 1.338 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64
Packages
100 /var/lib/dpkg/status
Steps to reproduce:
1) Boot to the desktop of Ubuntu 16.04 with the default GNOME desktop
environment
2) Open a terminal window
3) Type the following and press the Enter key to submit the command:
sudo apt-get install kubuntu-desktop
Expected results:
KDE package should install without incident.
Actual results:
KDE package installed, and is still installing, but generated errors
triggering the automated creation of this bug report.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kde-config-telepathy-accounts (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Jul 19 12:19:46 2016
DuplicateSignature:
package:kde-config-telepathy-accounts:(not installed)
Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
(--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
ErrorMessage: trying to overwrite
'/usr/share/accounts/services/google-im.service', which is also in package
account-plugin-google 0.12+16.04.20160126-0ubuntu1
InstallationDate: Installed on 2016-06-30 (19 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.12~ubuntu16.04.1
SourcePackage: ktp-accounts-kcm
Title: package kde-config-telepathy-accounts (not installed) failed to
install/upgrade: trying to overwrite
'/usr/share/accounts/services/google-im.service', which is also in package
account-plugin-google 0.12+16.04.20160126-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1604583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604516] Re: errors
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1604516 Title: errors Status in xorg package in Ubuntu: New Bug description: Errors ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.45.11 Tue May 17 18:25:03 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 19 23:29:42 2016 DistUpgraded: 2016-07-06 20:36:48,274 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.45.11, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.45.11, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:067d] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GK107M [GeForce GT 640M] [1025:067d] InstallationDate: Installed on 2016-03-11 (129 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire M3-581TG ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=33d6299c-51b9-4473-8383-8676d7735358 ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-07-06 (13 days ago) dmi.bios.date: 10/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: MA50_HX dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd10/22/2012:svnAcer:pnAspireM3-581TG:pvrV1.13:rvnAcer:rnMA50_HX:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire M3-581TG dmi.product.version: V1.13 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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: Tue Jul 19 23:06:25 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1604516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604587] [NEW] PCI/internal sound card not detected
Public bug reported: I updated 16.04 and rebooted. No sound on any applications. Checked to see if sound card was detected with aplay. None detected. Ran lspci. Shows audio device Intel Corporation Sunrise Point-H HD Audio (rev 31) Sound working prior to installing last updates. No hardware changes in the interim. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jul 19 16:01:29 2016 InstallationDate: Installed on 2016-06-07 (42 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: H170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/31/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** 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/1604587 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I updated 16.04 and rebooted. No sound on any applications. Checked to see if sound card was detected with aplay. None detected. Ran lspci. Shows audio device Intel Corporation Sunrise Point-H HD Audio (rev 31) Sound working prior to installing last updates. No hardware changes in the interim. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jul 19 16:01:29 2016 InstallationDate: Installed on 2016-06-07 (42 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: H170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/31/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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/1604587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585771] Re: Automatic security upgrades are always enabled
Tested:
a37843379dd7061c2c1dc87ed215a284 *xenial-server-amd64.iso
And selected "No Automatic updates" when prompted.
After install there is no longer a /etc/apt/apt.conf.d/20auto-upgrades
file present.
ubuntu@ubuntu:~$ cat /etc/apt/apt.conf.d/20auto-upgrades
cat: /etc/apt/apt.conf.d/20auto-upgrades: No such file or directory
ubuntu@ubuntu:~$ head -n 8 /etc/apt/apt.conf.d/50unattended-upgrades
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
};
$ grep -nr "APT::Periodic::Unattended-Upgrade.*1.*" /etc/apt/apt.conf.d/*
ubuntu@ubuntu:~$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1585771
Title:
Automatic security upgrades are always enabled
Status in pkgsel package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
New
Status in pkgsel source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Xenial:
New
Bug description:
After installing 16.04 server and selecting the option "no automatic
upgrades" the system will still be configured to automatically perform
security upgrades.
$ cat /etc/apt/apt.conf.d/20auto-upgrades
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
$ head -n 8 /etc/apt/apt.conf.d/50unattended-upgrades
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
//"${distro_id}:${distro_codename}-updates";
//"${distro_id}:${distro_codename}-proposed";
//"${distro_id}:${distro_codename}-backports";
};
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pkgsel/+bug/1585771/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
I apt purge'ed binfmt-support from my system and I'm still able to comment here :) We'll see if this fixes the issue. If it does, why was it even installed on my system by default to begin with? -- 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/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://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 1604442] Re: Keyboard stays on screen after leaving an application
On 19/07/2016 17:28, Daniel d'Andrada wrote: > I guess the only way forward is for you to > run a custom unity8 with debug logging specific for tracking this issue. I would provide that, naturally. -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
Still seeing this on xenial enough that I've written a script to perform the umounting when LXD gets stuck. Do I even need binfmt_misc on my system? Can I just remove it or would that break something? -- 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/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598010] Re: cellular data switch disabled until SIM selected in settings
** Changed in: canonical-devices-system-image Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1598010 Title: cellular data switch disabled until SIM selected in settings Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-network package in Ubuntu: Confirmed Bug description: Cellular data switch is disabled on nexus 4. rc_proposed: r476 Ubuntu Image Part: 20160701 Mobile data cannot be activated on this device (possibly others) as the cellular data switch in settings and in the indicator are disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
Thanks, Lukas! I've got an MP up. My bad. -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604576] [NEW] PCI/internal sound card not detected
Public bug reported: Fresh install of Xubuntu 16.04 on my recently bought HP ENVY All-In-One Desktop with Bang & Olufsen sound onboard. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Jul 19 17:34:55 2016 InstallationDate: Installed on 2016-07-02 (16 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: AMI dmi.bios.version: A0.04 dmi.board.asset.tag: 3CR5430742 dmi.board.name: 2B3E dmi.board.vendor: HP dmi.board.version: 1.05 dmi.chassis.asset.tag: 3CR5430742 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrA0.04:bd09/01/2015:svnHP:pn24-n014:pvr1.05:rvnHP:rn2B3E:rvr1.05:cvnHP:ct13:cvr: dmi.product.name: 24-n014 dmi.product.version: 1.05 dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-03T16:08:29.229881 ** 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/1604576 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Fresh install of Xubuntu 16.04 on my recently bought HP ENVY All-In- One Desktop with Bang & Olufsen sound onboard. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Tue Jul 19 17:34:55 2016 InstallationDate: Installed on 2016-07-02 (16 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: AMI dmi.bios.version: A0.04 dmi.board.asset.tag: 3CR5430742 dmi.board.name: 2B3E dmi.board.vendor: HP dmi.board.version: 1.05 dmi.chassis.asset.tag: 3CR5430742 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrA0.04:bd09/01/2015:svnHP:pn24-n014:pvr1.05:rvnHP:rn2B3E:rvr1.05:cvnHP:ct13:cvr: dmi.product.name: 24-n014 dmi.product.version: 1.05 dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-03T16:08:29.229881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1604576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
** Branch linked: lp:~mterry/unity8/fix-indicator-profile -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604442] Re: Keyboard stays on screen after leaving an application
Can't reproduce it. unity8 blindly obeys the OSK surface state. unity8 will show it as long as it is live and its state is visible (as in not minimized or hidden. If maliit crashed, unity8 would dismiss the surface. There's nothing particularly interesting in that unity8.log. unity8 doesn't log OSK surface state. If you still see this issue sometimes but not enough to provide good steps on how to reproduce it, I guess the only way forward is for you to run a custom unity8 with debug logging specific for tracking this issue. ** Changed in: unity8 (Ubuntu) Status: New => Incomplete -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: Incomplete Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1472639] Re: apparmor profile denied for kerberos: /run/.heim_org.h5l.kcm-socket
Hi, >From what I can tell, looking at the existing slapd apparmor profile, it does not include access to the kcm socket in /run as you say. However, I've yet to discover how to have slapd attempt to access this particular socket. I've examined a number of Kerberos + OpenLDAP setups and there's no easy answer on how to setup and configure this combination and certainly no indication which one of those would trigger such an access. Is there any additional information you can provide to help narrow down what possible configuration is needed and which command or action would trigger? I'll start reading the LDAP server code to see if I can understand a bit more what the KDC socket is doing but in the mean time, I'd like as much detail as possible. Note, the version mentioned 2.4.40 appeared between vivid and wily releases; Trusty has 2.4.31 and Xenial/Yakkety are at 2.4.42. If possible, it would be useful to know if this can be reproduced on Xenial or Yakkety; or if it's only on the older releases (Trusty and Precise would be affected). ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1472639 Title: apparmor profile denied for kerberos: /run/.heim_org.h5l.kcm-socket Status in openldap package in Ubuntu: Incomplete Bug description: The slapd apparmor profile doesn't allow access to /run/.heim_org.h5l .kcm-socket which is used by kerberos: apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" name="/run/.heim_org.h5l.kcm-socket" pid=61289 comm="slapd" requested_mask="wr" denied_mask="wr" fsuid=389 ouid=0 This is as of 2.4.40+dfsg-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1472639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604374] Re: Lock screen/greeter shown when switching user sessions
Do you get that same "staying black" behavior when switching between two unity7 sessions as well? -- 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/1604374 Title: Lock screen/greeter shown when switching user sessions Status in unity8 package in Ubuntu: In Progress Bug description: I have two users one set to use Unity7 and one using Unity8. Switching from 7 to 8 I login at the normal prompt then several seconds later the greeter is shown and need to login again. Switching from 8 to 7 is similar, login then get the lock screen. In this case the screen is black after the first login until you provide some mouse input. My settings are set to lock the screen on suspend or when screen goes off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603463] Re: Spelling mistake in an error string - cehcking
** Changed in: apport (Ubuntu) Importance: Undecided => Low ** No longer affects: ubiquity (Ubuntu) -- 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/1603463 Title: Spelling mistake in an error string - cehcking Status in apport package in Ubuntu: In Progress Bug description: There is a spelling mistake in this error string: "The system log from your installation contains an error. The specific error commonly occurs when there is an issue with the disk to which you are trying to install Ubuntu. It is recommended that you back up important data on your disk and investigate the situation. Measures you might take include cehcking cable connections for your disks and using software tools to investigate the health of your hardware." "cehcking" instead of "checking". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1603463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michael Terry (mterry) -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
By the way the commit which fixed that KDE bug is: http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu- qt/trunk/revision/189 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604442] Re: Keyboard stays on screen after leaving an application
Or dates even -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: New Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604442] Re: Keyboard stays on screen after leaving an application
Those revision numbers are useless. Just flashed my krillin with: ubuntu-device-flash touch ubuntu-system --channel ubuntu-touch/rc-proposed/ubuntu Revision number is 535. If you wanna give us reference points, package versions would work perfectly. -- 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/1604442 Title: Keyboard stays on screen after leaving an application Status in unity8 package in Ubuntu: New Bug description: Krillin, rc-proposed, r388 Between today and yesterday it happened twice that the keyboard did not hide after switching away from an application. The first time I think maliit crashed, I could interact with the system but the keyboard was unresponsive. I have no other info to provide on this, unfortunately. The second time I was writing a message on Telegram, then I swiped away to get to the switcher and the keyboard did not hide. At that point I dismissed the keyboard by dragging it out of the view (top to bottom drag). This is what I think is the unity8.log excerpt for the "second" case, i.e. swiping away from telegram and then hiding the keyboar while I was inside the switcher: http://pastebin.ubuntu.com/20043016/ Unfortunately I have no other details to report... I'd say there is a regression somewhere in between r386 and r388 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604563] [NEW] Install interrupted
Public bug reported: Goes to automatic report as soon as I try to install it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 19 14:50:39 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2016-07-12 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=defcb969-2ba0-4ba2-b311-3118142048bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42386C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42386C8 dmi.modalias: dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F42386C8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F42386C8: dmi.product.name: iMac7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.2 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: Tue Jul 19 09:59:09 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1604563 Title: Install interrupted Status in xorg package in Ubuntu: New Bug description: Goes to automatic report as soon as I try to install it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jul 19 14:50:39 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2016-07-12 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. iMac7,1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=defcb969-2ba0-4ba2
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Confirmed Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556389] Re: unnable to send SMS to multiple contact
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1556389 Title: unnable to send SMS to multiple contact Status in messaging-app package in Ubuntu: Confirmed Bug description: From about 2 our 3 month, I am unable to send SMS to multiple contact. I can write the SMS, add the contacts, but then when I press send nothing happen. No issue when there is just one contact, but as soon as I have two or more, it does not work anymore. What log do you need for this bug? I have ubuntu 15.04 , and the messaging-app is 15.04.20160109.1-0ubunutu1 Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1556389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604374] Re: Lock screen/greeter shown when switching user sessions
The OSK is just something else I was playing around with and can be ignored When it goes back to unity 7 the screen stays black until I interact with it with a mouse move and click, then I get the additional lock dialog -- 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/1604374 Title: Lock screen/greeter shown when switching user sessions Status in unity8 package in Ubuntu: In Progress Bug description: I have two users one set to use Unity7 and one using Unity8. Switching from 7 to 8 I login at the normal prompt then several seconds later the greeter is shown and need to login again. Switching from 8 to 7 is similar, login then get the lock screen. In this case the screen is black after the first login until you provide some mouse input. My settings are set to lock the screen on suspend or when screen goes off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
@jim that kinda sounds like media-hub or some service got into a loop would be interesting to run top command when tat happens, we could check the media-hub log also. -- 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
** Changed in: indicator-sound (Ubuntu) Status: New => Invalid ** Changed in: canonical-devices-system-image Assignee: Pat McGowan (pat-mcgowan) => Michał Sawicz (saviq) -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556330] Update Released
The verification of the Stable Release Update for curl 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 curl in Ubuntu. https://bugs.launchpad.net/bugs/1556330 Title: upstream curl bug #1371: p12 client certificates code is broken Status in curl package in Ubuntu: Fix Released Status in curl source package in Trusty: Fix Released Bug description: [Impact] The bug makes it impossible to use PKCS#12 secure storage of client certificates and private keys with any affected Ubuntu releases. The fix is one line fixing a broken switch statement and was already tested against Ubuntu 14.04 LTS with a rebuilt curl package. This was fixed in upstream libcurl in the following bug: https://sourceforge.net/p/curl/bugs/1371/ The bug fix consists of one missing break statement at the end of a case in a switch statement. I personally patched the bug using source code release curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it does indeed fix the bug and all of the package's tests still pass afterwards. [Test Case] The bug can be reproduced using the following libcurl parameters (even via CLI, pycurl, etc.). CURLOPT_SSLCERTTYPE == "P12" CURLOPT_SSLCERT = path to PKCS#12 CURLOPT_SSLKEY = path to PKCS#12 CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed Basically, just use a PKCS#12 format client certificate and private key against some certificate protected web server. [Regression Potential] If it could possibly break anything, which is extraordinarily unlikely, it would break one of the three client certificate formats (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already broken due to the bug. Client certificates of all three types could be checked to prevent this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken
This bug was fixed in the package curl - 7.35.0-1ubuntu2.7 --- curl (7.35.0-1ubuntu2.7) trusty; urgency=medium [ Matthew Hall ] * debian/patches/libcurl_broken_pkcs12.patch: - fix p12 client certificates (LP: #1556330) -- Gianfranco Costamagna Sat, 12 Mar 2016 17:22:33 +0100 ** Changed in: curl (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1556330 Title: upstream curl bug #1371: p12 client certificates code is broken Status in curl package in Ubuntu: Fix Released Status in curl source package in Trusty: Fix Released Bug description: [Impact] The bug makes it impossible to use PKCS#12 secure storage of client certificates and private keys with any affected Ubuntu releases. The fix is one line fixing a broken switch statement and was already tested against Ubuntu 14.04 LTS with a rebuilt curl package. This was fixed in upstream libcurl in the following bug: https://sourceforge.net/p/curl/bugs/1371/ The bug fix consists of one missing break statement at the end of a case in a switch statement. I personally patched the bug using source code release curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it does indeed fix the bug and all of the package's tests still pass afterwards. [Test Case] The bug can be reproduced using the following libcurl parameters (even via CLI, pycurl, etc.). CURLOPT_SSLCERTTYPE == "P12" CURLOPT_SSLCERT = path to PKCS#12 CURLOPT_SSLKEY = path to PKCS#12 CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed Basically, just use a PKCS#12 format client certificate and private key against some certificate protected web server. [Regression Potential] If it could possibly break anything, which is extraordinarily unlikely, it would break one of the three client certificate formats (most likely PKCS#12 but also PEM or DER). Note 1/3 formats is already broken due to the bug. Client certificates of all three types could be checked to prevent this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
$ bzr annotate indicatorsmanager.cpp
1789.5.5 michael.te...@canonical.com20160608 |
new_indicator->setProfile(m_profile.replace(QStringLiteral("phone"),
QStringLiteral("desktop")));
--
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/1604205
Title:
[regression?] Sound menu shows "Mute" instead of "Silent Mode" on
phone
Status in Canonical System Image:
Confirmed
Status in indicator-sound package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu:
New
Bug description:
On my krillin, I'm seeing "Mute" where "Silent Mode" used to be.
I had thought it was Mute on desktops and Silent Mode on phones (with
different behaviors).
Maybe this change was intentional, but on the off chance it wasn't,
here's a bug.
current build number: 387
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-07-16 17:51:09
version version: 387
version ubuntu: 20160716
version device: 20160606-ab415b2
version custom: 20160701-981-38-14
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604497] Re: Pulseaudio does not start
I should have said that pulseaudio is included in the startup applications. -- 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/1604497 Title: Pulseaudio does not start Status in pulseaudio package in Ubuntu: New Bug description: I'm using Ubuntu Mate 16.04 with the current updates. When I start the computer, pulseaudio is not working after I've logged in. If I type: start-pulseaudio-x11 from the command line, I get "Connection failure: Connection refused pa_context_connect() failed: Connection refused" and I cannot play any sound. If I type pulseaudio& on the command line, I can get sound in some applications (e.g. Audacity) but not others (e.g. Firefox or other browsers). At some point a command line message appears that says: "E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." I'm not clear why there's a reference to bluez5-util, since I don't have bluetooth on my machine. 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 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 19 17:43:11 2016 InstallationDate: Installed on 2016-05-10 (70 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Z97X-UD3H, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1604497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working
** Tags removed: verification-done ** Tags added: verification-done-xenial ** Tags added: verification-needed-trusty verification-needed-wily -- 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/1529815 Title: InfiniBand DHCP flow with PRA and DHCP relay not working Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Wily: Fix Committed Status in isc-dhcp source package in Xenial: Fix Released Bug description: [Impact] * Infiniband users relying on DHCP can't use DHCP relay. [Test Case] * Comment #13 * Mellanox has tested themselves. * Clear way of knowing if fix worked (tcpdump). [Regression Potential] * Only related to Infiniband. * Infiniband support could stop working (unlikely, already tested). [Other Info] DHCP client is sending discover with Unicast type request for the offer, in this configuration of IB to ETH through a relay we need the type to be broadcast. The issue is that when using dhclient from the client on Ubuntu (and only on Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in unicast instead of broadcast. It seems there is no way to correct this from the client side using dhclient configuration file. this issue exist even when we use always-broadcast statement in configuration file. in other vendors we see that discover request type is broadcast. attached pcap files from working (other vendor) and not working (Ubuntu) clients. DHCP CLIENT (IPoIB) Ubuntu 14.04 kernel 3.13.0-74 Mellanox OFED 3.1-1.0.3 or inbox driver isc-dhcp-client 4.2.4-7ubuntu12.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
Maybe a side effect of http://bazaar.launchpad.net/~unity-team/unity8/trunk/changes/2543?start_revid=2543 -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
I'm on rc-proposed for flo and saw Mute as well, should it be on tablets as well? -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.25.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
Looks like this might be a unity8 issue. What's going on here is the desktop and desktop_greeter profiles export menus with a "Mute" menuitem, and the phone counterparts export menus with "Silent Mode". This code hasn't changed in indicator-sound, so the most likely thing is that something's changed in unity8 to use a different profile -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604374] Re: Lock screen/greeter shown when switching user sessions
The 7-to-8 issue is a problem with unity8. I've got a branch attached. I don't know what's going on with your 8-to-7 issue, but I can't reproduce it myself. I don't actually recognize what's going on with your screen in that video -- you have an OSK? With some white box in the middle of the screen? ** Package changed: lightdm (Ubuntu) => unity8 (Ubuntu) ** Changed in: unity8 (Ubuntu) Status: New => In Progress -- 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/1604374 Title: Lock screen/greeter shown when switching user sessions Status in unity8 package in Ubuntu: In Progress Bug description: I have two users one set to use Unity7 and one using Unity8. Switching from 7 to 8 I login at the normal prompt then several seconds later the greeter is shown and need to login again. Switching from 8 to 7 is similar, login then get the lock screen. In this case the screen is black after the first login until you provide some mouse input. My settings are set to lock the screen on suspend or when screen goes off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563768] Re: Bluetooth HFP indicates a permanent ongoing call
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1563768 Title: Bluetooth HFP indicates a permanent ongoing call Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the upgrade to Bluez5 I can't have my Phone connected to my car (BMW 1) any more. It pairs fine, but as soon as the connection is established, the car's head unit thinks there is a phone call ongoing to the number "" (yes, it displays asterisks as the target number on the car). This has the effect that I cannot listen to any music in the car while the phone is connected as the head unit obviously mutes all other sound and only relays the Hands-Free audio between the car and the phone. Pressing the hangup button on the car has no effect. Disconnecting the phone is the only way to make the phone call go away. This is a regression with OTA-9. It was working perfectly fine before the Bluez5 upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594114] Re: Camera-app crashes when processing HDR photo
same on arale rc-proposed -- 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/1594114 Title: Camera-app crashes when processing HDR photo Status in camera-app package in Ubuntu: Confirmed Bug description: BQ E5 OTA-11, but it has been like this since i got it. (~january 2016) 7/10 when I take a photo with HDR enabled, the app crashes while processing the photo. I get the spinning wheel and then it dies and the photo is not saved. Please let me know what logs i can give you to help you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1594114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594114] Re: Camera-app crashes when processing HDR photo
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: camera-app (Ubuntu) Status: New => Confirmed -- 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/1594114 Title: Camera-app crashes when processing HDR photo Status in camera-app package in Ubuntu: Confirmed Bug description: BQ E5 OTA-11, but it has been like this since i got it. (~january 2016) 7/10 when I take a photo with HDR enabled, the app crashes while processing the photo. I get the spinning wheel and then it dies and the photo is not saved. Please let me know what logs i can give you to help you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1594114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604374] Re: Lock screen/greeter shown when switching user sessions
** Branch linked: lp:~mterry/unity8/fix-greeter-race -- 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/1604374 Title: Lock screen/greeter shown when switching user sessions Status in lightdm package in Ubuntu: New Bug description: I have two users one set to use Unity7 and one using Unity8. Switching from 7 to 8 I login at the normal prompt then several seconds later the greeter is shown and need to login again. Switching from 8 to 7 is similar, login then get the lock screen. In this case the screen is black after the first login until you provide some mouse input. My settings are set to lock the screen on suspend or when screen goes off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1604374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604205] Re: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1604205 Title: [regression?] Sound menu shows "Mute" instead of "Silent Mode" on phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: On my krillin, I'm seeing "Mute" where "Silent Mode" used to be. I had thought it was Mute on desktops and Silent Mode on phones (with different behaviors). Maybe this change was intentional, but on the off chance it wasn't, here's a bug. current build number: 387 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-07-16 17:51:09 version version: 387 version ubuntu: 20160716 version device: 20160606-ab415b2 version custom: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604205/+subscriptions -- Mailing list: https://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 1596958] Re: package whoopsie 0.2.52.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Yeah, thats a lot of communication happening. I appreciate your support. Please find the output below. ??5?? /lib/modules/4.4.0-24-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko ??5?? /lib/modules/4.4.0-24-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko ??5?? /lib/modules/4.4.0-22-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko ??5?? /lib/modules/4.4.0-22-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko ??5?? /usr/bin/easy_install ??5?? /usr/lib/python2.7/dist-packages/setuptools-20.7.0.egg-info/dependency_links.txt ??5?? /usr/lib/python2.7/dist-packages/setuptools-20.7.0.egg-info/top_level.txt ??5?? /usr/lib/python2.7/dist-packages/setuptools-20.7.0.egg-info/zip-safe ??5?? /usr/lib/python2.7/dist-packages/setuptools-20.7.0.egg-info/PKG-INFO ??5?? /usr/lib/python2.7/dist-packages/setuptools-20.7.0.egg-info/entry_points.txt ??5?? /usr/lib/python2.7/dist-packages/easy_install.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/depends.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/extension.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/ssl_support.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/package_index.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/__init__.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/extern/__init__.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/msvc9_support.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/lib2to3_ex.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/sdist.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/install_scripts.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/install.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/saveopts.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/install_lib.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/alias.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/test.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/__init__.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/bdist_egg.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/bdist_rpm.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/install_egg_info.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/setopt.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/register.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/rotate.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/bdist_wininst.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/develop.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/upload_docs.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/build_py.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/build_ext.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/command/upload.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/version.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/unicode_utils.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/windows_support.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/script.tmpl ??5?? /usr/lib/python2.7/dist-packages/setuptools/dist.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/py26compat.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/py27compat.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/archive_util.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/py31compat.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/utils.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/script (dev).tmpl ??5?? /usr/lib/python2.7/dist-packages/setuptools/launch.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/sandbox.py ??5?? /usr/lib/python2.7/dist-packages/setuptools/site-patch.py ??5?? /usr/lib/rhythmbox/plugins/rbzeitgeist/__pycache__/rbzeitgeist.cpython-35.opt-1.pyc ??5?? /usr/lib/rhythmbox/plugins/rbzeitgeist/__pycache__/rbzeitgeist.cpython-35.pyc dpkg: error: cannot compute MD5 hash for file '/etc/mysql/conf.d/mysql.cnf': failed to read (Is a directory) On Tue, Jul 19, 2016 at 2:39 PM, ALJI Mohamed wrote: > This is more complicated than I thought : > * sudo dpkg --verify > > Le mar. 19 juil. 2016 19:01, ashokvardhankari > a écrit : > > > Hello Alji, > > > > Output for sudo service plymouth status > > > > plymouth-quit.service - Terminate Plymouth Boot Screen > >Loaded: loaded (/lib/systemd/system/plymouth-quit.service; static; > > vendor preset: enabled) > >Active: inactive (dead) > > > > > > On Tue, Jul 19, 2016 at 1:28 PM, ALJI Mohamed > wrote: > > > > > Please, try this and share with u
Re: [Touch-packages] [Bug 1596958] Re: package whoopsie 0.2.52.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This is more complicated than I thought : * sudo dpkg --verify Le mar. 19 juil. 2016 19:01, ashokvardhankari a écrit : > Hello Alji, > > Output for sudo service plymouth status > > plymouth-quit.service - Terminate Plymouth Boot Screen >Loaded: loaded (/lib/systemd/system/plymouth-quit.service; static; > vendor preset: enabled) >Active: inactive (dead) > > > On Tue, Jul 19, 2016 at 1:28 PM, ALJI Mohamed wrote: > > > Please, try this and share with us the. Output > > > > * sudo servicr plymouth status > > > > Le lun. 18 juil. 2016 15:46, ashokvardhankari < > ashokvardhank...@gmail.com> > > a écrit : > > > > > Hello Alji, > > > > > > Please find the output for locate plymouth below. > > > > > > /bin/plymouth > > > /etc/alternatives/default.plymouth > > > /etc/alternatives/default.plymouth.grub > > > /etc/alternatives/text.plymouth > > > /etc/init.d/plymouth > > > /etc/init.d/plymouth-log > > > /etc/rc0.d/K01plymouth > > > /etc/rc2.d/S05plymouth > > > /etc/rc3.d/S05plymouth > > > /etc/rc4.d/S05plymouth > > > /etc/rc5.d/S05plymouth > > > /etc/rc6.d/K01plymouth > > > /etc/rcS.d/S02plymouth-log > > > /lib/lsb/init-functions.d/99-plymouth > > > /lib/systemd/system/plymouth-halt.service > > > /lib/systemd/system/plymouth-kexec.service > > > /lib/systemd/system/plymouth-log.service > > > /lib/systemd/system/plymouth-poweroff.service > > > /lib/systemd/system/plymouth-quit-wait.service > > > /lib/systemd/system/plymouth-quit.service > > > /lib/systemd/system/plymouth-read-write.service > > > /lib/systemd/system/plymouth-reboot.service > > > /lib/systemd/system/plymouth-start.service > > > /lib/systemd/system/plymouth-switch-root.service > > > /lib/systemd/system/plymouth.service > > > /lib/systemd/system/systemd-ask-password-plymouth.path > > > /lib/systemd/system/systemd-ask-password-plymouth.service > > > /lib/systemd/system/halt.target.wants/plymouth-halt.service > > > > > > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-start.service > > > > > > > > > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-switch-root.service > > > /lib/systemd/system/kexec.target.wants/plymouth-kexec.service > > > /lib/systemd/system/multi-user.target.wants/plymouth-quit-wait.service > > > /lib/systemd/system/multi-user.target.wants/plymouth-quit.service > > > /lib/systemd/system/poweroff.target.wants/plymouth-poweroff.service > > > /lib/systemd/system/reboot.target.wants/plymouth-reboot.service > > > /lib/systemd/system/sysinit.target.wants/plymouth-read-write.service > > > /lib/systemd/system/sysinit.target.wants/plymouth-start.service > > > /sbin/plymouthd > > > /usr/lib/x86_64-linux-gnu/plymouth > > > /usr/lib/x86_64-linux-gnu/plymouth/details.so > > > /usr/lib/x86_64-linux-gnu/plymouth/label.so > > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-generate-initrd > > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-populate-initrd > > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-update-initrd > > > /usr/lib/x86_64-linux-gnu/plymouth/renderers > > > /usr/lib/x86_64-linux-gnu/plymouth/script.so > > > /usr/lib/x86_64-linux-gnu/plymouth/text.so > > > /usr/lib/x86_64-linux-gnu/plymouth/tribar.so > > > /usr/lib/x86_64-linux-gnu/plymouth/ubuntu-text.so > > > /usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so > > > /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so > > > /usr/share/plymouth > > > /usr/share/apport/package-hooks/source_plymouth.py > > > /usr/share/doc/libplymouth4 > > > /usr/share/doc/plymouth > > > /usr/share/doc/plymouth-label > > > /usr/share/doc/plymouth-theme-ubuntu-logo > > > /usr/share/doc/plymouth-theme-ubuntu-text > > > /usr/share/doc/libplymouth4/changelog.Debian.gz > > > /usr/share/doc/libplymouth4/copyright > > > /usr/share/doc/plymouth/NEWS.Debian.gz > > > /usr/share/doc/plymouth/README > > > /usr/share/doc/plymouth/README.Debian > > > /usr/share/doc/plymouth/TODO > > > /usr/share/doc/plymouth/TODO.Debian > > > /usr/share/doc/plymouth/changelog.Debian.gz > > > /usr/share/doc/plymouth/copyright > > > /usr/share/doc/plymouth-label/changelog.Debian.gz > > > /usr/share/doc/plymouth-label/copyright > > > /usr/share/doc/plymouth-theme-ubuntu-logo/changelog.Debian.gz > > > /usr/share/doc/plymouth-theme-ubuntu-logo/copyright > > > /usr/share/doc/plymouth-theme-ubuntu-text/changelog.Debian.gz > > > /usr/share/doc/plymouth-theme-ubuntu-text/copyright > > > /usr/share/initramfs-tools/hooks/plymouth > > > /usr/share/initramfs-tools/scripts/init-bottom/plymouth > > > /usr/share/initramfs-tools/scripts/init-premount/plymouth > > > /usr/share/initramfs-tools/scripts/panic/plymouth > > > /usr/share/lintian/overrides/libplymouth4 > > > /usr/share/lintian/overrides/plymouth > > > /usr/share/man/man1/plymouth.1.gz > > > /usr/share/man/man8/plymouth.8.gz > > > /usr/share/man/man8/plymouthd.8.gz > > > /usr/share/plymouth/themes > > > /usr/share/plymouth/ubuntu-logo.png > > > /usr/share/plymouth/themes/default.grub > > > /usr/share/plymouth/themes/default.plymouth > > > /usr/share/plymout
[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window
Michael, thanks for the investigation! That check looks related, and links to https://bugs.kde.org/show_bug.cgi?id=254066. Do you have any idea how to fix your issue and not introduce regressions for that bug? I do not know if there is any active maintainer for libdbusmenu-qt, but I'm subscribing Nick and David who last touched the code — maybe they are still interested in this code. ** Bug watch added: KDE Bug Tracking System #254066 https://bugs.kde.org/show_bug.cgi?id=254066 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1604009 Title: Empty menus in global app-menu in VirtualBox second window Status in libdbusmenu-qt package in Ubuntu: New Bug description: Reporting this following this IRC discussion: https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00 The basic summary: when I run a two-screen/two-window virtual machine with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu, the menus are empty when the second screen window has the input focus. During start-up I get a number (55) of these messages on the console: Qt WARNING: void DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*, int, int, const QStringList&): No id for action and a number (7) of these: Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const QStringList&, DBusMenuLayoutItem&): Condition failed: menu Then another 55 of the first and two of the second. Looking at the interesting parts of the VirtualBox source code, I see that the menu items for the first window (menu displayed correctly) and the second (not displayed) share the same QAction objects. A very quick guess is that this might be triggering the condition in DBusMenuExporterPrivate::addMenu(). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 18 15:44:00 2016 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.1 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.1 InstallationDate: Installed on 2016-05-31 (48 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: libdbusmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)
The bug affects 11 people atm so hard to say -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1493574 Title: [vegeta] Phone app makes screen stay black during call (so you can't hang up) Status in Canonical System Image: Incomplete Status in vegetahd: New Status in powerd package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: A similar, if not the same bug, has been reported to be fixed for OTA6. This bug report explains that it's no necessary to wait for a minute or so on the phone call, but the screen turns black immediately, and doesn't turn back on again to allow hanging up via a screen control. Potential duplicate: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1483127 Device: Aquaris E5 HD Ubuntu Edition OS version: 15.04 (r5) A) Incoming phone call: - Accept the incoming call by sliding the grey middle button to the green button - Watch the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (continued from above, screen stays black after taking it away from your ear) - Press the screen lock/unlock button (= button above volume control) - Screen with phone app shows for about half a second, then turns black again - Press the screen lock/unlock button again, and try to press the red hangup button quickly - Repeat the previous step until hanging up succeeds B) Outbound phone call: - Open the phone app - Slide up Recent calls list from bottom edge, select a phone number - Press green dial button to initiate the call - Watch the phone dialling and the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (same procedure as in A. above) - Difference in behavior: * In some calls after pressing the lock/unlock button for the first time the screen stays alight (doesn't turn black again after half a second). Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list: In both cases, covering/uncovering the proximity sensor should turn the screen on, if the screen has not been turned off with the power button. (This is not happening.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604403] Re: Cannot access camera
** Also affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- 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/1604403 Title: Cannot access camera Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: New Bug description: Cannot access camera (see attached screenshots), it happened out of the blue while taking pictures, the camera app has access to hardware [c2] you need to restart the phone to use the camera again arale rc-proposed/ r381 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604519] [NEW] sudden akku drainage
Public bug reported: On my BQ E5 running OTA 11 I do realize for some time now sudden akku drainages, see attached screenshots. At least on one occassion lately I did find out that this happened when I was taking some photos. For the first couple of photos I did had the normal shutter sound. After a few photos the shutter went silent and the akku started to loose power. After Rebooting the phone the drainage usually stops occasionally it happens again. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Attachment added: "scrrenshots showing akku drainage issue" https://bugs.launchpad.net/bugs/1604519/+attachment/4703624/+files/screenshots%20akku%20drainage.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1604519 Title: sudden akku drainage Status in indicator-power package in Ubuntu: New Bug description: On my BQ E5 running OTA 11 I do realize for some time now sudden akku drainages, see attached screenshots. At least on one occassion lately I did find out that this happened when I was taking some photos. For the first couple of photos I did had the normal shutter sound. After a few photos the shutter went silent and the akku started to loose power. After Rebooting the phone the drainage usually stops occasionally it happens again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1604519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Recently I was taking some photos with my BQ E5. On the first couple of photos I did get the normal shutter sound. After I think maybe 3 or 4 photos there was no shutter sound any more. I am not sure if this goes along with loosing the sound on incoming SMS. BUT I did find that - at least at this last occasion - loosing the shutter sound did go along with a sudden akku drainage. I did experience this akku drainage before (see screenshots), but this time I could tell when it started. Maybe that helps. If you do need any logs let me know. ** Attachment added: "several sceenshots showing akku drainage issue" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1544477/+attachment/4703600/+files/screenshots%20akku%20drainage.zip -- 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 838757] Re: HP hs2340 HSPA+ Mobile Broadband Modem does not work
Also affects 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/838757 Title: HP hs2340 HSPA+ Mobile Broadband Modem does not work Status in modemmanager package in Ubuntu: Confirmed Status in modemmanager package in Debian: New Bug description: Description: Ubuntu 10.04.3 LTS Release: 10.04 network-manager: Installed: 0.8-0ubuntu3.2 I have installed Ubuntu 10.04.2 on HP Probook 6560b. The internal Mobile Broadband Modem is HP hs2340, which is correctly identified. In neither the LTS release or the live CD of Oneiric Ocelot Alpha 3 release does Mobile Broadband work 'out of the box' After fiddling around, I finally got the modem working. The missing bit was to do a hard shutdown from Windows, leaving the modem to an enabled state. After that, the connection worked instantly. Some remarks: = - network-manager should really provide more information to what it is doing. In all previous attempts, network-manager would be doing something for a while with no result or error message - rfkill always listed the hp-wwan as 'not blocked' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/838757/+subscriptions -- Mailing list: https://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 1596958] Re: package whoopsie 0.2.52.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello Alji, Output for sudo service plymouth status plymouth-quit.service - Terminate Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-quit.service; static; vendor preset: enabled) Active: inactive (dead) On Tue, Jul 19, 2016 at 1:28 PM, ALJI Mohamed wrote: > Please, try this and share with us the. Output > > * sudo servicr plymouth status > > Le lun. 18 juil. 2016 15:46, ashokvardhankari > a écrit : > > > Hello Alji, > > > > Please find the output for locate plymouth below. > > > > /bin/plymouth > > /etc/alternatives/default.plymouth > > /etc/alternatives/default.plymouth.grub > > /etc/alternatives/text.plymouth > > /etc/init.d/plymouth > > /etc/init.d/plymouth-log > > /etc/rc0.d/K01plymouth > > /etc/rc2.d/S05plymouth > > /etc/rc3.d/S05plymouth > > /etc/rc4.d/S05plymouth > > /etc/rc5.d/S05plymouth > > /etc/rc6.d/K01plymouth > > /etc/rcS.d/S02plymouth-log > > /lib/lsb/init-functions.d/99-plymouth > > /lib/systemd/system/plymouth-halt.service > > /lib/systemd/system/plymouth-kexec.service > > /lib/systemd/system/plymouth-log.service > > /lib/systemd/system/plymouth-poweroff.service > > /lib/systemd/system/plymouth-quit-wait.service > > /lib/systemd/system/plymouth-quit.service > > /lib/systemd/system/plymouth-read-write.service > > /lib/systemd/system/plymouth-reboot.service > > /lib/systemd/system/plymouth-start.service > > /lib/systemd/system/plymouth-switch-root.service > > /lib/systemd/system/plymouth.service > > /lib/systemd/system/systemd-ask-password-plymouth.path > > /lib/systemd/system/systemd-ask-password-plymouth.service > > /lib/systemd/system/halt.target.wants/plymouth-halt.service > > > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-start.service > > > > > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-switch-root.service > > /lib/systemd/system/kexec.target.wants/plymouth-kexec.service > > /lib/systemd/system/multi-user.target.wants/plymouth-quit-wait.service > > /lib/systemd/system/multi-user.target.wants/plymouth-quit.service > > /lib/systemd/system/poweroff.target.wants/plymouth-poweroff.service > > /lib/systemd/system/reboot.target.wants/plymouth-reboot.service > > /lib/systemd/system/sysinit.target.wants/plymouth-read-write.service > > /lib/systemd/system/sysinit.target.wants/plymouth-start.service > > /sbin/plymouthd > > /usr/lib/x86_64-linux-gnu/plymouth > > /usr/lib/x86_64-linux-gnu/plymouth/details.so > > /usr/lib/x86_64-linux-gnu/plymouth/label.so > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-generate-initrd > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-populate-initrd > > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-update-initrd > > /usr/lib/x86_64-linux-gnu/plymouth/renderers > > /usr/lib/x86_64-linux-gnu/plymouth/script.so > > /usr/lib/x86_64-linux-gnu/plymouth/text.so > > /usr/lib/x86_64-linux-gnu/plymouth/tribar.so > > /usr/lib/x86_64-linux-gnu/plymouth/ubuntu-text.so > > /usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so > > /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so > > /usr/share/plymouth > > /usr/share/apport/package-hooks/source_plymouth.py > > /usr/share/doc/libplymouth4 > > /usr/share/doc/plymouth > > /usr/share/doc/plymouth-label > > /usr/share/doc/plymouth-theme-ubuntu-logo > > /usr/share/doc/plymouth-theme-ubuntu-text > > /usr/share/doc/libplymouth4/changelog.Debian.gz > > /usr/share/doc/libplymouth4/copyright > > /usr/share/doc/plymouth/NEWS.Debian.gz > > /usr/share/doc/plymouth/README > > /usr/share/doc/plymouth/README.Debian > > /usr/share/doc/plymouth/TODO > > /usr/share/doc/plymouth/TODO.Debian > > /usr/share/doc/plymouth/changelog.Debian.gz > > /usr/share/doc/plymouth/copyright > > /usr/share/doc/plymouth-label/changelog.Debian.gz > > /usr/share/doc/plymouth-label/copyright > > /usr/share/doc/plymouth-theme-ubuntu-logo/changelog.Debian.gz > > /usr/share/doc/plymouth-theme-ubuntu-logo/copyright > > /usr/share/doc/plymouth-theme-ubuntu-text/changelog.Debian.gz > > /usr/share/doc/plymouth-theme-ubuntu-text/copyright > > /usr/share/initramfs-tools/hooks/plymouth > > /usr/share/initramfs-tools/scripts/init-bottom/plymouth > > /usr/share/initramfs-tools/scripts/init-premount/plymouth > > /usr/share/initramfs-tools/scripts/panic/plymouth > > /usr/share/lintian/overrides/libplymouth4 > > /usr/share/lintian/overrides/plymouth > > /usr/share/man/man1/plymouth.1.gz > > /usr/share/man/man8/plymouth.8.gz > > /usr/share/man/man8/plymouthd.8.gz > > /usr/share/plymouth/themes > > /usr/share/plymouth/ubuntu-logo.png > > /usr/share/plymouth/themes/default.grub > > /usr/share/plymouth/themes/default.plymouth > > /usr/share/plymouth/themes/details > > /usr/share/plymouth/themes/text > > /usr/share/plymouth/themes/text.plymouth > > /usr/share/plymouth/themes/tribar > > /usr/share/plymouth/themes/ubuntu-logo > > /usr/share/plymouth/themes/ubuntu-text > > /usr/share/plymouth/themes/details/details.plymouth > > /usr/share/plymouth/themes/text/text.plymouth > > /usr/share/plymouth/themes/tribar/tribar.plymo
[Touch-packages] [Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone
I give up. Everything is crashing repeatedly there and I don't know how to control services there as upstart seems no longer used. systemctl also doesn't seem to be working correctly. At least not like it does on the desktop. systemctl list-units for instance fails with: Failed to list units: No such method 'ListUnitsFiltered' ** Changed in: unity8 (Ubuntu) Status: In Progress => Confirmed ** Changed in: unity8 (Ubuntu) Assignee: Daniel d'Andrada (dandrader) => (unassigned) -- 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/1604421 Title: Unity 8 fails to start on staging (xenial) on the phone Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Unity 8 fails to start on staging (=xenial + xenial-overlay) on my krillin. unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows Opening/Closing/Opening/Closing when starting unity8. unity8.log attached. Using ubuntu-touch/staging/bq-aquaris.en channel on krillin. version_detail: ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49 Crash file at http://people.ubuntu.com/~timo- jyrinki/unity8/_usr_bin_unity8.32011.crash Xenial can be flashed on the phone with eg: ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu --developer-mode --password= --wipe --boostrap (ubuntu channel) ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en --developer-mode --password= --wipe --recovery-image recovery-krillin.img (Bq channel) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604509] Re: In the bottom edge component, using preload=true with contentUrl results in an empty page
** Branch linked: lp:~zsombi/ubuntu-ui-
toolkit/pleaseBottomEdgePreloadUrl
--
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/1604509
Title:
In the bottom edge component, using preload=true with contentUrl
results in an empty page
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the bottom edge component, using preload=true with contentUrl
results in an empty page.
For example the following code 'works' with a red rectangle in the
bottom edge:
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
}
But the following code does not and results in a transparent overlay,
the contentItem appears to stay null.
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
}
Note that using contentComponent does work with preloadContent true or false.
See the linked branch for an example of this not working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604509/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604511] Re: `tail -n N` no longer functions, prints all data in specified files instead of only the last N records
Turns out some shells are evil, and it was a failure in the system telling me the correct number of lines (this isn't an Ubuntu SSH client into the server) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1604511 Title: `tail -n N` no longer functions, prints all data in specified files instead of only the last N records Status in coreutils package in Ubuntu: Invalid Bug description: While running nginx install/upgrade tests, I was trying to get the last 10 lines of the /var/log/apt/history.log file. Naturally, I was trying to use 'tail' for this: tail -n 10 /var/log/apt/history.log Instead of only getting the last 10 lines of the file, I get the entire file spit out to me, as if I used 'cat' instead of 'tail'. This would appear to be a MAJOR problem if tail no longer functions as it should. This is on a fully-updated 16.10 server, by the way, so all the updates from the 'yakkety' repository are pulled in. -- ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: coreutils 8.25-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 Date: Tue Jul 19 13:39:31 2016 InstallationDate: Installed on 2016-05-14 (65 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160514) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1604511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604509] Re: In the bottom edge component, using preload=true with contentUrl results in an empty page
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Assignee: (unassigned) => Zsombor Egri (zsombi)
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided => High
--
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/1604509
Title:
In the bottom edge component, using preload=true with contentUrl
results in an empty page
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the bottom edge component, using preload=true with contentUrl
results in an empty page.
For example the following code 'works' with a red rectangle in the
bottom edge:
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
}
But the following code does not and results in a transparent overlay,
the contentItem appears to stay null.
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
}
Note that using contentComponent does work with preloadContent true or false.
See the linked branch for an example of this not working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604509/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604511] [NEW] `tail -n N` no longer functions, prints all data in specified files instead of only the last N records
Public bug reported: While running nginx install/upgrade tests, I was trying to get the last 10 lines of the /var/log/apt/history.log file. Naturally, I was trying to use 'tail' for this: tail -n 10 /var/log/apt/history.log Instead of only getting the last 10 lines of the file, I get the entire file spit out to me, as if I used 'cat' instead of 'tail'. This would appear to be a MAJOR problem if tail no longer functions as it should. This is on a fully-updated 16.10 server, by the way, so all the updates from the 'yakkety' repository are pulled in. -- ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: coreutils 8.25-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 Date: Tue Jul 19 13:39:31 2016 InstallationDate: Installed on 2016-05-14 (65 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160514) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug yakkety ** Description changed: While running nginx install/upgrade tests, I was trying to get the last 10 lines of the /var/log/apt/history.log file. Naturally, I was trying to use 'tail' for this: tail -n 10 /var/log/apt/history.log Instead of only getting the last 10 lines of the file, I get the entire file spit out to me, as if I used 'cat' instead of 'tail'. This would appear to be a MAJOR problem if tail no longer functions as it should. + + This is on a fully-updated 16.10 server, by the way, so all the updates + from the 'yakkety' repository are pulled in. + + -- ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: coreutils 8.25-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 Date: Tue Jul 19 13:39:31 2016 InstallationDate: Installed on 2016-05-14 (65 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160514) ProcEnviron: - TERM=linux - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: coreutils (Ubuntu) Status: New => Incomplete ** Changed in: coreutils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1604511 Title: `tail -n N` no longer functions, prints all data in specified files instead of only the last N records Status in coreutils package in Ubuntu: Invalid Bug description: While running nginx install/upgrade tests, I was trying to get the last 10 lines of the /var/log/apt/history.log file. Naturally, I was trying to use 'tail' for this: tail -n 10 /var/log/apt/history.log Instead of only getting the last 10 lines of the file, I get the entire file spit out to me, as if I used 'cat' instead of 'tail'. This would appear to be a MAJOR problem if tail no longer functions as it should. This is on a fully-updated 16.10 server, by the way, so all the updates from the 'yakkety' repository are pulled in. -- ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: coreutils 8.25-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 Date: Tue Jul 19 13:39:31 2016 InstallationDate: Installed on 2016-05-14 (65 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Alpha amd64 (20160514) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1604511/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604509] [NEW] In the bottom edge component, using preload=true with contentUrl results in an empty page
Public bug reported:
In the bottom edge component, using preload=true with contentUrl results
in an empty page.
For example the following code 'works' with a red rectangle in the
bottom edge:
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
}
But the following code does not and results in a transparent overlay,
the contentItem appears to stay null.
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
}
Note that using contentComponent does work with preloadContent true or false.
See the linked branch for an example of this not working.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: High
Assignee: Zsombor Egri (zsombi)
Status: Confirmed
** Branch linked: lp:~ahayzen/+junk/bottom-edge-preload
--
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/1604509
Title:
In the bottom edge component, using preload=true with contentUrl
results in an empty page
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the bottom edge component, using preload=true with contentUrl
results in an empty page.
For example the following code 'works' with a red rectangle in the
bottom edge:
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
}
But the following code does not and results in a transparent overlay,
the contentItem appears to stay null.
BottomEdge {
contentUrl: Qt.resolvedUrl("RedRect.qml")
height: parent.height
preloadContent: true
}
Note that using contentComponent does work with preloadContent true or false.
See the linked branch for an example of this not working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1604509/+subscriptions
--
Mailing list: https://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 1596958] Re: package whoopsie 0.2.52.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Please, try this and share with us the. Output * sudo servicr plymouth status Le lun. 18 juil. 2016 15:46, ashokvardhankari a écrit : > Hello Alji, > > Please find the output for locate plymouth below. > > /bin/plymouth > /etc/alternatives/default.plymouth > /etc/alternatives/default.plymouth.grub > /etc/alternatives/text.plymouth > /etc/init.d/plymouth > /etc/init.d/plymouth-log > /etc/rc0.d/K01plymouth > /etc/rc2.d/S05plymouth > /etc/rc3.d/S05plymouth > /etc/rc4.d/S05plymouth > /etc/rc5.d/S05plymouth > /etc/rc6.d/K01plymouth > /etc/rcS.d/S02plymouth-log > /lib/lsb/init-functions.d/99-plymouth > /lib/systemd/system/plymouth-halt.service > /lib/systemd/system/plymouth-kexec.service > /lib/systemd/system/plymouth-log.service > /lib/systemd/system/plymouth-poweroff.service > /lib/systemd/system/plymouth-quit-wait.service > /lib/systemd/system/plymouth-quit.service > /lib/systemd/system/plymouth-read-write.service > /lib/systemd/system/plymouth-reboot.service > /lib/systemd/system/plymouth-start.service > /lib/systemd/system/plymouth-switch-root.service > /lib/systemd/system/plymouth.service > /lib/systemd/system/systemd-ask-password-plymouth.path > /lib/systemd/system/systemd-ask-password-plymouth.service > /lib/systemd/system/halt.target.wants/plymouth-halt.service > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-start.service > > /lib/systemd/system/initrd-switch-root.target.wants/plymouth-switch-root.service > /lib/systemd/system/kexec.target.wants/plymouth-kexec.service > /lib/systemd/system/multi-user.target.wants/plymouth-quit-wait.service > /lib/systemd/system/multi-user.target.wants/plymouth-quit.service > /lib/systemd/system/poweroff.target.wants/plymouth-poweroff.service > /lib/systemd/system/reboot.target.wants/plymouth-reboot.service > /lib/systemd/system/sysinit.target.wants/plymouth-read-write.service > /lib/systemd/system/sysinit.target.wants/plymouth-start.service > /sbin/plymouthd > /usr/lib/x86_64-linux-gnu/plymouth > /usr/lib/x86_64-linux-gnu/plymouth/details.so > /usr/lib/x86_64-linux-gnu/plymouth/label.so > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-generate-initrd > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-populate-initrd > /usr/lib/x86_64-linux-gnu/plymouth/plymouth-update-initrd > /usr/lib/x86_64-linux-gnu/plymouth/renderers > /usr/lib/x86_64-linux-gnu/plymouth/script.so > /usr/lib/x86_64-linux-gnu/plymouth/text.so > /usr/lib/x86_64-linux-gnu/plymouth/tribar.so > /usr/lib/x86_64-linux-gnu/plymouth/ubuntu-text.so > /usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so > /usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so > /usr/share/plymouth > /usr/share/apport/package-hooks/source_plymouth.py > /usr/share/doc/libplymouth4 > /usr/share/doc/plymouth > /usr/share/doc/plymouth-label > /usr/share/doc/plymouth-theme-ubuntu-logo > /usr/share/doc/plymouth-theme-ubuntu-text > /usr/share/doc/libplymouth4/changelog.Debian.gz > /usr/share/doc/libplymouth4/copyright > /usr/share/doc/plymouth/NEWS.Debian.gz > /usr/share/doc/plymouth/README > /usr/share/doc/plymouth/README.Debian > /usr/share/doc/plymouth/TODO > /usr/share/doc/plymouth/TODO.Debian > /usr/share/doc/plymouth/changelog.Debian.gz > /usr/share/doc/plymouth/copyright > /usr/share/doc/plymouth-label/changelog.Debian.gz > /usr/share/doc/plymouth-label/copyright > /usr/share/doc/plymouth-theme-ubuntu-logo/changelog.Debian.gz > /usr/share/doc/plymouth-theme-ubuntu-logo/copyright > /usr/share/doc/plymouth-theme-ubuntu-text/changelog.Debian.gz > /usr/share/doc/plymouth-theme-ubuntu-text/copyright > /usr/share/initramfs-tools/hooks/plymouth > /usr/share/initramfs-tools/scripts/init-bottom/plymouth > /usr/share/initramfs-tools/scripts/init-premount/plymouth > /usr/share/initramfs-tools/scripts/panic/plymouth > /usr/share/lintian/overrides/libplymouth4 > /usr/share/lintian/overrides/plymouth > /usr/share/man/man1/plymouth.1.gz > /usr/share/man/man8/plymouth.8.gz > /usr/share/man/man8/plymouthd.8.gz > /usr/share/plymouth/themes > /usr/share/plymouth/ubuntu-logo.png > /usr/share/plymouth/themes/default.grub > /usr/share/plymouth/themes/default.plymouth > /usr/share/plymouth/themes/details > /usr/share/plymouth/themes/text > /usr/share/plymouth/themes/text.plymouth > /usr/share/plymouth/themes/tribar > /usr/share/plymouth/themes/ubuntu-logo > /usr/share/plymouth/themes/ubuntu-text > /usr/share/plymouth/themes/details/details.plymouth > /usr/share/plymouth/themes/text/text.plymouth > /usr/share/plymouth/themes/tribar/tribar.plymouth > /usr/share/plymouth/themes/ubuntu-logo/password-field.png > /usr/share/plymouth/themes/ubuntu-logo/password-field16.png > /usr/share/plymouth/themes/ubuntu-logo/progress-dot-off.png > /usr/share/plymouth/themes/ubuntu-logo/progress-dot-off16.png > /usr/share/plymouth/themes/ubuntu-logo/progress-dot-on.png > /usr/share/plymouth/themes/ubuntu-logo/progress-dot-on16.png > /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo-scale-2.plymouth > /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo-sca
[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.1 --- isc-dhcp (4.3.3-5ubuntu12.1) xenial; urgency=medium * Fixed missing broadcast flag for Infiniband interfaces (LP: #1529815) - added: + d/p/dhcp-4.2.4-dhclient-options-changed.patch -- Rafael David Tinoco (Inaddy) Wed, 08 Jun 2016 10:51:06 +0200 ** Changed in: isc-dhcp (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 isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1529815 Title: InfiniBand DHCP flow with PRA and DHCP relay not working Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Wily: Fix Committed Status in isc-dhcp source package in Xenial: Fix Released Bug description: [Impact] * Infiniband users relying on DHCP can't use DHCP relay. [Test Case] * Comment #13 * Mellanox has tested themselves. * Clear way of knowing if fix worked (tcpdump). [Regression Potential] * Only related to Infiniband. * Infiniband support could stop working (unlikely, already tested). [Other Info] DHCP client is sending discover with Unicast type request for the offer, in this configuration of IB to ETH through a relay we need the type to be broadcast. The issue is that when using dhclient from the client on Ubuntu (and only on Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in unicast instead of broadcast. It seems there is no way to correct this from the client side using dhclient configuration file. this issue exist even when we use always-broadcast statement in configuration file. in other vendors we see that discover request type is broadcast. attached pcap files from working (other vendor) and not working (Ubuntu) clients. DHCP CLIENT (IPoIB) Ubuntu 14.04 kernel 3.13.0-74 Mellanox OFED 3.1-1.0.3 or inbox driver isc-dhcp-client 4.2.4-7ubuntu12.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
