Would not it make sense to handle spindown_time the same way, adding a
spindown_time_battery so that the user can configure different timeouts for
hard drives?
I used to have 20 minutes when on AC and 3 when on battery. I don't understand
how to control it with pm-utils
--
pm-utils doesn't
I updated two days ago to Lucid and I am finding the whole indicator stuff on
the right to be totally annoying even if it is not new anymore.
I miss the tooltips, I hate the bluetooth icon, I hate the me-menu and the
session button without icons.
This indicator technology has potential but is
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Ricoh SD controller (1180:e822) not working: unknown version
https://bugs.launchpad.net/bugs/603445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Confirming with a Brother MFC-5460CN on Lucid. Please re-open this.
--
printer prints page at wrong position, page cut
https://bugs.launchpad.net/bugs/293832
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Gentoo has a patch here:
http://bugs.gentoo.org/show_bug.cgi?id=318567
(did not try it)
Confirming this on a Latitude E5410.
** Bug watch added: Gentoo Bugzilla #318567
http://bugs.gentoo.org/show_bug.cgi?id=318567
--
Dell Latitude E6410 Touchpad - Not all functions working; detected as
*** This bug is a duplicate of bug 601113 ***
https://bugs.launchpad.net/bugs/601113
** This bug has been marked a duplicate of bug 601113
Dell Latitude E6410 Touchpad - Not all functions working; detected as PS/2
mouse
--
Touchpad not recognized on new Dell E5410
Public bug reported:
Dell has updated its Latitude laptop line and it appears that once again
the touchpad is not correctly recognized.
/proc/bus/input/devices shows:
I: Bus=0011 Vendor=0002 Product=0001 Version=
N: Name=PS/2 Generic Mouse
P: Phys=isa0060/serio1/input0
S:
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/51609552/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/51609554/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51609555/BootDmesg.txt
**
Public bug reported:
Also tested on Maverick alpha 2. The laptop is a Dell E5410.
This SD reader does not work. Upon insertion of a SD card this shows in dmesg:
[ 3466.345329] mmc0: Unexpected interrupt 0x0200.
[ 3466.345335] sdhci: == REGISTER DUMP ==
[ 3466.345343]
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/51610314/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/51610315/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51610316/BootDmesg.txt
**
Alright then mine is a different problem.
However in the event of a reboot the dhcp client is not supposed to release the
address, since it is going to ask one again in a minute.
--
dhclient3 hangs on shutdown
https://bugs.launchpad.net/bugs/571933
You received this bug notification because
Alright then mine is a different problem.
However in the event of a reboot the dhcp client is not supposed to release the
address, since it is going to ask one again in a minute.
--
dhclient3 hangs on shutdown
https://bugs.launchpad.net/bugs/571933
You received this bug notification because
It seems that the DHCP server does not reply to DHCPRELEASE so dhclient waits
until timeout.
My DSL modem does the same.
My workaround is to remove /etc/rc0.d/S35networking and
/etc/rc6.d/S35networking, but I would like to know if there is a way to
configure dhclient to ignore release requests,
It seems that the DHCP server does not reply to DHCPRELEASE so dhclient waits
until timeout.
My DSL modem does the same.
My workaround is to remove /etc/rc0.d/S35networking and
/etc/rc6.d/S35networking, but I would like to know if there is a way to
configure dhclient to ignore release requests,
I change the volume and the lcd brightness by putting the mouse on the
indicator, scrolling up or down and reading the tooltip.
This is fast and usable. How would this work without tooltips?
--
please include status messages/tooltips
https://bugs.launchpad.net/bugs/527458
You received this bug
I installed sensors-applet_2.2.5-3_i386 and libsensors-applet-
plugin0_2.2.5-3_i386 straight from debian and it seems to work. It does
not need hddtemp anymore.
--
Please merge sensors-applet 2.2.5-3 (universe) from Debian (unstable)
https://bugs.launchpad.net/bugs/380669
You received this bug
Public bug reported:
Binary package hint: ubuntuone-client
I want to put the Ubuntu One folder wherever I please among my files.
Please add the possibility to manually set up the folder's path and
name, should be really easy.
ProblemType: Bug
.home.andrea..cache.ubuntuone.log.oauth.login.log:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35412488/Dependencies.txt
** Attachment added: UbuntuoneClientPackages.txt
http://launchpadlibrarian.net/35412489/UbuntuoneClientPackages.txt
** Attachment added: XsessionErrors.txt
The old way was jaunty without the applet or any previous release since ubuntu
existed (System menu has icons up to jaunty).
Jaunty is exactly affected by this in its default settings, and it looks awful.
All gnome programs have icons in menus. Through gconf one can choose to
see them or not
Public bug reported:
Binary package hint: indicator-applet-session
Please set some menu icons in the indicator-applet-session. Then honour
the gconf setting and hide them if necessary, but let users who like to
have icons for common actions have them.
It should not take a lot of work and would
Is it going to be backported or updated in intrepid too?
--
[patch] Inactive import folder in f-spot
https://bugs.launchpad.net/bugs/293305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-power
Importance: Undecided = Unknown
Bugwatch: None = GNOME Bug Tracker #568341
Status: New = Unknown
--
Hardware and software don't agree on brightness level
https://bugs.launchpad.net/bugs/295560
You received this bug notification because you are a member
my conclusion is that gnome power manager can:
notify change events to the user (brightness bar) (ok here)
dim the screen after a period of inactivity, if user wishes so. (and set it
back the previous level) (probably ok too, when the xrandr issue is fixed)
and must not:
1: use xrandr
2: set
Non unread vFolders still have a wrong unread message count for me.
In general this new Evolution (since intrepid) is handling read/unread
count totally wrong. Can we hope in another minor release in the
future?
--
Unread search folder removes messages as soon as their unread flag is toggled
I still have this after the update. However it seems less severe.
It is probably counting spam and automatically marked as read for unread
messages.
I hope in a new bugfix release...
--
Search folders have the wrong Unread count
https://bugs.launchpad.net/bugs/291881
You received this bug
** Description changed:
- Binary package hint: hal
+ Binary package hint: gnome-power
- The following description is a little complicated, but if you just play
- around with brightness controls, you will easily see for yourself what I
- am talking about.
-
- Since Intrepid (and Fedora 10)
I did some further investigation and updated the description. I think
that some kind of cooperation between all the project marked as affected
is necessary, at least for an initial decision.
I would like to know (from Dell?) if the bios can be made stop handling
brightness at all from userspace
** Also affects: hal
Importance: Undecided
Status: New
--
Hardware and software don't agree on brightness level
https://bugs.launchpad.net/bugs/295560
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
you rock!
Now the package can be fixed...
btw, the schema is missing as well.
--
smb:// URI's do not work
https://bugs.launchpad.net/bugs/291259
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: hal (Fedora)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: hal
- Since Intrepid Gnome has found a new way of setting brightness on my
- laptop (Dell Latitude D630) which interferes with the FN-buttons and the
- old libsmbios way.
+
Yes I am doing so.
sudo dellLcdBrightness -a
Read AC Mode Setting
current: 0
min: 0
max: 7
libsmbios worked well in hardy, but now it gets confused too. For example if I
do this:
1: Fn+down till mininum brightness
2: raise brightness to the maximum from the panel applet
I
confirming with nvidia 177.82 (downloaded from nvidia website), geforce 7050,
AMD Athlon 64 x2 BE 2350
Also version 169 did not compile...
--
Titlebar incorrectly drawn with geforce 5/6/7, compiz and human-theme
https://bugs.launchpad.net/bugs/99508
You received this bug notification because
Public bug reported:
Binary package hint: hal
Since Intrepid Gnome has found a new way of setting brightness on my
laptop (Dell Latitude D630) which interferes with the FN-buttons and the
old libsmbios way.
I don't know how it does it, since ACPI does not support brightness setting on
my
without hald-addon-dell-backlight you can change brightness only through
FN-keys, which work at a hardware level, (at least on many models).
thanks to hald-addon-dell-backlight, you can change brightness trough software,
and get a nice screen notification when you use the FN-keys.
If you don't
FN keys work at a hardware level, so they always work.
hald-addon-dell-backlight does this:
listen for changes by the FN-keys and notifies software that cares about it
(through HAL)
lets the brightness be changed by software (through HAL as well), eg, after
some inactivity
I think this bug can
Public bug reported:
Binary package hint: gnome-panel
software involved:
Ubuntu Intrepid, gnome-panel version 1:2.24.1-0ubuntu2
to reproduce:
1: use nautilus to browse a samba server's shares list. For example
smb://localhost
2: add a nautilus bookmark to that location
3: open the new bookmark
It effectively makes the crashes stop, but I think that the fix solves just the
urgent part of the bug. HAL still reports to gnome-power-manager that it can
change the brightness, so probably all the related work gets done and simply
fails every time with no error.
The brightness applet for
latitude d630 here. If I remember correctly there are some older latitudes as
well: d620, d420.
btw did you try the command line dellLcdBrightness or the panel applet and got
smooth operation?
--
HAL lockups or crashes dell laptops with a BIOS password
https://bugs.launchpad.net/bugs/189814
I asked a friend to test on an inspiron and he did not have problems.
I don't have access to any more dell machines, maybe it's latitude only.
Seems kind of strange in fact to need the bios password to change brightness,
at least it's not done on every line.
--
HAL lockups or crashes dell
probably on older kernel Hal does not report brightness setting
capability to gnome-power-manager, so the bug is just not triggered. You
also loose that functionality if you note.
--
HAL lockups or crashes dell laptops with a BIOS password
https://bugs.launchpad.net/bugs/189814
You received
Hal does not run the command with the password and that's how you are
supposed to reproduce this bug.
--
HAL lockups/crashes on Dell D-series Latitudes w/ BIOS password
https://bugs.launchpad.net/bugs/189814
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: hal
This is a follow-up bug to reap the fruits of comments and testing of #189814
and its duplicates. The root cause has been really hard to find as it seemed a
kernel issue related to the touchpad at first.
The problem reported here and its cause
A detailed new bug report as been opened, now that we got to the root of this:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/244606
please mark this as closed and anyone interested move to the new one.
--
[hardy]computer and touchpad is buggy with BIOS password set
After many comments and investigations, found the root cause!
** Changed in: hal (Ubuntu)
Sourcepackagename: linux = hal
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = (unassigned)
Status: Triaged = New
--
HAL crashes dell laptops with a BIOS password
cable
- into my computer.
+ This description is totally rewritten by Andrea Ratto (LP andrearatto) to
recap the situation. The root cause has been really hard to find as it seemed a
kernel issue related to the touchpad at first.
+ The problem reported here and its cause have already been confirmed
I really did not know that I could alter the original description and do
the other stuff myself.
Dell guys please read the description, this matters to you.
** Also affects: libsmbios
Importance: Undecided
Status: New
--
HAL crashes dell laptops with a BIOS password
Just answer me an apparent silly question if you are experiencing this.
Do you have a BIOS password set?
--
[hardy]computer and touchpad is buggy when running on battery
https://bugs.launchpad.net/bugs/189814
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think I now where the problem lies ultimately. Can you just do a small
test for me? Add a brighness applet to the gnome panel and try to see if
that works smoothly.
On my d630 it does not work with a bios password set, but does without.
Il giorno lun, 30/06/2008 alle 08.53 +,
This is my idea:
gnome-power-manager tries to dim the brightness of the screen after some
inactivity and then reset it upon input.
gnome-power-manager calls HAL to do the job. HAL has multiple methods of
handling brightness of LCD panels. On dell machines, since hardy it uses a
libsmbios.
I really took interest in fixing this and it seems I finally hit the
root of the problem. Thanks to you all for your comments and trials, as
without the hint on gnome-power-manager I would never have though of
such a thing. The community is always great!
If others having this problem confirm that
With the heat of these last days it seems to happen even more. Kernel
parameters did not solve the issue.
Yesterday I also uncovered something. I was watching a video on youtybe and had
the screensaver coming in every minute, so I touched the touchpad everytime the
screen started to go black.
On my latitude d630 it happens both on battery and on ac. I added
i8042.nomux=1 to the kernel command line and now it does not crash the
whole machine anymore. It also seems to happen less frequently, but it
is still there. It just came up now: lost my touchpad functionalities...
--
You might want to give a try to adding i8042.nomux=1 to your kernel command
line.
It is *maybe* working for me.
And if someone knows what does that mean, I'd like to know...
--
[hardy]computer and touchpad is buggy when running on battery
https://bugs.launchpad.net/bugs/189814
You received
still present with 2.6.24-19-generic. Here are my findings:
1 battery or not battery it happens
2 it starts when using again the touchpad after a period of inactivity. (Maybe
on battery this period can be shorter)
when it starts it freezes everything for some seconds, CPU usage get to 100% on
I have this very same problem with 2.6.24-17 generic on a dell latitude
d630. And it really bothers me.
My latitude has a touch point, a sort of secondary mouse in the middle
of the keyboard. I was wondering if this bug is somewhat related only to
similar hardware configurations. Is there someone
dammit it crashed again. So it is not due to frequency scaling... sorry
for the previous post.
--
[hardy]psmouse.c kernel panic
https://bugs.launchpad.net/bugs/207919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is preliminary, but I disabled cpu frequency scaling and the
touchpad has not given problems for a while. Could someone try this too?
--
[hardy]psmouse.c kernel panic
https://bugs.launchpad.net/bugs/207919
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fixed in my PPA: https://launchpad.net/~andrearatto/+archive
--
pam-encfs fails on upgrade to Hardy
https://bugs.launchpad.net/bugs/205783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Having similar problems on a Dell Latitude D630, Bios A09 kernel
2.6.24-17-generic, latest updates on hardy. It was ok with gutsy. Got several
crashes and lots of touchpad synch issues in one day. Tried a custom DSDT, but
did not help.
I would raise the importance as it basically makes the
Dell too here.
Every transition in a bug state should have a mandatory comment I guess it
means that Dell does not care for this issue.
--
power.sh: wrong laptop_mode activation
https://bugs.launchpad.net/bugs/89269
You received this bug notification because you are a member of Ubuntu
Bart Samwel:
FWIW, in Debian I solved this by removing the acpi-support logic for laptop
mode tools completely
That is the quick way to fix it, exactly what I have on my laptop.
Though I think that in the long run would be better to do it the other way
around: remove enabling/disabling based
acpi-support does support running scripts on lid clode.
It does not notify a battery critical event though. Maybe that functionality
could be added to acpid and thus to acpi-support? Does it require polling?
GNU/Linux, not just Ubuntu, needs one single framework for powermanagement, be
that
Allright, I have this very same problem on three different machines.
Lots of people have it.
It's not a showstopper, but it's a scary thing to have in a stable release for
this many months.
Let's raise the priority, let's look into this.
Looks like a synchronization problem to me. Did anyone
Finally something is moving.
fixing point ONE does not really help the whole powermanagement
subsytem, because there is still laptop-mode touching the disk
parameters.
What's most importat of this bug is that things should make sense. acpi-support
vs laptop-mode (vs powernowd). Which one
*** This bug is a duplicate of bug 121487 ***
https://bugs.launchpad.net/bugs/121487
confirming here, was working in feisty
--
wvdial 1.58-1.2ubuntu2 (gutsy) breaks gnome ppp dialog hang authenticating
https://bugs.launchpad.net/bugs/136707
You received this bug notification because you
This is a common problem:
http://ubuntuforums.org/showthread.php?t=587410
I have it once in a while too.
I think it happens only on fast, dual core machines, but it's really ugly to
have in a stable release. I would give it high priority.
Frankly it's strange that we don't have lots of bug
this is fixed in hardy.
here is a backport for gutsy:
http://ppa.launchpad.net/andrearatto/ubuntu/pool/main/libp/libpam-encfs/libpam-encfs_0.1.4.1-2~ppa3_i386.deb
--
libpam-encfs causes problems with sudo
https://bugs.launchpad.net/bugs/111595
You received this bug notification because you are a
I can confirm the problem, it's annoying, please roll a fix out.
--
libpam-encfs causes problems with sudo
https://bugs.launchpad.net/bugs/111595
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
confirmed on a dell d620, feisty clean install
--
Microphone does not work on Dell Inspiron 630m
https://bugs.launchpad.net/bugs/42600
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I can confirm this bug it's present also in festy.
There is also another bug I just found, half in power.sh and half in the
init script:
powersaving it's not activated on boot (on battery) if the laptop was
shut down while on battery.
I will come up with some patches if I hear some noise about
Public bug reported:
Binary package hint: acpi-support
I have divided this report into five parts, the first one is a real bug
which prevent correct functionality, the other are good things that
could be achieved with little effort.
power.sh should be really reworked, here is why:
Public bug reported:
I have tested Fedora Core Test 6 in these days and found they finally got
printing in gnome allmost right. You can easily control your printer's settings
about:
pages per sheet
color or monochrome
quality
plus the other usual stuff.
Also printing from openoffice.org seems
72 matches
Mail list logo
