[Bug 177713] Re: CFS in 2.6.24 kernel needs cpu_share adjustment for niced processes
Aah, okay. Perhaps this bug just needs to be renamed back to being specific to 'boinc' again, and not marked fixed yet since it's not yet a 'proper' fix. I can confirm, by installing the old .22 kernel, that the audio dropouts only happen with the new .24 kernel. It's especially noticeable with timidity (not as daemon) -- when PulseAudio drops out, the application itself stalls. In addition, with the old kernel, my folding tasks no longer slow down my compiz-fusion desktop. Should I add comments to the linked bug 188226 ? -- CFS in 2.6.24 kernel needs cpu_share adjustment for niced processes https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188226] Re: Kernel should use CONFIG_FAIR_CGROUP_SCHED
Although this mailing list applies to PowerPC specifically, the comments are relevant to the behavior seen with my [EMAIL PROTECTED] process, as commented in bug 177713 and bug 178807 : http://patchwork.ozlabs.org/linuxppc/patch?q=schedulingid=16345 http://patchwork.ozlabs.org/linuxppc/patch?q=schedulingid=16447 http://patchwork.ozlabs.org/linuxppc/patch?q=schedulingid=16492 http://patchwork.ozlabs.org/linuxppc/patch?q=schedulingid=16506 (Due to the organization of that site, I can't find a way to navigate the whole thread from one place.) -- Kernel should use CONFIG_FAIR_CGROUP_SCHED https://bugs.launchpad.net/bugs/188226 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: CFS in 2.6.24 kernel needs cpu_share adjustment for niced processes
I'm adding an assignment to linux-source-2.6.24, because working around the bug in boinc does not fix the underlying cause. In addition to the [EMAIL PROTECTED] issues, I've also noticed dropouts / skipping in PulseAudio upon doing things such as closing my laptop lid; under the 2.6.22 kernel, I never (or at least rarely) had such issues. I am in the pulse-rt group, so it should be running with realtime priority. -- CFS in 2.6.24 kernel needs cpu_share adjustment for niced processes https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: 2.6.24-2: Regression with idle cpu cycle handling
Oh wait, I just misinterpreted my own comment. What I mean is that issues with 'nice' handling (namely, 'nice' loads not showing up as 'nice') seem to be more complicated than just that user factor. -- 2.6.24-2: Regression with idle cpu cycle handling https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: 2.6.24-2: Regression with idle cpu cycle handling
Well, I don't run my [EMAIL PROTECTED] as a different user (actually, I ran it as root, though I suppose I should change that now), and I have noticed the issue still applies even to other non distributed-computing cpu loads: I tried to reproduce this using a simple busy loop in bash, and with 'yes', and by using cat /dev/zero or cat /dev/urandom /dev/null, each niced to +19 and SCHED_IDLEPRIO, but for some reason, these did not create the same sluggishness that [EMAIL PROTECTED] creates. In addition, these loads did not show up as 'nice' in my Gnome system monitor panel applet; Instead, these processes showed up as 'system' load, and they also sped up my CPU despite cpufreq being set to ignore 'nice' loads. Therefore, this is not just a boinc issue. -- 2.6.24-2: Regression with idle cpu cycle handling https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: 2.6.24-2: Regression with idle cpu cycle handling
Hmm, it seems like the only thing being marked as 'invalid' is the 'boinc' assignment; the 'linux' assignment seems to have mysteriously been replaced by the confusing statement: This bug is not recorded as needing to be fixed in linux (Ubuntu). Also Needs Fixing Here I sure hope it is being left as valid for 'linux'; the behavior feels like a regression subjectively, even if there is a good reason behind it. -- 2.6.24-2: Regression with idle cpu cycle handling https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: 2.6.24-2: Regression with idle cpu cycle handling
Well, if this is by design, then I guess I need a new method of running [EMAIL PROTECTED] -- whether I run it as root or as a new user, even at IDLEPRIO and +19, the [EMAIL PROTECTED] process still slows down other things on the system. The input lag is no longer present, and the process does show up as 'nice', but Compiz drops to half its framerate. It seems odd to me that a process cannot simply yield its CPU cycles to other processes regardless of user. Will I now have to arbitrarily assign a CPU time percentage to the user? I also figured out the is not in Linux issue: my marked-as-duplicate bug had been attached to linux, I made a 'freudian slip' and reached this bug by the /+source/linux/ path, which is not attached to this 'boinc' bug at all. -- 2.6.24-2: Regression with idle cpu cycle handling https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177570] Re: [hardy] two batteries display when left clicking on g-p-m
Comments copied (and fixed) from my bug report LP: 181101: The old interface is through the ACPI 'battery' module, and shows up as product Battery Bay. The new interface is through the 'power_supply' module, and shows up as product 'Li-ion'. The old battery interface disappears upon removal; the new interface indicates 0% and 'missing' instead. The new interface seems not to emit 'change' events to HAL (as seen in lshal --monitor), so the value is not updated except on state changes. In addition, this duplication of battery seems to halve gnome-power- manager's indicated wattage, but the ACPI power usage value given by powertop seems unaffected. Thankfully, this didn't see, to affect gnome-power-manager's battery-life estimates, but I would imagine having these duplicate batteries, one of which never changes, can screw up any existing battery profiles. Ideally, once the lack of events is fixed there should be a way to detect duplicates, perhaps by having the power_supply sysfs class keep a link to the /proc battery object. -- [hardy] two batteries display when left clicking on g-p-m https://bugs.launchpad.net/bugs/177570 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181101] Re: Hardy: new 2.6.24 'power_supply' interface confuses HAL (sees duplicate batteries)
Correction: the NEW interface is the one that's not emitting 'change' events. If I make an fdi file to ignore the power_supply object with name Li-ion, I'm left with just the working battery. However, this is not a solution -- it's just a workaround. Ideally, once the lack of events is fixed there should be a way to detect duplicates, perhaps by having the power_supply sysfs class keep a link to the battery object under /proc. -- Hardy: new 2.6.24 'power_supply' interface confuses HAL (sees duplicate batteries) https://bugs.launchpad.net/bugs/181101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179444] Re: gnome-settings-daemon crashed with signal 5
I don't have a secondary display to attach, but I still do get the same crash upon hitting my 'hotkey display switch' hotkey. Last line of gnome-settings-daemon console output is this: ** ERROR **: file gnome-settings-multimedia-keys.c: line 749 (do_action): should not be reached aborting... -- gnome-settings-daemon crashed with signal 5 https://bugs.launchpad.net/bugs/179444 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179444] Re: gnome-settings-daemon crashed with signal 5
Oh, and another note (curse the lack of edit function...): when I repeatedly kill gnome-settings-daemon so it stops respawning, then I can run 'xev' and hit the hotkey, and it tells me the key is 'xf86display'. Apport didn't automatically post the stack trace to this existing bug, so I've just posted the apport file from /var/crash ** Attachment added: _usr_lib_gnome-control-center_gnome-settings-daemon.1000.crash http://launchpadlibrarian.net/11183887/_usr_lib_gnome-control-center_gnome-settings-daemon.1000.crash -- gnome-settings-daemon crashed with signal 5 https://bugs.launchpad.net/bugs/179444 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181101] Hardy: new 2.6.24 'power_supply' interface confuses HAL (sees duplicate batteries)
Public bug reported: When I boot the 2.6.24 kernel, gnome-power-manager shows two battery devices, one of which changes indicated value only upon switching from battery to AC (and not vice versa). The old interface is through the ACPI 'battery' module, and shows up as product Li-Ion. This battery . The new interface is through the 'power_supply' module, and shows up as product 'Battery Bay'. The old battery interface disappears upon removal; the new interface indicates 0% and 'missing' instead, which is more proper behavior. The old interface seems to no longer emit 'change' events to HAL, so the value is not updated. In addition, this duplication of battery seems to halve gnome-power- manager's indicated wattage, but the ACPI power usage value given by powertop seems unaffected. Thankfully, none of this affects gnome-power-manager's battery-life estimates, but I would imagine having these duplicate batteries, one of which never changes, can screw up any existing battery profiles. ** Affects: ubuntu Importance: Undecided Status: New -- Hardy: new 2.6.24 'power_supply' interface confuses HAL (sees duplicate batteries) https://bugs.launchpad.net/bugs/181101 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178807] Severe sluggishness under 'nice' load in 2.6.24 kernels
Public bug reported: I usually run two instances of [EMAIL PROTECTED], using schedtool to assign each to a different CPU core, and both to nice +19 and SCHED_IDLEPRIO. Since booting the 2.6.24 -generic kernels, my system has become severely sluggish -- it will take somewhere between 1/4 and 1/2 second (subjectively) for a character to appear on-screen after hitting the key. This happens with both Metacity and Compiz-Fusion (using git version). Switching to the NV driver reduces this sluggishness slightly, but it's still subjectively worse than the 2.6.22 kernel ever was at its worst. Stopping my 'niced' [EMAIL PROTECTED] processes immediately alleviates this severe sluggishness, so it seems that somehow these 'nice' tasks are being given a too high priority. I believe this most likely has something to do with the new CFS scheduler in the 2.6.24 kernel. I tried to reproduce this using a simple busy loop in bash, and with 'yes', and by using cat /dev/zero or cat /dev/urandom /dev/null, each niced to +19 and SCHED_IDLEPRIO, but for some reason, these did not create the same sluggishness that [EMAIL PROTECTED] creates. In addition, these loads did not show up as 'nice' in my Gnome system monitor panel applet, and they also sped up my CPU despite cpufreq being set to ignore 'nice' loads. Instead, these processes showed up as 'system' load. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Severe sluggishness under 'nice' load in 2.6.24 kernels https://bugs.launchpad.net/bugs/178807 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177713] Re: 2.6.24-2: Regression with idle cpu cycle handling
[Comments copied from other bug report:] I usually run two instances of [EMAIL PROTECTED], using schedtool to assign each to a different CPU core, and both to nice +19 and SCHED_IDLEPRIO. Since booting the 2.6.24 -generic kernels, my system has become severely sluggish -- it will take somewhere between 1/4 and 1/2 second (subjectively) for a character to appear on-screen after hitting the key. This happens with both Metacity and Compiz-Fusion (using git version). Switching to the NV driver reduces this sluggishness slightly, but it's still subjectively worse than the 2.6.22 kernel ever was at its worst. Stopping my 'niced' [EMAIL PROTECTED] processes immediately alleviates this severe sluggishness, so it seems that somehow these 'nice' tasks are being given a too high priority. I believe this most likely has something to do with the new CFS scheduler in the 2.6.24 kernel. I tried to reproduce this using a simple busy loop in bash, and with 'yes', and by using cat /dev/zero or cat /dev/urandom /dev/null, each niced to +19 and SCHED_IDLEPRIO, but for some reason, these did not create the same sluggishness that [EMAIL PROTECTED] creates. In addition, these loads did not show up as 'nice' in my Gnome system monitor panel applet; Instead, these processes showed up as 'system' load, and they also sped up my CPU despite cpufreq being set to ignore 'nice' loads. -- 2.6.24-2: Regression with idle cpu cycle handling https://bugs.launchpad.net/bugs/177713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111145] Re: sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture
This issue is still present in Gutsy, and even into Hardy at this point (kernel 2.6.24-1-generic). One note: I have noticed this error in dmesg, though I'm not sure exactly when it occurs. I assume it's when I try capturing (which turns out to be when PulseAudio starts). [ 3378.669683] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x011f1c00 With this post, I shall attach the output of the now-back-online alsa- info.sh I shall attach the INI files for the configs for XP and Vista, in case they help: I'm not sure if it helps, but IDT has released specs sheets at http://www.idt.com/?genID=STAC9250 ** Attachment added: alsa-info.txt http://launchpadlibrarian.net/10898630/alsa-info.txt -- sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture https://bugs.launchpad.net/bugs/45 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111145] Re: sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture
** Attachment added: Driver INI for XP http://launchpadlibrarian.net/10898632/stac9250_xp.ini -- sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture https://bugs.launchpad.net/bugs/45 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111145] Re: sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture
Another note: Since apparently each port can be either input or output, would it be possible to allow the mic as output or line-in as output options for this audio chip? In addition, I noticed that ALSA reports some IEC958-related pins, even though my notebook lacks a physical output. However, there are no mixer controls for this nonexistant output. Another note: once the audio driver loads, PC speaker entirely breaks. I suppose that may be considered a good thing, though. cat /dev/dsp (hangs for a while, and then:)cat: /dev/dsp: Input/output error Another feature that's deliberately hidden in the XP drivers, and entirely removed in the Vista drivers, is Stereo Mix recording. Is there any chance of enabling this in the ALSA drivers? I'd imagine the function may be entirely software, though. ** Attachment added: Driver INI for Vista http://launchpadlibrarian.net/10898639/stac9250_vista.ini -- sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture https://bugs.launchpad.net/bugs/45 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
I managed to fix my LCD-turns-off issue by editing my DSDT; it turns out that whoever coded it foolishly used if LEqual instead of if LLessEqual, which meant that any time an invalid brightness value was passed in, the LCD would turn off. I changed the conditions to make more sense, and now I no longer get the horrid blinking. However, it would be nice if HAL and the kernel would pass correct (as in, not unlisted) brightness values to the ACPI controller. I still don't get why the values of 12, 37, 62, and 87 didn't work, though. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
Oh, and now I still get the LCD turning off when idle, and what's worse is that now if I don't do my no_automatic_changes=0 workaround, my brightness keys don't work at all! What gives? Also, I'm still curious why the multiples of 13 don't work through /sys/, but do work through /proc. ** Summary changed: - LCD backlight turns off between brightness levels during fades, and when on battery or at idle + Brightness keys don't work, and LCD backlight blinks off during fades, and turns off when dimming on battery or at idle. ** Description changed: Binary package hint: gnome-power-manager When gnome-power-manager dims the screen when on battery or when idle, the backlight turns entirely off. In addition, during the fade the screen blinks: 100%, OFF, 75%, OFF, 50%, OFF. cat /proc/acpi/video/VGA/LCD/brightness: levels: 100 37 12 25 37 50 62 75 87 100 current: 100 The screen is turning off whenever something requests a brightness level between the available discrete levels; thus the default dim-when- inactive brightness of 30 turns the backlight off. For a while, I thought my system was freezing at a black screen at login (battery) or idle (AC), until I remembered the brightness controls. One factor in this is the new /sys/class/backlight/ interface for brightness control, common to all ACPI drivers: This structure does not seem to provide the same, necessary information, such as available discrete brightness levels. /sys/class/backlight/acpi_video0/max_brightness: 100 /sys/class/backlight/acpi_video0/actual_brightness:62 == changes even when keyboard hotkeys are used; g-p-m does not notice this. /sys/class/backlight/acpi_video0/brightness: 62 == changes only when software requests a change. HAL lists num_levels=101, while ideally it should be 8 or 9. Better yet, the kernel itself should provide the discrete levels, or rounding issues may appear. Oddly. the brightness levels 12, 37, 62, and 75 work through echoing into 'brightness', but turn the backlight off if used in g-p-m. Echoing invalid values there turns the backlight off, but echoing into the /proc structure returns 'invalid argument'. Note: the data under /sys/class/backlight is not synchronized with /proc/acpi/video; for consistency, it should be. + EDIT: As of the beginning of October, 2007, my brightness keys don't + work at all! + (My DSDT also provides sys/class/backlight/acpi_video1/ and /proc/acpi/video/GFX0/DD0n/ for n from 1 to 5; LCD is 4. However, I would not expect the values there to be synchronized with acpi_video0 and VGA/LCD.) ** Summary changed: - Brightness keys don't work, and LCD backlight blinks off during fades, and turns off when dimming on battery or at idle. + LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. ** Description changed: Binary package hint: gnome-power-manager When gnome-power-manager dims the screen when on battery or when idle, the backlight turns entirely off. In addition, during the fade the screen blinks: 100%, OFF, 75%, OFF, 50%, OFF. cat /proc/acpi/video/VGA/LCD/brightness: levels: 100 37 12 25 37 50 62 75 87 100 current: 100 The screen is turning off whenever something requests a brightness level between the available discrete levels; thus the default dim-when- inactive brightness of 30 turns the backlight off. For a while, I thought my system was freezing at a black screen at login (battery) or idle (AC), until I remembered the brightness controls. One factor in this is the new /sys/class/backlight/ interface for brightness control, common to all ACPI drivers: This structure does not seem to provide the same, necessary information, such as available discrete brightness levels. /sys/class/backlight/acpi_video0/max_brightness: 100 - /sys/class/backlight/acpi_video0/actual_brightness:62 == changes even when keyboard hotkeys are used; g-p-m does not notice this. + /sys/class/backlight/acpi_video0/actual_brightness:62 == changes when software or hotkeys are used. /sys/class/backlight/acpi_video0/brightness: 62 == changes only when software requests a change. HAL lists num_levels=101, while ideally it should be 8 or 9. Better yet, the kernel itself should provide the discrete levels, or rounding issues may appear. - Oddly. the brightness levels 12, 37, 62, and 75 work through echoing into 'brightness', but turn the backlight off if used in g-p-m. - Echoing invalid values there turns the backlight off, but echoing into the /proc structure returns 'invalid argument'. + Oddly. the brightness levels 12, 37, 62, and 75 work through echoing into /proc, but turn the backlight off if used in /sys, and thus HAL or g-p-m. + Echoing invalid values into /sys turns the backlight
[Bug 121833] Re: LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle.
Okay, it turns out that the total-breakage was merely HAL breaking on upgrade; this was fixed by rebooting. -- LCD backlight turns off when between discrete levels, both from hotkeys and from dim-on-idle. https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
Oh great, now my workaround has been broken, too! Now I have to press the brightness keys FIVE times to go between adjacent brightness levels -- and some levels are still missing! I can't, for example, use the levels 12, 37, 62, or 87, despite those levels working when I directly manipulate the backlight sysfs entries. This is the change that re-broke hal (0.5.9.1-1ubuntu9) gutsy; urgency=low * debian/patches/64_read_brightness_not_actual_brightness.patch: Read the brightness from /sys/class/backlight/foo/brightness, not actual_brightness. It makes more sense to change based on the brightness that we wanted to set, not the brightness that we actually set. Where's the logic in that? You should show the actual brightness, not what you asked for! Try applying the act based on what we asked for, not what we got logic to everyday situations, and see how well it works... Having no_automatic_changes=0 now results in my screen BLINKING every time I press a brightness key, as the DSDT changes brightness to the right level, and then gnome-power-manager stupidly changes it back to an invalid value. Starting from 100%, it's like this: 100%, BLINK, BLINK, BLINK, BLINK, 75%, BLINK, BLINK, BLINK, BLINK, 50%, BLINK, BLINK, BLINK, BLINK, 25%, BLINK, BLINK, BLINK, BLINK, 0%. -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
Hmm, good point there. However, it still frustrates me that something was broken, and then I found a workaround, and then that workaround was broken without fixing the original issue, which is the lcd backlight turning off. In addition, when gnome-power-manager isn't running, then only the automatic-changes plus actual-brightness method seems to allow brightness changing. Are there any plans for a console brightness control? -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140485] Re: gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3
I've always used gsynaptics, anyway the new panel is nearly useless, because it is too basic -- it doesn't even have sensitivity adjustments, for example. I think SHMConfig should be enabled by default, and gsynaptics installed with it. At least that works with touchpad as CorePointer. I had to build my own package with the two relevant patches removed, also, to get my g-s-d back. -- gnome-settings-daemon not starting with 1:2.19.92-0ubuntu3 https://bugs.launchpad.net/bugs/140485 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
** Attachment added: uname-a.log http://launchpadlibrarian.net/9390542/uname-a.log -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
** Attachment added: version.log http://launchpadlibrarian.net/9390563/version.log -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
** Attachment added: dmesg.log http://launchpadlibrarian.net/9390564/dmesg.log -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/9390565/lspci-vvnn.log -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
Also, a note: With the recent updates to the kernel 'video' module, gnome-power-manager, and the acpi-support scripts, my brightness keys no longer work at the kernel level. Instead, it is left up to the userspace, which renders the system unable to change brightness when in console-only mode. This also means that I have to hit the brightness keys 5 times to go between valid brightness levels; everything in the middle is entirely off. I found a workaround for the new behavior: add 'options video no_automatic_changes=0' to some /etc/modprobe.d/ file -- this gives me the best of both worlds: I get the kernel-level brightness changing with the additional gnome OSD. * However, either way the brightness applet isn't synced with the hotkey-changed brightness. I also have the strange behavior when hitting 'down' while at the lowest brightness level: the LCD will alternate between low and off, with the OSD matching. * That OSD is partly redundant on my system where I have a small, blue, BIOS-level OSD in the upper-left corner of the screen; the gnome brightness OSD is also rather ugly compared to the volume OSD. -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
Another note on my system: while my hotkeys still change brightness properly, Gnome somehow does not notice the change (reflected in the sysfs actual_brightness file), so the slider does not move. and I don't get any OSD. I do, however, get OSD on the (blinking) fades. -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41427] Re: slow keys can turn on surreptitiously cause confusion.
This also still happens in Gutsy. I'd call this a MAJOR bug. At the very least, PLEASE don't make the dialog turn the feature on unless you press YES! What's worse is that even pressing escape does NOT disable the feature. I've finally had to set the slowkeys time to 1 millisecond, in order to essentially disable it. ootthrrrwwwiie, I end up typing like that, because I have to hold the key, and then react in time to let go before it repeats. Also notice that slowkeys breaks function keys. Try hitting alt-tab with it enabled, and notice that the 'alt' is entirely missing, unless you continue holding 'tab' while releasing and re-pressing 'alt'. Because the slowkeys confirmation box does not appear in the taskbar, it becomes ridiculously hard to find the window to tell it NO!. -- slow keys can turn on surreptitiously cause confusion. https://bugs.launchpad.net/bugs/41427 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41427] Re: slow keys can turn on surreptitiously cause confusion.
Actually, it looks like setting the time to be zero actually disables the prompt. The shortcut still causes a beep, but the dialog no longer comes up, and the feature is effectively disabled even if it does actually turn on. (dang, I wish we could edit posts, even if limited to, say, 5 minutes or until first response.) -- slow keys can turn on surreptitiously cause confusion. https://bugs.launchpad.net/bugs/41427 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41427] Re: slow keys can turn on surreptitiously cause confusion.
Hmm, it seems the time can only be set to zero when the feature is enabled, and as soon as it is disabled in any way, it sets itself to 1 and the dialog is re-enabled. -- slow keys can turn on surreptitiously cause confusion. https://bugs.launchpad.net/bugs/41427 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111145] Re: sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture
I have the same issue, even in Gutsy, with my STAC9250 in my Gateway M685 (also known as NX860 or PA6). If I try to arecord, all I get is this, followed by an application hang, then a read error due to timeout: [EMAIL PROTECTED]:~$ arecord -fcd Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo RIFF$�WAVEfmt D��data� I have pastebin'd the results of alsa-info.sh 0.4.19 ( linux-sound.info server is down, so I can't check for updates). http://pastebin.ca/626876 I have noticed in a BIOS update changelog, Change audio verb table for Vista DTM test -- would Gateway's driver INI files (one for Vista, one for XP) be useful? Note: one interesting fact is that the onboard microphone jack is stereo, and there is no separate line-in jack. -- sigmatel STAC9250 on ATI HDA SB on gateway laptop - no sound capture https://bugs.launchpad.net/bugs/45 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off between brightness levels during fades, and when on battery or at idle
** Summary changed: - LCD backlight turns off when at idle or on battery. + LCD backlight turns off between brightness levels during fades, and when on battery or at idle -- LCD backlight turns off between brightness levels during fades, and when on battery or at idle https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124073] Re: Gutsy Gnome menu System-Preference-Appearance-Fonts
I think what the original bug report is saying is that font changes are no longer applied on the-fly -- now you have to restart Xorg to apply font changes. This is a massive regression in my mind, and the bug should be titled as such. -- Gutsy Gnome menu System-Preference-Appearance-Fonts https://bugs.launchpad.net/bugs/124073 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] Re: LCD backlight turns off when at idle or on battery.
Actually, my laptop is a Gateway M685 -- the non-consumer version of the NX860. Video card is NVIDIA GeForce Go 7600. Gateway actually does not have any proprietary ACPI modules -- they just have standard ACPI 3.0 code, likely in order to comply with Microsoft's desires for Vista. http://www.google.com/search?q=acpi+in+windows+vista I shall attach the output of acpidump (run with no parameters) from my system. ** Attachment added: acpidump from Gateway M685 -- BIOS 72.14 http://launchpadlibrarian.net/8219587/gtw-m685-acpidump.txt -- LCD backlight turns off when at idle or on battery. https://bugs.launchpad.net/bugs/121833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121833] LCD backlight turns entirely off when set between brightness levels.
Public bug reported: Binary package hint: gnome-power-manager When gnome-power-manager dims the screen when on battery or when idle, the backlight turns entirely off. In addition, during the fade the screen blinks: 100%, OFF, 75%, OFF, 50%, OFF. cat /proc/acpi/video/VGA/LCD/brightness: levels: 100 37 12 25 37 50 62 75 87 100 current: 100 The screen is turning off whenever something requests a brightness level between the available discrete levels; thus the default dim-when- inactive brightness of 30 turns the backlight off. For a while, I thought my system was freezing at a black screen at login (battery) or idle (AC), until I remembered the brightness controls. One factor in this is the new /sys/class/backlight/ interface for brightness control, common to all ACPI drivers: This structure does not seem to provide the same, necessary information, such as available discrete brightness levels. /sys/class/backlight/acpi_video0/max_brightness: 100 /sys/class/backlight/acpi_video0/actual_brightness:62 == changes even when keyboard hotkeys are used; g-p-m does not notice this. /sys/class/backlight/acpi_video0/brightness: 62 == changes only when software requests a change. HAL lists num_levels=101, while ideally it should be 8 or 9. Better yet, the kernel itself should provide the discrete levels, or rounding issues may appear. Oddly. the brightness levels 12, 37, 62, and 75 work through echoing into 'brightness', but turn the backlight off if used in g-p-m. Echoing invalid values there turns the backlight off, but echoing into the /proc structure returns 'invalid argument'. Note: the data under /sys/class/backlight is not synchronized with /proc/acpi/video; for consistency, it should be. (My DSDT also provides sys/class/backlight/acpi_video1/ and /proc/acpi/video/GFX0/DD0n/ for n from 1 to 5; LCD is 4. However, I would not expect the values there to be synchronized with acpi_video0 and VGA/LCD.) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - LCD backlight turns entirely off when set between brightness levels. + LCD backlight turns off between brightness levels. ** Description changed: Binary package hint: gnome-power-manager When gnome-power-manager dims the screen when on battery or when idle, the backlight turns entirely off. In addition, during the fade the screen blinks: 100%, OFF, 75%, OFF, 50%, OFF. cat /proc/acpi/video/VGA/LCD/brightness: levels: 100 37 12 25 37 50 62 75 87 100 current: 100 The screen is turning off whenever something requests a brightness level between the available discrete levels; thus the default dim-when- inactive brightness of 30 turns the backlight off. For a while, I thought my system was freezing at a black screen at login (battery) or idle (AC), until I remembered the brightness controls. One factor in this is the new /sys/class/backlight/ interface for brightness control, common to all ACPI drivers: - This structure does not seem to provide the same information as the all the necessary information, such as available discrete brightness levels. + This structure does not seem to provide the same, necessary information, such as available discrete brightness levels. /sys/class/backlight/acpi_video0/max_brightness: 100 /sys/class/backlight/acpi_video0/actual_brightness:62 == changes even when keyboard hotkeys are used; g-p-m does not notice this. /sys/class/backlight/acpi_video0/brightness: 62 == changes only when software requests a change. - HAL lists num_levels=101, while ideally it should be 8 or 9. Better yet, the kernel itself should provide the discrete levels -- otherwise, rounding issues may appear. + HAL lists num_levels=101, while ideally it should be 8 or 9. Better yet, the kernel itself should provide the discrete levels, or rounding issues may appear. Oddly. the brightness levels 12, 37, 62, and 75 work through echoing into 'brightness', but turn the backlight off if used in g-p-m. Echoing invalid values there turns the backlight off, but echoing into the /proc structure returns 'invalid argument'. Note: the data under /sys/class/backlight is not synchronized with /proc/acpi/video; for consistency, it should be. My DSDT also provides acpi_video1/ corresponding to n=4 of /proc/acpi/video/GFX0/DD0n/; however, I would not expect the values there to be synchronized with acpi_video0/ and VGA/LCD/, respectively. ** Description changed: Binary package hint: gnome-power-manager When gnome-power-manager dims the screen when on battery or when idle, the backlight turns entirely off. In addition, during the fade the screen blinks:
[Bug 121831] Current gusty /usr/lib/libglademm-2.4.so.1 missing _ZN4Glib5Class21register_derived_typeEm
Public bug reported: I discovered this when trying to run 'paman' or 'pavucontrol': paman: symbol lookup error: /usr/lib/libglademm-2.4.so.1: undefined symbol: _ZN4Glib5Class21register_derived_typeEm pavucontrol: symbol lookup error: /usr/lib/libglademm-2.4.so.1: undefined symbol: _ZN4Glib5Class21register_derived_typeEm Current libglademm-2.4-1c2a version is 2.6.3-0ubuntu2 ** Affects: paman (Ubuntu) Importance: Undecided Status: New ** Affects: pavucontrol (Ubuntu) Importance: Undecided Status: New ** Also affects: pavucontrol (Ubuntu) Importance: Undecided Status: New -- Current gusty /usr/lib/libglademm-2.4.so.1 missing _ZN4Glib5Class21register_derived_typeEm https://bugs.launchpad.net/bugs/121831 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121832] Current gusty /usr/lib/libgconfmm-2.6.so.1 missing _ZN4Glib13wrap_registerEmPFPNS_10ObjectBaseEP8_GObjectE
Public bug reported: Binary package hint: paprefs When I attempt to run paprefs, I receive this message: paprefs: symbol lookup error: /usr/lib/libgconfmm-2.6.so.1: undefined symbol: _ZN4Glib13wrap_registerEmPFPNS_10ObjectBaseEP8_GObjectE Current version of libgconfmm-2.6-1c2 is 2.18.0-0ubuntu1 ** Affects: paprefs (Ubuntu) Importance: Undecided Status: New -- Current gusty /usr/lib/libgconfmm-2.6.so.1 missing _ZN4Glib13wrap_registerEmPFPNS_10ObjectBaseEP8_GObjectE https://bugs.launchpad.net/bugs/121832 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94133] Re: ipw3945 wireless doesn't work after resume from suspend
Hmm, well, /etc/modprobe.d/ipw3945 should already take care of stopping and starting the daemon, IF you modprobe -r the module first. Try this: make the script 'modprobe -r' and 'modprobe', but not 'killall' the daemon. -- ipw3945 wireless doesn't work after resume from suspend https://launchpad.net/bugs/94133 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94133] Re: ipw3945 wireless doesn't work after resume from suspend
Hmm, well, /etc/modprobe.d/ipw3945 should already take care of stopping and starting the daemon, IF you modprobe -r the module first. Try this: make the script 'modprobe -r' and 'modprobe', but not 'killall' the daemon. -- ipw3945 wireless doesn't work after resume from suspend https://launchpad.net/bugs/94133 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
Perhaps we need a modprobe script to load tifm_sd whenever tifm_7xx1 is
loaded. Something like,
/etc/modprobe.d/tifm_7xx1
install tifm_7xx1 /sbin/modprobe --ignore-install tifm_7xx1 $CMDLINE_OPTS {
/sbin/modprobe tifm_sd ; }
--
[feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
https://launchpad.net/bugs/82680
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
I discovered that the Makefile in the linked download puts the modules in the wrong place when you make install. It puts them in misc/ instead of kernel/drivers/misc. Once I corrected it, I found that it does work for me -- now I can read SD cards. I believe MMC cards may still not be supported -- I tried one and got nothing in dmesg. -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
As you said, The sudo setpci -s nn:nn.n 4c.b=0x02 fix doesn't fix the underlying problem. That is true for me -- I don't have the SDHCI controller at all, so that fix doesn't apply. My card reader is the TI PCI7412 -- 1 Cardbus, 2 firewire (though Gateway only gives me 1), and one media card reader. Perhaps Gateway disabled the SDHCI controller. -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
Even if I modprobe mmc_block (note that tifm_sd already pulls in mmc_core), the /dev/mmcblk0 device still isn't created, and I see nothing new in dmesg. Here's lspci -nnv (nn makes it show both names and numbers.) ** Attachment added: lspci -nnv as root http://librarian.launchpad.net/6452973/lspci-nnv -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
That is correct. I do now see a 254 mmc line after manually modprobing mmc_block, but there still is no /dev/mmcblk0 file created. -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
** Attachment added: /proc/devices with no card inserted http://librarian.launchpad.net/6439595/proc_devices_nocard.txt -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
** Attachment added: /proc/devices with (128MB) sd card inserted http://librarian.launchpad.net/6439596/proc_devices_sdcard.txt -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
Actually, there appears to be no difference between the two. -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82680] Re: [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy)
I have the same issue, except I don't remember it working entirely correctly in Edgy, either -- I'd get duplicate /media/SD /media/SD_ /media/SD__ ... My chip is the PCI7412. All the tutorials I can find refer to some function xx.xx.3 Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller but my system does not have this. It's a Gateway M685. 04:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 04:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 04:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) Also, in dmesg I see tifm_7xx1: sd card detected in socket 1 but I don't get a /dev/mmcblk0 . -- [feisty] regression: ti mmc card reader not working (worked flawlessly in edgy) https://launchpad.net/bugs/82680 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70525] Re: gsynaptics-init won't load settings
The odd thing for me is that it does work... sometimes. I'll log in to find the scrolling not working, but then after a while of normal usage, I'll suddenly note that the scrolling has started working. It seems really random to me. The CoastingSpeedThreshold misspelling has been fixed, but I still get: ** (gsynaptics-init:21589): WARNING **: Using synclient Unknown parameter CoastingSpeedThreshold -- gsynaptics-init won't load settings https://launchpad.net/bugs/70525 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70525] Re: gsynaptics-init won't load settings
(no 'edit' or 'append' function) Oh, and I also forgot this: somewhere along the line I manually put the relevant circularscrolling options directly into xorg.conf. (I used synclient directly to get the rightedge just perfect): snip Option Emulate3Buttons true Option TapButton0 0 Option TapButton1 0 Option TapButton2 0 Option MaxTapTime 0 Option RightEdge 5975 Option CircularScrolling 1 Option CircScrollDelta 0.234 Option CircScrollTrigger 3 EndSection -- gsynaptics-init won't load settings https://launchpad.net/bugs/70525 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70525] Re: gsynaptics-init won't load settings
I noticed something new (now on Fiesty also): Although the misspelling seems to have been fixed, my setting still don't reliably load. ** (gsynaptics-init:10682): WARNING **: Using synclient Unknown parameter CoastingSpeedThreshold When I first log in, the circular and vertical scrolling don't work, but if I try again some arbitrary time later, it DOES work. I've even put the CircularScrolling options directly in xorg.conf, yet the same issue remains. Another suggestion: The synaptics driver with SHMConfig enabled should be set up, and gsynaptics should be installed, if a touchpad is detected during setup. If it is made automatic, people won't have to deal with it manually, and it'll be far easier to disable tapping [assuming the other bug about the synaptics driver ignoring that setting has been fixed]. If the touchpad is made CorePointer and any other mice are set to use evdev with SendCoreEvents, then the secondary mouse will be hot- pluggable! -- gsynaptics-init won't load settings https://launchpad.net/bugs/70525 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70525] gsynaptics-init won't load settings
Public bug reported: Binary package hint: gsynaptics Install gsynaptics and have gsynaptics-init in startup (or just run it manually in the console)... $ gsynaptics-init ** (gsynaptics-init:5925): WARNING **: Using synclient Unknown parameter CoastingSpeedThreashold ..and because it doesn't run, it doesn't load my preferences such as Circular Scrolling. Here's my section in xorg.conf, for reference: Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option CorePointer Option Device /dev/psaux Option Protocol auto-dev Option HorizScrollDelta 0 Option SHMConfig on Option Emulate3Buttons true Option TapButton0 0 Option TapButton1 0 Option TapButton2 0 Option MaxTapTime 0 Option RightEdge 5982 EndSection ** Affects: gsynaptics (Ubuntu) Importance: Undecided Status: Unconfirmed -- gsynaptics-init won't load settings https://launchpad.net/bugs/70525 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
