[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)
** Also affects: fonts-android (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: fonts-android (Ubuntu) Status: In Progress = Fix Released ** Changed in: fonts-android (Ubuntu Trusty) Importance: Undecided = High ** Changed in: fonts-android (Ubuntu Trusty) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: Fix Released Status in fonts-android source package in Trusty: Triaged Status in fonts-android package in Debian: New Bug description: trusty SRU request == [Impact] When using Roboto fonts (the fonts-roboto package), printing fails with some printers. This has been fixed in later versions, so this proposed upload installs Roboto fonts from fonts-android 4.4.4r2 instead of 4.3. Unlike fonts-droid, fonts-roboto is not a seeded package, so while it's an annoying bug for those affected, this fix only affects those who explicitly install and use fonts-roboto. [Test Case] * Package: fonts-roboto 1:4.3-3ubuntu1.1 * Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. * Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. [Regression Potential] Low. [Original Description] As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
Thanks, that seems fixed in the current serie, so closing that part and accepting for precise. Since the issue has a CVE replacing the sponsors by the security-team sponsors ** Also affects: openldap (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu) Status: New = Fix Released ** Changed in: openldap (Ubuntu) Importance: Undecided = High ** Changed in: openldap (Ubuntu Precise) Status: New = Triaged ** Changed in: openldap (Ubuntu Precise) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Precise: Triaged Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] * this set of patches adds validations to avoid segfaults, so no regression is expected. [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456240] [NEW] AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456241] [NEW] AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1456241 Title: AP failure: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401084] Re: Missing rules in php5 abstraction
Here's a patch to fix this for trusty. ** Patch added: php5-Zend_semaphore-lp1401084.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1401084/+attachment/4399530/+files/php5-Zend_semaphore-lp1401084.patch ** Description changed: + [impact] + + This bug prevents the proper functioning of apache mod_php with + mod_apparmor. + + [steps to reproduce] + + 1) setuo apache and mod_php, verify php scripts are working + 2) stop apache2 + 3) install mod_apparmor + 4) restart apache2 + 5) with fix applied, apache should not generate rejections for /tmp/.ZendSem.* + for php scripts confined by mod_apparmor + + [regression potential] + + The change to the php abstraction in the patch for this bug is a + slight loosening of the apparmor policy. The risk of an introduced + regression is small. + + [original description] + I am using apache mod_apparmor with a wordpress blog. In my rules I have: #include abstractions/php5 But this did not allow all access that was needed: apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=k denied_mask=k fsuid=33 ouid=0 apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=wk denied_mask=wk fsuid=33 ouid=0 This access seems to be needed by opcache module, I found some info about it here: https://lists.ubuntu.com/archives/apparmor/2014-June/005879.html Ubuntu 14.04.1 apparmor 2.8.95~2430-0ubuntu5.1 -- 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/1401084 Title: Missing rules in php5 abstraction Status in apparmor package in Ubuntu: Fix Released Bug description: [impact] This bug prevents the proper functioning of apache mod_php with mod_apparmor. [steps to reproduce] 1) setuo apache and mod_php, verify php scripts are working 2) stop apache2 3) install mod_apparmor 4) restart apache2 5) with fix applied, apache should not generate rejections for /tmp/.ZendSem.* for php scripts confined by mod_apparmor [regression potential] The change to the php abstraction in the patch for this bug is a slight loosening of the apparmor policy. The risk of an introduced regression is small. [original description] I am using apache mod_apparmor with a wordpress blog. In my rules I have: #include abstractions/php5 But this did not allow all access that was needed: apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=k denied_mask=k fsuid=33 ouid=0 apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=wk denied_mask=wk fsuid=33 ouid=0 This access seems to be needed by opcache module, I found some info about it here: https://lists.ubuntu.com/archives/apparmor/2014-June/005879.html Ubuntu 14.04.1 apparmor 2.8.95~2430-0ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1401084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454724] Re: Mir server crashed with SIGSEGV from close_session() when a client is killed suddenly
** Branch linked: lp:~afrantzis/mir/fix-1441759-screencast -- 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/1454724 Title: Mir server crashed with SIGSEGV from close_session() when a client is killed suddenly Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed Bug description: Am able to crash mir_proving_server (0.12.1 in archive) with the following: 1. sudo mir_proving_server 2. sudo chmod 777 /tmp/mir_socket 3. export MIR_SOCKET=/tmp/mir_socket QT_QPA_PLATFORM=ubuntumirclient 4. download http://pastebin.ubuntu.com/2825/ and save as test.qml 5. qmlscene test.qml 6. resize the client window quite a bit - i.e. make it 500x400 or similar 7. Ctrl+C the client Bug: mir_proving_server crashes ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: mir-demos 0.12.1+15.04.20150324-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 13 14:44:50 2015 ExecutablePath: /usr/bin/mir_proving_server ExecutableTimestamp: 1427214539 InstallationDate: Installed on 2014-11-11 (183 days ago) InstallationMedia: Ubuntu-Desktop-Next 15.04 Vivid Vervet - Alpha amd64 (20141103) ProcCmdline: mir_proving_server ProcCwd: /home/gerry SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: mir StacktraceTop: __pthread_mutex_unlock_usercnt (decr=1, mutex=0x1) at pthread_mutex_unlock.c:314 __GI___pthread_mutex_unlock (mutex=0x1) at pthread_mutex_unlock.c:315 __gthread_mutex_unlock (__mutex=optimized out) at /usr/include/x86_64-linux-gnu/c++/4.9/bits/gthr-default.h:778 unlock (this=optimized out) at /usr/include/c++/4.9/mutex:153 unlock (this=0x7f665649a700) at /usr/include/c++/4.9/mutex:530 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1454724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433370] Re: Autopilot helpers documentation is blank
** Changed in: developer-ubuntu-com Status: Fix Committed = Fix Released -- 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/1433370 Title: Autopilot helpers documentation is blank Status in Ubuntu App Developer site: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: The ubuntu-ui-toolkit-autopilot package now generates json and html documentation as part of package creation. However, the resulting files are missing the actual API methods they intend to document. To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1433370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327257] Re: [split] Impossible to place snap decisions on greeter while screen is unlocked
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1327257 Title: [split] Impossible to place snap decisions on greeter while screen is unlocked Status in Server and client library for desktop notifications in Unity: New Status in unity8 package in Ubuntu: New Bug description: With the current greeter implementation we have a full telephony stack running as lightdm. When an incoming call arrives the telephony-service-approver daemons try to place a snap decision either on greeter and unity8. Everything works fine when the screen is locked (greeter displayed), but if the screen is unlocked, the approver gets stuck while calling notify_notification_show() until the screen is locked again. notify_notification_show() has a timeout, so it fails to display the snap decision in a minute or so (which means receiving a call and not activating the greeter so it can process the snap decision). If you run the approver manually you will get the following messages: - Failed to show snap decision: Timeout was reached Failed to get user property IncomingCallSound from AccountsService: Object path cannot be empty Failed to get active entry from Unity Greeter: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. In such case, the approver gives up on trying to show the snap decision, but in most of times, if you lock the screen to see the greeter, a snap decision is there, but the call does not exist anymore. Steps to reproduce: 1) install dialer-app-autopilot 2) reboot your device (to get ofono-phonesim running) 3) sometimes the modem is not online, so run this command just to make sure (/usr/share/ofono/scripts/online-modem) 4) run this command with the phone locked to check if the greeter is showing snap decisions: /usr/share/ofono/scripts/dial-number 199 5) unlock the phone, repeat the previous step and let it ring until the incoming call snap decision go away. 6) wait for 30 seconds more before you lock the screen again. 7) the previous notification will be incorrectly shown on the greeter. These steps are not 100% reproducible, sometimes you get the wrong notification, and sometimes it triggers another bug that no notifications will be displayed anymore on the greeter, not even if you restart the approver. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-notifications/+bug/1327257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)
** Changed in: unity8 (Ubuntu) Status: Incomplete = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Low -- 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/1368798 Title: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch) Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: Triaged Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401084] Re: Missing rules in php5 abstraction
This was fixed in utopic in apparmor 2.8.98-0ubuntu2. ** Changed in: apparmor (Ubuntu) Status: Triaged = Fix Released -- 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/1401084 Title: Missing rules in php5 abstraction Status in apparmor package in Ubuntu: Fix Released Bug description: [impact] This bug prevents the proper functioning of apache mod_php with mod_apparmor. [steps to reproduce] 1) setuo apache and mod_php, verify php scripts are working 2) stop apache2 3) install mod_apparmor 4) restart apache2 5) with fix applied, apache should not generate rejections for /tmp/.ZendSem.* for php scripts confined by mod_apparmor [regression potential] The change to the php abstraction in the patch for this bug is a slight loosening of the apparmor policy. The risk of an introduced regression is small. [original description] I am using apache mod_apparmor with a wordpress blog. In my rules I have: #include abstractions/php5 But this did not allow all access that was needed: apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=k denied_mask=k fsuid=33 ouid=0 apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=wk denied_mask=wk fsuid=33 ouid=0 This access seems to be needed by opcache module, I found some info about it here: https://lists.ubuntu.com/archives/apparmor/2014-June/005879.html Ubuntu 14.04.1 apparmor 2.8.95~2430-0ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1401084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403468] Re: dnsmasq profile incomplete for lxc usage
This will be addressed in wily by apparmor 2.9.2-0ubuntu1. Attached is a patch for trusty. ** Patch added: dnsmasq-lxc_networking-lp1403468.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1403468/+attachment/4399532/+files/dnsmasq-lxc_networking-lp1403468.patch ** Description changed: + [impact] + + This bug prevents the proper functioning of sdsnmasq under lxc + + [steps to reproduce] + + 1) install lxc + 2) start container, do dns lookups within it + 3) with the fix applied, dnsmasq in the host os should not generate + apparmor rejections in syslog + + [regression potential] + + The change in the patch for this bug is a slight loosening of the + apparmor policy for dnsmasq. The risk of an introduced regression + is small. + + [original description] + Hi, I am using the dnsmasq profile with lxc, and I am getting DENIED messages like: Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400 audit(1418768818.310:865): apparmor=DENIED operation=truncate profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118 ouid=0 Adding rw for that path obviously makes it go away, and seems like a reasonable change. Thanks, James ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:27:18 2014 PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: - + UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2014-12-16T20:38:31.370339 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2014-12-17T11:21:47.159017 ** Changed in: apparmor (Ubuntu) Status: New = In Progress ** Description changed: [impact] - This bug prevents the proper functioning of sdsnmasq under lxc + This bug prevents the proper functioning of dsnmasq under lxc [steps to reproduce] 1) install lxc 2) start container, do dns lookups within it 3) with the fix applied, dnsmasq in the host os should not generate apparmor rejections in syslog [regression potential] The change in the patch for this bug is a slight loosening of the apparmor policy for dnsmasq. The risk of an introduced regression is small. [original description] Hi, I am using the dnsmasq profile with lxc, and I am getting DENIED messages like: Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400 audit(1418768818.310:865): apparmor=DENIED operation=truncate profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118 ouid=0 Adding rw for that path obviously makes it go away, and seems like a reasonable change. Thanks, James ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor-profiles 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:27:18 2014 PackageArchitecture: all ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 2014-12-16T20:38:31.370339 mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2014-12-17T11:21:47.159017 ** Description changed: [impact] - This bug prevents the proper functioning of dsnmasq under lxc + This bug prevents the proper functioning of dnsmasq under lxc [steps to reproduce] 1) install lxc 2) start container, do dns lookups within it 3) with the fix applied, dnsmasq in the host os should not generate apparmor rejections in syslog [regression potential] The change in the patch for this bug is a slight loosening of the apparmor policy for dnsmasq. The risk of an introduced regression is small. [original description] Hi, I am using the dnsmasq profile with lxc, and I am getting DENIED messages like: Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400 audit(1418768818.310:865): apparmor=DENIED operation=truncate profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118 ouid=0 Adding rw for that path
[Touch-packages] [Bug 1456253] [NEW] [security/privacy] Dash search setting should be removed
Public bug reported: The setting for Dash Search to choose between Phone only and Phone and Internet should be removed. This setting made sense in Unity 7, but it's not really handled by the new scopes framework and moreover, it doesn't really make sense in Unity8 which doesn't have search everything Home screen; user now has full control over what scopes are searched (by adding them to favorites or enabling child scopes via settings of aggregator scopes). In other words, the current function of Dash Search setting is pretty much broken (only smartscopesproxy honors it, 3rd party or local scopes ignore it). This leads to user confusion and a bunch of bug reports such as https://bugs.launchpad.net/today-scope/+bug/1440576 ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: Invalid ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Assignee: Pawel Stolowski (stolowski) Status: Confirmed ** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1456253 Title: [security/privacy] Dash search setting should be removed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: The setting for Dash Search to choose between Phone only and Phone and Internet should be removed. This setting made sense in Unity 7, but it's not really handled by the new scopes framework and moreover, it doesn't really make sense in Unity8 which doesn't have search everything Home screen; user now has full control over what scopes are searched (by adding them to favorites or enabling child scopes via settings of aggregator scopes). In other words, the current function of Dash Search setting is pretty much broken (only smartscopesproxy honors it, 3rd party or local scopes ignore it). This leads to user confusion and a bunch of bug reports such as https://bugs.launchpad.net/today- scope/+bug/1440576 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1456253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
** Also affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd-shim (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in the base for Ubuntu mobile products: Confirmed Status in systemd package in Ubuntu: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383086] Re: rebooting defeats the screen lock timeout
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383086 Title: rebooting defeats the screen lock timeout Status in unity8 package in Ubuntu: Triaged Bug description: If you enable pin unlock, then repeatedly enter the incorrect pin, eventually you'll get a message stating that the phone cannot be unlocked for 5 minutes. However, this restriction can be trivially bypassed by simply rebooting the phone (which takes less than 5 minutes :-) krillin, r117. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456259] [NEW] package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error
Public bug reported: It comes from a update asked by the system. Description:Ubuntu 14.04.2 LTS Release:14.04 rsyslog: Installé : 7.4.4-1ubuntu2.5 Candidat : 7.4.4-1ubuntu2.6 Table de version : 7.4.4-1ubuntu2.6 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages *** 7.4.4-1ubuntu2.5 0 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.3 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main i386 Packages 7.4.4-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 5.8.11-2ubuntu4 0 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 Date: Mon May 18 17:11:01 2015 DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error ErrorMessage: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error InstallationDate: Installed on 2014-07-28 (294 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error UpgradeStatus: Upgraded to trusty on 2014-08-03 (288 days ago) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1456259 Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error Status in rsyslog package in Ubuntu: New Bug description: It comes from a update asked by the system. Description: Ubuntu 14.04.2 LTS Release: 14.04 rsyslog: Installé : 7.4.4-1ubuntu2.5 Candidat : 7.4.4-1ubuntu2.6 Table de version : 7.4.4-1ubuntu2.6 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages *** 7.4.4-1ubuntu2.5 0 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.3 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main i386 Packages 7.4.4-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 5.8.11-2ubuntu4 0 500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages ProblemType: Package DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 Date: Mon May 18 17:11:01 2015 DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error ErrorMessage: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error InstallationDate: Installed on 2014-07-28 (294 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: unable to stat `./usr/lib/rsyslog/lmtcpclt.so' (which I was about to install): Input/output error UpgradeStatus: Upgraded to trusty on 2014-08-03 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1456259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446298] Re: Should show power dialog when turning on screen with a long-press
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1446298 Title: Should show power dialog when turning on screen with a long-press Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: To work around the power dialog appearing on resume, I implemented a band-aid fix [1] that prevented showing the dialog when the screen was off. But I didn't think of the case where you are waking up your device with an intentional long-press to show the power dialog. Currently, we don't show the dialog, we just turn on the screen. Ideally we'd also show the power dialog. This is a break-out bug from bug 1445662. [1] https://code.launchpad.net/~mterry/unity8/no-shutdown-dialog- while-suspended/+merge/246445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1446298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340510] Re: [Mako] Session screen seen upon quick power key strike
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- 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/1340510 Title: [Mako] Session screen seen upon quick power key strike Status in Mir: Opinion Status in Mir 0.4 series: Won't Fix Status in Mir 0.5 series: Won't Fix Status in Mir 0.6 series: Won't Fix Status in Unity System Compositor: New Status in mir package in Ubuntu: Opinion Status in unity8 package in Ubuntu: Confirmed Bug description: this is not seen on krillin Image #125 on N4 1) boot phone and unlock phone to display dash 2) strike power key to blank unblank screen quickly 3) the dash is seen instead of lockscreen for a brief moment logging against u-s-c as this was fixed, but power policy changes may have effected this To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1340510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
Here is the patch to address the apparmor userspace component of this bug as part of a trusty SRU. It's already been addressed in utopic and later. ** Patch added: tests-workaround_for_unix_socket_change-lp1425398.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+attachment/4399542/+files/tests-workaround_for_unix_socket_change-lp1425398.patch ** Description changed: - [rsyslog impact] - This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. + [apparmor impact] - [rsyslog test case] - (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the XX profiles are in enforce mode. section reported by sudo aa-status (if it's disabled, do sudo aa-enforce rsyslogd). + This bug generates false positives when using the apparmor regression + tests on the HWE kernels (utopic and newer), which means the kernel team + needs to examine test output to ensure that addiitional failures didn't + occur when testing new kernels. - (2) Install the utopic or newer hwe enablement stack reboot into the - kernel. Using the logger(1) utility should generate log messages (e.g. - logger foo) that are recorded in syslog; with this bug, they will be - blocked (grep DENIED /var/log/syslog). + [apparmor test case] - [rsyslog regression potential] - The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. + 1) install hwe kernel libapparmor-dev libdbus-1-dev attr + 2) apt-get source apparmor + 3) cd apparmor-2.8.95~2430/tests/regression/apparmor/ + 4) make USE_SYSTEM=1 + 5) sudo bash unix_socket_file.sh - [rsyslog addition info] - The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) - + If the bug has not been addressed, this test script will fail with the + following messages: + + Error: unix_socket_file failed. Test 'socket file (dgram); confined server / access (w)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied + FAIL - poll timed out' + Error: unix_socket_file failed. Test 'socket file (dgram); confined client w/ access (rw)' was expected to 'pass'. Reason for failure 'FAIL CLIENT - connect: Permission denied + FAIL - poll timed out' + + and a return code of 2 (echo $?). If it has been fixed it should return + silently, with a return code of 0. + + [apparmor regression potential] + + The patch for this bug only affects the test suite for apparmor, which + is a loosening of the policy used in the specific failing testcases. + There should be no effect on the apparmor implementation proper from + this fix. + + [apparmor additional info] + + This testsuite is run as part of the test-apparmor.py test script + from lp:qa-regression-testing, and used as part of the kernel update + process, but is useful for ensuring that apparmor is functioning + properly. [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii
[Touch-packages] [Bug 1394712] Re: [wizard] password set as passphrase even though it was set as 4-digit passcode during wizard
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1394712 Title: [wizard] password set as passphrase even though it was set as 4-digit passcode during wizard Status in unity8 package in Ubuntu: Incomplete Bug description: I just reflashed using the mtk tool, ran through the wizard and got this same symptom. v178 vivid arale unity8.log contained QProcess: Destroyed while process (/usr/lib/arm-linux-gnueabihf/ubuntu-system-settings/private/Ubuntu/SystemSettings/SecurityP rivacy/UbuntuSecurityPrivacyHelper) is still running. qml: Error setting security method: Could not set security mode === Original description below === current build number: 27 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-20 18:31:21 version version: 27 version ubuntu: 20141120 version device: 20141119 version custom: 20141120 Flashed with 'ubuntu-device-flash --channel=ubuntu-touch/vivid- proposed --bootstrap', and selected 4-digit passcode during wizard, but after locking the screen I noticed it was asking for a passphrase instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1394712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373259] Re: package python3-apparmor 2.8.95~2430-0ubuntu5 failed to install/upgrade: próba nadpisania /usr/lib/python3/dist-packages/apparmor/__init__.py, który istnieje także
Attached is a patch for the debian/control changes to address this issue as part of a trusty SRU. It should be fixed in wily in apparmor 2.9.2-0ubuntu1. ** Patch added: apparmor_fix_python3_overwrite.patch https://bugs.launchpad.net/ubuntu/trusty/+source/apparmor/+bug/1373259/+attachment/4399557/+files/apparmor_fix_python3_overwrite.patch -- 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/1373259 Title: package python3-apparmor 2.8.95~2430-0ubuntu5 failed to install/upgrade: próba nadpisania /usr/lib/python3/dist- packages/apparmor/__init__.py, który istnieje także w pakiecie apparmor-utils 2.8.0-0ubuntu11 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Triaged Status in apparmor source package in Utopic: Fix Released Bug description: error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-apparmor 2.8.95~2430-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Tue Sep 23 12:24:26 2014 DuplicateSignature: package:python3-apparmor:2.8.95~2430-0ubuntu5:próba nadpisania /usr/lib/python3/dist-packages/apparmor/__init__.py, który istnieje także w pakiecie apparmor-utils 2.8.0-0ubuntu11 ErrorMessage: próba nadpisania /usr/lib/python3/dist-packages/apparmor/__init__.py, który istnieje także w pakiecie apparmor-utils 2.8.0-0ubuntu11 InstallationDate: Installed on 2010-10-28 (1426 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=c1b1bf8e-186f-4164-b348-5753f1d5c37f ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: Sep 23 13:19:24 i5-4000 dbus[1005]: [system] AppArmor D-Bus mediation is enabled Title: package python3-apparmor 2.8.95~2430-0ubuntu5 failed to install/upgrade: próba nadpisania /usr/lib/python3/dist-packages/apparmor/__init__.py, który istnieje także w pakiecie apparmor-utils 2.8.0-0ubuntu11 UpgradeStatus: Upgraded to trusty on 2013-05-06 (505 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1373259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325580] Re: [split] unity8 and the greeter consume a lot of memory
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1325580 Title: [split] unity8 and the greeter consume a lot of memory Status in unity8 package in Ubuntu: New Bug description: checking with htop on image #49 i see unity8 consuming ~130M RES constantly. after the split greeter landed in image #59 htop shows ~200M RES for unity8 and additionally another ~90M RES for the unity8-greeter process which also seems to constantly run. the higher ram usage is pretty noticeable when using multiple webapps, using more than two the ones in background constantly gets SIGKILLed ... before i could run up to 6 of them before the restarting happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1325580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
I do not know how to do it. I mean: when the computer freezes it is impossible to file any bug report. And I think that filing a bug report for a working (with the old kernel) system is useless... -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Expired Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Touch-packages] [Bug 1456195] [NEW] Zero-minimum possessive groups does not match empty string
Public bug reported: The 14.04/15.04 pcre version doesn't match some inputs with possessive qualfiers: $ echo 'a'|pcregrep '(([^b]*+(b.)?)*+)*+' $ Earlier versions (10.04, 12.04): $ echo 'a'|pcregrep '(([^b]*+(b.)?)*+)*+' a $ this is fixed with the following upstream commit (that applies cleanly to the 15.04 pcre): http://vcs.pcre.org/pcre?view=revisionrevision=1478 https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html ** Affects: pcre3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1456195 Title: Zero-minimum possessive groups does not match empty string Status in pcre3 package in Ubuntu: New Bug description: The 14.04/15.04 pcre version doesn't match some inputs with possessive qualfiers: $ echo 'a'|pcregrep '(([^b]*+(b.)?)*+)*+' $ Earlier versions (10.04, 12.04): $ echo 'a'|pcregrep '(([^b]*+(b.)?)*+)*+' a $ this is fixed with the following upstream commit (that applies cleanly to the 15.04 pcre): http://vcs.pcre.org/pcre?view=revisionrevision=1478 https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1456195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** Description changed: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. + + === + break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 1a48632ffed61352a7810ce089dc5a8bcd505a60 ** Tags added: kernel-bug-break-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. === break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)
** Branch linked: lp:~ken-vandine/ubuntu/wily/systemd-shim/ntpfix -- 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/1390120 Title: Manually set time and date reverts to Automatically on restart (Ubuntu Phone) Status in the base for Ubuntu mobile products: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: 1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time Date settings and select Manually under Set the time and date: 2a - I set the time manually from Old_Time to New_Time and wait for New_Time to display in the Date Time Indicator at top-right 3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 10 seconds and then reverts to Old_Time 4a - Time Date settings agree with Old_Time and Automatically has been selected under Set the time and date: To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340927] Re: libapparmor aalogparse memory leak
Attached is a patch as a part of a trusty SRU. ** Patch added: libapparmor-fix_memory_leaks-lp1340927.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1340927/+attachment/4399540/+files/libapparmor-fix_memory_leaks-lp1340927.patch -- 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/1340927 Title: libapparmor aalogparse memory leak Status in AppArmor Linux application security framework: Fix Released Status in AppArmor 2.8 series: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: My kern.log is filled by lots of messages so aa-notify tries to parse them on first run. My OS is going down when there's no memory left because aa-notify leaks. I've found that leak is in /usr/bin/aa-notify file in function parse_message. If I comment lines from my ($test) = LibAppArmorc::parse_record($msg); to LibAppArmorc::free_record($test); then all goes fine. Program parses file and no memory leak is happened. Do I've got sources of my version (libapparmor-perl (2.8.0-5.1) from ubuntu) and found that some variables from aa_log_record struct were not freed by the free_record function. These are char *net_local_addr; char *net_foreign_addr; Could this be a reason of a leak? I haven't much time right now to compile and run tests. So I posted just information I've found and commented lines in bugged function to get my system working. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1340927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296667] Re: dovecot/apparmor: profile not found
This will be fixed in wily with apparmor 2.9.2-0ubuntu1. Attached is patch to update the dovecot profiles for a trusty SRU. ** Patch added: profiles-dovecot-updates-lp1296667.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1296667/+attachment/4399538/+files/profiles-dovecot-updates-lp1296667.patch ** Description changed: + [impact] + + This bug prevents dovecot users from using the apparmor policies shipped + in the apparmor-profiles package without significant modifications. + + [steps to reproduce] + + 1) install and setup dovecot and confirm that it's functioning as +expected + 2) install the apparmor-profiles package + 3) restart dovecot to ensure apparmor policies are being applied + 4) if this bug has been addressed, dovecot should start successfully +without generating apparmor rejections + + [regression potential] + + The change in the patch for this bug updates the dovecot policy to + match the most recent apparmor release (2.9.2). These add missing + policies, restructure a few things to common abstractions, and grant + additional permissions. Any regressions related to this patch would + be strictly limited to the policy for dovecot. + + [original description] + I'm on Ubuntu 14.04 LTS. Since last week I get these messages: [11468.257576] type=1400 audit(1395659127.103:38560): apparmor=ALLOWED operation=connect profile=/usr/lib/dovecot/imap-login name=/run/dovecot/config pid=30971 comm=imap-login requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [11491.128691] type=1400 audit(1395659149.988:38616): apparmor=ALLOWED operation=exec info=profile not found error=-2 profile=/usr/sbin/dovecot name=/usr/lib/dovecot/auth pid=30978 comm=dovecot requested_mask=x denied_mask=x fsuid=0 ouid=0 [11551.171186] type=1400 audit(1395659210.056:38853): apparmor=ALLOWED operation=capable profile=/usr/sbin/dovecot pid=31620 comm=dovecot capability=36 capname=block_suspend [11551.171338] type=1400 audit(1395659210.056:38854): apparmor=ALLOWED operation=exec info=profile not found error=-2 profile=/usr/sbin/dovecot name=/usr/lib/dovecot/auth pid=31630 comm=dovecot requested_mask=x denied_mask=x fsuid=0 ouid=0 When I then start dovecot I get these in mail.log: Mar 24 08:42:52 polly dovecot: master: Dovecot v2.2.9 starting up (core dumps disabled) Mar 24 08:42:52 polly dovecot: master: Fatal: execv(/usr/lib/dovecot/log) failed: No such file or directory Mar 24 08:42:52 polly dovecot: master: Error: service(anvil): command startup failed, throttling for 2 secs Mar 24 08:42:52 polly dovecot: master: Error: service(log): child 1387 returned error 84 (exec() failed) Mar 24 08:42:52 polly dovecot: master: Error: service(log): command startup failed, throttling for 2 secs Mar 24 08:42:52 polly dovecot: master: Error: service(ssl-params): command startup failed, throttling for 2 secs Mar 24 08:55:42 polly dovecot: master: Error: service(config): command startup failed, throttling for 2 secs Mar 24 08:55:42 polly dovecot: master: Error: service(imap-login): command startup failed, throttling for 2 secs I tried to purge and reinstall apparmor(-profiles) but that didn't fix this issue. I did a aa-disable dovecot and now the errors are gone. -- 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/1296667 Title: dovecot/apparmor: profile not found Status in AppArmor Linux application security framework: New Status in apparmor package in Ubuntu: New Bug description: [impact] This bug prevents dovecot users from using the apparmor policies shipped in the apparmor-profiles package without significant modifications. [steps to reproduce] 1) install and setup dovecot and confirm that it's functioning as expected 2) install the apparmor-profiles package 3) restart dovecot to ensure apparmor policies are being applied 4) if this bug has been addressed, dovecot should start successfully without generating apparmor rejections [regression potential] The change in the patch for this bug updates the dovecot policy to match the most recent apparmor release (2.9.2). These add missing policies, restructure a few things to common abstractions, and grant additional permissions. Any regressions related to this patch would be strictly limited to the policy for dovecot. [original description] I'm on Ubuntu 14.04 LTS. Since last week I get these messages: [11468.257576] type=1400 audit(1395659127.103:38560): apparmor=ALLOWED operation=connect profile=/usr/lib/dovecot/imap-login name=/run/dovecot/config pid=30971 comm=imap-login requested_mask=rw denied_mask=rw fsuid=0 ouid=0 [11491.128691] type=1400 audit(1395659149.988:38616): apparmor=ALLOWED operation=exec info=profile not found error=-2 profile=/usr/sbin/dovecot name=/usr/lib/dovecot/auth pid=30978 comm=dovecot
[Touch-packages] [Bug 1455797] Re: Merge libx11 2:1.6.3-1 (main) from Debian unstable (main)
https://launchpad.net/ubuntu/+source/libx11/2:1.6.3-1ubuntu1 ** Changed in: libx11 (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1455797 Title: Merge libx11 2:1.6.3-1 (main) from Debian unstable (main) Status in libx11 package in Ubuntu: Fix Committed Bug description: libx11 (2:1.6.3-1) unstable; urgency=medium * New upstream release. * Drop 006_tailor_pt_BR.UTF-8_Compose.diff, no longer necessary. * Rediff 003_recognize_glibc_2.3.2_locale_names.diff. * Let uscan verify tarball signatures. -- Julien Cristau jcris...@debian.org Thu, 30 Apr 2015 22:31:01 +0200 libx11 (2:1.6.2-3) unstable; urgency=medium [ Julien Cristau ] * libx11-6.symbols: yet another 64bit arch (ppc64el). Closes: #749728. -- Cyril Brulebois k...@debian.org Mon, 18 Aug 2014 01:39:32 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1455797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
@james we can land in vivid first if we need to, and the fix does not need to be made to utopic We do need the fix to land by May 21 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: In Progress Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1006898] Re: [SRU] dnsmasq fails at leasing issues when using vlan mode
Jorge, Chuck, can you get that update/uploaded? -- 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/1006898 Title: [SRU] dnsmasq fails at leasing issues when using vlan mode Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Precise: Triaged Bug description: ** Issue ** There is an issue with the way nova uses dnsmasq in VLAN mode. It starts up a single copy of dnsmasq for each vlan on the network host (or on every host in multi_host mode). The problem is in the way that dnsmasq binds to an ip address and port[2]. Both copies can respond to broadcast packet, but unicast packets can only be answered by one of the copies. In nova this means that guests from only one project will get responses to their unicast dhcp renew requests. Unicast projects from guests in other projects get ignored. What happens next is different depending on the guest os. Linux generally will send a broadcast packet out after the unicast fails, and so the only effect is a small (tens of ms) hiccup while interface is reconfigured. It can be much worse than that, however. I have seen cases where Windows just gives up and ends up with a non-configured interface. This bug was first noticed by some users of openstack who rolled their own fix. Basically, on linux, if you set the SO_BINDTODEVICE socket option, it will allow different daemons to share the port and respond to unicast packets, as long as they listen on different interfaces. I managed to communicate with Simon Kelley, the maintainer of dnsmasq and he has integrated a fix[3] for the issue in the current version[1] of dnsmaq. [3] http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12 ** Development Fix ** This has been fixed in quantal with the newer version of dnmasq. ** Stable Fix ** I have backported the patch which fixes this issue, I have attached the debdiff and the buildlog. ** Test Case ** 1. Install openstack with vlan mode. 2. Watch instances loose their IP addresses. ** Regression Potential ** Minimal, most installations dont use this type of networking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1006898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
Erroneous test failures can (and should) be overridden in proposed- migration. Also the requirement is not that the package *reach* the development release before being SRUed, only that it be *uploaded* to the development series. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: In Progress Status in Upstart: Fix Committed Status in upstart package in Ubuntu: In Progress Status in upstart source package in Utopic: New Status in upstart source package in Vivid: New Status in upstart source package in Wily: In Progress Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
** Description changed: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. === - break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 1a48632ffed61352a7810ce089dc5a8bcd505a60 + break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file Status in linux package in Ubuntu: In Progress Status in upstart package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in upstart source package in Vivid: Invalid Bug description: As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid- adt-upstart/?, upstart's test fail almost all the time, on ok 53 - with single line command writing fast and exiting not ok 54 - with single line command writing lots of data fast and exiting wrong value for bytes, expected 3145728 got 3018027 at tests/test_job_process.c:3886 (test_start). 1..153 FAIL: test_job_process Sometimes they succeed on one architecture, and with lots of luck on both, but this is way too flaky to be an useful test. This keeps blocking the propagation of other packages from -proposed. This was most likely triggered by the kernel update from 3.18 to 3.19. === break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 1a48632ffed61352a7810ce089dc5a8bcd505a60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304447] Re: apport-bug crashing on server install
Attached is the changes as part of an SRU for trusty. ** Patch added: apparmor_apport-lp1304447.patch https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1304447/+attachment/4399536/+files/apparmor_apport-lp1304447.patch ** Description changed: + [impact] + + This bug prevents apport from reporting apparmor bugs on systems with + non-UTF-8 characters showing up in syslog (the kernel reporting raw + information from hardware is a common culprit). + + [steps to reproduce] + + 1) on a system with non-UTF-8 characters in syslog, run 'apport -p apparmor -f' +if the bug has been addressed, this should generate a report as +expected instead of causing apport to crash. + + [regression potential] + + The change in the patch for this bug solely modifies the apparmor + apport hook. It could potentially introduce more breakage there (but + couldn't affect apparmor mediation); also the lp:qa-regression-testign + test-apparmor.py attempts to exercise the apport hook, and this is + exercised in as part of every linux kernel update by the kernel team + (who frequently hit this issue due to the quirkiness of some of + their hardware). + + [original description] + jenkins@dagmar:~$ sudo apport-bug apparmor --save testlib.apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .ERROR: hook /usr/share/apport/package-hooks/source_apparmor.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) + 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_apparmor.py, line 48, in add_info - report['KernLog'] = recent_kernlog(sec_re) - File /usr/share/apport/package-hooks/source_apparmor.py, line 24, in recent_kernlog - for line in open(file): - File /usr/lib/python3.4/codecs.py, line 313, in decode - (result, consumed) = self._buffer_decode(data, self.errors, final) + 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_apparmor.py, line 48, in add_info + report['KernLog'] = recent_kernlog(sec_re) + File /usr/share/apport/package-hooks/source_apparmor.py, line 24, in recent_kernlog + for line in open(file): + File /usr/lib/python3.4/codecs.py, line 313, in decode + (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 6574: invalid continuation byte -- 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/1304447 Title: apport-bug crashing on server install Status in apparmor package in Ubuntu: Fix Released Bug description: [impact] This bug prevents apport from reporting apparmor bugs on systems with non-UTF-8 characters showing up in syslog (the kernel reporting raw information from hardware is a common culprit). [steps to reproduce] 1) on a system with non-UTF-8 characters in syslog, run 'apport -p apparmor -f' if the bug has been addressed, this should generate a report as expected instead of causing apport to crash. [regression potential] The change in the patch for this bug solely modifies the apparmor apport hook. It could potentially introduce more breakage there (but couldn't affect apparmor mediation); also the lp:qa-regression-testign test-apparmor.py attempts to exercise the apport hook, and this is exercised in as part of every linux kernel update by the kernel team (who frequently hit this issue due to the quirkiness of some of their hardware). [original description] jenkins@dagmar:~$ sudo apport-bug apparmor --save testlib.apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .ERROR: hook /usr/share/apport/package-hooks/source_apparmor.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
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
this workaround works: http://askubuntu.com/questions/588538/whats-the- correct-driver-to-use-with-a-geforce-6150se-nforce-430-on-lubuntu-14 but IMHO it is not acceptable for two reasons: 1) it is an all proprietary solution 2) it works bad (noveau under kernel 3.2.0 worked better) -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Confirmed Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core
[Touch-packages] [Bug 1452300] Re: Reboot takes too long
** Changed in: unity8 (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in the base for Ubuntu mobile products: Fix Released Status in powerd package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in powerd source package in Vivid: Fix Released Status in powerd package in Ubuntu RTM: Fix Released Bug description: Test case. - Make sure phone is not plugged in. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378095] Re: aa-complain traceback when marking multiple profiles
the fix has been uploaded to wily it seems
https://launchpad.net/ubuntu/+source/apparmor/2.9.2-0ubuntu1
unsubscribing sponsors as well since previous comment suggested that the
security team want to deal with the update and not have this particular
fix sponsored on its own
** Changed in: apparmor (Ubuntu)
Importance: Undecided = High
** Changed in: apparmor (Ubuntu)
Status: Confirmed = 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/1378095
Title:
aa-complain traceback when marking multiple profiles
Status in AppArmor Linux application security framework:
Fix Released
Status in AppArmor 2.9 series:
Fix Released
Status in AppArmor master series:
Fix Released
Status in apparmor package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
Confirmed
Bug description:
[SRU justification]
[Impact]
$ sudo aa-complain /etc/apparmor.d/usr.lib.postfix.*
Setting /etc/apparmor.d/usr.lib.postfix.anvil to complain mode.
Traceback (most recent call last):
File /usr/sbin/aa-complain, line 30, in module
tool.cmd_complain()
File /usr/lib/python3/dist-packages/apparmor/tools.py, line 171, in
cmd_complain
apparmor.read_profiles()
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2573, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2599, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 3277, in
store_list_var
raise AppArmorException(_('Redefining existing variable %s: %s in %s') %
(list_var, value, filename))
apparmor.common.AppArmorException: 'Redefining existing variable @{TFTP_DIR}:
/var/tftp /srv/tftpboot in /etc/apparmor.d/usr.sbin.dnsmasq'
$ sudo grep -R TFTP_DIR /etc/apparmor.d/
/etc/apparmor.d/usr.sbin.dnsmasq:@{TFTP_DIR}=/var/tftp /srv/tftpboot
/etc/apparmor.d/usr.sbin.dnsmasq: @{TFTP_DIR}/ r,
/etc/apparmor.d/usr.sbin.dnsmasq: @{TFTP_DIR}/** r,
Looks like the tools are re-parsing everything, but not resetting
whatever is storing the variable declarations.
[Test Case]
sudo aa-enforce /etc/apparmor.d/*
got error
[Regression Potential]
[Other Info]
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1378095/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1010909] Re: permission denied: /usr/bin/{mktexpk, mktextfm}
This will be fixed in wily with apparmor 2.9.2-0ubuntu1. Attached is a
patch for this issue as part of a trusty SRU.
** Patch added: profiles-texlive_font_generation-lp1010909.patch
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1010909/+attachment/4399534/+files/profiles-texlive_font_generation-lp1010909.patch
** Description changed:
+ [impact]
+
+ This bug prevents viewing dvi files with evince while confined by
+ apparmor.
+
+ [steps to reproduce]
+
+ 1) install evince, ensure evince apparmor policy is enabled
+ 2) view a dvi with evince
+ 3) with the fix applied, evince should be able to display the dvi
+ document and should not generate apparmor rejections in syslog
+
+ [regression potential]
+
+ The change in the patch for this bug is a loosening of the apparmor
+ policy for the sanitized helpers of evince. The risk of an introduced
+ regression is small.
+
+ [original description]
+
1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) apt-cache policy evince apparmor texlive
evince:
- Installed: 3.14.1-0ubuntu1
- Candidate: 3.14.1-0ubuntu1
- Version table:
- *** 3.14.1-0ubuntu1 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.14.1-0ubuntu1
+ Candidate: 3.14.1-0ubuntu1
+ Version table:
+ *** 3.14.1-0ubuntu1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
apparmor:
- Installed: 2.8.98-0ubuntu4
- Candidate: 2.8.98-0ubuntu4
- Version table:
- *** 2.8.98-0ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 2.8.98-0ubuntu4
+ Candidate: 2.8.98-0ubuntu4
+ Version table:
+ *** 2.8.98-0ubuntu4 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
texlive:
- Installed: 2014.20141024-1ubuntu1
- Candidate: 2014.20141024-1ubuntu1
- Version table:
- *** 2014.20141024-1ubuntu1 0
- 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 2014.20141024-1ubuntu1
+ Candidate: 2014.20141024-1ubuntu1
+ Version table:
+ *** 2014.20141024-1ubuntu1 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
+ 100 /var/lib/dpkg/status
3) What is expected to happen is when one attempts to open
https://bugs.launchpad.net/ubuntu/+source/texlive-
bin/+bug/1010909/+attachment/4282336/+files/example.dvi it does so
successfully.
4) What happens instead is it hangs indefinitely, as per output of running
evince via a terminal
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282345/+files/error.txt
. This would appear to be due to apparmor as per:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282344/+files/kern.log
However, attempting to disable the offending profile fails:
sudo aa-complain /usr/bin/evince//sanitized_helper
/usr/bin/evince//sanitized_helper does not exist, please double-check the
path.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: texlive-binaries 2009-11ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 9 17:05:03 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: texlive-bin
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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
Status in apparmor package in Ubuntu:
Triaged
Bug description:
[impact]
This bug prevents viewing dvi files with evince while confined by
apparmor.
[steps to reproduce]
1) install evince, ensure evince apparmor policy is enabled
2) view a dvi with evince
3) with the fix applied, evince should be able to display the dvi
document and should not generate apparmor rejections in syslog
[regression potential]
The change in the patch for this bug is a loosening of the apparmor
policy for the sanitized helpers of evince. The risk of an introduced
regression is small.
[original description]
1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) apt-cache policy evince apparmor texlive
evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
*** 3.14.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100
[Touch-packages] [Bug 1456240] Re: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click
** Changed in: unity Status: Confirmed = In Progress ** Changed in: unity (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1456240 Title: AP failure: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Recently, an AP test has started failing consistently: unity.tests.test_panel.PanelIndicatorEntryTests.test_menu_opens_closes_on_click Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456245] [NEW] AP failure: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open
Public bug reported: Recently, an AP test has started failing consistently: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.3.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1456245 Title: AP failure: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Recently, an AP test has started failing consistently: unity.tests.test_quicklist.QuicklistActionTests.test_right_click_opens_quicklist_if_already_open Need to investigate if a regression has been introduced or if the test needs to be updated to work with a new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1456245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421623 Title: Welcome wizard claims GPS is less accurate than wifi based location Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: First boot welcome wizard in location sections claims GPS is less accurate than network based location service from HERE. While this can be theoretically true in some insane corner case, in normal life GPS is far more accurate. To help form correct text here are main differences. GPS - more accurate, but slow to acquire fix, does not work indoors, drains battery more, no need for internet connection, does not send any data out. Network based location - almost instant to get coarse location, works indoors, accuracy depends on network coverage in the area, more power efficient, requires internet connection. To get location data about visible GSM network and wifi networks needs to be send to 3rd party server. tested on krillin vivid-proposed r107 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456253] Re: [security/privacy] Dash search setting should be removed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1456253 Title: [security/privacy] Dash search setting should be removed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: The setting for Dash Search to choose between Phone only and Phone and Internet should be removed. This setting made sense in Unity 7, but it's not really handled by the new scopes framework and moreover, it doesn't really make sense in Unity8 which doesn't have search everything Home screen; user now has full control over what scopes are searched (by adding them to favorites or enabling child scopes via settings of aggregator scopes). In other words, the current function of Dash Search setting is pretty much broken (only smartscopesproxy honors it, 3rd party or local scopes ignore it). This leads to user confusion and a bunch of bug reports such as https://bugs.launchpad.net/today- scope/+bug/1440576 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1456253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456253] Re: [security/privacy] Dash search setting should be removed
see bug #1422700 ** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1456253 Title: [security/privacy] Dash search setting should be removed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: The setting for Dash Search to choose between Phone only and Phone and Internet should be removed. This setting made sense in Unity 7, but it's not really handled by the new scopes framework and moreover, it doesn't really make sense in Unity8 which doesn't have search everything Home screen; user now has full control over what scopes are searched (by adding them to favorites or enabling child scopes via settings of aggregator scopes). In other words, the current function of Dash Search setting is pretty much broken (only smartscopesproxy honors it, 3rd party or local scopes ignore it). This leads to user confusion and a bunch of bug reports such as https://bugs.launchpad.net/today- scope/+bug/1440576 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1456253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456253] Re: [security/privacy] Dash search setting should be removed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-scopes-api (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1456253 Title: [security/privacy] Dash search setting should be removed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: The setting for Dash Search to choose between Phone only and Phone and Internet should be removed. This setting made sense in Unity 7, but it's not really handled by the new scopes framework and moreover, it doesn't really make sense in Unity8 which doesn't have search everything Home screen; user now has full control over what scopes are searched (by adding them to favorites or enabling child scopes via settings of aggregator scopes). In other words, the current function of Dash Search setting is pretty much broken (only smartscopesproxy honors it, 3rd party or local scopes ignore it). This leads to user confusion and a bunch of bug reports such as https://bugs.launchpad.net/today- scope/+bug/1440576 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1456253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
@Alfonso
Updated version of the script in comment #5 looks good to me...
--
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/1454625
Title:
Cannot send MMS messages with combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1215120] Re: It should be possible to queue a phone lock during a call
** Changed in: unity8 (Ubuntu) Assignee: Michael Terry (mterry) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1215120 Title: It should be possible to queue a phone lock during a call Status in PowerD: New Status in unity8 package in Ubuntu: Triaged Bug description: When a user is in a call and manually turns the screen off, Android will continue showing their dialer app, but when the call ends, the phone will be locked. I think users might expect that same behavior. Either we can queue the lock until the call ends or we can lock in the background and keep showing the dialer-app in the meantime. To manage notifications about this bug go to: https://bugs.launchpad.net/powerd/+bug/1215120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
Sorry I got a working xorg adding nomodeset to boot but the screen resolution is wrong (1024x768 instead of FHD 1920x1080). Hope this helps... -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Expired Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1455406] Re: Search history popover displaced when OSK opens
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/revision/1438 -- 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/1455406 Title: Search history popover displaced when OSK opens Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: With a vivid based image, do a search in the dash. Clear it, start a second one (the popover should appear). When the OSK comes up, the popver is displaced, being partly off-screen, and covering the input field. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455406] Re: Search history popover displaced when OSK opens
Appears to be caused by these changes: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/langing- popoverfix/+merge/252066 -- 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/1455406 Title: Search history popover displaced when OSK opens Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: With a vivid based image, do a search in the dash. Clear it, start a second one (the popover should appear). When the OSK comes up, the popver is displaced, being partly off-screen, and covering the input field. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
This is the content of Xorg.1.log: [ 12693.660]. X.Org X Server 1.11.3 Release Date: 2011-12-16 [ 12693.660] X Protocol Version 11, Revision 0 [ 12693.660] Build Operating System: Linux 2.6.42-37-generic x86_64 Ubuntu [ 12693.660] Current Operating System: Linux babi-desk 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 [ 12693.660] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-68-generic root=UUID=000bc455-e879-4d2d-a416-659e9668f49a ro quiet splash vt.handoff=7 [ 12693.660] Build Date: 16 October 2013 04:41:23PM [ 12693.660] xorg-server 2:1.11.4-0ubuntu10.14 (For technical support please see http://www.ubuntu.com/support). [ 12693.660] Current version of pixman: 0.30.2 [ 12693.660] -Before reporting problems, check http://wiki.x.org --to make sure that you have the latest version. [ 12693.660] Markers: (--) probed, (**) from config file, (==) default setting, --(++) from command line, (!!) notice, (II) informational, --(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 12693.660] (==) Log file: /var/log/Xorg.1.log, Time: Sun Sep 21 22:34:51 2014 [ 12693.660] (==) Using config file: /etc/X11/xorg.conf [ 12693.660] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 12693.664] (==) No Layout section. Using the first Screen section. [ 12693.664] (**) |--Screen Default Screen (0) [ 12693.664] (**) | |--Monitor default monitor [ 12693.664] (==) No device specified for screen Default Screen. --Using the first device section listed. [ 12693.664] (**) | |--Device Default Device [ 12693.664] (==) No monitor specified for screen Default Screen. --Using a default monitor configuration. [ 12693.664] (==) Automatically adding devices [ 12693.664] (==) Automatically enabling devices [ 12693.664] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 12693.664] -Entry deleted from font path. [ 12693.664] (==) FontPath set to: --/usr/share/fonts/X11/misc, --/usr/share/fonts/X11/100dpi/:unscaled, --/usr/share/fonts/X11/75dpi/:unscaled, --/usr/share/fonts/X11/Type1, --/usr/share/fonts/X11/100dpi, --/usr/share/fonts/X11/75dpi, --/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, --built-ins [ 12693.664] (==) ModulePath set to /usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules [ 12693.664] (II) The server relies on udev to provide the list of input devices. --If no devices become available, reconfigure udev or disable AutoAddDevices. [ 12693.664] (II) Loader magic: 0x7f65757a3b00 [ 12693.664] (II) Module ABI versions: [ 12693.664] -X.Org ANSI C Emulation: 0.4 [ 12693.664] -X.Org Video Driver: 11.0 [ 12693.664] -X.Org XInput driver : 16.0 [ 12693.664] -X.Org Server Extension : 6.0 [ 12693.665] (--) PCI:*(0:0:13:0) 10de:03d6:1043:83a4 rev 162, Mem @ 0xde00/16777216, 0xc000/268435456, 0xdd00/16777216, BIOS @ 0x/131072 [ 12693.660]. X.Org X Server 1.11.3 Release Date: 2011-12-16 [ 12693.660] X Protocol Version 11, Revision 0 [ 12693.660] Build Operating System: Linux 2.6.42-37-generic x86_64 Ubuntu [ 12693.660] Current Operating System: Linux babi-desk 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 [ 12693.660] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-68-generic root=UUID=000bc455-e879-4d2d-a416-659e9668f49a ro quiet splash vt.handoff=7 [ 12693.660] Build Date: 16 October 2013 04:41:23PM [ 12693.660] xorg-server 2:1.11.4-0ubuntu10.14 (For technical support please see http://www.ubuntu.com/support). [ 12693.660] Current version of pixman: 0.30.2 [ 12693.660] -Before reporting problems, check http://wiki.x.org --to make sure that you have the latest version. [ 12693.660] Markers: (--) probed, (**) from config file, (==) default setting, --(++) from command line, (!!) notice, (II) informational, --(WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 12693.660] (==) Log file: /var/log/Xorg.1.log, Time: Sun Sep 21 22:34:51 2014 [ 12693.660] (==) Using config file: /etc/X11/xorg.conf [ 12693.660] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 12693.664] (==) No Layout section. Using the first Screen section. [ 12693.664] (**) |--Screen Default Screen (0) [ 12693.664] (**) | |--Monitor default monitor [ 12693.664] (==) No device specified for screen Default Screen. --Using the first device section listed. [ 12693.664] (**) | |--Device Default Device [ 12693.664] (==) No monitor specified for screen Default Screen. --Using a default monitor configuration. [ 12693.664] (==) Automatically adding devices [ 12693.664] (==) Automatically enabling devices [ 12693.664] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 12693.664] -Entry deleted from font path. [ 12693.664] (==) FontPath set to: --/usr/share/fonts/X11/misc, --/usr/share/fonts/X11/100dpi/:unscaled, --/usr/share/fonts/X11/75dpi/:unscaled,
[Touch-packages] [Bug 1357053] Re: [Launcher] home button should reset dash department
** Branch linked: lp:~huangzhiquan/unity8/resetDashNavigation -- 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/1357053 Title: [Launcher] home button should reset dash department Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Triaged Bug description: I've seen people filtering the dash by department and then trying to use the home button in the launcher to get back to the starting position. Should the Launcher's home button clear any department selection? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1357053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446634] Re: Active windows loses focus after returning from Dash if another Always on top window is present
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446634 Title: Active windows loses focus after returning from Dash if another Always on top window is present Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from Dash if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. This is very similar to bug #1366583. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446165] Re: the skydome effect of the cube plugin doesn't work with unity 7
** Changed in: unity Status: New = Fix Committed ** Changed in: unity Milestone: None = 7.3.3 ** Changed in: unity (Ubuntu) Importance: Undecided = High ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Eleni Maria Stea (hikiko) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446165 Title: the skydome effect of the cube plugin doesn't work with unity 7 Status in Compiz: New Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: when running compiz + unity 7 the skydome doesn't appear correctly (looks like it has a weird transformation) screenshot: https://i.imgur.com/nnj4y1f.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1446165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240757] Re: Bridge not created if bind9 is on
This bug just hit me in Ubuntu 14.04 LTS and is quite serious because
LTS is used in servers, and it is common to try to have virtualization
(LXC) as well as being configured as DNS servers (bind9).
Additionally, under some configurations at least, the whole DNS
resolving becomes malfunctioning as 10.0.3.1 is the first entry in
/etc/resolv.conf (put by resolvconf / dnsmasq) but it is not accessible.
As a result, any DNS resolving wait some seconds for a timeout!
A detailed workaround without reboot:
1. Add this line in /etc/bind/named.conf.options before the last line::
listen-on { ! 10.0.3.1; };
2. Restart bind9::
service bind9 restart
3. Restart the LXC network::
service lxc-net restart
--
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/1240757
Title:
Bridge not created if bind9 is on
Status in bind9 package in Ubuntu:
Confirmed
Status in lxc package in Ubuntu:
Confirmed
Bug description:
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not
take the 10.0.3.1 address. If bind9 is stopped, then LXC successfully
creates the bridge.
Expected result: LXC will create the bridge, even if bind9 is on.
---
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2013-06-29 (110 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
MarkForUpload: True
Package: lxc
PackageArchitecture: i386
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic
root=UUID=4c07e19b-cf33-4cbd-ab6d-fe300398b22b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
RelatedPackageVersions:
bind9utils 1:9.9.2.dfsg.P1-2ubuntu2.1
apparmor 2.8.0-0ubuntu11
Tags: raring
Uname: Linux 3.8.0-31-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.bind.named.conf.local: [modified]
mtime.conffile..etc.bind.named.conf.local: 2013-08-01T12:03:20.742316
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1240757/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456205] Re: unit test for ActionSelectionPopover is not complete
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/1456205 Title: unit test for ActionSelectionPopover is not complete Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The unit test for ActionSelectionPopover only checks the default value of properties. It does not open an ActionSelectionPopover and verify that clicking an option in the popover will trigger the desired action. These tests should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1456205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456221] [NEW] while installing regional settings
Public bug reported: I just tried to install additional language pack ProblemType: Package DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 CrashReports: 600:111:116:0:2015-05-18 15:39:26.381760672 +0200:2015-05-18 15:39:26.381760672 +0200:/var/crash/rsyslog.0.uploaded 600:0:116:207779:2015-05-18 15:34:47.344107389 +0200:2015-05-18 15:34:48.344107389 +0200:/var/crash/network-manager.0.crash 640:0:116:1587420:2015-05-18 15:39:23.263367891 +0200:2015-05-18 15:39:25.286591098 +0200:/var/crash/rsyslog.0.crash 600:0:116:207759:2015-05-18 15:34:47.332113265 +0200:2015-05-18 15:34:48.332113265 +0200:/var/crash/wpasupplicant.0.crash 644:0:116:0:2015-05-18 15:39:24.607106916 +0200:2015-05-18 15:39:24.607106916 +0200:/var/crash/rsyslog.0.upload Date: Mon May 18 15:34:48 2015 DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.2:package wpasupplicant is already installed and configured ErrorMessage: package wpasupplicant is already installed and configured InstallationDate: Installed on 2015-05-18 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) SourcePackage: wpa Title: package wpasupplicant 2.1-0ubuntu1.2 failed to install/upgrade: package wpasupplicant is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1456221 Title: while installing regional settings Status in wpa package in Ubuntu: New Bug description: I just tried to install additional language pack ProblemType: Package DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 CrashReports: 600:111:116:0:2015-05-18 15:39:26.381760672 +0200:2015-05-18 15:39:26.381760672 +0200:/var/crash/rsyslog.0.uploaded 600:0:116:207779:2015-05-18 15:34:47.344107389 +0200:2015-05-18 15:34:48.344107389 +0200:/var/crash/network-manager.0.crash 640:0:116:1587420:2015-05-18 15:39:23.263367891 +0200:2015-05-18 15:39:25.286591098 +0200:/var/crash/rsyslog.0.crash 600:0:116:207759:2015-05-18 15:34:47.332113265 +0200:2015-05-18 15:34:48.332113265 +0200:/var/crash/wpasupplicant.0.crash 644:0:116:0:2015-05-18 15:39:24.607106916 +0200:2015-05-18 15:39:24.607106916 +0200:/var/crash/rsyslog.0.upload Date: Mon May 18 15:34:48 2015 DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.2:package wpasupplicant is already installed and configured ErrorMessage: package wpasupplicant is already installed and configured InstallationDate: Installed on 2015-05-18 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) SourcePackage: wpa Title: package wpasupplicant 2.1-0ubuntu1.2 failed to install/upgrade: package wpasupplicant is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1456221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456126] Re: Alarm snooze countdown is not start from the time of tapping on Snooze button
** Project changed: ubuntu-clock-app = indicator-datetime ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1456126 Title: Alarm snooze countdown is not start from the time of tapping on Snooze button Status in The Date and Time Indicator: New Status in indicator-datetime package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 42 device name: arale channel: ubuntu-touch/tangxi/devel-proposed last update: 2015-05-15 04:19:20 version version: 42 version device: 1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c version custom: 8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d Steps to reproduce: 1.Launch Clock app and set Snooze time for 5 minnutes 2.Create a alarm and wait for it to trigger 3.Waiting for more than one minutes, then tap on Snooze 4.Waiting for the alarm rings again 5.Check the real time interval after tap on Snooze Expected results: The time interval is 5 minutes after the time of tapping on Snooze Actual results: The alarm snooze countdown is start from the time of alarm rings To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1456126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1052024] Re: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1052024 Title: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on Applications. This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1052024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Status: In Progress = Fix Committed ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity/7.2 Importance: Undecided = Low ** Changed in: unity/7.2 Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity/7.2 Milestone: None = 7.2.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453742] Re: xorg started to systematically crash after every suspend/resume
Yeah, and that's precisely what's ridiculous: discouraging dual boot. It's like not recommendiung the use of laptops, or that of an external keyboard, or some given screen resolutions. Ubuntu should struggle to better support all normal use scenarios, rather than picking those where it doesn't work well and say you are strongly advised not to do it. At this point I'd suggest updating the documentation to state that you're strongly advised not to use Ubuntu. -- 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/1453742 Title: xorg started to systematically crash after every suspend/resume Status in xorg package in Ubuntu: Incomplete Bug description: - I suspended - I pressed a key to resume - the screen turned on and I was prompted for the password as usual - I entered the password = my previous session was lost, every application I had left open prior to suspend was closed, all unsaved data was lost and everything was as if I had just rebooted. Then I tried suspending and resuming again just for the sake of testing, and it happened again, exactly the same way. It now happens 100% of the times systematically. Now maybe (I hope) it will stop happening after a reboot, but for now, once it has started happening, it has become systematic. This is not the first time I observe it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 11 11:55:56 2015 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-10-11 (576 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-24 (351 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon May 11 11:55:34 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445082] Re: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1445082 Title: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, navigating to an icon that has multiple windows and hitting Enter should open that application's window Spread. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456221] Re: while installing regional settings
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1456221 Title: while installing regional settings Status in wpa package in Ubuntu: New Bug description: I just tried to install additional language pack ProblemType: Package DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 CrashReports: 600:111:116:0:2015-05-18 15:39:26.381760672 +0200:2015-05-18 15:39:26.381760672 +0200:/var/crash/rsyslog.0.uploaded 600:0:116:207779:2015-05-18 15:34:47.344107389 +0200:2015-05-18 15:34:48.344107389 +0200:/var/crash/network-manager.0.crash 640:0:116:1587420:2015-05-18 15:39:23.263367891 +0200:2015-05-18 15:39:25.286591098 +0200:/var/crash/rsyslog.0.crash 600:0:116:207759:2015-05-18 15:34:47.332113265 +0200:2015-05-18 15:34:48.332113265 +0200:/var/crash/wpasupplicant.0.crash 644:0:116:0:2015-05-18 15:39:24.607106916 +0200:2015-05-18 15:39:24.607106916 +0200:/var/crash/rsyslog.0.upload Date: Mon May 18 15:34:48 2015 DuplicateSignature: package:wpasupplicant:2.1-0ubuntu1.2:package wpasupplicant is already installed and configured ErrorMessage: package wpasupplicant is already installed and configured InstallationDate: Installed on 2015-05-18 (0 days ago) InstallationMedia: Ubuntu MATE 14.04.2 Trusty Tahr - LTS amd64 (20150323) SourcePackage: wpa Title: package wpasupplicant 2.1-0ubuntu1.2 failed to install/upgrade: package wpasupplicant is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1456221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
Edit of Comment #17: I am on OS version 19, as I have a problem with automatic updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Mobile: New Status in messaging-app package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
Filed bug report here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1456184 -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Expired Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
[Touch-packages] [Bug 1456184] [NEW] NVidia VGA freeze with new kernels
Public bug reported: VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) Freeze when used with new kernels (3.13 or 3.16) and works with 3.2.0 (from 12.04 precise) or 3.13 (trusty) with nomodesed option (but wrong resolution) lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 apt-cache policy xorg xorg: Installato: 1:7.7+1ubuntu8.1 Candidato: 1:7.7+1ubuntu8.1 Tabella versione: *** 1:7.7+1ubuntu8.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+1ubuntu8 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 18 14:29:23 2015 DistUpgraded: 2015-05-12 07:07:16,098 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.28, 3.13.0-52-generic, x86_64: installed vboxhost, 4.3.28, 3.2.0-83-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2010-07-30 (1752 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=000bc455-e879-4d2d-a416-659e9668f49a ro nomodeset nomdmonddf nomdmonisw vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2015-05-12 (6 days ago) dmi.bios.date: 08/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon May 18 14:24:41 2015 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1456184 Title: NVidia VGA freeze with new kernels Status in xorg package in Ubuntu: New Bug description: VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) Freeze when used with new kernels (3.13 or 3.16) and works with 3.2.0 (from 12.04 precise) or 3.13 (trusty) with nomodesed option (but wrong resolution) lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 apt-cache policy xorg xorg: Installato: 1:7.7+1ubuntu8.1 Candidato: 1:7.7+1ubuntu8.1
[Touch-packages] [Bug 1322121] Re: pictures taken with flash are almost completely black
@Yuan-Chen: https://bugs.launchpad.net/tangxi/+bug/1446069 is valid but is a different bug to the dark pictures we get with arale. The arale bug is https://bugs.launchpad.net/tangxi/+bug/1455494 where dark pictures are produced with the flash actually firing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1322121 Title: pictures taken with flash are almost completely black Status in Camera App: Invalid Status in the base for Ubuntu mobile products: Incomplete Status in android package in Ubuntu: Triaged Status in qtubuntu-camera package in Ubuntu: Triaged Bug description: On the mako / Nexus 4, the camera has an LED to use for camera flash. Our camera app supports the flash, and fires it while taking a picture with flash enabled. However, the resulting image ends up severely underexposed, to the point where almost the entire image is black. Steps to reproduce: 1. Run the camera app. 2. Take a picture with flash off. 3. Turn the flash setting on and take a picture of the same scene again. 4. Go to the gallery app to view the results. Expected results: The picture with flash should appear brighter (or, at least, appear how most with-flash pictures look). Actual results: The picture with flash is almost completely black, with only a few dim details in the brightest parts of the image. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1322121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
I managed to create an apport report just before screen freeze (changing console to ctrl+alt+f1) and saved to file this time. See attached report. ** Attachment added: Apport report https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1389732/+attachment/4399452/+files/apport.xorg.ks87z0ff.apport -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Expired Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core:
[Touch-packages] [Bug 1444643] Re: While in Launcher keynav, icon Spread does not work as expected
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1444643 Title: While in Launcher keynav, icon Spread does not work as expected Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, if an icon has multiple windows open and one of the windows was last focused, clicking on the icon does not bring up the application Spread, it only focuses the window. The expected behavior would be to open the application Spread if it was the last focused window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444626] Re: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1444626 Title: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using the arrow keys to navigate a Quicklist and using the left arrow key to exit the Quicklist, Launcher keynav should activate and on the icon for which the Quicklist was active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444113] Re: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1444113 Title: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using Launcher keynav to open the BFB Quicklist and selecting a scope to open does not open the Dash until you use the mouse right click Quicklist navigation. Once you use the mouse right click, then keynav works as expected. Steps to reproduce: 1. Start a fresh instance of Unity. 2. *Do not* move the mouse into the BFB, ie Home, icon. 3. Start Launcher keynav by pressing Alt-F1. 4. Arrow to the right to open the BFB Quicklist. 5. Select any Scope to open. Expected results: The selected Scope will open in the Dash. Actual results: The Dash does not open. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366583] Re: Active windows loses focus after returning from HUD if another Always on top window is present
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366583 Title: Active windows loses focus after returning from HUD if another Always on top window is present Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from HUD if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. How to reproduce? 1. Open vlc and set it always on top 2. Open nautilus, try to rename a file using hud 3. As soon as rename option is pressed on hud, nautilus looses its focus and the focus is given to VLC. 4. To rename I have to re-select nautilus ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Sep 7 23:05:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-19-generic, x86_64: installed i915-3.15-3.13, 0.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] InstallationDate: Installed on 2014-04-13 (146 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lsusb: 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 003: ID 0ac8:c349 Z-Star Microelectronics 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 MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4a883016-3392-4731-824d-ac87981ccaef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03RAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP300E5X-A04IN dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03RAC:bd05/07/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5X-A04IN:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4C/300E5C/300E7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 7 22:23:30 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5539 vendor CMO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1366583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove compiz from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after export COMPIZ_CONFIG_PROFILE: env UNITY_LOW_GFX_MODE=1 export UNITY_LOW_GFX_MODE We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456205] [NEW] unit test for ActionSelectionPopover is not complete
Public bug reported: The unit test for ActionSelectionPopover only checks the default value of properties. It does not open an ActionSelectionPopover and verify that clicking an option in the popover will trigger the desired action. These tests should be added. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Low Status: Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided = Low -- 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/1456205 Title: unit test for ActionSelectionPopover is not complete Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The unit test for ActionSelectionPopover only checks the default value of properties. It does not open an ActionSelectionPopover and verify that clicking an option in the popover will trigger the desired action. These tests should be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1456205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] Re: The computer freeze randomly
** Changed in: xorg (Ubuntu) Status: Expired = Confirmed -- 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/1389732 Title: The computer freeze randomly Status in xorg package in Ubuntu: Confirmed Bug description: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the Nibbles (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel:
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
I'm also experiencing this bug. It started when I was using Chromium. Firefox and gimp was close. No torrent -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in hud package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically
** Branch linked: lp:~michael-sheldon/oxide/fix-1384357 -- 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/1384357 Title: Current composition is not canceled when a text input field is cleared programmatically Status in Oxide Webview: In Progress Status in Ubuntu Keyboard: Invalid Status in Web Browser App: Invalid Status in webbrowser-app package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) on a touch device, browse to http://mikeasoft.com/~mike/oxide-clear.html 2) focus the text field and type any word in it (e.g. Ubuntu) 3) tap the X below the text field, this clears it 4) press backspace on the OSK Expected result: nothing happens Current result: the previous preedit is restored and backspace deletes the last letter (in that example, the text field now contains Ubunt) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366583] Re: Active windows loses focus after returning from HUD if another Always on top window is present
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1366583 Title: Active windows loses focus after returning from HUD if another Always on top window is present Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from HUD if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. How to reproduce? 1. Open vlc and set it always on top 2. Open nautilus, try to rename a file using hud 3. As soon as rename option is pressed on hud, nautilus looses its focus and the focus is given to VLC. 4. To rename I have to re-select nautilus ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Sep 7 23:05:07 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-19-generic, x86_64: installed i915-3.15-3.13, 0.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] InstallationDate: Installed on 2014-04-13 (146 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lsusb: 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 003: ID 0ac8:c349 Z-Star Microelectronics 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 MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4a883016-3392-4731-824d-ac87981ccaef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03RAC
[Touch-packages] [Bug 1444113] Re: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1444113 Title: Opening BFB Quicklist using Launcher keynav doesn't work until moving mouse into the BFB icon Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using Launcher keynav to open the BFB Quicklist and selecting a scope to open does not open the Dash until you use the mouse right click Quicklist navigation. Once you use the mouse right click, then keynav works as expected. Steps to reproduce: 1. Start a fresh instance of Unity. 2. *Do not* move the mouse into the BFB, ie Home, icon. 3. Start Launcher keynav by pressing Alt-F1. 4. Arrow to the right to open the BFB Quicklist. 5. Select any Scope to open. Expected results: The selected Scope will open in the Dash. Actual results: The Dash does not open. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445082] Re: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1445082 Title: While in Launcher keynav, hitting Enter on an icon with multiple windows should open the application Spread Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, navigating to an icon that has multiple windows and hitting Enter should open that application's window Spread. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1131385] Re: Always on top prevents application spread from working
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove compiz from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after export COMPIZ_CONFIG_PROFILE: env UNITY_LOW_GFX_MODE=1 export UNITY_LOW_GFX_MODE We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1052024] Re: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1052024 Title: BFB Quicklist fails to work when mouse is used to right click and choose an option when Launcher is keynav mode Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on Applications. This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1052024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444626] Re: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1444626 Title: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When using the arrow keys to navigate a Quicklist and using the left arrow key to exit the Quicklist, Launcher keynav should activate and on the icon for which the Quicklist was active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444643] Re: While in Launcher keynav, icon Spread does not work as expected
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1444643 Title: While in Launcher keynav, icon Spread does not work as expected Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: While in Launcher keynav mode, if an icon has multiple windows open and one of the windows was last focused, clicking on the icon does not bring up the application Spread, it only focuses the window. The expected behavior would be to open the application Spread if it was the last focused window. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446165] Re: the skydome effect of the cube plugin doesn't work with unity 7
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1446165 Title: the skydome effect of the cube plugin doesn't work with unity 7 Status in Compiz: New Status in Unity: New Status in unity package in Ubuntu: Fix Released Bug description: when running compiz + unity 7 the skydome doesn't appear correctly (looks like it has a weird transformation) screenshot: https://i.imgur.com/nnj4y1f.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1446165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446634] Re: Active windows loses focus after returning from Dash if another Always on top window is present
This bug was fixed in the package unity - 7.3.2+15.10.20150512-0ubuntu1 --- unity (7.3.2+15.10.20150512-0ubuntu1) wily; urgency=medium [ Chris Townsend ] * Add new signal to tell the Launcher to terminate keynav mode and use that signal when a BFB quicklist item is chosen. (LP: #1052024, #1444643) * Add option to enable and disable Unity low graphics mode on the fly in ccsm or via gsettings. (LP: #1412937) * Remove code that is no longer needed and broke opening application spread while in Launcher keynav mode. (LP: #1445082) * Save the active window when showing the Dash so the correct window is focused when hiding the Dash. Fixes issue when Always on Top windows are present. (LP: #1446634) * Save the active window when showing the Hud so the correct window is focused when hiding the Hud. Fixes issue when Always on Top windows are present. (LP: #1366583) * Send signal to ensure the Dash will show when entering keynav mode since the first icon always highlighted is the BFB. (LP: #1444113) * When looking for the top-most valid window in a VP, also check if the window is focused if the window is set to Always on Top. This allows Launcher icon spread to work properly when a window is minimized an Always on Top exists in the group. (LP: #1131385) * When using the left arrow to exit a Quicklist, Launcher keynav is implied and should be active regardless of how the Quicklist was opened. (LP: #1444626) [ Eleni Maria Stea ] * The skydome rendering of the cube plugin was wrong with unity because transformation matrices set by the unityshell plugin were left in the opengl matrix stacks affecting other compiz plugins. Saving the compiz state at the beginning of the unityshell plugin rendering functions and restoring it at the end of them fixes the problem. (LP: #1446165) -- CI Train Bot ci-train-...@canonical.com Tue, 12 May 2015 13:10:15 + ** Changed in: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1446634 Title: Active windows loses focus after returning from Dash if another Always on top window is present Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Active window looses focus after returning from Dash if Always on top window like VLC is already running. The focus is given to VLC instead of the window on which HUD was invoke. This is very similar to bug #1366583. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1446634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433943] Re: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)
Sorry for late reply. Well It work that waymanually adding https://www.googleapis.com/auth/carddav to /usr/share/accounts/services /google-contacts.service But it requires evolution to get oauth2 token. So I have to grant access for evolution from UOA as well. A single sign-on for google from UOA is not enough. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1433943 Title: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid) Status in evolution-data-server package in Ubuntu: Confirmed Bug description: It seems Ubuntu does not enable CardDav scope (https://www.googleapis.com/auth/carddav) in online account. Ubuntu only enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a result when some application( ex. Syncevolution) tries to access it (through oauth2), it gives “authentication failed error”. For example, running following command: ''' SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\ loglevel=2 backend=carddav username=uoa:3,google-contacts\ syncURL=https://www.googleapis.com/.well-known/carddav ''' gives following error: “PROPFIND: Neon error code 1: 403 Forbidden, must not retry” NOTE: It is required that that the scope for accessing CardDAV needs to be specified in the sources too. Having it only in the APIs Console is not enough. Otherwise Google rejects access to the CardDAV resources with a 401 AuthSub challenge. Discussion on Syncevolution Mailing List: https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1433943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Thanks. If you comment out this line from fstab: tmpfs /var/lock tmpfs defaults 0 0 do things work again? Note that this is really broken: /var/lock must be a symlink to /run/lock, otherwise different programs use different lock directories. However, it's not really obvious that this is the cause for it. Why did you add this entry, out of interest? ** Summary changed: - Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd + boot failure when mounting /var/lock as a tmpfs -- 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/1452717 Title: boot failure when mounting /var/lock as a tmpfs Status in systemd package in Ubuntu: Won't Fix Bug description: Problem happens when choosing a normal boot. Works ok when choosing upstart. WORKAROUND: Do a fresh install (not upgrade). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452717] Re: boot failure when mounting /var/lock as a tmpfs
I confirm that when I add such a mount, the system boots into emergency mode. This is yet another case of mountall silently ignoring errors instead of failing, and we don't really want to proliferate these bugs. So I set this to wontfix for now. Thanks for your report! ** Changed in: systemd (Ubuntu) Status: Incomplete = Won't Fix -- 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/1452717 Title: boot failure when mounting /var/lock as a tmpfs Status in systemd package in Ubuntu: Won't Fix Bug description: Problem happens when choosing a normal boot. Works ok when choosing upstart. WORKAROUND: Do a fresh install (not upgrade). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
Pete's suggestion is also what OS X does: whenever you open the menu, it triggers a scan, with the first menu item saying Wi-Fi: Looking for networks… until the scan completes. When I suggested the same for Ubuntu a couple of years ago, I was told (by Mathieu, I think?) that it wouldn't apply to Network Manager because it is constantly scanning in the background. Is that still the case, or did I misremember, or has the behavior changed since? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453159] Re: [Ubuntu Phone BQ] GPS disabled after flight mode/restart
See also bug 1450925, where turning off Flight Mode turns on Bluetooth when it wasn't on before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1453159 Title: [Ubuntu Phone BQ] GPS disabled after flight mode/restart Status in Location Service: New Status in indicator-network package in Ubuntu: New Bug description: Hi! Steps: 1. Enable GPS from the status bar. 2. Change to Flight mode enabled 3. Change to Flight mode disabled Bug: GPS is disabled It's not happening all the times. I don't know the pattern. The GPS is losing its status a few times with a mobile restart too. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1453159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450925] Re: [Ubuntu Phone BQ] Bluetooth enabled after flight mode
See also bug 1453159, where turning off Flight Mode leaves the GPS off when it was on before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1450925 Title: [Ubuntu Phone BQ] Bluetooth enabled after flight mode Status in indicator-network package in Ubuntu: Confirmed Bug description: Hi! Steps: 1. Enable Flight mode from the status bar with bluetooth disabled. 2. Disable Flight mode Bug: Bluetooth is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1450925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1053048] Re: the system does not ignore comments in /etc/hostname
/etc/hostname is not specified to accept comments, lowering severity. ** Changed in: systemd (Ubuntu) Status: Confirmed = Triaged ** Changed in: systemd (Ubuntu) Importance: Medium = Wishlist -- 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/1053048 Title: the system does not ignore comments in /etc/hostname Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Quantal: Won't Fix Bug description: As found at bug 1052664 $ dpkg-query --show network-manager network-manager 0.9.6.0-0ubuntu7 $ cat /etc/hostname # xxx by cloud-init domU-12-31-39-0C-6C-81 This *should* be ok, as per 'man hostname': -F, --file filename Read the host name from the specified file. Comments (lines starting with a `#') are ignored. However, network-manager does not ignore the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1053048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450748] Re: 10de:0dfc NVRM Graphics Exception on resume from hibernate
Christopher, I tested this now with the newer nvidia driver as you suggested and so far the problem has not been reoccuring. Thanks! Thomas -- 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/1450748 Title: 10de:0dfc NVRM Graphics Exception on resume from hibernate Status in xorg package in Ubuntu: Incomplete Bug description: When I try to resume from hibernating, my DELL Latitude E6430 (nvidia prime disabled in bios and NVIDIA 346.59 driver is correctly being used) in Kubuntu 15.04 I often get the text console instead of X and the following error message being displayed, requiring a restart: May 1 11:13:49 posterior kernel: [52927.775439] NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 1 Error May 1 11:13:49 posterior kernel: [52927.775493] NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 2 Error May 1 11:13:49 posterior kernel: [52927.775536] NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 3 Error May 1 11:13:49 posterior kernel: [52927.775579] NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 4 Error May 1 11:13:49 posterior kernel: [52927.775621] NVRM: Xid (PCI::01:00): 13, Graphics Exception: Shader Program Header 9 Error May 1 11:13:49 posterior kernel: [52927.775665] NVRM: Xid (PCI::01:00): 13, Graphics Exception: ESR 0x405840=0xa200021e May 1 11:13:49 posterior kernel: [52927.775719] NVRM: Xid (PCI::01:00): 13, Graphics Exception: ChID 0017, Class 9197, Offset 1614, Data WORKAROUND: Use nouveau. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 1 11:25:19 2015 DistUpgraded: 2015-04-26 15:59:38,198 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-37-generic, x86_64: installed bbswitch, 0.8, 3.16.0-34-generic, x86_64: installed bbswitch, 0.8, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0534] InstallationDate: Installed on 2014-01-15 (471 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E6430 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/kubuntu--vg-root ro splash quiet plymouth:debug=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-04-26 (4 days ago) dmi.bios.date: 08/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd08/19/2014:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri May 1 11:14:44 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1450748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456066] [NEW] Laptop suspends immediately after startup
Public bug reported: When booting my laptop while docked with the lid down (pair of external monitors attached to dock), the system boots to the point of displaying the login dialog, but immediately suspends. When resumed from suspend by briefly pressing the power button, lightdm displays a login screen that just prompts for 'password' (no username). This is under xubuntu. Intuitively it seems that the system implements a default power manager policy, which suspends when the laptop lid is down, before having the chance to implement my policy which prohibits this when on mains power. This behaviour is new in 15.04, on 14.10 and earlier it worked as expected - at least gave me a chance to log in. There's an easy workaround: boot with the lid up (at least my dock permits this - I know of some that wouldn't), but it's annoying. Not sure what packages this is - lightdm is certainly running, but is this the culprit ? I doubt xfce4-power-manager has had a chance to start ? Is there a power management service in systemd that runs on boot ? $ lsb_release -r Release:15.04 $ apt-cache policy systemd systemd: Installed: 219-7ubuntu5 Candidate: 219-7ubuntu5 Version table: *** 219-7ubuntu5 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 219-7ubuntu3 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages $ apt-cache policy lightdm lightdm: Installed: 1.14.0-0ubuntu2 Candidate: 1.14.0-0ubuntu2 Version table: *** 1.14.0-0ubuntu2 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy xfce4-power-manager xfce4-power-manager: Installed: 1.4.3-0ubuntu1 Candidate: 1.4.3-0ubuntu1 Version table: *** 1.4.3-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.14.1-1ubuntu1 Candidate: 3.14.1-1ubuntu1 Version table: *** 3.14.1-1ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 18 16:25:49 2015 InstallationDate: Installed on 2015-05-13 (5 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=/dev/mapper/xubuntu-root2 ro quiet splash SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/01/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: syslog covering initial boot, resume, hard reset and boot with lid up https://bugs.launchpad.net/bugs/1456066/+attachment/4399298/+files/syslog -- 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/1456066 Title: Laptop suspends immediately after startup Status in systemd package in Ubuntu: New Bug description: When booting my laptop while docked with the lid down (pair of external monitors attached to dock), the system boots to the point of displaying the login dialog, but immediately suspends. When resumed from suspend by briefly pressing the power button, lightdm displays a login screen that just prompts for 'password' (no username). This is under xubuntu. Intuitively it seems that the system implements a default power manager policy, which suspends when the laptop lid is down, before having the chance to implement my policy which prohibits this when on mains power. This behaviour is new in 15.04, on 14.10 and earlier it worked as expected - at least gave me a chance to log in. There's an easy workaround: boot with the lid up (at least my dock permits this - I know of some that wouldn't), but it's annoying. Not sure what packages this is - lightdm is certainly running, but is this the culprit ? I doubt xfce4-power-manager has had a chance to start ? Is there a power management service in systemd that runs
[Touch-packages] [Bug 1455811] Re: Navigation bar should not drag page content
*** This bug is a duplicate of bug 1365179 *** https://bugs.launchpad.net/bugs/1365179 Thanks for the report. This is fixed in the development series, and will be propagated to a BQ official update very soon. ** This bug has been marked a duplicate of bug 1365179 [Browser] Top bar should overlay the page, not anchoring on top of it -- 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/1455811 Title: Navigation bar should not drag page content Status in webbrowser-app package in Ubuntu: New Bug description: Strange movement of page when dragging. REproduce: 1 open a page with a content much higher than the screen 2 drag the page down from top. Keep finger on the screen 3 After a second, the location bar disappears, and drag the whole page up under your finger You can test the behavior with the opposite direction, too. Sometimes the page is flickering after the location bar disappears/appears I think, the location bar should appear/disappear without sticking to the page content area. Bq Aquaris 4.5, Ubuntu 14.10 (22) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1455811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Martin Pitt, Attaching files that you requested. -- 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/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd Status in systemd package in Ubuntu: Incomplete Bug description: Problem happens when choosing a normal boot. Works ok when choosing upstart. WORKAROUND: Do a fresh install (not upgrade). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
** Attachment added: fstab https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399332/+files/fstab -- 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/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd Status in systemd package in Ubuntu: Incomplete Bug description: Problem happens when choosing a normal boot. Works ok when choosing upstart. WORKAROUND: Do a fresh install (not upgrade). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
** Attachment added: journal.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399331/+files/journal.txt -- 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/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd Status in systemd package in Ubuntu: Incomplete Bug description: Problem happens when choosing a normal boot. Works ok when choosing upstart. WORKAROUND: Do a fresh install (not upgrade). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 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: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455223] Re: [time and date] Searching for locations is slow and doesn't work offline
When I designed this, I didn't know it was going to be implemented by accessing the Internet -- though I might have guessed by re-reading the equivalent part of the Ubuntu installer spec. https://goo.gl/terpNZ So, add ubiquity to the list of callsites for that API. If I'd known it was going to access the Internet, I would have specified progress, error, and offline feedback. So, why does it use the Internet? What are some concrete examples of places that people would expect to show up, that wouldn't show up, if we relied entirely on an offline list? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1455223 Title: [time and date] Searching for locations is slow and doesn't work offline Status in libtimezonemap package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Bug description: Click on clock - Time and Date settings - Clock - Choose Locations - Click the + - Start typing San Franc When I'm at home, on a 300mbps connections, it takes several seconds to several minutes, when trying to add a new location. When I'm on a plane without internet connectivity, (ie, exactly when I most importantly need to change the time on my laptop to the new/next timezone), it doesn't work at all. Can we please, please, please move this timezone/location information to a locally cached database? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtimezonemap/+bug/1455223/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455811] Re: Navigation bar should not drag page content
*** This bug is a duplicate of bug 1365179 *** https://bugs.launchpad.net/bugs/1365179 Thank you. Good luck for the OS, and you all! -- 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/1455811 Title: Navigation bar should not drag page content Status in webbrowser-app package in Ubuntu: New Bug description: Strange movement of page when dragging. REproduce: 1 open a page with a content much higher than the screen 2 drag the page down from top. Keep finger on the screen 3 After a second, the location bar disappears, and drag the whole page up under your finger You can test the behavior with the opposite direction, too. Sometimes the page is flickering after the location bar disappears/appears I think, the location bar should appear/disappear without sticking to the page content area. Bq Aquaris 4.5, Ubuntu 14.10 (22) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1455811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
