You can now avoid touching gnome-settings-daemon at all. I've added the module parameter "type" to 'nvidiabl' to enable users to change the backlight type from the default "raw".
...
Type: Posts; User: IntuitiveNipple; Keyword(s):
You can now avoid touching gnome-settings-daemon at all. I've added the module parameter "type" to 'nvidiabl' to enable users to change the backlight type from the default "raw".
...
See bug #1039916 Nvidia driver causing SIGSEGV in nvclock and smartdimmer
I've opened a bug report to deal with this issue:
Bug #555500 Buggy BIOS hard disk workaround missing; causes: "Geom Error"
I'd be grateful if those of you affected could add your comments to...
There are two problems here:
Displays that don't provide Extended Display Identification Data (EDID) (bug #194760) - usually because they are older models.
Xorg server using the RandR...
For Karmic and after (and possibly Jaunty) it would be better to use the kernel's uvcvideo module (instead of the now deprecated r5u870 module) together with Alex Hixon's userspace firmware loader...
This affects all qt4 applications - Skype, qtconfig-qt4, etc.. The reason is that qt4 is not handling sub-pixel font rendering correctly. Changing to another font rendering method is a temporary...
I've just seen your comment to bug #119233. I suspect it is related to slight differences between the installer and installed kernel. The order of device detection can be different in some...
It looks as if kernel updates have made that module match the one created by the DKMS package and DKMS tries to be helpful by not replacing the kernel's version. It then quits which causes the...
I suspect if you're having problems you'll need to build/install the accompanying kernel modules against the running kernel. Things have moved on substantially since the Hardy kernel module was...
alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*
The package in my PPA is only for Hardy (kernel 2.6.24):
Show details ch341-dkms - 1.1-0ubuntu1~ppa2h (changesfile) 2008-09-19 Published Hardy Misc All builds were built...
I've produced backports of the kvm-83 package for Intrepid, Hardy and Gutsy. I've tested Intrepid and Hardy but not had chance to test Gutsy so far.
They are available from my PPA.
kvm...
Since you've altered UID and GID the user home directory should have all its files updated too.
First, check for any files *not* having the expected settings:
whoami
cd ~
find . ! -user...
I've added a tutorial to my Wiki, where it is easier to maintain and update.
The reason for wine ./configure reporting
configure: error: FreeType 32-bit development files not found. Fonts will not be built.
on a 64-bit host/build system is that the 32-bit...
Debian/Ubuntu already includes an Xorg input driver for many ELO touch-screens. I've created an Ubuntu Wiki article on how to install and configure it.
See my comments in comment #10
The trick is to reduce the scope of the problem using the log files and so forth.
That kern.log is helpful but could you do another one. Follow the same procedure (delete the existing kern.log...
The explanation is right there in the log-file. Look at the time-stamp of the messages. There is a big difference between:
[ 0.000000] Detected 1992.958 MHz processor.
[ 1051.189836]...
I noticed this:
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
Check the system BIOS for any option to enable Advanced Programmable Interrupt Controller or add...
I suspect you need to force the clocksource on the kernel's command-line (set in the GRUB menu or via the file /boot/grub/menu.lst):
clocksource= [GENERIC_TIME] Override the default clocksource...
It all starts when the kernel is configured, before it is built.
The Ubuntu git kernel repository contains the Debian package build scripts and other resources in ./debian/, such as the kernel...
The same situation I explained in comment #6 applies to 045E:00F4 as well.
As I said, I have no idea why the driver declares support for device IDs and then doesn't have the internal structures in...
The best way might be to write a udev rule keyed to the internal IEEE-1394 device that prevents it being configured as a device.
Please report the entries from /var/log/kern.log when inserting the camera so we know what the system found and did.