[Kernel-packages] [Bug 577114] Re: [Lenovo IdeaPad S10-3] Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3
After long time I am happy now, because I surprisingly found a workaround that fixed this issue for me, with neither opening the case nor using/installing any proprietary software like Windows, etc. I booted with a KALI-Linux Live-CD to try to recover some lost pictures from an IPhone that got deactivated because the children entered a wrong passcode too often... Then KALI-Linux told me that the Airplane mode is on and I should use the hardware switch to turn it on. Thus I turned it off and on again, the same procedure which was useless for so long time with ubuntu. When I turned the switch on again, there was some disc activity and suddenly Wireless LAN started working again and I could connect to WLAN. After some unsuccessful tries with the IPhone :-( I was leaving KALI- Linux and booting from hard disk again, and found: Wireless LAN is still working! :-) Then I stored the nvram and compared with and old nvram image: They both have the same size and MD5sum. Thus the information if the hardware switch is on or off seems to be stored somewhere else, but not in the area used for nvram. Probably the flash memory available is bigger than the area used for nvram and the information is stored somewhere else. As KALI Linux is Open-Source, it is very likely that it is possible to find a solution for Ubuntu and to try out what turns Wireless on or off. Here is a small HOWTO howto fix the issue: (I wrote it very detailled, so that almost everybody that finds this here can use it) - Download Kali Linux: https://www.kali.org/ and download directory is http://cdimage.kali.org/kali-2016.1/ wget http://cdimage.kali.org/kali-2016.1/kali-linux-2016.1-amd64.iso wget http://cdimage.kali.org/kali-2016.1/SHA1SUMS wget http://cdimage.kali.org/kali-2016.1/SHA1SUMS.gpg - Check that your download is not corrupt and is authentic gpg --verify SHA1SUMS.gpg SHA1SUMS The output should be as follows: gpg: Unterschrift vom Mi 20 Jan 2016 21:37:00 CET mittels RSA-Schlüssel ID 7D8D0BF6 gpg: Korrekte Unterschrift von »Kali Linux Repository « gpg: WARNUNG: Dieser Schlüssel trägt keine vertrauenswürdige Signatur! gpg: Es gibt keinen Hinweis, daß die Signatur wirklich dem vorgeblichen Besitzer gehört. Haupt-Fingerabdruck = 44C6 513A 8E4F B3D3 0875 F758 ED44 4FF0 7D8D 0BF6 Now you know that the SHA1SUMS file has been signed with the key, but you still cannot trust the key. Compare the fingerprint with the one listed on https://www.kali.org/downloads/ and check the https// certificate. If you trust the https// certificate an the finger print there equals the one from gpg --verify, then you can trust the key used for the signature and the signed file. Now you need to check the file against the trusted SHA1SUM sha1sum -c SHA1SUMS The output should be as follows: kali-linux-2016.1-amd64.iso: OK ... If you didn't download all the other files mentioned in the SHA1SUM file, SHA1SUM will complain about the other files, but that can be igored. The SHA1SUM of the file should be: deaa41c5c8f26b7854cafb34b6f1b567871c4875 kali-linux-2016.1-amd64.iso Now you can be quite sure that you got an authentic copy of KALI-Linux and can write it onto a DVD: growisofs --dvd-compat -Z /dev/dvd=kali-linux-2016.1-amd64.iso Then boot your Lenovo ideapad from this CD (you need an external DVD drive for it). In the network settings dialog try to enable WLAN. If it does not get detected immediately, turn the Wireless Switch off and after some seconds on again. Now the wireless LED should be on and Wireless should work. You can then shutdown KALI Linux and boot into the installed system and Wireless should still work as it should. -- 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/577114 Title: [Lenovo IdeaPad S10-3] Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: linux-image-2.6.32-21-generic I have installed Ubuntu from CD [Ubuntu-Netbook 10.04 _Lucid Lynx_ - Beta i386 (20100318)] Wireless has been detected automatically and everything worked fine. One day after installing updates on the 26.04.2010, i noticed that after Booting the Wireless interface and bluetooth is disabled, regardless of the wireless switch. It seems that the switch is turned off, regardless if the switch is on or off, even Fn-F5 (Software-Switch for Wireless/Bluetooth) does not help. WORKAROUND: After a suspend and wake, do: sudo rmmod ath9k sudo modprobe ath9k Then wireless is available and connects automatically. Bluetooth is also available. Everything works fine then. But when booting the kernel from power off, the wireless led is on when grub is shown and gets turned off, when the kernel boots and both, Wlan and Bluetooth are disabled. When Wlan is working and
[Kernel-packages] [Bug 577114] Re: [Lenovo IdeaPad S10-3] Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3
Note: the kali-linux-2016.1-amd64.iso image is 2,8G big and won't fit on a CD. So you need to take a DVD to write it on, even if I wrote CD somewhere in the text above. -- 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/577114 Title: [Lenovo IdeaPad S10-3] Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Binary package hint: linux-image-2.6.32-21-generic I have installed Ubuntu from CD [Ubuntu-Netbook 10.04 _Lucid Lynx_ - Beta i386 (20100318)] Wireless has been detected automatically and everything worked fine. One day after installing updates on the 26.04.2010, i noticed that after Booting the Wireless interface and bluetooth is disabled, regardless of the wireless switch. It seems that the switch is turned off, regardless if the switch is on or off, even Fn-F5 (Software-Switch for Wireless/Bluetooth) does not help. WORKAROUND: After a suspend and wake, do: sudo rmmod ath9k sudo modprobe ath9k Then wireless is available and connects automatically. Bluetooth is also available. Everything works fine then. But when booting the kernel from power off, the wireless led is on when grub is shown and gets turned off, when the kernel boots and both, Wlan and Bluetooth are disabled. When Wlan is working and I turn off the wireless hardware switch, Wlan and Bluetooth gets disabled as expected, but when I turn it on again, it does not get reactivated and I have to do the workaround again to get it working again. I don't think that it is defective hardware, because: * Before the problem appeared the first time, everything was working fine. * After doing the workaround, everything works fine * The wlan led is on in the grub menu, but it turns off, when the kernel is loaded. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1882 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x4060 irq 22' Mixer name : 'Realtek ALC272' Components : 'HDA:10ec0272,17aa4004,0011' Controls : 14 Simple ctrls : 8 DistroRelease: Ubuntu 10.04 HibernationDevice: RESUME=UUID=a30e85e0-cb12-4510-b5fe-db4fff465466 InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318) MachineType: LENOVO S10-3 Package: linux (not installed) ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic root=UUID=7341b634-5ce1-417c-b3d0-f001464c95f1 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Regression: Yes RelatedPackageVersions: linux-firmware 1.34 Reproducible: Yes Tags: ubuntu-une lucid networking regression-update needs-upstream-testing Uname: Linux 2.6.32-22-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 02/03/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 2ACN21WW dmi.board.name: Mariana3A dmi.board.vendor: Lenovo dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr2ACN21WW:bd02/03/2010:svnLENOVO:pnS10-3:pvrLenovo:rvnLenovo:rnMariana3A:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: S10-3 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO The case label says: Lenovo IdeaPad S10-3 Model name: 0647 Factory ID: CS20 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/577114/+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
[Kernel-packages] [Bug 1313274] [NEW] After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Public bug reported: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Attached nvidia bug report log file. ** Attachment added: "File created by sudo nvidia-bug-report.sh" https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+attachment/4098072/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1307236] Re: NVidia Issues - blurry text after upgrading from 13.10 to 14.04
I have had the issue, but in my case it seemed to be caused by some broken package dependencies. After resolving them and rebooting, the issue was gone. Probably you should have a look at the package dependencies, if you can't fix it with the suggestion above. But in my case the resolution settings are still not like what I want and I cannot change it: Now I have a problem with nvidia-settings, that crashes every time when I try to apply new settings: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1307236 Title: NVidia Issues - blurry text after upgrading from 13.10 to 14.04 Status in “nvidia-settings” package in Ubuntu: Incomplete Bug description: I have a System76 Bonoboo with a GeForce GTX 670MX I upgraded from 13.10 to 14.04 and after the upgrade finished I logged in and the text in the windows would get blurry until I refocused on the window and then get blurry again. I tried various nvidia installs (nvidia-common, nvidia-prime, etc.) and when I would reboot I would get the lightdm screen to authenticate but the dash panel would not appear after logging in. Looking at .xsessions I noticed: init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped My workaround has been: apt-get purge nvidia* and then to run NVIDIA-Linux-x86_64-331.49.run xrandr shows: Screen 0: minimum 8 x 8, current 3280 x 1080, maximum 16384 x 16384 LVDS-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.0*+ 40.0 HDMI-0 connected 1360x768+1920+0 (normal left inverted right x axis y axis) 880mm x 506mm 1360x768 60.0*+ 1920x1080 59.9 60.1 60.0 1440x480 60.1 1280x768 59.9 1280x720 60.0 59.9 1024x768 60.0 800x60060.3 720x48059.9 60.1 640x48059.9 59.9 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) Let me know if any other information would be helpful. I have seen that there are some nvidia related issues that will hopefully be worked out. I just wanted to document my experience in case others have a similar problem. Peace - Anthony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1307236/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Found the following link: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
The above was from the attached nvidia-bug-report.log. dpkg -p nvidia-settings |grep Version Version: 331.20-0ubuntu8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Currently NVIDIA GLX Module 304.117 is installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
The issue is the following: i nvidia-304-updates- NVIDIA legacy binary driver - version 304.117 The legacy driver is version 304. But nvidia-settings has version 331. In the link, tey recommend downgrading nvidia-settings, but I think it would be interesting for me to try to upgrade the driver, because it seems to support Underscan (as Overscan compensation). Probably it could solve the following issues that I have with my television set: Currently I am using a SEG Nevada television set as Monitor, but that one has the issue that it crops the image which is displayed on the screen in 720p mode. This is called Overscan and its purpose was for old (analog) signals to hide the borders that might not look nice, but today in the digital age the feature has become obsolete, because all pixels even at the border are expected to look nice (and when using a computer, they are even required as there are the taskbars, etc.). See also: http://en.wikipedia.org/wiki/Overscan Good televisions make that feature configurable: When disabled, all pixels are displayed and the image is not cropped. Unfortunately I can't find any setting to disable Overscan at the television set, even not in the secret menu. The TV service menu can be accessed by pressing "MENU" and then "9" "3" "0" "1". Menu entries can be selected with the curser keys "UP" and "DOWN" and entered with "RIGHT". There is also an entry EEPROM edit, but I will better leave my hands off until I know what the numbers there stand for. If someone can give me a hint how to disable Overscan, please let me know. With Ubuntu 12.04 I used as workaround the resolution 1024x768 which is not affected by the overscan issue and displays all pixels. Unfortunately the aspect ratio was not correct and pixels were not sqares, so I would prefer to use 1280x768 without Overscan or (if not possible) to compensate Overscan by leaving the hidden (non displayed) border area of the display unused, if possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Trying to upgrade gives some dependency problems:
michael@quad:~/download$ sudo aptitude install nvidia-331
The following NEW packages will be installed:
bbswitch-dkms{a} libcuda1-331{a} nvidia-331{b} nvidia-libopencl1-331{ab}
nvidia-opencl-icd-331{a} nvidia-prime{a}
0 packages upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 36,1 MB of archives. After unpacking 158 MB will be used.
The following packages have unmet dependencies:
ocl-icd-libopencl1 : Conflicts: libopencl1 which is a virtual package.
nvidia-libopencl1-331 : Conflicts: libopencl1 which is a virtual package.
nvidia-304-updates : Conflicts: xorg-driver-binary which is a virtual package.
nvidia-331 : Conflicts: xorg-driver-binary which is a virtual package.
The following actions will resolve these dependencies:
Remove the following packages:
1) nvidia-304-updates
2) nvidia-current-updates
Keep the following packages at their current version:
3) nvidia-libopencl1-331 [Not Installed]
Leave the following dependencies unresolved:
4) nvidia-331 recommends nvidia-libopencl1-331
Accept this solution? [Y/n/q/?]
My question: Is it a good idea to leave that dependency unresolved?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1313274
Title:
After upgrading to 14.04, nvidia-settings crashes with "BadValue" X
Window System error
Status in “nvidia-settings” package in Ubuntu:
New
Bug description:
After upgrading to 14.04 the screen resolution is not as I want and
changing with nvidia-settings is not possible, because the program
crashes when applying new settings.
michael@quad:~$ nvidia-settings
ERROR: Error querying target relations
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 738 error_code 2 request_code 158 minor_code 25)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
michael@quad:~$
The crash occurs when using the "Apply" button.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-settings 331.20-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CurrentDesktop: Unity
Date: Sun Apr 27 09:34:38 2014
InstallationDate: Installed on 2012-05-11 (715 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
(20120423)
SourcePackage: nvidia-settings
UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Unfortunately the nvidia-331 does not work with the graphics card: 01:00.0 VGA compatible controller: NVIDIA Corporation G72 [GeForce 7300 GS] (rev a1) And the nouveau driver which is open source can only display 640x480 on the television set. So It seems that I have to stay with the nvidia driver. My problem is now: * The 1280 x 720 does not display without Overscan. I can't see the task bar. :-( * If I change to 1024 x 768 in System Settings, the computer will send 1024 x 768 @ 75 Hz while the television set only supports 60 Hz, leading to a distorted picture. Changing to 60 Hz with nvidia-settings is not possible, because the program crashes when I press "Apply". :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Found a link that might be helpful: http://analogbit.com/fix_nvidia_edid You can use nvidia-settings to get your EDID info. Run nvidia-settings, click on DFP-0, then click "Acquire EDID..." Store the file to television-edid.bin Install the package edid-decode and do edid-decode television-edid.bin This gives the following output: ... First detailed timing is preferred timing Established timings supported: 720x400@70Hz 640x480@60Hz 640x480@67Hz 640x480@72Hz 640x480@75Hz 800x600@56Hz 800x600@60Hz 800x600@72Hz 800x600@75Hz 832x624@75Hz 1024x768@60Hz 1024x768@70Hz 1024x768@75Hz Standard timings supported: Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm 1280 1720 1760 1980 hborder 0 720 725 730 750 vborder 0 +hsync +vsync Monitor ranges: 56-76HZ vertical, 31-61kHz horizontal, max dotclock 80MHz ... Thus the television says it can do 1024x768@75Hz, and it is not NVIDIAS fault that it gets such a signal that it cannot display well when switching to 1024x768. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Trying to set the display size manually was not successful: michael@quad:~$ xrandr Screen 0: minimum 8 x 8, current 1280 x 720, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-I-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected primary 1280x720+0+0 (normal left inverted right x axis y axis) 708mm x 398mm 1280x720 50.0*+ 1024x768 75.0 70.1 60.0 800x60075.0 72.2 60.3 56.2 640x48075.0 72.8 59.9 michael@quad:~$ xrandr -s 1024x768 -r 60.0 Rate 60.0 Hz not available for this size Strange: 60.0 Hz is listed for 1024x768, but cannot be selected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 1313274] Re: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error
Does anybody have another idea for a workaround? Otherwise the bug should get higher priority to get fixed quickly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1313274 Title: After upgrading to 14.04, nvidia-settings crashes with "BadValue" X Window System error Status in “nvidia-settings” package in Ubuntu: New Bug description: After upgrading to 14.04 the screen resolution is not as I want and changing with nvidia-settings is not possible, because the program crashes when applying new settings. michael@quad:~$ nvidia-settings ERROR: Error querying target relations The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 738 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) michael@quad:~$ The crash occurs when using the "Apply" button. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sun Apr 27 09:34:38 2014 InstallationDate: Installed on 2012-05-11 (715 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1313274/+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
[Kernel-packages] [Bug 495930] Re: 0a12:0001 Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10
Also affects: Ubuntu precise (12.04.4 LTS) ** Tags added: precise -- 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/495930 Title: 0a12:0001 Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10 Status in “linux” package in Ubuntu: Expired Bug description: Binary package hint: bluez ---Ubuntu 9.10--- Description: Ubuntu 9.10 Release: 9.10 :~$ uname -r 2.6.31-16-generic Packages: bluez 4.57-0ubuntu1 bluetooth 4.57-0ubuntu1 USB Devices: :~$ lsusb Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 03f0:1712 Hewlett-Packard Printing Support Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 045e:0038 Microsoft Corp. SideWinder Precision 2 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 006: ID 0a5c:3500 Broadcom Corp. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub :~$ sudo hciconfig -a hci0: Type: USB BD Address: 00:1B:10:00:06:75 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING RX bytes:646 acl:0 sco:0 events:16 errors:0 TX bytes:67 acl:0 sco:0 commands:17 errors:0 Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Can't read local name on hci0: Connection timed out (110) :~$ sudo hcitool inq [sudo] password for tank: Inquiring ... Inquiry failed.: Connection timed out Log Files I got: Messages: Dec 12 21:56:15 kernel: [ 683.120066] usb 3-1: new full speed USB device using uhci_hcd and address 6 Dec 12 21:56:15 kernel: [ 683.280252] usb 3-1: configuration #1 chosen from 1 choice Dec 12 21:56:15 kernel: [ 683.283122] hub 3-1:1.0: USB hub found Dec 12 21:56:15 kernel: [ 683.295061] hub 3-1:1.0: 3 ports detected Dec 12 21:56:16 kernel: [ 683.602220] usb 3-1.1: new full speed USB device using uhci_hcd and address 7 Dec 12 21:56:16 kernel: [ 683.776189] usb 3-1.1: configuration #1 chosen from 1 choice Dec 12 21:56:16 kernel: [ 683.867946] usb 3-1.2: new full speed USB device using uhci_hcd and address 8 Dec 12 21:56:21 kernel: [ 689.073997] usb 3-1.2: new full speed USB device using uhci_hcd and address 9 Dec 12 21:56:21 kernel: [ 689.196165] usb 3-1.2: configuration #1 chosen from 1 choice Dec 12 21:56:21 kernel: [ 689.209110] input: HID 0a5c:3502 as /devices/pci:00/:00:04.3/usb3/3-1/3-1.2/3-1.2:1.0/input/input8 Dec 12 21:56:21 kernel: [ 689.209345] generic-usb 0003:0A5C:3502.0004: input,hidraw1: USB HID v1.11 Keyboard [HID 0a5c:3502] on usb-:00:04.3-1.2/input0 Dec 12 21:56:21 kernel: [ 689.282004] usb 3-1.3: new full speed USB device using uhci_hcd and address 10 Dec 12 21:56:22 kernel: [ 689.434147] usb 3-1.3: configuration #1 chosen from 1 choice Dec 12 21:56:22 kernel: [ 689.457110] input: HID 0a5c:3503 as /devices/pci:00/:00:04.3/usb3/3-1/3-1.3/3-1.3:1.0/input/input9 Dec 12 21:56:22 kernel: [ 689.457364] generic-usb 0003:0A5C:3503.0005: input,hidraw2: USB HID v1.11 Mouse [HID 0a5c:3503] on usb-:00:04.3-1.3/input0 kern.log: Dec 12 21:59:16 kernel: [ 864.083825] hci_cmd_task: hci0 command tx timeout Dec 12 22:01:10 kernel: [ 978.278941] hci_cmd_task: hci0 command tx timeout daemon.log: Dec 12 21:56:16 bluetoothd[4125]: Bluetooth daemon 4.57 Dec 12 21:56:16 bluetoothd[4127]: Starting SDP server Dec 12 21:56:16 bluetoothd[4127]: Can't load plugin /usr/lib/bluetooth/plugins/netlink.so: /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug Dec 12 21:56:16 NetworkManager:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan0, iface: pan0) Dec 12 21:56:16 NetworkManager:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found. Dec 12 21:56:16 NetworkManager: device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring... Dec 12 21:56:16 bluetoothd[4127]: bridge pan0 created Dec 12 21:56:16 bluetoothd[4127]: HCI dev 0 registered Dec 12 21:56:16 bluetoothd[4127]: HCI dev 0 up Dec 12 21:56:16 bluetoothd[4127]: Starting security manager 0 Dec 12 21:56:16 bluetoothd[4127]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Dec 12 21:56:16 bluetoothd[4127]: Adapter /org/bluez/4125/hci0 has been enabled Dec 12 21:59:16 bluetoothd[4127]: Discovery session 0x190e9e0 with :1.67 activated Dec 12 22:01:10 bluetoothd[4127]: Stopping discovery syslog: Dec 12 21:56:15 kernel: [ 683.120066] usb 3-1
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
With OTA 7 it could not connect to my TomTom VIA 135. With an android device it was no problem to pair it and use it as hands free, so I would expect it to work with Ubuntu, too. I will retest this with OTA 8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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
[Kernel-packages] [Bug 1310402] Re: Userland depends on ionice idle but default scheduler is "deadline".
I have experienced this also on Ubuntu 16.04.7 LTS when I wanted to move 1,5 TB data to an external USB3 disk. When I started the mv command it performed well until I have noticed that BackupPC and updatedb.mlocate woke up to do plenty of disk activity, slowing down the source disk of the mv command. Then I used ionice to set the priority of those processes to "idle" and the mv to "rt/4" priority in the hope that the mv will be able to read at maximum speed while the idle processes will have to wait most of the time until the mv process has finished. But the performance of the mv process didn't increase as expected. Both, source and target disks are spinning disks, not SSDs. I would expect that it should be possible to force the linux kernel to process the mv command to be done in maximum speed while other processes should not be able to steal I/O throughput until the mv is done. I could have killed the other processes, but this is not what I wanted to do for that. -- 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/1310402 Title: Userland depends on ionice idle but default scheduler is "deadline". Status in linux package in Ubuntu: Triaged Bug description: Userland depends upon the idle feature of the CFQ scheduler, this can lead to extreme desktop sluggishness with the default deadline scheduler due to IO blocking. In my case, the KDE baloo indexer was indexing all of my files, and making other desktop processes block. The baloo processes are set to idle IO priority to avoid this problem but this was not being honored. From the information I have found online and in the ionice man page, the idle priority only is useful with the CFQ scheduler. KDE Baloo indexer sets it's processes to use "idle" priority the man-db cronjobs also use idle priority root@sirius:/etc# grep idle cron.daily/man-db iosched_idle= iosched_idle='--iosched idle' --oknodo --chuid man $iosched_idle -- -c \ $iosched_idle \ The compiled in default scheduler is "deadline" root@sirius:/boot# grep DEFAULT_IOSCHED config-3.13.0-24-generic CONFIG_DEFAULT_IOSCHED="deadline" from the ionice man page: Linux supports I/O scheduling priorities and classes since 2.6.13 with the CFQ I/O scheduler. root@sirius:/boot# uname -a Linux sirius 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.24.28 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zmc2658 F pulseaudio zmc3010 F pulseaudio /dev/snd/controlC0: zmc2658 F pulseaudio zmc3010 F pulseaudio CurrentDesktop: KDE Date: Sun Apr 20 17:23:28 2014 HibernationDevice: RESUME=UUID=dea47071-fda3-4725-a9c5-1f4fc531e6ef InstallationDate: Installed on 2014-04-18 (2 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: Acer Aspire 7551 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 7551 dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd10/26/2010:svnAcer:pnAspire7551:pvrV1.15:rvnAcer:rnAspire7551:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 7551 dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310402/+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
[Kernel-packages] [Bug 1310402] Re: Userland depends on ionice idle but default scheduler is "deadline".
Finally I have sent the processes stealing I/O throughput a STOP signal (kill -19), and voila: The I/O througput of the mv command increased from ~2 Mb/s to ~75 Mb/s. -- 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/1310402 Title: Userland depends on ionice idle but default scheduler is "deadline". Status in linux package in Ubuntu: Triaged Bug description: Userland depends upon the idle feature of the CFQ scheduler, this can lead to extreme desktop sluggishness with the default deadline scheduler due to IO blocking. In my case, the KDE baloo indexer was indexing all of my files, and making other desktop processes block. The baloo processes are set to idle IO priority to avoid this problem but this was not being honored. From the information I have found online and in the ionice man page, the idle priority only is useful with the CFQ scheduler. KDE Baloo indexer sets it's processes to use "idle" priority the man-db cronjobs also use idle priority root@sirius:/etc# grep idle cron.daily/man-db iosched_idle= iosched_idle='--iosched idle' --oknodo --chuid man $iosched_idle -- -c \ $iosched_idle \ The compiled in default scheduler is "deadline" root@sirius:/boot# grep DEFAULT_IOSCHED config-3.13.0-24-generic CONFIG_DEFAULT_IOSCHED="deadline" from the ionice man page: Linux supports I/O scheduling priorities and classes since 2.6.13 with the CFQ I/O scheduler. root@sirius:/boot# uname -a Linux sirius 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.24.28 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zmc2658 F pulseaudio zmc3010 F pulseaudio /dev/snd/controlC0: zmc2658 F pulseaudio zmc3010 F pulseaudio CurrentDesktop: KDE Date: Sun Apr 20 17:23:28 2014 HibernationDevice: RESUME=UUID=dea47071-fda3-4725-a9c5-1f4fc531e6ef InstallationDate: Installed on 2014-04-18 (2 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: Acer Aspire 7551 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 7551 dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd10/26/2010:svnAcer:pnAspire7551:pvrV1.15:rvnAcer:rnAspire7551:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 7551 dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310402/+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
