[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location
I too have been seeing this issue on my Ubuntu 16.04.6 LTS installation and after living with it for a long long time, decided to hunt down reports of others with the issue. As I now see, it is a known issue. That sort of made me feel better - specifically that misery loves company - :(. Here is how I can reliably reproduce this issue on my system: Configure at least 2 workspaces: On the left workspace, open an application - say Chrome On the right workspace I have Firefox If I switch between workspaces using keyboard shortcuts, the right-click context menu on Firefox continues to function as expected. Also, if I click the Workspace Switcher in launcher and select the different workspaces, again Firefox context menu functions as expected. However, if I click the Chrome icon in the launcher and then click the Firefox icon (in essence I'm switching workspaces indirectly), the Firefox context menu appears at random locations - mainly along the edges of the screen - I am yet to see it appear in a random location away from screen edges (see attached screenshot). I have noticed there are several ways to restore the placement of the context menu: * Middle-click the title bar (or the panel if Firefox is maximized) * Switch to another application running in the same workspace and return to Firefox * Move the Firefox window * Resize the Firefox window There could be other ways to restore the context menu, but the few I mention above work reliably in my environment. I'm hoping that when I migrate to Ubuntu 20.04 next year the issue will have been resolved. ** Attachment added: "Screenshot of Firefox context menu placement" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1603430/+attachment/5305830/+files/firefox-context-menu.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1603430 Title: Firefox dropdowns in wrong location Status in Linux Mint: New Status in cinnamon-desktop-environment package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: On Mint 17.3 Cinnamon 64bit. Steps to reproduce: * Do a fresh install. * Run mintupdate and update all packages. * Run firefox. * Start right clicking on the page to open the context menu. Resize the window and perhaps move it around the screen a couple of times. Right click some more. * Observer that, eventually, the context menu will start to appear in incorrect locations on the screen. The same also happens with the search bar, text fields and any other dropdown box. In the worst embodiment of the bug, the menu opens underneath the pointer and treats the release of the mouse button as a click, and so does things the user does not want to do. I believe the root cause is the following bug in GTK+ 3.10.8. Firefox switched over to using GTK+3 in version 46 which is when this bug appeared and has been there ever since. https://bugzilla.gnome.org/show_bug.cgi?id=758609 https://bugzilla.mozilla.org/show_bug.cgi?id=1022241 Mozilla aren't going to fix it because it's a GTK bug. GTK have already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not have the patch. Please roll out the patch for us 17.3 users who cannot upgrade. I can confirm that the problem is solved in Mint 18. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out
** Attachment added: "syslog lines pertinent to vpn connection failure" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+attachment/4839770/+files/failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10, in the nm applet menu, VPN Connections -> Configure VPN is grayed out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 16:04:49 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-04 (951 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IpRoute: default via 172.28.77.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 172.28.77.0/24 dev wlan0 proto kernel scope link src 172.28.77.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-07T11:36:55.286063 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/0 BlueCedar-GUEST f7b79954-9427-47eb-adba-875b5b152f37 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out
** Attachment added: "syslog lines pertinent to vpn connection success" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+attachment/4839771/+files/success -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10, in the nm applet menu, VPN Connections -> Configure VPN is grayed out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 16:04:49 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-04 (951 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IpRoute: default via 172.28.77.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 172.28.77.0/24 dev wlan0 proto kernel scope link src 172.28.77.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-07T11:36:55.286063 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/0 BlueCedar-GUEST f7b79954-9427-47eb-adba-875b5b152f37 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out
I'm also going to add to this. I have just done a clean install of 16.04 LTS and OpenVPN connects intermittently. Despite installing openvpn, network-manager-openvpn, and network-manager-openvpn-gnome, the "Configure VPN..." option remains grayed out. In addition, after creating my VPN profile via 'Edit Connections...', I'm not able to consistently create a VPN tunnel to the office. Attached are 2 files: success and failure. Both files contain pertinent lines from /var/log/syslog with success showing a success full connection and failure showing a failed connection. In both cases, I get a notification pop-up that suggests that the vpn connected successfully :(. When the VPN fails to connect, the 'tun0' interface has no IP Address and is in a down state. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10, in the nm applet menu, VPN Connections -> Configure VPN is grayed out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 16:04:49 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-04 (951 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) IpRoute: default via 172.28.77.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 172.28.77.0/24 dev wlan0 proto kernel scope link src 172.28.77.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-07T11:36:55.286063 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/0 BlueCedar-GUEST f7b79954-9427-47eb-adba-875b5b152f37 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work
I get this from time to time as well and it gets frustrating. I can resolve the issue by restarting lightdm (or rebooting), but it is frustrating as hell as I'm heavily dependent on that shortcut. For instance, I currently have 6 VM's running on my laptop and right now have to shut them down just to get this shortcut back. Other shortcuts using CTRL+ALT (such heading to tty1-6 via F1-F6 and back to the GUI via F7) are working so not sure why it only affects the terminal in the GUI! $ uname -a Linux akk-m6700.anroet.com 3.16.0-44-generic #59~14.04.1-Ubuntu SMP Tue Jul 7 15:07:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux (linux-generic-lts-utopic) $ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:p rinting-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty I'm going to install the Vivid kernel so that the reboot to fix this current annoyance is at least worthwhile! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Fix Released Bug description: The global shortcut CTRL+ALT+T to open a new terminal windows is missing in Ubuntu since 14.04 Please reenable it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 13 18:01:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-10 (92 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2014-03-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
I have the same problem and the solution for me was to manually change the profile. This post on the Ubuntu forums was very helpful: http://askubuntu.com/questions/287254/ubuntu-13-04-bluetooth-a2dp-does-not-work In essence, you need to run the following command to switch profile to a2dp: sudo pactl list cards short sudo pactl set-card-profile card name from above step a2dp The interesting thing for me is that when I initially connected the Logitech Mini Boombox, it was found with no problems and it worked flawlessly. However, I forgot to connect the laptop to a power source and when it finally shutdown in the night, I could not get it to work again in the morning - not even after purging and reinstalling all bluetooth related packages as well as pulseaudio. In the end, the two commands above worked just fine. Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will show in the PulseAudio mixer * After connecting the external speaker to the audio sink, I can also see the device in the Play sound through listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose Audio Profile from the context menu and try to select High Fidelity Playback (A2DP) as the new profile, I get an error message stating failed to change profile to a2dp I've already added Enable=Socket in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273832] Re: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used.
UPDATE: I got tired of the workaround and reverted to gnome-screensaver which has since fixed my blank screen w/ mouse issue: sudo apt-get install --reinstall ubuntu-desktop gnome-screensaver sudo apt-get remove --purge xscreensaver* sudo apt-get autoremove I'm now back to a bland blank screen as my screensaver but at least it resumes every time! Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1273832 Title: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used. Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: On a Haswell system, if AccelMethod UXA selected in xorg.conf, xserver freezes (moveable cursor, but frozen and unresponsive desktop) each time the screen is locked (either via inactivity or lid close on laptop) . This freeze does not occur if SNA AccelMethod is selected. This freeze can also be avoided if vblank_mode=0 is used, even if UXA acceleration selected. 1) Ubuntu release: 13.10, but I also tested this on 12.04 LTS, in which case I got exactly the same bug, only the frozen screen was blank rather than frozen desktop image. 2) Expected result: No freeze when locking screen/closing lid. Just the login screen greeter. 3) How to reproduce: On Haswell system, in xorg.conf: Section Device Identifier Intel Graphics Driver intel Option AccelMethod UXA #bug occurs # Option AccelMethod SNA #(default) no bug! EndSection reboot. Try closing the lid or locking screen a number of times (normally within a few attempts you will see the freeze). 4) Resolution: Short term solution is to switch to a tty and back. Alternatively, boot with the SNA acceleration method instead. Another alternative: use a dri config file in home directory: ~/.drirc containing device screen=0 driver=dri2 application name=Default option name=vblank_mode value=0/ /application /device to turn off vsync. 5) Importance for fglrx driver users with AMD cards: fglrx and pxpress by default force the i915 driver to use UXA mode, thus when selecting the iGPU users of fglrx will experience this freezing bug. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jan 28 20:43:34 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: fglrx, 13.251, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2216] Subsystem: Lenovo Device [17aa:2216] InstallationDate: Installed on 2014-01-17 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20B3CTO1WW MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=8a15962e-ad4d-4eb0-96af-37d167313e92 ro SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GPET53WW (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B3CTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGPET53WW(1.53):bd11/28/2013:svnLENOVO:pn20B3CTO1WW:pvrThinkPadS5-S540:rvnLENOVO:rn20B3CTO1WW:rvr0B98405Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20B3CTO1WW dmi.product.version: ThinkPad S5-S540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Desktop-packages] [Bug 1273832] Re: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used.
Recently I underwent a botched nvidia-prime install that left a bitter taste in my mouth: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067 I had to purge my system of all nvidia drivers (apt-get --purge remove nvidia\*), then reinstall them: https://wiki.ubuntu.com/Bumblebee After reinstallation, when my screen goes blank after idling, sometimes it resumes to the desktop, other times I'm left at a black screen with moving cursor that appears to indicate the screen is actually there, but just not visible. The mouse cursor will change from a pointer to a hand (if it happens to hover over a hyperlink in the browser), or a 'I' (when it hovers over a text input area). I kept searching for a solution that related to the Xorg system, but everything I threw at it (the little I know about X) didn't bear fruit. In the end, I just simply had to go to a console (CTRL+ALT+F1) to restart lightdm to get my desktop back. When working with multiple windows and having many applications open, losing the desktop can cause one to experiance weird emotions and exhibit irrational actions; and it gets really old, really fast! To cut a long story short, today I got fedup with it and started killing anything that interracts with the display system (sometimes fatally that I had to reboot by holding power button down for 5secs) to get this sorted. Interestingly, the culprit appears to be compiz. I can now duplicate this easily: 1. launch screensaver preferences (i use xscreensaver) 2. select a GL screensaver (the black screen with mouse occurs more often with such a screensaver) 3. click Preview button then hit the ESC key to return to desktop repeatedly until the black screen+mouse appears 4. CTRL+ALT+F1 to go to console window 1 and run the command: kill -9 $(pgrep compiz) 5 CTRL+ALT+F7 to return to GUI desktop - you should see your desktop minus the open windows 6 move mouse cursor to get compiz to reactivate itself and bring all your open applications into view Hopefully this workaround will keep people like me sane for a little longer... Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1273832 Title: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used. Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: On a Haswell system, if AccelMethod UXA selected in xorg.conf, xserver freezes (moveable cursor, but frozen and unresponsive desktop) each time the screen is locked (either via inactivity or lid close on laptop) . This freeze does not occur if SNA AccelMethod is selected. This freeze can also be avoided if vblank_mode=0 is used, even if UXA acceleration selected. 1) Ubuntu release: 13.10, but I also tested this on 12.04 LTS, in which case I got exactly the same bug, only the frozen screen was blank rather than frozen desktop image. 2) Expected result: No freeze when locking screen/closing lid. Just the login screen greeter. 3) How to reproduce: On Haswell system, in xorg.conf: Section Device Identifier Intel Graphics Driver intel Option AccelMethod UXA #bug occurs # Option AccelMethod SNA #(default) no bug! EndSection reboot. Try closing the lid or locking screen a number of times (normally within a few attempts you will see the freeze). 4) Resolution: Short term solution is to switch to a tty and back. Alternatively, boot with the SNA acceleration method instead. Another alternative: use a dri config file in home directory: ~/.drirc containing device screen=0 driver=dri2 application name=Default option name=vblank_mode value=0/ /application /device to turn off vsync. 5) Importance for fglrx driver users with AMD cards: fglrx and pxpress by default force the i915 driver to use UXA mode, thus when selecting the iGPU users of fglrx will experience this freezing bug. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Jan 28 20:43:34 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: fglrx, 13.251, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
In the end, I just gave up on nvidia-prime and went back to bumblebee: https://wiki.ubuntu.com/Bumblebee Hopefully by the time I'm migrating to the next LTS version, nvidia- prime will be ready for prime time - ;)! Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
Let me add that although nvidia-prime maybe working for some, the above statement should really have quantified it more to be specific to my use case: Dell Precision M6700 w/ Optimus Tech 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK104GLM [Quadro K3000M] (rev ff) This combination does not work with nvidia-prime. Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
Below is a transcript of what happened (I ran the commands as root - sudo su -): # apt-get --purge remove nvidia-331-updates nvidia-331 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: nvidia-304 nvidia-current The following packages will be REMOVED: nvidia-319* nvidia-319-updates* nvidia-331* nvidia-331-updates* The following NEW packages will be installed: nvidia-304 nvidia-current 0 to upgrade, 2 to newly install, 4 to remove and 0 not to upgrade. Need to get 68.3 MB of archives. After this operation, 261 MB disk space will be freed. Do you want to continue [Y/n]? Get:1 http://au.archive.ubuntu.com/ubuntu/ precise-updates/restricted nvidia-304 amd64 304.116-0ubuntu0.0.1 [68.3 MB] Get:2 http://au.archive.ubuntu.com/ubuntu/ precise-updates/restricted nvidia-current amd64 304.116-0ubuntu0.0.1 [4,504 B] Fetched 68.3 MB in 53s (1,276 kB/s) Selecting previously unselected package nvidia-304. (Reading database ... 460709 files and directories currently installed.) Unpacking nvidia-304 (from .../nvidia-304_304.116-0ubuntu0.0.1_amd64.deb) ... Selecting previously unselected package nvidia-current. Unpacking nvidia-current (from .../nvidia-current_304.116-0ubuntu0.0.1_amd64.deb) ... Processing triggers for man-db ... Setting up nvidia-304 (304.116-0ubuntu0.0.1) ... update-alternatives: using /usr/share/nvidia-331-updates/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode. INFO:Enable nvidia-304 DEBUG:Parsing /usr/share/nvidia-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/nvidia-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/nvidia-common/quirks/dell_latitude Loading new nvidia-304-304.116 DKMS files... First Installation: checking all kernels... Building only for 3.9.0-030900-generic Building for architecture x86_64 Building initial module for 3.9.0-030900-generic Done. nvidia_304: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.9.0-030900-generic/updates/dkms/ depmod DKMS: install completed. Setting up nvidia-current (304.116-0ubuntu0.0.1) ... (Reading database ... 460917 files and directories currently installed.) Removing nvidia-319 ... Purging configuration files for nvidia-319 ... Removing nvidia-319-updates ... Purging configuration files for nvidia-319-updates ... Removing nvidia-331 ... Removing all DKMS Modules Done. INFO:Disable nvidia-331 DEBUG:Parsing /usr/share/nvidia-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/nvidia-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/nvidia-common/quirks/dell_latitude update-initramfs: deferring update (trigger activated) Purging configuration files for nvidia-331 ... update-initramfs: deferring update (trigger activated) Removing nvidia-331-updates ... Removing all DKMS Modules Done. update-alternatives: using /usr/share/nvidia-304/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode. INFO:Disable nvidia-331-updates DEBUG:Parsing /usr/share/nvidia-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/nvidia-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/nvidia-common/quirks/dell_latitude update-initramfs: deferring update (trigger activated) Purging configuration files for nvidia-331-updates ... update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin ... ldconfig deferred processing now taking place Processing triggers for man-db ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.9.0-030900-generic # apt-get install nvidia-331 nvidia-prime Reading package lists... Done Building dependency tree Reading state information... Done nvidia-prime is already the newest version. Suggested packages: nvidia-331-uvm The following NEW packages will be installed: nvidia-331 0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade. Need to get 75.4 MB of archives. After this operation, 233 MB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://au.archive.ubuntu.com/ubuntu/ precise-updates/restricted nvidia-331 amd64 331.20-0ubuntu0.0.1 [75.4 MB] Fetched 75.4 MB in 52s (1,427 kB/s) Selecting previously unselected package nvidia-331. (Reading database ... 460455 files and directories currently installed.) Unpacking nvidia-331 (from .../nvidia-331_331.20-0ubuntu0.0.1_amd64.deb) ... Processing triggers for man-db ... Setting up nvidia-331 (331.20-0ubuntu0.0.1) ... INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/nvidia-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/nvidia-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/nvidia-common/quirks/dell_latitude Loading new nvidia-331-331.20 DKMS
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
I'm using bumblebee to enable optimus. Is this functionality now built into the Nvidia driver? Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
I've just noticed that when I attempt to purge nvidia-331*, systems insists on installing nvidia-304. Why? # apt-get --purge remove nvidia-331 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: nvidia-304 nvidia-current The following packages will be REMOVED: nvidia-331* The following NEW packages will be installed: nvidia-304 nvidia-current 0 to upgrade, 2 to newly install, 1 to remove and 3 not to upgrade. Need to get 0 B/68.3 MB of archives. After this operation, 27.4 MB disk space will be freed. Do you want to continue [Y/n]? In any case, I'll rerun the previous commands in addition to also purging bumblebee and if anything fails, maybe it's time to move onto the Salamanda! Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
** Attachment added: update-alternatives --display i386-linux-gnu_gl_conf https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3970808/+files/2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
** Attachment added: update-alternatives --display x86_64-linux-gnu_gl_conf https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3970807/+files/1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
According to my apt history log: Start-Date: 2014-02-05 08:00:40 Commandline: aptdaemon role='role-commit-packages' sender=':1.80' Upgrade: nvidia-prime:amd64 (0.4.2~hybrid0.0.1, 0.5~hybrid0.0.2), lightdm:amd64 (1.2.3-0ubuntu2.3, 1.2.3-0ubuntu2.4), python-apt:amd64 (0.8.3ubuntu7.1, 0.8.3ubuntu7.2), python-apt-common:amd64 (0.8.3ubuntu7.1, 0.8.3ubuntu7.2), libyaml-0-2:amd64 (0.1.4-2, 0.1.4-2ubuntu0.12.04.1), libcurl3:amd64 (7.22.0-3ubuntu4.6, 7.22.0-3ubuntu4.7), libcurl3:i386 (7.22.0-3ubuntu4.6, 7.22.0-3ubuntu4.7), dkms:amd64 (2.2.0.3-1ubuntu3.1, 2.2.0.3-1ubuntu3.2), libcurl3-nss:amd64 (7.22.0-3ubuntu4.6, 7.22.0-3ubuntu4.7), curl:amd64 (7.22.0-3ubuntu4.6, 7.22.0-3ubuntu4.7), jockey-common:amd64 (0.9.7-0ubuntu7.11, 0.9.7-0ubuntu7.13), jockey-gtk:amd64 (0.9.7-0ubuntu7.11, 0.9.7-0ubuntu7.13), liblightdm-gobject-1-0:amd64 (1.2.3-0ubuntu2.3, 1.2.3-0ubuntu2.4), libcurl3-gnutls:amd64 (7.22.0-3ubuntu4.6, 7.22.0-3ubuntu4.7) End-Date: 2014-02-05 08:00:52 I did not have any problems when running the nvidia-prime v0.4.2! When I remove the quiet and splash entries from my kernel line in grub.cfg, I hear a beep before the laptop freezes. REISUB doesn't even bring it back to life; only power button for ~5 seconds gets it to shutdown then I can restart! Cheers, ak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
This morning (20140205 @ ~8am AEDST) accepted an update on my system (nvidia-prime amongst others). However, I was unable to login afterwards. After prowling my /var/log folder, I came across /var/log /nvidia-prime-upstart.log (attached) which suggested that nvidia-prime was the issue. I was then able to login to my desktop (degraded graphics mode - max res 1024x768) and do a Google search which brougt me here. Having never manually submitted (I believe my laptop automatically collects info about my laptop before it submits a bug when something crashes) a bug report on Launchpad, please bear with me: Laptop details: Manufacturer: Dell Precision M6700 CPU: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz Onboard Video: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) Discrete Video: 01:00.0 VGA compatible controller: NVIDIA Corporation GK104GLM [Quadro K3000M] (rev ff) OS: Ubuntu 12.04.3 LTS Kernel: 3.9.0-030900-generic (from Saucy Salamanda to fix issues with slow Wifi performance on Ultimate-N 6300 built-in card) Work-around: I had to modify /etc/init/nvidia-prime.conf (add 'exit' statement near the top) and cat /dev/null to /etc/X11/xorg.conf in order to get back to full desktop mode. Please see attachment from out put of apport-cli -f -p nvidia-prime --save bug.apport Cheers, ak. ** Attachment added: apport-cli -f -p nvidia-prime --save bug.apport https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3969441/+files/bug.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
Attaching /var/log/nvidia-prime-upstart.log ** Attachment added: nvidia-prime-upstart.log https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+attachment/3969442/+files/nvidia-prime-upstart.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
