[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Utopic fix committed to git, thanks! I keep this open for trusty, but as it's neither a data loss nor critical bug and just a cosmetical corner case I keep it as low importance. You say since 3.13.0-16.36 which is trusty -- i. e. precise's kernel still has it as a module? So it seems to me that this doesn't affect precise at all. But even if it would, if such a cosmetical bug hasn't caused trouble in 2.5 years, it's certainly going to be fine for the other 1.5 years. ** Also affects: udev (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Utopic) Importance: Undecided Assignee: Dariusz Gadomski (dgadomski) Status: Confirmed ** Also affects: systemd (Ubuntu Utopic) Importance: Undecided Assignee: Dariusz Gadomski (dgadomski) Status: New ** Changed in: systemd (Ubuntu Utopic) Status: New = Fix Committed ** Changed in: systemd (Ubuntu Trusty) Status: New = Triaged ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided = Low ** No longer affects: udev (Ubuntu Utopic) ** No longer affects: udev (Ubuntu Trusty) ** Also affects: udev (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: udev (Ubuntu) Status: Confirmed = Invalid ** Changed in: udev (Ubuntu Precise) Status: New = Incomplete ** No longer affects: systemd (Ubuntu Precise) -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Incomplete Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 202861] [NEW] nautilus hangs after network disconnect
You have been subscribed to a public bug: Binary package hint: gvfs Release: Ubuntu Hardy amd64 Gvfs version 0.2.0.1-0ubuntu2 When using Nautilus to browse on a remote location using sftp it hangs after and while my network had a disconnection. Killing gvfs, gvfs-sftp and nautilus is the only solution. It should give an error that my network connection is unavailable instead. Steps to reproduce: * Start nautilus * Browse on a remove location using sftp * Disconnect your network * This causes nautilus to hang completely, killing gvfs, gvfs-sftp and nautilus is the only solution * After a reconnect it sometimes get working again, and sometimes remains dead. ** Affects: nautilus-cd-burner Importance: Medium Status: Fix Released ** Affects: gtk+3.0 (Ubuntu) Importance: Low Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Confirmed ** Affects: nautilus-cd-burner (Ubuntu) Importance: Medium Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Fix Released -- nautilus hangs after network disconnect https://bugs.launchpad.net/bugs/202861 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1302264] Re: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL
@Luis: That version (http://launchpadlibrarian.net/182673897/systemd_204-5ubuntu20.4_204-5ubuntu20.5.diff.gz) does not change anything related to this bug at all, so this sounds like a race condition and pure coincidence. However, you posted this to both here and bug 1309025 and both are already fixed/closed. If you still experience crashes, please report them as new bugs, as they are most certainly different. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1302264 Title: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL Status in “systemd” package in Ubuntu: Fix Released Bug description: Initially presents as a 'hang' during bootup. Checking the upstart logs it looks like systemd-logind is failing. I tried a few different approaches - and eventually found that installing cgmanager allowed the system to reach a x11 login checking into the logs now I continue to see errors: Removed session c1. cgmanager: cgm_remove for controller=blkio, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpu, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuacct, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuset, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=devices, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=freezer, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=hugetlb, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=memory, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=perf_event, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=systemd, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=blkio, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpu, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuacct, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuset, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=devices, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=freezer, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=hugetlb, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=memory, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=perf_event, cgroup_path=user/115.user, recursive=1 failed: invalid request Failed to issue method call: Unknown unit: autovt@tty2.service but the system seems to working now. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AssertionMessage: error.c:319: Assertion failed in nih_error_get: context_stack != NULL Date: Thu Apr 3 18:18:23 2014 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-03-24 (10 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140323) ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: systemd StacktraceTop: nih_error_get () from /lib/x86_64-linux-gnu/libnih.so.1 ?? () ?? () ?? () ?? () Title: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309025] Re: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL
@Luis: That version (http://launchpadlibrarian.net/182673897/systemd_204-5ubuntu20.4_204-5ubuntu20.5.diff.gz) does not change anything related to this bug at all, so this sounds like a race condition and pure coincidence. However, you posted this to both here and bug 1302264 and both are already fixed/closed. If you still experience crashes, please report them as new bugs, as they are most certainly different. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1309025 Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Fix Released Status in “systemd” source package in Utopic: Fix Released Bug description: SRU: Rationale: systemd-logind randomly crashes on random systems, usually with a similar traceback or most commonly with a corrupted one. We've identified a few problems in the patch, most of which can account for the symptoms people have seen and all of which being obviously correct bugfixes. Testcase: Get the fixes into utopic and trusty-proposed, wait for a week for new reports (here and on errors.ubuntu.com), if none were reported, push to -updates. While we know what we've fixed, actually reproducing the bug in the wild is notoriously difficult, we attempted various kind of stress tests over the past 2 months without much luck... Regression potential: All the fixes are very simple, very targeted and pretty obvious, so if we do end up breaking something else as the result of that, it's most likely another bug that was hidden behind incorrect behaviour. Any such bug should be easy to deal with or we can always revert to the current state (better the devil you know). === Original bug report === Occurred after a dist-upgrade, reboot and logging in. Any needed logs will be added later ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu20 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AssertionMessage: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL Date: Thu Apr 17 14:53:58 2014 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2012-10-08 (555 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121008) ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: TERM=linux PATH=(custom, no user) Signal: 6 SourcePackage: systemd StacktraceTop: cgmanager_list_children_sync () from /lib/x86_64-linux-gnu/libcgmanager.so.0 ?? () ?? () ?? () ?? () Title: systemd-logind assert failure: cgmanager-client.c:6322: Assertion failed in cgmanager_list_children_sync: proxy != NULL UpgradeStatus: Upgraded to trusty on 2013-10-26 (172 days ago) UserGroups: utah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1309025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 202861] Re: nautilus hangs after network disconnect
I am pretty sure the bug most of us are experiencing is https://bugzilla.gnome.org/show_bug.cgi?id=735953 which by the way was fixed in git. So I'm reassigning from gvfs to gtk+3.0 . The patch in comment 7: https://bug735953.bugzilla-attachments.gnome.org/attachment.cgi?id=285251 should really be adopted by distributors. ** Bug watch added: GNOME Bug Tracker #735953 https://bugzilla.gnome.org/show_bug.cgi?id=735953 ** Package changed: gvfs (Ubuntu) = gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/202861 Title: nautilus hangs after network disconnect Status in nautilus-cd-burner: Fix Released Status in “gtk+3.0” package in Ubuntu: Confirmed Status in “nautilus-cd-burner” package in Ubuntu: Fix Released Bug description: Binary package hint: gvfs Release: Ubuntu Hardy amd64 Gvfs version 0.2.0.1-0ubuntu2 When using Nautilus to browse on a remote location using sftp it hangs after and while my network had a disconnection. Killing gvfs, gvfs- sftp and nautilus is the only solution. It should give an error that my network connection is unavailable instead. Steps to reproduce: * Start nautilus * Browse on a remove location using sftp * Disconnect your network * This causes nautilus to hang completely, killing gvfs, gvfs-sftp and nautilus is the only solution * After a reconnect it sometimes get working again, and sometimes remains dead. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus-cd-burner/+bug/202861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1140716]
*** Bug 83661 has been marked as a duplicate of this bug. *** -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on,
[Touch-packages] [Bug 1140716]
Is there any ongoing development to fix this bug? I still see it with Linux hostname 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux And the latest intel drivers as provided by intel linux graphics installer from https://01.org/linuxgraphics/ Many times my system freezes few minutes after starting to watch a movie with vlc. I have my screen connected through a receiver (hdmi for audio + video) with the linux system. The probability for a freeze is higher when the hdmi receiver was powered of for some time before playing the movie than when I do a reboot and hdmi is always on. I'm happy to help with crashdumps as far as I'm able to collect them. -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10
[Touch-packages] [Bug 1140716]
(In reply to comment #183) I recommend configuring i915.semaphores=0. I did it and it doesn't freeze anymore. -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[Touch-packages] [Bug 1140716]
*** Bug 83783 has been marked as a duplicate of this bug. *** -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: Triaged Status in “linux” source package in Precise: Invalid Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “mesa” source package in Precise: Triaged Status in “linux” source package in Quantal: Invalid Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on,
[Touch-packages] [Bug 1368470] Re: Celllular and Wi-Fi Settings... options don't always display Settings
*** This bug is a duplicate of bug 1362017 *** https://bugs.launchpad.net/bugs/1362017 ** This bug has been marked a duplicate of bug 1362017 Focusing already-focused apps does not close indicators -- 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/1368470 Title: Celllular and Wi-Fi Settings... options don't always display Settings Status in “indicator-network” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Bug description: Tested on krillin ( rtm image #30 ) and mako ( rtm image #33 ). When I try tap the Cellular Settings... or Wi-Fi Settings... menu items in the network menu, I expect the menu to be dismissed, and the requested settings page displayed. Actual result, nothing appears to happen, although when the menu is dismissed manually, the correct settings page is revealed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Thanks Martin for taking a look. In my precise (12.04.5) install the default kernel is 3.13.0-32-generic, which is affected by the issue: $ grep FB_VESA /boot/config-3.13.0-32-generic CONFIG_FB_VESA=y In fact initially this has been reported by a CTS customer for precise. -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Incomplete Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296989] Re: libass outdated in Trusty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libass (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libass in Ubuntu. https://bugs.launchpad.net/bugs/1296989 Title: libass outdated in Trusty Status in “libass” package in Ubuntu: Confirmed Bug description: https://code.google.com/p/libass/ Currently, libass is at version 0.10.1, even though version 0.11.1 was already released a month ago. Major changes have happened since the 10.1 release for improving performance and quality drastically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libass/+bug/1296989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot
According to ofono guys this feature should have landed by today's
image. But it still does not work:
{ConnectionManager} [/ril_0] Attached = True
{ConnectionManager} [/ril_0] Bearer = umts
{Modem} [/ril_0] Powered = False
{Modem} [/ril_0] Online = False
{Modem} [/ril_0] Interfaces = []
{Modem} [/ril_0] Features = []
{Modem} [/ril_0] Powered = True
{Modem} [/ril_0] Interfaces = org.ofono.NetworkTime
{Modem} [/ril_0] Features = []
{Modem} [/ril_0] Manufacturer = Fake Manufacturer
{Modem} [/ril_0] Model = Fake Modem Model
{Modem} [/ril_0] Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
{Modem} [/ril_0] Serial = 354142060715150
{Modem} [/ril_0] Online = True
{Modem} [/ril_0] Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager
org.ofono.NetworkTime
{Modem} [/ril_0] Features = []
{VoiceCallManager} [/ril_0] EmergencyNumbers = 08 000 999 110 112 911 118 119
{Modem} [/ril_0] Interfaces = org.ofono.SimManager org.ofono.CallVolume
org.ofono.VoiceCallManager org.ofono.NetworkTime
{Modem} [/ril_0] Features = sim
{CallVolume} [/ril_0] Muted = False
{Modem} [/ril_0] Interfaces = org.ofono.RadioSettings org.ofono.SimManager
org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime
{Modem} [/ril_0] Features = rat sim
--
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/1332306
Title:
Hot-swapped SIMs should be detected and prompt user to reboot
Status in “indicator-network” package in Ubuntu:
Triaged
Status in “ofono” package in Ubuntu:
Fix Released
Bug description:
Our telephony stack doesn't support hot-swapping of SIM cards. If a
user hot-swaps a SIM, the telephony stack will become unusable.
The telephony-service should detect when this happens and display a
snap-decision informing the user that they need to restart their
device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1332306/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332306] Re: Hot-swapped SIMs should be detected and prompt user to reboot
According to ofono guys this feature should have landed by today's
image. But it still does not work:
{ConnectionManager} [/ril_0] Attached = True
{ConnectionManager} [/ril_0] Bearer = umts
{Modem} [/ril_0] Powered = False
{Modem} [/ril_0] Online = False
{Modem} [/ril_0] Interfaces = []
{Modem} [/ril_0] Features = []
{Modem} [/ril_0] Powered = True
{Modem} [/ril_0] Interfaces = org.ofono.NetworkTime
{Modem} [/ril_0] Features = []
{Modem} [/ril_0] Manufacturer = Fake Manufacturer
{Modem} [/ril_0] Model = Fake Modem Model
{Modem} [/ril_0] Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49
{Modem} [/ril_0] Serial = 354142060715150
{Modem} [/ril_0] Online = True
{Modem} [/ril_0] Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager
org.ofono.NetworkTime
{Modem} [/ril_0] Features = []
{VoiceCallManager} [/ril_0] EmergencyNumbers = 08 000 999 110 112 911 118 119
{Modem} [/ril_0] Interfaces = org.ofono.SimManager org.ofono.CallVolume
org.ofono.VoiceCallManager org.ofono.NetworkTime
{Modem} [/ril_0] Features = sim
{CallVolume} [/ril_0] Muted = False
{Modem} [/ril_0] Interfaces = org.ofono.RadioSettings org.ofono.SimManager
org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime
{Modem} [/ril_0] Features = rat sim
--
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/1332306
Title:
Hot-swapped SIMs should be detected and prompt user to reboot
Status in “indicator-network” package in Ubuntu:
Triaged
Status in “ofono” package in Ubuntu:
Fix Released
Bug description:
Our telephony stack doesn't support hot-swapping of SIM cards. If a
user hot-swaps a SIM, the telephony stack will become unusable.
The telephony-service should detect when this happens and display a
snap-decision informing the user that they need to restart their
device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1332306/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368593] [NEW] no funciona flash player
Public bug reported: no funciona flahs players desde que tengo Ubuntu 14 por favor respondame en español ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Sep 12 09:39:00 2014 DistUpgraded: 2014-04-19 10:33:48,184 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2400] InstallationDate: Installed on 2013-04-24 (506 days ago) InstallationMedia: LINUX 12.10 - Release i386 MachineType: CLEVO CO. W24xCZ ProcEnviron: LANGUAGE=es PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=696f463a-f386-4dc8-b6d9-7d298907db0d ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (145 days ago) dmi.bios.date: 12/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/18/2012:svnCLEVOCO.:pnW24xCZ:pvrNotApplicable:rvnCLEVOCO.:rnW24xCZ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W24xCZ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 12 08:34:13 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8684 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1368593 Title: no funciona flash player Status in “xorg” package in Ubuntu: New Bug description: no funciona flahs players desde que tengo Ubuntu 14 por favor respondame en español ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Sep 12 09:39:00 2014 DistUpgraded: 2014-04-19 10:33:48,184 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2400] InstallationDate: Installed on 2013-04-24 (506 days ago) InstallationMedia: LINUX 12.10 - Release i386 MachineType: CLEVO CO. W24xCZ ProcEnviron: LANGUAGE=es PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=696f463a-f386-4dc8-b6d9-7d298907db0d ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (145 days ago) dmi.bios.date: 12/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I'm still not fully convinced about the SRUs -- this might have a potential to break existing setups if they run custom kernels? It's ok to add the expectancy to build in vesafb for a new release (utopic), but not for existing stables? Or is it impossible to build vesafb as a module now? -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Ah right, that's the backported trusty kernels I figure (12.04.4 or later). ** Changed in: udev (Ubuntu Precise) Status: Incomplete = Triaged ** Changed in: udev (Ubuntu Precise) Importance: Undecided = Low -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329584] Re: the label in the panel menu can't change to Ubuntu Kylin Desktop
** Changed in: ubuntukylin Assignee: handsome_feng (445865575-b) = (unassigned) ** Changed in: ubuntukylin Assignee: (unassigned) = Anthony Wong (anthonywong) -- 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/1329584 Title: the label in the panel menu can't change to Ubuntu Kylin Desktop Status in Ubuntu Kylin: Confirmed Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: The desktop name Ubuntu Desktop can't change to Ubuntu Kylin Desktop,it is not convenient for us to change it to our Special symbol. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1329584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
** Summary changed: - scope images do not load in HSDPA or 3G + QNetworkAccessManager doesn't support roaming on Ubuntu ** No longer affects: unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: New Status in The Savilerow project: New Status in “qtubuntu” package in Ubuntu: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
No bluez-simple-agent 'solution' for me. cinnamon-bluetooth useless. Blueman useless. All options greyed out. bluetooth-wizard useless. Bluewho useless. Mint 17 64bit fresh install. Microsoft Sculp Mobile keyboard + working universal bluetooth dongle. Traceback (most recent call last): File /usr/bin/bluez-simple-agent, line 117, in module path = manager.DefaultAdapter() File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 70, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python2.7/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter More like this in the forum: http://forums.linuxmint.com/viewtopic.php?t=177748p=921515 http://forums.linuxmint.com/viewtopic.php?f=49t=168079 -- 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/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in “bluez” package in Ubuntu: Fix Released Status in “gnome-bluetooth” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Triaged Status in “gnome-bluetooth” source package in Precise: Triaged Status in “bluez” source package in Trusty: In Progress Status in “gnome-bluetooth” source package in Trusty: In Progress Bug description: When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363075] Re: Background does not display rotated imaged as rotated
** Changed in: unity8 (Ubuntu) Status: Opinion = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1363075 Title: Background does not display rotated imaged as rotated Status in “gallery-app” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Invalid Bug description: Steps: 1. Take a picture of something at an incorrect orientation and larger than desired (pic1.png) 2. Open the picture in the gallery, use the editor to rotate and crop the pic (pic2.png) 3. Go to system settings and choose the pic in the backgound. Effect: The pic is displayed in the background as cropped but not rotated (pic3.png and pic4.png) Expected: The pic is display rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1363075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
if the scopes are confined then we need to change the QPA plugin to use connectivity-service instead of NM to get the networking status changes. Well, this doesn't only affect scopes. It also affects apps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: New Status in The Savilerow project: New Status in “qtubuntu” package in Ubuntu: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368287] Re: [Apps switcher] Different drag behaviour between items that can and cannot be closed
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1368287
Title:
[Apps switcher] Different drag behaviour between items that can and
cannot be closed
Status in Ubuntu UX bugs:
New
Status in “unity8” package in Ubuntu:
New
Bug description:
Drag to close is a great feature in application spread. In user
testing it had a great success rate and users understood it and knew
how to use it. The problem is the Dash item that's part of the spread
but is the only item which cannot be closed. Currently the Dash item
drag movement is similar to the movement of the items that actually
can be closed.
We want to make Dash drag different from others by restricting the
movement while still responding to user's drag.
Desired solution
Use restriction algorithm for dash item so that it moves along the
drag but soon starts restricting the movement indicating that it's an
item that cannot be closed.
Here is quite nice elastic function that can be used:
function elastic( currentPosition, limit ) {
return limit * ( 1 - Math.pow( ( limit - 1 ) / limit, currentPosition ) )
}
Where:
limit is the highest value that ever can be returned by the function
current position is the value to be limited
It's a bit hard to describe the parameters, therefore I created a prototype
that should explain the usage.
Find it from: lp:~willow-team/willow/elasticRestriction
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1368287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366134] Re: [regression] Mir FTBFS with g++-4.8 [error: ISO C++ forbids casting between pointer-to-function and pointer-to-object]
** Also affects: mir/0.7
Importance: Undecided
Status: New
** Changed in: mir/0.7
Milestone: None = 0.7.2
** Changed in: mir/0.7
Status: New = Fix Committed
** Changed in: mir/0.7
Importance: Undecided = High
** Changed in: mir/0.7
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1366134
Title:
[regression] Mir FTBFS with g++-4.8 [error: ISO C++ forbids casting
between pointer-to-function and pointer-to-object]
Status in Mir:
Fix Committed
Status in Mir 0.7 series:
Fix Committed
Status in “mir” package in Ubuntu:
New
Bug description:
/home/camako/workspace/mir-dev/src/platform/options/default_configuration.cpp:
In function ‘void {anonymous}::ensure_loaded_with_rtld_global()’:
/home/camako/workspace/mir-dev/src/platform/options/default_configuration.cpp:77:67:
error: ISO C++ forbids casting between pointer-to-function and
pointer-to-object [-Werror]
dladdr(reinterpret_castvoid*(ensure_loaded_with_rtld_global), info);
...
/home/camako/workspace/mir-dev/src/client/default_connection_configuration.cpp:
In function ‘void {anonymous}::ensure_loaded_with_rtld_global()’:
/home/camako/workspace/mir-dev/src/client/default_connection_configuration.cpp:57:67:
error: ISO C++ forbids casting between pointer-to-function and
pointer-to-object [-Werror]
dladdr(reinterpret_castvoid*(ensure_loaded_with_rtld_global), info);
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1366134/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362619] Re: unity8-dash hangs in scopes backend
I have this on krillin, today image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1362619 Title: unity8-dash hangs in scopes backend Status in “unity8” package in Ubuntu: Incomplete Status in “unity-scopes-api” package in Ubuntu RTM: Incomplete Status in “unity-scopes-shell” package in Ubuntu RTM: Incomplete Status in “unity8” package in Ubuntu RTM: Incomplete Bug description: This is a forced crash, it was unity8-dash hanging. I got it twice on startup, once during normal operation. Most suspect are threads 12 to 22. A `restart unity8-dash` it works again, so this is a race of some kind. ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.00+14.10.20140825.3-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf CurrentDesktop: Unity Date: Thu Aug 28 13:19:11 2014 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1408985173 InstallationDate: Installed on 2014-08-27 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140827-202410) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: unity8 Stacktrace: #0 0xb6221022 in poll () at ../sysdeps/unix/syscall-template.S:81 No locals. #1 0xb5d460c0 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) StacktraceTop: poll () at ../sysdeps/unix/syscall-template.S:81 ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368517] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::
** Branch linked: lp:~jpakkane/indicator-network/snapguard -- 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/1368517 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:notify::Notification::show Status in “indicator-network” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20140904-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bdcb312681ba14a98809fdd4b953888e591b24a6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368612] Re: upowerd crashed with SIGSEGV in strlen()
*** This bug is a duplicate of bug 1334827 *** https://bugs.launchpad.net/bugs/1334827 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1334827, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1368612/+attachment/4202086/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202088/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202089/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202090/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202091/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202092/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1368612/+attachment/4202093/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1334827 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1368612 Title: upowerd crashed with SIGSEGV in strlen() Status in “upower” package in Ubuntu: New Bug description: Ubuntu 14.10 Beta 1 Nvidia drivers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 11 02:51:54 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-08-29 (13 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140826) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f1dd9a2d4fa strlen+42:movdqu (%rax),%xmm12 PC (0x7f1dd9a2d4fa) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %xmm12 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upower StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:106 __GI___strdup (s=0x0) at strdup.c:41 plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 lockdownd_client_new_with_handshake () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 Title: upowerd crashed with SIGSEGV in strlen() 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/1368612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368615] [NEW] Alt+Shift+Tilde (~) should switch windows in reverse order
Public bug reported: There's a GUI convention for navigation: adding the Shift modifier to a hotkey is typically interpreted as 'do the same thing as the hotkey, except in the other direction'. Control+Tab+Shift may visit the previous Web browser tab. Control+Z+Shift may redo the last edit, and so on. Ubuntu offers Alt+Tab for switching between windows, and Alt+Tilde for switching between windows of the same application. Ubuntu also offers Alt+Shift+Tab for switching between windows in reverse order. However, Ubuntu, or some odd dependency, neglected to make a corresponding Alt+Shift+Tilde hotkey for switching between windows of the same application in reverse order. Please add this missing hotkey. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: alt alt+tab hotkey mac shift shortcut tab tilde -- 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/1368615 Title: Alt+Shift+Tilde (~) should switch windows in reverse order Status in “unity” package in Ubuntu: New Bug description: There's a GUI convention for navigation: adding the Shift modifier to a hotkey is typically interpreted as 'do the same thing as the hotkey, except in the other direction'. Control+Tab+Shift may visit the previous Web browser tab. Control+Z+Shift may redo the last edit, and so on. Ubuntu offers Alt+Tab for switching between windows, and Alt+Tilde for switching between windows of the same application. Ubuntu also offers Alt+Shift+Tab for switching between windows in reverse order. However, Ubuntu, or some odd dependency, neglected to make a corresponding Alt+Shift+Tilde hotkey for switching between windows of the same application in reverse order. Please add this missing hotkey. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1368615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368620] [NEW] Hard to tell which dock apps are running / not running
Public bug reported: The colorized background of dock icons makes it harder for me to tell which apps are running. I would prefer that the dock icon backgrounds remain the same color regardless of icon content, and that the same color is used across apps to indicate a running app. This would make it easier at a glance for me to tell which apps are running and which are not. Similarly, some applications have rather large dock icons, such as the Wunderlist browser app. When this happens, there is very little room for a background color, so any such change in the dock icon when the app launches / quits is barely noticeable. In the future, could Ubuntu scale down all dock icons to the same size, allowing for some padding for background colors? ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: dock icon icons -- 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/1368620 Title: Hard to tell which dock apps are running / not running Status in “unity” package in Ubuntu: New Bug description: The colorized background of dock icons makes it harder for me to tell which apps are running. I would prefer that the dock icon backgrounds remain the same color regardless of icon content, and that the same color is used across apps to indicate a running app. This would make it easier at a glance for me to tell which apps are running and which are not. Similarly, some applications have rather large dock icons, such as the Wunderlist browser app. When this happens, there is very little room for a background color, so any such change in the dock icon when the app launches / quits is barely noticeable. In the future, could Ubuntu scale down all dock icons to the same size, allowing for some padding for background colors? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1368620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368622] Re: upowerd crashed with SIGSEGV in strlen()
*** This bug is a duplicate of bug 1334827 *** https://bugs.launchpad.net/bugs/1334827 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1334827, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1368622/+attachment/4202095/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202097/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202098/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202099/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202100/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202101/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1368622/+attachment/4202102/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1334827 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1368622 Title: upowerd crashed with SIGSEGV in strlen() Status in “upower” package in Ubuntu: New Bug description: My Ubuntu did not boot up properly when my external hard disk was connected. When I removed it, it booted up properly. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Fri Sep 12 11:44:40 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-09-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0x7ffa5883f4fa strlen+42:movdqu (%rax),%xmm12 PC (0x7ffa5883f4fa) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %xmm12 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upower StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:106 __GI___strdup (s=0x0) at strdup.c:41 plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 lockdownd_client_new_with_handshake () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 Title: upowerd crashed with SIGSEGV in strlen() 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/1368622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Trusty had vesafb build in the kernel from the very first release, so I believe the assumption is safe here. Well no, one could still run a self-built kernel. So I think for an SRU it would be safer to not drop the script, but instead do some 2/dev/null to quiesce the error. -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
do some 2/dev/null to quiesce the error. or if that's not possible (because it's the kernel who spits out errors, but that's unlikely), it could also do if modinfo vesafb /dev/null 21; then modprobe -q vesafb; fi -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368519] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::
The backtrace only shows worker thread, meaning the exception is thrown and leaked fully inside dbus-cpp. That makes this a bug in dbus-cpp, not indicator-network. ** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** 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/1368519 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_system_error Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20140904-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2976077aa05c26721c6567aef8790b0cf5ec1ac contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368519] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::
** Changed in: dbus-cpp (Ubuntu) Status: New = Confirmed ** Changed in: dbus-cpp (Ubuntu) Importance: Undecided = Critical ** Changed in: dbus-cpp (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) -- 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/1368519 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_system_error Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20140904-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2976077aa05c26721c6567aef8790b0cf5ec1ac contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while disabled in status bar
There are actually three separated issues discussed there. First one is the original reported problem where URfkill was not updating killswitch states properly. That has been fixed. The second one is about the icon which actually is nm-no-connection which unfortunately looks like a wifi icon. Actually looking at spec it says that if there is no wifi nothing should be shown in the indicator, but that is not possible due to the fact that we might end up in a situation where there is no icons shown by the indicator and then you would not be able to pull down the indicator. I need to ping MPT about it. https://bugs.launchpad.net/indicator-network/+bug/1340206 Thirdly there is the toggle switch bug which already has a bug of it's own. https://bugs.launchpad.net/indicator-network/+bug/1336715 So to summarize, the original bug is fixed and thus it can be closed as Fix Released. ** Changed in: network-manager (Ubuntu) Status: Incomplete = Invalid ** Changed in: urfkill (Ubuntu) Status: Incomplete = Fix Released ** 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/1355776 Title: WiFi shown as enabled in indicator while disabled in status bar Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Status in “urfkill” package in Ubuntu: Fix Released Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. # system-image-cli -i current build number: 171 device name: mako channel: ubuntu-touch/utopic-proposed last update: 2014-08-05 07:56:23 version version: 171 version ubuntu: 20140805 version device: 20140728.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360582] Re: Can't manually install clicks Signature verification error since #205
The last piece of this was fixed a couple of days ago: phablet-tools (1.1+14.10.20140909-0ubuntu1) utopic; urgency=low [ Michael Vogt ] * click-buddy: adding --allow-untrusted to the pkcon install-local call. -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 09 Sep 2014 20:43:43 + ** Changed in: phablet-tools (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1360582 Title: Can't manually install clicks Signature verification error since #205 Status in PackageKit: Confirmed Status in “click” package in Ubuntu: Fix Released Status in “phablet-tools” package in Ubuntu: Fix Released Status in “qtcreator-plugin-ubuntu” package in Ubuntu: Fix Released Bug description: See mailing list thread at https://lists.launchpad.net/ubuntu- phone/msg09607.html Since image #205 I can't install click packages using click-buddy pkcon install-local. Changed click-buddy to use adb $ADBOPTS shell click install --user=$DEVICE_USER --allow-unauthenticated /tmp/$click which worked for me, but dunno if that's the right thing to do. alan@deep-thought:~/phablet/code/coreapps⟫ adb push com.ubuntu.music_1.3.597_all.click /tmp 2560 KB/s (401406 bytes in 0.153s) alan@deep-thought:~/phablet/code/coreapps⟫ phablet-shell start: Job is already running: ssh /home/alan/.ssh/known_hosts updated. Original contents retained as /home/alan/.ssh/known_hosts.old 9 KB/s (399 bytes in 0.040s) Warning: Permanently added '[localhost]:' (RSA) to the list of known hosts. Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako armv7l) * Documentation: https://help.ubuntu.com/ Last login: Fri Aug 22 23:53:19 2014 from localhost.localdomain phablet@ubuntu-phablet:~$ pkcon install-local /tmp/com.ubuntu.music_1.3.597_all.click Installing files [=] Finished [=] Installing files [=] Waiting for authentication[=] Starting [=] Finished [=] Fatal error: /tmp/com.ubuntu.music_1.3.597_all.click failed to install. Cannot install /tmp/com.ubuntu.music_1.3.597_all.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed. To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1360582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Actually I think the second approach would be better, since the error comes not from the message (which is redirected to upstart logs anyway), but from the return code of the script. Unfortunately, according to my knowledge, the upstart scripts are executed with the -e switch making it stop with a failure on a first failed call. This ties our hands a bit as we cannot have any failing commands there (even those we expect to fail in a particular configuration) and makes our potential script less flexible. So in any case we would be interested in not returning anything other than 0. A commonly used work-around for this limitation could be used like this: modprobe -q -b vesafb || true This would load the module if available, but would remain quiet (-q switch to modprobe with additional || true) if the module is not there. -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
Can we close the ubuntu-rtm/upstart task now? https://launchpad.net /ubuntu-rtm/+source/upstart shows 1.13.2~rtm-0ubuntu1 (a spurious version due to CI Train thinking it owns upstart upstream releases, but the effect should be the same). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: Fix Released Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Status in “cgmanager” package in Ubuntu RTM: Fix Released Status in “upstart” package in Ubuntu RTM: Triaged Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368668] [NEW] [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture
Public bug reported: Right edge compound gesture has two phases. During the second phase all the recent applications stack together in to the apps spread. There is a second phase commit threshold value after which this stacking happens. Currently when this commit threshold has been exceeded user loses control over the gesture. There is no way to go back and the UI doesn't react to further finger movement to left. We want user to be in control also after the second commit line. RIght edge gesture progress is explained and broken into pieces in this spec: https://docs.google.com/a/canonical.com/document/d/1FC_-5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# There is already a bug about reversibility (movement back to right) after second commit line (#1355284). So this bug is to fix the non- responsiveness after second phase commit line when user moves finger towards left edge. Steps to repro: 1. Start right edge swipe 2. keep finger pressed and drag to left until you reach the point when apps spread is formed 3. keep still finger pressed and move finger towards left Current behaviour: No visual feedback Expected behaviour: Applications should start moving to left and stack the way they do when they're dragged to left in normal spread use case ** Affects: ubuntu-ux Importance: Medium Assignee: Vesa Rautiainen (vesar) Status: Fix Committed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Assignee: (unassigned) = Vesa Rautiainen (vesar) -- 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/1368668 Title: [Apps switcher] Visual feedback of user's finger movement needed throughout the gesture Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: Right edge compound gesture has two phases. During the second phase all the recent applications stack together in to the apps spread. There is a second phase commit threshold value after which this stacking happens. Currently when this commit threshold has been exceeded user loses control over the gesture. There is no way to go back and the UI doesn't react to further finger movement to left. We want user to be in control also after the second commit line. RIght edge gesture progress is explained and broken into pieces in this spec: https://docs.google.com/a/canonical.com/document/d/1FC_-5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# There is already a bug about reversibility (movement back to right) after second commit line (#1355284). So this bug is to fix the non- responsiveness after second phase commit line when user moves finger towards left edge. Steps to repro: 1. Start right edge swipe 2. keep finger pressed and drag to left until you reach the point when apps spread is formed 3. keep still finger pressed and move finger towards left Current behaviour: No visual feedback Expected behaviour: Applications should start moving to left and stack the way they do when they're dragged to left in normal spread use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361132] Re: [lockscreen] new design is not consistent with our UX patterns
This will be addressed with updated visuals. ** Summary changed: - New lockscreen design is not consistent with our UX patterns + [lockscreen] new design is not consistent with our UX patterns -- 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/1361132 Title: [lockscreen] new design is not consistent with our UX patterns Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: The new lockscreen design features an X at the bottom of the screen, http://i.imgur.com/JORXscB.png What does the X mean? It appears that if you click on it it goes back to the welcome screen. I find the X triggering an action that is not hinted, someone could guess the X is to clear the passcode (at this point it would better be placed next to the passcode entry). If we want to quit the lockscreen, we might want to put a back button where we usually have in our designs: next to the top left of the header (otherwise we should making it clearer with a button with Close label). Either way, I find the placement unfortunate next to the emergency call button too. On SIM PIN, there's at least a symmetrical ✓ on the right. In the case of SIM PIN, this X also results in Skip and not Cancel, so it's even more confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1361132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362518] Re: Badge missing from System Settings icon on dash when update is available
- High because the absence may delay people installing important Ubuntu Touch updates. ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Assignee: (unassigned) = Matthew Paul Thomas (mpt) -- 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/1362518 Title: Badge missing from System Settings icon on dash when update is available Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r203 1. Wait until software updates are available. 2. Look at the System Settings icon in the Dash. What you see: It appears as normal. What you should see: Wherever the System Settings icon appears, it should have a badge with the number of updates available. https://wiki.ubuntu.com/SoftwareUpdates#Prompting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1362518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357548] Re: Empty PIN/password/passphrase field appears to contain 4 characters
** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1357548 Title: Empty PIN/password/passphrase field appears to contain 4 characters Status in Ubuntu UI Toolkit: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: minor interrelated issues probably needs design input 1) visual inconsistency of the pin text box prompt shows 4 bullets implying needing 4 characters, but the passphrase is text box is empty 2) selecting the pin text box prompt, the bullets remain, and don't respond to delete, they don't disappear once typing begins (i would think dissappear on text box selection) 3) having a show password would be nice Desired resolution: Passcode/password fields should never contain bullets when you haven't entered anything in them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1357548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368670] [NEW] Simplify 'Manage Dash' area
Public bug reported: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368670 Title: Simplify 'Manage Dash' area Status in “unity8” package in Ubuntu: New Bug description: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363557] Re: Password textfield missing when unlocking
*** This bug is a duplicate of bug 1311316 *** https://bugs.launchpad.net/bugs/1311316 ** This bug has been marked a duplicate of bug 1311316 After locking screen there is no input field to type password for unlock -- 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/1363557 Title: Password textfield missing when unlocking Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Intermittently the password textfield will be completely missing from the unlock screen. The user's name appears and the background graphic which usually surrounds the textfield is present, but the textfield itself is missing. This typically happens when multiple users are logged into the computer. Unfortunately I do not have reliable steps to repeat the problem. There are a number of workarounds. Sometimes I can use ctrl-alt-f7 or -f8 to switch to another user, log that user out and get to the log in screen with all the users listed. Then the original user can log in. Sometimes it is necessary to switch to ctrl-alt-f1 and restart lightdm. Sometimes I need to log into the machine remotely and restart lightdm. Sometimes all of these fail and it is necessary to restart the computer. If there is something I could do to gather more information the next the computer is in this state, I would be happy to do so. Unfortunately I cannot run ubuntu-bug while the problem is exhibited, as there is no access to the GUI. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 Candidate: 7.2.2+14.04.20140714-0ubuntu1.1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The unlock screen would contain a textfield to accept the user's password. 4) What happened instead The unlock screen contained no place to enter the user's password. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,imgpng,move,place,animation,vpswitch,grid,session,resize,snap,gnomecompat,workarounds,mousepoll,unitymtgrabhandles,wall,expo,ezoom,fade,scale,unityshell] CurrentDesktop: Unity Date: Sat Aug 30 22:16:21 2014 InstallationDate: Installed on 2014-05-25 (97 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368677] [NEW] [Apps switcher] Move commit points toward right to make spread more accessible
Public bug reported: In our user testing users often failed to access the spread via long right edge swipe. We want to make spread a bit more accessible by moving second phase commit point few grid units to right. Not to affect the overall functionality and experience the right thing to do is to make first phase reveal phase shorter which then automatically moves both first phase and second phase commit point same amount towards right. See the spec for detailed descriptions of different gesture phases: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# Desired solution: Shorten the first phase reveal by 4 gu Since the 4gu value is just an estimate and might need refining the result should be approved with design team before committing. ** Affects: ubuntu-ux Importance: Low Assignee: Vesa Rautiainen (vesar) Status: Fix Committed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Assignee: (unassigned) = Vesa Rautiainen (vesar) -- 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/1368677 Title: [Apps switcher] Move commit points toward right to make spread more accessible Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: New Bug description: In our user testing users often failed to access the spread via long right edge swipe. We want to make spread a bit more accessible by moving second phase commit point few grid units to right. Not to affect the overall functionality and experience the right thing to do is to make first phase reveal phase shorter which then automatically moves both first phase and second phase commit point same amount towards right. See the spec for detailed descriptions of different gesture phases: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit# Desired solution: Shorten the first phase reveal by 4 gu Since the 4gu value is just an estimate and might need refining the result should be approved with design team before committing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368677/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368670] Re: Simplify 'Manage Dash' area
** Description changed: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure + + + Additional UX Testing Report findings addressed by the redesign: + + + Poor discoverability and comprehension of scopes - The use of labelings that do not include the word 'scope'/'scopes' + + Lack of visual distinctions between apps and scopes in the 'manage + dash' screen + + Undefined relationship between apps and scopes + + Search function does not help the discovery of scopes + + No dedicated place for adding scopes on the dash + + Poor memorability in locating the' manage dash' screen again + + The impact of making a scope favourite is unclear + + Lack of indication of the nature of the scopes under 'all' tab on + 'manage dash' + + Navigation between manage dash and apps scope was difficult + + Expect to see categorises instead of content -- 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/1368670 Title: Simplify 'Manage Dash' area Status in “unity8” package in Ubuntu: New Bug description: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure Additional UX Testing Report findings addressed by the redesign: Poor discoverability and comprehension of scopes - The use of labelings that do not include the word 'scope'/'scopes' Lack of visual distinctions between apps and scopes in the 'manage dash' screen Undefined relationship between apps and scopes Search function does not help the discovery of scopes No dedicated place for adding scopes on the dash Poor memorability in locating the' manage dash' screen again The impact of making a scope favourite is unclear Lack of indication of the nature of the scopes under 'all' tab on 'manage dash' Navigation between manage dash and apps scope was difficult Expect to see categorises instead of content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368680] [NEW] Dash pagination graphic should remain static when swiping between favourites.
Public bug reported: Pagination graphic should remain fixed in place when swiping between favourites contained within the dash. 'Dot' used to communicate which favourite is currently being viewed should be more visible (switch colour from Dark Grey to Orange colour used for highlights, etc): See here for more info on dash pagination states: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/home/dash-pagination UX Testing Report finding recommendation: No incentive to discover scopes beyond the apps scope. Lack of strong visual cues to hint swiping from the apps scope to discover more scopes on the right. In the SURU divider pagination pattern (as currently used by the Dash), change the selected colour from orange to white. When the Scopes slide, the SURU divider portion of the screen should not slide (it should remain static). The state of the 'dot' pagination pattern should of course change. Keeping the SURU divider static should make the change to the pagination pattern more noticeable. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- 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/1368680 Title: Dash pagination graphic should remain static when swiping between favourites. Status in “unity8” package in Ubuntu: New Bug description: Pagination graphic should remain fixed in place when swiping between favourites contained within the dash. 'Dot' used to communicate which favourite is currently being viewed should be more visible (switch colour from Dark Grey to Orange colour used for highlights, etc): See here for more info on dash pagination states: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/home/dash-pagination UX Testing Report finding recommendation: No incentive to discover scopes beyond the apps scope. Lack of strong visual cues to hint swiping from the apps scope to discover more scopes on the right. In the SURU divider pagination pattern (as currently used by the Dash), change the selected colour from orange to white. When the Scopes slide, the SURU divider portion of the screen should not slide (it should remain static). The state of the 'dot' pagination pattern should of course change. Keeping the SURU divider static should make the change to the pagination pattern more noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359802] Re: header's timestamp can take a minute to update after resume from suspend
Not really sure how the suspend works, but maybe installing signal handler for SIG_CONT maybe to force a refresh would work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1359802 Title: header's timestamp can take a minute to update after resume from suspend Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: Not the same as the bug #1328646, where the clock fell completely out- of-sync and never came back. This bug has a milder but similar symptom, the clock is set to update once per minute, so after resume from suspend it will still show the wrong time until that periodic update timer triggers. In addition to the periodic update, indicator-datetime should listen to powerd's Wakeup signal, or better yet, to com.canonical.Unity.Screen's DisplayPowerStateChange signal http://bazaar.launchpad.net/~unity-system-compositor-team/unity- system-compositor/trunk/view/head:/src/dbus_screen.cpp#L100 to ensure that it makes the timestamp up-to-date whenever the screen is turned on. Reported by ogra and dednick in #ubuntu-touch. *edit:* also discussed by kgunn72 and aacid @ https://code.launchpad.net/~nick- dedekind/unity8/lp1328646/+merge/231335 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1359802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368663] Re: - Bottom edge from lockscreen should open the content hub so the user can pick a wallpaper
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368663 Title: - Bottom edge from lockscreen should open the content hub so the user can pick a wallpaper Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: - Bottom edge from lockscreen should open the content hub so the user can pick a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368662] Re: - Remove the 'folded corner' that indicates when an app is pinned
** Summary changed: - - Remove the 'folded corner' that indicates when an app is pinned (not needed anymore because all apps in the Launcher other than the currently focused app will be pinned) + - Remove the 'folded corner' that indicates when an app is pinned ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368662 Title: - Remove the 'folded corner' that indicates when an app is pinned Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: - Remove the 'folded corner' that indicates when an app is pinned (not needed anymore because all apps in the Launcher other than the currently focused app will be pinned) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368660] Re: - implement the updated visual design whereby the quicklist is positioned above the user's fingers
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368660 Title: - implement the updated visual design whereby the quicklist is positioned above the user's fingers Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: - implement the updated visual design whereby the quicklist is positioned above the user's fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368688] [NEW] Inconsistence between /etc/init and /etc/init.d files
Public bug reported:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
The first one was executed from /etc/init/isc-dhcp-server.conf and second
from /etc/init.d/isc-dhcp-server.
Looking inside init/isc-dhcp-server.conf I found:
~~
respawn
script
. /etc/default/isc-dhcp-server
..
exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
But in init.d/isc-dhcp-server startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z $DHCPD_PID ]; then
DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
fi
DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
..
case $1 in
start)
test_config
log_daemon_msg Starting $DESC $NAME
start-stop-daemon --start --quiet --pidfile $DHCPD_PID \
--exec /usr/sbin/dhcpd -- \
-q $OPTIONS -cf $DHCPD_CONF -pf $DHCPD_PID
$INTERFACES
~~
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1368688
Title:
Inconsistence between /etc/init and /etc/init.d files
Status in “isc-dhcp” package in Ubuntu:
New
Bug description:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
The first one was executed from /etc/init/isc-dhcp-server.conf and second
from /etc/init.d/isc-dhcp-server.
Looking inside init/isc-dhcp-server.conf I found:
~~
respawn
script
. /etc/default/isc-dhcp-server
..
exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
But in init.d/isc-dhcp-server startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z $DHCPD_PID ]; then
DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
fi
DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
..
case $1 in
start)
test_config
log_daemon_msg Starting $DESC $NAME
start-stop-daemon --start --quiet --pidfile $DHCPD_PID \
--exec /usr/sbin/dhcpd -- \
-q $OPTIONS -cf $DHCPD_CONF -pf $DHCPD_PID
$INTERFACES
~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1368688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368659] Re: Pop out effect to show that Launcher icon is in reorder state
** Summary changed: - - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user that the icon is now in the reorder state + Pop out effect to show that Launcher icon is in reorder state ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368659 Title: Pop out effect to show that Launcher icon is in reorder state Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user that the icon is now in the reorder state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368658] Re: - Implement new visual designs for Snap Decisions and other notifications
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368658 Title: - Implement new visual designs for Snap Decisions and other notifications Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: The poor discoverabiltiy of the text field for snap decision (lack of contrast) One participant discovered the snap decision, however, after he clicked on the message button, he could not locate the text field immeditately as it was blended into the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files
** Description changed:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
-
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
-
The first one was executed from /etc/init/isc-dhcp-server.conf and second
from /etc/init.d/isc-dhcp-server.
Looking inside init/isc-dhcp-server.conf I found:
~~
respawn
script
-. /etc/default/isc-dhcp-server
- ..
- exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
+ . /etc/default/isc-dhcp-server
+ ..
+ exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
-
But in init.d/isc-dhcp-server startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z $DHCPD_PID ]; then
- DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
+ DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
fi
DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
- ..
+ ..
case $1 in
- start)
- test_config
- log_daemon_msg Starting $DESC $NAME
- start-stop-daemon --start --quiet --pidfile $DHCPD_PID \
- --exec /usr/sbin/dhcpd -- \
- -q $OPTIONS -cf $DHCPD_CONF -pf $DHCPD_PID
$INTERFACES
+ start)
+ test_config
+ log_daemon_msg Starting $DESC $NAME
+ start-stop-daemon --start --quiet --pidfile $DHCPD_PID \
+ --exec /usr/sbin/dhcpd -- \
+ -q $OPTIONS -cf $DHCPD_CONF -pf $DHCPD_PID
$INTERFACES
~~
+
+
+ So obivous is to either change init script to NOT use hardcoded path to PID
file and use $DHCP_PID (from /etc/default/isc-dhcp-server, which is sourced
inside this script), or at least change it to default one: /var/run/dhcpd.pid
+
+ OR
+
+ change init.d script to fallback to /run/dhcp-server/dhcpd.pid instead
+ of /var/run/dhcpd.pid
+
+ P.S. /var/run is a link to /run
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1368688
Title:
Inconsistence between /etc/init and /etc/init.d files
Status in “isc-dhcp” package in Ubuntu:
New
Bug description:
After upgrade Ubuntu server from 12.04 LTS to 14.04 LTS (with
do-release-upgrade) I found a strange behavior in /var/log/messages from
isc-dhcp-server. It had doubled DHCPREQUESTS/OFFERS/ACKs... It was like:
~~
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
dhcpd: DHCPDISCOVER from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPREQUEST for 192.168.1.102 (10.112.1.252) from 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
DHCPACK on 192.168.1.102 to 00:0b:82:27:be:d1 via eth0
~~
Futher investigation show that there was actually two dhcpd processes:
~~
dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcp-server/dhcpd.pid
/usr/sbin/dhcpd -q -cf /etc/dhcp/dhcpd.conf -pf /var/run/dhcpd.pid
~~
The first one was executed from /etc/init/isc-dhcp-server.conf and second
from /etc/init.d/isc-dhcp-server.
Looking inside init/isc-dhcp-server.conf I found:
~~
respawn
script
. /etc/default/isc-dhcp-server
..
exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf /run/dhcp-server/dhcpd.pid
-cf $CONFIG_FILE $INTERFACES
~~
As you can see path to PID file is hardcoded.
But in init.d/isc-dhcp-server startup script:
~~
# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
if [ -z $DHCPD_PID ]; then
DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
fi
DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
..
case $1 in
start)
test_config
log_daemon_msg Starting $DESC $NAME
start-stop-daemon --start --quiet --pidfile $DHCPD_PID
[Touch-packages] [Bug 1320563] Re: invoke-rc.d: initscript systemd-logind, action start failed.
Bytemark VPS was using 3.2.60. Swapped it out for 3.4.92 and the package correctly configures. Thanks for the pointer. Iain -- 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/1320563 Title: invoke-rc.d: initscript systemd-logind, action start failed. Status in “systemd” package in Ubuntu: Invalid Bug description: Impossible to do sudo apt-get upgrade, the console output is ubuntu@ip-10-184-21-111:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Setting up libpam-systemd:i386 (204-5ubuntu20.2) ... start: Job failed to start invoke-rc.d: initscript systemd-logind, action start failed. dpkg: error processing package libpam-systemd:i386 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libpam-systemd:i386 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu20.2 ProcVersionSignature: User Name 2.6.32-312.24-ec2 2.6.32.27+drm33.12 Uname: Linux 2.6.32-312-ec2 i686 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: i386 Date: Sat May 17 23:24:50 2014 Ec2AMI: ami-ab8592c2 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1b Ec2InstanceType: m1.medium Ec2Kernel: aki-fec63697 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-19 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1320563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Right, protecting this with || true sounds perfectly fine and safe for an SRU. -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368696] [NEW] - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user th
Public bug reported: - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user that the icon is now in the reorder state ** Affects: unity8 (Ubuntu) Importance: Undecided Assignee: Estibaliz Landa Torres (estilanda) Status: New ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Estibaliz Landa Torres (estilanda) -- 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/1368696 Title: - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user that the icon is now in the reorder state Status in “unity8” package in Ubuntu: New Bug description: - when a user unlocks an icon from the Launcher by long pressing on the icon, the icon should 'pop out' with a drop shadow giving a 3d effect to inform the user that the icon is now in the reorder state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348110] Re: Please enter a number label is too big for some translations
Seems the German translation has been updated too already. At least German fits nicely now. -- 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/1348110 Title: Please enter a number label is too big for some translations Status in Dialer app for Ubuntu Touch: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Here's a screenshot from German translation. I guess the font size should be reduced in such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1348110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346355] Re: 14.04 power-cog does not turn red when restart is needed
Greg, there are two misunderstandings here. First, it is not always true that The power-cog is where users go to shutdown/restart their computer. Some people only ever put their computer to sleep and wake it up again, by closing and opening the lid; they don't shut down or restart unless explicitly prompted, so futzing with the cog icon would be meaningless to them. Second, it is not correct that the user needs to go to the Power-Cog to accomplish the restart. There's a much more obvious Restart Now button in the restart-required alert. If Software Updater is crashing somehow before it displays that alert on your parents' computer, please report that as a separate bug. Thanks! -- 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/1346355 Title: 14.04 power-cog does not turn red when restart is needed Status in The Session Menu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In ubuntu 12.04 the power-cog turned red when a reboot/restart was needed. This was a helpful feature because it informed users that they needed to restart the computer. But this helpful indicator is gone in 14.04 and it has resulted in me never remembering to restart my computer because there is no helpful feedback from ubuntu that a restart is needed. In 14.04, I will perform an update and a popup tells me a Restart is needed but I usually select to restart-later because I am in the middle of working. By the the time I am done working I have forgotten that a restart is needed. Later when I am working again a popup occurs informing me that a restart is needed (but again I am in the middle of working so I don't restart). Bottom line: when the power-cog turned red, it reminded me that I needed to restart the computer. When I finished my work I look up and see the red power-cog and Oh yeah, I need to restart. Now is a good time. In 14.04 this doesn't happen. Instead I'm perpetually bugged by a popup (which is useless because it's never a good time to restart when it pops up). The red power-cog was a much BETTER design choice. The removal of the power-cog turning red has negatively affected the management of ubuntu updates and it should be fixed so that it behaves like 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1346355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368695] [NEW] [Greeter] Greeter should be dismissed only via an edge gesture
Public bug reported: - Greeter should only be dismissable via an edge gesture - When the user interacts with the greeter, the greeter should inform the user about how to perform an edge gesture. - Also remove the Slide to unlock text. **This item is to be designed, prototyped and tested before implementation. A bug report created for transparency reasons. ** Affects: ubuntu-ux Importance: Wishlist Assignee: Vesa Rautiainen (vesar) Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-ux Importance: Undecided = Wishlist ** Changed in: ubuntu-ux Assignee: (unassigned) = Vesa Rautiainen (vesar) ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368695 Title: [Greeter] Greeter should be dismissed only via an edge gesture Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: - Greeter should only be dismissable via an edge gesture - When the user interacts with the greeter, the greeter should inform the user about how to perform an edge gesture. - Also remove the Slide to unlock text. **This item is to be designed, prototyped and tested before implementation. A bug report created for transparency reasons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368711] [NEW] - toggle switch animation needs to be faster
Public bug reported: - toggle switch animation needs to be faster ** Affects: unity8 (Ubuntu) Importance: Undecided Assignee: Estibaliz Landa Torres (estilanda) Status: New ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Estibaliz Landa Torres (estilanda) -- 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/1368711 Title: - toggle switch animation needs to be faster Status in “unity8” package in Ubuntu: New Bug description: - toggle switch animation needs to be faster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368707] [NEW] - invistigate resolution
Public bug reported: - invistigate resolution ** Affects: unity8 (Ubuntu) Importance: Undecided Assignee: Estibaliz Landa Torres (estilanda) Status: New ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Estibaliz Landa Torres (estilanda) -- 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/1368707 Title: - invistigate resolution Status in “unity8” package in Ubuntu: New Bug description: - invistigate resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368675] Re: No Wi-Fi on Nexus 4 (Mako)
** Description changed: Ubuntu Touch 14.10 r235, LG Nexus 4 1. Open the Network menu. 2. Navigate to System Settings Wi-Fi. What happens: - 1. The Network menu contains only the word Empty! (That wording is bug - 1350952, but this isn't about the wording.) + 1. The Network menu contains only the word Empty! No Wi-Fi switch, no + Wi-Fi Settings item, no Cellular Settings item, nothing. (The Empty! + wording is bug 1350952, but this isn't about the wording.) 2. The screen contains only Previous networks and (as long as bug 1365960 isn't fixed) Other network. What should happen: - 1. A Wi-Fi switch is available. - 2. A Wi-Fi switch is available. + 1. A Wi-Fi switch is present. + 2. A Wi-Fi switch is present. -- 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/1368675 Title: No Wi-Fi on Nexus 4 (Mako) Status in “network-manager” package in Ubuntu: New Bug description: Ubuntu Touch 14.10 r235, LG Nexus 4 1. Open the Network menu. 2. Navigate to System Settings Wi-Fi. What happens: 1. The Network menu contains only the word Empty! No Wi-Fi switch, no Wi-Fi Settings item, no Cellular Settings item, nothing. (The Empty! wording is bug 1350952, but this isn't about the wording.) 2. The screen contains only Previous networks and (as long as bug 1365960 isn't fixed) Other network. What should happen: 1. A Wi-Fi switch is present. 2. A Wi-Fi switch is present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366854] Re: bluetooth will not enable stays blocked
** Package changed: bluez (Ubuntu) = ubuntu -- 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/1366854 Title: bluetooth will not enable stays blocked Status in Ubuntu: New Bug description: Since installation of 14.04.1 I've been trying to get bluetooth working. Under preferences bluetooth says it's disabled. So I did $rfkill list all, and that showed me that asus bluetooth is soft blocked. I did an $rfkill unblock all, and nothing. I have tried everything listed here: http://askubuntu.com/questions/521190 /bluetooth-disabled-asus-g750jm and the person answering my questions suggested I report it as a bug because I'm out of options. I'm running a ROG ASUS G750JM it's a fairly new gaming laptop, the modem installation went fine through the install process of ubuntu. But bluetooth hasn't worked yet. I'm not sure what package it is it's probably bluez and it's up to date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1366854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366391] Re: re-prompted for already-known password when switching networks
Hi Antii, Having taken a look at them, I don't think they are actually relevant since they are identical apart from the obvious fields (id, uuid, ssid, psk). I'll try and do further tests over the w/e with both networks... -- 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/1366391 Title: re-prompted for already-known password when switching networks Status in “indicator-network” package in Ubuntu: Incomplete Bug description: When I re-connect to a known network, I am prompted for the WPA2 password. However, clicking cancel then successfully connects to this network! This is only happening for one of my networks. Not currently sure why since the other main network I use is also WPA2 protected and I'm not prompted for that networks password. I wonder if the re-prompt only occurs if the user attempts to connect to a different network to the first-joined network on boot (can't test atm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful
I think we're confusing three issues here. First, the Transfers menu should show something more appropriate, like No active transfers or something, when there are none. That requires design work. Second, the Notifications list should show something more appropriate, like None or something, when there are none. That requires separate design work. Third, some code in the indicator system itself is inserting the word Empty! into empty indicator menus and should not. For example, right now I'm getting Empty! in, of all places, the Network menu (bug 1368675). That should never happen ... but when it *does* happen, for whatever reason, it should be something more elegant, like a silhouetted error icon, or even nothing at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
I have uploaded new patches updated as agreed. -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Adding new SRU proposal for Precise. ** Patch removed: systemd_204-5ubuntu20.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff ** Patch removed: udev_175-0ubuntu9.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201483/+files/udev_175-0ubuntu9.7.debdiff ** Patch added: udev_175-0ubuntu9.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202152/+files/udev_175-0ubuntu9.7.debdiff -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Adding new SRU proposal for Trusty. ** Patch added: systemd_204-5ubuntu20.7.debdiff https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202154/+files/systemd_204-5ubuntu20.7.debdiff -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: Starting load fallback graphic devices: [fail] [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I experience this issue on a single-screen environment; however, we frequently have multiple users logged in and so are using multiple virtual terminals. Sometimes it is possible to switch another VT and have that user log out and that alleviates the issue. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364999] Re: Blocked password prompt in Unity lock screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- 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/1364999 Title: Blocked password prompt in Unity lock screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes when I lock the screen, I can't get in again. I have to press Ctrl+Alt+F1 and kill X or reboot to get in again. The problem is actually that I can't type in the password because the text input field is no longer there. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Sep 3 14:25:34 2014 InstallationDate: Installed on 2014-07-10 (55 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1364999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368720] [NEW] I am having problems when booting for keyboard and mouse to be detected Also my screen is resolving to wide.
Public bug reported: I am having problems when booting for keyboard and mouse to be detected unless I use an earlier safe boot and repair in Grub (34 not 35). Also my screen is only able to use resolutions that are too flat and wide. IE circles are flat ovals instead of round. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Sep 12 13:54:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0344] InstallationDate: Installed on 2014-08-13 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=13f60426-40a3-4dd2-9ceb-619f75343e4d ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: SGP4510H.86A.0118.2009.0622.1056 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DP45SG dmi.board.vendor: Intel Corporation dmi.board.version: AAE27733-405 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSGP4510H.86A.0118.2009.0622.1056:bd06/22/2009:svn:pn:pvr:rvnIntelCorporation:rnDP45SG:rvrAAE27733-405:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 12 13:26:11 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1368720 Title: I am having problems when booting for keyboard and mouse to be detected Also my screen is resolving to wide. Status in “xorg” package in Ubuntu: New Bug description: I am having problems when booting for keyboard and mouse to be detected unless I use an earlier safe boot and repair in Grub (34 not 35). Also my screen is only able to use resolutions that are too flat and wide. IE circles are flat ovals instead of round. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Sep 12 13:54:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0344] InstallationDate: Installed on 2014-08-13 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=13f60426-40a3-4dd2-9ceb-619f75343e4d ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: SGP4510H.86A.0118.2009.0622.1056 dmi.board.asset.tag: To be
[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful
Third, some code in the indicator system itself is inserting the word Empty! into empty indicator menus and should not Indeed, unity8 is putting that in while the menu has not been loaded yet: http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/qml/Panel/Indicators/DefaultIndicatorPage.qml#L200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319489] Re: Google callendar events often not shown in indicator panel
I just realized that this bug was reported *before* google changed the http handling, so the bug reporter might have been experiencing a different problem. Nevertheless, the problem exists now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1319489 Title: Google callendar events often not shown in indicator panel Status in “evolution-data-server” package in Ubuntu: Confirmed Bug description: I use Ubuntu 14.04, evolution-data-server is version 3.10.4-0ubuntu1. In the online account settings I added my Google account and selected the option to synchronise the callendar with the evolution-data- server. Expected behavior: When I click on the time in the top panel, I should be able to see my next events from my Google callendar. What happens: Very often there are no eventy shown. Only after restarting the system I can see the upcoming events again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1319489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342858] Re: old click packages are not always cleaned out
** Changed in: click (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1342858 Title: old click packages are not always cleaned out Status in “click” package in Ubuntu: Fix Committed Bug description: /var/lib/apparmor/clicks still has a lot of symlinks pointing to security manifests for click packages that are no longer installed. I haven't verified this, but I think it might have something to do with preinstalled packages and system-image updates. Eg: $ ls -1 /var/lib/apparmor/clicks/*json | wc -l 157 $ click list | wc -l 85 $ sudo click list | wc -l 19 None of the symlinks in /var/lib/apparmor/clicks are dangling, so while this doesn't actively harm the system AFAICT, the 70+ additional and unneeded apparmor profiles means a slower first boot when policy regeneration is required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1342858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362518] Re: Badge missing from System Settings icon on dash when update is available
** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Low = Medium -- 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/1362518 Title: Badge missing from System Settings icon on dash when update is available Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: Ubuntu 14.10 r203 1. Wait until software updates are available. 2. Look at the System Settings icon in the Dash. What you see: It appears as normal. What you should see: Wherever the System Settings icon appears, it should have a badge with the number of updates available. https://wiki.ubuntu.com/SoftwareUpdates#Prompting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1362518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368746] [NEW] Recent tab displays contacts behind the top bar
Public bug reported: Mako with MultiROM #239 The recent tab in the dialler app initially shows the contacts as they should, but shortly thereafter the contacts list moves all the way to the top of the screen resulting in the top most contact being hidden beneath the top bar. This is very annoying and has caused me to call back to the wrong person several times today. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1368746 Title: Recent tab displays contacts behind the top bar Status in “dialer-app” package in Ubuntu: New Bug description: Mako with MultiROM #239 The recent tab in the dialler app initially shows the contacts as they should, but shortly thereafter the contacts list moves all the way to the top of the screen resulting in the top most contact being hidden beneath the top bar. This is very annoying and has caused me to call back to the wrong person several times today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1368746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368675] Re: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '')
** Attachment removed: Output of /usr/share/ofono/scripts/list-modems https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368675/+attachment/4202229/+files/output.txt -- 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/1368675 Title: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '') Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Confirmed Bug description: Ubuntu Touch 14.10 r235, LG Nexus 4 1. Open the Network menu. 2. Navigate to System Settings Wi-Fi. What happens: 1. The Network menu contains only the word Empty! No Wi-Fi switch, no Wi-Fi Settings item, no Cellular Settings item, nothing. (The Empty! wording is bug 1350952, but this isn't about the wording.) 2. The screen contains only Previous networks and (as long as bug 1365960 isn't fixed) Other network. What should happen: 1. A Wi-Fi switch is present. 2. A Wi-Fi switch is present. phablet@ubuntu-phablet:~$ /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service ModemManager::ModemManager() void SimUnlockDialog::Private::reset() Unknown Interface: org.ofono.NetworkTime void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: Mode org::ofono::Interface::NetworkRegistration::Status org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '' Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368670] Re: Simplify 'Manage Dash' area
** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Medium -- 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/1368670 Title: Simplify 'Manage Dash' area Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: UX Testing Report: Replace the current bottom edge screens with the simpler Complete list of Scopes design. New Manage Dash design can be found here: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/scope-structure-navigation/my-feeds-structure Additional UX Testing Report findings addressed by the redesign: Poor discoverability and comprehension of scopes - The use of labelings that do not include the word 'scope'/'scopes' Lack of visual distinctions between apps and scopes in the 'manage dash' screen Undefined relationship between apps and scopes Search function does not help the discovery of scopes No dedicated place for adding scopes on the dash Poor memorability in locating the' manage dash' screen again The impact of making a scope favourite is unclear Lack of indication of the nature of the scopes under 'all' tab on 'manage dash' Navigation between manage dash and apps scope was difficult Expect to see categorises instead of content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368675] Re: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '')
** Attachment added: Output of /usr/share/ofono/scripts/list-modems https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368675/+attachment/4202230/+files/output.txt -- 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/1368675 Title: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '') Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Confirmed Bug description: Ubuntu Touch 14.10 r235, LG Nexus 4 1. Open the Network menu. 2. Navigate to System Settings Wi-Fi. What happens: 1. The Network menu contains only the word Empty! No Wi-Fi switch, no Wi-Fi Settings item, no Cellular Settings item, nothing. (The Empty! wording is bug 1350952, but this isn't about the wording.) 2. The screen contains only Previous networks and (as long as bug 1365960 isn't fixed) Other network. What should happen: 1. A Wi-Fi switch is present. 2. A Wi-Fi switch is present. phablet@ubuntu-phablet:~$ /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service ModemManager::ModemManager() void SimUnlockDialog::Private::reset() Unknown Interface: org.ofono.NetworkTime void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: Mode org::ofono::Interface::NetworkRegistration::Status org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '' Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362133] Re: Rebooting after disabling wifi leaves wifi in wrong state (enabled but doesn't show networks)
The output of nmcli is this: nmcli d DEVICE TYPE STATE /ril_1 gsm disconnected /ril_0 gsm disconnected wlan0 802-11-wireless unavailable The top bar icon shows that wifi is off but indicator-network shows it to be on. -- 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/1362133 Title: Rebooting after disabling wifi leaves wifi in wrong state (enabled but doesn't show networks) Status in “indicator-network” package in Ubuntu: New Bug description: Steps to reproduce: 1.) Open the network indicator 2.) Toggle the Wi-Fi switch to 'Off' 3.) Reboot the device 4.) Open the network indicator Expected result: Wi-Fi is either disabled and shows no networks, or is enabled and shows networks Actual result: Wi-Fi is enabled and shows no networks. Toggling it on and off returns it to normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1362133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368749] [NEW] Bluetooth pairing not working on all devices
Public bug reported: Mako with MultiROM, utopic r235 There ar, a few bluetooth devices that still don't work together with Ubuntu Touch. These devices work perfectly well when booting the phone as Android. The devices that fails to connect for me are BlueAnt Supertooth 3 (http://www.myblueant.com/shop/us/products/st3.php#related) and My Volvo car bluetooth system, both with Bluetooth version 2.0 specifications. With BlueAnt Ubuntu can discover the unit and attempts to connect, opening a pairing dialogue with the digits . Confirming the pin code (which is correct) doesn't do anything, my Ubuntu phone is not recognized by BlueAnt and won't show as a connected device in the phone's bluetooth settings, but shows up under Connect other device followed by ... The bluetooth indicator, however, shows as connected. Moreover, the indicator remains lit even after turning BlueAnt off and toggling Bluetooth off/on in the phone settings. With My Volvo Car, pairing works differently. The bluetooth system in the car searches for devices and shows Nexus 4 and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. ** Affects: ubuntu-ui-toolkit (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-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368749 Title: Bluetooth pairing not working on all devices Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Mako with MultiROM, utopic r235 There ar, a few bluetooth devices that still don't work together with Ubuntu Touch. These devices work perfectly well when booting the phone as Android. The devices that fails to connect for me are BlueAnt Supertooth 3 (http://www.myblueant.com/shop/us/products/st3.php#related) and My Volvo car bluetooth system, both with Bluetooth version 2.0 specifications. With BlueAnt Ubuntu can discover the unit and attempts to connect, opening a pairing dialogue with the digits . Confirming the pin code (which is correct) doesn't do anything, my Ubuntu phone is not recognized by BlueAnt and won't show as a connected device in the phone's bluetooth settings, but shows up under Connect other device followed by ... The bluetooth indicator, however, shows as connected. Moreover, the indicator remains lit even after turning BlueAnt off and toggling Bluetooth off/on in the phone settings. With My Volvo Car, pairing works differently. The bluetooth system in the car searches for devices and shows Nexus 4 and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1368749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368748] [NEW] The screen disappears after lock/unlock
Public bug reported: Credential screen is gone after locking/unlocking the phone. Test case - Go to System Settings Accounts. - Click on Add account. - Click on Ubuntu One. - With the credentials screen in foreground, lock the phone. - Unlock. Expected result - Credential screen appears. Actual result - Ubuntu One Credential screen is gone. - Accounts screen appears instead, and the Ubuntu One option is disabled. - Going back to System Settings and returning to Accounts doesn't show again the window. ** Affects: ubuntuone-credentials (Ubuntu) Importance: Undecided Status: New ** Tags: rtm14 touch ** Summary changed: - The screen disappear after lock/unlock + The screen disappears after lock/unlock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1368748 Title: The screen disappears after lock/unlock Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: Credential screen is gone after locking/unlocking the phone. Test case - Go to System Settings Accounts. - Click on Add account. - Click on Ubuntu One. - With the credentials screen in foreground, lock the phone. - Unlock. Expected result - Credential screen appears. Actual result - Ubuntu One Credential screen is gone. - Accounts screen appears instead, and the Ubuntu One option is disabled. - Going back to System Settings and returning to Accounts doesn't show again the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1368748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368680] Re: Dash pagination graphic should remain static when swiping between favourites.
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368680 Title: Dash pagination graphic should remain static when swiping between favourites. Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: Pagination graphic should remain fixed in place when swiping between favourites contained within the dash. 'Dot' used to communicate which favourite is currently being viewed should be more visible (switch colour from Dark Grey to Orange colour used for highlights, etc): See here for more info on dash pagination states: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/home/dash-pagination UX Testing Report finding recommendation: No incentive to discover scopes beyond the apps scope. Lack of strong visual cues to hint swiping from the apps scope to discover more scopes on the right. In the SURU divider pagination pattern (as currently used by the Dash), change the selected colour from orange to white. When the Scopes slide, the SURU divider portion of the screen should not slide (it should remain static). The state of the 'dot' pagination pattern should of course change. Keeping the SURU divider static should make the change to the pagination pattern more noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368675] Re: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '')
This is about ofono setting an invalid value to the NetworkRegistration Status property. The reason why indicator-network seems to crash here is that I'm intentionally throwing an exception that nobody will catch and cause the service to generate an apport report so that: - A) if the indicator is not handling all the valid values coming from ofono we need to know about it - B) to catch exactly these kind of API violations coming from our ofono implementation. ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New = Invalid ** Changed in: indicator-network (Ubuntu) Status: New = Invalid ** Changed in: ofono (Ubuntu) Status: New = Incomplete ** Changed in: ofono (Ubuntu) Status: Incomplete = Confirmed ** Changed in: ofono (Ubuntu) Importance: Undecided = Critical -- 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/1368675 Title: No Wi-Fi on Nexus 4 (org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '') Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Confirmed Bug description: Ubuntu Touch 14.10 r235, LG Nexus 4 1. Open the Network menu. 2. Navigate to System Settings Wi-Fi. What happens: 1. The Network menu contains only the word Empty! No Wi-Fi switch, no Wi-Fi Settings item, no Cellular Settings item, nothing. (The Empty! wording is bug 1350952, but this isn't about the wording.) 2. The screen contains only Previous networks and (as long as bug 1365960 isn't fixed) Other network. What should happen: 1. A Wi-Fi switch is present. 2. A Wi-Fi switch is present. phablet@ubuntu-phablet:~$ /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service ModemManager::ModemManager() void SimUnlockDialog::Private::reset() Unknown Interface: org.ofono.NetworkTime void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: Mode org::ofono::Interface::NetworkRegistration::Status org::ofono::Interface::NetworkRegistration::str2status(std::string): Unknown status '' Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1368675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368751] [NEW] [enhancement] allow MTP access for authenticated computers
Public bug reported: In accordance with https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData, MTP currently refuses to show any folders when connecting the device to a system and the device's screen is locked (good). A nice future enhancement might be to do something similar to what is planned with adb-- using a certificate or token for each system the device connects to. Eg, it might look something like this: 1. Janet plugs in a locked device to her new laptop 2. MTP checks to see if this system (the new laptop) is known to the device 3. Since it is not, MTP checks the state of the screensaver and sees that it is locked, so refuses to export any directories 4. Janet unlocks the screen on the device and the files are exported to her laptop 5. Meanwhile on the device, MTP prompts Janet with: Detected new system. Unconditionally export MTP files to this system in the future? [ ] yes [ ] no 6. Janet answers 'yes' and MTP adds Janet's new laptop to its database of known devices 7. Janet performs file transfers via MTP, then unplugs the device and goes out to dinner, taking a lot of fun pictures 8. Janet returns home and plugs her locked device into her laptop 9. MTP checks to see if this system (the new laptop) is known to the device 10. Since Janet answered 'yes' in step '6', the files are exported to her laptop (without having to unlock the screen) and she can copy her fun pictures to her laptop If Janet answered 'no' in step '6', after performing step '9', MTP would proceed to step '3' instead of '10'. This probably requires design for the user interactions. Eg, perhaps it would be good to remember if the user answered 'no' in step '5'. Also, it would be good to be able to revoke systems from the database of known devices. This is not for RTM. This is not a security requirement. This is for UX. ** Affects: mtp (Ubuntu) Importance: Undecided Status: New ** Description changed: In accordance with https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData, MTP currently refuses to show any folders when connecting the device to - a system and the device's screen is locked. (good). A nice future + a system and the device's screen is locked (good). A nice future enhancement might be to do something similar to what is planned with adb-- using a certificate or token for each system the device connects to. Eg, it might look something like this: 1. Janet plugs in a locked device to her new laptop 2. MTP checks to see if this system (the new laptop) is known to the device 3. Since it is not, MTP checks the state of the screensaver and sees that it is locked, so refuses to export any directories 4. Janet unlocks the screen on the device and the files are exported to her laptop 5. MTP then prompts Janet with: - Detected new system. Unconditionally export MTP files to this system in the future? - [ ] yes [ ] no + Detected new system. Unconditionally export MTP files to this system in the future? + [ ] yes [ ] no 6. Janet answers 'yes' and MTP adds Janet's new laptop to its database of known devices 7. Janet performs file transfers via MTP, then unplugs the device and goes out to dinner, taking a lot of fun pictures 8. Janet returns home and plugs her locked device into her laptop 9. MTP checks to see if this system (the new laptop) is known to the device 10. Since Janet answered 'yes' in step '6', the files are exported to her laptop (without having to unlock the screen) If Janet answered 'no' in step '6', after performing step '9', MTP would proceed to step '3' instead of '10'. This probably requires design for the user interactions. Eg, perhaps it would be good to remember if the user answered 'no' in step '5'. Also, it would be good to be able to revoke systems from the database of known devices. This is not for RTM. This is not a security requirement. This is for UX. ** Description changed: In accordance with https://wiki.ubuntu.com/SecurityAndPrivacySettings/ProtectingUserData, MTP currently refuses to show any folders when connecting the device to a system and the device's screen is locked (good). A nice future enhancement might be to do something similar to what is planned with adb-- using a certificate or token for each system the device connects to. Eg, it might look something like this: 1. Janet plugs in a locked device to her new laptop 2. MTP checks to see if this system (the new laptop) is known to the device 3. Since it is not, MTP checks the state of the screensaver and sees that it is locked, so refuses to export any directories 4. Janet unlocks the screen on the device and the files are exported to her laptop - 5. MTP then prompts Janet with: + 5. Meanwhile on the device, MTP prompts Janet with: Detected new system. Unconditionally export MTP files to this system in the future? [ ] yes [ ] no 6. Janet
[Touch-packages] [Bug 1368680] Re: Dash pagination graphic should remain static when swiping between favourites.
The problem with this is that is that when you start swiping to the sides, the divider line doesn't necessarily have to be aligned with that of the other scope, it only comes into view a moment after you started swiping, which might mean the pagination could overflow onto the other scope's header. On top of that the dividers can have wildly different colours, we'd need assets that are certain to work well on all kinds of backgrounds. Can we please have some visual/motion exploration for this? There currently isn't a static place anywhere in the dash right now. -- 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/1368680 Title: Dash pagination graphic should remain static when swiping between favourites. Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: Pagination graphic should remain fixed in place when swiping between favourites contained within the dash. 'Dot' used to communicate which favourite is currently being viewed should be more visible (switch colour from Dark Grey to Orange colour used for highlights, etc): See here for more info on dash pagination states: https://sites.google.com/a/canonical.com/unity-8-dash-rtm-1/home/dash-pagination UX Testing Report finding recommendation: No incentive to discover scopes beyond the apps scope. Lack of strong visual cues to hint swiping from the apps scope to discover more scopes on the right. In the SURU divider pagination pattern (as currently used by the Dash), change the selected colour from orange to white. When the Scopes slide, the SURU divider portion of the screen should not slide (it should remain static). The state of the 'dot' pagination pattern should of course change. Keeping the SURU divider static should make the change to the pagination pattern more noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358328] Re: Add optional avatar to scope reviews preview widget
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = James Mulholland (jamesjosephmulholland) -- 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/1358328 Title: Add optional avatar to scope reviews preview widget Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: I'd like to use the reviews widget for each facebook comment (in a preview) in order to include each commenter's FB profile pic as an avatar. Saviq suggested the reviews widget should therefor have an optional avatar. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1358328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367804] Re: initial account after creation transfers back to the settings app
** Branch linked: lp:~mardy/ubuntu-system-settings-online- accounts/lp1367804 -- 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/1367804 Title: initial account after creation transfers back to the settings app Status in Online Accounts setup for Ubuntu Touch: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Triaged Bug description: STEPS: 1. Open Settings 2. Click on accounts 3. Select any account 4. Complete the account setup EXPECTATION: I expect to be transferred back to the main accounts page showing the newly created account. ACTUAL: Instead I am returned to the main Settings app page and the online accounts is completely closed. Opening the accounts page again I see the account I created. This only ever happens on the first account and it doesn't matter which account you choose to setup first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1367804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342151] Re: [Indicators] Silent mode control in the indicator
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = James Mulholland (jamesjosephmulholland) -- 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/1342151 Title: [Indicators] Silent mode control in the indicator Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: Should the indicator expose the control for silent mode for easy access? Implementing in settings now but would like to leverage a common implementation -- I've attached a wireframe which shows an additional setting in the sound indicator for turning on and off silent mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1342151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234982] Re: [osk] Keyboard does not auto-hide when no longer needed
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = Giorgio Venturi (giorgio-venturi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1234982 Title: [osk] Keyboard does not auto-hide when no longer needed Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-keyboard” package in Ubuntu: Invalid Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When I have entered the requisite data in a form or text field in an application, and then scroll and click on some other UI element which does not require text entry, the keyboard does not automatically go away. Instead, I must swipe down to close the keyboard, which is very annoying, especially when the keyboard is on top of Flickable elements. Having the keyboard auto-hide when it is no longer needed would be a great improvement to the user experience, as would possibly an explicit close button visible on the keyboard itself. Desired solution: Auto-hide behaviour should be handled by the application as different use cases would require different auto-hide behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1234982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303633] Re: [snapdecision.pinlock] no way to trigger the error haptic feedback
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = James Mulholland (jamesjosephmulholland) -- 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/1303633 Title: [snapdecision.pinlock] no way to trigger the error haptic feedback Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Fix Released Status in “indicator-network” package in Ubuntu: New Status in “unity8” package in Ubuntu: Fix Released Bug description: We need an additional action to signal the dialog that there was an error and to trigger the haptic shaking. The action has to carry a parameter that contains the text to show during the shaking. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1303633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355422] Re: [notifications] Can't dismiss notification bubbles
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1355422 Title: [notifications] Can't dismiss notification bubbles Status in Ubuntu UX bugs: Fix Committed Status in Server and client library for desktop notifications in Unity: New Status in “unity-notifications” package in Ubuntu: New Status in “unity8” package in Ubuntu: In Progress Bug description: On a phone with accounts setup for twitter, facebook and 2x google accounts I get a fair number of notifications. Often times these notifications appear while I'm actually using the phone. This presents issues in multiple areas:- * If I'm in the dash I am blocked from using the search function because a notification covers the search button * If I'm in the dash and already searching, having typed something, I'm blocked from seeing what I'm typing by the notification * In apps I can't go back because the notification blocks the button You get the idea. Basically notifications slow me down, because I have to wait for them to disappear. I'd like to be able to dismiss them. On iOS you swipe up which is indicated with a horizontal bar to grab and swipe away. --- Desired solution We've added in the latest specification for notifications bubbles (or clickable notifications) the ability to dismiss a notification via swiping left to right. Link to the spec: https://docs.google.com/a/canonical.com/document/d /1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz-oeM/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350952] Re: [Indicators] replace the text Empty! with something more useful
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: Invalid Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318812] Re: [osk] no way to remove user added dictionary words
** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1318812 Title: [osk] no way to remove user added dictionary words Status in Ubuntu Keyboard: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: when spell checking is enabled, any word the user types that is not recognized gets added to the user dictionary (I think). The problem is once a word gets added there is no way to delete it and it always shows up on the word ribbon, whether you want it or not. We should be more selective when adding words (i.e. if you type asdafadfadsfadsfadsfadsf that gets added). We can address that in another bug. For this bug, I think we need to provide the user with a way to remove words they added to the dictionary. One idea: press and hold the word on the word ribbon would produce an x button which when pressed would remove the word from the dictionary. This would be consistent with how users close apps, delete bookmarks, etc. -- Desired solution: Design specified here - section 'custom words': https://wiki.ubuntu.com/LanguageAndText To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1318812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368711] Re: - toggle switch animation needs to be faster
** Package changed: unity8 (Ubuntu) = ubuntu-ui-toolkit (Ubuntu) ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1368711 Title: - toggle switch animation needs to be faster Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: - toggle switch animation needs to be faster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368707] Re: - invistigate resolution
** Package changed: unity8 (Ubuntu) = ubuntu-ux -- 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/1368707 Title: - invistigate resolution Status in Ubuntu UX bugs: New Bug description: - invistigate resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368708] Re: Home button Long swipe from left edge should return the user to the Apps Scope
*** This bug is a duplicate of bug 1355359 *** https://bugs.launchpad.net/bugs/1355359 ** This bug has been marked a duplicate of bug 1355359 Overview should close on left edge and Ubuntu button in launcher -- 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/1368708 Title: Home button Long swipe from left edge should return the user to the Apps Scope Status in “unity8” package in Ubuntu: New Bug description: Home Button (located in the Launcher Bar) Long swipe right from left edge should return the user to the Apps Scope, regardless of their current place within the U.I. (i.e. within the Dash, looking at an app, etc). Note: Currenlty UX Testing Report Findings: Home button on the launcher does not always lead to the apps scope Participants expected to be able to go back to the apps scope when pressing the home button, instead of last visited page. Left edge swipe does not always lead to the apps scope Participants expected to be able to get to the apps scope via using the left edge swipe no matter where they were, landing on the last visited page was not expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368709] Re: - Add a crop function directly to the Camera app
** Package changed: unity8 (Ubuntu) = camera-app (Ubuntu) ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368709 Title: - Add a crop function directly to the Camera app Status in Ubuntu UX bugs: New Status in “camera-app” package in Ubuntu: New Bug description: - Add a crop function directly to the Camera app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
