[Touch-packages] [Bug 1432123] Re: mountall service unavailable on systemd, preventing full zfs integration
*** This bug is a duplicate of bug 1431523 *** https://bugs.launchpad.net/bugs/1431523 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/1432123 Title: mountall service unavailable on systemd, preventing full zfs integration Status in systemd package in Ubuntu: Confirmed Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447839] Re: Support dynamic mouse cursor icons
** Summary changed: - mouse edge of window drag handles + Support dynamic mouse cursor icons -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1447839 Title: Support dynamic mouse cursor icons Status in Mir: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: currently on the unity8 desktop windowed mode, the mouse remains in it's arrow form not prompting the user when it's on the edge of a window where the window can be rescaled. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1447839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432122] Re: mountall service unavailable on systemd, preventing full zfs integration
*** This bug is a duplicate of bug 1431523 *** https://bugs.launchpad.net/bugs/1431523 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/1432122 Title: mountall service unavailable on systemd, preventing full zfs integration Status in systemd package in Ubuntu: Confirmed Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service - /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 mountall bug report: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441798] Re: -- NO more avaible -- 3G network doesn't work
** Project changed: indicator-network = indicator-network (Ubuntu) ** Changed in: indicator-network (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1441798 Title: -- NO more avaible -- 3G network doesn't work Status in indicator-network package in Ubuntu: Invalid Bug description: The 3G network and MMS doesn't work. Indeed, when I try to configure my APN network it seems like some fields are missing. When I fill all field matching with my APN config and I try to connect to internet it doesn't work. For more information, this is my APN configuration : http://community.48months.ie/t5/Need-Help/Internet-Settings/td-p/78 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1441798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447056] Re: Favourite scopes forcefully refreshed when opened from Manage Dash
I have a branch for this which linked above,and it works fine. But i'm not sure whether it is the most suitable way, maybe there is a better way for this? Modify the activate method in unity-scope-shell ? hope to hear your opinion. ** Branch linked: lp:~feng- kylin/unity8/openPrepopulatedScopeInManageDash -- 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/1447056 Title: Favourite scopes forcefully refreshed when opened from Manage Dash Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Steps: * swipe left/right through all favourite scopes to trigger a refresh where needed * bottom-swipe to Manage Dash * select one of the favourite scopes Expected: * the scope is opened pre-populated Current: * the scope is refreshed on open ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150409.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:46:36 2015 SourcePackage: unity8 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1447056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
It seems I've found a workaround for the original unity8 hang on boot, which we can include in lxc-android-config without touching Qt while the upstream fixing of QDBus is not 100% complete. ** Also affects: lxc-android-config (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-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447282] Re: Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs)
Thanks Jason! ** Also affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Vivid) Importance: Undecided = High ** Changed in: systemd (Ubuntu Vivid) Status: New = In Progress ** Changed in: systemd (Ubuntu Vivid) Assignee: (unassigned) = Martin Pitt (pitti) ** Summary changed: - Prompted for cryptoswap passphrase when using GPT partitioning + encrypted home directory (ecryptfs) + Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) -- 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/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447601] Re: Phone app settings are oddly in System Settings
** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided = Low ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Won't Fix ** Changed in: ubuntu-system-settings (Ubuntu) Status: Won't Fix = 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/1447601 Title: Phone app settings are oddly in System Settings Status in dialer-app package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: In System Settings, most of the Phone settings are about things that happen inside, or (in the case of ringtone) when you are about to use, the Phone app. Therefore it is weird for those settings to be accessed from System Settings. Probably they should be moved to the Phone app. Implementation of this move should be coordinated with that of (private) bug 1388012. [Realized during discussion of bug 1306078.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1447601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know that, but as I donut have a better link to it, and it belongs to design, I guess its not my fault ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448068] [NEW] Keyboard layout not set correctly in Ubuntu 15.04 network installer
Public bug reported: I'm using the network installer CD image in order to install Ubuntu 15.04. At the Keyboard layout step I select French and legacy, alternate or alternate but every times I get Qwerty layout for the next Ubuntu's installation steps. I thing there is a bug somewhere. The situation is simple to reproduce. Use an Azerty keyboard ; Choose the network installer cd image ; Choose French language, French keyboard layout and finally legacy, alternate or alternate ; Thats it. After these steps you'll get Querty layout instead of Azerty ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1448068 Title: Keyboard layout not set correctly in Ubuntu 15.04 network installer Status in console-setup package in Ubuntu: New Bug description: I'm using the network installer CD image in order to install Ubuntu 15.04. At the Keyboard layout step I select French and legacy, alternate or alternate but every times I get Qwerty layout for the next Ubuntu's installation steps. I thing there is a bug somewhere. The situation is simple to reproduce. Use an Azerty keyboard ; Choose the network installer cd image ; Choose French language, French keyboard layout and finally legacy, alternate or alternate ; Thats it. After these steps you'll get Querty layout instead of Azerty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1448068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448070] [NEW] shutdown -h/-r now wall message message does not send wall
Public bug reported: Hi, As far as I know, shutdown command (and other reboot/poweroff/halt commands) are now just alias for systemctl which inits the right target, so I am reporting this bug to systemd package. I noted a strange thing : shutdown -h now wall message do not send the wall message, but shutdown -h +any_value does. I conduct this test in TTY also, it seems that when the timer is now (or +0), the wall is sent after shuting down services like OpenSSH, so users logged in cannot see it. When the time value is +1 or more, the wall is properly displayed. Step to reproduce : Ubuntu Version : 15.04 from a fresh Released install (seems to not be the case in 14.10 where systemd is not completely used, as all shutdown/halt/poweroff/reboot commands are symlink to reboot and not systemctl). - sudo shutdown -r now This is a maintenance reboot as we discuss earlier, server will be back in few seconds. - No one of my logged user saw this notice - sudo shutdown -r +3 This is an unscheduled URGENT maintenance. Please save your work and prepare to immediate reboot in 3 minutes - It's working. Regards, ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, As far as I know, shutdown command (and other reboot/poweroff/halt commands) are now just alias for systemctl which inits the right target, so I am reporting this bug to systemd package. I noted a strange think : shutdown -h now wall message do not send the wall message, but shutdown -h +any_value does. I conduct this test in TTY also, it seems that when the timer is now (or +0), the wall is sent after shuting down services like OpenSSH, so users logged in cannot see it. When the time value is +1 or more, the wall is properly displayed. Step to reproduce : + Ubuntu's Version : 15.04 (seems to not be the case in 14.10 where + systemd is not completely used, as all shutdown/halt/poweroff/reboot + commands are symlink to reboot and not systemctl). + - sudo shutdown -r now This is a maintenance reboot as we discuss earlier, server will be back in few seconds. - No one of my logged user saw this notice - sudo shutdown -r +3 This is an unscheduled URGENT maintenance. Please save your work and prepare to immediate reboot in 3 minutes - It's working. Regards, ** Description changed: Hi, As far as I know, shutdown command (and other reboot/poweroff/halt commands) are now just alias for systemctl which inits the right target, so I am reporting this bug to systemd package. I noted a strange think : shutdown -h now wall message do not send the wall message, but shutdown -h +any_value does. I conduct this test in TTY also, it seems that when the timer is now (or +0), the wall is sent after shuting down services like OpenSSH, so users logged in cannot see it. When the time value is +1 or more, the wall is properly displayed. Step to reproduce : - Ubuntu's Version : 15.04 (seems to not be the case in 14.10 where - systemd is not completely used, as all shutdown/halt/poweroff/reboot - commands are symlink to reboot and not systemctl). + Ubuntu Version : 15.04 from a fresh Released install (seems to not be + the case in 14.10 where systemd is not completely used, as all + shutdown/halt/poweroff/reboot commands are symlink to reboot and not + systemctl). - sudo shutdown -r now This is a maintenance reboot as we discuss earlier, server will be back in few seconds. - No one of my logged user saw this notice - sudo shutdown -r +3 This is an unscheduled URGENT maintenance. Please save your work and prepare to immediate reboot in 3 minutes - It's working. Regards, ** Description changed: Hi, As far as I know, shutdown command (and other reboot/poweroff/halt commands) are now just alias for systemctl which inits the right target, so I am reporting this bug to systemd package. - I noted a strange think : shutdown -h now wall message do not send the + I noted a strange thing : shutdown -h now wall message do not send the wall message, but shutdown -h +any_value does. I conduct this test in TTY also, it seems that when the timer is now (or +0), the wall is sent after shuting down services like OpenSSH, so users logged in cannot see it. When the time value is +1 or more, the wall is properly displayed. Step to reproduce : Ubuntu Version : 15.04 from a fresh Released install (seems to not be the case in 14.10 where systemd is not completely used, as all shutdown/halt/poweroff/reboot commands are symlink to reboot and not systemctl). - sudo shutdown -r now This is a maintenance reboot as we discuss earlier, server will be back in few seconds. - No one of my logged user saw this notice - sudo shutdown -r +3 This is an unscheduled URGENT maintenance. Please save your work and prepare to immediate reboot in 3 minutes - It's working. Regards, ** Summary
[Touch-packages] [Bug 1448076] [NEW] Wrong keyboard settings.
Public bug reported: Hi, I'm using a fresh installation of kubuntu 15.04 on a laptop with an external keyboard. My system is installed in english but I'm using french keyboards. When I enter my password in sddm with the laptop internal keyboard it works ok. However, when I use the external keyboard then I have to type the password as if the keyword was a qwerty one. Nothing critical but it is annoying. Maybe is a bug in the kubuntu installer. Here there a way to tell sddm that both keyboards are french ones? Does it correlates with locales? or with the kde keyboards layaouts?? Xavier ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Package changed: xorg (Ubuntu) = sddm (Ubuntu) ** Description changed: Hi, I'm using a fresh installation of kubuntu 15.04 on a laptop with an external keyboard. My system is installed in english but I'm using french keyboards. - When I enter my password with the laptop internal keyboard it works ok. However, when I use the external keyboard then I have to type the password as if the keyword was a qwerty one. Nothing critical but it is annoying. + When I enter my password in sddm with the laptop internal keyboard it works ok. However, when I use the external keyboard then I have to type the password as if the keyword was a qwerty one. Nothing critical but it is annoying. Maybe is a bug in the kubuntu installer. Here there a way to tell sddm that both keyboards are french ones? Does it correlates with locales? or with the kde keyboards layaouts?? Xavier -- 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/1448076 Title: Wrong keyboard settings. Status in sddm package in Ubuntu: New Bug description: Hi, I'm using a fresh installation of kubuntu 15.04 on a laptop with an external keyboard. My system is installed in english but I'm using french keyboards. When I enter my password in sddm with the laptop internal keyboard it works ok. However, when I use the external keyboard then I have to type the password as if the keyword was a qwerty one. Nothing critical but it is annoying. Maybe is a bug in the kubuntu installer. Here there a way to tell sddm that both keyboards are french ones? Does it correlates with locales? or with the kde keyboards layaouts?? Xavier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1448076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447821] [NEW] Lockscreen does not ask for ldap password
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: I manage desktops where the users log into an today updated ubuntu 14.04.1 amd64 desktop using ldap users. When the desktop goes to lockscreen, in order to unlock I may [see IMG_20150423_182816.jpg attached]: 1. Use my right ldap password: Unlock successfully; 2. Use a wrong ldap password: It doesn't unlock, showing an error message; 3. Don't use any password, just press Enter: Unlock successfully! This is a serious security failure. One unauthorized person walking around could access a machine and use it. There's no references in logs like syslog, auth.log, etc. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: ldap -- Lockscreen does not ask for ldap password https://bugs.launchpad.net/bugs/1447821 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity 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 1421009] Re: unity8 sometimes hangs on boot
** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: lxc-android-config (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: In Progress Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
Set to critical as you can't access the phone or make emergency calls which I think is a legal requirement. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
The bug (which leds to screenshot in comment #3) has been produced with a modified ofono that was fixing bug #1436820. This modified ofono shows the number of retries on boot and when the SIM gets toasted after introducing 10 times a wrong PUK (both things were not happening before). Package attached to make testing easier for indicator-network or other packages affected. ** Attachment added: ofono_1.12.bzr6894+15.04.20150423-0ubuntu1_armhf.deb https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+attachment/4382789/+files/ofono_1.12.bzr6894%2B15.04.20150423-0ubuntu1_armhf.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440811] Re: ibus-ui-gtk3 crashed with SIGABRT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1440811 Title: ibus-ui-gtk3 crashed with SIGABRT Status in ibus package in Ubuntu: Confirmed Bug description: I'm getting this in 15.04: The application Keyboard Input Methods has closed unexpectedly. /usr/lib/ibus/ibus-ui-gtk3 There were other reports, but none for 15.04 it seemed so I reported again.. One special case: [This program doesn't seem essential to me (for Icelandic language) and probably should work in any kernel?] After installing 15.04 I can't actually boot in and do anything w/13.19. That is, I do not get far enough to get the above error. I have to start with an older kernel: $ uname -a Linux Ryksugan 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I may report another bug for the kernel problem.. I never got this in 14.04. Upgraded to 14.10 (to get to 15.04, didn't seem to be another way to it) where I got this error (from memory, exactly the same..) and then soon after to 15.04. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 16:56:09 2015 Disassembly: = 0x7f59dfc33267: Cannot access memory at address 0x7f59dfc33267 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-08-21 (227 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-04-06 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1440811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Zsombor UX Spec link is broken https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444268] Re: [Lenovo ThinkPad T400] Screen corruption
MegaBrutal, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions verbatim at https://01.org/linuxgraphics/documentation /how-report-bugs ? Please provide a direct URL to your bug report once you have made it so that it may be tracked. Thank you for your understanding. ** Changed in: xorg (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1444268 Title: [Lenovo ThinkPad T400] Screen corruption Status in xorg package in Ubuntu: Triaged Bug description: I often perceive massive screen corruption, most prominently in Firefox / GMail, but it may happen with any application, including terminals. Sometimes oversized letters appear. I run video stress tests, but they run without errors. I suspect the problem presents when many text needs to be rendered on-screen, as odd as it sounds. I will attach screenshots. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 15 07:23:31 2015 DistUpgraded: 2014-11-11 12:36:03,224 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-06-10 (308 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-11-11 (154 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Apr 11 00:20:40 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16435 vendor LEN xserver.version: 2:1.16.0-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222053] Re: per-session gsettings overrides
** Bug watch added: GNOME Bug Tracker #746592 https://bugzilla.gnome.org/show_bug.cgi?id=746592 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=746592 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1222053 Title: per-session gsettings overrides Status in The G Library - GLib: Unknown Status in glib2.0 package in Ubuntu: New Bug description: There have been several occasions now where Ubuntu GNOME has had to patch code, that could in theory instead be handled by per-session gsettings overrides. A recent example is the background plugin in gnome-settings-daemon (LP: #1219148), this should be loaded under unity, gnome-flashback sessions but not gnome-shell session. A per- session override would make this possible without any patches to the codebase. As I understand it the overrides are processed by glib-compile-schemas so perhaps we would have to recompile schemas on each login to achieve this? Any thoughts on how we can achieve this? To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1222053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447917] [NEW] popup volume previewer should not show up when adjusting volume using a volume slider
You have been subscribed to a public bug: $ system-image-cli -i current build number: 21 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-24 06:07:50 version version: 21 Steps 1. swipe down from Sound Indicator 2. slide on the volume slider = a popup volume previewer shows up 3. enter System Settings - Sound 4. slide on the Ringer volume slider = a popup volume previewer shows up Expect In step2 and step4, The popup previewer is unexpected, as there is already a slider shows the current volume status. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- popup volume previewer should not show up when adjusting volume using a volume slider https://bugs.launchpad.net/bugs/1447917 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound 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 1447917] Re: popup volume previewer should not show up when adjusting volume using a volume slider
that's an indicator issue ** Package changed: ubuntu-system-settings (Ubuntu) = indicator-sound (Ubuntu) ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1447917 Title: popup volume previewer should not show up when adjusting volume using a volume slider Status in indicator-sound package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 21 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-24 06:07:50 version version: 21 Steps 1. swipe down from Sound Indicator 2. slide on the volume slider = a popup volume previewer shows up 3. enter System Settings - Sound 4. slide on the Ringer volume slider = a popup volume previewer shows up Expect In step2 and step4, The popup previewer is unexpected, as there is already a slider shows the current volume status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1447917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267184] Re: [Apps Scope] apps that are being downloaded/installed are not shown differently from un-installed apps
** Changed in: ubuntu-ux Status: Fix Committed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1267184 Title: [Apps Scope] apps that are being downloaded/installed are not shown differently from un-installed apps Status in Ubuntu UX bugs: In Progress Status in unity-scope-click package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: If a user chooses to install an app but doesn't stay on the app preview while it downloads and installs (or the device sleeps in the meantime), when they see the list of apps, the app that is being downloaded is still shown as un-installed, with no distinction made. This needs design input - some platforms show the app in the list of 'installed apps' (eg iOS home screen) but have a progress bar or some other badge to show that it's not ready to run yet. This affects both unity8 and the scope because there will be additional state for the scope to send to the dash in the apps list results. RESOLUTION Design: Description of desired behaviour added to comments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1267184/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Bug watch removed: LibreOffice Bugzilla #82659 https://www.libreoffice.org/bugzilla/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: Fix Released Status in upower source package in Vivid: Fix Released 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 1447917] Re: popup volume previewer should not show up when adjusting volume using a volume slider
Talked to Ted about it, we should add a new action to indicator-sound to change the sound without notifications and makes the settings use that -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1447917 Title: popup volume previewer should not show up when adjusting volume using a volume slider Status in indicator-sound package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 21 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-24 06:07:50 version version: 21 Steps 1. swipe down from Sound Indicator 2. slide on the volume slider = a popup volume previewer shows up 3. enter System Settings - Sound 4. slide on the Ringer volume slider = a popup volume previewer shows up Expect In step2 and step4, The popup previewer is unexpected, as there is already a slider shows the current volume status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1447917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 760140] Re: HOME environmental variable no long preserved with sudo by default
I personally believe that the decision of adding this patch is wrong, please refer Bug #1373495. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/760140 Title: HOME environmental variable no long preserved with sudo by default Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Natty: Fix Released Bug description: Binary package hint: sudo As discussed on ubuntu-devel in February https://lists.ubuntu.com/archives/ubuntu- devel/2011-February/032490.html: sudo sh -c 'echo $HOME' no longer returns the current users home directory rather it returns /root. This is a change in behavior from Maverick which kept $HOME. The following debian bug contains information about why this is happening now - http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=596847. The HOME and MAIL environment variables are now reset based on the target user's password database entry when the env_reset sudoers option is enabled (which is the case in the default configuration). Something should be done to ensure there isn't a regression and that $HOME is preserved by default. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: sudo 1.7.4p4-5ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.41-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs nls_utf8 isofs nfs lockd fscache nfs_acl auth_rpcgss sunrpc snd_hrtimer binfmt_misc usblp autofs4 dm_crypt snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_ac97_codec snd_hda_codec ac97_bus snd_pcm snd_util_mem snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc netconsole configfs firewire_sbp2 emu10k1_gp lp gameport parport psmouse serio_raw joydev dcdbas raid10 raid456 async_pq async_xor async_memcpy async_raid6_recov raid6_pq async_tx raid0 multipath linear dm_raid45 xor raid1 hid_logitech ff_memless hid_microsoft usbhid hid usb_storage uas firewire_ohci firewire_core crc_itu_t radeon ahci libahci ttm drm_kms_helper e1000e drm i2c_algo_bit Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Apr 13 11:23:27 2011 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sudo UpgradeStatus: Upgraded to natty on 2011-04-10 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270189] Re: Ubuntu Touch devices are using cellular DNS servers over wifi connection
I created a tail file in /etc/resolvconf/resolv.conf.d and added BT's primary DNS which seems to workaround my problem. -- 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/1270189 Title: Ubuntu Touch devices are using cellular DNS servers over wifi connection Status in network-manager package in Ubuntu: Confirmed Bug description: On my Nexus 4, build 121 with TMobile, when I am on wifi, I correctly get a 192.168 ip and DNS entries for this network (on wlan0) -- fine. When I am in range of cellular data, I get an ip address from TMobile and am given DNS entries that aren't on the same network as the TMobile ip address (on rmnet_usb0). The problem is, the DNS entries from TMobile are preferred over the ones from the wifi network such that while wlan0 is correctly setup as the default route, DNS queries are being made to the TMobile DNS servers over wlan0 because there are no explicit routes to these servers. This is problematic because the remote DNS server may not respond to queries coming from out of network or site policy may disallow the use of foreign DNS servers-- both of which result in slow (or possibly failing) DNS queries since the cellular DNS is checked first. Also, where it did work, these queries could incur charges when the user is intending to use only wifi. In the case of (at least) TMobile, this could be a security concern because the well-known TMobile DNS servers are on the private '10.' network, which opens the possibility for a rogue DNS server to be on the private wifi network with this ip address. This could be fixed in (at least) four ways: 1) when on wifi, don't merge the DNS servers on cellular networks at all which forces the device to use the ones available on the site (wlan0). This is guaranteed to not incur changes 2) when on wifi, merge the DNS server from the cellular network, but add them after the ones on the wifi network. This will try the site's DNS first and only if they fail, fallback to the cellular DNS. This may incur charges under certain circumstances 3) add an explicit route to the cellular DNS servers through rmnet_usb0. This will bypass the site DNS with all queries going through cellular DNS. This will incur charges and would make the device unable to resolve site-local names. 4) same as '2', but also add explicit routes for the cellular name servers. This should only incur charges if wifi DNS fails I think '3' is out. '2' and '4' seems most intuitive (with '4' perhaps most correct). '1' seems also ok. # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.x.1 0.0.0.0 UG0 0 0 wlan0 100.152.35.128 0.0.0.0 255.255.255.252 U 0 0 0 rmnet_usb0 192.168.x.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info Auto-activating connection '/310260575949457/context1'. Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) starting connection '/310260575949457/context1' Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info (/ril_0): device state change: disconnected - prepare (reason 'none') [30 40 0] Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 1 of 5 (Device Prepare) scheduled... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 1 of 5 (Device Prepare) started... Jan 17 07:36:38 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 1 of 5 (Device Prepare) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info (/ril_0): IPv4 static configuration: Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info address 100.152.35.130/30 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info DNS 10.177.0.34 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info DNS 10.168.183.116 Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 2 of 5 (Device Configure) scheduled... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 2 of 5 (Device Configure) starting... Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info (/ril_0): device state change: prepare - config (reason 'none') [40 50 0] Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 2 of 5 (Device Configure) successful. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation (/ril_0) Stage 2 of 5 (Device Configure) complete. Jan 17 07:36:41 ubuntu-phablet NetworkManager[1130]: info Activation
[Touch-packages] [Bug 1447987] [NEW] apt-add-repository fails when adding Ondrej PHP5 Launchpad Repository
Public bug reported: Hi, I was adding Ondrej PHP5 repo and it thrown me following error: gpg: /tmp/tmptxhd3gxt/trustdb.gpg: trustdb created gpg: key E5267A6C: public key Launchpad PPA for Ond\xc5\x99ej Sur� imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python3.4/threading.py, line 920, in _bootstrap_inner self.run() File /usr/lib/python3.4/threading.py, line 868, in run self._target(*self._args, **self._kwargs) File /usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py, line 687, in addkey_func func(**kwargs) File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 370, in add_key return apsk.add_ppa_signing_key() File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 261, in add_ppa_signing_key tmp_export_keyring, signing_key_fingerprint, tmp_keyring_dir): File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 210, in _verify_fingerprint got_fingerprints = self._get_fingerprints(keyring, keyring_dir) File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 202, in _get_fingerprints output = subprocess.check_output(cmd, universal_newlines=True) File /usr/lib/python3.4/subprocess.py, line 605, in check_output output, unused_err = process.communicate(inputdata, timeout=timeout) File /usr/lib/python3.4/subprocess.py, line 936, in communicate stdout = _eintr_retry_call(self.stdout.read) File /usr/lib/python3.4/subprocess.py, line 487, in _eintr_retry_call return func(*args) File /usr/lib/python3.4/encodings/ascii.py, line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128) Found that its issue with specifically Ondrej repos. On digging further found that, its happening because of some special characters present in the name of Ondrej Suri: gpg: key E5267A6C: public key Launchpad PPA for Ond\xc5\x99ej Sur� imported Only fix I found is to use UTF-8 encoding. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1447987 Title: apt-add-repository fails when adding Ondrej PHP5 Launchpad Repository Status in software-properties package in Ubuntu: New Bug description: Hi, I was adding Ondrej PHP5 repo and it thrown me following error: gpg: /tmp/tmptxhd3gxt/trustdb.gpg: trustdb created gpg: key E5267A6C: public key Launchpad PPA for Ond\xc5\x99ej Sur� imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python3.4/threading.py, line 920, in _bootstrap_inner self.run() File /usr/lib/python3.4/threading.py, line 868, in run self._target(*self._args, **self._kwargs) File /usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py, line 687, in addkey_func func(**kwargs) File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 370, in add_key return apsk.add_ppa_signing_key() File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 261, in add_ppa_signing_key tmp_export_keyring, signing_key_fingerprint, tmp_keyring_dir): File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 210, in _verify_fingerprint got_fingerprints = self._get_fingerprints(keyring, keyring_dir) File /usr/lib/python3/dist-packages/softwareproperties/ppa.py, line 202, in _get_fingerprints output = subprocess.check_output(cmd, universal_newlines=True) File /usr/lib/python3.4/subprocess.py, line 605, in check_output output, unused_err = process.communicate(inputdata, timeout=timeout) File /usr/lib/python3.4/subprocess.py, line 936, in communicate stdout = _eintr_retry_call(self.stdout.read) File /usr/lib/python3.4/subprocess.py, line 487, in _eintr_retry_call return func(*args) File /usr/lib/python3.4/encodings/ascii.py, line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128) Found that its issue with specifically Ondrej repos. On digging further found that, its happening because of some special characters present in the name of Ondrej Suri: gpg: key E5267A6C: public key Launchpad PPA for Ond\xc5\x99ej Sur� imported Only fix I found is to use UTF-8 encoding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1447987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1437719] Re: [Dell Inspiron 5547] Black Screen on user switch
Rusty Shackleford, you may be affected by https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1446417 (WORKAROUND is available). -- 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/1437719 Title: [Dell Inspiron 5547] Black Screen on user switch Status in xorg package in Ubuntu: Incomplete Bug description: When switching users (primarly using Ctrl-Alt-F(7-10) the monitor will sometimes go black. This happens once or twice a day, although on occasion it doesn't occur for several days. It has occurred at least once a week since I installed Ubuntu 14.04.1. It seems to be more of a problem since moving to 14.04.2 - I did perform installation of the Utopic Kernel, X, and MesaGL packages, but this is only perception. At the same time I switched from Unity to Cinnamon (Jeremy Clarkson isn't the only dinosaur roaming the world) - but I have confirmed that just running Unity desktops is vunerable. The display can be restored by sudo service lightdm restart - run from an ssh login from another system. Steps to consistently reproduce the problem is simply to perform abusive user stress testing: switching from one user to another rapidly: as soon as the display switches go back to the other. Usually I can get a black screen with this method in under a minute with Unity desktops. I have the same issue with another system (Dell Vostro 3550) reported in Bug #1437557 - submitting a new defect since this is different hardware and even though the defects look the same there might be differences underneath the hood causing the problem. 14.04.2 Trusty 3.16.0-33-generic. I'll edit this report shortly with additional system info. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 28 14:45:26 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:063e] InstallationDate: Installed on 2014-12-23 (95 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 5547 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=6eb0eadb-81ed-43ee-aab3-e3fe6b37ca75 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/12/2014:svnDellInc.:pnInspiron5547:pvrA05:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 5547 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Mar 27 15:14:18 2015 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448017] Re: Apps crash when opening tab menus in landscape mode
Confirmed on arale as well, running r127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1448017 Title: Apps crash when opening tab menus in landscape mode Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1448017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448017] Re: Apps crash when opening tab menus in landscape mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1448017 Title: Apps crash when opening tab menus in landscape mode Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1448017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403867] Re: Desktop/wallpaper flickers dreadfully
This bug continues in 15.04. Desktop is apparently never redrawn, so when I close or minimise a window, it leaves behind ghosts of the animation as it minimises. -- 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/1403867 Title: Desktop/wallpaper flickers dreadfully Status in Unity: New Status in unity package in Ubuntu: New Bug description: Since 14.10 the only way to use the system is with apps full-screen, because the background/desktop is constantly flickering. If you close a window, it leaves flickering ghosts of itself, like a nightmare. See enclosed ogv file for an example. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,vpswitch,unitymtgrabhandles,grid,place,move,resize,regex,animation,expo,mousepoll,session,snap,gnomecompat,ezoom,wall,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 18 13:45:17 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0344] InstallationDate: Installed on 2011-12-09 (1105 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Acer Aspire X3900 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=b7a5a606-5ebd-444b-8760-c11800be9c9e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: FIH57 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd12/16/2009:svnAcer:pnAspireX3900:pvr:rvnAcer:rnFIH57:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X3900 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 18 12:31:24 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1139 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1403867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292700] Re: [Scopes] No indication that searches are local only
--UX comment-- 1- Indication of search is only local: As part of the Touch Navigation Update project that is ongoing, scopes will be treated as apps; therefore, the search function won't be global. Each scope will have it's own search history and results will be displayed as it follows: a. Scopes with only local content will only display locally stored results (eg. Apps/Catalogue scope) b. Scopes with online and local content will display both locally stored and external results (eg. Music scope) c. Scopes with only online content will display external results (eg. News scope) *Grouping search results by category (eg: ubuntu store, local, web...) will be taken into consideration when designing Scope filters. ** The serch function cannot be 'set to search locally' or 'set to search globally' therefore there's not need for indicating this at a UI level. 2. Offline states: Latest spec covers offline use case (https://sites.google.com/a/canonical.com/unity8dash/toolkit/10-content- loading). Also, there's an ongoing project to update the scope toolkit and this will be consider. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1292700 Title: [Scopes] No indication that searches are local only Status in Ubuntu UX bugs: Fix Committed Status in unity-scope-click package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: 1) root@ubuntu-phablet:/# lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 2) root@ubuntu-phablet:/# dpkg -l unity-scope-click Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii unity-scope-cl 0.1+14.04.20 armhfClick Packages Scope for Unity 3) When searching on the Applications scope I would have expected to get an indication that the search is only local. It took too many people a too long time to figure out that this was the reason that no search results from ubuntu one on the net was shown 4) We were playing guessing games what could be wrong ;D Solution Latest spec covers offline use case (https://sites.google.com/a/canonical.com/unity8dash/toolkit/10-content-loading) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1292700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1097089] Re: debconf gtk+ dialog boxes do not remember window sizes on ubuntu.
** No longer affects: unity (Ubuntu) -- 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/1097089 Title: debconf gtk+ dialog boxes do not remember window sizes on ubuntu. Status in LibreOffice Productivity Suite: Won't Fix Status in Nautilus: Invalid Status in Unity: Confirmed Status in compiz package in Ubuntu: Confirmed Status in debconf package in Ubuntu: Incomplete Bug description: Gtk window placement not remembering size when it is an open or save dialog window. Problem: 1. Open the open dialog on libreoffice. 2. Window overlaps off screen. Does not fit on screen. 3. Click the maximise button and the window adjusts as a maximised window that fits on the screen. 4. Close window. 5. Open window again. 6. Same problem overlaps on screen does not remember that it was in a maximised state when I closed it from last time. 7. Have to click maximise again! What it needs to do: 1. The 2nd window should remember where it was in a maximised state (not overlap when i open it again) as I had left it when I had closed the 1st window. 2. Window open and save dialog s should remember there state no matter how they are adjusted. I have filed a gtk bug. My response so far is that it is a Ubuntu problem and maybe a unity problem. What I think is happening: The open and save dialog window knows that it needs to be at a resolution as it was before... And that is what it is directly doing. But, What the window needs to do though is to be told when it is opened to go to that size and resolution but to also go back into maximise mode as I had left it before. Links: https://bugs.launchpad.net/ubuntu/+s...iz/+bug/760645 launchpad bug: Bug filed with gtk developer: https://bugzilla.gnome.org/show_bug.cgi?id=685347 Screenshots in both links of what is going wrong. I have had this problem with many versions of ubuntu since 10.04.. Earlier. It would be great if it could be fixed... still happens in quantal 12.10. It is quite annoying when the dialog doesn't remember its position or fits on the screen?? this happens on any open or save window in ubuntu on any program. Including Firefox... Chromium... Libreoffice... Archive manager Nautilus And many many many others. more links are attached from existing bug reports... if this bug needs to be cleaned up for more information I am happy to provide a clearer outline. Please help, bash321. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1097089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445916] Re: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1445916 Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Confirmed Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 14.10 Package: util-linux 2.25.1-3ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 Date: Sat Apr 18 15:27:30 2015 DuplicateSignature: package:util-linux:2.25.1-3ubuntu4.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-16 (214 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) SourcePackage: util-linux Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-11-30 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1445916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447955] [NEW] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Public bug reported: This bug is reproduced during upgrade from 14.10 to 15.04. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: modemmanager ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 09:00:25 2015 DuplicateSignature: package:modemmanager:1.4.0-1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2014-12-09 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: modemmanager Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1447955 Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in modemmanager package in Ubuntu: New Bug description: This bug is reproduced during upgrade from 14.10 to 15.04. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: modemmanager ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 09:00:25 2015 DuplicateSignature: package:modemmanager:1.4.0-1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2014-12-09 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: modemmanager Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
yesterday i plugged my ipad4 (ios8) into my Ubuntu 14.04 (trusty) laptop. After that i began to get this same message popup at login and exit - though there did not seem to be any actual problem. I had libimobiledevice4 already installed and installed libimobiledevice-utils this morning. On Reboot i did not see the message. -- 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/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in upower package in Ubuntu: Confirmed Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 service_client_free+25: mov (%esi),%eax PC (0xb74e9919) ok source (%esi) (0x302e) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
Two ideas how to fix that: * ecryptfs-setup-swap should change the partition type UUID to not be swap any more so that we don't try and auto-activate it. This is my preferred solution if it works. * ecryptfs-setup-swap creates an override .swap unit which disables the auto-mounting. But as we would again have to refer to real device names, we lose the entire point of keeping the underlying unencrypted swap partition, i. e. so that we can refer to it by UUID. ** Package changed: systemd (Ubuntu Vivid) = ecryptfs-utils (Ubuntu Vivid) -- 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/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) Status in ecryptfs-utils package in Ubuntu: In Progress Status in ecryptfs-utils source package in Vivid: In Progress Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
So it is as I suspected: * ecryptfs-setup-swap creates cryptswap1 at 512KiB offset of the former real swap partition (vda3), and adds that to /etc/crypttab; as we need/want the UUID, we keep the original swap header * During boot, systemd-gpt-generator sees the apparent unencrypted swap partition on vda3 and creates a .swap unit for this. This doesn't happen on classic MBR partitions, as there are no partition type UUIDs and no auto-discovery * The real encrypted swap partition (cryptswap1) gets enabled later, and that fails with busy as the unencrypted partition is already active. -- 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/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) Status in ecryptfs-utils package in Ubuntu: In Progress Status in ecryptfs-utils source package in Vivid: In Progress Bug description: I'm still sorting out the details and eliminating variables, but as far as I can tell: Steps to reproduce === 1) Install Ubuntu using GPT partitioning for the OS drive[*] 2) Choose require my password to login, and check encrypt my home directory Expected behavior === No special user interaction should be required to initialized the crytposwap other than normally logging in Actual behavior Prior to lightdm coming up, you will be prompted to enter your passphrase to unlock the cryptoswap, similar to how you would be prompted to unlock the OS drive when using full disk encryption (see attached photo). When lightdm comes up, you have to enter your password/passphrase again to login. Work-arounds === 1) This only seems to happen when using GTP partitioning, not MBR... so use MBR if you can 2) Even with GTP partitioning, booting with init=/sbin/upstart seems to reliably fix the problem, so it certainly seems systemd related Notes = * As far as I can tell, there isn't a way to force Ubiquity to create a GPT partition table when the OS drive is 2TB, but it will automatically use GPT partitioning when the OS drive is = 2TB. My particular test was done using the System76 imaging server, which by default uses GPT partitioning even when the OS drive is 2TB. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 22 11:40:29 2015 EcryptfsInUse: Yes MachineType: System76, Inc. Kudu Professional ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=e6c5aea5-d57c-410d-abce-66e96175e946 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RS76 dmi.board.asset.tag: Tag 12345 dmi.board.name: Kudu Professional dmi.board.vendor: System76, Inc. dmi.board.version: kudp1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: kudp1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnKuduProfessional:pvrkudp1:rvnSystem76,Inc.:rnKuduProfessional:rvrkudp1:cvnSystem76,Inc.:ct9:cvrkudp1: dmi.product.name: Kudu Professional dmi.product.version: kudp1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
I think I understand what's happening now - it's not the log that isn't being freed, it's the list entry the log is attached to that is not freed. The effect is the same though - calling log_clear_unflushed() multiple times could trigger this issue since the still-valid (but incorectly so) list entry is now pointing at potentially garbage memory where a Log used to be. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447748] Re: SIM unlock screen unusable when launched from indicator
I have a feeling the breakage here is nothing to do with unlocking from the indicator, and everything to do with cancelling the dialogue once, and starting it again. ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Pete Woods (pete-woods) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447748 Title: SIM unlock screen unusable when launched from indicator Status in indicator-network package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: The SIM lock screen behaves differently during boot and launching it from indicator network. Mostly unusable from indicator to unlock PIN (those were the failures reported below). Test case. - Reboot the phone with a valid SIM card. - Unlock the device. - Dismiss the PIN unlock screen. - Open the network indicator. - Tap on unlock SIM card. - Introduce incorrect PINs. Expected result. - The behaviour is the same as when the SIM unlock page is run on boot time. Actual result. - The number of remaining PIN trials is not correctly shown. - When the PIN is locked, no PUK lock screen is shown. Must be closed and opened (tap on unlock SIM card in indicator) to be shown. - After PUK has been correctly introduced, PIN screen should be shown. It is not. - Close and re-open the screen does show the PIN screen to introduce the new one. Tested with vivid-proposed 183 / Arale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336731] Re: [Scopes] Sticky headings when scrolling Scopes should have some visible separation from the items (including icons) that slide under them.
Drop shadows is ok for now. We are working on an improved version of all headers. I reattach the image for reference. ** Attachment added: drop.jpg https://bugs.launchpad.net/ubuntu-ux/+bug/1336731/+attachment/4382788/+files/drop.jpg ** Changed in: ubuntu-ux Status: Fix Committed = 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/1336731 Title: [Scopes] Sticky headings when scrolling Scopes should have some visible separation from the items (including icons) that slide under them. Status in Ubuntu UI Toolkit: Invalid Status in Ubuntu UX bugs: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Sticky headings when scrolling the dash should have some visible separation from the icons that slide under them. When scrolling the dash you see sticky headings like Recent and My apps. This is great but there's no visible delineation between the heading background that icons are sliding under and the icons themselves. They just appear and disappear. I think we need a better visual cue for what's happening. Like making the heading transparent so you can see the icons slide under. Or perhaps a simple drop shadow across the edge the icons go under. # system-image-cli -i current build number: 106 device name: mako channel: devel alias: ubuntu-touch/utopic last update: 2014-07-02 10:17:01 version version: 106 version ubuntu: 20140701 version device: 20140625 # dpkg -l | grep unity8 ii unity8 7.89+14.10.20140627-0ubuntu1 armhf Unity 8 shell ii unity8-common 7.89+14.10.20140627-0ubuntu1 all Unity 8 shell (common files) ii unity8-private:armhf 7.89+14.10.20140627-0ubuntu1 armhf Unity 8 private libs [UX Comment] Edited title to reflect this is a Scopes bug (rather than a Dash bug) This bug applies to items other than icons in the Apps Scope. Former Lead Visual Designer provided a fix: https://launchpadlibrarian.net/183779221/drop.jpg. Reassigning to new Lead Visual Designer to follow up on status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1336731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424948] Re: Evince doesn't show µ
This bug still exists in Ubuntu 15.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1424948 Title: Evince doesn't show µ Status in fontconfig package in Ubuntu: New Bug description: I am on Ubuntu 14.10 with evince 3.14.1. In the attached example file there should be some µ on page 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1424948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch
I have a similar issue ( BQ E4.5 ), on my phone the location service works only when I'm in a wi-fi network. This is a shame because I love the NearBy scope, but it's useless without the location service. :'( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
** Description changed: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by - whatever proposed solution, it will hang at 30 boots. + whatever proposed solution, it will hang eventually. Current highest + amount of reboots without errors is 54, so it's probable a 100 reboots + is needed for testing. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang eventually.
[Touch-packages] [Bug 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)
Screenshot showing the super-thin divider. ** Attachment added: scratch.jpg https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368798 Title: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch) Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 926379] Re: compiz crashed with SIGSEGV in intel_miptree_release()
** Bug watch removed: LibreOffice Bugzilla #46303 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=46303 -- 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/926379 Title: compiz crashed with SIGSEGV in intel_miptree_release() Status in X.org xf86-video-intel: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: i just update czajkowski bryceh: alt tab through applications fast czajkowski vlc thunderbird, 2 terminals and 2 chromes out czajkowski seems to make it have a hissy fit ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-ux31 3.2.2 Uname: Linux 3.2.0-12-ux31 x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 3 23:10:11 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120125) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f109783fd49 intel_miptree_release+9: mov (%rdi),%rcx PC (0x7f109783fd49) ok source (%rdi) (0x0220) not located in a known VMA region (needed readable region)! destination %rcx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: intel_miptree_release () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so intel_update_renderbuffers () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so intelSetTexBuffer2 () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so TfpTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so boost::detail::function::function_invoker4GLTexture::List (*)(unsigned long, int, int, int), GLTexture::List, unsigned long, int, int, int::invoke(boost::detail::function::function_buffer, unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in intel_miptree_release() UpgradeStatus: Upgraded to precise on 2012-02-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/926379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
In fact I would not expect neither of the screenshots in comments #2 or #3, but something saying that the SIM is unrecoverable AND a way to dismiss that warning and enter the phone. The SIM is unrecoverable when following ofono properties have values: org.ofono.SimManager.PinRequired = puk org.ofono.SimManager.Retries = ... [puk = 0] ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444402] Re: While sbuilding, systemd loops attempting to umount the underlay
Seems the revert in the linked bug stops this happening for me. ** Bug watch added: freedesktop.org Bugzilla #89383 https://bugs.freedesktop.org/show_bug.cgi?id=89383 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=89383 Importance: Unknown Status: Unknown -- 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/102 Title: While sbuilding, systemd loops attempting to umount the underlay Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? laney@vivid apt-cache policy systemd systemd: Installed: 219-7ubuntu1 Candidate: 219-7ubuntu1 Version table: *** 219-7ubuntu1 0 500 http://sherwood/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
** Description changed: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == + # Prepare debugging + adb shell + sudo apt install qtbase5-dbg libc6-dbg + + # Start the reboot loop + # This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang eventually. Current highest amount of reboots without errors is 54, so it's probable a 100 reboots is needed for testing. + bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done - This reboots the device in a loop, and if this bug is not fixed by - whatever proposed solution, it will hang eventually. Current highest - amount of reboots without errors is 54, so it's probable a 100 reboots - is needed for testing. + # When it fails + adb shell + sudo gdb -p $(pidof unity8) + bt + + -- + At this point, the backtrace should show: + #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37 + #1 0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=optimized out) + at thread/qmutex_linux.cpp:146 + #2 lockInternal_helperfalse (timeout=-1, elapsedTimer=0x0, d_ptr=...) + at thread/qmutex_linux.cpp:187 + #3 QBasicMutex::lockInternal (this=this@entry=0x1523b44) + at thread/qmutex_linux.cpp:203 + #4 0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59 + #5 lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620 + #6 QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215 + #7 0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, + a=ToggleWatchAction, this=synthetic pointer) at qdbusthreaddebug_p.h:183 + #8 QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, + this=synthetic pointer) at qdbusthreaddebug_p.h:198 + #9 qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46) + at qdbusintegrator.cpp:346 + #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3 + + With this, it's know that it was a QDBus locking related problem. + -- --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description:
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Damn launchpad said error or posting, and then I see it posted both of my comments :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence
Alex, I know, and I guess you can be a better person to update that, I am not in UI/UX team contrary to you :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1428762 Title: [SDK] Add Menu to the SDK to support convergence Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: We need a menu component to enable medium large form factors point click interactions E.g. Selection Menu Contextual Menu UX Spec here https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447952] [NEW] splash is small
Public bug reported: splash is small ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.76 Thu Jan 22 12:11:08 PST 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 03:24:11 2015 DistUpgraded: 2015-04-23 18:16:50,985 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed nvidia-340, 340.76, 3.19.0-15-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1525] InstallationDate: Installed on 2014-12-24 (121 days ago) InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MachineType: BIOSTAR Group G41D3C ProcEnviron: LANGUAGE=es_VE:es PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=68e6c831-40c5-44fb-a3e0-6fe136c3b202 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 12/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41D3C dmi.board.vendor: BIOSTAR Group dmi.board.version: ' ' dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: ' ' dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd12/27/2010:svnBIOSTARGroup:pnG41D3C:pvr'':rvnBIOSTARGroup:rnG41D3C:rvr'':cvnBIOSTARGroup:ct3:cvr'': dmi.product.name: G41D3C dmi.product.version: ' ' dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Apr 24 03:10:39 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputGeneric USB+PS2 Keyboard KEYBOARD, id 8 inputGeneric USB+PS2 Keyboard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1447952 Title: splash is small Status in xorg package in Ubuntu: New Bug description: splash is small ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.76 Thu Jan 22 12:11:08 PST 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 03:24:11 2015 DistUpgraded: 2015-04-23 18:16:50,985 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed nvidia-340, 340.76, 3.19.0-15-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1525] InstallationDate: Installed on 2014-12-24 (121 days ago) InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MachineType: BIOSTAR Group G41D3C ProcEnviron: LANGUAGE=es_VE:es PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=68e6c831-40c5-44fb-a3e0-6fe136c3b202 ro drm.debug=0xe plymouth:debug SourcePackage:
[Touch-packages] [Bug 1447984] [NEW] Sim blocked dialogue broken on starting phone
Public bug reported: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. ** Affects: indicator-network (Ubuntu) Importance: Critical Status: New ** Tags: qa-silo ** Attachment added: Warning page correct with and without silo https://bugs.launchpad.net/bugs/1447984/+attachment/4382776/+files/screenshot20150423_194125039.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447986] Re: seed openvpn
seeding this would cost us around 1M on disk but this way at least commandline configuartion could be used to set up VPN access on devices ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Confirmed ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Undecided = High ** Changed in: ubuntu-touch-meta (Ubuntu) Assignee: (unassigned) = Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1447986 Title: seed openvpn Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: For testing purpose the device needs resources accessible via a VPN. There is no way to do it without tainting the device, or using an access point which already have a VPN up. Could you please add openvpn by default on the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1447986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.
** Tags added: vivid ** Changed in: bluez (Ubuntu) Importance: Undecided = Medium ** Tags removed: vivid ** Tags added: jaunty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1014992 Title: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied. Status in bluez package in Ubuntu: Confirmed Bug description: After updating from 8.04 to 12.04 I cannot use rfcomm without sudo. I've already added the user to group 'dialout' . Temporary I tried to change udev.rules (KERNEL==rfcomm[0-9]*, GROUP=dialout, MODE=666) but this doesn't solve the problem so I removed it again. Here the commands I used : burki@orion:/$ hcitool scan Scanning ... 00:12:6F:08:98:FFGEO LE-71 1 burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF Can't open RFCOMM device: Permission denied burki@orion:/$ ls -l /dev/rfcomm1 ls: cannot access /dev/rfcomm1: No such file or directory burki@orion:/$ groups burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse scanner lpadmin netdev sambashare burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1 Press CTRL-C for hangup In another terminal while connection is running ... burki@orion:/$ ls -l /dev/rfcomm1 crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1 burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1) (I've stolen this command from another bug report #570692. Output is very long. Please see attachment) WORKAROUND: sudo chmod u+s /usr/bin/rfcomm ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18 Uname: Linux 3.2.0-25-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: burki 1730 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 56' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0887,10438444,00100302 HDA:80862805,80862805,0010' Controls : 49 Simple ctrls : 21 Date: Tue Jun 19 09:15:54 2012 HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-25-generic-pae N/A linux-backports-modules-3.2.0-25-generic-pae N/A linux-firmware1.79 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1014992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448017] [NEW] Apps crash when opening tab menus in landscape mode
Public bug reported: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1448017 Title: Apps crash when opening tab menus in landscape mode Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1448017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
Scratch that. We started testing on arale, and it seems that on arale at least the delay workaround is not enough. It also seems 30 reboot is noy enough to reliably reproduce the hang, as once it happened after 54 reboots. ** Changed in: lxc-android-config (Ubuntu) Assignee: Timo Jyrinki (timo-jyrinki) = (unassigned) ** Changed in: lxc-android-config (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R ~phablet/.cache/QML; ./tools/unlock-device || break; done This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang at 30 boots. --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388612] Re: [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510
** Bug watch removed: LibreOffice Bugzilla #85367 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=85367 -- 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/1388612 Title: [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510 Status in Mesa: Fix Released Status in mesa package in Ubuntu: In Progress Bug description: Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on a Dell Vostro 1510 laptop with Intel graphics. The problem used to arise also with Ubuntu 14.04 and is always reproducible with glmark2 on the LiveCD. Just to run the ideas benchmark of glmark2 to trigger the lockup in few seconds (glmark2 -b ideas). Other OpenGL applications also causes the lockup (e.g. FooBillard++, my self-made SDL applications). Memory test passed, BIOS at the latest version. Don't know if the following is a good point but I think that the problem is not caused by a failing hardware because it works fine on Windows. I tried with the latest Intel upstream kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/) and upstream X.org (https://launchpad.net/~xorg- edgers/+archive/ubuntu/ppa), no change. [Personal Notes] I'm new to Ubuntu's world, I hope I've done things right, if not please tell me and I will resend the report or supply more information. I've created the bug report with ubuntu-bug xorg --save from another machine via SSH while the sick machine was frozen. It seemed to me more logical than using ubuntu-bug directly when the system is working fine. I've collected other information via SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was added as attachment. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Nov 2 19:24:31 2014 DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0273] Subsystem: Dell Device [1028:0273] InstallationDate: Installed on 2014-10-11 (22 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro1510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago) dmi.bios.date: 03/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0M277C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro1510 dmi.product.version: Null dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.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: Sun Nov 2 18:41:51 2014 xserver.configfile: default xserver.errors: intel(0): Detected a hung GPU, disabling acceleration. intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 15873 vendor LPL xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1388612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1444883] Re: Emergency numbers for China (110, 119) are not available in emergency mode
The emergency call number (110, 112, 119) works on Arale r183, but another two number (120, 122) not, they are also emergency call number in China. -- 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/1444883 Title: Emergency numbers for China (110,119) are not available in emergency mode Status in dialer-app package in Ubuntu: New Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on Emergency Call) 2. try input 911, 112 == OK 2. try input 110, 119 == Dial button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1444883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447986] [NEW] seed openvpn
Public bug reported: For testing purpose the device needs resources accessible via a VPN. There is no way to do it without tainting the device, or using an access point which already have a VPN up. Could you please add openvpn by default on the devices. ** Affects: ubuntu-touch-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-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1447986 Title: seed openvpn Status in ubuntu-touch-meta package in Ubuntu: New Bug description: For testing purpose the device needs resources accessible via a VPN. There is no way to do it without tainting the device, or using an access point which already have a VPN up. Could you please add openvpn by default on the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1447986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
** Attachment added: What I expect to see https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+attachment/4382777/+files/screenshot20150424_091256244.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447984] Re: Sim blocked dialogue broken on starting phone
** Attachment added: What I actually see https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+attachment/4382778/+files/screenshot20150423_192816321.png ** Tags added: qa-silo ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1447984 Title: Sim blocked dialogue broken on starting phone Status in indicator-network package in Ubuntu: New Bug description: STEPS: 1. Start the phone with a sim you are prepared to scrap 2. Input the incorrect sim pin 3 times 3. Input the incorrect Puk code and new sim pin 10 times EXPECTED: I expect to see a page similar to the pin unlock page, only announcing that the sim is blocked. ACTUAL: See screenshots. I get a light grey page with the correct text and then I can't do anything with the phone. I can't swipe the page away as there is no unity8, I can't swipe down the indcators or in the launcher so I'm stuck, I can't make an emergency call which makes this a critical ship blocker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353341] Re: [Apps Scope] Apps screen spacing should be even
New app icons and grid layout is being designed and prototyped. ** Changed in: ubuntu-ux Status: Triaged = 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/1353341 Title: [Apps Scope] Apps screen spacing should be even Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: New Bug description: 1. Open the Apps screen. Use the attached screenshot for reference. What you see: The space between (A) the edge of the screen and the edge of a header, (B) the edge of the screen and the leftmost/rightmost icon, and (C) two adjacent icons, are very different. What you should see: All those spaces should be the same size. It's a basic layout error for items in a box to be closer to the edge of the box than they are to each other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1353341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441798] [NEW] -- NO more avaible -- 3G network doesn't work
You have been subscribed to a public bug: The 3G network and MMS doesn't work. Indeed, when I try to configure my APN network it seems like some fields are missing. When I fill all field matching with my APN config and I try to connect to internet it doesn't work. For more information, this is my APN configuration : http://community.48months.ie/t5/Need-Help/Internet-Settings/td-p/78 ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: Invalid -- -- NO more avaible -- 3G network doesn't work https://bugs.launchpad.net/bugs/1441798 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network 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 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)
can you send a visual reference? ** Changed in: ubuntu-ux Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368798 Title: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch) Status in Ubuntu UX bugs: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: The pin code entry screen has what appears to be a 1 pixel high line horizontal line that goes almost to the left and right borders of the screen, just above the unlock keypad. I can see the value of such a horizontal rule but it is _so_ thin that when I looked at it earlier I thought I'd either scratched the screen or damaged it somehow. Could we possibly make it slightly thicker (or dotted or something) to make it more obviously a ruler and less possibly a scratch/screen damage? :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446681] Re: resolvconf v4/v6 order does not handle bridge interfaces correctly
** Also affects: resolvconf (Debian) Importance: Undecided Status: New ** Changed in: resolvconf (Debian) Assignee: (unassigned) = Thomas Hood (jdthood) ** Changed in: resolvconf (Debian) Status: New = In Progress ** Changed in: resolvconf (Debian) Assignee: Thomas Hood (jdthood) = (unassigned) ** Changed in: resolvconf (Debian) Assignee: (unassigned) = Thomas Hood (jdthood) ** Summary changed: - resolvconf v4/v6 order does not handle bridge interfaces correctly + resolvconf interface-order gives bridge interfaces too low a priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1446681 Title: resolvconf interface-order gives bridge interfaces too low a priority Status in resolvconf package in Ubuntu: Confirmed Status in resolvconf package in Debian: In Progress Bug description: The interface-order that ships with 1.70 does not correctly detect bridge interfaces and therefore renders IPv4 resolvers before IPv6 when they are in use. I believe the automatic bug reporter has attached the interface-order I hurriedly patched in which detects bridges separately from eth interfaces. It might make sense to combine these as @(br|eth) as is done with the wifi. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: resolvconf 1.69ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Tue Apr 21 10:02:47 2015 InstallationDate: Installed on 2012-12-14 (857 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to trusty on 2014-08-18 (245 days ago) mtime.conffile..etc.resolvconf.interface.order: 2015-04-20T23:43:05.861928 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1446681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267184] Re: [Apps Scope] apps that are being downloaded/installed are not shown differently from un-installed apps
In order to reflect app installation progress in the scope main view [item: APP ARTWORK (ie icon) item 2: CARD HEADER (eg in Store)] cards will need to change layout once activated. This is part of a bigger redesign across scopes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1267184 Title: [Apps Scope] apps that are being downloaded/installed are not shown differently from un-installed apps Status in Ubuntu UX bugs: In Progress Status in unity-scope-click package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: If a user chooses to install an app but doesn't stay on the app preview while it downloads and installs (or the device sleeps in the meantime), when they see the list of apps, the app that is being downloaded is still shown as un-installed, with no distinction made. This needs design input - some platforms show the app in the list of 'installed apps' (eg iOS home screen) but have a progress bar or some other badge to show that it's not ready to run yet. This affects both unity8 and the scope because there will be additional state for the scope to send to the dash in the apps list results. RESOLUTION Design: Description of desired behaviour added to comments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1267184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com
This is a radical solution. As pointed out in comment #20 and some following comments from other users, it seems to be at first the tu- dresden mirror. May be it is enough to decouple this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. apt-get update failed, and later apt-get dist upgrade It started with this when doing a normal apt-get update W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448017] Re: Apps crash when opening tab menus in landscape mode
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/orientationManual ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1448017 Title: Apps crash when opening tab menus in landscape mode Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: On devel-proposed, *every* application that I tested crashes when trying to open the tab menu or the header menu in landscape mode. Note: This bug is not reproducible on the RTM Utopic image as of OTA-3. Steps to reproduce: 1. Open gallery app 2. Switch to landscape mode by tilting phone. 3. Press the tab menu What happens: phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-24 11:26:49 version version: 184 version ubuntu: 20150424 version device: 20150210 version custom: 20150424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1448017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439554] Re: Calendar app is not syncing anymore.
Same problem with OS Build r21, Aquaris 4.5 Ubuntu Edition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1439554 Title: Calendar app is not syncing anymore. Status in Calendar application for Ubuntu devices: Confirmed Status in qtorganizer5-eds package in Ubuntu: Confirmed Bug description: For two days already I always get an error message when trying to sync my calendar app manually, no events are synced with google-calendar anymore. calendar-app-log shows: UbuntuWindow::handleSurfaceFocusChange(focused=true) UbunutClipboard - Got invalid serialized mime data. Ignoring it. UbuntuWindow::handleSurfaceFocusChange(focused=false) It shows these three lines over and over again. I already tried to readd the google account, reinstalled the app, reset the phone to manufacturers default. Contacts do sync normal though, google calendar in webapp works. Calendar is allowed to access google-account within calendar app and account settings. Worked well until march 31st though. app-version 0.4.600, 0.4.627 os-build 20, 21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1439554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444402] Re: While sbuilding, systemd loops attempting to umount the underlay
Launchpad has imported 8 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=89383.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2015-03-01T21:25:59+00:00 Tpgxyz wrote:
Log story short.
After update to systemd-219, dracut during live iso boot was not able to
mount devices for further switch root, whereby booting iso in live mode
was not possible. An example:
LOOPDEV=$( losetup -f )
losetup -r $LOOPDEV /live/media/LiveOS/squashfs.img
mount -n -t squashfs -o ro $LOOPDEV /live/distrib
After a deep digging, and getting system to boot into a real root simple
mount command was not mounting anything.
mount -n -t squashfs -o ro
/media/OpenMandriva_2015.0/LiveOS/squashfs.img /media/test
Applying those patches fixed issue:
https://bugzilla.gnome.org/show_bug.cgi?id=743891
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/0
On 2015-03-03T14:39:39+00:00 Tpgxyz wrote:
Bump. System is unbootable with 219 release. Raising importance.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/1
On 2015-03-05T10:44:24+00:00 Tpgxyz wrote:
Looks like that applying this patch:
https://abf.io/openmandriva/systemd/blob/master/0001-Revert-core-mount-add-dependencies-to-dynamically-mo.patch
allows to mount devices.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/2
On 2015-04-03T10:50:49+00:00 Tpgxyz wrote:
Ping anyone ?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/3
On 2015-04-19T04:51:36+00:00 胡祖仪 wrote:
(In reply to Tomasz Paweł Gajc from comment #2)
Looks like that applying this patch:
https://abf.io/openmandriva/systemd/blob/master/0001-Revert-core-mount-add-
dependencies-to-dynamically-mo.patch
allows to mount devices.
Thank you very much, this patch helps me, I am doubt why upstream don't
fix this problem.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/6
On 2015-04-22T13:28:34+00:00 Grey-8 wrote:
This is a bad bug.
Please see my report on the Arch Linux bug tracker on it here:
https://bugs.archlinux.org/task/44658#comment134665
This report is using systemd from Arch's [testing] repo which seems to
be version 219 with some patches applied by the Arch maintainers which
try to address this bug: systemd 219-6,
https://www.archlinux.org/packages/testing/x86_64/systemd/
In summary, even when the bug has been fixed (allowing mounts to be
made again) there are cases when systemd is unmounting things it should
not be when the user runs umount (seems like it unmounts ALL mounts
associated with a device whenever any mount associated with that device
is umounted).
A bug that breaks filesystem mouting/unmounting seems particularly
critical. Whatever new logic 219 introduced that created this bug should
probably be reverted from the systemd release until all the mounting and
unmounting corner cases can be tested and covered.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/102/comments/7
On 2015-04-23T16:02:20+00:00 Bastien-g wrote:
Another use case to complement the report:
- system is a home server running Arch linux, full disk encrypted with
dmcrypt/LUKS and remotely unlocked via dropbear_initrd_encrypt [1]
- it was updated today with the latest systemd packages
({lib}systemd{-sysvcompat} 219-5) and latest linux-lts (3.14.39), therefore the
initramfs was rebuilt with mkinitcpio.
What happens: after rebooting I am locked out at the initramfs stage
with the following error messages:
- on client trying to ssh in dropbear_initrd:
Device /dev/disk/by-id/wwn-redacted_id-part3 doesn't exist or access
denied.
- on server:
Running systemd 219
(dropbear initialization sequence, everything is ok)
Starting dropbear
[123] Apr 23 09:43:56 Running in background
(try to connect remotely via SSH)
Pubkey auth succeeded for 'root' with key xxx from 192.xxx
syslogin_perform_logout: logout(pts/0) returned an error: No such file or
directory
Exit (root) Disconnect received
ERROR: device '/dev/mapper/lvm-archroot' not found. Skipping fsck.
ERROR: Unable to find rot device '/dev/mapper/lvm-archroot'
You are being dropped to a recovery shell
If I don't try to login via SSH there is a 15
[Touch-packages] [Bug 1437649] Re: XServer crashes when visiting web page containing PDF with Firefox
I can't reproduce this, either in a VM, or on real hardware that uses the nouveau driver. Are you still able to reproduce this with all current updates applied? ** 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/1437649 Title: XServer crashes when visiting web page containing PDF with Firefox Status in xorg package in Ubuntu: Incomplete Bug description: When opening the following link with Firefox, the X Server crashes: http://www.rauchmoebel.de/fileadmin/user_upload/Prospekte_PDF/Select/Prospekt_IMPULS_D_Webseite.pdf As such a bug might be used for evil purposes like buffer overrun to execute arbitrary code, etc. this might be security relevant. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 28 16:35:21 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8280] [1002:9836] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9836] InstallationDate: Installed on 2014-02-25 (395 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=5e706392-b33a-488d-bd51-fc1d86c7ed43 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: AM1B-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd02/21/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM1B-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 28 16:31:08 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint KEYBOARD, id 8 inputLite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0 HDMI-1 VGA-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417652] Re: Did not shut system down on low battery condition
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww21-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1417652 Title: Did not shut system down on low battery condition Status in the base for Ubuntu mobile products: Confirmed Status in powerd package in Ubuntu: Confirmed Bug description: The syslog contains a number of warnings for low battery all the way to 0%, with 0% reported for several minutes. The system just turned off but not initiated by powerd When the system was booted the charge level was reported as over 10% almost immediately. Mako running rtm To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network
** Branch linked: lp:~joergberroth/ubuntu-system-settings/wifi-802-1x- configurations -- 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/1241986 Title: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network Status in network-manager package in Ubuntu: Confirmed Bug description: On Ubuntu for Phones final image on mako I can see a network but cannot connect because I never get prompted for the username/password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1241986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440804] Re: tracker-extract assert failure: tracker-extract: /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c:193: cio_skip: Asserção `0' falhou.
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1440804 Title: tracker-extract assert failure: tracker-extract: /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c:193: cio_skip: Asserção `0' falhou. Status in tracker package in Ubuntu: New Bug description: esta ruim ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: tracker-extract 1.2.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 AssertionMessage: tracker-extract: /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c:193: cio_skip: Asserção `0' falhou. CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Apr 6 13:21:04 2015 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2015-04-06 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta i386 (20150326) ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: tracker StacktraceTop: __assert_fail_base (fmt=0xb4be1727 error: Não é possível acessar a memória no endereço 0xb4be1727, assertion=0xabb67711 0, file=0xabb672f4 /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c, line=193, function=0xb4328000 ) at assert.c:92 __GI___assert_fail (assertion=0xabb67711 0, file=0xabb672f4 /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c, line=193, function=0xabb673ec cio_skip) at assert.c:101 cio_skip () from /usr/lib/i386-linux-gnu/libopenjpeg.so.5 opj_jp2_decode () from /usr/lib/i386-linux-gnu/libopenjpeg.so.5 opj_decode_with_info () from /usr/lib/i386-linux-gnu/libopenjpeg.so.5 Title: tracker-extract assert failure: tracker-extract: /build/buildd/openjpeg-1.5.2/libopenjpeg/cio.c:193: cio_skip: Asserção `0' falhou. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1440804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448100] Re: Indicator appearing to lose status of Wi-Fi connection
** Package changed: indicator-network (Ubuntu RTM) = canonical-devices- system-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1448100 Title: Indicator appearing to lose status of Wi-Fi connection Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Bug description: Version: ubuntu-touch/stable/bq-aquaris.en r21 vegeta Don't have a scenario to reproduce this at the moment - but observed on few occasions. Symptoms: * Have been connected to Wi-Fi network for a while (Canonical-2.4GHz-g) * Connection appears to drop * Indicator icon shows me no information about data connectivity (see screenshot) * Indicator menu shows presence on a unsecured network of same name - this doesn't exist * ifconfig indicates wifi still connected * can browse internet To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1448100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410495] Re: Battery indicator goes Critical Red with more than 1 hour battery left
Specification updated. https://wiki.ubuntu.com/Power?action=diffrev2=71rev1=70 ** Changed in: indicator-power (Ubuntu) Status: In Progress = Triaged ** Changed in: indicator-power (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = (unassigned) ** Description changed: + indicator-power 12.10.6+14.10.20141015-0ubuntu1, Ubuntu 14.10 + On my current laptop, the battery indicator shows a red-with-a-little- left icon when there is more than an hour left in the battery, which is not really appropriate for a critical battery warning. This bug is probably a regression of #743823, and I was asked to create a new bug by @mpt: Christoph, yes, please report a new bug including a screenshot. On phones we may have to color by percentage, but on PCs we can and should color by time remaining to avoid false alarms. A screenshot is attached. Unfortunately I didn't realize at the time that the screenshotter does not record open menus, so you'll have to take my word that the time remaining in the indicator menu was at 1 hour. I can redo the screenshot, if necessary. - fwiw, the transition levels (based on minutes left) proposed in the bug - description of #743823 sound good to me. - - ProblemType: Bug - DistroRelease: Ubuntu 14.10 - Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1 - ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 - Uname: Linux 3.16.0-28-generic x86_64 - ApportVersion: 2.14.7-0ubuntu8 - Architecture: amd64 - CurrentDesktop: Unity - Date: Tue Jan 13 21:08:43 2015 - InstallationDate: Installed on 2014-12-22 (22 days ago) - InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) - SourcePackage: indicator-power - UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago) + https://wiki.ubuntu.com/Power#Icon: If it is discharging, the icon + interior should be filled from left to right approximately as much as + the remaining charge. If it has less than 30 minutes left on a PC, or + less than 20% left on a phone or tablet, the fill should be red rather + than monochrome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1410495 Title: Battery indicator goes Critical Red with more than 1 hour battery left Status in indicator-power package in Ubuntu: Triaged Bug description: indicator-power 12.10.6+14.10.20141015-0ubuntu1, Ubuntu 14.10 On my current laptop, the battery indicator shows a red-with-a-little- left icon when there is more than an hour left in the battery, which is not really appropriate for a critical battery warning. This bug is probably a regression of #743823, and I was asked to create a new bug by @mpt: Christoph, yes, please report a new bug including a screenshot. On phones we may have to color by percentage, but on PCs we can and should color by time remaining to avoid false alarms. A screenshot is attached. Unfortunately I didn't realize at the time that the screenshotter does not record open menus, so you'll have to take my word that the time remaining in the indicator menu was at 1 hour. I can redo the screenshot, if necessary. https://wiki.ubuntu.com/Power#Icon: If it is discharging, the icon interior should be filled from left to right approximately as much as the remaining charge. If it has less than 30 minutes left on a PC, or less than 20% left on a phone or tablet, the fill should be red rather than monochrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448101] [NEW] package click-apparmor (not installed) failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
Public bug reported: error in line = from click import command ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click-apparmor (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 11:18:05 2015 ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1 InstallationDate: Installed on 2014-11-19 (155 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click-apparmor Title: package click-apparmor (not installed) failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1448101 Title: package click-apparmor (not installed) failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1 Status in click-apparmor package in Ubuntu: New Bug description: error in line = from click import command ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click-apparmor (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 11:18:05 2015 ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1 InstallationDate: Installed on 2014-11-19 (155 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click-apparmor Title: package click-apparmor (not installed) failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1448101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442844] Re: loging o unlocking screen with no password
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1442844 Title: loging o unlocking screen with no password Status in unity package in Ubuntu: Invalid Bug description: Hi. I can login my session without entering a password.I assigned a password to my account at installation time,and login with just typing enter. And when i lock the screen,can unlock by just clicking enter and typing anything. This problem is also present in the terminal and ttys. I installed ubuntu 14.04 x86 lts with all updates. but i haven't installed any update since installation finish. Can anybody help me with this? Thanks to all ubuntu developers for working on this operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1442844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448153] [NEW] system-image-cli --list-channels does not return anything
Public bug reported: calling system-image-cli --list-channels with either 2.5 or 2.5.1 results in the command quietly returning ... adding verbosity shows a traceback like in http://paste.ubuntu.com/10878729/ ** Affects: system-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1448153 Title: system-image-cli --list-channels does not return anything Status in system-image package in Ubuntu: New Bug description: calling system-image-cli --list-channels with either 2.5 or 2.5.1 results in the command quietly returning ... adding verbosity shows a traceback like in http://paste.ubuntu.com/10878729/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1448153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447821] Re: Lockscreen does not ask for ldap password
Does this happen at the login screen too, or just at the lock screen? Could you please attach the contents of /etc/pam.d ? ** Information type changed from Private Security to Public Security ** Package changed: gnome-screensaver (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1447821 Title: Lockscreen does not ask for ldap password Status in unity package in Ubuntu: Incomplete Bug description: I manage desktops where the users log into an today updated ubuntu 14.04.1 amd64 desktop using ldap users. When the desktop goes to lockscreen, in order to unlock I may [see IMG_20150423_182816.jpg attached]: 1. Use my right ldap password: Unlock successfully; 2. Use a wrong ldap password: It doesn't unlock, showing an error message; 3. Don't use any password, just press Enter: Unlock successfully! This is a serious security failure. One unauthorized person walking around could access a machine and use it. There's no references in logs like syslog, auth.log, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1447821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447821] Re: Lockscreen does not ask for ldap password
Switching package to unity as the screenshot shows unity, not gnome- screensaver. -- 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/1447821 Title: Lockscreen does not ask for ldap password Status in unity package in Ubuntu: Incomplete Bug description: I manage desktops where the users log into an today updated ubuntu 14.04.1 amd64 desktop using ldap users. When the desktop goes to lockscreen, in order to unlock I may [see IMG_20150423_182816.jpg attached]: 1. Use my right ldap password: Unlock successfully; 2. Use a wrong ldap password: It doesn't unlock, showing an error message; 3. Don't use any password, just press Enter: Unlock successfully! This is a serious security failure. One unauthorized person walking around could access a machine and use it. There's no references in logs like syslog, auth.log, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1447821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448132] [NEW] Ubuntu 15.04 ifquery segfault issue is reported in dmesg intermediately .
Public bug reported: Ubuntu 15.04 ifquery segfault issue is reported in dmesg intermediately . Steps to reproduce: 1.Install Ubnutu 15.04 Released OS on any Gen9 servers 2.Run dmesg | grep -i error Observation: [9.287025] ifquery[819]: segfault at 1 ip 004031c8 sp 7ffd692a5bd0 error 4 in ifup[40+d000] Could find the public LaunchPad (Pubilc Launchpad # 1416793: ifquery segfaults if /run/network/ifstate file is not found ) about ifquery segfault but in our case file /run/network/ifstate is already present and command ifquery gives output : root@BL460cGen9:~# ifquery --state em49 em49=em49 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1448132 Title: Ubuntu 15.04 ifquery segfault issue is reported in dmesg intermediately . Status in ifupdown package in Ubuntu: New Bug description: Ubuntu 15.04 ifquery segfault issue is reported in dmesg intermediately . Steps to reproduce: 1.Install Ubnutu 15.04 Released OS on any Gen9 servers 2.Run dmesg | grep -i error Observation: [9.287025] ifquery[819]: segfault at 1 ip 004031c8 sp 7ffd692a5bd0 error 4 in ifup[40+d000] Could find the public LaunchPad (Pubilc Launchpad # 1416793: ifquery segfaults if /run/network/ifstate file is not found ) about ifquery segfault but in our case file /run/network/ifstate is already present and command ifquery gives output : root@BL460cGen9:~# ifquery --state em49 em49=em49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1448132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
Test binaries are available here: http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447197] Re: Stale PID file, overwriting.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1447197 Title: Stale PID file, overwriting. Status in pulseaudio package in Ubuntu: New Bug description: I can't hear any sound henokh@henokh-Inspiron-3420:~$ pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] main.c: Daemon startup without any loaded modules, refusing to work. E: [pulseaudio] xmalloc.c: Assertion 'size 0' failed at pulse/xmalloc.c:62, function pa_xmalloc(). Aborting. Aborted ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Apr 22 21:01:02 2015 InstallationDate: Installed on 2014-05-11 (345 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 05JPFK dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn05JPFK:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.daemon.conf: [deleted] modified.conffile..etc.pulse.default.pa: [inaccessible: [Errno 13] Permission denied: '/etc/pulse/default.pa'] modified.conffile..etc.pulse.system.pa: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1447197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448116] [NEW] Pointer missing on login
Public bug reported: When I login there is no pointer. I unplug my mouse replug again...pointer appears. Has happened a half dozen times now, but not every time. Might just be when I shut down after using the touchpad (usually I have the touchpad disabled). This laptop has a touchpad and an IBM mouse. Bus 001 Device 008: ID 04b3:3107 IBM Corp. ThinkPad 800dpi Optical Travel Mouse root@Hedy:/home/themusicgod1# xinput -list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=13 [slave pointer (2)] ⎜ ↳ HID 04b3:3107 id=15 [slave pointer (2)] ... Has been happening for at least a month, probably longer, but seems like it started some time after October. Ubuntu 15.04 Linux Hedy 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux xserver-xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 xserver-xorg-input-synaptics: Installed: 1.8.1-1ubuntu1 Candidate: 1.8.1-1ubuntu1 xserver-xorg-input-mouse: Installed: 1:1.9.1-1 Candidate: 1:1.9.1-1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:25:27 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0689] Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689] InstallationDate: Installed on 2014-07-09 (288 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140708) MachineType: Acer TravelMate P273-MG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate P273-MG dmi.product.version: V2.11 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Apr 24 08:18:10 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5278 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1448116 Title: Pointer missing on login Status in xorg package in Ubuntu: New Bug description: When I login there is no pointer. I unplug my mouse replug again...pointer appears. Has happened a half dozen times now, but not every time. Might just be when I shut down after using the touchpad (usually I have the touchpad disabled). This laptop has a touchpad and an IBM mouse. Bus 001 Device 008: ID 04b3:3107 IBM Corp. ThinkPad 800dpi Optical Travel Mouse root@Hedy:/home/themusicgod1# xinput -list ⎡ Virtual core pointer
[Touch-packages] [Bug 1436952] Re: X crashes on some runs of Kubuntu live image returning in SDDM login
Asus g73jh a1 upgrade from 14.02.2. - 14.10 - 15.04 No Login screen but can acess tty's if need any other information please let me know -- 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/1436952 Title: X crashes on some runs of Kubuntu live image returning in SDDM login Status in X.Org X server: New Status in xorg package in Ubuntu: Incomplete Status in xorg source package in Vivid: Incomplete Bug description: Running a Kubuntu vivid beta 2 live image on my laptop I get the ubituity-dm screen. I press Try Kubuntu and it takes me to the SDDM login screen. Autologin should work and trying the exact same USB drive on a different computer it does reliable autologin. It's also reported to work fine on Virtualbox. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1436952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448134] [NEW] Ubuntu 15.04 boot delay
Public bug reported: After upgrading to Ubuntu 15.04 I experience a mayor boot delay of one and half minutes. It does not happen when I boot with upstart in anvanced menu. systemd-analyze critical-chain gives me this: graphical.target @1min 37.987s └─multi-user.target @1min 37.987s └─kerneloops.service @1min 37.873s +15ms └─network-online.target @1min 37.873s └─network.target @1min 30.654s └─NetworkManager.service @1min 30.450s +202ms └─basic.target @1min 30.443s └─sockets.target @1min 30.443s └─acpid.socket @1min 30.443s └─sysinit.target @1min 30.441s └─networking.service @1.547s +363ms └─apparmor.service @1.436s +108ms └─local-fs.target @1.435s └─run-vmblock\x2dfuse.mount @1min 37.977s ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448134 Title: Ubuntu 15.04 boot delay Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 15.04 I experience a mayor boot delay of one and half minutes. It does not happen when I boot with upstart in anvanced menu. systemd-analyze critical-chain gives me this: graphical.target @1min 37.987s └─multi-user.target @1min 37.987s └─kerneloops.service @1min 37.873s +15ms └─network-online.target @1min 37.873s └─network.target @1min 30.654s └─NetworkManager.service @1min 30.450s +202ms └─basic.target @1min 30.443s └─sockets.target @1min 30.443s └─acpid.socket @1min 30.443s └─sysinit.target @1min 30.441s └─networking.service @1.547s +363ms └─apparmor.service @1.436s +108ms └─local-fs.target @1.435s └─run-vmblock\x2dfuse.mount @1min 37.977s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436952] Re: X crashes on some runs of Kubuntu live image returning in SDDM login
** Changed in: xorg (Ubuntu Vivid) Status: Incomplete = Opinion ** Changed in: xorg (Ubuntu Vivid) Status: Opinion = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1436952 Title: X crashes on some runs of Kubuntu live image returning in SDDM login Status in X.Org X server: New Status in xorg package in Ubuntu: Confirmed Status in xorg source package in Vivid: Confirmed Bug description: Running a Kubuntu vivid beta 2 live image on my laptop I get the ubituity-dm screen. I press Try Kubuntu and it takes me to the SDDM login screen. Autologin should work and trying the exact same USB drive on a different computer it does reliable autologin. It's also reported to work fine on Virtualbox. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1436952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447839] Re: Support dynamic mouse cursor icons
** Tags added: desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1447839 Title: Support dynamic mouse cursor icons Status in Mir: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: currently on the unity8 desktop windowed mode, the mouse remains in it's arrow form not prompting the user when it's on the edge of a window where the window can be rescaled. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1447839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1426588] Re: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x00007fa04bf00910 ***
I ran the test case with the package from vivid-proposed, and confirm that systemctl now stops crashing. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1426588 Title: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** Status in systemd: Won't Fix Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Bug description: root@file-control:~# systemctl disable vmware-USBArbitrator Synchronizing state for vmware-USBArbitrator.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d vmware-USBArbitrator defaults insserv: Service localfs has to be enabled to start service vmware-USBArbitrator insserv: exiting now! update-rc.d: error: insserv rejected the script header *** Error in `systemctl': double free or corruption (fasttop): 0x7f4ad5bff910 *** Aborted (core dumped) SRU TEST CASE = - Create a file /etc/init.d/broken with #!/bin/sh ### BEGIN INIT INFO # Provides: unknownservice # Required-Start: localfs # Required-Stop: localfs # Default-Start: 2 3 4 # Default-Stop: 0 6 # Short-Description: unknown service ### END INIT INFO true - Make it executable: sudo chmod 755 /etc/init.d/broken - Run sudo systemctl enable broken.service. This will show the double-free corruption. Notice that the insserv: Service localfs has to be enabled to start service unknownservice is an honest error message which must stay, as the init.d script is broken (it meant to say $local_fs presumably). ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu1 Uname: Linux 4.0.0-04rc1-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AssertionMessage: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** Date: Fri Feb 27 18:12:48 2015 ExecutablePath: /bin/systemctl InstallationDate: Installed on 2014-08-22 (189 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140730) MachineType: LENOVO 20349 ProcCmdline: systemctl disable vmware-USBArbitrator ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc1-generic root=/dev/mapper/fcntl-ubuntu ro rootflags=subvol=@ quiet splash init=/lib/systemd/systemd vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fa049a247a0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=optimized out, str=0x7fa049a24968 double free or corruption (fasttop), action=1) at malloc.c:4996 _int_free (av=optimized out, p=optimized out, have_lock=0) at malloc.c:3840 ?? () ?? () Title: systemctl assert failure: *** Error in `systemctl': double free or corruption (fasttop): 0x7fa04bf00910 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sbuild dmi.bios.date: 08/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1426588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field
** Bug watch removed: OpenOffice.org Issue Tracker #42985 http://qa.openoffice.org/issues/show_bug.cgi?id=42985 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince document viewer: Unknown Status in Poppler: Confirmed Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: Кириллица' To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Branch linked: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Confirmed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447243] Re: systemd crashes with Assertion 'current[*l + 1] == quotechars[0]' failed at ../src/shared/util.c:583 with invalid line break escapes
I ran the test case on the package from -proposed, and it works as expected now. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447243 Title: systemd crashes with Assertion 'current[*l + 1] == quotechars[0]' failed at ../src/shared/util.c:583 with invalid line break escapes Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: Fix Committed Bug description: Reproducer: - Boot current vivid amd64 VM - sudo add-apt-repository ppa:maas-maintainers/experimental - sudo apt update - sudo apt install isc-dhcp-server - sudo apt install maas-dhcp SRU TEST CASE (do this in a VM!) - Create a /lib/systemd/system/broken.service with the contents as in comment 7. Make sure that there is a trailing space after the true \ (Launchpad filtered that out in the comment!). - sudo systemctl status broken.service - This crashes pid 1 in vivid final, and should just complain a broken .service file with the fix. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 22 17:04:42 2015 ExecutablePath: /lib/systemd/systemd ExecutableTimestamp: 1429391580 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /sbin/init ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=6a708076-c5ee-4e4f-998a-4aa5ed4c3850 ro console=ttyS0 Signal: 6 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Activation of org.freedesktop.systemd1 timed out UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421684] Re: [scopes] Accessing preview in Apps scope is not intuitive
-- UX comment -- By default, tapping on a card opens the associated preview page. There are some exceptions to this rule and installed apps is one one of them. Currently, tapping on a card that displays an installed app opens the app and long pressing the card opens the preview where user can uninstall it (independently of the phone being online/offline mode). There’s an ongoing discussion about making direct activation the default. This will be part of the Scopes customisation project where we’ll specify a new card interactional model. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1421684 Title: [scopes] Accessing preview in Apps scope is not intuitive Status in Ubuntu UX bugs: Triaged Status in unity-scope-click package in Ubuntu: New Bug description: Hi! When the Ubuntu Phone is in offline mode, I can't browse my installed applications, then I can't uninstall. Please, allow a offline browse. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
