[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect Status in systemd package in Ubuntu: New Bug description: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect Status in systemd package in Ubuntu: New Bug description: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect Status in systemd package in Ubuntu: New Bug description: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade Status in gnome-power-manager package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade Status in gnome-power-manager package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect Status in systemd package in Ubuntu: New Bug description: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization Status in account-plugins package in Ubuntu: Incomplete Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in 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 Status in Unity: Opinion Status in libxfixes package in Ubuntu: Incomplete Status in unity package in Ubuntu: Opinion Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu Precise 12.04 Beta 2 AMD64 DVD: I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session. VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu Precise repository, and Unity is running in 3D mode with Compiz. When the Unity Launcher is set to "autohide," the Launcher will never reveal when the mouse pointer is moved to the left edge of the screen. It does not matter how much "pressure" is applied; the Launcher never appears. I have tried the following VirtualBox window "form-factors," all with the same result (the Launcher never appears): -- VirtualBox session running in a non-maximized window -- VirtualBox session running in a maximized window -- VirtualBox session running full-screen I have attached a screen capture (OGV) with Ubuntu Precise running in a maximized VirtualBox window. Note: This Bug may be related to the following other Bugs reported on LaunchPad: -- Bug 965643: Unity 5.8: auto-hide using mouse reveals launcher inconsistently -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643 -- Bug 923749: New "push mouse offscreen" feature really difficult to get -- -- https://bugs.launchpad.net/unity/+bug/923749 -- Bug 937792: Left launcher does not revel when in autohide mode on multi-monitor setups -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Apr 1 14:46:23 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/971018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization Status in account-plugins package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1612488 Title: Window too small for Facebook authorization Status in account-plugins package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu.
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1360545 Title: [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: 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.
[Touch-packages] [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
[Touch-packages] [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 Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1360732 Title: [utopic] [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug detection to polling Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: 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.:rvn
