[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
In response to #6 $ echo mem | sudo tee /sys/power/state That works for me too - but then there's no password protection on resume... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1703506] Re: SMT not supported by QEMU on AMD Ryzen CPU
I was able to avoid rebooting after following @Andrii's instructions - https://bugs.launchpad.net/qemu/+bug/1703506/comments/19 - above: systemctl stop libvirtd libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket sudo modprobe -r kvm_intel kvm systemctl start libvirtd libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket These instructions to avoid rebooting might not work for those using a non-Intel CPU as you'll have a different kernel module. You can check by running `lsmod | grep kvm`. Cheers, ak. System info: # inxi -CMz Machine: Type: Laptop System: Dell product: Precision M6700 v: 01 serial: Mobo: Dell model: 0JWMFY v: A00 serial: UEFI: Dell v: A20 date: 11/30/2018 CPU: Info: quad core model: Intel Core i7-3840QM bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 3607 min/max: 1200/3800 cores: 1: 3588 2: 3615 3: 3638 4: 3588 5: 3588 6: 3638 7: 3617 8: 3588 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1703506 Title: SMT not supported by QEMU on AMD Ryzen CPU Status in QEMU: Expired Bug description: HyperThreading/SMT is supported by AMD Ryzen CPUs but results in this message when setting the topology to threads=2: qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly. Checking in a Windows 10 guest reveals that SMT is not enabled, and from what I understand, QEMU converts the topology from threads to cores internally on AMD CPUs. This appears to cause performance problems in the guest perhaps because programs are assuming that these threads are actual cores. Software: Linux 4.12, qemu 2.9.0 host with KVM enabled, Windows 10 pro guest To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1703506/+subscriptions
[Kernel-packages] [Bug 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hey Ian.
Nevermind. After looking at the patch file, I realized what I needed to
do and I can report that my m6700 from 9 years ago (what a journey) can
finally make use of the mic on my Bluetooth headset.
Cheers,
Anthony.
For anyone looking for the same instructions as I was, I used the
following sources:
Getting the Kernel source:
https://askubuntu.com/questions/159833/how-do-i-get-the-kernel-source-code
Compiling the module:
https://unix.stackexchange.com/questions/199350/bluetooth-btusb-how-to-replace-module-version-with-a-newer-one
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Confirmed
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hey Ian. Nevermind. After looking at the patch file, I realized what I needed to do and I can report that my m6700 from 9 years ago (what a journey) can finally make use of the mic on my Bluetooth headset. Cheers, Anthony. For anyone looking for the same instructions as I was, I used the following sources: Getting the Kernel source: https://askubuntu.com/questions/159833/how-do-i-get-the-kernel-source-code Compiling the module: https://unix.stackexchange.com/questions/199350/bluetooth-btusb-how-to-replace-module-version-with-a-newer-one -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924741 Title: Load Broadcom firmware for Dell Bluetooth device [413c:8197] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hi Ian. I've had my m6700 since 2012 and have never been able to use any Bluetooth headset. Any chance you can provide pointers on what incantations one needs to call upon to get this fixed like you've done on your laptop? Cheers, Anthony. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924741 Title: Load Broadcom firmware for Dell Bluetooth device [413c:8197] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1924741] Re: Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Hi Ian.
I've had my m6700 since 2012 and have never been able to use any
Bluetooth headset.
Any chance you can provide pointers on what incantations one needs to
call upon to get this fixed like you've done on your laptop?
Cheers,
Anthony.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device [413c:8197]
Status in linux package in Ubuntu:
Confirmed
Bug description:
The Broadcom Bluetooth kernel module supports loading patches for
specific hardware devices. Which devices require patchram support is
defined in an array of structs in the kernel module `btusb`, which
allow matching by Vendor ID and, optionally, Product ID.
The Dell-branded device `413c:8197` requires the patch
`BCM20702A1-413c-8197.hcd`[1] to be loaded in order for HSP/HFP
functionality to work (A2DP and AVRCP work without the patch).
However, the patch is not sought for this device by `btusb`.
In 2011, `413c:8197` was included in the module[2], but not marked as
requiring patchram. Later, in 2017, a blanket entry was added for all
Dell-branded (`413c`) devices[3], marking them as requiring patchram.
However, the previous entry for `413c:8197` was not removed and
appears to block the patchram requirement from being added for this
device (presumably the algorithm stops searching after the first
match). The code stands like so:
```
static const struct usb_device_id btusb_table[] = {
...
/* Broadcom BCM20702A0 */
{ USB_DEVICE(0x413c, 0x8197) },
...
/* Dell Computer - Broadcom based */
{ USB_VENDOR_AND_INTERFACE_INFO(0x413c, 0xff, 0x01, 0x01),
.driver_info = BTUSB_BCM_PATCHRAM },
```
I would like to request removal of the earlier entry to facilitate
patchram support for device `413c:8197`.
I have tested this as working on my Dell Precision M6700 running
Ubuntu 20.04 with kernel `5.4.0-71-generic`.
[1]:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[2]:
https://github.com/torvalds/linux/commit/d13431ca3eb2a2c14314f04813cdc11cd869f150
[3]:
https://github.com/torvalds/linux/commit/fdfddc601713d4ed564b0bd25b29415bd622020a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924741/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603430 Title: Firefox dropdowns in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640970 Title: 16.10: VPN Connections -> Configure VPN grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1640970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[Touch-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 Ubuntu Touch seeded 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/~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 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-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
[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
In comparison, when attempting to lunch a VitualBox VM, it fails with a
slightly better error message at least directing one to investigate what
else would be using a hypervisor. But it also suggests some rather
drastic steps to do with recompiling the kernel to remove KVM kernel
extension - wow:
==
Failed to open a session for the virtual machine core-plus-vm.
VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VirtualBox can't operate in VMX root mode. Please disable the KVM kernel
extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
I've been struggling with this for nearly 2 hours before I realized that
I was running a virtualbox vm in headless mode. Was trying to create a
qemu-kvm vm and it kept failing with symptoms similar to those reported
here.
What would be good is getting qemu-kvm to at least check if another
hypervisor is currently running, then allude that fact to the moronic
end-user and save the sucker from wasting 2 hours on a Saturday
afternoon chasing his tail!
This is the error I was getting:
==
[Sat, 26 Mar 2016 15:47:21 virt-manager 490] DEBUG (error:84) error dialog
message:
summary=Unable to complete install: 'internal error: process exited while
connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
failed to initialize KVM: Device or resource busy
'
details=Unable to complete install: 'internal error: process exited while
connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
failed to initialize KVM: Device or resource busy
'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1819, in do_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install
noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3497, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: internal error: process exited while connecting to monitor:
ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy
failed to initialize KVM: Device or resource busy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent channel perms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457078] Re: L2TP client support for PSK removed from 15.04/15.10
This begs 2 questions from my end: 1. How does the removal of such a critical VPN component get past QA? 2. How is it that the very vulnerable PPTP VPN is still readily available while a more secure option gets tossed to the gutter? Can anyone at Canonical please answer these questions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457078 Title: L2TP client support for PSK removed from 15.04/15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/1457078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437931] Re: starting stellarium causes system crash
I too am getting the same issue. However, for me the crash doesn't happen until I try to resize the window - like exiting from full screen via F11 or even just exiting the application. In addition, just attempting to switch to a different workspace also causes X/Unity to hang! On my system, CTRL+ALT+Backspace has never worked. However, I can CTRL+ALT+F1 and from there restart lightdm and all is well again! I'm running Ubuntu 15.10: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily Linux akk-m6700 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437931 Title: starting stellarium causes system crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stellarium/+bug/1437931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Touch-packages] [Bug 147216] Re: LVM filesystems not mounted at boot
Being that I'm still having this issue on Ubuntu 15.10, I can only conclude that this appears to be a design philosophy at Canonical rather than a bug. Logical volumes that are not necessary for system boot and/or are not on the primary disk where the OS is installed are not made available / mounted on (re)boot! It is much better that the system comes up rather than waiting for a user input at (re)boot. Case closed, at least for me! ak. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/147216 Title: LVM filesystems not mounted at boot Status in lvm2 package in Ubuntu: Confirmed Bug description: My system has a root filesystem in an LVM logical volume, backed up by two MD RAID-1 arrays. It fails to boot propertly after upgrading to kubuntu gutsy gibbon prerelease (latest packages as of today). In order to boot it, I have to specify the break=mount boot option, then subsequently run lvm vgscan lvm vgchange -a y to manually enable the LVM volumes. I should note that the MD arrays are started successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/147216/+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
[Bug 147216] Re: LVM filesystems not mounted at boot
Being that I'm still having this issue on Ubuntu 15.10, I can only conclude that this appears to be a design philosophy at Canonical rather than a bug. Logical volumes that are not necessary for system boot and/or are not on the primary disk where the OS is installed are not made available / mounted on (re)boot! It is much better that the system comes up rather than waiting for a user input at (re)boot. Case closed, at least for me! ak. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/147216 Title: LVM filesystems not mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/147216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Help with RegEx Rule
On 20/09/15 03:07, Dave Funk wrote: Notes: 1) Due to SA pre-processing collapsing body into one long line, cannot match on '^' repeatedly, need to look for '\n' as line break indicator. Find start of a line and then following repeats of ".\n" Dave, I need to see the mail message as spamassassin see's it so as to create some *awesome* rules; is there a tool that will let me convert my ASCII representation of an email message into a file in the rawbody format or any other format for that matter? Thanks, ak.
Re: Resume / Doc Spam
On 09/09/15 07:26, John Schmerold wrote: I haven't had the courage to open in word, if I open in 7zip, I see following files: Directory of C:\ No courage needed. Simply install Sanboxie [0] (preferably in a VM) and you can safely open any application inside the sandbox and see what it invokes. Cheers, AK. [0] - http://www.sandboxie.com/index.php?HowItWorks
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Hi there. I'm running Ubuntu Trusty Tahr (14.04) 64bit and I'm affected by this bug. By following the instructions here (especially comment #101 by Chris (poser) on 2013-09-15), I was able to get HSP/HFP working on my system. I realized something was broken when I tried to pair my Laptop with a PLCM VS500 (Voice Station conference phone) and couldn't. I was especially angry when a friend running a MacBook Air (Grrr, don't get me started...) was able to immediately pair and use the headset. My anger brought me here and I can say all is well. System Details: *** $ 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:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty My device is listed above, namely: Bus 001 Device 004: ID 413c:8197 Dell Computer Corp. iManufacturer 1 Dell Computer Corp iProduct 2 DW380 Bluetooth Module Cheers, ak. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Hi there. I'm running Ubuntu Trusty Tahr (14.04) 64bit and I'm affected by this bug. By following the instructions here (especially comment #101 by Chris (poser) on 2013-09-15), I was able to get HSP/HFP working on my system. I realized something was broken when I tried to pair my Laptop with a PLCM VS500 (Voice Station conference phone) and couldn't. I was especially angry when a friend running a MacBook Air (Grrr, don't get me started...) was able to immediately pair and use the headset. My anger brought me here and I can say all is well. System Details: *** $ 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:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty My device is listed above, namely: Bus 001 Device 004: ID 413c:8197 Dell Computer Corp. iManufacturer 1 Dell Computer Corp iProduct 2 DW380 Bluetooth Module Cheers, ak. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux” source package in Raring: Fix Released Status in “linux” source package in Saucy: Fix Released Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetoothm=132039175324993w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-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
[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 Ubuntu Bugs, which is subscribed to 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) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1149092] Re: mouse scroll wheel not working in Launcher
*** This bug is a duplicate of bug 1173623 *** https://bugs.launchpad.net/bugs/1173623 It is time to leave the Ubuntu field and try something else. I pity non-techies as they are left with no option but to cope with this ridiculous crippling of a perfectly working feature just 'cause a developer decided (with their infinite wisdom) that they prefer to use two hands than one to scroll though a list of items - really? I hope that Mozilla developers do not go down the same road and start requiring us to depress ctrl+shift while scrolling in Firefox, then they go ahead and state it is intended behaviour - just plain silly! Well, I guess I'll stop ranting to deaf ears and move on to Arch! Ciao, ak. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1149092 Title: mouse scroll wheel not working in Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1149092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147216] Re: LVM filesystems not mounted at boot
Forgot to add that the LV's are for media files and virtualbox vms so the system could otherwise boot (if I chose to skip mounting the LV's via 'S'). I'd than still have to run 'vgchange -ay' then manually mount the partitions after the system was up. Cheers, ak. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/147216 Title: LVM filesystems not mounted at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/147216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147216] Re: LVM filesystems not mounted at boot
Just wanted to add that after doing a vgrename without first doing a
vgchange -an, I ended up with a system that could not activate the LV's
on boot. I had to drop to a root shell (via 'M') then type vgchange
-ay followed by ctrl+d to get a system (re)boot to complete
successfully. I'll add that I'm not sure if the vgrename without first
making unavailable caused the issue!!!
Anyhow, after much googling, I came across this bug and after following
the suggestion by Mark Tomich, namely:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_TYPE}==disk, \
RUN+=watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'
I can now (re)boot without it stopping to wait for manual intervention.
My system:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.4 LTS
Release:12.04
Codename: precise
$ uname -a
Linux akk-m6700 3.11.0-19-generic #33~precise1-Ubuntu SMP Wed Mar 12 21:16:27
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
I'm running the kernel from - linux-image-generic-lts-saucy.
Cheers,
ak.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/147216
Title:
LVM filesystems not mounted at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/147216/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [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 Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273832/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat 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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273832 Title: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [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 Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273832/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273832 Title: [fglrx] Lockscreen/lid-close xserver freeze if UXA accel used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249067 Title: nvidia prime causes freeze at start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [CentOS] Hanging issue with sudo command
On 19/06/12 00:29, Kaplan, Andrew H. wrote: Recently it was observed the user account took longer to complete its login from a terminal window and console. It is also now having problems when running the sudo command. Essentially when the user runs the command, the latter hangs, and the administrator is forced to log in as root, and kill the hung progress. What would cause this issue to occur, and how can it be corrected? Thanks. Any recent changes to DNS settings on server? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RAR from Console
On Tue, 2010-01-26 at 01:04 -0500, Alberto García Gómez wrote: Hi fellows, how can I unrar (.rar of course) from my console? What package do I need? yum search unrar ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] update of openssh-server i386 4.3p2-36.el5, dependencies
On Tue, 2010-01-12 at 10:39 +0100, Christopher Thorjussen wrote: Just checking 'yum update ecryptfs-utils' gives me alone 54 packages to install: Transaction Summary = Install 54 Package(s) Update 5 Package(s) Remove 0 Package(s) Total download size: 25 M Is this ok [y/N]: n Exiting on user Command Is there no way out of getting all these extra packages? Maybe you could use 'exclude=ecryptfs*' (or whatever is causing ecryptfs* to be included in the update) in /etc/yum.conf then run your update. Once the issue is resolved, don't forget to remove the exclude line for future updates??? Just a thought. Cheers, ak. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.4 and BitTorrent
On Thu, 2009-10-15 at 16:01 -0700, nate wrote: Could someone describe to me what the rush is? I mean what drives the need that you need to have it _right now_ ? Me I always like to wait at least a week or two to see if others run into issues, and wait for the mirrors to become less clogged. nate But if we all take the same stance, then where will you get your baseline to help determine if there are any issues with new packages? ak. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum update gone bad...
Here's some additional info to the problem: I created a VM to watch it boot up so I could see what was happening where. Well, the first step where the scrolling text stops is as shown below: SELinux: Disabled at runtime. Type=1404 audit(1242405997.079:2): selinux=0 auid=4294967295 ses=4294967295 On my main server, nothing else appears here until I get the login prompt. On the VM I see right after the SELinux stuff above the following: INIT: version 2.86 booting Welcome. So what would cause messages spewed by INIT not show up and also the lack of the kernel selection screen and also kill output to the serial console? Tia, tkb. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Yum update gone bad...
Morning list! I have a situation that was brought about by a system crash during a yum update. The motherboard suffered a catastrophic failure due to busted CAPS. Lucky for me (or so I thought at the time), I had a spare, identical motherboard as the one that failed. I replaced the dud board and rebooted. This machine runs headless and is my primary (personal/home) mail server. I normally access the booting console via hyper terminal when I need to change boot parameters or just watch the system boot up! Getting to the point, nothing comes up at all on the terminal screen. So I hooked up a monitor and keyboard (even a mouse) to check what was going on. What I noticed immediately was that the kernel screen selection screen did not appear! Instead, I just got a message at the bottom on the screen stating Grub Loading Stage 2 or something to that effect. Straight from there, was the usual scrolling text up to the point where SELinux starts. Then nothing displays at all until the final login screen. Not even the Nash screen that prompts one to enter I for interactive start-up appeared! Could someone enlighten me on what I could check? I have reinstalling all packages that were installed just before and after the system crash to no avail. This is a system that was running CentOS 5.3 final and I was updating several packages including upgrading the kernel from 2.6.18-128.1.6.el5 to 2.6.18-128.1.10.el5. Cheers, tkb. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Rsync/SSH automation problem?
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Kai Schaetzl Sent: Wednesday, 29 April 2009 9:09 PM To: centos@centos.org Subject: Re: [CentOS] Rsync/SSH automation problem? is a quote marker, don't write your own text after a quote marker! I totally understand how to quote messages when replying to posts in newsgroups. I've just checked my sent items folder and the message did not go out with the you talk about!!! I'm not sure where it got injected into the message before getting to the newsgroup! Tia, Tkb. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Rsync/SSH automation problem?
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of James Bensley Sent: Wednesday, 29 April 2009 6:54 PM To: CentOS mailing list Subject: Re: [CentOS] Rsync/SSH automation problem? hi Kai, You can't. Thats what I thought, I have been looking into using certificates and passphrases and that will have to be it! Interesting - why not do a pull from the CentOS box? This would only work if the machines are local to each other! I mount Windows Server 2003 as follows: mount //[servername]/C$ /winmnts/[servername]/cdrive \ -o credentials=/root/sysaccess /root/sysaccess - contains just two lines: username=[administrative account] password=[administrative account password] Also, you'll need to have created the path /winmnts/[servername]/cdrive beforehand (as if you hadn't guessed that already)! From here, I run the rsync command without the need for the -e option. Of course, if the servers are in geographically different locations, then Kai's link is the way to go! Cheers, Tkb. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] repository for mod_security
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Bowie Bailey Sent: Saturday, 25 April 2009 6:27 AM To: CentOS mailing list (E-mail) Subject: [CentOS] repository for mod_security I want to add mod_security to my Apache server running CentOS 5.3 and am trying to find a repository to get it from. I found it in EPEL, but they have version 2.1.7, which is over a year old according to what I found on the modsecurity.org website. Is there a repository which is keeping this up to date? Or should I just build it from source? Interesting that you are finding version 2.1.7 - just did a quick check and I see version 2.5.9 on epel: Name : mod_security Arch : i386 Version: 2.5.9 Release: 1.el5 Size : 933 k Repo : epel My epel.repo file looks like this: [epel] name=Extra Packages for Enterprise Linux 5 - $basearch #baseurl=http://download.fedoraproject.org/pub/epel/5/$basearch mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5arch= $basearch failovermethod=priority enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL protect=0 priority=12 Cheers, Tkb. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 5.3 Update Problem clamav-milter
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Leo Arnts Sent: Sunday, 5 April 2009 5:20 PM To: centos@centos.org Subject: [CentOS] 5.3 Update Problem clamav-milter After performing an update from CentOS 5.2 to 5.3 with yum update I have an error with clamav-milter The clamav-milter won't start. [r...@is3 sysconfig]# service clamav-milter restart Stopping Clamav Milter Daemon: [FAILED] Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options [FAILED] The config of /etc/sysconfig/clamav-milter CLAMAV_FLAGS= --config-file=/etc/clamd.conf --local --max-children=10 --outgoing --quiet SOCKET_ADDRESS=local:/var/run/clamd.socket Had the same error on upgrade! It appears that ClamAV people have decided to do away with /etc/sysconfig/clamav-milter altogether. Get rid of the file above and modify /etc/clamav-milter.conf instead and make the necessary changes. Most important is to comment out the Example line near the top of that file. Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] hdc: no DRQ after issuing MULTWRITE
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Robert Moskowitz Sent: Thursday, 29 January 2009 5:30 AM To: CentOS mailing list Subject: [CentOS] hdc: no DRQ after issuing MULTWRITE Any idea what can be done? They seem to be more nuance that not, but if I am in init 3 mode and in VI and get one of these messages in the middle of editing some file, well, I typically :q! out and start over. man dmesg suggests that running the command `dmesg -n1' should stop you getting messages on the console other than panic messages! But all in all, you probably want to fix the issue to avoid filling up your logs with crap messages; for that, I have no solution! Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum problem
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of James Bensley Sent: Tuesday, 27 January 2009 7:49 PM To: CentOS mailing list Subject: Re: [CentOS] yum problem It doesn't matter if its in resolv.conf you don't seem to have a working DNS provider. I would start there, use nslookup, can you solve anything? Check with your resolv.conf, what name server are you using, can you ping it? Try another name server? If all else fails, then you can use opendns.com - they provide their services for free! Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: Daily run output
-Original Message- From: Benny Pedersen [mailto:m...@junc.org] Sent: Monday, 12 January 2009 4:13 AM To: users@spamassassin.apache.org Subject: RE: Daily run output On Sun, January 11, 2009 03:08, Anthony Kamau wrote: 2/ Locate the line starting with 'root:' in the file '/etc/aliases' and change it to look like this: root: sysnotify root: dest1, dest2 why add unneeded new users ? -- Benny Pedersen Need more webspace ? http://www.servage.net/?coupon=cust37098 I wasn't aware you could use an e-mail address in the form usern...@domain.com in the aliases file. I guess I need to read a bit more on the alias file! Cheers, AK.
RE: Daily run output
-Original Message- From: Benny Pedersen [mailto:m...@junc.org] Sent: Monday, 12 January 2009 4:13 AM To: users@spamassassin.apache.org Subject: RE: Daily run output On Sun, January 11, 2009 03:08, Anthony Kamau wrote: 2/ Locate the line starting with 'root:' in the file '/etc/aliases' and change it to look like this: root: sysnotify root: dest1, dest2 why add unneeded new users ? -- Benny Pedersen Need more webspace ? http://www.servage.net/?coupon=cust37098 I wasn't aware you could use an e-mail address in the form usern...@domain.com in the aliases file. I guess I need to read a bit more on the alias file! Cheers, AK.
RE: Daily run output
-Original Message- From: Simon.Baker [mailto:simon_ba...@medfin.com.au] Sent: Thursday, 8 January 2009 4:19 PM To: users@spamassassin.apache.org Subject: Daily run output Hi, We have a spamassassin server filtering our companies emails currently. Each day we recieve an email from the root account of our server overviewing the previous days spam filtered emails, network status and disk status. As i was not the one who setup the server, i'm not sure exactly how it's all configured. Could someone tell me what configuration file i need to change in order to change the email address this email is being sent to? Regards, To change the address where cron job messages are sent, follow directions given by Rubin Bennett. If you only want to change where logwatch messages go, then add a 'MailTo = ' entry into the file '/etc/logwatch/conf/logwatch.conf' - defaults are saved in the file '/usr/share/logwatch/default.conf/logwatch.conf' If however, you want to redirect all messages sent to user 'root' to another user account or even to a group, here's what you need to do: 1/ Create a new user account - a good name is 'sysnotify' 2/ Locate the line starting with 'root:' in the file '/etc/aliases' and change it to look like this: root: sysnotify 3/ Create the file 'home/sysnotify/.forward' and add the follwing to it: us...@domain.com,us...@domain.com,us...@domain.com,[local logon id],... You can add as many e-mail addresses as you like as long as you comma separate them! If you want the message sent a user on the same system that has an account on the box, then you can simply enter that users logon id. If you want a copy left in the 'sysnotify' account, then you need to enter '\sysnotify' into that file. The '\' ensure that a loop is not created! The assumption I made for the above is that you are running a Red Hat Linux based Linux server such as Red Hat itself, Fedora Core, or CentOS. Cheers, Anthony.
RE: [CentOS] yum: not updating kernel
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, 14 October 2008 2:25 PM To: CentOS mailing list Subject: [CentOS] yum: not updating kernel Hi. I recently switched my CentOS kernel to 2.6.27, manually. Is there a way to take it off the list of possible yum updates? I want to handle kernel stuff myself. Edit /etc/yum.conf Below excerpt from `man yum.conf' exclude List of packages to exclude from updates or installs. This should be a space separated list. Shell globs using wildcards (eg. * and ?) are allowed. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Network issues with CentOS 5.2
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joey Mendez Sent: Friday, 19 September 2008 9:09 AM To: centos@centos.org Subject: [CentOS] Network issues with CentOS 5.2 Snip DHCP. I connected to the net fine and began downloading open office. I left for the day and came back and I can no longer get back online. The eth-0 wont even activate unless I manually enter a static IP but still can not establish a connection online. I treid reinstalling to no avail. Even built a completely new box and still no avail. I am using CentOS 5.2 i386 DVD. I experienced something similar and it turned out that if you run an update and the kernel changes, then you need to update the network drivers to match up with the installed kernel. If you provide details on the type of NIC on your system, I may be able to provide more help. Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [Clamav-users] failed updates
-Original Message- From: [EMAIL PROTECTED] [mailto:clamav-users- [EMAIL PROTECTED] On Behalf Of Chris Sent: Saturday, 6 September 2008 10:47 AM To: ClamAV users ML Subject: [Clamav-users] failed updates The next time freshclam is run there are no issues, then it may update a couple more times then fail again. Anyone have any ideas on this? Yeah, delete /var/clamav/mirrors.dat. That will force a rebuild of the file on next update. I've modified the /etc/cron.daily/freshclam and added the following code after the line that reads LOG_FILE=/var/log/clamav/freshclam.log: x=`tail -1 $LOG_FILE|egrep '^Update failed.'|wc -l` if [ $x = 1 ]; then rm -f /var/clamav/mirrors.dat fi When an update fails, the last line starts with Update failed... HTH, AK ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] announcing ClamAV 0.94rc1
-Original Message- From: [EMAIL PROTECTED] [mailto:clamav-users- [EMAIL PROTECTED] On Behalf Of Charles Gregory Sent: Wednesday, 20 August 2008 11:56 PM To: ClamAV users ML Subject: Re: [Clamav-users] announcing ClamAV 0.94rc1 I recently *stopped* advising our members to use AVG Free edition because the latest download had bloated to nearly 40MB. That's roughly SEVEN hours on a dial-up connection. I've started to recommend ClamWin, but that package is also slowly increasing in size. It's up to 21MB. Still, ClamAV has the most efficient updates I've seen (smile) - Charles Yeah - I'm smiling too - 72MB for an entire month for ~100 machines on a network - that's just bloody cool bananas! Calculations: Machines with ClamAV - 100 Updates - 1 per hour daily-.cdiff size - ~1024 bytes Machine on-time - 24 hrs Bandwidth per day = ~2.4MB Bandwidth per month (31 days) - ~72MB Bloody terrific!!! I don't see any other AV package coming anywhere close! ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
RE: Sendmail Question [OT]
-Original Message- From: Marc Perkel [mailto:[EMAIL PROTECTED] Sent: Saturday, 19 July 2008 5:14 AM To: Spamass Subject: Sendmail Question [OT] Just a quick sendmail question I'm asking for a friend. If they want to make sendmail listen on port 2525 instead of 25 - what do they meed to change? Email me privately off list. Thanks in advance You can also leave sendmail as it is and on the firewall, drop packets going to port 25 and redirect traffic on port 2525 to port 25 on the machine running sendmail: iptables -A FORWARD -p tcp --dport smtp -j DROP iptables -t nat -A PREROUTING -p tcp --dport 2525 -j DNAT --to-destination server:25
RE: [CentOS] Bonding and Xen
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Victor Padro Sent: Wednesday, 16 July 2008 8:34 AM To: CentOS mailing list Subject: Re: [CentOS] Bonding and Xen We're not using windows under Xen, we're trying to get rid of M$(reducing licensing fees mostly). Pray tell, what are you replacing Exchange with? My end users are dependent on Exchange for calendaring but organization is becoming more and more anti MS and it won't be long before they decide enough is enough, especially being that some savvy users refused to upgrade to Vista and are now using CentOS as their preferred desktop. These savvy users are software developers who were previously using XP and multiple PuTTY sessions to get the job done! Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Rsync + crontab centos5.1
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank Murphy Sent: Sunday, 22 June 2008 9:38 PM To: CentOS User-List Subject: [CentOS] Rsync + crontab centos5.1 Just looking at the man rsync. Might as well be duagnosing a plattypus. I have made a dir on my Cent samba shares to setup a local fedora.repo (1) How do I get it to run weekly at a certain time. is this correct? crontab -e 22 7 0 0 /usr/bin/rsync -va This is what I added to the top of my /etc/crontab file to remind me what goes where: SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin:/root/bin MAILTO=root HOME=/ # * * * * * 'command to be executed - preceed with a usersname (such as root) # | | | | | to run command as that user' # | | | | | # | | | | +- day of week (0 - 6) (0 = Sunday) # | | | +--- month (1 - 12) # | | +- day of month (1 - 31) # | +--- hour (0 - 23) # +- min (0 - 59) # an asterix (*) in any field matches all values. # To create a periodic event, use */n where n is the required period. # For instance, to run a command every 5 minutes, do the following # */5 * * * * 'command to be executed' Hope it helps clean the issue of setting up a cron job. As for rsync, maybe I'll know better when I'm done setting up a cluster system which I'm in the middle of. Cheers, AK. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: Temp fail not working...
-Original Message- From: Jari Fredriksson [mailto:[EMAIL PROTECTED] Sent: Saturday, 24 May 2008 12:54 PM To: Anthony Kamau; users@spamassassin.apache.org Subject: Re: Temp fail not working... Hey! Do not mix options for spamc and spamass-milter! Put all the options back as they were, and then (I do not know spamass-milter, but your message has the help in it!) add -- -x to the end of the milter call. See the last line of then milter usage: -- spamc args: pass the remaining flags to spamc. -x for milter is different from -x for spamc! Same goes with -f and -F !! Thanks so much Jari for sorting me out. Your help was invaluable! All is now working as I was hoping it would. Cheers, AK.
RE: Temp fail not working...
-Original Message- From: Jari Fredriksson [mailto:[EMAIL PROTECTED] Sent: Friday, 23 May 2008 3:29 PM To: Anthony Kamau; users@spamassassin.apache.org Subject: Re: Temp fail not working... Do you have -x in your call to spamc? Thanks for that. I added that option to the startup script and restarted spamc (service spamass-milter restart) then killed spamd (service spamassassin stop). Oddly enough, messages are still being delivered by sendmail!!! I then checked the process list and saw the following: /usr/bin/spamd -d -c -m5 -H -x -q -u spambucket -r /var/run/spamd.pid spamass-milter -p /var/run/spamass.sock -f -x Further reading of `man spamc' revealed that option `-f' is non-existent (at least not mentioned in my spamc man pages); there's only a `-F' option - so why do I have this option that appears to do nothing for me? Could it be that it was meant to be `-F'? Well, I removed that option from the startup script and on trying to start the service, it hang indefinitely! I then added `-F' in its place and I got the following output: ### [EMAIL PROTECTED] ~]# sudo /sbin/service spamass-milter start Starting spamass-milter: spamass-milter: invalid option -- F spamass-milter - Version 0.3.1 SpamAssassin Sendmail Milter Plugin Usage: spamass-milter -p socket [-b|-B bucket] [-d xx[,yy...]] [-D host] [-e defaultdomain] [-f] [-i networks] [-m] [-M] [-P pidfile] [-r nn] [-u defaultuser] [-x] [-- spamc args ] -p socket: path to create socket -b bucket: redirect spam to this mail address. The orignal recipient(s) will not receive anything. -B bucket: add this mail address as a BCC recipient of spam. -d xx[,yy ...]: set debug flags. Logs to syslog -D host: connect to spamd at remote host (deprecated) -e defaultdomain: pass full email address to spamc instead of just username. Uses 'defaultdomain' if there was none -f: fork into background -i: skip (ignore) checks from these IPs or netblocks example: -i 192.168.12.5,10.0.0.0/8,172.16.0.0/255.255.0.0 -m: don't modify body, Content-type: or Subject: -M: don't modify the message at all -P pidfile: Put processid in pidfile -r nn: reject messages with a score = nn with an SMTP error. use -1 to reject any messages tagged by SA. -u defaultuser: pass the recipient's username to spamc. Uses 'defaultuser' if there are multiple recipients. -x: pass email address through alias and virtusertable expansion. -- spamc args: pass the remaining flags to spamc. [FAILED] [EMAIL PROTECTED] ~]# ### This is when I realized that the man page falsely states what the `-x' option does, and as seen above, there isn't even a -F option as stated in the man pages. From the above, it is clear what `-x' does: -x: pass email address through alias and virtusertable expansion. I also understand why when I killed the Ctrl-C'd from the hang session, I got the [OK] message; the process was not forking to the background! So, is it that I have a real old version of spamass-milter? Odd thing is that I cannot find a newer version!!! Puzzled, AK.
RE: Temp fail not working...
-Original Message- From: Jari Fredriksson [mailto:[EMAIL PROTECTED] Sent: Saturday, 24 May 2008 12:54 PM To: Anthony Kamau; users@spamassassin.apache.org Subject: Re: Temp fail not working... Hey! Do not mix options for spamc and spamass-milter! Put all the options back as they were, and then Thanks for setting me on the straight and narrow. I now clued in on what I'm doing wrong! Cheers, AK.
Temp fail not working...
Hello all. My spamass-milter INPUT_MAIL_FILTER config in sendmail is as follows: INPUT_MAIL_FILTER(`spamassassin',`S=local:/var/run/spamass.sock,F=T, ...)dnl Yet when I test this feature by manually shutting down spamassassin (service spamassassin stop), I still receive messages. Shouldn't they be temp failed? What I see in the logs is 3 failed attempts by spamass-milter (spamc) to connect to spamassassin (spamd) after which sendmail delivers the message to the recipient: May 23 13:57:43 mail spamc[10285]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused May 23 13:57:44 mail spamc[10284]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused May 23 13:57:44 mail spamc[10285]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused May 23 13:57:45 mail spamc[10284]: connection attempt to spamd aborted after 3 retries May 23 13:57:45 mail spamc[10285]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused May 23 13:57:46 mail sendmail[10287]: STARTTLS=client, relay=server.mydomain.local., version=TLSv1/SSLv3, verify=FAIL, cipher=RC4-MD5, bits=128/128 May 23 13:57:46 mail sendmail[10287]: m4N3va6b010268: to=[EMAIL PROTECTED], delay=00:00:06, xdelay=00:00:00, mailer=smtp, pri=127244, relay=server.mydomain.local. [10.1.1.2], dsn=2.0.0, stat=Sent ( [EMAIL PROTECTED] Queued mail for delivery) I absolutely need to have all messages scanned for SPAM - too much of it in our domains! What can I do to rectify this issue? Server config: OS - Red Hat Enterprise Linux AS 4 (Nahant) Sendmail - 8.13.1-2 spamass-milter - 0.3.1 spamassassin - 3.1.7 (2006-10-05) Perl - 5.8.5-12 Cheers, AK.
RE: Temp fail not working...
-Original Message- From: Anthony Kamau [mailto:[EMAIL PROTECTED] Sent: Friday, 23 May 2008 2:07 PM To: users@spamassassin.apache.org Subject: Temp fail not working... I absolutely need to have all messages scanned for SPAM - too much of it in our domains! What can I do to rectify this issue? After further diagnosis, it appears that if I keep spamassassin running but busy enough not to respond to new connections, then new connections will be temp failed. Maybe I have it all wrong, but I'd think that one would like it to temp fail whether or not spamassassin is running!!! Can someone please set me on the straight and narrow, please? It is killing me when I get all sorts of complaints from my users when they get spam that is not tagged! Company policy dictates that all mail is delivered as long as it is scanned for spam and viruses! Cheers, AK.
RE: [sa-list] Re: Auto-RBL was: Why did this not hit more? (SPF, DKIM, Ironport,
-Original Message- From: Dan Mahoney, System Admin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 9 October 2007 7:14 AM To: Rob McEwen Cc: users@spamassassin.apache.org Subject: Re: [sa-list] Re: Auto-RBL was: Why did this not hit more? (SPF, DKIM, Ironport, On Mon, 8 Oct 2007, Rob McEwen wrote: Therefore, I recommend that you re-think your choices here! Don't let your quest for guaranteed long-term perfection keep you from making **substantial** progress today! Rob, Then help rally the SA team to include those RBLs that you mentioned in the stock config. Also, rally them to update the documentation on the wiki on how to configure SA for third-party DNSBL's, because it blows (and refers to years-old versions of SA). Yes, I know the point of a wiki is that ANYONE can update it, but I'm not about to update it with information I don't understand for certain. You should update the Wiki nevertheless and append a disclaimer of sorts! Choosing not to update in fear of appearing clueless is just lame! If you believe that what you are posting is halfway valid, then someone else can update. This is the sole function of a Wiki as otherwise there'd be no need for an UPDATE function!!! . . .
RE: OT Alert: Forward low scoring SPAM to sa-learn.
-Original Message- From: Michael Scheidell [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 July 2007 2:51 PM To: Anthony Kamau; users@spamassassin.apache.org Subject: RE: OT Alert: Forward low scoring SPAM to sa-learn. Only hope it to create shared, public folders for them to move the email to and have a separate program use imap to that folder to read the email (again, google is your friend, there are several programs like this for SA out there) Thanks Michael. I've always known that Google is my friend, but creativity with search terms eludes me -:). After reading your response, I quickly Googled imap exchange sa-learn and up came 794 links. The link at the top [1] provides all the details I need! [1] - http://www.ctdx.net/2006/10/27/spamassassin-linux-exchange-imap/ Cheers, AK.
RE: OT Alert: Forward low scoring SPAM to sa-learn.
-Original Message- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 July 2007 11:35 AM To: Anthony Kamau Cc: users@spamassassin.apache.org Subject: Re: OT Alert: Forward low scoring SPAM to sa-learn. That said, if you're just doing a forward as attachment type operation, you should be able to get any standard mime attachment extractor tool.. Thanks Matt, I was planning on having the users forward the spam/ham as an attachment, but that was before I read Michael's post. All should be well unless I have other issues with the script... Cheers, AK.
OT Alert: Forward low scoring SPAM to sa-learn.
Hello all. I'm faced with a dilemma on how to use sa-learn with mail forwarded from a user's inbox on Exchange to the sendmail server. Since we just recently started using sendmail as a front end server, our bayes system is still in its infancy and spam is getting through to user inboxes with scores lower than our threshold of 10 and thus not being clearly identified as spam on the subject line. My intention is to have a user forward spam back to sendmail server and use sa-learn to help the scoring system get better fast. Here's what I've done so far: I have created two email addresses for this purpose; [EMAIL PROTECTED] for spam and [EMAIL PROTECTED] for false positives. I have created a connector that forwards all email destined for mail.domain.com back to the sendmail server and messages are getting into the appropriate mailboxes. The next step is what has me stunned - is there a standard marker to look out for that segregates the attachment from the mail sending the attachment? Any help would be mightily appreciated. Cheers, AK.
RE: Problems with Received: header checks and ALL_TRUSTED rule...
I've checked my logs and noticed the following entry whenever I restart the spamassassin service: config: dup unknown type msa_networks, Mail::SpamAssassin::NetSet Is this something I should be worried about? Cheers, AK. -Original Message- From: Anthony Kamau [mailto:[EMAIL PROTECTED] Sent: Wednesday, 13 June 2007 5:12 PM To: Daryl C. W. O'Shea Cc: SpamAssassin Mailing List Subject: RE: Problems with Received: header checks and ALL_TRUSTED rule... Thanks a ton Daryl. I've patched my SA 3.1.7 per [1] and it is working as expected. Cheers, AK.
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Thanks Daryl. That error is now no more. Cheers, AK. -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Monday, 18 June 2007 12:59 PM To: Anthony Kamau Cc: SpamAssassin Mailing List Subject: Re: Problems with Received: header checks and ALL_TRUSTED rule... As long as you don't have any users calling clear_msa_networks in their per user config I believe it's a harmless warning. In any case, attached is a patch to correct the issue. Daryl
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Daryl, You'll be glad to know that I'm now rejecting at RCPT instead of blindly forwarding to the exchange box! We don't have numerous updates in active directory so for now I'm doing a manual export to the sendmail box. Cheers, AK. -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Thursday, 14 June 2007 11:53 AM To: Anthony Kamau Cc: SpamAssassin Mailing List Subject: Re: Problems with Received: header checks and ALL_TRUSTED rule... In any case, spamming people with backscatter in the form of NDRs from your system is completely unacceptable. You have at least three options to prevent this; (i) configure out how to do LDAP queries from Sendmail against your Exchange system to verify addresses, or (ii) use a milter such as Anthony Howe's milter-ahead (which I believe he licenses for 90 Euros), or (iii) export all of your addresses to your Sendmail box. Daryl
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Thanks Kris. OT I Googled for MIMEDefang and AD and came across this post [1] by Brian at RoaringPenguine; he suggests not to use MIMEDefang as it imposes a heavy load on Exchange/AD on Windows 2003. He provides an alternative by releasing 2 scripts that automate the harvesting of email addresses from AD via LDAP and dumps those addresses into the accessdb file to filter on. Not wanting to cause performance issues on the Exchange box, I'll try this 'easy' way out first! [1] http://lists.roaringpenguin.com/pipermail/mimedefang/2003-December/01863 3.html Cheers, AK. -Original Message- From: Kris Deugau [mailto:[EMAIL PROTECTED] Sent: Friday, 15 June 2007 12:56 AM To: users@spamassassin.apache.org Subject: Re: Problems with Received: header checks and ALL_TRUSTED rule... Anthony Kamau wrote: OT Any chance you know of a quick and dirty method to implement sendmail AD authentication? I did search during build of the sendmail box, but did not find conclusive instructions to do so - possibly because I was under immense pressure to get a spam identifier installed. /OT Check out MIMEDefang, http://www.mimedefang.org. Among other things, it can do exactly this in several ways, and may also help with your problem of spam-tagged mail having the spam tags stripped off in some cases. -kgd
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Thanks Daryl. I've done a little bit of reading on msa_netowrks and it appears I need to upgrade to SA 3.2.x to get this added benefit - correct? Cheers, AK. -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Wednesday, 13 June 2007 4:07 PM To: Anthony Kamau Cc: SpamAssassin Mailing List Subject: Re: Problems with Received: header checks and ALL_TRUSTED rule... Anthony Kamau wrote: How then can I tell spamassassin to fire the ALL_TRUSTED rule if the connecting host is on the trusted list and ignore further Received: header checks? I have read Mail::SpamAssassin::Conf help file but cannot find the solution yet. I thought the whitelist_allows_relays would help, but I'm not too sure what that does! Is there a better source of documentation somewhere? msa_networks
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Thanks a ton Daryl. I've patched my SA 3.1.7 per [1] and it is working as expected. Cheers, AK. -Original Message- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Wednesday, 13 June 2007 4:15 PM To: Anthony Kamau Cc: SpamAssassin Mailing List Subject: Re: Problems with Received: header checks and ALL_TRUSTED rule... That's only available with 3.2, though, so you'll either need to patch SA [1] or do something else [2]. Daryl [1] http://people.apache.org/~dos/sa-patches/msa_networks.3.1 [2] http://wiki.apache.org/spamassassin/DynablockIssues
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Hey Daryl, et al, I've just discovered something rather interesting after I enabled the msa_networks feature in local.cf. What's happening is this: 1/ spam arrives at the sendmail box from someone who has used a non-existent email address in our domain 2/ spamassassin clearly marks this as spam, sendmail adds the necessary headers, modifies the subject and relays to exchange 3/ if exchange is configured to send a copy of received email to an external account OR the message is destined for a non-existent mailbox, exchange will initiate a connection with sendmail either for forwarding mail or for NDR 4/ since the exchange box is now trusted via msa_networks, the email receives a clean bill of health from spamassassin and sendmail proceeds to remove the headers previously added for the incoming message except for the subject line which is left with the previously changed header! How can I tell sendmail milter not to remove any of the headers as the email message is really still spam??? Although we could drop all spam and forget about this whole issue, company policy dictates that any email destined to an existing recipient mailbox will be delivered be it spam or not (false positives in the past have left many weary of lost email)! Cheers, AK.
RE: Problems with Received: header checks and ALL_TRUSTED rule...
Thanks Robert. And you are correct - the exchange rejects mail destined to non-existent mailboxes! Due to lack of time, I have not yet found a quick method to have sendmail authenticate against active directory so I've instructed sendmail to relay all mail and leave it to exchange to deal with rejection and NDR's. OT Any chance you know of a quick and dirty method to implement sendmail AD authentication? I did search during build of the sendmail box, but did not find conclusive instructions to do so - possibly because I was under immense pressure to get a spam identifier installed. /OT Cheers, AK. -Original Message- From: Robert - eLists [mailto:[EMAIL PROTECTED] Sent: Thursday, 14 June 2007 10:47 AM To: users@spamassassin.apache.org Subject: RE: Problems with Received: header checks and ALL_TRUSTED rule... AK, The MTA should not accept email for non existent email addresses - rh
