Re: [Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hellow Konrad: I enable the developer mode, connect the phone to the computer and write adb shell in a terminal. It shows this: c@C:~$ adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * error: device not found c@C:~$ I don't know how to continue. Cheers, Cesar > Date: Thu, 28 Jul 2016 08:54:41 + > From: konrad.zapalow...@canonical.com > To: c...@outlook.es > Subject: [Bug 1539158] Re: Unable to pair with in-car hands-free system after > OTA-9 update > > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1539158 > > Title: > Unable to pair with in-car hands-free system after OTA-9 update > > Status in Canonical System Image: > Fix Released > Status in bluez package in Ubuntu: > Confirmed > Status in ubuntu-system-settings package in Ubuntu: > Fix Released > > Bug description: > After OTA-9 I started having trouble with my bluetooth connection to the car > hands-free system (no sound, and incoming calls no longer displayed the > number), so I have reset both the car and the phone connections (eg. forgot > the devices). > Now I can't even pair the phone with the car's system. > The car finds the phone, and then asks me to enter the code "" to pair > the device, but after a few moments, it just says the connection failed and > asks me to try again. Which fails again. > > It was working fine just before the update. > > Any logs I should post to help debug? > > PS - The car is a 2015 Honda Civic Tourer, if that matters. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452465] Re: No way to undo in TextField
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1452465 Title: No way to undo in TextField Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: While typing a text message just now and accidentally deleting almost all of it I was again painfully reminded that there's no undo in the TextField (and TextArea). The context menu needs to offer Undo. 15.04 at r204 UX Solution: Add undo and re-do to the context menu. There is a wider Text Input piece of work that is happening as part of the SDK work page 128: https://docs.google.com/document/edit?hgd=1&id=1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw#heading=h.edgqmq2oc51t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1452465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607648] [NEW] package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory
Public bug reported: tpaivaa@soittila:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 tpaivaa@soittila:~$ apt-cache policy util-linux util-linux: Installed: 2.26.2-6ubuntu3 Candidate: 2.27.1-6ubuntu3.1 Version table: 2.27.1-6ubuntu3.1 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial-updates/main amd64 Packages 2.27.1-6ubuntu3 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial/main amd64 Packages *** 2.26.2-6ubuntu3 0 100 /var/lib/dpkg/status I was running : tpaivaa@soittila:~$ sudo apt-get dist-upgrade This happened: Unpacking gcc-5-base:amd64 (5.4.0-6ubuntu1~16.04.1) over (5.2.1-22ubuntu2) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for man-db (2.7.4-1) ... Errors were encountered while processing: /var/cache/apt/archives/libmpfr4_3.1.4-1_amd64.deb Error in function: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 480, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 433, in write block = f.read(1048576) File "/usr/lib/python3.4/codecs.py", line 319, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jul 29 09:53:14 2016 DuplicateSignature: package:util-linux:2.26.2-6ubuntu3:unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory ErrorMessage: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory InstallationDate: Installed on 2015-06-04 (420 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu2 SourcePackage: util-linux Title: package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1607648 Title: package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory Status in util-linux package in Ubuntu: New Bug description: tpaivaa@soittila:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 tpaivaa@soittila:~$ apt-cache policy util-linux util-linux: Installed: 2.26.2-6ubuntu3 Candidate: 2.27.1-6ubuntu3.1 Version table: 2.27.1-6ubuntu3.1 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial-updates/main amd64 Packages 2.27.1-6ubuntu3 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial/main amd64 Packages *** 2.26.2-6ubuntu3 0 100 /var/lib/dpkg/status I was running : tpaivaa@soittila:~$ sudo apt-get dist-upgrade This happened: Unpacking gcc-5-base:amd64 (5.4.0-6ubuntu1~16.04.1) over (5.2.1-22ubuntu2) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for man-db (2.7.4-1) ... Errors were encountered while processing: /var/cache/apt/archives/libmpfr4_3.1.4-1_amd64.deb Error in function: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 480, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 433, in write block = f.read(1048576) File "/usr/lib/python3.4/codecs.py", line 319, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jul 29 09:53:14 2016 DuplicateSignature: package:util-linux:2.
[Touch-packages] [Bug 1528230] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected
Hello Andy, or anyone else affected, Accepted apparmor into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1528230 Title: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected Status in AppArmor: Fix Committed Status in QA Regression Testing: Invalid Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: Invalid Bug description: [Impact] The AppArmor regression tests are ran as part of the kernel SRU verification process. One of the tests, onexec.sh, contains a racy section that introduces intermittent failures. Such failures introduce doubt in the kernel SRU process and generate additional work to verify that the failures can be ignored. [Test Case] Since the fix is to the onexec.sh test itself, the best test case is to simply run the test. The QRT test-apparmor.py script runs this test, among many others, and should be used for verification. [Regression Potential] None. The fix is to the test and does not affect code that is user- facing. [Original Report] New ADT test failure in Vivid: running onexec ONEXEC - check current 'unconfined' != expected '/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec' Fatal Error (onexec): Unable to run test sub-executable Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1528230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588069] Re: parser doesn't catch conflicting change_profile exec modes (safe/unsafe)
** Also affects: apparmor (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1588069 Title: parser doesn't catch conflicting change_profile exec modes (safe/unsafe) Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: New Bug description: The ability to specify change_profile exec modes (safe/unsafe) is a recently merged feature. A missing piece is that the parser doesn't detect conflicting exec modes on the same exec condition. The following profile should fail to compile: /t { change_profile safe /foo -> /bar, change_profile unsafe /foo -> bar, } To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1588069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452465] Re: No way to undo in TextField
I lost already at least two messages the same way. Mostly because of the copy/paste field that appears in the text and can very easily selact all and paste something instead of our text. ** Attachment added: "screenshot20160728_233340513.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1452465/+attachment/4709258/+files/screenshot20160728_233340513.png -- 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/1452465 Title: No way to undo in TextField Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: While typing a text message just now and accidentally deleting almost all of it I was again painfully reminded that there's no undo in the TextField (and TextArea). The context menu needs to offer Undo. 15.04 at r204 UX Solution: Add undo and re-do to the context menu. There is a wider Text Input piece of work that is happening as part of the SDK work page 128: https://docs.google.com/document/edit?hgd=1&id=1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw#heading=h.edgqmq2oc51t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1452465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582374] Re: Log contains unknown mode senw
Hello Neil, or anyone else affected, Accepted apparmor into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1582374 Title: Log contains unknown mode senw Status in AppArmor: New Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: [Impact] AppArmor policy developers cannot use aa-logprof without it exiting with a traceback on certain denial messages. [Test Case] $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \ operation="file_perm" profile="foo" pid=13215 comm="apache2" \ laddr=:::192.168.1.100 lport=80 faddr=:::192.168.1.100 fport=45658 \ family="inet6" sock_type="stream" protocol=6 requested_mask="send" \ denied_mask="send"' > /tmp/log $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo $ aa-logprof -f /tmp/log -d /tmp/profiles Expected output of the last command is: Reading log entries from /tmp/log. Updating AppArmor profiles in /tmp/profiles. [Regression Potential] There is little potential for regression. This "hotfix" could result in some slight confusion because the problematic denial messages will simply be ignored but it allows aa-logprof to do its intended job without unexpectedly exiting. [Original Report] Ref #1243932. Same title but appears to be different cause. Ubuntu 16.04. Error thrown on 'sudo aa-logprof' Python 3.5.1+: /usr/bin/python3 Mon May 16 20:13:30 2016 A problem occurred in a Python script. Here is the sequence of function calls leading up to the error, in the order they occurred. /usr/sbin/aa-logprof in () 42 43 if profiledir: 44 apparmor.profile_dir = apparmor.get_full_path(profiledir) 45 if not os.path.isdir(apparmor.profile_dir): 46 raise apparmor.AppArmorException("%s is not a directory."%profiledir) 47 48 apparmor.loadincludes() 49 50 apparmor.do_logprof_pass(logmark) 51 apparmor = apparmor.do_logprof_pass = logmark = '' /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], ['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]}) 2184 ##repo_cfg = read_config('repository.conf') 2185 ##if not repo_cfg['repository'].get('enabled', False) or repo_cfg['repository]['enabled'] not in ['yes', 'no']: 2186 ##UI_ask_to_enable_repo() 2187 2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, existing_profiles, profile_dir, log) 2189 log = log_reader.read_log(logmark) 2190 #read_log(logmark) 2191 2192 for root in log: 2193 handle_children('', '', root) global log = [[['path', 13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']], [['unknown_hat', 13215, '/usr/sbin/apache2', 'null-www.po4management.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], ['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']]] log_reader = log_reader.read_log = > logmark = '' /usr/lib/python3/dist-packages/apparmor/logparser.py in read_log(self=, logmark='') 402 self.add_event_to_tree(event) 403 except AppArmorException as e: 404 ex_m
[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"
Hello Me, or anyone else affected, Accepted apparmor into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1577051 Title: aa-logprof fails with unknown mode "reweive" Status in AppArmor: Confirmed Status in Linux Mint: New Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: [Impact] AppArmor policy developers cannot use aa-logprof without it exiting with a traceback on certain denial messages. [Test Case] $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \ type=1400 audit(1462045985.636:2154): apparmor="DENIED" \ operation="file_perm" profile="foo" pid=12529 comm="java" \ laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \ family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive" \ denied_mask="receive"' > /tmp/log $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo $ aa-logprof -f /tmp/log -d /tmp/profiles Expected output of the last command is: Reading log entries from /tmp/log. Updating AppArmor profiles in /tmp/profiles. [Regression Potential] There is little potential for regression. This "hotfix" could result in some slight confusion because the problematic denial messages will simply be ignored but it allows aa-logprof to do its intended job without unexpectedly exiting. [Original Report] Ubuntu 16.04. Profiling apache tomcat. 1) aa-genprof on the catalina.sh script that is used to start and stop tomcat. 2) Start and stop tomcat. 3) Scan and save the profile. 4) aa-complain on the tomcat profile 5) Start tomcat again and this time also send a http request to tomcat. 6) Run aa-logprof which fails with this message Reading log entries from /var/log/syslog. Updating AppArmor profiles in /etc/apparmor.d. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in read_log self.add_event_to_tree(event) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in add_event_to_tree e = self.parse_event_for_tree(e) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in parse_event_for_tree raise AppArmorException(_('Log contains unknown mode %s') % rmask) apparmor.common.AppArmorException: 'Log contains unknown mode reweive' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/aa-logprof", line 50, in apparmor.do_logprof_pass(logmark) File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in do_logprof_pass log = log_reader.read_log(logmark) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in read_log raise AppArmorBug(ex_msg) # py3-only: from None apparmor.common.AppArmorBug: Log contains unknown mode reweive This error was caused by the log line: Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java" pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 family="inet6" sock_type="stream" protocol=6 requested_mask="receive" denied_mask="receive" An unexpected error occoured! For details, see /tmp/apparmor-bugreport-wj6gamog.txt Please consider reporting a bug at https://bugs.launchpad.net/apparmor/ and attach this file. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1577051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : http
[Touch-packages] [Bug 1607648] Re: package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1607648 Title: package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory Status in util-linux package in Ubuntu: New Bug description: tpaivaa@soittila:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 tpaivaa@soittila:~$ apt-cache policy util-linux util-linux: Installed: 2.26.2-6ubuntu3 Candidate: 2.27.1-6ubuntu3.1 Version table: 2.27.1-6ubuntu3.1 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial-updates/main amd64 Packages 2.27.1-6ubuntu3 0 500 http://fi.archive.ubuntu.com/ubuntu/ xenial/main amd64 Packages *** 2.26.2-6ubuntu3 0 100 /var/lib/dpkg/status I was running : tpaivaa@soittila:~$ sudo apt-get dist-upgrade This happened: Unpacking gcc-5-base:amd64 (5.4.0-6ubuntu1~16.04.1) over (5.2.1-22ubuntu2) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for man-db (2.7.4-1) ... Errors were encountered while processing: /var/cache/apt/archives/libmpfr4_3.1.4-1_amd64.deb Error in function: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/problem_report.py", line 480, in add_to_existing self.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 433, in write block = f.read(1048576) File "/usr/lib/python3.4/codecs.py", line 319, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte Original exception was: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Jul 29 09:53:14 2016 DuplicateSignature: package:util-linux:2.26.2-6ubuntu3:unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory ErrorMessage: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory InstallationDate: Installed on 2015-06-04 (420 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu2 SourcePackage: util-linux Title: package util-linux 2.26.2-6ubuntu3 failed to install/upgrade: unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/postrm': Is a directory UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1607648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588069] Re: parser doesn't catch conflicting change_profile exec modes (safe/unsafe)
** Changed in: apparmor (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1588069 Title: parser doesn't catch conflicting change_profile exec modes (safe/unsafe) Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: The ability to specify change_profile exec modes (safe/unsafe) is a recently merged feature. A missing piece is that the parser doesn't detect conflicting exec modes on the same exec condition. The following profile should fail to compile: /t { change_profile safe /foo -> /bar, change_profile unsafe /foo -> bar, } To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1588069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584069] Re: change_profile rules need a modifier to allow non-secureexec transitions
Hello Tyler, or anyone else affected, Accepted apparmor into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1584069 Title: change_profile rules need a modifier to allow non-secureexec transitions Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: [Impact] Applications which use libapparmor's aa_change_onexec() to set up an AppArmor profile transition across an upcoming exec() cannot pre- initialize the environment. This is caused by AppArmor unconditionally setting the AT_SECURE flag on the process, causing libc to scrub the environment upon exec(). Upstream AppArmor and Yakkety now support policy language that allows the policy author to specify that the environment should not be scrubbed but the changes need to be SRU'ed to Ubuntu 16.04. [Test Case] The upstream changes include exhaustive tests for the new policy language keywords. Some of them are run at build time (the apparmor_parser tests) and all of them are run by QRT's test- apparmor.py (the apparmor_parser tests, the Python utility tests, and the kernel regression tests). If a manual test is desired, see the original report below for steps. [Regression Potential] Regression potential is considerable since the fixes add new keywords to the policy language. No kernel changes are required, which mitigates some of the risk. Additionally, as mentioned above, the upstream changes include many new tests to ensure that regressions are not introduced. [Original Report] As it stands today, all exec transitions triggered by a change_profile rule cause the AT_SECURE flag in the auxiliary vector to be set due to the kernel function apparmor_bprm_secureexec() returning 1 while setting up the execution environment. This causes libc to always scrub the environment variables during such an exec transition. There should be a way to indicate, in the policy language, that AT_SECURE should not be triggered. This would be equivalent to the file rule type having the Px permission to trigger AT_SECURE and the px permission to not trigger it. The file rule type even has an 'unsafe' modifier keyword that could be reused as the change_profile modifier keyword. Steps to show that AT_SECURE is being set: # Build a test program to dump the AT_SECURE flag $ cat < print_at_secure.c #include #include int main(void) { printf("AT_SECURE = %lu\n", getauxval(AT_SECURE)); return 0; } EOF $ gcc -o print_at_secure print_at_secure.c # Load the test profile that allows all file accesses and any change_profile operations $ echo "profile test { file, change_profile, }" | sudo apparmor_parser -qr # Run bash under the test profile $ aa-exec -p test -- bash # Show the AT_SECURE is not set on exec $ ./print_at_secure AT_SECURE = 0 # Set up an exec transition (change_profile from the test profile back to the test profile) $ echo "exec test" > /proc/self/attr/exec # See that AT_SECURE is now set on exec $ ./print_at_secure AT_SECURE = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1584069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607330] Re: Not possible to edit online accounts
Hi Dubstar, and thanks for reporting this bug. However, I need some more information to understand what exactly needs to be fixed. We don't store the Google password, so introducing a way to change it wouldn't make much sense, as it would be completely useless. Why do you need this for? If you change the password on the remote service, the next time that you use an application interacting with that service, you should be prompted to reauthenticate yourself (entering the new password), if the application cannot use the service anymore. If this is not happening, please describe the steps to reproduce this case, so we can investigate why things don't work as expected. ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1607330 Title: Not possible to edit online accounts Status in Canonical System Image: Incomplete Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: Once a user account is created its not possible to edit the credentials. For example if the user creates a google online account and later wants to change the password, its not possible without deleting the account and creating a new one. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349834] Re: [MIR] flask-script and libjsoncpp (b-d's for net-cpp)
I try to build net-cpp in xenial and have the following problem. libjsoncpp-dev: Installed: 1.7.2-1 Candidate: 1.7.2-1 Version table: *** 1.7.2-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status . [ 63%] Built target gmock Scanning dependencies of target http_client_load_test [ 66%] Building CXX object tests/CMakeFiles/http_client_load_test.dir/http_client_load_test.cpp.o [ 69%] Linking CXX executable http_client_load_test CMakeFiles/http_client_load_test.dir/http_client_load_test.cpp.o: In function `HttpClientLoadTest_async_get_request_for_existing_resource_succeeds_Test::TestBody()::{lambda(core::net::http::Response const&)#2}::operator()(core::net::http::Response const&) const': http_client_load_test.cpp:(.text+0x1966): undefined reference to `Json::Reader::parse(std::string const&, Json::Value&, bool)' http_client_load_test.cpp:(.text+0x1a77): undefined reference to `Json::Value::asString() const' CMakeFiles/http_client_load_test.dir/http_client_load_test.cpp.o: In function `HttpClientLoadTest_async_post_request_for_existing_resource_succeeds_Test::TestBody()::{lambda(core::net::http::Response const&)#2}::operator()(core::net::http::Response const&) const': http_client_load_test.cpp:(.text+0x22ea): undefined reference to `Json::Reader::parse(std::string const&, Json::Value&, bool)' http_client_load_test.cpp:(.text+0x23fb): undefined reference to `Json::Value::asString() const' collect2: error: ld returned 1 exit status tests/CMakeFiles/http_client_load_test.dir/build.make:100: recipe for target 'tests/http_client_load_test' failed However rebuilding libjsoncpp from source solves this problem. Please have a check. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjsoncpp in Ubuntu. https://bugs.launchpad.net/bugs/1349834 Title: [MIR] flask-script and libjsoncpp (b-d's for net-cpp) Status in flask-script package in Ubuntu: Incomplete Status in libjsoncpp package in Ubuntu: Incomplete Bug description: [MIR] flask-script and libjsoncpp (b-d's for net-cpp) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flask-script/+bug/1349834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607666] [NEW] sudo fails with host netgroup returned from freeipa
Public bug reported: Sudo currently fails to validate netgroups against host netgroups returned from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the glory details. This was fixed in sudo 1.8.17 (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which I'd very much like to see backported to Ubuntu 16.04. If possible, updating sudo completely to 1.8.17 would be nice, since there have been quite a few improvements with regards to sss and freeipa and it would be a shame if we could not benefit from them given that 16.04 is LTS. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1607666 Title: sudo fails with host netgroup returned from freeipa Status in sudo package in Ubuntu: New Bug description: Sudo currently fails to validate netgroups against host netgroups returned from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the glory details. This was fixed in sudo 1.8.17 (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which I'd very much like to see backported to Ubuntu 16.04. If possible, updating sudo completely to 1.8.17 would be nice, since there have been quite a few improvements with regards to sss and freeipa and it would be a shame if we could not benefit from them given that 16.04 is LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
I also confirm that #5 fixes audio output (was able to connect before but no audio output) with Sony MDRXB950BT on Kubuntu 16.04. -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596713] Re: apport-cli crashes if a hook provides a python list which is a directory w/o files
This bug was fixed in the package apport - 2.20.3-0ubuntu1 --- apport (2.20.3-0ubuntu1) yakkety; urgency=medium [ Hans Joachim Desserud ] * Fix typo (cehcking -> checking) (LP: #1603463). [ Martin Pitt ] * New upstream release: - problem_report.py: Fail with proper exception when trying to assign a list to a report key, or when trying to assing a tuple with more than 4 entries. (LP: #1596713) - test_backend_apt_dpkg.py: Install GPG key for ddebs.ubuntu.com to avoid apt authentication errors. * Bump Standards-Version to 3.9.8 (no changes necessary). -- Martin Pitt Thu, 28 Jul 2016 14:10:46 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- 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/1596713 Title: apport-cli crashes if a hook provides a python list which is a directory w/o files Status in apport package in Ubuntu: Fix Released Bug description: I was reviewing an apport hook for somebody and noticed that apport- cli would crash when you try to save a report (option K) if the apport hook does something odd. As an example: 1) mkdir -p /tmp/directory1/directory2 2) modify an apport package hook to contain the following: contents = os.listdir('/tmp/directory1') report['DirContents'] = contents 3) run apport-cli ubuntu-release-upgrader (package hook I modified) 4) observe the following crash Traceback (most recent call last): File "/usr/bin/apport-cli", line 370, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 645, in run_argv self.run_symptom() File "/usr/lib/python3/dist-packages/apport/ui.py", line 636, in run_symptom self.run_report_bug(script) File "/usr/lib/python3/dist-packages/apport/ui.py", line 489, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 220, in ui_present_report_details self.report.write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 448, in write f = open(v[0], 'rb') # file name FileNotFoundError: [Errno 2] No such file or directory: 'directory2' If DirContents is a folder that contains at least one file we see the following error raised instead. TypeError: value for key DirContents must be a string, CompressedValue, or a file reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1596713/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package apport - 2.20.3-0ubuntu1 --- apport (2.20.3-0ubuntu1) yakkety; urgency=medium [ Hans Joachim Desserud ] * Fix typo (cehcking -> checking) (LP: #1603463). [ Martin Pitt ] * New upstream release: - problem_report.py: Fail with proper exception when trying to assign a list to a report key, or when trying to assing a tuple with more than 4 entries. (LP: #1596713) - test_backend_apt_dpkg.py: Install GPG key for ddebs.ubuntu.com to avoid apt authentication errors. * Bump Standards-Version to 3.9.8 (no changes necessary). -- Martin Pitt Thu, 28 Jul 2016 14:10:46 +0200 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1603463 Title: Spelling mistake in an error string - cehcking Status in apport package in Ubuntu: Fix Released 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 1599915] Re: initramfs-tools: merge debian v0.125
This bug was fixed in the package initramfs-tools - 0.125ubuntu1 --- initramfs-tools (0.125ubuntu1) yakkety; urgency=medium * Merge with debian 0.125 (LP: #1599915). Remaining delta: - Set takeover=1 in update-initramfs. - Drop hooks/keymap and associated code; console-setup takes care of this in Ubuntu. - Add a new 'fixrtc' script that tries to set the system clock forward based on the last mount time of the root disk; without this kludge, systems without a working RTC will end up in a perpetual reboot loop. - Set hostname at boot, for the benefit of mdadm autoassembly. - Ignore errors from iscan and iscan-data hooks. - Allow scripts and hooks to specify OPTION=VAR, and unless VAR is set to something other than "n", the script will not be included. - Restore the framebuffer hook and script, copying KMS and other framebuffer drivers into the initramfs, but make them optional; you need to set FRAMEBUFFER=y for these to be included. - Add hwaddr= alias for BOOTIF= for compatibility. - When receiving "recovery" on cmdline, start upstart with --startup- event=recovery (LP: #575469) - Make /etc/mtab a symlink to /proc/mounts on startup, since e.g. current ntfs-3g doesn't work otherwise. - Automatically blacklist vga16fb when vga= or video= specified on kernel command-line. - Add Hyper-V paravirtualised device drivers to the initramfs to allow booting of stock images in a Hyper-V guest. (LP: #917135) - Add mountroot failure support, to allow meaningful messages when no root device can be found. - Retain netboot= compatibility option. - Retain cryptopts= compatibility option. - Add vfat modules to the initramfs. - Maintain compatibility with pre- /run configurations - Increase rootdelay to 180s on powerpc/ppc64/ppc64el (LP: #1326199) - fixrtc: wait for udev to settle to expose device symlinks - fixrtc: handle hwclock -s failures safely - fixrtc: support busybox, handle last mount time on system partition, expose fs create time (LP: #1420473) - fixrtc: avoid using xargs, wait-for-root before examining - fixrtc: suppress /dev/ram as a root when using systempart (LP: #1443329) - ppc64el: enable PowerPC NX Crypto Coprocessor - resume: only resume when the partition contains a resume image - resume: announce resume via plymouth if available - Don't load keymaps unless we're loading a framebuffer; but set the keymap before giving a root shell. - Add new initramfs-tools-bin package containing a binary that uses libudev to wait for udev to create the udev device, or wait for udev to finish processing if we catch it in the act, and returns the filesystem type as already probed by udev. - Incorporate rzscontrol from compcache so that we can control current ramzswap devices. - Support loading compcache from the initramfs. - debian/control: update Vcs-* links for Ubuntu. - hook-functions: fix PowerPC NX Crypto Coprocessor support (LP: #1454687) - Drop: Maintain compatibility with pre- /run configurations (LP: #1485752) - Drop: Ignore errors from iscan and iscan-data hooks (LP: #1485562) - add squashfs to list of 'most' modules (LP: #1501834) - drop Breaks: against upstart as we use it in user sessions - support mounting of loopback devices via loop*= parameters - local_device_setup: use wait-for-root if it supports the device alias type - Fix vfat support from initramfs (LP: #1540522) - initramfs-tools-core uses initramfs-tools-bin add dependancy (LP: #1543244) - Add support for uppercase and lowercase uuids. (LP: #1548120) - uuids: busybox tr does not support symbolic ranges expand manually (LP: #1548120) - wait-for-root.c: Drop check if device is queued in udev (LP: #1539195) - uuids: only apply case mapping to RFC#4122 format uuids (LP: #1553107, #1548120) - hooks/framebuffer: Copy kernel/ubuntu/i915 backport driver too. (LP: #1500751) - hook-functions: add hyperv-keyboard for Generation 2 VMs (LP: #1567107) - init: fix redirection for /bin/hostname command - init: drop -b from hostname as it is not supported by busybox - Ensure we have a /usr/sbin directory in initramfs-tools-core initramfs-tools (0.125) unstable; urgency=medium * [74597dd] update-initramfs: Remove $USETRIGGERS variable and condition * [b19d13e] initramfs-tools: Install script to be invoked by linux-signed postinst * [79c0204] mkinitramfs: Fix wildcard for excluding dot-files (Closes: #821346) initramfs-tools (0.124) unstable; urgency=medium * [e05fc3e] hook-functions: Add detached module signatures if present (Closes: #820037) * [99dadac] hook-functions: Create ORDER files even if there are no valid scripts (Closes: #814965) * [57a9f2a] mkinitramfs: Exclude VCS directories when copying /etc/initramfs-tools/scripts * [eff1806]
[Touch-packages] [Bug 1599945] Re: busybox: merge debian 1:1.22.0-19
This bug was fixed in the package busybox - 1:1.22.0-19ubuntu1 --- busybox (1:1.22.0-19ubuntu1) yakkety; urgency=low * Merge from Debian unstable (LP: #1599945). Remaining changes: - [udeb] Enable chvt, killall, losetup, od, and stat. - test-bin.patch: Move test and friends to /bin. - static-sh-alias.patch: Add static-sh alias name for ash, and install /bin/static-sh symlink to busybox in busybox-static. - Add busybox-initramfs. - Refresh busybox-initramfs config to keep it in sync with the featureset of the other builds. (No changes upstream.) - Enable chpasswd in standard and static builds (needed by LXC). - Move zz-busybox to busybox-initramfs to ensure we get links to all the tools we need, stop shipping it anywhere else. - Prefer busybox commands over klibc commands where there is duplication. * Add Ubuntu configuration for busybox binaries. busybox (1:1.22.0-19) unstable; urgency=medium * busybox-udeb, udhcpc: Remove /udhcpc/usr/share/udhcpc/default.script, erroneously included in version 1:1.22.0-18 * Disable CONFIG_FEATURE_PREFER_APPLETS in standard build (Closes: #821307) busybox (1:1.22.0-18) unstable; urgency=medium [ Colin Watson ] * Use HTTPS for Vcs-* URLs, and link to cgit rather than gitweb. busybox (1:1.22.0-17) unstable; urgency=medium [ Ben Hutchings ] * Completely take over busybox installation from initramfs-tools: - Add conf hook defining BUSYBOXDIR - Make main hook fail if /bin/busybox does not exist busybox (1:1.22.0-16) unstable; urgency=medium * Stop reading initramfs.conf in initramfs hook; this is redundant and can result in a broken initramfs (Closes: #810153) -- Andy Whitcroft Thu, 07 Jul 2016 18:58:30 +0100 ** Changed in: busybox (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1599945 Title: busybox: merge debian 1:1.22.0-19 Status in busybox package in Ubuntu: Fix Released Bug description: Merge debian busybox 1:1.22.0-19 release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1599945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475223] Re: Crash during Clock application start on Desktop
@Marcus Please create separate bug report for that crash, and attach logs. Here you have instruction how to gather logs: http://askubuntu.com/questions/548504/ubuntu-sdk-how-can-i-see-error-logs-for-my-ubuntu-touch-app -- 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/1475223 Title: Crash during Clock application start on Desktop Status in Ubuntu Clock App: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Statistically once per 8 Clock runs, the application is crashing with following BackTrace: #0 0x754539fc in g_type_check_instance (type_instance=type_instance@entry=0xf1a0b0) at /build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136 #1 0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090 #2 0x7544a8ff in g_signal_emit (instance=, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #3 0x7fffbe19e271 in () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0 #4 0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller (closure=0x1520db0, return_value=0x0, n_param_values=, param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) at dbus-gproxy.c:1736 #8 0x7544a8ff in (instance=instance@entry=0xf0f780, signal_id=, detail=) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361 #5 0x754302d5 in g_closure_invoke (closure=0x1520db0, return_value=0x0, n_param_values=3, param_values=0x7fffd590, invocation_hint=0x7fffd530) at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768 #6 0x7544203c in signal_emit_unlocked_R (node=node@entry=0x151e740, detail=detail@entry=1533, instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd590) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549 #7 0x7544a698 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffd740) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305 #9 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789 #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356 #11 0x7fffec3e21d1 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7fffdfb095d5 in message_queue_dispatch (source=, callback=, user_data=) at dbus-gmain.c:90 #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122 #14 0x7515ac3d in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #15 0x7515af20 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808 ---Type to continue, or q to quit--- #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #17 0x767bcc57 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x767613e2 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7676902c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00404098 in () #21 0x75ac1a40 in __libc_start_main (main= 0x4037d0, argc=4, argv=0x7fffdf38, init=, fini=, rtld_fini=, stack_end=0x7fffdf28) at libc-start.c:289 #22 0x004058b9 in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions -- Mailing list: https://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 1589401] Re: cannot view wifi networks after re-enabling wifi
I found out, that the bug appears even if I disable wifi with the hardware key. After re enabling wifi I got the two arrows. No network to select. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589817] Re: Quotation marks in Polish keyboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1589817 Title: Quotation marks in Polish keyboard Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The quotation marks " "in a Polish keyboard are available on a page 2/2 of the digit/special sign mode in an on screen keyboard. In the mode 1/1 we have a sign ' that nobody needs while writing in Polish language. In Polish there are no words as can't or won't. There are absolutely no cases where the sign ' should be used. What we need is a " sign that is available after two clicks which drives users up the wall while quoting anything: First you have to click ?123 button then 1/2button and then the needed " is available. According to Polish language rules when quoting something only "" and »« sings are right which takes place while quoting a quote. Example: »Mark said:"give her the water"«. There is no case in Polish where we need a ' and the " is like one of the fingers of your right hand so the ' and " should be replaced. While filling a bug report when i have to quote something my patience to the OSK is over after first " quotation mark that we have to use twice which is not the case in case of ' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1589817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607681] [NEW] Mouse cursor goes missing in Aisleriot (native GTK on Mir)
Public bug reported: Mouse cursor goes missing in Aisleriot (native GTK on Mir) Just run '/usr/games/sol' under Mir. ** Affects: gtk+3.0 (Ubuntu) Importance: High Assignee: Andreas Pokorny (andreas-pokorny) Status: New ** Tags: cursor gtk-mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1607681 Title: Mouse cursor goes missing in Aisleriot (native GTK on Mir) Status in gtk+3.0 package in Ubuntu: New Bug description: Mouse cursor goes missing in Aisleriot (native GTK on Mir) Just run '/usr/games/sol' under Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380480] Re: network disabled after suspend - resume
Same problem on my XPS 13 9343. Have to restart through command line. I like the solution to add a script in the meantime in /etc/pm/sleep.d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1380480 Title: network disabled after suspend - resume Status in linux-lts-xenial package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Background: this started to happen after the upgrade to Utopic Beta 1 3) When I close the laptop's lid and open, the wifi should reconnect 4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I left-click on NM icon in notif area. However the context menu (right-click) has items "Enable networking" and "Enable Wi-Fi" both with checkmarks. Workarounds: switch off - on the physical switch on laptop OR two times go and select "Enable networking" in the NM context menu (after first time it removes checkmark and the "Enable Wi-Fi" item - visual feedback of being disabled). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 11 22:33:06 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-21 (447 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 10.9.9.0/24 dev vboxnet0 proto kernel scope link src 10.9.9.1 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.239 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-07-19T15:03:44.847279 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1380480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607680] [NEW] Smooth touchpad scrolling doesn't work in GTK-on-Mir
Public bug reported: Smooth touchpad scrolling doesn't work in GTK-on-Mir Touchpad scrolling is instead jumpy and unresponsive. ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Assignee: Andreas Pokorny (andreas-pokorny) Status: New ** Tags: gtk-mir input -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1607680 Title: Smooth touchpad scrolling doesn't work in GTK-on-Mir Status in gtk+3.0 package in Ubuntu: New Bug description: Smooth touchpad scrolling doesn't work in GTK-on-Mir Touchpad scrolling is instead jumpy and unresponsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607680] Re: Smooth touchpad scrolling doesn't work in GTK-on-Mir
It does work in GTK-on-X11-on-Xmir, but not in GTK-on-Mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1607680 Title: Smooth touchpad scrolling doesn't work in GTK-on-Mir Status in gtk+3.0 package in Ubuntu: New Bug description: Smooth touchpad scrolling doesn't work in GTK-on-Mir Touchpad scrolling is instead jumpy and unresponsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605117] Re: Unity greeter indicators don't show on second launch
Updating from xenial-proposed fixes the problem: ~# apt-cache policy lightdm lightdm: Installed: 1.18.2-0ubuntu2 Candidate: 1.18.2-0ubuntu2 Version table: *** 1.18.2-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main i386 Packages 100 /var/lib/dpkg/status 1.18.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1605117 Title: Unity greeter indicators don't show on second launch Status in Light Display Manager: Fix Committed Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Xenial: Fix Committed Bug description: [Impact] Unity Greeter indicators don't show second time greeter started. [Test Case] 1. Log in with greeter 2. Log out Expected result: Unity greeter is shown with all UI elements as in step 1. Observed result: Unity greeter is shown but only one indicator shows (accessibility) [Regression potential] Low. The fix was already present in the Bzr branch (removed some unneeded code that would accidentally close stdin). The fix was not released since it hadn't been shown to be a problem before this report. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1605117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked
It seems also just switching displays makes the kernel upset, please see attached dmesg output. Also, please consider making https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 a duplicate, as it seems to involve the same cases and error messages. ** Attachment added: "dmesg-switch-displays" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+attachment/4709293/+files/dmesg-switch-displays -- 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/1578011 Title: Laptop sometimes doesn't detect external monitor when docked Status in xorg package in Ubuntu: Confirmed Bug description: Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when docked with a Onelink Pro dock. Problem has also occurred on a non-Pro OneLink dock. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 4 11:47:20 2016 DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217] InstallationDate: Installed on 2015-12-02 (153 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20C0S1CWAU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago) dmi.bios.date: 01/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GQET48WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S1CWAU dmi.board.vendor: LENOVO dmi.board.version: 0B98417 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S1CWAU dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 08:27:55 2016 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1079 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607686] [NEW] testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 and new UITK
Public bug reported: In yakkety-proposed plus new UITK (in silo https://requests.ci- train.ubuntu.com/#/ticket/1604) two tests are crashing reliably: testWizard testShellWithPin The trace for both is quite similar: [testWizard] #0 0x73b159b4 in QQuickItem::window (this=0x56249c40) at items/qquickitem.cpp:2837 No locals. #1 0x7fffddeb58db in TouchEventSequenceWrapper::commit (this=0x557623d0, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30 No locals. #2 0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x557623d0 #3 0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall (this=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834 [testShellWithPin] #0 QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at items/qquickwindow.cpp:1964 No locals. #1 0x7fffdd15790d in TouchEventSequenceWrapper::commit (this=0x570f9310, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:32 wp = 0x385586ff #2 0x7fffdd15be8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x570f9310 #3 0x7fffdd15c046 in TouchEventSequenceWrapper::qt_metacall (this=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickwindow.cpp?h=5.6.1#n1962 Looks to me like Qt-internal issue potentially. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 (not installed) ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.3-0ubuntu1 Architecture: amd64 Date: Fri Jul 29 08:21:31 2016 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images yakkety ** Also affects: qtdeclarative-opensource-src (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/1607686 Title: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 and new UITK Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: In yakkety-proposed plus new UITK (in silo https://requests.ci- train.ubuntu.com/#/ticket/1604) two tests are crashing reliably: testWizard testShellWithPin The trace for both is quite similar: [testWizard] #0 0x73b159b4 in QQuickItem::window (this=0x56249c40) at items/qquickitem.cpp:2837 No locals. #1 0x7fffddeb58db in TouchEventSequenceWrapper::commit (this=0x557623d0, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30 No locals. #2 0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x557623d0 #3 0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall (this=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834 [testShellWithPin] #0 QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at items/qquickwindow.cpp:1964 No locals. #1 0x7
Re: [Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards
Hi, In Spanish is the same bug. In general, this occurs in all not English languages that need dead keys ALT + other key combination. I have BQ M10 ubuntu tablet + AQUARIS E4.5 UBUNTU EDITION both with OTA-12. I'm disappointed with this bug. I expected that after OTA11 it was fixed. I agree with Jyoti, this bug do unusable the phone or the tablet in ours languages. We can not write e-mails because we can not write the @ character because in our languages this character need a ALTGR + 2 combination!!! It's disappointing. And I think that this bug is already reported before. I apologize for my English. Jordi Bardají 2016-07-29 3:57 GMT+02:00 Daniel van Vugt : > I see no evidence or history of work on this topic in the Mir code. > Please clarify if there were any code changes for it in Mir 0.24.0 > > ** Changed in: mir >Status: Fix Committed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1565236 > > Title: > AltGr not working on external keyboards > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions > -- Jordi http://www.elmarathon.com -- 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/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Released Status in Mir: Incomplete Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607696] [NEW] Version string missing in libjpeg.pc
Public bug reported: Proper pkg-config files are installed if I build libjpeg-turbo myself. The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu (/Debian?) patching in a custom pkg-config file before they were included upstream in https://github.com/libjpeg-turbo/libjpeg- turbo/pull/53 . ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Description changed: - If I build libjpeg-turbo myself proper pkg-config files are installed. + Proper pkg-config files are installed if I build libjpeg-turbo myself. + The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu - (/Debian?) patching in a custom pkg-config file before there was one - upstream. + (/Debian?) patching in a custom pkg-config file before they were + included upstream in https://github.com/libjpeg-turbo/libjpeg- + turbo/pull/53 . -- 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/1607696 Title: Version string missing in libjpeg.pc Status in libjpeg-turbo package in Ubuntu: New Bug description: Proper pkg-config files are installed if I build libjpeg-turbo myself. The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu (/Debian?) patching in a custom pkg-config file before they were included upstream in https://github.com/libjpeg-turbo/libjpeg- turbo/pull/53 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607697] [NEW] GTK window titles are wrong under native Mir
Public bug reported: GTK window titles are wrong under native Mir Try running gnome-calculator under mir_proving_server and Alt+drag the window. Expected: Titlebar shows 'Calculator' Observed: Titlebar shows 'gnome-calculator' ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Assignee: Andreas Pokorny (andreas-pokorny) Status: New ** Tags: gtk-mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1607697 Title: GTK window titles are wrong under native Mir Status in gtk+3.0 package in Ubuntu: New Bug description: GTK window titles are wrong under native Mir Try running gnome-calculator under mir_proving_server and Alt+drag the window. Expected: Titlebar shows 'Calculator' Observed: Titlebar shows 'gnome-calculator' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607681] Re: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator
** Summary changed: - Mouse cursor goes missing in Aisleriot (native GTK on Mir) + Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator ** Description changed: - Mouse cursor goes missing in Aisleriot (native GTK on Mir) + Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and + Calculator Just run '/usr/games/sol' under Mir. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1607681 Title: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator Status in gtk+3.0 package in Ubuntu: New Bug description: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator Just run '/usr/games/sol' under Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582992] Re: broken apport hook: TypeError: Can't convert 'bytes' object to str implicitly
** Changed in: libvirt (Ubuntu) Assignee: Chris J Arges (arges) => (unassigned) -- 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/1582992 Title: broken apport hook: TypeError: Can't convert 'bytes' object to str implicitly Status in apport package in Ubuntu: New Status in libvirt package in Ubuntu: In Progress Bug description: The apport hooks appear broken: # ubuntu-bug libvirt-bin /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ERROR: hook /usr/share/apport/package-hooks/source_libvirt.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 202, in _run_hook symb['add_info'](report) File "/usr/share/apport/package-hooks/source_libvirt.py", line 21, in add_info 'libvirt-.*']) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 716, in attach_mac_events for match in re.findall(aa_re, report.get('KernLog', '') + report.get('AuditLog', '')): TypeError: Can't convert 'bytes' object to str implicitly Don't worry about the Wnck thing, that's bug 1580412. Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libvirt-bin 1.3.1-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue May 17 22:02:30 2016 InstallationDate: Installed on 2012-10-18 (1307 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: LANGUAGE=en_US TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libvirt UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago) modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified] mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-04-30T00:20:19.958268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1582992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540108] Re: Blue dots for text marking/placing a cursor are too small
Seems like the bug was reported in the wrong place so I didn't see it in my regular rounds of bug triaging, which is why it was stuck for so long. Sorry about that. The usability of the size of the text handlers is an issue that has come up several times. We've changed the handlers repeatedly over time, as you may have seen, larger and smaller, in response to user feedback. Evidently we haven't found a solution that works for everyone. I'll poke the designers again. But don't expect an "obvious" fix, it's really very subjective in this context. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => Medium -- 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/1540108 Title: Blue dots for text marking/placing a cursor are too small Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I mean the blue dots that are visible in the photo. Ok my hands are not the smallest but I saw already bigger ones. I can not place the cursor in the text where I want to as well as mark/highlight the text to cut or copy. On Android these dots are big raindrops. I have no problem. In Ubuntu it simply doesn't work at all without a touchpen. These dots are too tiny. -- I'm updating the bug with an additional information which is actually another problem which You can see in the photo in a comment #3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1540108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu 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/1607240 Title: Unity8 default mouse wheel speed is 7.0 (it should be 1.0) Status in Canonical System Image: New Status in QtMir: In Progress Status in qtubuntu: In Progress Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed Xmir 2:1.18.4-1ubuntu4 wheel mouse scrolling is too fast, tried with firefox and geany. run firefox on mir scroll up/down some random long page using the mouse wheel TEST CASE: 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- --desktop_file_hint=unity8 2. Roll your mouse wheel over it and watch the log Expected: vscroll values of +1/-1 Observed: vscroll values of +7/-7 WORKAROUND: System Settings > Mouse & Touchpad > Slide the second (unlabelled) slider all the way left, and then one notch right. Turns out that unlabelled slider is the wheel scroll speed. Setting it one notch from the left correctly reduces the wheel speed from 7.0 to 1.0 as Mir clients expect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607401] Re: Ctrl+Alt+Delete results in immediate reboot on devices with external keyboard
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/1607401 Title: Ctrl+Alt+Delete results in immediate reboot on devices with external keyboard Status in unity8 package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: With a bluetooth keyboard attached, pressing Ctrl+Alt+Delte combo on ubuntu touch results in a reboot sequence being initiated immediately and unconditionally. This is in contrast with running unity 8 on a laptop. The culprit seems to be coming from upstart, with this file: /etc/init /control-alt-delete.conf This shouldn't be imo enabled on the phone at all, we do handle these shortcuts on our own, with the help of logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana) -- 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/1514860 Title: OptionSelector does not work with keyboard Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu RTM: Triaged Bug description: OptionSelector does not fully work with only keyboard. There is no way to select a option on OptionSelector using only the keyboard. Pressing the arrows does not navigate on the options. And it does not have any visual feedback that it contains focus. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607401] Re: Ctrl+Alt+Delete results in immediate reboot on devices with external keyboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (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/1607401 Title: Ctrl+Alt+Delete results in immediate reboot on devices with external keyboard Status in unity8 package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: With a bluetooth keyboard attached, pressing Ctrl+Alt+Delte combo on ubuntu touch results in a reboot sequence being initiated immediately and unconditionally. This is in contrast with running unity 8 on a laptop. The culprit seems to be coming from upstart, with this file: /etc/init /control-alt-delete.conf This shouldn't be imo enabled on the phone at all, we do handle these shortcuts on our own, with the help of logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
** Changed in: qtubuntu Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: qtubuntu Importance: Undecided => High ** Changed in: qtubuntu (Ubuntu) Importance: Undecided => High ** Changed in: qtubuntu Status: New => In Progress ** Changed in: qtubuntu (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/1607240 Title: Unity8 default mouse wheel speed is 7.0 (it should be 1.0) Status in Canonical System Image: New Status in QtMir: In Progress Status in qtubuntu: In Progress Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed Xmir 2:1.18.4-1ubuntu4 wheel mouse scrolling is too fast, tried with firefox and geany. run firefox on mir scroll up/down some random long page using the mouse wheel TEST CASE: 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- --desktop_file_hint=unity8 2. Roll your mouse wheel over it and watch the log Expected: vscroll values of +1/-1 Observed: vscroll values of +7/-7 WORKAROUND: System Settings > Mouse & Touchpad > Slide the second (unlabelled) slider all the way left, and then one notch right. Turns out that unlabelled slider is the wheel scroll speed. Setting it one notch from the left correctly reduces the wheel speed from 7.0 to 1.0 as Mir clients expect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582267] Re: please merge busybox from debian
** Changed in: busybox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1582267 Title: please merge busybox from debian Status in busybox package in Ubuntu: Invalid Bug description: debdiff here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1582267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607713] [NEW] 'The website says "%2"' sentence's missing from translations
Public bug reported: Website authentication's second sentence is missing from translations: In the code: text: request ? i18n.tr('The website at %1 requires authentication. The website says "%2"').arg(request.host).arg(request.realm) : "" On Launchpad: The website %1 requires authentication. So the 'The website says "%2"' part is missing. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20160729_113517856.png" https://bugs.launchpad.net/bugs/1607713/+attachment/4709345/+files/screenshot20160729_113517856.png ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1607713 Title: 'The website says "%2"' sentence's missing from translations Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: New Bug description: Website authentication's second sentence is missing from translations: In the code: text: request ? i18n.tr('The website at %1 requires authentication. The website says "%2"').arg(request.host).arg(request.realm) : "" On Launchpad: The website %1 requires authentication. So the 'The website says "%2"' part is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"
** Attachment added: "apparmor-bugreport-dxclyajj.txt" https://bugs.launchpad.net/apparmor/+bug/1577051/+attachment/4709351/+files/apparmor-bugreport-dxclyajj.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1577051 Title: aa-logprof fails with unknown mode "reweive" Status in AppArmor: Confirmed Status in Linux Mint: New Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: [Impact] AppArmor policy developers cannot use aa-logprof without it exiting with a traceback on certain denial messages. [Test Case] $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \ type=1400 audit(1462045985.636:2154): apparmor="DENIED" \ operation="file_perm" profile="foo" pid=12529 comm="java" \ laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \ family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive" \ denied_mask="receive"' > /tmp/log $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo $ aa-logprof -f /tmp/log -d /tmp/profiles Expected output of the last command is: Reading log entries from /tmp/log. Updating AppArmor profiles in /tmp/profiles. [Regression Potential] There is little potential for regression. This "hotfix" could result in some slight confusion because the problematic denial messages will simply be ignored but it allows aa-logprof to do its intended job without unexpectedly exiting. [Original Report] Ubuntu 16.04. Profiling apache tomcat. 1) aa-genprof on the catalina.sh script that is used to start and stop tomcat. 2) Start and stop tomcat. 3) Scan and save the profile. 4) aa-complain on the tomcat profile 5) Start tomcat again and this time also send a http request to tomcat. 6) Run aa-logprof which fails with this message Reading log entries from /var/log/syslog. Updating AppArmor profiles in /etc/apparmor.d. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in read_log self.add_event_to_tree(event) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in add_event_to_tree e = self.parse_event_for_tree(e) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in parse_event_for_tree raise AppArmorException(_('Log contains unknown mode %s') % rmask) apparmor.common.AppArmorException: 'Log contains unknown mode reweive' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/aa-logprof", line 50, in apparmor.do_logprof_pass(logmark) File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in do_logprof_pass log = log_reader.read_log(logmark) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in read_log raise AppArmorBug(ex_msg) # py3-only: from None apparmor.common.AppArmorBug: Log contains unknown mode reweive This error was caused by the log line: Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java" pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 family="inet6" sock_type="stream" protocol=6 requested_mask="receive" denied_mask="receive" An unexpected error occoured! For details, see /tmp/apparmor-bugreport-wj6gamog.txt Please consider reporting a bug at https://bugs.launchpad.net/apparmor/ and attach this file. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1577051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"
Hello Martin. Although I'm not getting exact "reweive"-crashes with aa-logprof anymore it still crashed on other similar events: ~# aa-logprof Reading log entries from /var/log/syslog. Updating AppArmor profiles in /etc/apparmor.d. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 409, in read_log self.add_event_to_tree(event) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in add_event_to_tree e = self.parse_event_for_tree(e) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 310, in parse_event_for_tree raise AppArmorException(_('Log contains unknown mode %s') % rmask) apparmor.common.AppArmorException: 'Log contains unknown mode senw reweive' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/aa-logprof", line 50, in apparmor.do_logprof_pass(logmark) File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in do_logprof_pass log = log_reader.read_log(logmark) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 414, in read_log raise AppArmorBug(ex_msg) # py3-only: from None apparmor.common.AppArmorBug: Log contains unknown mode senw reweive This error was caused by the log line: Jul 29 11:42:05 files kernel: [483212.877816] audit: type=1400 audit(1469785325.122:21021): apparmor="ALLOWED" operation="file_inherit" profile="/usr/bin/nginx-amplify-agent.py//null-/bin/dash" pid=18239 comm="sh" laddr=192.168.10.3 lport=50758 faddr=54.153.70.241 fport=443 family="inet" sock_type="stream" protocol=6 requested_mask="send receive" denied_mask="send receive" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1577051 Title: aa-logprof fails with unknown mode "reweive" Status in AppArmor: Confirmed Status in Linux Mint: New Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Bug description: [Impact] AppArmor policy developers cannot use aa-logprof without it exiting with a traceback on certain denial messages. [Test Case] $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \ type=1400 audit(1462045985.636:2154): apparmor="DENIED" \ operation="file_perm" profile="foo" pid=12529 comm="java" \ laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \ family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive" \ denied_mask="receive"' > /tmp/log $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo $ aa-logprof -f /tmp/log -d /tmp/profiles Expected output of the last command is: Reading log entries from /tmp/log. Updating AppArmor profiles in /tmp/profiles. [Regression Potential] There is little potential for regression. This "hotfix" could result in some slight confusion because the problematic denial messages will simply be ignored but it allows aa-logprof to do its intended job without unexpectedly exiting. [Original Report] Ubuntu 16.04. Profiling apache tomcat. 1) aa-genprof on the catalina.sh script that is used to start and stop tomcat. 2) Start and stop tomcat. 3) Scan and save the profile. 4) aa-complain on the tomcat profile 5) Start tomcat again and this time also send a http request to tomcat. 6) Run aa-logprof which fails with this message Reading log entries from /var/log/syslog. Updating AppArmor profiles in /etc/apparmor.d. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in read_log self.add_event_to_tree(event) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in add_event_to_tree e = self.parse_event_for_tree(e) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in parse_event_for_tree raise AppArmorException(_('Log contains unknown mode %s') % rmask) apparmor.common.AppArmorException: 'Log contains unknown mode reweive' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/sbin/aa-logprof", line 50, in apparmor.do_logprof_pass(logmark) File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in do_logprof_pass log = log_reader.read_log(logmark) File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in read_log raise AppArmorBug(ex_msg) # py3-only: from None apparmor.common.AppArmorBug: Log contains unknown mode reweive This error was caused by the log line: Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java" pid=12529 comm="java"
[Touch-packages] [Bug 1606950] Re: Some Emojis are not colored in OTA 12
** Description changed: Hi, after i updated today to OTA 12, not all the emojis are colored. Im on Nexus 4 with bq stable channel. r32 + UPDATE: i can report that is just on he_IL.UTF-8 and not on en_US If there is some log to attach, please tell me. ** Also affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1606950 Title: Some Emojis are not colored in OTA 12 Status in Canonical System Image: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: Hi, after i updated today to OTA 12, not all the emojis are colored. Im on Nexus 4 with bq stable channel. r32 UPDATE: i can report that is just on he_IL.UTF-8 and not on en_US If there is some log to attach, please tell me. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607672] Re: Emojis keyboard incomplete
I couldn't find the thinking face emoji (🤔 http://emojipedia.org /thinking-face/) too. ** Also affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1607672 Title: Emojis keyboard incomplete Status in Canonical System Image: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: The ubuntu touch keyboard for emojis is not really complete: there are many different forms of hearts, like a blue, green, yellow one, or double hearts etc, but there is not the classic red hearth! (this one: http://emojipedia.org/heavy-black-heart/) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607420] Re: Tab to unlock the screen faster
*** This bug is a duplicate of bug 1435923 *** https://bugs.launchpad.net/bugs/1435923 ** This bug has been marked a duplicate of bug 1435923 [greeter/desktop] the password entry is not focused by default -- 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/1607420 Title: Tab to unlock the screen faster Status in unity8 package in Ubuntu: New Bug description: Hey, after the OTA-12, if you press tab key, you cannot start writing your password (when the screen of the tablet is of). Now you have to touch it with your finger (the space where you have to write the password) to start writing the password. Before OTA-12, you just pressed tab key and you could automatically write the password. I don't know, if I made it clear, or I made a mess with explaining the problem. Thanks ps. I use M10 FHD tablet and an bluetooth keyboard Logitech k810. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607445] Re: Zoom is not correct when using HD monitor
But if I connect my PC with Ubuntu 16.04, it work nice. I will try that and I'll report it how it goes. Thanks -- 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/1607445 Title: Zoom is not correct when using HD monitor Status in mir package in Ubuntu: Invalid Bug description: Hey, I use M10 FHD tablet with OTA-12 and when I connect it to the external HD monitor, the zoom is not correct. I cannot see the any of the border (top panel, launcher,...). But this only happens with some of the monitors. One of the monitors that doesn't work correct is Samsung SyncMaster 2333HD. Maybe because it's also a tv tuner? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1607445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435923] Re: [greeter/desktop] the password entry is not focused by default
** Changed in: canonical-devices-system-image Milestone: backlog => 13 -- 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/1435923 Title: [greeter/desktop] the password entry is not focused by default Status in Canonical System Image: Fix Committed Status in unity8 package in Ubuntu: Fix Released Bug description: Using current vivid in desktop mode (desktop-next live session or installed), the greeter screen for password has an entry, but this one is not getting the keyboard focus by default, which is annoying since you can't directly type your password then To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603016] Re: OSK should be able to have app specific suggestions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1603016 Title: OSK should be able to have app specific suggestions Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: It would be nice, for instance in the Terminal app, to have the OSK autocompletion suggestions for terminal commands, rather than English words. jounih: I was thinking - would it be useful to have a library of terminal commands for autocompletion in the terminal? instead of English [10:45am] Elleo: it'd probably be good to have a way for apps in general to add their own context specific suggestions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1603016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607435] Re: Apps not filling windows on startup
** Summary changed: - opening apps in desktop mode + Apps not filling windows on startup -- 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/1607435 Title: Apps not filling windows on startup Status in unity8 package in Ubuntu: New Bug description: Hey, I use M10 FHD tablet with OTA-12 which is connected with the external HD monitor. When I open new app, the right and the bottom side of the app is not shown. So I have to maximize the app and de-maximize it, to be normal again. It happens only with the touch apps (dekko, music,...) and not with the xmir apps. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488778] Re: Using inputMethodHints: Qt.ImhFormattedNumbersOnly for keyboard doesn't present locale "."
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1488778 Title: Using inputMethodHints: Qt.ImhFormattedNumbersOnly for keyboard doesn't present locale "." Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: With OTA5, a simple program with: TextField { validator: DoubleValidator {} inputMethodHints: Qt.ImhFormattedNumbersOnly } The user won't be able to put any non integer value in the field using the keyboard in some languages. Indeed, the DoubleValidator is using the current locale to know what is the normalized "." type. In FR_fr, it's ",". So the Qt DoubleValidator will only accept [0-9,] in the field, where the keyboard only present "." which is thus rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1488778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607431] Re: Blurry icons and bad quality text on external monitor
*** This bug is a duplicate of bug 1536751 *** https://bugs.launchpad.net/bugs/1536751 This bug is refers to the AOC monitor, which shows the picture nice, just the blurryness of the icons and low quality of font rendering is present. The bug 1607445 deals with TV-tuner I have at work. Cheers -- 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/1607431 Title: Blurry icons and bad quality text on external monitor Status in unity8 package in Ubuntu: New Bug description: Hey, I use M10 FHD tablet with OTA-12 and when I connect it to the external HD monitor (23") the icons in the left panel are a bit blurry and the title of the window and the icons on the top panel are really low quality (you can even see bitmap dots). I presume that this is still a work to do and probably that is not a priority at the moment. But still. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576576] Re: Update to 3.20 needs work and coordination
I'm uploading this to proposed today, but let's keep it blocked there until more things are ready. ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576576 Title: Update to 3.20 needs work and coordination Status in Mozilla Firefox: Fix Released Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: The current upstream stable/Debian version is 3.20 but that includes quite some changes in the css handling which means we are going to need to update/fix the unity themes and make sure you main application look fine before landing. The transition needs to be prepared in a staging ppa before being considered, help is welcome since it's likely the desktop team is not going to have lot of cycles to work on that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1576576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593048] Re: ubuntu-themes should support GTK 3.20
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1593048 Title: ubuntu-themes should support GTK 3.20 Status in ubuntu-themes package in Ubuntu: Triaged Bug description: This is a tracking bug. ubuntu-themes needs to be updated to support GTK+ 3.20 before GTK+ 3.20 can land in Ubuntu. Some initial work has been done at https://code.launchpad.net/~laney/ubuntu-themes/gtk320 If you would like to help, please contact the Ubuntu Desktop Team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1593048/+subscriptions -- Mailing list: https://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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, I tried to remove the "Nissan Connect" device, but i got this error: "*Failed to remove device: org.bluez.Error.NotReady*". Here you can read what I'm doing: *user@user-laptop:~$ adb shell* * daemon not running. starting it now on port 5037 * * daemon started successfully * phablet@ubuntu-phablet:~$ $ bluetoothctl bash: $: command not found *phablet@ubuntu-phablet:~$ bluetoothctl* [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# devices* Device 90:F1:AA:7B:80:0F [Samsung] Soundbar Device 60:38:0E:59:32:39 NISSAN CONNECT *[bluetooth]# remove 60:38:0E:59:32:39** **Failed to remove device: org.bluez.Error.NotReady* What can I do? Thank you Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
gsettings-ubuntu-touch-schemas has the default values ** Also affects: gsettings-ubuntu-touch-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-ubuntu-touch- schemas in Ubuntu. https://bugs.launchpad.net/bugs/1607240 Title: Unity8 default mouse wheel speed is 7.0 (it should be 1.0) Status in Canonical System Image: New Status in QtMir: In Progress Status in qtubuntu: In Progress Status in gsettings-ubuntu-touch-schemas package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed Xmir 2:1.18.4-1ubuntu4 wheel mouse scrolling is too fast, tried with firefox and geany. run firefox on mir scroll up/down some random long page using the mouse wheel TEST CASE: 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- --desktop_file_hint=unity8 2. Roll your mouse wheel over it and watch the log Expected: vscroll values of +1/-1 Observed: vscroll values of +7/-7 WORKAROUND: System Settings > Mouse & Touchpad > Slide the second (unlabelled) slider all the way left, and then one notch right. Turns out that unlabelled slider is the wheel scroll speed. Setting it one notch from the left correctly reduces the wheel speed from 7.0 to 1.0 as Mir clients expect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
What is your phone? -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Marco, this is super strange, I will think of possible solutions however in the meantime what is the output from info 60:38:0E:59:32:39 Thanks, K On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti wrote: > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this error: "*Failed > to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39* > *Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: > > Hey, > > I'll try to help a bit here. > > First as for the unknown or unwanted entries on the paired devices lists > [and such] you can try to remove them from the bluetoothctl level. > > ) enable developers mode & connect it via usb cable > ) login with adb shell to the deivce > ) type $ bluetoothctl > ) then type: devices - to list the known devices > ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address of the > device [not it's name] > > Second we are in the of releasing the newest bluez 5.41 which is now in > silo 37. If you are familiar with installing silos on your device you > can try it out and check if it improves anything. It includes fixes for > link management and pairing therefore there is a chance [although not > certain] that there might be joy. > > If unsure please ask. > > Best, > Konrad > > > > -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607686] Re: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1
** Summary changed: - testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 and new UITK + testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 ** Description changed: - In yakkety-proposed plus new UITK (in silo https://requests.ci- - train.ubuntu.com/#/ticket/1604) two tests are crashing reliably: + In yakkety-proposed two tests are crashing reliably: testWizard testShellWithPin The trace for both is quite similar: [testWizard] #0 0x73b159b4 in QQuickItem::window (this=0x56249c40) at items/qquickitem.cpp:2837 No locals. #1 0x7fffddeb58db in TouchEventSequenceWrapper::commit (this=0x557623d0, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30 No locals. #2 0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x557623d0 #3 0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall (this=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834 [testShellWithPin] #0 QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at items/qquickwindow.cpp:1964 No locals. #1 0x7fffdd15790d in TouchEventSequenceWrapper::commit (this=0x570f9310, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:32 wp = 0x385586ff #2 0x7fffdd15be8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x570f9310 #3 0x7fffdd15c046 in TouchEventSequenceWrapper::qt_metacall (this=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickwindow.cpp?h=5.6.1#n1962 Looks to me like Qt-internal issue potentially. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 (not installed) ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.3-0ubuntu1 Architecture: amd64 Date: Fri Jul 29 08:21:31 2016 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1607686 Title: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: In yakkety-proposed two tests are crashing reliably: testWizard testShellWithPin The trace for both is quite similar: [testWizard] #0 0x73b159b4 in QQuickItem::window (this=0x56249c40) at items/qquickitem.cpp:2837 No locals. #1 0x7fffddeb58db in TouchEventSequenceWrapper::commit (this=0x557623d0, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30 No locals. #2 0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x557623d0 #3 0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall (this=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834 [testShellWithPin] #0 QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at items/qquickwindow.cpp:1964 No locals. #1 0x7fffdd15790d in TouchEve
[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/acceptTheOptionSelector -- 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/1514860 Title: OptionSelector does not work with keyboard Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu RTM: Triaged Bug description: OptionSelector does not fully work with only keyboard. There is no way to select a option on OptionSelector using only the keyboard. Pressing the arrows does not navigate on the options. And it does not have any visual feedback that it contains focus. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions -- Mailing list: https://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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Hi Konrad, the problem was that my bluetooth is turned off :D :D Now I'm able to remove the NISSAN CONNECT device [bluetooth]# remove 60:38:0E:59:32:39 [DEL] Device 60:38:0E:59:32:39 NISSAN CONNECT Device has been removed Now I will try to pair it again. Thank you, Marco Il 29/07/2016 12:43, Konrad Zapałowicz ha scritto: > Marco, > > this is super strange, I will think of possible solutions however in > the meantime what is the output from > > info 60:38:0E:59:32:39 > > Thanks, > K > > On Fri, Jul 29, 2016 at 12:40 PM, Marco Graziotti > mailto:graziottima...@gmail.com>> wrote: > > Hi Konrad, > > I tried to remove the "Nissan Connect" device, but i got this > error: "*Failed to remove device: org.bluez.Error.NotReady*". > Here you can read what I'm doing: > > *user@user-laptop:~$ adb shell* > * daemon not running. starting it now on port 5037 * > * daemon started successfully * > > phablet@ubuntu-phablet:~$ $ bluetoothctl > bash: $: command not found > > *phablet@ubuntu-phablet:~$ bluetoothctl* > [NEW] Controller 38:BC:1A:29:69:4B MX4 Ubuntu Edition [default] > [NEW] Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > [NEW] Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# devices* > Device 90:F1:AA:7B:80:0F [Samsung] Soundbar > Device 60:38:0E:59:32:39 NISSAN CONNECT > > *[bluetooth]# remove 60:38:0E:59:32:39** > **Failed to remove device: org.bluez.Error.NotReady* > > What can I do? > > Thank you > > > Il 28/07/2016 10:54, Konrad Zapałowicz ha scritto: >> Hey, >> >> I'll try to help a bit here. >> >> First as for the unknown or unwanted entries on the paired devices lists >> [and such] you can try to remove them from the bluetoothctl level. >> >> ) enable developers mode & connect it via usb cable >> ) login with adb shell to the deivce >> ) type $ bluetoothctl >> ) then type: devices - to list the known devices >> ) to remove type: remove $BDADDR - where BDADDR is a Bluetooth address >> of the device [not it's name] >> >> Second we are in the of releasing the newest bluez 5.41 which is now in >> silo 37. If you are familiar with installing silos on your device you >> can try it out and check if it improves anything. It includes fixes for >> link management and pairing therefore there is a chance [although not >> certain] that there might be joy. >> >> If unsure please ask. >> >> Best, >> Konrad >> > > -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598904] Re: X server crashes sporadically with a segfault
I've added the xenial enablement stack and will report back if the crash occurs. Here's my updated kernel and Xorg version info: ➜ ~ Xorg -version X.Org X Server 1.18.3 Release Date: 2016-04-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.13.0-91-generic x86_64 Ubuntu Current Operating System: Linux hyperion-stfs 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7 Build Date: 03 July 2016 09:17:03AM xorg-server 2:1.18.3-1ubuntu2.2~trusty1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.30.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. ➜ ~ uname -a Linux hyperion-stfs 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- 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/1598904 Title: X server crashes sporadically with a segfault Status in xorg package in Ubuntu: Incomplete Bug description: My desktop session crashes sporadically. Often this happens when I leave the computer and the screensaver starts (Euphoria GL screensaver). This bug is not reproducible on demand. Attached is my Xorg log file which seems to indicate that this problem is related to the i915 driver code. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2016-05-26 (59 days ago) InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: LENOVO 20BWS18900 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7 Tags: trusty ubuntu Uname: Linux 4.6.3-040603-generic x86_64 UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS18900 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS18900 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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: Mon Jul 25 09:49:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor
[Touch-packages] [Bug 1607223] Re: Smooth two-finger touchpad scrolling is not accurate in apps under Unity8 (but is in Mir demo servers)
** Branch linked: lp:~vanvugt/qtubuntu/correct-scroll-speed ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu Importance: Undecided Status: New ** Changed in: qtubuntu Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: qtubuntu Status: New => In Progress ** Changed in: qtubuntu (Ubuntu) Status: New => In Progress ** Changed in: qtubuntu Importance: Undecided => High ** Changed in: qtubuntu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1607223 Title: Smooth two-finger touchpad scrolling is not accurate in apps under Unity8 (but is in Mir demo servers) Status in Canonical System Image: In Progress Status in QtMir: In Progress Status in qtubuntu: In Progress Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Smooth two-finger touchpad scrolling is not accurate in apps under Unity8 (but is in Mir demo servers). The reason appears to be because QtMir drops the nice float vscroll precision that Mir gives it and converts that into an int with very limited resolution: void handleWheelEvent(ulong timestamp, QPoint angleDelta, Qt::KeyboardModifiers mods) override QPoint is a pair of integers, but touchpad v/hscroll values are floats. I have only just discovered that although my new smooth scrolling support about to land in Xmir works in Mir's demo servers, it doesn't work when I run the same binaries under Unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606501] Re: initial app surface size wrong
*** This bug is a duplicate of bug 1606835 *** https://bugs.launchpad.net/bugs/1606835 ** This bug has been marked a duplicate of bug 1606835 Wrong usage of map{To,From}Item -- 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/1606501 Title: initial app surface size wrong Status in Canonical System Image: Confirmed Status in QtMir: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 16.10 - unity8.13+16.10.20160714+fix1-0ubuntu2~1 initial app surface size wrong i don't know how to better describe this bug, PLEASE see the attached screenshot note: if you resize the windows the app recovers and scales fine however if you reopen the app you get the same bug To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607686] Re: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1
** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1607686 Title: testWizard and testShellWithPin crashes on yakkety-proposed with Qt 5.6.1 Status in qtdeclarative-opensource-src package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: In Progress Bug description: In yakkety-proposed two tests are crashing reliably: testWizard testShellWithPin The trace for both is quite similar: [testWizard] #0 0x73b159b4 in QQuickItem::window (this=0x56249c40) at items/qquickitem.cpp:2837 No locals. #1 0x7fffddeb58db in TouchEventSequenceWrapper::commit (this=0x557623d0, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:30 No locals. #2 0x7fffddeb9e8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x557623d0 #3 0x7fffddeba046 in TouchEventSequenceWrapper::qt_metacall (this=0x557623d0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff6f20) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickitem.cpp?h=5.6.1#n2834 [testShellWithPin] #0 QQuickWindowPrivate::flushDelayedTouchEvent (this=0x385586ff) at items/qquickwindow.cpp:1964 No locals. #1 0x7fffdd15790d in TouchEventSequenceWrapper::commit (this=0x570f9310, processEvents=true) at /home/ubuntu/dev/canonical/unity8/repo/tests/utils/modules/Unity/Test/TouchEventSequenceWrapper.cpp:32 wp = 0x385586ff #2 0x7fffdd15be8b in TouchEventSequenceWrapper::qt_static_metacall (_o=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:90 _t = 0x570f9310 #3 0x7fffdd15c046 in TouchEventSequenceWrapper::qt_metacall (this=0x570f9310, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff7040) at /home/ubuntu/dev/canonical/unity8/repo/builddir/tests/utils/modules/Unity/Test/moc_TouchEventSequenceWrapper.cpp:126 No locals. [...] http://code.qt.io/cgit/qt/qtdeclarative.git/tree/src/quick/items/qquickwindow.cpp?h=5.6.1#n1962 Looks to me like Qt-internal issue potentially. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 (not installed) ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.3-0ubuntu1 Architecture: amd64 Date: Fri Jul 29 08:21:31 2016 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1607686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (only Ubuntu 16.04 LTS)
** Summary changed: - bluetooth not working + serious bug on bluetooth (only Ubuntu 16.04 LTS) -- 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/1607390 Title: serious bug on bluetooth (only Ubuntu 16.04 LTS) Status in bluez package in Ubuntu: New Bug description: I've recently installed ubuntu 16.04 LTS twice -and i discovered that the problem was from the tool katoolin so i didn't install it- after i installed ubuntu the bluetooth didn't work for me. P.S:the bluetooth was working when my laptop was ubuntu 15.04 when i turn bluetooth on to connect my mouse the switch was on but it said that Bluetooth is disabled i entered the command sudo rfkill unblock bluetooth it worked but didn't connect to the mouse even after the next restart i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock bluetooth before last line and restarting) and i've tried **sudo hciconfig hci0 reset** with output > Can't init device hci0: Connection timed out (110) my lsusb; rfkill list output: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 11: hci0: Bluetooth Soft blocked: no Hard blocked: no and output of **dmesg | grep -Ei 'ath3k|blue'** [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller [ 34.157120] Bluetooth: Core ver 2.21 [ 34.157135] Bluetooth: HCI device and connection manager initialized [ 34.157138] Bluetooth: HCI socket layer initialized [ 34.157140] Bluetooth: L2CAP socket layer initialized [ 34.157145] Bluetooth: SCO socket layer initialized [ 35.604410] usbcore: registered new interface driver ath3k [ 51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller [ 53.810045] Bluetooth: hci0 command 0x0c25 tx timeout [ 55.814079] Bluetooth: hci0 command 0x0c38 tx timeout [ 57.818111] Bluetooth: hci0 command 0x0c39 tx timeout [ 59.822149] Bluetooth: hci0 command 0x0c05 tx timeout [ 66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 66.997552] Bluetooth: BNEP filters: protocol multicast [ 66.997556] Bluetooth: BNEP socket layer initialized [ 195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller [ 195.328480] Bluetooth: RFCOMM TTY layer initialized [ 195.328488] Bluetooth: RFCOMM socket layer initialized [ 195.328495] Bluetooth: RFCOMM ver 1.11 [ 199.131870] Bluetooth: hci0 command 0x1009 tx timeout [ 276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller [ 294.258992] Bluetooth: hci0 command 0x1005 tx timeout [ 296.263065] Bluetooth: hci0 command 0x0c23 tx timeout [ 298.267076] Bluetooth: hci0 command 0x0c14 tx timeout [ 306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller [ 346.417970] Bluetooth: hci0 command 0x0c56 tx timeout [ 348.421916] Bluetooth: hci0 command 0x0c45 tx timeout [ 350.425782] Bluetooth: hci0 command 0x0c58 tx timeout [ 352.429744] Bluetooth: hci0 command 0x1004 tx timeout [ 366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller [ 368.145218] Bluetooth: hci0 command 0x1001 tx timeout [ 370.149130] Bluetooth: hci0 command 0x1009 tx timeout [ 410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller [ 421.612041] Bluetooth: hci0 command 0x0c23 tx timeout [ 423.616060] Bluetooth: hci0 command 0x0c14 tx timeout [ 425.620018] Bluetooth: hci0 command 0x0c25 tx timeout [ 427.623984] Bluetooth: hci0 command 0x0c38 tx timeout [ 442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller [ 444.727752] Bluetooth: hci0 command 0x0c52 tx timeout [ 446.731800] Bluetooth: hci0 command 0x0c45 tx timeout [ 448.735743] Bluetooth: hci0 command 0x0c58 tx timeout [ 450.739762] Bluetooth: hci0 command 0x1004 tx timeout [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller [ 4011.801141] Bluetooth: hci0 command 0x2002 tx timeout [ 4013.805106] Bluetooth: hci0 command
[Touch-packages] [Bug 1607427] Re: super key not showing scopes home
@Daniel, got a revision number? ** Changed in: unity8 (Ubuntu) Status: New => Incomplete ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: mir 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/1607427 Title: super key not showing scopes home Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Hey, if I press super key, the scopes home does not appear. In OTA-11 it worked as it should, but in OTA-12 it doesn't work. I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606835] Re: Wrong usage of map{To, From}Item
** Summary changed: - qmluitests fails with Qt 5.6.1 + Wrong usage of map{To,From}Item ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: unity8 (Ubuntu) Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Milestone: None => 13 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => 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/1606835 Title: Wrong usage of map{To,From}Item Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Logs from yakkety-proposed autopkgtests failures: amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/u/unity8/20160727_034401@/log.gz i386 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/u/unity8/20160726_220251@/log.gz --- FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 0) Uncaught exception: Type error FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 1) Uncaught exception: Type error FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 2) Uncaught exception: Type error FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 3) Uncaught exception: Type error FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 4) Uncaught exception: Type error FAIL! : qmltestrunner::PhoneStage::test_selectAppFromSpread(App 5) Uncaught exception: Type error --- FAIL! : qmltestrunner::Launcher::test_quicklist_positioning(top) 'verify()' returned FALSE. () FAIL! : qmltestrunner::Launcher::test_quicklist_positioning(bottom) 'verify()' returned FALSE. () --- To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606555] Re: unity-greeter or any other greeter can not change keyboard layout
** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- 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/1606555 Title: unity-greeter or any other greeter can not change keyboard layout Status in lightdm package in Ubuntu: Confirmed Bug description: After boot, from login screen , I can not change layout from keyboard by shortcut (ctrl+shift, alt+shift, Caps lock or any other I choose in keyboard settings) When locking screen by ctrl-alt-L, when I try to press shortcut keys lock screen disappears for a second showing my desktop, and appears again. Layout not changed also. Using mouse to switch layout via icon working good. I tried to change greeter (unity-greeter, lightdm-gtk-greeter) whith no effect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 26 16:05:37 2016 InstallationDate: Installed on 2016-06-30 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1606555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606767] Re: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1606767 Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: I am trying to upgrade from 14 to 15 to 16 LTS. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 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 26 20:42:38 2016 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu7_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu7_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:systemd:229-4ubuntu7 De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu7_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2013-11-04 (995 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=01bbbe85-6a97-4afc-bc61-f394bbd7bf52 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu7 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-07-27 (0 days ago) dmi.bios.date: 05/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/14/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1606767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588459] Re: OTA-11: missing GPS swtich in battery setings, GPS seems not working
Same issue with OTA-12. Attaching logcat output. There are some interesting lines, such as: D/gps_mt3326( 3334): nmea_reader_parse: line = 1247GPS get accuracy failed, fix mode:1 D/mnl_linux(10399): mtk_gps_sys_gps_mnl_callback: MTK_GPS_MSG_FIX_READY,GET_RTC_FAIL D/gps_mt3326( 3334): mt3326_gps_start: line = 2188no EPOHAL file, the EPO.DAT is not exsited, or is the latest one With OTA-11 at least where was some space vehicles visible, now completely zero after ~24h keeping location on. ** Attachment added: "logcat" https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588459/+attachment/4709387/+files/logcat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1588459 Title: OTA-11: missing GPS swtich in battery setings, GPS seems not working Status in location-service package in Ubuntu: Confirmed Bug description: Just updated Aquaris E5 to OTA-11 (using settings app, no flashing), and noticed that slider to enable GPS device is missing. I am not sure if it was designed so, but GPS does seems like not working. Location service is enabled (at least it seems so). There are Wireless Wi-Fi and Bluetoof sliders, but no GPS one. Location service is enabled, but SensorStatus, HERE app does not seem receive GPS info. By the way, there is no such thing as "/var/log/ubuntu-location- service*" as stated in https://wiki.ubuntu.com/Process/Merges/TestPlan /location-service#Forensics Attached tar with some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
** Branch linked: lp:~vanvugt/qtubuntu/correct-scroll-speed -- 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/1607240 Title: Unity8 default mouse wheel speed is 7.0 (it should be 1.0) Status in Canonical System Image: New Status in QtMir: In Progress Status in qtubuntu: In Progress Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed Xmir 2:1.18.4-1ubuntu4 wheel mouse scrolling is too fast, tried with firefox and geany. run firefox on mir scroll up/down some random long page using the mouse wheel TEST CASE: 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- --desktop_file_hint=unity8 2. Roll your mouse wheel over it and watch the log Expected: vscroll values of +1/-1 Observed: vscroll values of +7/-7 WORKAROUND: System Settings > Mouse & Touchpad > Slide the second (unlabelled) slider all the way left, and then one notch right. Turns out that unlabelled slider is the wheel scroll speed. Setting it one notch from the left correctly reduces the wheel speed from 7.0 to 1.0 as Mir clients expect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607431] Re: Blurry icons and bad quality text on external monitor
*** This bug is a duplicate of bug 1536751 *** https://bugs.launchpad.net/bugs/1536751 Please look at the picture od the desktop. You can see the scope icons being crisp and clean and the launcher icons being blurry. ** Attachment added: "PIcture of the desktop (tablet + hd screen)" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607431/+attachment/4709403/+files/screenshot20160729_135247449.png -- 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/1607431 Title: Blurry icons and bad quality text on external monitor Status in unity8 package in Ubuntu: New Bug description: Hey, I use M10 FHD tablet with OTA-12 and when I connect it to the external HD monitor (23") the icons in the left panel are a bit blurry and the title of the window and the icons on the top panel are really low quality (you can even see bitmap dots). I presume that this is still a work to do and probably that is not a priority at the moment. But still. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-ubuntu-touch- schemas in Ubuntu. https://bugs.launchpad.net/bugs/1607240 Title: Unity8 default mouse wheel speed is 7.0 (it should be 1.0) Status in Canonical System Image: New Status in QtMir: In Progress Status in qtubuntu: In Progress Status in gsettings-ubuntu-touch-schemas package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed Xmir 2:1.18.4-1ubuntu4 wheel mouse scrolling is too fast, tried with firefox and geany. run firefox on mir scroll up/down some random long page using the mouse wheel TEST CASE: 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- --desktop_file_hint=unity8 2. Roll your mouse wheel over it and watch the log Expected: vscroll values of +1/-1 Observed: vscroll values of +7/-7 WORKAROUND: System Settings > Mouse & Touchpad > Slide the second (unlabelled) slider all the way left, and then one notch right. Turns out that unlabelled slider is the wheel scroll speed. Setting it one notch from the left correctly reduces the wheel speed from 7.0 to 1.0 as Mir clients expect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1542021] Re: Libtinyxml2.6.2v5 replaces libtinyxml2.6.2, but doesn't provide it
** Changed in: tinyxml (Ubuntu) Status: Confirmed => Triaged ** Changed in: hundredpapercuts Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml in Ubuntu. https://bugs.launchpad.net/bugs/1542021 Title: Libtinyxml2.6.2v5 replaces libtinyxml2.6.2, but doesn't provide it Status in One Hundred Papercuts: Triaged Status in tinyxml package in Ubuntu: Triaged Bug description: Some packages references libtinyxml2.6.2. libtinyxml2.6.2v5 replaces it, but doesn't provide it. So no program which depends on libtinyxml2.6.2 can be installed anymore... One example are ros packages. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1542021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522057] Re: DNS resolution stops working after some time
*** This bug is a duplicate of bug 1003842 *** https://bugs.launchpad.net/bugs/1003842 ** This bug has been marked a duplicate of bug 1003842 dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1522057 Title: DNS resolution stops working after some time Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: DNS resolution stops working after sometime (usually 10-20 minutes) in Lubuntu 15.10 The problem can be temporarily corrected after restarting network- manager using systemctl, but it starts again after 10-20 minutes. Looks like network-manager is not configuring dnsmasq properly. Output from 'nslookup google.com': ~ Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED ~ Output from 'tcpdump -i lo port 53' while running above command: ~ 20:16:59.235879 IP localhost.38045 > comp0.arhome.info.domain: 28529+ A? google.com. (28) 20:16:59.286851 IP comp0.arhome.info.domain > localhost.38045: 28529 Refused 0/0/0 (28) ~ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: LXDE Date: Wed Dec 2 20:14:32 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-25 (68 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 172.16.84.1 dev wlan0 proto static metric 600 172.16.84.0/22 dev wlan0 proto kernel scope link src 172.16.84.50 metric 600 200.1.1.2 via 172.16.84.1 dev wlan0 proto dhcp metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-11-06 (25 days ago) nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/1 nn0.arhome.info bab29dc2-8a79-4170-8253-277286712124 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- vboxnet0 ethernet unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1522057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
This breaks domain name resolution in Ubuntu 16.04, as seen in bug #1522057. ** Tags added: precise xenial ** Changed in: network-manager (Ubuntu) Importance: Medium => Critical ** Changed in: dnsmasq (Ubuntu Precise) Importance: Medium => Critical ** Changed in: dnsmasq (Ubuntu) Importance: Medium => Critical ** Changed in: network-manager (Ubuntu Precise) Importance: Medium => Critical ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid ** Changed in: network-manager (Ubuntu Precise) Status: Triaged => Invalid ** Changed in: dnsmasq (Ubuntu) Status: Confirmed => Triaged ** Changed in: dnsmasq (Ubuntu Precise) Status: Confirmed => Triaged ** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: dnsmasq (Ubuntu Precise) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
** Changed in: oxide Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: In Progress Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
** Also affects: shim (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid ** Changed in: shim (Ubuntu) Importance: Undecided => Critical ** Changed in: shim (Ubuntu) Status: New => Confirmed ** Project changed: shim => hundredpapercuts ** Changed in: hundredpapercuts Status: New => Confirmed ** No longer affects: hundredpapercuts ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => Critical ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu) ** No longer affects: xorg (Ubuntu) ** No longer affects: linux (Ubuntu) ** Changed in: shim (Ubuntu) Status: Confirmed => Triaged -- 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/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable Status in shim package in Ubuntu: Triaged Bug description: I am running Ubuntu 16.04 since at least four months, always with the nvidia proprietary drivers (installed from the repository). I used nvidia-361 for a while with no issues (and i need it for steam gaming). However, an update installed on my machine yesterday breaks the nvidia drivers. I tried purging the driver, rebooting and reinstalling and i tried a newer version for the ubuntu-drivers ppa. Nothing helps: With the nvidia driver installed, i get a low- resolution login screen, but cannot login due to missing 3d acceleration. Running on nouveau works fine. This seems very strange to since everything worked until this afternoon. Yesterday, i was happily playing games on steam, installed some updates and now, my graphics are broken. $ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 25 17:45:12 2016 DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381] InstallationDate: Installed on 2016-01-05 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed
Here's a set of logs from #381, where the bug does not reproduce. ** Attachment added: "working.tgz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+attachment/4709413/+files/working.tgz -- 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/1607466 Title: Mono BT headset has no in-call audio on recent rc-proposed Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in phone-app package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: MX4/arale ubuntu-touch/rc-proposed/meizu.en #387 Flash phone with --bootstrap, and walk through the welcome wizard. Once you have a phone to use, visit the BT settings, and pair a mono 'HSP' headset. In my case an old Jabra OTE-1. Once the device is paired, make an incoming call to the handset. Use the headset button to answer the call. The handset transitions to showing you an in-call UI, and appears to claim the audio is routed to the headset. I heard no audio. Expected: Audio was heard on the headset during the call. Note that this does not occur on rc-proposed/meizu.en #381, so it seems to be a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607770] [NEW] Xubuntu 16.04.1 + Atheros AR9285 : wifi KO (boot and reboot)
Public bug reported: Hello, With Xubuntu 14.04, network-manager and Atheros AR9285 card, the wifi connections were OK. Passing Xubuntu 16.04.1, the wifi connection is KO : At boot and reboot, research Wifi my box fails. We must stop looking for "Disconnect" and then try to connect to other network visible and new stop this research and then an retry with a new connection with the WiFi SSID of my box, this third time the connection is successful. Notes: 1) When connected to wifi, disconnecting the user in again and the wifi connection is good in this case. 2) Orders "echo" ath9k options nohwcrypt = 1 "| sudo tee -a /etc/modprobe.d/ath9k.conf" + "sudo echo ath9k" / etc / modules "+ change the wireless channel has improved the problem but have not been settled. Thanks. Informations : Asus X72J - Intel i5 460M - 4Go - Radeon 5470 Xubuntu 16.04.1 64 bits, Kernel : 4.4.0.31 Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Kernel driver in use: ath9k, linux-firmware 1.157.2 Network-manager : 1.2.0, security wifi : "Wpa et Wpa2 personnal" ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1607770 Title: Xubuntu 16.04.1 + Atheros AR9285 : wifi KO (boot and reboot) Status in network-manager package in Ubuntu: New Bug description: Hello, With Xubuntu 14.04, network-manager and Atheros AR9285 card, the wifi connections were OK. Passing Xubuntu 16.04.1, the wifi connection is KO : At boot and reboot, research Wifi my box fails. We must stop looking for "Disconnect" and then try to connect to other network visible and new stop this research and then an retry with a new connection with the WiFi SSID of my box, this third time the connection is successful. Notes: 1) When connected to wifi, disconnecting the user in again and the wifi connection is good in this case. 2) Orders "echo" ath9k options nohwcrypt = 1 "| sudo tee -a /etc/modprobe.d/ath9k.conf" + "sudo echo ath9k" / etc / modules "+ change the wireless channel has improved the problem but have not been settled. Thanks. Informations : Asus X72J - Intel i5 460M - 4Go - Radeon 5470 Xubuntu 16.04.1 64 bits, Kernel : 4.4.0.31 Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Kernel driver in use: ath9k, linux-firmware 1.157.2 Network-manager : 1.2.0, security wifi : "Wpa et Wpa2 personnal" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1607770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574897] Re: Upgrading to 16.04 disables Python3?
Can someone explain to the community why this has gone this far ? Powerline is not shipped directly with vim, but with powerline (http://packages.ubuntu.com/xenial/powerline). How come you solve a powerline problem by changing dependencies on vim package instead of fixing powerline package ? Forcing vim users to install libpython3.5 is a bit excessive, don't you think ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1574897 Title: Upgrading to 16.04 disables Python3? Status in vim package in Ubuntu: Fix Released Status in vim source package in Xenial: Fix Released Bug description: Since I ran a do-release-upgrade last week from 15.10 to 16.04, starting Vim now produces this warning I haven't seen before: ~/D/abc ❯❯❯ vim develop ✭ You need vim compiled with Python 2.6, 2.7 or 3.2 and later support for Powerline to work. Please consult the documentation for more details. Press ENTER or type command to continue Then had a look at the included features of Vim: /e/alternatives ❯❯❯ vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +tag_binary +arabic +file_in_path+mouse_sgr +tag_old_static +autocmd +find_in_path-mouse_sysmouse -tag_any_white -balloon_eval+float +mouse_urxvt -tcl -browse +folding +mouse_xterm +terminfo ++builtin_terms -footer +multi_byte +termresponse +byte_offset +fork() +multi_lang +textobjects +channel +gettext -mzscheme+timers +cindent -hangul_input+netbeans_intg +title -clientserver+iconv +packages-toolbar -clipboard +insert_expand +path_extra +user_commands +cmdline_compl +job -perl+vertsplit +cmdline_hist+jumplist+persistent_undo +virtualedit +cmdline_info+keymap +postscript +visual +comments+langmap +printer +visualextra +conceal +libcall +profile +viminfo +cryptv +linebreak -python +vreplace +cscope +lispindent -python3 +wildignore +cursorbind +listcmds+quickfix+wildmenu +cursorshape +localmap+reltime +windows +dialog_con -lua +rightleft +writebackup +diff+menu-ruby-X11 +digraphs+mksession +scrollbind -xfontset -dnd +modify_fname+signs -xim -ebcdic +mouse +smartindent -xsmp +emacs_tags -mouseshape +startuptime -xterm_clipboard +eval+mouse_dec +statusline -xterm_save +ex_extra+mouse_gpm -sun_workshop-xpm +extra_search-mouse_jsbterm +syntax system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl I see, there is -python and -python3 But all news and documentation say the Vim in Xenial 16.04 comes with Python3 enabled. I am confused? A bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1574897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576576] Re: Update to 3.20 needs work and coordination
gtk2 because the merge brings package reorganisation ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576576 Title: Update to 3.20 needs work and coordination Status in Mozilla Firefox: Fix Released Status in Ubuntu GNOME: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: The current upstream stable/Debian version is 3.20 but that includes quite some changes in the css handling which means we are going to need to update/fix the unity themes and make sure you main application look fine before landing. The transition needs to be prepared in a staging ppa before being considered, help is welcome since it's likely the desktop team is not going to have lot of cycles to work on that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1576576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607096] Re: lxc-container-default-with-mounting profile systemd permission denied
** Description changed: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems similar but not specially calling out the aa profile. Also, I cannot actually recreate this problem in Trusty. + + (UPDATE: Forgot to mention I have 2 additional conf lines as follows) + lxc.cgroup.devices.allow = b 7:* rwm + lxc.cgroup.devices.allow = c 10:237 rwm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1607096 Title: lxc-container-default-with-mounting profile systemd permission denied Status in lxc package in Ubuntu: New Bug description: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems similar but not specially calling out the aa profile. Also, I cannot actually recreate this problem in Trusty. (UPDATE: Forgot to mention I have 2 additional conf lines as follows) lxc.cgroup.devices.allow = b 7:* rwm lxc.cgroup.devices.allow = c 10:237 rwm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1607096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards
It seems to be only partially fixed also for the Norwegian keyboard layout. For the Norwegian keyboard layout everything works in the Xapps (both special glyphs like @$£[]... and accented characters like àáêëñ...). In the Ubuntu touch apps, only special glyphs work, but not accented characters. -- 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/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Released Status in Mir: Incomplete Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600637] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1600637 Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: I have not any other details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1 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.1 Architecture: amd64 Date: Sun Jul 10 21:54:14 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-07 (277 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-07-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1600637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607785] [NEW] Xapps disappear from launcher on restart
Public bug reported: Every time I use Firefox, LibreOffice writer etc, I swipe in from the left to get to the launcher, long click on their icons and select "Pin to launcher" (not necessarily correct phrase, I'm on the Norwegian translation). My icons for the Xapps stay in the launcher, but after a restart, they are all gone and only Ubuntu touch apps stay there. This is annoying, as I am frequently using the Xapps and would like to launch them from the launcher in stead of from the Xapps scope. I am using OTA 12 on Bq M10 FHD. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: launcher xapps -- 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/1607785 Title: Xapps disappear from launcher on restart Status in unity8 package in Ubuntu: New Bug description: Every time I use Firefox, LibreOffice writer etc, I swipe in from the left to get to the launcher, long click on their icons and select "Pin to launcher" (not necessarily correct phrase, I'm on the Norwegian translation). My icons for the Xapps stay in the launcher, but after a restart, they are all gone and only Ubuntu touch apps stay there. This is annoying, as I am frequently using the Xapps and would like to launch them from the launcher in stead of from the Xapps scope. I am using OTA 12 on Bq M10 FHD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599181] Re: Add a Composers category (wishlist)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mediascanner2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1599181 Title: Add a Composers category (wishlist) Status in Ubuntu Music App: Triaged Status in Ubuntu UX: New Status in mediascanner2 package in Ubuntu: Confirmed Bug description: In addition to "Artists", "Albums", "Genres" etc. please add a "Composers" category (possibly available only when some setting is toggled, to avoid cluttering up the menu for those who don't need it). Note: this is partially related to https://bugs.launchpad.net/music- app/+bug/1599179 , but is separate from it. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1599181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588459] Re: OTA-11: missing GPS swtich in battery setings, GPS seems not working
I am thinking about reflashing, but maybe it would be actually better to try to find actual issue and fix it... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1588459 Title: OTA-11: missing GPS swtich in battery setings, GPS seems not working Status in location-service package in Ubuntu: Confirmed Bug description: Just updated Aquaris E5 to OTA-11 (using settings app, no flashing), and noticed that slider to enable GPS device is missing. I am not sure if it was designed so, but GPS does seems like not working. Location service is enabled (at least it seems so). There are Wireless Wi-Fi and Bluetoof sliders, but no GPS one. Location service is enabled, but SensorStatus, HERE app does not seem receive GPS info. By the way, there is no such thing as "/var/log/ubuntu-location- service*" as stated in https://wiki.ubuntu.com/Process/Merges/TestPlan /location-service#Forensics Attached tar with some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed
I have tried to reproduce on both 387 & 389. I have been unable to, using the same equipment as last night. I did not enable logging, so it does not seem to be the presence of extra logging that stops reproduction. -- 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/1607466 Title: Mono BT headset has no in-call audio on recent rc-proposed Status in Canonical System Image: New Status in bluez package in Ubuntu: New Status in phone-app package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: MX4/arale ubuntu-touch/rc-proposed/meizu.en #387 Flash phone with --bootstrap, and walk through the welcome wizard. Once you have a phone to use, visit the BT settings, and pair a mono 'HSP' headset. In my case an old Jabra OTE-1. Once the device is paired, make an incoming call to the handset. Use the headset button to answer the call. The handset transitions to showing you an in-call UI, and appears to claim the audio is routed to the headset. I heard no audio. Expected: Audio was heard on the headset during the call. Note that this does not occur on rc-proposed/meizu.en #381, so it seems to be a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards
Guys, accented characters (with dead keys) is a different thing than AltGr. AltGr should be fixed for everyone now while the accented characters are tracked in this bug: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607237 -- 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/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Released Status in Mir: Incomplete Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576576] Re: Update to 3.20 needs work and coordination
** Branch linked: lp:~ubuntu-desktop/gtk/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576576 Title: Update to 3.20 needs work and coordination Status in Mozilla Firefox: Fix Released Status in Ubuntu GNOME: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: The current upstream stable/Debian version is 3.20 but that includes quite some changes in the css handling which means we are going to need to update/fix the unity themes and make sure you main application look fine before landing. The transition needs to be prepared in a staging ppa before being considered, help is welcome since it's likely the desktop team is not going to have lot of cycles to work on that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1576576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed
** Changed in: canonical-devices-system-image Status: New => Incomplete -- 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/1607466 Title: Mono BT headset has no in-call audio on recent rc-proposed Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: New Status in phone-app package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: MX4/arale ubuntu-touch/rc-proposed/meizu.en #387 Flash phone with --bootstrap, and walk through the welcome wizard. Once you have a phone to use, visit the BT settings, and pair a mono 'HSP' headset. In my case an old Jabra OTE-1. Once the device is paired, make an incoming call to the handset. Use the headset button to answer the call. The handset transitions to showing you an in-call UI, and appears to claim the audio is routed to the headset. I heard no audio. Expected: Audio was heard on the headset during the call. Note that this does not occur on rc-proposed/meizu.en #381, so it seems to be a recent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection
Ok, patch set 31 that now includes the Mir backend is in the silo 038 https://requests.ci-train.ubuntu.com/#/ticket/1723 The UITK branch is however outdated. As Unity 8 is already using an internal copy of this, the main benefit from the landing would come via UITK. Unity 8 would also switch to use the qtsystems version instead. If the patch set 31 is not complete enough or the UITK branch won't be ready to be tested by next Friday, this'd be OTA-14 instead of 13. -- 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/1536669 Title: "BottomEdge" component does not support automatic mouse detection Status in Canonical System Image: In Progress Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: BottomEdge component does not work property with mouse unless you set the: QuickUtils.mouseAttached = true This should be done automatically by SDK. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)
This was reported in the test lab at one point but not reproduced Adding your syslog would be helpful ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1607684 Title: wifi networks not remembered correctly (ubuntu touch, bq M10) Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: New Bug description: I have a M10, on ubuntu touch OTA-12 (and same issue previously on OTA-11). The issue is that it doesn't remember wifi networks properly. To explain: 1. turn on tablet 2. select my wifi network from the list 3. enter password and click connect 4. reboot device 5. select my wifi network from the list 6. enter password and click connect . . . 30. go to wifi settings -> previous networks 31. view long list that looks like: MyWifinetwork1 MyWifinetwork2 MyWifinetwork3 MyWifinetwork4 ... What it should do (and did some time ago), is see that MyWifinetwork was saved in previous networks and automatically connect using the saved password/settings. So, I'm wondering is this a bug, something badly configured in my wifi network (although other devices remember it fine), or something else? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions -- Mailing list: https://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 1565236] Re: AltGr not working on external keyboards
AltGr is not working nor in phone neither tablet OTA12 Do you need a video? Jordi El divendres, 29 de juliol de 2016, Michael Zanetti < michael.zane...@canonical.com> va escriure: > Guys, accented characters (with dead keys) is a different thing than > AltGr. > > AltGr should be fixed for everyone now while the accented characters are > tracked in this bug: > > https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607237 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1565236 > > Title: > AltGr not working on external keyboards > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions > -- Jordi http://www.elmarathon.com -- 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/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Released Status in Mir: Incomplete Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607799] Re: Dash freezes after U1 login
confirmed on desktop too. ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Milestone: None => 13 ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Tags added: regression-proposed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => 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/1607799 Title: Dash freezes after U1 login Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: New Bug description: Test case. - Without U1 account, go to Ubuntu Store. - Tap on an app. - Tap on the install button. - Introduce credentials. Expected result. - After credentials, the app is installed. Actual result. - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do work, though. There is no crash. current build number: 389 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603937] Re: Documentation: cannot link to Qt QML classes/components
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-landing-070 -- 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/1603937 Title: Documentation: cannot link to Qt QML classes/components Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: staging branch, revision 2033 Description Linking to Qt QML classes/methods/components when writing documentation for UITK components does not work. If you want to link to, say, the Text component while writing the documentation for a UITK component, you should be allowed to use "\l Text", and it should just work. At the moment, it doesn't, qdoc fails with "Can't link to Text". Looking at the current documentation, it seems the documentation writers mainly used 2 workarounds: 1) Do not link to Qt classes/components/properties at all. This is clearly suboptimal, but it seems 95% of the writers went this way. 2) Hardcode the absolute URL to the Qt docs. This of course means that those links will break when the webpage at that URL will change address. Example: links at https://developer.ubuntu.com/api/qml/sdk-15.04.5/UbuntuUserInterfaceToolkit.ubuntu-layouts/ are broken, because they point to https://qt-project.org/doc/qt-5.0 See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/view/2033/documentation/ubuntu-layouts.qdoc#L29 The docs.sh script specifies that the cross-referencing of docs is only done for the ONLINE documentation, although I don't see why that is the case. http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/2033/documentation/docs.sh#L39 Is there any reason? If not, we should add "indexes" to the offline documentation, so that we can start fixing the documentation files by removing hardcoded URLs and adding links to Qt docs in as many places as possible :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1603937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523817] Re: ComboButton needs keyboard support
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-landing-070 -- 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/1523817 Title: ComboButton needs keyboard support Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: In Progress Bug description: The ComboButton needs to open and close with a keyboard, via Space/Enter key, Up/Down arrows change the current choice while the dropdown is visible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp