[Bug 1919377] Re: gnome-shell 3.38+ HUD app grid is limited to only 4x6
Going back to low resolution 1080p 100dpi, it actually looks decent there, notice the spacing actually looks sane and there aren't huge areas of wasted space like at 4K. So it looks like they only really considered 1080p 100dpi and just blissfully ignored all other use cases. ** Attachment added: "Gnome 40 - 1080p - landscape" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477351/+files/Gnome%2040%20-%201080p%20-%20landscape.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 4x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919377] Re: gnome-shell 3.38+ HUD app grid is limited to only 4x6
I'm using my monitor in portrait mode, but it still looks silly even in normal landscape mode due to it being limited to only 8x3. ** Attachment added: "Gnome 40 - 8x3 grid - landscape" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477349/+files/Gnome%2040%20-%208x3%20grid%20-%20landscape.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 4x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919377] Re: gnome-shell 3.38+ HUD app grid is limited to only 4x6
It also doesn't look any better on Gnome 40, which Ubuntu doesn't use yet. ** Attachment added: "Gnome 40 - 4x6 grid" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477348/+files/Gnome%2040.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 4x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919377] Re: gnome-shell 3.38+ HUD app grid is limited to only 4x6
** Attachment added: "Gnome 3.36 - 6x12 grid" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477346/+files/Ubuntu%2020.04.png ** Description changed: For some reason after Ubuntu 20.04 (Gnome 3.36) the app grid was limited to a maximum of 4x6. This might be acceptable on an iPhone, which is where they actually got the limit from, but it is not at all acceptable for an actual large computer screen. It looks farcical. Even the spacing prior to Ubuntu 20.10 (Gnome 3.38) was much too wide, but this is MUCH MUCH WORSE. It looks like previously it was limited to only ~ 6x12 which was still pretty bad. See the attached screenshot of what this looks like on Gnome 3.36 vs 3.38. Also notice there is more than one page of apps on 3.38 and that it only shows 4x6 at maximum. 🤦 + + As you will notice this is a 4K screen at 100 dpi, its not a small + screen, but is being treated like its a phone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 4x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919377] [NEW] gnome-shell 3.38+ HUD app grid is limited to only 4x6
Public bug reported: For some reason after Ubuntu 20.04 (Gnome 3.36) the app grid was limited to a maximum of 4x6. This might be acceptable on an iPhone, which is where they actually got the limit from, but it is not at all acceptable for an actual large computer screen. It looks farcical. Even the spacing prior to Ubuntu 20.10 (Gnome 3.38) was much too wide, but this is MUCH MUCH WORSE. It looks like previously it was limited to only ~ 6x12 which was still pretty bad. See the attached screenshot of what this looks like on Gnome 3.36 vs 3.38. Also notice there is more than one page of apps on 3.38 and that it only shows 4x6 at maximum. 🤦 As you will notice this is a 4K screen at 100 dpi, its not a small screen, but is being treated like its a phone. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Gnome 3.38 - 4x6 grid" https://bugs.launchpad.net/bugs/1919377/+attachment/5477345/+files/Ubuntu%2020.10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 4x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852001] Re: KDE GUI freeze on high disk IO
The last time I got it to hang long enough to produce a backtrace it showed: [1560556.660010] INFO: task vgs:3103183 blocked for more than 1105 seconds. [1560556.660012] Tainted: G U OE 5.4.0-40-lowlatency #44-Ubuntu [1560556.660013] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1560556.660014] vgs D0 3103183 411358 0x80004004 [1560556.660016] Call Trace: [1560556.660021] __schedule+0x2e5/0x750 [1560556.660023] schedule+0x49/0xd0 [1560556.660024] schedule_timeout+0x21a/0x300 [1560556.660027] ? call_rcu+0x10/0x20 [1560556.660030] ? __percpu_ref_switch_mode+0xec/0x1b0 [1560556.660031] wait_for_completion+0xa3/0x100 [1560556.660033] ? wake_up_q+0x70/0x70 [1560556.660036] exit_aio+0xe7/0xf0 [1560556.660038] mmput+0x22/0x120 [1560556.660039] do_exit+0x2f8/0xae0 [1560556.660041] ? finish_task_switch+0x75/0x250 [1560556.660042] do_group_exit+0x43/0xa0 [1560556.660044] get_signal+0x13e/0x8f0 [1560556.660046] ? hrtimer_cancel+0x15/0x20 [1560556.660047] ? read_events+0x14f/0x160 [1560556.660049] do_signal+0x34/0x6e0 [1560556.660050] ? hrtimer_init_sleeper+0xb0/0xb0 [1560556.660052] ? do_io_getevents+0x7a/0xf0 [1560556.660054] exit_to_usermode_loop+0xbf/0x160 [1560556.660055] do_syscall_64+0x163/0x190 [1560556.660057] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1560556.660058] RIP: 0033:0x7f3b1269a70d [1560556.660062] Code: Bad RIP value. [1560556.660062] RSP: 002b:7fffd99f2f08 EFLAGS: 0246 ORIG_RAX: 00d0 [1560556.660064] RAX: fffc RBX: 7f3b1228e6c0 RCX: 7f3b1269a70d [1560556.660064] RDX: 0040 RSI: 0001 RDI: 7f3b12a7e000 [1560556.660065] RBP: 7f3b12a7e000 R08: R09: 00020016 [1560556.660065] R10: 7fffd99f2f90 R11: 0246 R12: 0001 [1560556.660066] R13: 0002 R14: 0040 R15: 7fffd99f2f90 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852001] Re: KDE GUI freeze on high disk IO
Actually looking at the patch (shrink_dcache_for_umount) this might not be the whole problem but may be just related. The problem I am having is while the system is still running, and cache growing huge, not while umounting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852001] Re: KDE GUI freeze on high disk IO
It appears Red Hat fixed this problem with a kernel patch in RHEL 7.5 that was not upstreamed. https://access.redhat.com/errata/RHSA-2018:1062 BZ - 1471875 - soft lockups during unmount when dentry cache is very large https://bugzilla.redhat.com/show_bug.cgi?id=1471875 ** Bug watch added: Red Hat Bugzilla #1471875 https://bugzilla.redhat.com/show_bug.cgi?id=1471875 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852001] Re: KDE GUI freeze on high disk IO
I haven't verified if this actually fixes the problem but it seems to make a huge difference in 'free' memory as shown by 'free'. I had already closed my VMs by the time I tried this so haven't verified if it stops the long freezes yet. totalusedfree shared buff/cache available Mem: 31030533127905347 22907 19900 Swap: 327673130 29637 echo 3 > /proc/sys/vm/drop_caches totalusedfree shared buff/cache available Mem: 310305349 1712253128557 19915 Swap: 327673130 29637 Notice the 2790 -> 17122 change above in 'free', and 22907 -> 8557 for buff/cache. It appears the kernel doesn't get rid of cache in a reasonable timeframe at the expense of swapping programs out to disk while i/o is happening, which causes gui freezes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852001] Re: KDE GUI freeze on high disk IO
I have this problem as well on Cinnamon, so it doesn't appear to be specific to KDE. It stalls often and frequently over 15-30 seconds at a time for no apparent reason. But the swapping to disk may be a clue. I see this on 5.4.0-40 and have also tried with the lowlatency version of the kernel and it doesn't help. One thing that seems to reduce the frequency of the problem somewhat is to disable transparent_hugepage support but it still happens even after that. I have 32GB ram and it starts happening when I get to about 50% ram (mem available) usage. The system also appears to start swapping at that point despite what swappiness is set to. I tried setting it to 10 but it is still swapping at what appears to be ~ 50% usage. It appears to be very easy to reproduce if you run a few VMware VMs on a system. # cat /proc/sys/vm/swappiness 10 $ free -m totalusedfree shared buff/cache available Mem: 310306591 2469050 24192 14936 Swap: 327674942 27825 $ cat /proc/meminfo MemTotal: 31774792 kB MemFree: 256768 kB MemAvailable: 15324804 kB Buffers: 5887324 kB Cached: 16712984 kB SwapCached: 488276 kB Active: 19816476 kB Inactive:8835508 kB Active(anon): 12801324 kB Inactive(anon): 2522936 kB Active(file):7015152 kB Inactive(file): 6312572 kB Unevictable: 145612 kB Mlocked: 48 kB SwapTotal: 33554428 kB SwapFree: 28493052 kB Dirty: 2301336 kB Writeback: 9564 kB AnonPages: 6161528 kB Mapped: 7931416 kB Shmem: 9272240 kB KReclaimable:2201904 kB Slab:2451272 kB SReclaimable:2201904 kB SUnreclaim: 249368 kB KernelStack: 21552 kB PageTables:85272 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:49441824 kB Committed_AS: 30098296 kB VmallocTotal: 34359738367 kB VmallocUsed: 55400 kB VmallocChunk: 0 kB Percpu: 7712 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB ShmemHugePages:0 kB ShmemPmdMapped:0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 5078656 kB DirectMap2M:27346944 kB DirectMap1G: 0 kB ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect
Has there been any progress on getting rid of initrd or adding stats in the past 2 years? Ubuntu 20.04 still uses initrd and a huge one at that, so the plan to get rid of it seemed to have failed, but without systemd so there are still no timings like with other dists. Having separate stats breakdown for firmware, loader, kernel, and initrd would be useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867572] [NEW] bumblee is not installable with 18.04 HWE due to versioned depends on a provided package
Public bug reported: Ubuntu 18.04 with HWE bumblebee 3.2.1-17 This makes laptops with hybrid graphics not work well. === bumblebee depends on a versioned xserver-xorg-core package Depends: bbswitch-dkms | bbswitch-source, lsb-base (>= 3.0-6), xserver- xorg-core (>= 2:1.18), libbsd0 (>= 0.2.0), libc6 (>= 2.15), libglib2.0-0 (>= 2.12.0), libkmod2 (>= 5~), libx11-6 === HWE 18.04 uses a different package name for xserver-xorg-core -> xserver-xorg-core-hwe-18.04 Provides: xorg-input-abi-24, xorg-renamed-package, xorg-renamed-package- hwe-18.04, xorg-video-abi-24, xserver-xorg-core, xserver-xorg-video- modesetting === apt/dpkg does not handle version depends on virtual/provide packages so can't be installed. === So trying to install bumblebee while HWE is installed does not work: # apt install bumblebee Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: bumblebee : Depends: xserver-xorg-core (>= 2:1.18) E: Unable to correct problems, you have held broken packages. === ** Affects: bumblebee (Ubuntu) Importance: Undecided Status: New ** Summary changed: - bumblee is not installable with HWE due to versioned depends on a provided package + bumblee is not installable with 18.04 HWE due to versioned depends on a provided package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867572 Title: bumblee is not installable with 18.04 HWE due to versioned depends on a provided package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1867572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
wrt #91 which snaps might those be? If its the regular 'chromium' snap it certainly doesn't make any mention of the fact it supports hardware video acceleration or includes the vaapi patch. # snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: Apache-2.0 AND BSD-3-Clause AND LGPL-2.0 AND LGPL-2.1 AND MIT AND MS-PL AND (GPL-2.0+ OR LGPL-2.1+ OR MPL-1.1) description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R channels: stable:73.0.3683.75 2019-03-14 (660) 161MB - candidate: 73.0.3683.75 2019-03-13 (660) 161MB - beta: 73.0.3683.75 2019-03-13 (660) 161MB - edge: 74.0.3729.22 2019-03-20 (667) 162MB - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
Fedora started enabling video acceleration in this build late last year: * Tue Nov 27 2018 Tom Callaway - 70.0.3538.110-2 - enable vaapi support (thanks to Akarshan Biswas for doing the hard work here) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding
As neither Chrome/Chromium or Firefox has any real interest in Linux support can we get Ubuntu to apply the patch? The patch has existed for 5 years already. Even a partial solution where its built in but you still have to enable it in config would be fine. Having to hunt down a ppa to get working video in 2019 on Linux is absurd. Otherwise users would be much better off moving to another distro that supports it such as Arch, Fedora, etc as noted above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect
Thanks for the information Dimitri, I didn't realize that was the reason the times sometimes shows up on some distributions and doesn't on others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect
Its also not clear why Ubuntu's systemd-analyze doesn't report more than just kernel + userspace times even on Ubuntu 18.04. Both CentOS 7 and Fedora 27 report times properly, which are using older versions of systemd. --- CentOS 7 - systemd-219-42.el7_4.7.x86_64 $ systemd-analyze time Startup finished in 846ms (kernel) + 2.678s (initrd) + 2min 29.307s (userspace) = 2min 32.832s --- Fedora 27 - systemd-234-10.git5f8984e.fc27.x86_64 $ systemd-analyze time Startup finished in 21.114s (firmware) + 2.086s (loader) + 1.131s (kernel) + 8.841s (initrd) + 6.125s (userspace) = 39.298s --- Ubuntu systemd 237-3ubuntu4 $ systemd-analyze time Startup finished in 2.561s (kernel) + 12.868s (userspace) = 15.429s graphical.target reached after 12.842s in userspace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615685] Re: systemd-analyze stats for kernel startup time looks suspect
Note firmware and loader times only show up when using UEFI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623666] Re: iOS device contents not displayed in Ubuntu
reply #48 Yes packaged version in main archive, using Ubuntu Mate 17.10 now and its still not showing the photos mount in Caja (like nautilus). I can see the Documents mount though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623666] Re: iOS device contents not displayed in Ubuntu
I should note that the above is while using the regular packaged versions of idevicepair / ifuse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623666] Re: iOS device contents not displayed in Ubuntu
For whatever reason while trying to backup an iPhone 6s+ 10.3.3 before upgrading to 11.0 I can't see the photo mount in mate fuse at all but if I use idevicepair and ifuse from the command line it lets me copy the files. I'm not sure if this is related to the issue others have reported above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] Re: ResolutionKMS patch for Wayland (RHBZ#1292234)
Here are some further bug reports related to this: https://github.com/vmware/open-vm-tools/issues/22 https://bugzilla.redhat.com/show_bug.cgi?id=1292234 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872779 Fedora was fixed on Apr 2, and OpenSUSE was fixed a few days ago. Its not clear why open-vm-tools upstream has still not added this patch. ** Bug watch added: github.com/vmware/open-vm-tools/issues #22 https://github.com/vmware/open-vm-tools/issues/22 ** Bug watch added: Red Hat Bugzilla #1292234 https://bugzilla.redhat.com/show_bug.cgi?id=1292234 ** Bug watch added: Debian Bug tracker #872779 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872779 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708578] Re: Both "Ubuntu" and "Ubuntu on Wayland" run Ubuntu on Wayland, no Xorg option
This issue combined with lp#1703499 makes VMWare only able to display 800x600 by default since there is no obvious way to launch Ubuntu using Xorg and the Wayland patch still hasn't been applied for open-vm-tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708578 Title: Both "Ubuntu" and "Ubuntu on Wayland" run Ubuntu on Wayland, no Xorg option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-session/+bug/1708578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708578] [NEW] Both "Ubuntu" and "Ubuntu on Wayland" run Ubuntu on Wayland, no Xorg option
Public bug reported: At login time you can select between "Ubuntu" and "Ubuntu on Wayland" on Ubuntu 17.10. However both options actually end up running Ubuntu on Wayland and there appears to be no way to actually run Ubuntu on Xorg. I'm not certain if this is actually the right package to file this bug on but its at least related. ** Affects: ubuntu-session (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: ubuntu-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708578 Title: Both "Ubuntu" and "Ubuntu on Wayland" run Ubuntu on Wayland, no Xorg option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-session/+bug/1708578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] Re: ResolutionKMS patch for Wayland (RHBZ#1292234)
Update: Looking at the processes while running it appears both 'Ubuntu' and 'Ubuntu on Wayland' modes _both_ run Ubuntu on Wayland in reality. There appears to be no regular X mode in Ubuntu 17.10... Which makes this patch even more important. gdm 843 0.0 1.2 271332 48588 tty1 S+ 15:22 0:00 /usr/bin/Xwayland :1024 -rootless -noreset -listen 4 -listen 5 -displayfd 6 ccheney1345 0.3 1.2 293488 52000 tty2 S+ 15:22 0:00 /usr/bin/Xwayland :0 -rootless -noreset -listen 4 -listen 5 -displayfd 6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] Re: ResolutionKMS patch for Wayland (RHBZ#1292234)
Somewhat interestingly Debian 9.1.0 Gnome works in both regular and Wayland modes with open-vm-tools-desktop 2:10.1.5-5055683-4, but Ubuntu does not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] Re: ResolutionKMS patch for Wayland (RHBZ#1292234)
Correction: Debian 9.1.0 Gnome with Wayland does not work after reboot (as I expected without the patch), it appears setting the resolution while in Xorg mode seems to have fixed it for Wayland temporarily. Ubuntu 17.10 even when not in 'Wayland' mode does not work though. Running "vmware-user-suid-wrapper" just returns without resizing the screen or doing anything else obvious. I'm not sure why its broken in both regular and Wayland modes on Ubuntu maybe something else is wrong with the Ubuntu package as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] Re: ResolutionKMS patch for Wayland (RHBZ#1292234)
Just wondering why open-vm-tools was updated without this patch as its mostly unusable on 17.10 without it, certainly if you are running regular Ubuntu with a desktop interface anyway. open-vm-tools (2:10.1.5-5055683-5ubuntu1) artful; urgency=low * Merge from Debian unstable. Remaining changes: - Compile with libxmlsec1-dev instead of xmlsecurity/xerces and thus provide VGAuthServices. -- Dimitri John Ledkov Thu, 27 Jul 2017 09:26:39 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703499] [NEW] ResolutionKMS patch for Wayland (RHBZ#1292234)
Public bug reported: open-vm-tools no longer works for Ubuntu 17.10 now that it uses Wayland. There is a patch to fix this issue in Fedora 26, which I have attached to this report. * Sun Apr 02 2017 Ravindra Kumar - 10.1.5-4 - ResolutionKMS patch for Wayland (RHBZ#1292234). * Thu Mar 16 2017 Ravindra Kumar - 10.1.5-3 - Need to add xmlsec1-openssl dependency explicitly. * Tue Feb 28 2017 Richard W.M. Jones - 10.1.5-2 - Use 0644 permissions for udev rules file. * Fri Feb 24 2017 Ravindra Kumar - 10.1.5-1 - Package new upstream version open-vm-tools-10.1.5-5055683 (RHBZ#1408959). ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "resolutionKMS-wayland.patch" https://bugs.launchpad.net/bugs/1703499/+attachment/4912557/+files/resolutionKMS-wayland.patch ** Changed in: open-vm-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703499 Title: ResolutionKMS patch for Wayland (RHBZ#1292234) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1703499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652110] Re: Chromium 55+ doesn't support Widevine library
This also affects Spotify and likely Netflix. Is this going to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652110 Title: Chromium 55+ doesn't support Widevine library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1652110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] Re: i2c_designware 808622C1:06: punit semaphore timed out, resetting
Alex, you should probably file a new upstream bug about the issue if you can reproduce it on the upstream 4.11 version. I no longer have a Cherry Trail system so can't do it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: i2c_designware 808622C1:06: punit semaphore timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used
Kai-Heng, Yes, but with ASPM disabled unfortunately even ASPT doesn't help enough. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682711 Title: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Bug watch added: GNOME Bug Tracker #780078 https://bugzilla.gnome.org/show_bug.cgi?id=780078 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=780078 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used
I sent a follow up email to Lenovo but don't expect to hear back from them until sometime after next Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682711 Title: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used
Talking to Matthew Garrett on irc he said that he thinks this may only be fixable via an UEFI change. 04:33 < ccheney> anyone know if it is possible to change a setting in LnkCap on a pci device? My pcie ports apparently have 'ASPM not supported' set and I need to turn it on somehow 04:33 < ccheney> its on a skylake system 04:35 < mjg59> ccheney: It's set by either the firmware or the chipset itself 04:35 < ccheney> the FADT doesn't have aspm disabled but its not enabled on the ports or the devices, setpci seems to be able to turn it on for LnkCtl but LnkCap seems to be overriding it? 04:35 < mjg59> lnkcap represents what the link is capable of 04:35 < ccheney> mjg59: is there anyway to force enable it afterwards via initrd (similar to acpi replacement tables) or something like that? 04:35 < mjg59> ccheney: Nope 04:35 < ccheney> ugh :( 04:35 < mjg59> Not that I know of -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682711 Title: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used
The setpci commands I used modified the LnkCtl option but not the LnkCap values. I'm not sure but suspect that the LnkCap values are what are causing the problem. -- LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkCap: Port #7, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- vs LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s unlimited, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkCap: Port #7, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s unlimited, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682711 Title: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682711] [NEW] PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used
Public bug reported: This is somewhat similar in issue to lp#1377596. I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe drive in it. As far as I can tell from dissembling the FADT PCIe ASPM is not set to disabled but the ports are not enabled in UEFI during boot. I also notice that the PCIe ASPM debug files are not in sysfs like they normally are ie: link_state I tried running the following manually but I think it must not be enough as the NVMe drive does not run any cooler as it does in a system with known working ASPM. setpci -s 00:1b.0 0x50.B=0x3 setpci -s 00:1c.0 0x50.B=0x3 setpci -s 01:00.0 0x80.B=0x3 setpci -s 02:00.0 0x50.B=0x3 I noticed via lspci that the root ports say ASPM not supported even though the FADT doesn't have them disabled. Is that the reason its still not working and how do I work around that issue? Also is there something specific I can tell Lenovo to do to fix this issue on their end, if it can't be worked around in Linux? I have an open case with them via the UEFI engineering team but so far its been slow going since I don't have anything concrete to tell them to fix. === 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 25.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00218 Data: Capabilities: [90] Subsystem: Lenovo Sunrise Point-H PCI Root Port Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [140 v1] Access Control Services ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir-
[Bug 1682542] [NEW] Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
Public bug reported: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1682542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?
I'm closing this bug as after rebooting onto current linux 4.4.0-43-generic the problem went away. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634005 Title: linux treats first partition on sdcard as much bigger than it really is? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?
blockdev also reports the wrong value: # blockdev --getsz /dev/sdd1 32787056 strace shows that fstat() reports the wrong value. 9175 02:20:07.714355 open("/dev/sdd1", O_RDONLY) = 3 9175 02:20:07.714387 uname({sysname="Linux", nodename="desktop-clc", release="4.4.0-38-generic", version="#57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016", machine="x86_64", domainname="(none)"}) = 0 9175 02:20:07.714420 ioctl(3, BLKGETSIZE64, 0x7fff6d39def0) = -1 ENOTTY (Inappropriate ioctl for device) 9175 02:20:07.718949 ioctl(3, BLKGETSIZE, 0x7fff6d39de08) = -1 ENOTTY (Inappropriate ioctl for device) 9175 02:20:07.719001 ioctl(3, FDGETPRM, 0x7fff6d39de10) = -1 ENOTTY (Inappropriate ioctl for device) 9175 02:20:07.719031 fstat(3, {st_dev=makedev(0, 6), st_ino=714, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=32787056, st_size=16786972672, st_atime=2016/10/17-02:15:26.246576853, st_mtime=2016/10/17-02:15:26.242576837, st_ctime=2016/10/17-02:15:26.242576837}) = 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634005 Title: linux treats first partition on sdcard as much bigger than it really is? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634005] Re: linux treats first partition on sdcard as much bigger than it really is?
Taking the first sector output and decoding it shows: 00 - 00 01 01 - 0c - 3f a0 00 - 00 08 00 00 - 00 00 10 00 00 - 00 81 01 - 83 - 3f 20 00 - 00 08 10 00 - 00 00 10 00 00 - 00 01 01 - 83 - 3f 20 00 - 00 08 20 00 - 00 00 20 00 00 - 00 01 01 - 83 - 3f e0 3f - 00 08 40 00 - 00 f8 79 03 Which looks correct, so I'm not sure whats causing it to think partition 1 is 16GB, is there some kind of special casing for sdcards? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634005 Title: linux treats first partition on sdcard as much bigger than it really is? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634005] [NEW] linux treats first partition on sdcard as much bigger than it really is?
Public bug reported: For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first partition of my sdcard as 16GB regardless of what fdisk says it should be. dd sees the other partitions as the correct size. Also if I run mkfs.vfat on the first partition it is treated as a fuse filesystem when mounted, it seems very strange. The whole card has been zeroed out so it shouldn't be an issue of some other weird data on the card. Pulling and reinserting the card after partitioning makes no difference. I have also included the fdisk bootsector dump at the end of this message. Running linux 4.4.0-38.57 amd64 --- ii linux-headers-4.4.0-38 4.4.0-38.57 all Header files related to Linux kernel version 4.4.0 ii linux-headers-4.4.0-38-generic 4.4.0-38.57 amd64Linux kernel headers for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-38-generic 4.4.0-38.57 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-extra-4.4.0-38-generic 4.4.0-38.57 amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP ii linux-signed-image-4.4.0-38-generic 4.4.0-38.57 amd64Signed kernel image generic ii linux-tools-4.4.0-38 4.4.0-38.57 amd64Linux kernel version specific tools for version 4.4.0-38 ii linux-tools-4.4.0-38-generic 4.4.0-38.57 amd64Linux kernel version specific tools for version 4.4.0-38 --- # fdisk -l /dev/sdd Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes # fdisk /dev/sdd Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x57ca34c2. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p Partition number (1-4, default 1): 1 First sector (2048-62521343, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (2048-62521343, default 62521343): +512MiB Created a new partition 1 of type 'Linux' and of size 512 MiB. Command (m for help): p Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x57ca34c2 Device Boot Start End Sectors Size Id Type /dev/sdd12048 1050623 1048576 512M 83 Linux Command (m for help): n Partition type p primary (1 primary, 0 extended, 3 free) e extended (container for logical partitions) Select (default p): p Partition number (2-4, default 2): First sector (1050624-62521343, default 1050624): Last sector, +sectors or +size{K,M,G,T,P} (1050624-62521343, default 62521343): +512MiB Created a new partition 2 of type 'Linux' and of size 512 MiB. Command (m for help): n Partition type p primary (2 primary, 0 extended, 2 free) e extended (container for logical partitions) Select (default p): p Partition number (3,4, default 3): First sector (2099200-62521343, default 2099200): Last sector, +sectors or +size{K,M,G,T,P} (2099200-62521343, default 62521343): +1024MiB Created a new partition 3 of type 'Linux' and of size 1 GiB. Command (m for help): n Partition type p primary (3 primary, 0 extended, 1 free) e extended (container for logical partitions) Select (default e): p Selected partition 4 First sector (4196352-62521343, default 4196352): Last sector, +sectors or +size{K,M,G,T,P} (4196352-62521343, default 62521343): Created a new partition 4 of type 'Linux' and of size 27.8 GiB. Command (m for help): print Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 62521344 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x57ca34c2 Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 1050623 1048576 512M 83 Linux /dev/sdd2 1050624 2099199 1048576 512M 83 Linux /dev/sdd3 2099200 4196351 20971521G 83 Linux /dev/sdd4 4196352 62521343 58324992 27.8G 83 Linux Command (m for help): t Partition number (1-4, default 4): 1 Partition type (type L to list all types): c Changed type of partition 'Linux' to 'W95 FAT32 (LBA)'. Command (m for help): print Disk /dev/sdd: 29.8 GiB, 32010928128 bytes, 625213
[Bug 1625440] Re: i2c_designware 808622C1:06: punit semaphore timed out, resetting
As noted at the link the code is known wrong for CHT but may have further bugs: https://bugzilla.kernel.org/show_bug.cgi?id=150481#c1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: i2c_designware 808622C1:06: punit semaphore timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] Re: WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]()
I dug around and found upstream kernel bzs related to this issue: https://bugzilla.kernel.org/show_bug.cgi?id=150481 https://bugzilla.kernel.org/show_bug.cgi?id=155241 ** Bug watch added: Linux Kernel Bug Tracker #150481 http://bugzilla.kernel.org/show_bug.cgi?id=150481 ** Bug watch added: Linux Kernel Bug Tracker #155241 http://bugzilla.kernel.org/show_bug.cgi?id=155241 ** Summary changed: - WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() + i2c_designware: probe of 808622C1:06 failed with error -110 ** Summary changed: - i2c_designware: probe of 808622C1:06 failed with error -110 + i2c_designware 808622C1:06: punit semaphore timed out, resetting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: i2c_designware 808622C1:06: punit semaphore timed out, resetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744498/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744501/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744500/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744496/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744503/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744502/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744499/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744497/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744495/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1625440/+attachment/4744494/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] Re: WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]()
apport information ** Tags added: apport-collected yakkety ** Description changed: kernel crash on boot rendering sdio wifi and bluetooth from operating on Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4 on Fedora 25 alpha. The acpi errors don't show up in the 4.8.0 kernel dmesg. Ubuntu 16.10 output. [ 34.656025] i2c_designware 808622C1:06: I2C bus managed by PUNIT [ 34.756942] i2c_designware 808622C1:06: punit semaphore timed out, resetting [ 34.757068] i2c_designware 808622C1:06: PUNIT SEM: 2 [ 34.757134] [ cut here ] [ 34.757148] WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() [ 34.757152] Modules linked in: mei_txe(+) mei snd_rawmidi lpc_ich(+) processor_thermal_device(+) intel_soc_dts_iosf snd_seq hci_uart snd_seq_device 8250_fintek snd_timer intel_hid btbcm btqca dw_dmac btintel sparse_keymap dw_dmac_core bluetooth snd pwm_lpss_platform spi_pxa2xx_platform i2c_designware_platform(+) rfkill_gpio i2c_designware_core pwm_lpss soundcore int3403_thermal int340x_thermal_zone 8250_dw int3400_thermal soc_button_array acpi_thermal_rel mac_hid acpi_ pad parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid mmc_block i915 i2c_algo_bit drm_kms_helper syscopyar ea sysfillrect sysimgblt fb_sys_fops drm video fjes i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview [ 34.757245] CPU: 1 PID: 1137 Comm: systemd-udevd Not tainted 4.4.0-9136-generic #55-Ubuntu [ 34.757248] Hardware name: N/A CherryTrail/Type2 - Board Product Name, BIOS YT11.6W4x64.D003 05/17/2016 [ 34.757254] 0286 be581321 8800b8803a00 813f13e3 [ 34.757260] c0325708 8800b8803a38 810810f2 [ 34.757266] 8801384f9018 ff92 fffefce0 88013b08c810 [ 34.757272] Call Trace: [ 34.757285] [] dump_stack+0x63/0x90 [ 34.757293] [] warn_slowpath_common+0x82/0xc0 [ 34.757298] [] warn_slowpath_null+0x1a/0x20 [ 34.757305] [] baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform] [ 34.757313] [] i2c_dw_init+0x27/0x350 [i2c_designware_core] [ 34.757319] [] i2c_dw_probe+0x52/0x180 [i2c_designware_core] [ 34.757325] [] dw_i2c_plat_probe+0x1d4/0x410 [i2c_designware_platform] [ 34.757334] [] platform_drv_probe+0x3b/0xa0 [ 34.757339] [] driver_probe_device+0x222/0x4a0 [ 34.757344] [] __driver_attach+0x84/0x90 [ 34.757349] [] ? driver_probe_device+0x4a0/0x4a0 [ 34.757354] [] bus_for_each_dev+0x6c/0xc0 [ 34.757359] [] driver_attach+0x1e/0x20 [ 34.757364] [] bus_add_driver+0x1eb/0x280 [ 34.757368] [] ? 0xc032e000 [ 34.757373] [] driver_register+0x60/0xe0 [ 34.757378] [] __platform_driver_register+0x36/0x40 [ 34.757384] [] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [ 34.757390] [] do_one_initcall+0xb3/0x200 [ 34.757397] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [ 34.757404] [] do_init_module+0x5f/0x1cf [ 34.757412] [] load_module+0x1667/0x1c00 [ 34.757417] [] ? __symbol_put+0x60/0x60 [ 34.757424] [] ? kernel_read+0x50/0x80 [ 34.757429] [] SYSC_finit_module+0xb4/0xe0 [ 34.757435] [] SyS_finit_module+0xe/0x10 [ 34.757441] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 34.757446] ---[ end trace e446adf67caf8c0d ]--- [ 34.757451] i2c_designware 808622C1:06: couldn't acquire bus ownership [ 34.757582] i2c_designware: probe of 808622C1:06 failed with error -110 + --- + ApportVersion: 2.20.3-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperVersion: 1.378 + DistroRelease: Ubuntu 16.10 + IwConfig: + lono wireless extensions. + + enxc44eac810358 no wireless extensions. + LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) + MachineType: N/A CherryTrail + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- + ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-9136-generic N/A + linux-backports-modules-4.4.0-9136-generic N/A + linux-firmware 1.161 + RfKill: + + Tags: yakkety + Uname: Linu
[Bug 1625440] Re: WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]()
Fedora 25 alpha kernel (4.8-rc4) output looks effectively the same: [ 20.811692] i2c_designware 808622C1:06: I2C bus managed by PUNIT [ 20.912602] i2c_designware 808622C1:06: punit semaphore timed out, resetting [ 20.912723] i2c_designware 808622C1:06: PUNIT SEM: 2 [ 20.912803] [ cut here ] [ 20.912819] WARNING: CPU: 0 PID: 886 at drivers/i2c/busses/i2c-designware-baytrail.c:106 baytrail_i2c_acquire+0x13c/0x1f0 [i2c_designware_platform] [ 20.912821] Modules linked in: snd acpi_thermal_rel tpm_tis intel_soc_dts_iosf int340x_thermal_zone tpm_tis_core acpi_pad soundcore tpm i2c_designware_platform(+) i2c_designware_core spi_pxa2xx_platform nfsd auth_rpcgss nfs_acl lockd g race nls_utf8 isofs squashfs mmc_block crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel fjes i2c_hid sdhci_acpi sdhci mmc_core 8021q garp stp llc mrp hid_logitech_hidpp uas usb_storage cdc_ether usbnet r8152 hid_logitech_dj mii sunrpc scsi_transport_iscsi loop [ 20.912879] CPU: 0 PID: 886 Comm: systemd-udevd Not tainted 4.8.0-0.rc4.git0.1.fc25.x86_64 #1 [ 20.912881] Hardware name: N/A CherryTrail/Type2 - Board Product Name, BIOS YT11.6W4x64.D003 05/17/2016 [ 20.912885] 0286 7481af87 8ef97997b9c0 833e76cd [ 20.912891] 8ef97997ba00 830a1d7b [ 20.912896] 006a7997b9e0 8ef978496028 fffbbdb7 c05196d0 [ 20.912902] Call Trace: [ 20.912915] [] dump_stack+0x63/0x86 [ 20.912922] [] __warn+0xcb/0xf0 [ 20.912927] [] warn_slowpath_null+0x1d/0x20 [ 20.912932] [] baytrail_i2c_acquire+0x13c/0x1f0 [i2c_designware_platform] [ 20.912938] [] i2c_dw_init+0x23/0x420 [i2c_designware_core] [ 20.912942] [] i2c_dw_probe+0x39/0x1d0 [i2c_designware_core] [ 20.912947] [] dw_i2c_plat_probe+0x1e2/0x420 [i2c_designware_platform] [ 20.912954] [] platform_drv_probe+0x3b/0xa0 [ 20.912958] [] ? devices_kset_move_last+0x4c/0x90 [ 20.912961] [] driver_probe_device+0x223/0x430 [ 20.912965] [] __driver_attach+0xdf/0xf0 [ 20.912968] [] ? driver_probe_device+0x430/0x430 [ 20.912972] [] bus_for_each_dev+0x6c/0xc0 [ 20.912975] [] driver_attach+0x1e/0x20 [ 20.912978] [] bus_add_driver+0x170/0x270 [ 20.912981] [] ? 0xc051d000 [ 20.912984] [] driver_register+0x60/0xe0 [ 20.912987] [] ? 0xc051d000 [ 20.912990] [] __platform_driver_register+0x36/0x40 [ 20.912995] [] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [ 20.913000] [] do_one_initcall+0x50/0x180 [ 20.913006] [] ? kmem_cache_alloc_trace+0x159/0x1b0 [ 20.913010] [] ? do_init_module+0x27/0x1ef [ 20.913013] [] do_init_module+0x5f/0x1ef [ 20.913018] [] load_module+0x22c4/0x29e0 [ 20.913021] [] ? __symbol_put+0x60/0x60 [ 20.913026] [] SYSC_init_module+0x173/0x190 [ 20.913030] [] SyS_init_module+0xe/0x10 [ 20.913034] [] do_syscall_64+0x67/0x160 [ 20.913039] [] entry_SYSCALL64_slow_path+0x25/0x25 [ 20.913042] ---[ end trace e78b154d2d89 ]--- [ 20.913045] i2c_designware 808622C1:06: couldn't acquire bus ownership [ 20.913177] i2c_designware: probe of 808622C1:06 failed with error -110 ** Attachment added: "Fedora 25 dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+attachment/4744084/+files/nexbox.dmesg.4.8.0-0.rc4.git0.1.fc25.x86_64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625440] [NEW] WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]()
Public bug reported: kernel crash on boot rendering sdio wifi and bluetooth from operating on Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4 on Fedora 25 alpha. The acpi errors don't show up in the 4.8.0 kernel dmesg. Ubuntu 16.10 output. [ 34.656025] i2c_designware 808622C1:06: I2C bus managed by PUNIT [ 34.756942] i2c_designware 808622C1:06: punit semaphore timed out, resetting [ 34.757068] i2c_designware 808622C1:06: PUNIT SEM: 2 [ 34.757134] [ cut here ] [ 34.757148] WARNING: CPU: 1 PID: 1137 at /build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() [ 34.757152] Modules linked in: mei_txe(+) mei snd_rawmidi lpc_ich(+) processor_thermal_device(+) intel_soc_dts_iosf snd_seq hci_uart snd_seq_device 8250_fintek snd_timer intel_hid btbcm btqca dw_dmac btintel sparse_keymap dw_dmac_core bluetooth snd pwm_lpss_platform spi_pxa2xx_platform i2c_designware_platform(+) rfkill_gpio i2c_designware_core pwm_lpss soundcore int3403_thermal int340x_thermal_zone 8250_dw int3400_thermal soc_button_array acpi_thermal_rel mac_hid acpi_ pad parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid mmc_block i915 i2c_algo_bit drm_kms_helper syscopyar ea sysfillrect sysimgblt fb_sys_fops drm video fjes i2c_hid hid sdhci_acpi sdhci pinctrl_cherryview [ 34.757245] CPU: 1 PID: 1137 Comm: systemd-udevd Not tainted 4.4.0-9136-generic #55-Ubuntu [ 34.757248] Hardware name: N/A CherryTrail/Type2 - Board Product Name, BIOS YT11.6W4x64.D003 05/17/2016 [ 34.757254] 0286 be581321 8800b8803a00 813f13e3 [ 34.757260] c0325708 8800b8803a38 810810f2 [ 34.757266] 8801384f9018 ff92 fffefce0 88013b08c810 [ 34.757272] Call Trace: [ 34.757285] [] dump_stack+0x63/0x90 [ 34.757293] [] warn_slowpath_common+0x82/0xc0 [ 34.757298] [] warn_slowpath_null+0x1a/0x20 [ 34.757305] [] baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform] [ 34.757313] [] i2c_dw_init+0x27/0x350 [i2c_designware_core] [ 34.757319] [] i2c_dw_probe+0x52/0x180 [i2c_designware_core] [ 34.757325] [] dw_i2c_plat_probe+0x1d4/0x410 [i2c_designware_platform] [ 34.757334] [] platform_drv_probe+0x3b/0xa0 [ 34.757339] [] driver_probe_device+0x222/0x4a0 [ 34.757344] [] __driver_attach+0x84/0x90 [ 34.757349] [] ? driver_probe_device+0x4a0/0x4a0 [ 34.757354] [] bus_for_each_dev+0x6c/0xc0 [ 34.757359] [] driver_attach+0x1e/0x20 [ 34.757364] [] bus_add_driver+0x1eb/0x280 [ 34.757368] [] ? 0xc032e000 [ 34.757373] [] driver_register+0x60/0xe0 [ 34.757378] [] __platform_driver_register+0x36/0x40 [ 34.757384] [] dw_i2c_init_driver+0x17/0x1000 [i2c_designware_platform] [ 34.757390] [] do_one_initcall+0xb3/0x200 [ 34.757397] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [ 34.757404] [] do_init_module+0x5f/0x1cf [ 34.757412] [] load_module+0x1667/0x1c00 [ 34.757417] [] ? __symbol_put+0x60/0x60 [ 34.757424] [] ? kernel_read+0x50/0x80 [ 34.757429] [] SYSC_finit_module+0xb4/0xe0 [ 34.757435] [] SyS_finit_module+0xe/0x10 [ 34.757441] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 34.757446] ---[ end trace e446adf67caf8c0d ]--- [ 34.757451] i2c_designware 808622C1:06: couldn't acquire bus ownership [ 34.757582] i2c_designware: probe of 808622C1:06 failed with error -110 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "Ubuntu 16.10 dmesg output" https://bugs.launchpad.net/bugs/1625440/+attachment/4744080/+files/nexbox.dmesg.4.4.0-9136-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625440 Title: WARNING: CPU: 1 PID: 1137 at /build/linux- rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1612488] Re: Window too small for Facebook authorization
It was after I entered the username and password. If you look closely at the picture you can see where it shows my login but won't let me click through since the window is too small. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612488] Re: Window too small for Facebook authorization
This was on today's version of 16.10. ** Attachment added: "Screenshot from 2016-08-11 23-06-22.png" https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+attachment/4719412/+files/Screenshot%20from%202016-08-11%2023-06-22.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612488] [NEW] Window too small for Facebook authorization
Public bug reported: When trying to add a Facebook account under System Settings -> Online Accounts it says the following after trying to login to Facebook. "Your popup is too small to display this page. Please enlarge it to proceed." This is a gray overlay blocking the ability to accept Ubuntu access to Facebook. There is no way to enlarge the window so it can't proceed. ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware
This is still happening on 16.10 as expected due to the previous setting of 'Opinion' the only way to work around this issue on VMWare Workstation is to change the setting under Edit->Preferences->Input Optimize mouse for games: Always. Disabling "Automatically grab and ungrab the mouse cursor." does not fix the issue. There probably should be an option for auto-hide to unhide on being near the edge, it could be settable just in unity-tweak-tool... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971018 Title: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/971018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448834] Re: mouse battery not shown after upgrade
After rereading the original bug description my issue is slightly different. I could not see my keyboard or mouse until I applied the patch in #8. The patch only made the keyboard show up for me though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448834] Re: mouse battery not shown after upgrade
I have the same problem as the original submitter. The patch appears to correct the problem for the logitech keyboard but not the mouse. I have a MK700 keyboard and M705 mouse both of which used to show up via upower -d. $ upower -d Device: /org/freedesktop/UPower/devices/keyboard_0003o046Do2008x0005 native-path: /sys/devices/pci:00/:00:14.0/usb1/1-10/1-10.3/1-10.3:1.2/0003:046D:C52B.0003/0003:046D:2008.0005 vendor: Logitech, Inc. model:MK700 serial: 9086B70C power supply: no updated: Fri 15 May 2015 11:43:06 AM CDT (19 seconds ago) has history: yes has statistics: no keyboard present: yes rechargeable:yes state: discharging warning-level: none percentage: 55% icon-name: 'battery-good-symbolic' History (charge): 1431708186 0.000 unknown History (rate): 1431708186 0.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Fri 15 May 2015 11:43:06 AM CDT (19 seconds ago) has history: no has statistics: no unknown warning-level: none icon-name: '' Daemon: daemon-version: 0.99.2 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348007] Re: xhci_hcd: Setup ERROR: setup context command for slot n.
I'm seeing what appears to be the same bug on linux 3.17.0-031700rc6 from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc6-utopic/ Plugging the same devices (HD / wacom tablet) into the on chipset Intel USB2 controller works fine. -- [ 156.603076] usb 10-2: new high-speed USB device number 2 using xhci_hcd [ 156.719630] usb 10-2: device descriptor read/64, error -71 [ 156.823527] xhci_hcd :06:00.0: Setup ERROR: setup context command for slot 1. [ 156.823535] usb 10-2: hub failed to enable device, error -22 -- 06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) (prog-if 30 [XHCI]) Subsystem: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1348007 Title: xhci_hcd: Setup ERROR: setup context command for slot n. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360545] Re: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
So I dug around in fdo intel BZ area and found that adding the following to the kernel may produce better logs: "drm.debug=0xe log_buf_len=4M" I have attached the resulting log. It looks a lot like the other bugs for ThinkPad that have been around for a long time now. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1263681 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213 ** Attachment added: "dmesg.3.13.0-35-generic.debug.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+attachment/4195899/+files/dmesg.3.13.0-35-generic.debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360545] Re: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
I forgot to mention in #2 that the reason I tested and uploaded a new dmesg was due to multiple entries in the 3.13.0-35.62 Ubuntu changelog relating to i915 dp support. The changes didn't appear to fix my issue though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360545] Re: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
Still happens on linux-image-3.13.0-35-generic 3.13.0-35.62 Attached updated dmesg output ** Attachment added: "dmesg.3.13.0-35-generic.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+attachment/4195842/+files/dmesg.3.13.0-35-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291827] Re: STABLE Version 2014.2.15
Any chance of getting this updated in 14.10? If it wasn't for the Ubuntu specific changes it would have already been automatically updated as its been in Debian testing since April. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291827 Title: STABLE Version 2014.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1291827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361870] [NEW] exfat-utils: new version 1.1.0 available
Public bug reported: There is a much newer, by a year, release of exfat-utils 1.1.0 available in Debian now, along with matching updated fuse-exfat. It has numerous bug fixes and hopefully will be updated since its needed for interoperability. ** Affects: exfat-utils (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: exfat-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361870 Title: exfat-utils: new version 1.1.0 available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exfat-utils/+bug/1361870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361869] [NEW] fuse-exfat: new version 1.1.0 available
Public bug reported: There is a much newer, by a year, release of fuse-exfat 1.1.0 available in Debian now, along with matching updated exfat-utils. It has numerous bug fixes and hopefully will be updated since its needed for interoperability. ** Affects: fuse-exfat (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: fuse-exfat (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361869 Title: fuse-exfat: new version 1.1.0 available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-exfat/+bug/1361869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291827] Re: STABLE Version 2014.2.15
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291827 Title: STABLE Version 2014.2.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1291827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360732] Re: [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360732 Title: [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360545] Re: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed ** Description changed: I have a haswell motherboard with 3 1080p monitors connected, 2 directly via HDMI and a 3rd HDMI connected to an active displayport dongle. The monitor on the displayport connection had been working fairly reliably until I decided to finally upgrade my bios to fix some other issues (big mistake, since I late found out its nearly impossible to downgrade). Since I upgraded the monitor nearly never works, I did get it to show display a few times but I'm not sure how that happened. At the moment while researching information to add to this post it actually started working for the moment. When I run xrandr it causes the screens to blink - rapidly for around 30sec-1min. + rapidly for around 30sec-1min. Most of the time the system is + unresponsive while the monitor is plugged in. It appears to occasionally + cause the entire desktop to stop responding until the mate-session is + killed. In dmesg I see instances of: [ 10.053292] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling [ 240.125029] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Also fwiw I get different errors, and a kernel backtrace, but still no display on current drm-intel-nightly from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/ And of course it all still works fine under Windows 8.1. Searching google I see other instances of people with the same problem on the i915 driver on other systems like ThinkPad, etc. eg: https://bugzilla.redhat.com/show_bug.cgi?id=1062571 http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/23611 And a few possibly unrelated things in fdo bugzilla 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.0: - + ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 23 01:14:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] + Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-03-16 (160 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140315) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=19efb927-173d-42b5-bb48-163ee5cb72d8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD5H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD5H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.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 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 23 01:11:35 2014 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputVideo Bus
[Bug 1360545] Re: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
** Summary changed: - [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling + [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360732] [NEW] [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
Public bug reported: This is essentially the same issue as bug #1360545 but on utopic. On utopic there are also some kernel backtraces as shown below. The system was completely unresponsive and I had to actually unplug the displayport dongle to be able to file this bug report. In addition to the interrupt storm message I got on trusty I also saw: [3.713503] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe C [3.713536] [drm:ivb_err_int_handler] *ERROR* Pipe C FIFO underrun The numerous backtraces looked similar to this each time, they appear to be happening about 3 times per second until I unplugged the dongle. [3.721942] [ cut here ] [3.721959] WARNING: CPU: 0 PID: 83 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_dp.c:3122 intel_dp_link_down+0x1a9/0x230 [i915]() [3.721960] Modules linked in: mxm_wmi i915 igb psmouse e1000e firewire_ohci drm_kms_helper dca firewire_core drm ahci ptp crc_itu_t i2c_algo_bit libahci pps_core wmi video [3.721969] CPU: 0 PID: 83 Comm: kworker/0:1 Not tainted 3.16.0-10-generic #15-Ubuntu [3.721970] Hardware name: Gigabyte Technology Co., Ltd. Z87X-UD5H/Z87X-UD5H-CF, BIOS 10c 06/12/2014 [3.721978] Workqueue: events i915_hotplug_work_func [i915] [3.721979] 0009 8807ee2f7c88 82777e9f [3.721981] 8807ee2f7cc0 8206fced 8807e8b2 8002 [3.721983] 8807ee642800 0003 8807ee6460d8 8807ee2f7cd0 [3.721984] Call Trace: [3.721989] [] dump_stack+0x45/0x56 [3.721991] [] warn_slowpath_common+0x7d/0xa0 [3.721993] [] warn_slowpath_null+0x1a/0x20 [3.722002] [] intel_dp_link_down+0x1a9/0x230 [i915] [3.722011] [] intel_dp_complete_link_train+0x105/0x390 [i915] [3.722020] [] intel_dp_check_link_status+0xb8/0x1b0 [i915] [3.722028] [] intel_ddi_hot_plug+0x28/0x30 [i915] [3.722035] [] i915_hotplug_work_func+0x1f4/0x340 [i915] [3.722037] [] process_one_work+0x182/0x4e0 [3.722039] [] worker_thread+0x6b/0x6a0 [3.722041] [] ? __schedule+0x39d/0x890 [3.722042] [] ? process_one_work+0x4e0/0x4e0 [3.722045] [] kthread+0xdb/0x100 [3.722047] [] ? kthread_create_on_node+0x1c0/0x1c0 [3.722048] [] ret_from_fork+0x7c/0xb0 [3.722050] [] ? kthread_create_on_node+0x1c0/0x1c0 [3.722051] ---[ end trace eb9925ee23e16705 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CasperVersion: 1.343 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Aug 24 01:23:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140822) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD5H ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash -- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD5H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr10c:bd06/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD5H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.x
[Bug 1360545] Re: [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360545] [NEW] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling
Public bug reported: I have a haswell motherboard with 3 1080p monitors connected, 2 directly via HDMI and a 3rd HDMI connected to an active displayport dongle. The monitor on the displayport connection had been working fairly reliably until I decided to finally upgrade my bios to fix some other issues (big mistake, since I late found out its nearly impossible to downgrade). Since I upgraded the monitor nearly never works, I did get it to show display a few times but I'm not sure how that happened. At the moment while researching information to add to this post it actually started working for the moment. When I run xrandr it causes the screens to blink rapidly for around 30sec-1min. In dmesg I see instances of: [ 10.053292] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling [ 240.125029] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Also fwiw I get different errors, and a kernel backtrace, but still no display on current drm-intel-nightly from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/ And of course it all still works fine under Windows 8.1. Searching google I see other instances of people with the same problem on the i915 driver on other systems like ThinkPad, etc. eg: https://bugzilla.redhat.com/show_bug.cgi?id=1062571 http://comments.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/23611 And a few possibly unrelated things in fdo bugzilla 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.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 23 01:14:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-03-16 (160 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140315) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=19efb927-173d-42b5-bb48-163ee5cb72d8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD5H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD5H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.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 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 23 01:11:35 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 9 inputLogitech Unifying Device. Wireless PID:2008 KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22746 vendor GSM xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne
[Bug 1313436] Re: Unity/Compiz very slow after resume from suspend
After watching a few more days most of the time compiz apparently just doesn't come back at all from suspend, all that is seen is a black screen with a mouse cursor. That is what happens probably 95% of the time. Unfortunately due to Ubuntu dropping the previous 18mo support cycle I will probably end up having to transition the systems off of Ubuntu onto Fedora soon or something else that actually works and doesn't use compiz. Since sticking with 13.10 is no longer an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313436 Title: Unity/Compiz very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313436] Re: Unity/Compiz very slow after resume from suspend
So I found a temporary workaround that seems to work, whenever it hangs I can send HUP to compiz and that seems to fix the problem. eg: kill -HUP $(pidof compiz) However this appears to expose yet another bug that minimized windows at the time of compiz restart essentially disappear permanently, they do not show up in the sidebar anymore, eg if you have 5 firefox windows any that are minimized disappear from the list until firefox is restarted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313436 Title: Unity/Compiz very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313436] Re: Unity/Compiz very slow after resume from suspend
** Attachment added: "Example of problem" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313436/+attachment/4098712/+files/image.jpg ** Package changed: xorg (Ubuntu) => unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Description changed: After suspending and then resuming the system unity/compiz often but not always becomes extremely slow to respond, so much so that you can see the transistion from lockscreen to desktop for many minutes (if it ever finishes). I will attach a picture of what it looks like. I didn't wait around long enough to see if it would ever actually finish showing the desktop. Is there any way to work around this issue? setsid unity has been mentioned online as a workaround for unity/compiz problems but that does not appear to work when run from the linux command line outside of X. The system has never been able to run the nouveau driver due to it crashing on resume under any desktop environment, which is the primary - reason its running the nvidia driver. + reason its running the nvidia driver which has worked fine for the past + 5 years I've owned the system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 + GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 27 15:14:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd Device [1458:3417] + NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd Device [1458:3417] InstallationDate: Installed on 2014-04-25 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. P55-UD5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4cbdddb9-1645-4914-b056-903626ac77cf ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11c dmi.board.name: P55-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11c:bd11/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD5:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 27 15:10:24 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.15.1-0ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313436 Title: Unity/Compiz very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313436/+subscriptions -- ubuntu-bugs mailing
[Bug 1313436] [NEW] Unity/Compiz very slow after resume from suspend
Public bug reported: After suspending and then resuming the system unity/compiz often but not always becomes extremely slow to respond, so much so that you can see the transistion from lockscreen to desktop for many minutes (if it ever finishes). I will attach a picture of what it looks like. I didn't wait around long enough to see if it would ever actually finish showing the desktop. Is there any way to work around this issue? setsid unity has been mentioned online as a workaround for unity/compiz problems but that does not appear to work when run from the linux command line outside of X. The system has never been able to run the nouveau driver due to it crashing on resume under any desktop environment, which is the primary reason its running the nvidia driver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 27 15:14:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3417] InstallationDate: Installed on 2014-04-25 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. P55-UD5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4cbdddb9-1645-4914-b056-903626ac77cf ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11c dmi.board.name: P55-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11c:bd11/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD5:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 27 15:10:24 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 performance trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313436 Title: Unity/Compiz very slow after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] Re: unity hud shows through screensaver
Sorry I was out of town for a conference so was unable to respond quickly. I just reproduced this bug again with final 14.04, and on top of that it appears to have passed my password through to the application with focus behind the screensaver which happened to be IRC (ugh). ** Changed in: unity (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] Re: unity hud shows through screensaver
I saw it happen this morning but that session was logged in on April 9. I just logged out and back in after verifying the system is fully up to date and will monitor to see if the problem occurs again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066481/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066478/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066480/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066479/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066482/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066469/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] LightdmGreeterLogOld.txt
apport information ** Attachment added: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066468/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066471/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066474/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066465/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066476/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066470/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066475/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066477/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066460/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066473/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302835] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1302835/+attachment/4066472/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302835 Title: unity hud shows through screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs