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
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 no
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.
** Summ
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
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 b
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
auto
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
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
t
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
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 notific
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
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
htt
** 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.ne
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 r
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
'y
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). "
I sure hope it is being left as valid for 'linu
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
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 n
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
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=scheduling&id=16345
http://patchwork.ozlabs.org/linuxppc/patch?q=s
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 the
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; th
** 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
** 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
** 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
** 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 U
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.
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 h
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 s
[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 b
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
** 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
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
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...
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
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 batt
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: _ZN4G
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
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
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.g
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
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 supporte
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] reg
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
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
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
** 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.
** 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
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
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/64529
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
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 wo
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 st
(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):
Option "Emulate3Buttons" "true"
Option
54 matches
Mail list logo
