[Touch-packages] [Bug 1384724] Re: click chroots do not have intltool
This is fixed with click 0.4.34.2 (https://launchpad.net/ubuntu/+source/click/0.4.34.2): """ click (0.4.34.2) vivid; urgency=medium ... [ David Planella ] * Adds internationalization tools and CMake macros required by the new Qt Creator app and scope templates that provide internationalization code. ... -- Ubuntu daily releaseMon, 03 Nov 2014 12:49:25 + ** Changed in: click (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1384724 Title: click chroots do not have intltool Status in “click” package in Ubuntu: Invalid Bug description: The cmake of the template app from the Ubuntu SDK fails with " Could not find intltool-merge, please install the intltool package" Installing that package works the problem around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1384724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
** Changed in: hwe-next/trusty Status: Triaged => In Progress -- 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/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work Status in HWE Next Project: Fix Released Status in HWE Next trusty series: In Progress Status in HWE Next utopic series: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Won't Fix Status in “systemd” source package in Trusty: In Progress Bug description: CID: 201402-14663 Dell Latitude 12 Rugged Extreme The microphone mute key does not work on this system, so as its LED Steps: 1. Install 14.04 + update (3.13.0-30), boot to desktop 2. Try to mute the microphone with the hotkey (fn+F4) Expected results: * Mic mute key should work, its LED should be lit and the "Mute" option for input device should be ticked after you press the mic mute key. Actual result: * Nothing happened. Debugging information: ubuntu@201402-14663:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 29 press ^Ccaught signal 2, cleaning up... xev cannot detect any microphone mute key event ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1501 F pulseaudio /dev/snd/controlC0: ubuntu 1501 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jul 9 23:57:11 2014 HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734 InstallationDate: Installed on 2014-07-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0TH1GJ dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 12 Rugged Extreme (7204) dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384724] Re: click chroots do not have intltool
** Changed in: click (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1384724 Title: click chroots do not have intltool Status in “click” package in Ubuntu: Invalid Bug description: The cmake of the template app from the Ubuntu SDK fails with " Could not find intltool-merge, please install the intltool package" Installing that package works the problem around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1384724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393474] Re: su call in postinst fails with "Killed" when not running from a logind shell
I could never reproduce it with "real" logins, so for now I suspect that this is due to the rather unusual way of running processes in a VM directly on a root shell on ttyS1, which circumvents any PAM/logind. I remember that this also breaks some other tests which expect automatic ACLs and other things that a proper PAM session provides, so I fixed autopkgtest to provide a PAM session in all cases: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=5d45a5999 ** Package changed: systemd-shim (Ubuntu) => autopkgtest (Ubuntu) ** Changed in: autopkgtest (Ubuntu) Status: New => Fix Committed ** Changed in: autopkgtest (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1393474 Title: su call in postinst fails with "Killed" when not running from a logind shell Status in “autopkgtest” package in Ubuntu: Fix Committed Bug description: Recent keystone autopkgtest runs (https://jenkins.qa.ubuntu.com/job /vivid-adt-keystone/?) fail during installation of test dependencies: Setting up keystone (1:2014.2-0ubuntu1) ... Killed dpkg: error processing package keystone (--configure): subprocess installed post-installation script returned error exit status 137 dpkg: dependency problems prevent configuration of adt-satdep: adt-satdep depends on keystone; however: Package keystone is not configured yet. This only seems to happen when running them with more than one CPU, like this: adt-run keystone --- qemu /srv/vm/adt-vivid-amd64-cloud.img --cpus 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1393474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393318] Re: Media-Hub can't play a file (*.mp3) downloaded with DownloadManager 0.1
** Summary changed:
- Media-Hub can't play a file (*.mp3) downlowded with DownloadManager 0.1
+ Media-Hub can't play a file (*.mp3) downloaded with DownloadManager 0.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1393318
Title:
Media-Hub can't play a file (*.mp3) downloaded with DownloadManager
0.1
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
New
Bug description:
When download *.mp3 file with DownloadManager 0.1, can't play it with
MediaPlayer.
The error in media-hub is: Client denied access to open_uri()
the code:
Rectangle {
width: parent.width
height: units.gu(20)
TextField {
id: text
text:
"http://www.everyayah.com/data/Ghamadi_40kbps/001001.mp3";
height: 50
anchors {
left: parent.left
right: button.left
rightMargin: units.gu(2)
}
}
Button {
id: button
text: "Download"
height: 50
anchors.right: parent.right
onClicked: {
single.download(text.text);
}
}
ProgressBar {
minimumValue: 0
maximumValue: 100
value: single.progress
anchors {
left: parent.left
right: parent.right
bottom: parent.bottom
}
SingleDownload {
id: single
}
}
}
MediaPlayer{
id: playSound
}
Button {
text:"Play file Downloaded"
onClicked: {
playSound.source=
"/home/phablet/.local/share/ubuntu-download-manager/com.ubuntu.developer.myApp/Downloads/001001.mp3"
playSound.play()
}
}
When click on the Button ("Play file Downloaded") le file is not
playing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1393318/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380761] Re: bug in Arabic keyboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1380761 Title: bug in Arabic keyboard Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: Tested on Ubuntu 14.10(r4) STEPS: 1-in "System Settings" add "Arabic keyboard" 2-lunch "Messagging" application 3-Create new Message 4-choise "Arabic keyboard" expected to happen: The keyboard show all Arabic lettre happened instead: it show only 3 lettres! "إ", "أ","آ". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1380761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380765] Re: bug in "Phone" application with "Arabic keyboard layout" actived
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1380765 Title: bug in "Phone" application with "Arabic keyboard layout" actived Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Tested on Ubuntu 14.10(r4) STEPS: 1-in "System Settings" add "Arabic keyboard layout" 2-lunch "Messagging" application 3-Create new Message 4-choise "Arabic keyboard" 5-lunch "Phone" application 6-tape this USSD: *222# expected to happen: in the input field we see *222# happened instead: in the input field we see 222#* to get the correcte USSD code we must active anthor keyboard layout (English or french) and run "Phone" application and tape *222# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1380765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384724] Re: click chroots do not have intltool
the logs of a click chroot creation http://pastebin.ubuntu.com/9067294/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1384724 Title: click chroots do not have intltool Status in “click” package in Ubuntu: New Bug description: The cmake of the template app from the Ubuntu SDK fails with " Could not find intltool-merge, please install the intltool package" Installing that package works the problem around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1384724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384724] Re: click chroots do not have intltool
The chroot.py in the lp:click lists the intltool as part of the frameworks. Still it is the intltool-debian package what gets installed when the click chroot is created. The cmake looks for the /usr/bin /intltool-merge when the intltool-debian installes to the /usr/share /intltool-debian/intltool-merge. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1384724 Title: click chroots do not have intltool Status in “click” package in Ubuntu: New Bug description: The cmake of the template app from the Ubuntu SDK fails with " Could not find intltool-merge, please install the intltool package" Installing that package works the problem around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1384724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393382] Re: A faulty .click scope can disable all .click scopes
** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Critical ** 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/1393382 Title: A faulty .click scope can disable all .click scopes Status in “unity-scopes-api” package in Ubuntu: Confirmed Bug description: 1. Install one or several .click scopes 2. Make sure they work 3. Install "ssbscope" from the click store All click scopes are then ignored by scope-registry "scoperegistry: unity::ResourceException: cannot open scope installation directory "/home/phablet/.local/share/unity-scopes//com.ubuntu.developer.psasse.sbbscope_sbbscope_0.8": No such file or directory scoperegistry: could not open Click installation directory, ignoring Click scopes" Log : http://paste.ubuntu.com/9054919/ ssbscope source : https://code.launchpad.net/sbbscope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1393382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
I'm also unable to reproduce this issue when mounting /userdata (and also it's bind mounts) with data=journal instead of data=ordered. This might be a consequence of it being slower, not yet sure. Decided to try that to see if I'd get any error when running e2fsck, but still nothing. Only side effect is that I can't really reproduce the problem. Running for almost an hour now, will let it for a few more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: New Status in “android” package in Ubuntu RTM: In Progress Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: In Progress Status in “linux-mako” package in Ubuntu RTM: New Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh" The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/13872
[Touch-packages] [Bug 1393683] [NEW] notification indicator shows new messages as being from yesterday
Public bug reported: If I receive SMS messages, they appear in the notification indicator as having happened "yesterday", immediately after being received. I suspect this is an issue with calculating times in UTC instead of local time. I noticed it less than 7 hours before midnight, and I'm in UTC-7, so in UTC it's technically already tomorrow, and my local "today" is technically yesterday. The actual time of day displayed in the indicator is correct, but the day itself is wrong. I noticed this on rtm krillin image 162. It probably isn't an issue in places near UTC, but it definitely shows up in the west hemisphere. I wouldn't be surprised if eastern time zones have the opposite symptom, showing "tomorrow" sometimes. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: rtm14 ue -- 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/1393683 Title: notification indicator shows new messages as being from yesterday Status in “messaging-app” package in Ubuntu: New Bug description: If I receive SMS messages, they appear in the notification indicator as having happened "yesterday", immediately after being received. I suspect this is an issue with calculating times in UTC instead of local time. I noticed it less than 7 hours before midnight, and I'm in UTC-7, so in UTC it's technically already tomorrow, and my local "today" is technically yesterday. The actual time of day displayed in the indicator is correct, but the day itself is wrong. I noticed this on rtm krillin image 162. It probably isn't an issue in places near UTC, but it definitely shows up in the west hemisphere. I wouldn't be surprised if eastern time zones have the opposite symptom, showing "tomorrow" sometimes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1393683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392615] Re: OA sign-in should not block
** Changed in: unity-scopes-api (Ubuntu) Status: New => In Progress -- 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/1392615 Title: OA sign-in should not block Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: If I login with my Google account and authorise YouTube access it appears that when I get 'near' to the Video scope (i.e. which includes YouTube) the Dash starts to become unresponsive. This manifests itself in swipes that take a few seconds to get actioned and scrolling freezes when moving between scopes. Removing YouTube access appears to cure this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1392615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387763] Re: deleting Google contacts not working reliably
This bug was fixed in the package address-book-service - 0.1.1+15.04.20141112-0ubuntu1 --- address-book-service (0.1.1+15.04.20141112-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Renato Araujo Oliveira Filho ] * Avoid create sources with duplicated Id; Remove address book sources based on source name instead of source id. (LP: #1387763) address-book-service (0.1.1+14.10.20141023~rtm-0ubuntu1) 14.09; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Renato Araujo Oliveira Filho ] * Make sure that the full name always get updated with some value. (LP: #1380094) -- Ubuntu daily releaseWed, 12 Nov 2014 15:30:49 + ** Changed in: address-book-service (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 address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1387763 Title: deleting Google contacts not working reliably Status in “address-book-service” package in Ubuntu: Fix Released Status in “address-book-service” package in Ubuntu RTM: In Progress Bug description: krillin build 132 on rtm Steps to repdouce: - create 2 google accounts - enable contact syncing on 1 of the accounts - let the sync happen and open addresss book to verify the contacts are displayed - go back to system settings for accounts - delete the google account associated with the contact sync - when prompted, say "No" to keep contact data - go back to address book Expected results: - all the contacts should be gone from address book Actual results: - all the contacts remain in the address book I've seen this work sometimes and fail quite often, so not sure what is going on. But it's pretty easy to reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1387763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381583] Re: imported pictures should show in Event for today
This bug was fixed in the package gallery-app - 0.0.67+15.04.20141112-0ubuntu1 --- gallery-app (0.0.67+15.04.20141112-0ubuntu1) vivid; urgency=low [ Arthur Mello ] * Delay the opening photo process until all media files are loaded when called by url handler (LP: #1389514) * Switch to events view after a media imported (LP: #1382109) * Set the TimeDigitized Exif field for the import date on imported files (LP: #1381583) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily releaseWed, 12 Nov 2014 22:27:36 + ** Changed in: gallery-app (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 gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1381583 Title: imported pictures should show in Event for today Status in Gallery App: In Progress Status in Ubuntu UX bugs: New Status in “gallery-app” package in Ubuntu: Fix Released Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: When pictures are imported into the gallery, via content-hub, we should always display them in the Event for the current day. Right now, the picture is played in the Event that corresponds to the metadata creation date which is very confusing because after the picture is imported you can't find it easily. Arthur and I discussed modifiying one of the standard exif tags (like DateTime, but don't modify CreationDate) with the current date of import as the gallery already sorts by a series of tags. Another solution would be to add a custom tag like (importDate) and change the sort to use that if it exists before falling back to other tags. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1381583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382109] Re: Events view should be shown on import
This bug was fixed in the package gallery-app - 0.0.67+15.04.20141112-0ubuntu1 --- gallery-app (0.0.67+15.04.20141112-0ubuntu1) vivid; urgency=low [ Arthur Mello ] * Delay the opening photo process until all media files are loaded when called by url handler (LP: #1389514) * Switch to events view after a media imported (LP: #1382109) * Set the TimeDigitized Exif field for the import date on imported files (LP: #1381583) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily releaseWed, 12 Nov 2014 22:27:36 + ** Changed in: gallery-app (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 gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1382109 Title: Events view should be shown on import Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: Fix Released Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: If a photo is imported via the content-hub, we should always make sure to display the Events view as the photo will show up by default there. Currenty if the gallery is open to a specific photo or album, after the import occurs we don't update the view so user has no idea where the imported picture is. Would be nice to directly open the imported picture but this won't work as we might get multiple import events in a row from content-hub in the case where the user "Dimissed" the open dialog multiple times. Next time gallery-app launched or displayed it will be delivered multiple events so we would not know which to open. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1382109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389514] Re: open photo from scope fails on first try
This bug was fixed in the package gallery-app - 0.0.67+15.04.20141112-0ubuntu1 --- gallery-app (0.0.67+15.04.20141112-0ubuntu1) vivid; urgency=low [ Arthur Mello ] * Delay the opening photo process until all media files are loaded when called by url handler (LP: #1389514) * Switch to events view after a media imported (LP: #1382109) * Set the TimeDigitized Exif field for the import date on imported files (LP: #1381583) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily releaseWed, 12 Nov 2014 22:27:36 + ** Changed in: gallery-app (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 gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1389514 Title: open photo from scope fails on first try Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: Fix Released Status in “gallery-app” package in Ubuntu RTM: New Bug description: The Photos scope and gallery app support a mechanism where a photo can be opened directly in the gallery by tapping 'open' on it in the photos scope. However, this appears to fail on the first try if Gallery hasn't been run before. Steps to reproduce this: 1. Flash the phone to get a fresh install. 2. Take some photos in the camera app. 3. Navigate to those photos in the Photos scope. 4. Select a photo and tap 'open'. Expected results: Selected photo opens in the gallery app. Actual results: Gallery app opens and shows the 'Events' view, but does not open the chosen photo. On second attempt, the expected results happen. I suspect that the gallery app may be getting stuck on indexing and thumbnailing the first time, and once that is done things work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1389514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393474] Re: su call in postinst fails with "Killed" when not running from a logind shell
** Package changed: keystone (Ubuntu) => systemd-shim (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1393474 Title: su call in postinst fails with "Killed" when not running from a logind shell Status in “systemd-shim” package in Ubuntu: New Bug description: Recent keystone autopkgtest runs (https://jenkins.qa.ubuntu.com/job /vivid-adt-keystone/?) fail during installation of test dependencies: Setting up keystone (1:2014.2-0ubuntu1) ... Killed dpkg: error processing package keystone (--configure): subprocess installed post-installation script returned error exit status 137 dpkg: dependency problems prevent configuration of adt-satdep: adt-satdep depends on keystone; however: Package keystone is not configured yet. This only seems to happen when running them with more than one CPU, like this: adt-run keystone --- qemu /srv/vm/adt-vivid-amd64-cloud.img --cpus 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1393474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393474] [NEW] su call in postinst fails with "Killed" when not running from a logind shell
You have been subscribed to a public bug: Recent keystone autopkgtest runs (https://jenkins.qa.ubuntu.com/job /vivid-adt-keystone/?) fail during installation of test dependencies: Setting up keystone (1:2014.2-0ubuntu1) ... Killed dpkg: error processing package keystone (--configure): subprocess installed post-installation script returned error exit status 137 dpkg: dependency problems prevent configuration of adt-satdep: adt-satdep depends on keystone; however: Package keystone is not configured yet. This only seems to happen when running them with more than one CPU, like this: adt-run keystone --- qemu /srv/vm/adt-vivid-amd64-cloud.img --cpus 2 ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New -- su call in postinst fails with "Killed" when not running from a logind shell https://bugs.launchpad.net/bugs/1393474 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.39
---
apparmor-easyprof-ubuntu (1.2.39) utopic; urgency=medium
* ubuntu/{music,pictures,video}_files*: allow access to global SD card
directories (LP: #1391930)
* ubuntu/ubuntu-scope-network, pending/ubuntu-scope-local-content: allow
scopes to read data from the apps data dir (LP: #1384286)
-- Jamie StrandbogeThu, 13 Nov 2014 09:54:18 -0600
** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “click-reviewers-tools” package in Ubuntu:
In Progress
Status in “unity-scopes-api” package in Ubuntu:
Fix Committed
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
In Progress
Status in “unity-scopes-api” source package in Utopic:
New
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
In Progress
Status in “click-reviewers-tools” source package in Vivid:
In Progress
Status in “unity-scopes-api” source package in Vivid:
Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
Fix Released
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391930] Re: Need a way for applications to ask permission to read/write in pictures/videos folders on SD card
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.39
---
apparmor-easyprof-ubuntu (1.2.39) utopic; urgency=medium
* ubuntu/{music,pictures,video}_files*: allow access to global SD card
directories (LP: #1391930)
* ubuntu/ubuntu-scope-network, pending/ubuntu-scope-local-content: allow
scopes to read data from the apps data dir (LP: #1384286)
-- Jamie StrandbogeThu, 13 Nov 2014 09:54:18 -0600
** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1391930
Title:
Need a way for applications to ask permission to read/write in
pictures/videos folders on SD card
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
In Progress
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
Fix Released
Bug description:
The camera and the gallery app today are authorized to read/write in
/home/$USER/Pictures and /home/$USER/Videos.
Now they also need to be able to read/write in the similar directories of the
SD card, for example:
- /media/phablet/064a-7494/Pictures
- /media/phablet/064a-7494/Videos
As a side note, we are using the following API in applications to retrieve
the path (e.g. /home/phablet/Pictures):
http://qt-project.org/doc/qt-5/qstandardpaths.html#writableLocation
To retrieve the similar path on the SD card we are considering using a
combination of that to guess the directory name (Pictures)
concatenated with the value of http://doc-snapshot.qt-
project.org/qt5-5.4/qstorageinfo.html#rootPath
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1391930/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381583] Re: imported pictures should show in Event for today
** Branch linked: lp:ubuntu/vivid-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1381583 Title: imported pictures should show in Event for today Status in Gallery App: In Progress Status in Ubuntu UX bugs: New Status in “gallery-app” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: When pictures are imported into the gallery, via content-hub, we should always display them in the Event for the current day. Right now, the picture is played in the Event that corresponds to the metadata creation date which is very confusing because after the picture is imported you can't find it easily. Arthur and I discussed modifiying one of the standard exif tags (like DateTime, but don't modify CreationDate) with the current date of import as the gallery already sorts by a series of tags. Another solution would be to add a custom tag like (importDate) and change the sort to use that if it exists before falling back to other tags. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1381583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382109] Re: Events view should be shown on import
** Branch linked: lp:ubuntu/vivid-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1382109 Title: Events view should be shown on import Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: If a photo is imported via the content-hub, we should always make sure to display the Events view as the photo will show up by default there. Currenty if the gallery is open to a specific photo or album, after the import occurs we don't update the view so user has no idea where the imported picture is. Would be nice to directly open the imported picture but this won't work as we might get multiple import events in a row from content-hub in the case where the user "Dimissed" the open dialog multiple times. Next time gallery-app launched or displayed it will be delivered multiple events so we would not know which to open. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1382109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387763] Re: deleting Google contacts not working reliably
** Branch linked: lp:ubuntu/vivid-proposed/address-book-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1387763 Title: deleting Google contacts not working reliably Status in “address-book-service” package in Ubuntu: In Progress Status in “address-book-service” package in Ubuntu RTM: In Progress Bug description: krillin build 132 on rtm Steps to repdouce: - create 2 google accounts - enable contact syncing on 1 of the accounts - let the sync happen and open addresss book to verify the contacts are displayed - go back to system settings for accounts - delete the google account associated with the contact sync - when prompted, say "No" to keep contact data - go back to address book Expected results: - all the contacts should be gone from address book Actual results: - all the contacts remain in the address book I've seen this work sometimes and fail quite often, so not sure what is going on. But it's pretty easy to reproduce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1387763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389514] Re: open photo from scope fails on first try
** Branch linked: lp:ubuntu/vivid-proposed/gallery-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1389514 Title: open photo from scope fails on first try Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: New Bug description: The Photos scope and gallery app support a mechanism where a photo can be opened directly in the gallery by tapping 'open' on it in the photos scope. However, this appears to fail on the first try if Gallery hasn't been run before. Steps to reproduce this: 1. Flash the phone to get a fresh install. 2. Take some photos in the camera app. 3. Navigate to those photos in the Photos scope. 4. Select a photo and tap 'open'. Expected results: Selected photo opens in the gallery app. Actual results: Gallery app opens and shows the 'Events' view, but does not open the chosen photo. On second attempt, the expected results happen. I suspect that the gallery app may be getting stuck on indexing and thumbnailing the first time, and once that is done things work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1389514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384724] Re: click chroots do not have intltool
** Changed in: click (Ubuntu) Assignee: (unassigned) => Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1384724 Title: click chroots do not have intltool Status in “click” package in Ubuntu: New Bug description: The cmake of the template app from the Ubuntu SDK fails with " Could not find intltool-merge, please install the intltool package" Installing that package works the problem around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1384724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 757551] Re: upowerd leaks memory with Logitech universal receiver
** Changed in: upower (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/757551 Title: upowerd leaks memory with Logitech universal receiver Status in “upower” package in Ubuntu: Confirmed Bug description: Binary package hint: upower I currently have 36 days of uptime on my laptop (using suspend a lot) and over time, I've noticed that the upowerd process got to the top of the list in terms of memory usage by claiming 1GB+. I can manage with this situation since I have 6GB of physical memory, but I'm sure that people with less in their laptops will not be so fortunate. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upower 0.9.5-4 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 Architecture: amd64 Date: Mon Apr 11 09:47:23 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/757551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
@Hui Wang: Yes, of course. That fix is in 204-5ubuntu20.9 which is waiting in https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 . This just requires an SRU team member to review/accept it from the queue. -- 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/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: In Progress Status in “systemd” source package in Trusty: Fix Released Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393612] Re: Protect against BadUSB device
Removing package for now, as it's not at all clear how to design this (at least udev is way too low in the stack to even potentially ask the user anything). I'm very sceptical of these approaches. Experience shows that popping up dialog boxes with security related questions à la "are you sure that ..." are at least annoying and rarely productive. And on a server you usually don't even have a way to interactively ask the user anything on hardware changes. If there is a way to detect "malicious" USB devices in some way, we absolutely should do that, but as versatile as they are, USB devices can do pretty much anything. They could act as an audio device to record what you are doing, as a network device to re-route traffic, or as a malicious keyboard (but that's not even the worst IMHO, as you then usually see that something funky is going on and yank it out again). It's nothing new at all that malicious hardware can exist and that hardware always trumps software in terms of trying to keep each other in check :-) ** Package changed: systemd (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1393612 Title: Protect against BadUSB device Status in Ubuntu: New Bug description: During the last months, it appeared that the theoretical threat of a compromised USB device acting as keyboard became a real possibility: https://srlabs.de/badusb. The solution against such threat is simply to ask the user the confirmation before binding a new USB device as keyboard and a solution was already documented: http://vogelchr.blogspot.in/2014/08 /controlling-usb-device-access-on-linux.html Similar solution already exist for MS Windows: http://robert.penz.name/930/protect-your-pc-against-the-badusb-attack- on-linux-and-windows Even though the probability to get a compromised USB device is low, the security threat is serious and since the solution is simple, Ubuntu should be protected properly asap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 18 02:48:36 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-25 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: LENOVO 4298RD9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=fa0ba264-7e15-48e1-89e6-3c88237a1903 ro persistent quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298RD9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4298RD9:pvrThinkPadX220Tablet:rvnLENOVO:rn4298RD9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298RD9 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1393612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
@ Martin Pitt, It seems the Dell microphone mute hotkey udev rule (below) is not in the systemd - 204-5ubuntu20.8 yet. I have a bug (https://bugs.launchpad.net /oem-priority/trusty/+bug/1339998) and need this udev rule be backported to trusty. Thanks, Hui. -- 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/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: In Progress Status in “systemd” source package in Trusty: Fix Released Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
The udev rule patch locates at: http://bazaar.launchpad.net/~hui.wang/systemd/systemd-fix-micmute- hotkey/revision/74 -- 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/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: In Progress Status in “systemd” source package in Trusty: Fix Released Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236508] Re: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- 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/1236508 Title: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger Status in Mir: Expired Status in The Ubuntu Power Consumption Project: Expired Status in Unity Mir: Incomplete Status in “unity8” package in Ubuntu: Expired Bug description: I've looked at the CPU, wakeup event and current drawn on a LG Nexus 4 comparing the Mir enabled and non-Mir versions of Unity8 with today's image + updates (at 18:00 UTC, 7th Oct 2013). I ran a 5 minute idle soak test with the screen set to be un-blanked at full brightness and measured the current drawn at 0.5 second intervals. The Mir enabled version of Unity is drawing on average ~143.7mA where as the non-Mir version is drawing 138.7mA, or around 5mA less current (~3.6% difference) Measuring CPU load (just Mir) Mir: 0.70% user,0.63% system, 1.33% total CPU usage Non-Mir: 0.17% user, 0.07% system, 0.23% total CPU usage Context Switches: Mir: 219.24 context switches/sec Non-Mir: 22.32 context switches/sec poll/epoll/nanosleeps Mir: 4.9664/sec Non-Mir: 3.1333/sec Total CPU of system: Mir: 0.87% Non-Mir: 0.70% So it seems that the Mir variant of Unity8 is busier and consumes more power than the non-Mir variety when idle. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1236508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370386] Re: libmirclient7 hang on client startup
[Expired for Mir because there has been no activity for 60 days.] ** Changed in: mir Status: Incomplete => Expired -- 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/1370386 Title: libmirclient7 hang on client startup Status in Mir: Expired Status in “mir” package in Ubuntu: Expired Bug description: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1370386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370386] Re: libmirclient7 hang on client startup
[Expired for mir (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mir (Ubuntu) Status: Incomplete => Expired -- 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/1370386 Title: libmirclient7 hang on client startup Status in Mir: Expired Status in “mir” package in Ubuntu: Expired Bug description: When starting up a mir 7 client on vmware (Ubuntu 14.04) it hangs in the following location: at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory. (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7679266c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x77b92e9b in MirWaitHandle::wait_for_all() () from /usr/lib/x86_64-linux-gnu/libmirclient.so.7 #3 0x00401027 in demo_client () #4 0x00400e97 in main () (This is mir_demo_client_basic from the mir_demos package) The mir_demo_standalone_* applications seem to work fine, and the mir_demo_server_* applications seem to be running nicely with a visible mouse cursor. This also happens with XMir, which is the most annoying part. It appears to be a regression, since I'm sure I had this running on an earlier update snapshot of Ubuntu 14.04 Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1370386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369645] Re: [945GCM-S2L, Realtek ALC883, Green Line Out, Rear] volume slider problem
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1369645 Title: [945GCM-S2L, Realtek ALC883, Green Line Out, Rear] volume slider problem Status in “alsa-driver” package in Ubuntu: Expired Bug description: i saw in sound setting... on left side of window, there" headphone " word was flashing below "analog output(built in audio)" just for seconds and with its dancing the sound was connecting- disconnectingthe connections are not loose...in windows os it works well on same pc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saurav 1926 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 15 21:28:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-13 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_Type: Volume slider, or mixer problems Title: [945GCM-S2L, Realtek ALC883, Green Line Out, Rear] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5u dmi.board.name: 945GCM-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5u:bd07/14/2008:svnGigabyteTechnologyCo.,Ltd.:pn945GCM-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCM-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GCM-S2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1369645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236508] Re: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger
[Expired for The Ubuntu Power Consumption Project because there has been no activity for 60 days.] ** Changed in: ubuntu-power-consumption Status: Incomplete => Expired -- 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/1236508 Title: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger Status in Mir: Expired Status in The Ubuntu Power Consumption Project: Expired Status in Unity Mir: Incomplete Status in “unity8” package in Ubuntu: Expired Bug description: I've looked at the CPU, wakeup event and current drawn on a LG Nexus 4 comparing the Mir enabled and non-Mir versions of Unity8 with today's image + updates (at 18:00 UTC, 7th Oct 2013). I ran a 5 minute idle soak test with the screen set to be un-blanked at full brightness and measured the current drawn at 0.5 second intervals. The Mir enabled version of Unity is drawing on average ~143.7mA where as the non-Mir version is drawing 138.7mA, or around 5mA less current (~3.6% difference) Measuring CPU load (just Mir) Mir: 0.70% user,0.63% system, 1.33% total CPU usage Non-Mir: 0.17% user, 0.07% system, 0.23% total CPU usage Context Switches: Mir: 219.24 context switches/sec Non-Mir: 22.32 context switches/sec poll/epoll/nanosleeps Mir: 4.9664/sec Non-Mir: 3.1333/sec Total CPU of system: Mir: 0.87% Non-Mir: 0.70% So it seems that the Mir variant of Unity8 is busier and consumes more power than the non-Mir variety when idle. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1236508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366703] Re: Google starred contacts should be marked as Favorites in Ubuntu touch (and vice-versa)
[Expired for syncevolution (Ubuntu) because there has been no activity for 60 days.] ** Changed in: syncevolution (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1366703 Title: Google starred contacts should be marked as Favorites in Ubuntu touch (and vice-versa) Status in “syncevolution” package in Ubuntu: Expired Bug description: When syncing contacts with google, the "Special" (starred) contacts are not marked as favorite in Ubuntu touch. For the same reason, when Favorite contacts are added, in Ubuntu they should be starred ar google level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1366703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236508] Re: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- 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/1236508 Title: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger Status in Mir: Expired Status in The Ubuntu Power Consumption Project: Expired Status in Unity Mir: Incomplete Status in “unity8” package in Ubuntu: Expired Bug description: I've looked at the CPU, wakeup event and current drawn on a LG Nexus 4 comparing the Mir enabled and non-Mir versions of Unity8 with today's image + updates (at 18:00 UTC, 7th Oct 2013). I ran a 5 minute idle soak test with the screen set to be un-blanked at full brightness and measured the current drawn at 0.5 second intervals. The Mir enabled version of Unity is drawing on average ~143.7mA where as the non-Mir version is drawing 138.7mA, or around 5mA less current (~3.6% difference) Measuring CPU load (just Mir) Mir: 0.70% user,0.63% system, 1.33% total CPU usage Non-Mir: 0.17% user, 0.07% system, 0.23% total CPU usage Context Switches: Mir: 219.24 context switches/sec Non-Mir: 22.32 context switches/sec poll/epoll/nanosleeps Mir: 4.9664/sec Non-Mir: 3.1333/sec Total CPU of system: Mir: 0.87% Non-Mir: 0.70% So it seems that the Mir variant of Unity8 is busier and consumes more power than the non-Mir variety when idle. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1236508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
It works fine if I move the writable paths under /, and it also works fine after creating another image file (ext4) that gets stored under /userdata, to be consumed by the writable paths (using bind-mounts and everything). But if I use bind mounts from /userdata/system-data directly, I can easily get it to break. The same setup works fine when using / instead (same bind-mounts and etc, but on a different dir path). The only peculiarity with /userdata is that it's shared between both containers. Ubuntu uses /userdata/system-data, /userdata/SWAP.img and /userdata/user-data. Android uses /userdata/android-data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: New Status in “android” package in Ubuntu RTM: In Progress Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: In Progress Status in “linux-mako” package in Ubuntu RTM: New Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh" The kernel team has verified
[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04
Do you have multiple monitors? -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381296] Re: Dragging app between workspaces freezes system
Alan Westhagen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1381296 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1381296 Title: Dragging app between workspaces freezes system Status in “xorg” package in Ubuntu: Incomplete Bug description: If I start Firefox in, say, workspace 2 and I drag it to workspce 1, the system freezes. The only way out that I have discovered is to use ctrl-alt-f1 to get a pseudo terminal, log in, then execute shutdown -r now This happens often. Workspaces work fine if I do not attempt to drag apps between workspaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1381296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376604] Re: Could not printing from LPT port with Ubuntu
ubuntuers_medan, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1376604 ** Tags added: precise raring trusty ** Package changed: ubuntu => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1376604 Title: Could not printing from LPT port with Ubuntu Status in “cups” package in Ubuntu: Incomplete Bug description: I have lenovo PC edge 73z, this PC has an LPT port. I've tried to install Windows in this PC, and it's printing well from LPT, but whe I reinstall it with ubuntu 12.04, 13.04, and 14.04, it would not work. When I try to add print, it's detecting my printing such as LQ310 and LQ2180, but in Printing Tes steps, it can't printing. I've also tried to print with the same print and with the same OS but at this time via USB, it working well. Please, any one have the solution for me? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1376604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381296] [NEW] Dragging app between workspaces freezes system
You have been subscribed to a public bug: If I start Firefox in, say, workspace 2 and I drag it to workspce 1, the system freezes. The only way out that I have discovered is to use ctrl-alt-f1 to get a pseudo terminal, log in, then execute shutdown -r now This happens often. Workspaces work fine if I do not attempt to drag apps between workspaces. ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: bot-comment -- Dragging app between workspaces freezes system https://bugs.launchpad.net/bugs/1381296 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376604] [NEW] Could not printing from LPT port with Ubuntu
You have been subscribed to a public bug: I have lenovo PC edge 73z, this PC has an LPT port. I've tried to install Windows in this PC, and it's printing well from LPT, but whe I reinstall it with ubuntu 12.04, 13.04, and 14.04, it would not work. When I try to add print, it's detecting my printing such as LQ310 and LQ2180, but in Printing Tes steps, it can't printing. I've also tried to print with the same print and with the same OS but at this time via USB, it working well. Please, any one have the solution for me? ** Affects: cups (Ubuntu) Importance: Low Status: Incomplete ** Tags: precise raring trusty -- Could not printing from LPT port with Ubuntu https://bugs.launchpad.net/bugs/1376604 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
Used links instead of bind-mounts (for /userdata) and was still able to reproduce the issue. So not necessarily related with bind-mounts itself. ** Also affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-mako (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “linux-mako” package in Ubuntu: New Status in “android” package in Ubuntu RTM: In Progress Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: In Progress Status in “linux-mako” package in Ubuntu RTM: New Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh" The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pa
[Touch-packages] [Bug 1363670] Re: 8480dn
keith, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1363670 ** Package changed: ubuntu => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1363670 Title: 8480dn Status in “cups” package in Ubuntu: Incomplete Bug description: Terrible print drivers for the Brother MFC-8480DN (connected via USB to the computer). I've been running Ubuntu since version 10 and in five versions the supplied Ubuntu drivers have never worked. Sometimes I get double copies when I choose one copy. Sometimes nothing prints. Sometimes I get the message: ERROR NAME; ioerror COMMAND; image OPERAND STACK; 10 --arraytype-- 10 0 --arraytype-- Sometimes when sending a job to the printer, it just shuts down and reboots. Sometimes it prints gibberish or blank pages. It happens whether I print from Firefox or Open office. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1363670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363670] [NEW] 8480dn
You have been subscribed to a public bug: Terrible print drivers for the Brother MFC-8480DN (connected via USB to the computer). I've been running Ubuntu since version 10 and in five versions the supplied Ubuntu drivers have never worked. Sometimes I get double copies when I choose one copy. Sometimes nothing prints. Sometimes I get the message: ERROR NAME; ioerror COMMAND; image OPERAND STACK; 10 --arraytype-- 10 0 --arraytype-- Sometimes when sending a job to the printer, it just shuts down and reboots. Sometimes it prints gibberish or blank pages. It happens whether I print from Firefox or Open office. ** Affects: cups (Ubuntu) Importance: Low Status: Incomplete -- 8480dn https://bugs.launchpad.net/bugs/1363670 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 103945] Re: desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop)
** Changed in: xorg-server Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/103945 Title: desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop) Status in X.Org X server: Incomplete Status in “xorg” package in Ubuntu: Fix Released Bug description: Binary package hint: xorg The feisty beta desktop cd for amd64 boots ok on my nc6400, but gdm fails to start. The error log suggests that xorg found the ati video card, but couldn't find a valid mode. If I remove /etc/X11/xorg.conf entirely, xorg still can't find a usable mode. If I hand-edit the xorg.conf to add some modelines, I can get 1024x768 to work. Here are some details that may help: $ lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc M52 [ATI Mobility Radeon X1300] $ sudo ddcprobe vbe: VESA 3.0 detected. oem: ATI ATOMBIOS vendor: (C) 1988-2005, ATI Technologies Inc. product: M52T 01.00 memory: 16384kb mode: 640x400x256 mode: 640x480x256 mode: 800x600x256 mode: 1024x768x256 mode: 1280x1024x256 mode: 640x480x32k mode: 640x480x64k mode: 640x480x16m mode: 800x600x32k mode: 800x600x64k mode: 800x600x16m mode: 1024x768x32k mode: 1024x768x64k mode: 1024x768x16m mode: 1280x1024x32k mode: 1280x1024x64k mode: 1280x1024x16m mode: 320x200x32k mode: 320x200x64k mode: 320x200x16m mode: 1600x1200x256 mode: 1600x1200x32k mode: 1600x1200x64k edid: edid: 1 3 id: 8d00 eisa: LPL8d00 serial: manufacture: 0 2005 input: analog signal. screensize: 30 19 gamma: 2.20 dpms: RGB, no active off, no suspend, no standby dtiming: 1280x800@59 monitorid: LGPhilipsLCD monitorid: LP141WX1-TLA $ sudo /usr/share/xresprobe/ddcprobe.sh res: 1280x800 disptype: crt name: freq: The ddcinfo seems off: this is definitely an lcd, not a crt. The input is digital, I'd think, and the dpms is probably wrong too. The native lcd resolution, 1280x800, isn't listed in the modes. If I can provide any other info, please let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/103945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04
This is found in /var/log/auth.log after failing to authenticate on lock screen then switching account and successfully authenticating with greeter screen. ** Attachment added: "/var/log/auth.log extract" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+attachment/4262687/+files/auth.log -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329048] Re: Shouldn't stop listing events until they are over
Could this be related to https://bugs.launchpad.net/ubuntu/+source /indicator-datetime/+bug/1302004? For example I use a lot of all-day events, and it's unintuitive my events aren't shown in the 5 event list in the indicator *on the day they are active*. Instead the indicator skips the day's events and shows the next 5. If the indicator doesn't show events that have started, and all-day events are considered to have started at 00:00, that'd explain it. I'd still argue it's not useful behavior. -- 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/1329048 Title: Shouldn't stop listing events until they are over Status in “indicator-datetime” package in Ubuntu: New Bug description: Using current utopic, events are dropped from the list when they start, wouldn't it make sense to list as well the ongoing ones (if you are looking to the menu 3 minutes after a meeting started you might still be interested in joining it for example) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1329048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 757551] Re: upowerd leaks memory with Logitech universal receiver
Possibly a related bug: https://www.libreoffice.org/bugzilla/show_bug.cgi?id=82659 ** Bug watch added: LibreOffice Bugzilla #82659 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=82659 ** Bug watch added: freedesktop.org Bugzilla #82659 https://bugs.freedesktop.org/show_bug.cgi?id=82659 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/757551 Title: upowerd leaks memory with Logitech universal receiver Status in “upower” package in Ubuntu: Incomplete Bug description: Binary package hint: upower I currently have 36 days of uptime on my laptop (using suspend a lot) and over time, I've noticed that the upowerd process got to the top of the list in terms of memory usage by claiming 1GB+. I can manage with this situation since I have 6GB of physical memory, but I'm sure that people with less in their laptops will not be so fortunate. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upower 0.9.5-4 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 Architecture: amd64 Date: Mon Apr 11 09:47:23 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/757551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 757551] Re: upowerd leaks memory with Logitech universal receiver
Correct bug link (what does UPower have to do with LO :/) https://bugs.freedesktop.org/show_bug.cgi?id=82659 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/757551 Title: upowerd leaks memory with Logitech universal receiver Status in “upower” package in Ubuntu: Incomplete Bug description: Binary package hint: upower I currently have 36 days of uptime on my laptop (using suspend a lot) and over time, I've noticed that the upowerd process got to the top of the list in terms of memory usage by claiming 1GB+. I can manage with this situation since I have 6GB of physical memory, but I'm sure that people with less in their laptops will not be so fortunate. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upower 0.9.5-4 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 Architecture: amd64 Date: Mon Apr 11 09:47:23 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/757551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity DB
** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Assignee: (unassigned) => Andrea Azzarone (andyrock) ** Changed in: unity Status: Confirmed => In Progress ** Changed in: unity (Ubuntu) Status: Confirmed => In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (andyrock) -- 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/1242112 Title: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity DBus Status in Cairo-Dock : Core: Invalid Status in DockbarX: Invalid Status in Plank: Confirmed Status in Unity: In Progress Status in “cairo-dock” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Status in “cairo-dock” source package in Trusty: Invalid Status in “unity” source package in Trusty: Confirmed Status in “cairo-dock” source package in Utopic: Invalid Status in “unity” source package in Utopic: Confirmed Bug description: Unity's shutdown/restart dialogue is not working when another application is registered to LauncherEntry interface of Unity DBus. It seems we have this bug when Cairo-Dock (and its Launcher-API-Deamon), DockbarX or Plank are launched before Unity. [How to reproduce this bug] Simply launch this script at startup (launched before Unity). It will watch 'com.canonical.Unity.LauncherEntry' bus interface: https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Dbus/data/cairo-dock-launcher-API-daemon.py [Original description] Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in Ubuntu. When cairo dock is set to automatically run at boot up the options to shutdown/restart do not work from the top menu panel next to the clock. When run manually after boot the shutdown/restart works fine. The shutdown/restart options do work fine from cairo dock/terminal but just mess up the shutdown/restart from the top menu panel To manage notifications about this bug go to: https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04
More information here http://askubuntu.com/questions/459720/14-04 -password-not-accepted-after-computer-wakes-up-from-sleep -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393624] [NEW] Lock screen rejects password on Ubuntu 14.04
Public bug reported: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: lock-screen password -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings
This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20141112.1~rtm-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20141112.1~rtm-0ubuntu1) 14.09; urgency=low [ Ken VanDine ] * Backport fix for Switch/Check binding (LP: #1336715) (LP: #1336715) [ Sebastien Bacher ] * Tweaks to try to make the section headers and titles closer to the design. Use a custom component, with tweaked margins and disabled tap effects, for that. -- Ubuntu daily releaseWed, 12 Nov 2014 16:28:25 + ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: In Progress => Fix Released -- 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/1336715 Title: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393618] Re: Bug
when can you repair the bug? -- 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/1393618 Title: Bug Status in “xorg” package in Ubuntu: New Bug description: I have a spam in box of email,and I don't know how I can make to destroy it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 18 01:38:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0649] InstallationDate: Installed on 2014-05-19 (182 days ago) InstallationMedia: It 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 04f2:b337 Chicony Electronics Co., Ltd 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: Packard Bell EasyNote TE11HC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=c41f8877-7f18-4fb7-ac14-8934c002fa97 ro plymouth:debug splash quiet drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Packard Bell dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.13 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnPackardBell:pnEasyNoteTE11HC:pvrV2.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13: dmi.product.name: EasyNote TE11HC dmi.product.version: V2.13 dmi.sys.vendor: Packard Bell 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 18 01:33:30 2014 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.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393618] [NEW] Bug
Public bug reported: I have a spam in box of email,and I don't know how I can make to destroy it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 18 01:38:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0649] InstallationDate: Installed on 2014-05-19 (182 days ago) InstallationMedia: It 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 04f2:b337 Chicony Electronics Co., Ltd 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: Packard Bell EasyNote TE11HC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=c41f8877-7f18-4fb7-ac14-8934c002fa97 ro plymouth:debug splash quiet drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Packard Bell dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.13 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnPackardBell:pnEasyNoteTE11HC:pvrV2.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13: dmi.product.name: EasyNote TE11HC dmi.product.version: V2.13 dmi.sys.vendor: Packard Bell 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 18 01:33:30 2014 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.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1393618 Title: Bug Status in “xorg” package in Ubuntu: New Bug description: I have a spam in box of email,and I don't know how I can make to destroy it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 18 01:38:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0649] InstallationDate: Installed on 2014-05-19 (182 days ago) InstallationMedia: It 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 04f2:b337 Chicony Electronics Co., Ltd 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: Packard Bell EasyNote TE11HC ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8
[Touch-packages] [Bug 1393612] Re: Protect against BadUSB device
@ Seth Arnold: Thanks for your comment. In the case of an USB device acting as a keyboard and for multi-seat machines or remote servers, the keyboard should simply not be activated (what for?). This security measure can also be an option available in "Security & Privacy". I agree that Ubuntu and GNU/Linux is used in many different configuration and the solution proposed here is mostly for desktop use, but it still make sense. -- 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/1393612 Title: Protect against BadUSB device Status in “systemd” package in Ubuntu: Confirmed Bug description: During the last months, it appeared that the theoretical threat of a compromised USB device acting as keyboard became a real possibility: https://srlabs.de/badusb. The solution against such threat is simply to ask the user the confirmation before binding a new USB device as keyboard and a solution was already documented: http://vogelchr.blogspot.in/2014/08 /controlling-usb-device-access-on-linux.html Similar solution already exist for MS Windows: http://robert.penz.name/930/protect-your-pc-against-the-badusb-attack- on-linux-and-windows Even though the probability to get a compromised USB device is low, the security threat is serious and since the solution is simple, Ubuntu should be protected properly asap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 18 02:48:36 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-25 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: LENOVO 4298RD9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=fa0ba264-7e15-48e1-89e6-3c88237a1903 ro persistent quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298RD9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4298RD9:pvrThinkPadX220Tablet:rvnLENOVO:rn4298RD9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298RD9 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1393612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
The attachment "skip failing network tests" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Invalid Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “qtbase-opensource-src” package in Ubuntu RTM: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393612] Re: Protect against BadUSB device
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1393612 Title: Protect against BadUSB device Status in “systemd” package in Ubuntu: Confirmed Bug description: During the last months, it appeared that the theoretical threat of a compromised USB device acting as keyboard became a real possibility: https://srlabs.de/badusb. The solution against such threat is simply to ask the user the confirmation before binding a new USB device as keyboard and a solution was already documented: http://vogelchr.blogspot.in/2014/08 /controlling-usb-device-access-on-linux.html Similar solution already exist for MS Windows: http://robert.penz.name/930/protect-your-pc-against-the-badusb-attack- on-linux-and-windows Even though the probability to get a compromised USB device is low, the security threat is serious and since the solution is simple, Ubuntu should be protected properly asap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 18 02:48:36 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-25 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: LENOVO 4298RD9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=fa0ba264-7e15-48e1-89e6-3c88237a1903 ro persistent quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298RD9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4298RD9:pvrThinkPadX220Tablet:rvnLENOVO:rn4298RD9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298RD9 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1393612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393612] Re: Protect against BadUSB device
Sadly, the solution is not easy nor obvious. Ubuntu is used in a wide variety of different ways and many of them do not lend themselves well to just popping up a dialog box. Furthermore, the problem is not at all restricted to just devices that can be reprogrammed to act like keyboards. A fairly lengthy discussion can be found here: http://www.openwall.com/lists/oss-security/2014/08/09/4 Thanks -- 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/1393612 Title: Protect against BadUSB device Status in “systemd” package in Ubuntu: Confirmed Bug description: During the last months, it appeared that the theoretical threat of a compromised USB device acting as keyboard became a real possibility: https://srlabs.de/badusb. The solution against such threat is simply to ask the user the confirmation before binding a new USB device as keyboard and a solution was already documented: http://vogelchr.blogspot.in/2014/08 /controlling-usb-device-access-on-linux.html Similar solution already exist for MS Windows: http://robert.penz.name/930/protect-your-pc-against-the-badusb-attack- on-linux-and-windows Even though the probability to get a compromised USB device is low, the security threat is serious and since the solution is simple, Ubuntu should be protected properly asap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 18 02:48:36 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-25 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: LENOVO 4298RD9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=fa0ba264-7e15-48e1-89e6-3c88237a1903 ro persistent quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298RD9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4298RD9:pvrThinkPadX220Tablet:rvnLENOVO:rn4298RD9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298RD9 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1393612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393612] Re: Protect against BadUSB device
** Information type changed from Private Security to Public Security -- 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/1393612 Title: Protect against BadUSB device Status in “systemd” package in Ubuntu: New Bug description: During the last months, it appeared that the theoretical threat of a compromised USB device acting as keyboard became a real possibility: https://srlabs.de/badusb. The solution against such threat is simply to ask the user the confirmation before binding a new USB device as keyboard and a solution was already documented: http://vogelchr.blogspot.in/2014/08 /controlling-usb-device-access-on-linux.html Similar solution already exist for MS Windows: http://robert.penz.name/930/protect-your-pc-against-the-badusb-attack- on-linux-and-windows Even though the probability to get a compromised USB device is low, the security threat is serious and since the solution is simple, Ubuntu should be protected properly asap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 18 02:48:36 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-25 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: LENOVO 4298RD9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=fa0ba264-7e15-48e1-89e6-3c88237a1903 ro persistent quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298RD9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4298RD9:pvrThinkPadX220Tablet:rvnLENOVO:rn4298RD9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298RD9 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1393612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
Here's a patch to skip some of the tests that are failing due to no valid configurations on the test machines. ** Patch added: "skip failing network tests" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1357321/+attachment/4262629/+files/0001-skip-QtBearer-autotests-when-no-valid-configurations.patch -- 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/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Invalid Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “qtbase-opensource-src” package in Ubuntu RTM: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 757551] Re: upowerd leaks memory with Logitech universal receiver
UPower 0.99.1 had one minor fix which fixed a memleak: dbb9bead6d3b9e70a5d58019b1615d2a6fba5312 Another leak fix: b1aeed994884602b3601a7f4b98419c65be9009c I am working to flesh out more memory leaks here: https://git.lekensteyn.nl/upower/log/?h=memleak-fixes The GetStatistics calls are probably the ones which result in the largest memory leaks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/757551 Title: upowerd leaks memory with Logitech universal receiver Status in “upower” package in Ubuntu: Incomplete Bug description: Binary package hint: upower I currently have 36 days of uptime on my laptop (using suspend a lot) and over time, I've noticed that the upowerd process got to the top of the list in terms of memory usage by claiming 1GB+. I can manage with this situation since I have 6GB of physical memory, but I'm sure that people with less in their laptops will not be so fortunate. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upower 0.9.5-4 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 Architecture: amd64 Date: Mon Apr 11 09:47:23 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/757551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354841] Re: Screen corruption (characters are drawn as black squares)
M, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1354841 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1354841 Title: Screen corruption (characters are drawn as black squares) Status in “xorg” package in Ubuntu: Incomplete Bug description: Sometimes, the characters are rendered as black squares (cf attachment). I couldn't find any event in the systems logs that could explain that. I can "stop" the bug by changing the anti-aliasing options in the system settings (enabled / disabled, level of hinting) and restarting the applications, but the squares can come back later on, and I have to repeat the operation. The bug almost exclusively happens with firefox and thunderbird, though krunner is also affected (but not other kde apps). I'm not using many GTK applications, but I can also see the bug with unison. It used to happen in 13.10 as well, and upgrading to 14.04.1 hasn't improved the situation ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 14:03:25 2014 InstallationDate: Installed on 2011-01-10 (1307 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-08-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data
** No longer affects: click-reviewers-tools (Ubuntu Utopic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “click-reviewers-tools” package in Ubuntu:
In Progress
Status in “unity-scopes-api” package in Ubuntu:
Fix Committed
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
In Progress
Status in “unity-scopes-api” source package in Utopic:
New
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
In Progress
Status in “click-reviewers-tools” source package in Vivid:
In Progress
Status in “unity-scopes-api” source package in Vivid:
Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
Fix Committed
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354088] Re: screen flickering ubuntu 14.04
nouha, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1354088 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1354088 Title: screen flickering ubuntu 14.04 Status in “xorg” package in Ubuntu: Incomplete Bug description: I have sony VAIO, serie E VPCEH16EF, nvidia Geforce with cuda,i3 I have upgraded my ubuntu from 13.10 =>14.04.1 LTS I faced many problems,with unity and GPU black screen then just login screen then i've tried to fix it... it works now good.. but still one thing: my screen flickering thought it was from my nvidia card, here's the output of nvidia-settings -q NvidiaDriverVersion : Attribute 'NvidiaDriverVersion' (nouha-VPCEH16EF:0.0): 340.24 Attribute 'NvidiaDriverVersion' (nouha-VPCEH16EF:0[gpu:0]): 340.24 and by the way https://drive.google.com/file/d/0B55mJS- yKk03SThUd2l3RkVfQkE/edit?usp=sharing I don't know what to do help pzzz :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354841] [NEW] Screen corruption (characters are drawn as black squares)
You have been subscribed to a public bug: Sometimes, the characters are rendered as black squares (cf attachment). I couldn't find any event in the systems logs that could explain that. I can "stop" the bug by changing the anti-aliasing options in the system settings (enabled / disabled, level of hinting) and restarting the applications, but the squares can come back later on, and I have to repeat the operation. The bug almost exclusively happens with firefox and thunderbird, though krunner is also affected (but not other kde apps). I'm not using many GTK applications, but I can also see the bug with unison. It used to happen in 13.10 as well, and upgrading to 14.04.1 hasn't improved the situation ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 14:03:25 2014 InstallationDate: Installed on 2011-01-10 (1307 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-08-06 (3 days ago) ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug kubuntu resolution trusty -- Screen corruption (characters are drawn as black squares) https://bugs.launchpad.net/bugs/1354841 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1320752] Re: MAC Spoofing / Cloning for WiFi is broken in Trusty 14.04 / 14.10 and all others including Mint 17
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpasupplicant (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1320752 Title: MAC Spoofing / Cloning for WiFi is broken in Trusty 14.04 / 14.10 and all others including Mint 17 Status in “network-manager” package in Ubuntu: Confirmed Status in “wpasupplicant” package in Ubuntu: Confirmed Bug description: **SHORT OVERVIEW** "Cloned MAC Address" feature doesn't work with any USB WiFi adapters in 14.04, 14.10, Mint 17 and likely all others based on Ubuntu. It worked under 13.10 and was broken from day one in 14.04+. This is not an upgrade issue, i did a clean install to test. Atheros, Realtek, Ralink adapters tested, this has nothing to do with the driver type. The only symptoms are WiFi not connecting and the following dmesg output: [ 214.296350] wlan0: authenticate with 98:fc:11:f2:f7:43 [ 214.305098] wlan0: send auth to 98:fc:11:f2:f7:43 (try 1/3) [ 214.307421] wlan0: authenticated [ 219.367559] wlan0: deauthenticating from 98:fc:11:f2:f7:43 by local choice (reason=3) **TEMP SOLUTION*** This bug is caused by wpasupplicant (2.1-0ubuntu1.1) in Trusty, network-manager is not the culprit. I quick fix is to downgrade wpasupplicant to the Saucy version, wpasupplicant (1.0-3ubuntu2). This is relatively easy and doesn't seem to affect anything else. Original bug report info: after setting the mac to change in networkmanager i try to connect yet it never will, when looking at the logs it says it got disconnected by local choice (reason 3), it appeared it was because the mac wasnt effectively changed but then again i tried to do so disabling network-manager -> macchanger -m -> enabling network-manager, i checked with ifconfig if the mac has changed and it did however the result was the same maybe its because of this http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-4579.html? **UPDATE** now works doing the macchanger procedure, directly from network- manager it doesnt ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Mon May 19 02:00:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-06 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-06 (13 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=b249fe00-d117-42dc-a2a4-e2b8763b5b7c ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3568 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.3A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn3568:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 06901320461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1320752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packa
[Touch-packages] [Bug 1354088] [NEW] screen flickering ubuntu 14.04
You have been subscribed to a public bug: I have sony VAIO, serie E VPCEH16EF, nvidia Geforce with cuda,i3 I have upgraded my ubuntu from 13.10 =>14.04.1 LTS I faced many problems,with unity and GPU black screen then just login screen then i've tried to fix it... it works now good.. but still one thing: my screen flickering thought it was from my nvidia card, here's the output of nvidia-settings -q NvidiaDriverVersion : Attribute 'NvidiaDriverVersion' (nouha-VPCEH16EF:0.0): 340.24 Attribute 'NvidiaDriverVersion' (nouha-VPCEH16EF:0[gpu:0]): 340.24 and by the way https://drive.google.com/file/d/0B55mJS- yKk03SThUd2l3RkVfQkE/edit?usp=sharing I don't know what to do help pzzz :( ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: bot-comment -- screen flickering ubuntu 14.04 https://bugs.launchpad.net/bugs/1354088 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384286] Re: add directory allowing scopes and apps to share data
This is in rtm silo 002.
** Changed in: apparmor-easyprof-ubuntu (Ubuntu Utopic)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “click-reviewers-tools” package in Ubuntu:
In Progress
Status in “unity-scopes-api” package in Ubuntu:
Fix Committed
Status in “apparmor-easyprof-ubuntu” source package in Utopic:
In Progress
Status in “click-reviewers-tools” source package in Utopic:
New
Status in “unity-scopes-api” source package in Utopic:
New
Status in “apparmor-easyprof-ubuntu” source package in Vivid:
In Progress
Status in “click-reviewers-tools” source package in Vivid:
In Progress
Status in “unity-scopes-api” source package in Vivid:
Fix Committed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
Fix Committed
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/r,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
@failling unit tests - per lorn on irc, tests are written in that they assume the generic plugin is loaded & those are never going to pass since they need a valid configuration based on the generic plugin FAIL! : tst_QNetworkConfiguration::comparison() 'configs.count()' returned FALSE. () but our patch set explicitly blocks the generic plugin if the networkmanager plugin is found so it may be safe to selectively disable tests depending on a valid config. -- 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/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Invalid Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: In Progress Status in “qtbase-opensource-src” package in Ubuntu RTM: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Re: ubuntu 12.04.5 broken on VMware
This bug was fixed in the package mesa-lts-trusty - 10.1.3-0ubuntu0.2~precise1 --- mesa-lts-trusty (10.1.3-0ubuntu0.2~precise1) precise-proposed; urgency=low * Copy package back to precise. mesa (10.1.3-0ubuntu0.2) trusty; urgency=medium [ Timo Aaltonen ] * Drop fix-kwin.diff hack, as 10.1.3 has 0380ec467d78f40 which fixes the issue properly. [ Maarten Lankhorst ] * Add fix-svga-ioctl.patch (LP: #1365490) -- Maarten LankhorstWed, 01 Oct 2014 15:14:26 +0200 ** Changed in: mesa-lts-trusty (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Fix Released Status in “mesa” source package in Trusty: Fix Released Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using "easy install". Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, "winsys/svga: Fix incorrect type usage in IOCTL v2", with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365490] Update Released
The verification of the Stable Release Update for mesa-lts-trusty has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1365490 Title: ubuntu 12.04.5 broken on VMware Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-trusty” package in Ubuntu: Invalid Status in “mesa-lts-trusty” source package in Precise: Fix Released Status in “mesa” source package in Trusty: Fix Released Bug description: [Impact] A user might find Ubuntu 12.04.5 unusable on vmware because he would face a black screen after logging in. Although there is a workaround (disabling 3D) a user may have given up at that point. Backporting will help the user run the distro after upgrading, so I believe it's highly justified. [Test Case] On VMware Workstation 10, Install Ubuntu 12.04.5, preferrably using "easy install". Boot the VM, log in. You'll see a black screen only. [Regression Potential] The bug affects a function that impots a shared buffer to the 3D driver. The function is completely broken by the bug. Even if the patch should introduce another type of breakage, the problem couldn't be much worse than it already is, and should be confined to the specific function in question. [Other info] Due to different stack ordering of automatic variables, the bug may or may not be visible depending on the C compiler and the level of optimization used. For example, if -O0 -g is used the bug is not visible on 12.04.5. I have not encountered any symptoms of the bug yet on 14.04. [ Original bug report ] Ubuntu 12.04.5 shows a black screen after login with 3D enabled on VMware. This is due to a bug in the svga gallium driver's winsys. It's recently fixed in mesa master commit 2d6206140a, "winsys/svga: Fix incorrect type usage in IOCTL v2", with a request to backport to mesa stable, but I'm not sure whether anyone's still maintaining the 10.1 branch. Due to the severity of the symptoms it would be greatly appreciated if this fix could be incorporated in the libgl1-mesa-dri-lts-trusty package as soon as possible. Unfortunately it's affecting the package on the installation iso. Is there anything that can be done about that? Thanks, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1365490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391149] Re: greeter not reacting to swipes
got it, i was conflating the unity frozen ui bug 1391076 & the double tap bug 1388359 as solving this. -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: Triaged Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393603] [NEW] No acceptable non compositing desktop anymore
Public bug reported: Since 12.04 (I guess) there is no usable full fledged desktop without compositing anymore. Despite providing several benefits, compositing desktops introduce some small lag to almost any display operation, that some people (including me) find annoying. This is an effect currently experienced on any compositing system (including Windows and Mac OS), which gives a kind of slight honey feel to every mouse or keyboard input. However, with gnome-fallback gone (or replaced by classic mode building on top of gnome-shell) there is no full featured gnome like environment without compositing anymore. lxde and xfce can be used of course, but the are not in the best shape for Ubuntu, for example showing several small caveats at desktop configuration, eg. multi monitor setups and such. Ubuntu should provide a featured and lag free experience for those who do power work with. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1393603 Title: No acceptable non compositing desktop anymore Status in “ubuntu-meta” package in Ubuntu: New Bug description: Since 12.04 (I guess) there is no usable full fledged desktop without compositing anymore. Despite providing several benefits, compositing desktops introduce some small lag to almost any display operation, that some people (including me) find annoying. This is an effect currently experienced on any compositing system (including Windows and Mac OS), which gives a kind of slight honey feel to every mouse or keyboard input. However, with gnome-fallback gone (or replaced by classic mode building on top of gnome-shell) there is no full featured gnome like environment without compositing anymore. lxde and xfce can be used of course, but the are not in the best shape for Ubuntu, for example showing several small caveats at desktop configuration, eg. multi monitor setups and such. Ubuntu should provide a featured and lag free experience for those who do power work with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1393603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1273261] Re: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1273261 Title: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file Status in “cryptsetup” package in Ubuntu: Confirmed Status in “initramfs-tools” package in Ubuntu: Confirmed Bug description: While booting cryptsetup outputs following error: /scripts/local- top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file, seems to be not related to this particular installation as saw the same output on other machines, also seems to be nothing major as everything boots fine, so just reporting to let you know it's there. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cryptsetup 2:1.4.3-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 27 15:58:16 2014 InstallationDate: Installed on 2014-01-18 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) crypttab: sda3_crypt UUID=68851a49-83a4-41eb-84c0-27d15280bbc1 none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341539] Re: Dell XPS L502x Ubuntu 14.04 freeze sometimes
Jcostas-madrid, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect 1341539 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1341539 Title: Dell XPS L502x Ubuntu 14.04 freeze sometimes Status in “xorg” package in Ubuntu: Incomplete Bug description: When I'm using Ubuntu 14.4 the system sometimes freeze, I can unfreeze entering into console mode and then going out from this mode. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 14 13:24:44 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-08 (66 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1341539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393596] [NEW] Extreme slow syntax highlighting for Windows Registry Files
Public bug reported: If exported Windows Registry Information is opened in vim, an very simple, but apropriate syntax highlighting is enabled. However, on any longer block of ASCII hex representation (and usual Registry data has a lot of that trash) the text rendering gets extremely slow, hugging CPU and make scrolling almost impossible. The simple scheme of marking keys and there values should not need such complex parsing. ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1393596 Title: Extreme slow syntax highlighting for Windows Registry Files Status in “vim” package in Ubuntu: New Bug description: If exported Windows Registry Information is opened in vim, an very simple, but apropriate syntax highlighting is enabled. However, on any longer block of ASCII hex representation (and usual Registry data has a lot of that trash) the text rendering gets extremely slow, hugging CPU and make scrolling almost impossible. The simple scheme of marking keys and there values should not need such complex parsing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1393596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340739] Re: Video tearing when rotated second screen is set
manfromthezoo, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect 1340739 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: ubuntu => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340739 Title: Video tearing when rotated second screen is set Status in “xorg” package in Ubuntu: Incomplete Bug description: I have a dual monitor setup - one regular, one rotated. All seems to be well on the regularly oriented monitor, however on the rotated one, there is significant video tearing when dragging windows - which is worse when done vertically. I have tried with 14.04, and I am using Haswell HD4600. Unfortunately the problem renders me unable to use Ubuntu, as smooth scrolling is important for my work. Any pointers very much appreciated. Another instance from someone else: http://askubuntu.com/questions/474499/screen-tearing-on-rotated- screen-in-14-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390624] Re: Black line on top of the scope headers with image vivid/mako 12
Fixed here - https://code.launchpad.net/~mzanetti/unity8/new-pageheader- api/+merge/239242 -- 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/1390624 Title: Black line on top of the scope headers with image vivid/mako 12 Status in “unity8” package in Ubuntu: Fix Released Bug description: current build number: 12 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-11-07 21:01:06 version version: 12 version ubuntu: 20141107 version device: 20141106 version custom: 20141107 See: http://people.canonical.com/~rsalveti/home.png Opening against the toolkit as this bug was introduced on image 12, which got only the following changes: http://people.canonical.com/~ogra/touch-image-stats/12.changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1390624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341539] [NEW] Dell XPS L502x Ubuntu 14.04 freeze sometimes
You have been subscribed to a public bug: When I'm using Ubuntu 14.4 the system sometimes freeze, I can unfreeze entering into console mode and then going out from this mode. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 14 13:24:44 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-05-08 (66 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug trusty -- Dell XPS L502x Ubuntu 14.04 freeze sometimes https://bugs.launchpad.net/bugs/1341539 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340739] [NEW] Video tearing when rotated second screen is set
You have been subscribed to a public bug: I have a dual monitor setup - one regular, one rotated. All seems to be well on the regularly oriented monitor, however on the rotated one, there is significant video tearing when dragging windows - which is worse when done vertically. I have tried with 14.04, and I am using Haswell HD4600. Unfortunately the problem renders me unable to use Ubuntu, as smooth scrolling is important for my work. Any pointers very much appreciated. Another instance from someone else: http://askubuntu.com/questions/474499/screen-tearing-on-rotated-screen- in-14-04 ** Affects: xorg (Ubuntu) Importance: Low Status: Incomplete ** Tags: bot-comment -- Video tearing when rotated second screen is set https://bugs.launchpad.net/bugs/1340739 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location
On Nov 17, 2014, at 10:36 PM, Manuel de la Peña wrote:
>Any updates on when we can land this? Can I propose it for vivid?
Are there any blocks on vivid landings?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1341685
Title:
When unconstrained, udm sometimes downloads files to wrong location
Status in Ubuntu Download Manager:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
In Progress
Bug description:
I'm working on making the s-i tests more robust and I've run into an
odd situation, where udm sometimes stores its downloaded files using
an incorrect path, and not the one that s-i (which is unconstrained)
requests. This only appears to happen when the full s-i test suite is
run. When run in isolation, the test succeeds.
Here's a log of the createDownloadGroup call I'm making:
createDownloadGroup:
[Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
checksum=''),
Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
checksum='')]
url is the source url, destination is the local path to save the file
in. This call produces incorrect destination paths in the 'finished'
signal:
FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
download-manager//usr/lib/telepathy/mission-
control-5/Downloads/blacklist (20).tar.xz'),
dbus.String('/home/barry/.local/share/ubuntu-download-
manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
(20).tar.xz.asc')], signature=dbus.Signature('s'))
Notice the very strange directory udm chooses which is definitely not
the path requested, and in fact doesn't exist. This matches the
observed behavior that after a succesful group download completion
(i.e. no errors occur), I assert that the requested destination path
exists, and in the failing test it does not.
I suspect some state is not getting reset in udm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-download-manager/+bug/1341685/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
I have the same problem with two different notebooks with intel graphics after upgrade to 14.10. (Acer - Intel Core i3 380M - HD Graphics, Asus - Intel Core i3 3217U - HD Graphics 4000). I use Ubuntu with Unity. -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
I have the same problem with two different notebooks with intel graphics after upgrade to 14.10. (Acer - Intel Core i3 380M - HD Graphics, Asus - Intel Core i3 3217U - HD Graphics 4000). I use Ubuntu with Unity. -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location
Any updates on when we can land this? Can I propose it for vivid?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1341685
Title:
When unconstrained, udm sometimes downloads files to wrong location
Status in Ubuntu Download Manager:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
In Progress
Bug description:
I'm working on making the s-i tests more robust and I've run into an
odd situation, where udm sometimes stores its downloaded files using
an incorrect path, and not the one that s-i (which is unconstrained)
requests. This only appears to happen when the full s-i test suite is
run. When run in isolation, the test succeeds.
Here's a log of the createDownloadGroup call I'm making:
createDownloadGroup:
[Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
checksum=''),
Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
checksum='')]
url is the source url, destination is the local path to save the file
in. This call produces incorrect destination paths in the 'finished'
signal:
FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
download-manager//usr/lib/telepathy/mission-
control-5/Downloads/blacklist (20).tar.xz'),
dbus.String('/home/barry/.local/share/ubuntu-download-
manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
(20).tar.xz.asc')], signature=dbus.Signature('s'))
Notice the very strange directory udm chooses which is definitely not
the path requested, and in fact doesn't exist. This matches the
observed behavior that after a succesful group download completion
(i.e. no errors occur), I assert that the requested destination path
exists, and in the failing test it does not.
I suspect some state is not getting reset in udm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-download-manager/+bug/1341685/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378898] Re: Keyboard visible over the welcome screen
A quick work around would be removing the forceActiveFocus call from the terminal AuthenticationDialog app. Still looking into something better. -- 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/1378898 Title: Keyboard visible over the welcome screen Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Triaged Bug description: Steps: * start terminal app * lock the phone immediately Expected: * keyboard not visible over the welcome screen (should it ever show? shouldn't the window be unfocused, and so not be able to have a keyboard at all?) Current * keyboard shows up on top of the welcome screen ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20141006-0ubuntu1 [modified: usr/share/unity8/Shell.qml] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Wed Oct 8 17:41:02 2014 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141008-090632) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391149] Re: greeter not reacting to swipes
Nope, not a dupe. See the description, the phone works rather fine, but the welcome screen stops receiving events. So you can't double-tap to change the infographics, or swipe the greeter away, other than from the left edge, etc. ** This bug is no longer a duplicate of bug 1377332 [TOPBLOCKER] UI randomly freezes ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => High -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: Triaged Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381014] Re: [Indicators] Notifications menu: gesture control when updating the system
The resolution of this bug is conflicting with the expand/contract behaviour which is baked into the notification items. Could you please comment on what should happen with that? ** Changed in: ubuntu-ux Status: Fix Committed => New ** Changed in: unity8 (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1381014 Title: [Indicators] Notifications menu: gesture control when updating the system Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: 14.10 (r279) Steps to reproduce: Tap on the status bar Pull the Notifications menu Tap on the ‘system update message’ Actual behaviour: Message is selected (colour changes to grey) and small SS icon, on the right hand side, swings. User needs to tap on the small icon in order to update the system. Expected behaviour: The whole message’s real state should be tappable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1381014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1277311] Re: can't open URL in text viewed in the message indicator
I'm actually not sure there's anything to do in unity8 here, ubuntu- settings-components is probably the only culprit here. Please talk to the messaging app folk to find out how they're doing it, and ideally use the same code or at least approach. -- 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/1277311 Title: can't open URL in text viewed in the message indicator Status in “ubuntu-settings-components” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed Bug description: I received a text with a URL in it. In the messaging app, it is blue and I am able to tap it to open the browser, but in viewing the same message in the message indicator I am not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1277311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
Just migrated /opt/click.ubuntu.com under '/' (not bind-mounted) and was able to run the same test case for more than 2 hours without any issue. It fails again at the moment I move it back under /data (bind-mounted at /opt/click.ubuntu.com), on the first run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Fix Released Status in “android-tools” package in Ubuntu: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Fix Released Status in “android” package in Ubuntu RTM: In Progress Status in “android-tools” package in Ubuntu RTM: In Progress Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM: In Progress Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: "I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh" The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326513] Re: Applications are orphaned when unity8 crashes
** Changed in: qtmir Assignee: (unassigned) => Josh Arenson (josharenson) ** Changed in: unity8 (Ubuntu) Status: Triaged => Invalid -- 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/1326513 Title: Applications are orphaned when unity8 crashes Status in Mir: Expired Status in Qt integration with the Mir display server: Triaged Status in “ubuntu-app-launch” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: For some reason Unity8 crashed on me. The applications I had open are now orphaned. They're still running but you can't get to it as it no longer shows up under the recent applications. In addition if I attempt to start the app, it fails to run or come back from orphaned state, so I have to restart. My unity process where Unity8 died an hour or two back. lightdm 1871 0.0 0.0 1392 464 ?Ss 10:06 0:00 /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 1875 0.0 0.0 1392 472 ?S10:06 0:00 /bin/sh /usr/bin/unity8-greeter-wrapper /usr/bin/unity8-greeter lightdm 2362 0.2 5.0 343724 95000 ?Sl 10:06 1:47 /usr/bin/unity8-greeter phablet 22852 0.4 5.6 452692 105852 ? Ssl 19:03 0:34 unity8 The application:- phablet 8503 10.3 8.6 297792 161652 ? Ssl 11:33 59:33 /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene ubuntu-calculator- app.qml Now when I start calculator it just white-screens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.87+14.10.20140603.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Wed Jun 4 21:04:34 2014 InstallationDate: Installed on 2014-06-04 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140604) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1326513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391149] Re: greeter not reacting to swipes
*** This bug is a duplicate of bug 1377332 *** https://bugs.launchpad.net/bugs/1377332 going ahead and marking as dup of bug 1391076 ** This bug has been marked a duplicate of bug 1377332 [TOPBLOCKER] UI randomly freezes -- 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/1391149 Title: greeter not reacting to swipes Status in “unity8” package in Ubuntu: New Bug description: i had this a few times over the weekend with images 150-153, suddenly the greeter does not react to right/left swipes on the wallpaper to reveal the PIN unlock dialog ... swiping in the launcher from the left makes the greeter go away and reveals the PIN unlock dialog then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1391149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
** Summary changed: - [themes] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image + [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image -- 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/1391560 Title: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Incomplete Bug description: As discussed with Olga, we need to develop a strategy on keeping the fonts readable when we allow the user to change the background. This is currently the case on the Greeter and the Lockscreens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381014] Re: [Indicators] Notifications menu: gesture control when updating the system
** Changed in: ubuntu-ux Status: New => Fix Committed -- 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/1381014 Title: [Indicators] Notifications menu: gesture control when updating the system Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Confirmed Bug description: 14.10 (r279) Steps to reproduce: Tap on the status bar Pull the Notifications menu Tap on the ‘system update message’ Actual behaviour: Message is selected (colour changes to grey) and small SS icon, on the right hand side, swings. User needs to tap on the small icon in order to update the system. Expected behaviour: The whole message’s real state should be tappable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1381014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389195] Re: "Fitbit" section in Dashboard goes to a near-empty screen when tapped
i'm guessing this is specific to cwayne's fitbit scope? maybe there's no project? ** Changed in: unity8 (Ubuntu) Status: New => Opinion -- 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/1389195 Title: "Fitbit" section in Dashboard goes to a near-empty screen when tapped Status in “unity8” package in Ubuntu: Opinion Bug description: Ubuntu 14.10 RTM r6 Ubuntu 14.10 RTM-proposed r214 0. Remove your Fitbit account from the phone if you have one. 1. Go to the "Dashboard" screen and scroll to "Fitbit". 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a "Dashboard" screen that contains only vague text about setting up an account (same as bug 1389192). What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should contain more obvious explanation of the benefit and method of adding an account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392412] Re: may constantly try to upload reports when server responds with 400
Evan points out that it should only try to upload the crash report every
2 hours so it is not *that* bad.
** Description changed:
parse_and_upload_report will return success = True on a 400 response
- from the server, however if for some reason the report is not mark as
+ from the server, however if for some reason the report is not marked as
handled (mark_handled) then because there is no .uploaded file whoopsie
will continuely try to upload the .crash file.
from src/whoopsie.c:
- } else if (online_state && parse_and_upload_report (crash_file)) {
- if (!mark_handled (crash_file))
- log_msg ("Unable to mark report as seen (%s)\n", crash_file);
+ } else if (online_state && parse_and_upload_report (crash_file)) {
+ if (!mark_handled (crash_file))
+ log_msg ("Unable to mark report as seen (%s)\n", crash_file);
- }
+ }
Given that every crash report is not precious, we should just remove the
crash_file if mark_handled fails.
** Changed in: whoopsie (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1392412
Title:
may constantly try to upload reports when server responds with 400
Status in “whoopsie” package in Ubuntu:
New
Bug description:
parse_and_upload_report will return success = True on a 400 response
from the server, however if for some reason the report is not marked
as handled (mark_handled) then because there is no .uploaded file
whoopsie will continuely try to upload the .crash file.
from src/whoopsie.c:
} else if (online_state && parse_and_upload_report (crash_file)) {
if (!mark_handled (crash_file))
log_msg ("Unable to mark report as seen (%s)\n", crash_file);
}
Given that every crash report is not precious, we should just remove
the crash_file if mark_handled fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1392412/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1277311] Re: can't open URL in text viewed in the message indicator
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Ying-Chun Liu (paulliu) ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Status: New => Confirmed ** Changed in: unity8 (Ubuntu RTM) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1277311 Title: can't open URL in text viewed in the message indicator Status in “ubuntu-settings-components” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu RTM: Confirmed Bug description: I received a text with a URL in it. In the messaging app, it is blue and I am able to tap it to open the browser, but in viewing the same message in the message indicator I am not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1277311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
