*** This bug is a duplicate of bug 48008 ***
https://bugs.launchpad.net/bugs/48008
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 48008, so it is being marked as such. Please look at
th
Hi Wub
Please attach the output of running the following command:
hal-device `hal-find-by-capability --capability "battery"`
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: New => Incomplete
--
Battery Monitor cannot re
nd the screen will go back to
100% brightness
6. Press brightness down once; you should get a percentage reading in a small
pop-up, what does this say? And does it go to a brightness level that match the
reported?
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: Incomplete => In Progress
--
kde-guidance-powermanager: python2.5 crashed with AttributeError in
checkBatteryCritical()
https://bugs.launchpad.net/bugs/231163
You received th
Please try runnning "sudo apt-get dist-upgrade"; this thould report what
the problem is with your dependencies.
--
After full upgrade, nothing works.
https://bugs.launchpad.net/bugs/235659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Feel free to report any other bugs you find.
** Changed in: hal (Ubuntu)
Status: New => Invalid
--
button.state.value switched for lid event
https://bugs.launchpad.net/bugs/230056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Could be a bios that has gotten confused at some point. I'll close this.
--
button.state.value switched for lid event
https://bugs.launchpad.net/bugs/230056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: Confirmed => In Progress
--
displayconfig resolution change bug
https://bugs.launchpad.net/bugs/82279
You received this bug notification because you are a member of Ubuntu
Bugs, wh
You shouldn't mark it as fix committed until it is committed to ubuntu
and not just a PPA. I'll have a look at the patch when time permits.
** Changed in: kde-guidance (Ubuntu)
Status: Fix Committed => Confirmed
--
displayconfig resolution change bug
https://bugs.launchpad.net/bugs/82279
@Aleks
Btw. i would advice you to provide info on your current installed version of
'hal', and your kernel version.
See https://wiki.ubuntu.com/DebuggingHal for some debugging information
you can provide to help.
--
button.state.value switched for lid event
https://bugs.launchpad.net/bugs/23005
The problem is, that HAL reports the opposite for your lid.
"button.state.value" should be false when the lid is open, but for your
laptop it reports true.
The bug might not actually be a HAL issue, but could be connected to a
lower layer (eg. kernel issue), but I'm not capable of determining that
)
Assignee: (unassigned) => awen (andreas-wenning)
Status: New => Incomplete
** Tags added: guidance-powermanager
--
Lock screen happens on Lid open, not Lid closed
https://bugs.launchpad.net/bugs/230056
You received this bug notification because you are a member of Ubuntu
Bugs, wh
The fix for the kde-guidance-powermanager part of this problem is
attached. See also duplicate bug 218889 for further info.
** Attachment added: "kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff"
http://launchpadlibrarian.net/14473412/kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff
--
Scr
Thanks for clearing that up.
Then this is a wishlist bug. g-p-m doesn't actually handle battery
insertions.
The system freeze however has nothing to do with this or guidance-
powermanager. I will suggest you look in /var/log/syslog or some of the
other logs to see if you can find a cause for the
This patch adds the recommends on python-uniconvertor as well as patches
inkscape to use the correct binary.
inkscape (0.46-0ubuntu3) intrepid; urgency=low
* Make use of UniConvertor to r/w additional file formats (LP: #200750).
- Added recommends for python-uniconvertor.
- Added patch
** Summary changed:
- Add uniconvertor package to Recommends (for Corel Draw formats support)
+ Add python-uniconvertor to Recommends and patch inkscape (for Corel Draw
formats support)
** Description changed:
Binary package hint: inkscape
- Please add uniconvertor package to Recommends -
@Luca
Am I understanding right, that the battery is not present (eg. physically
removed) when booting?
And does it work if you are running on A/C when booting and the battery
is inserted?
--
guidance doesn't find any battery if battery is not present on startup
https://bugs.launchpad.net/bugs/2
That is how it handles batteries as it is now. It doesn't really handle
removal/insertion of batteries that well.
This bug should be marked as wishlist.
--
guidance doesn't find any battery if battery is not present on startup
https://bugs.launchpad.net/bugs/228568
You received this bug notifica
** Summary changed:
- Sync request: libapache-mod-random from debian
+ Please sync libapache-mod-random 2.1-1 (universe) from Debian unstable (main)
** Description changed:
- Binary package hint: libapache-mod-random
-
- Please sync libapache-mod-random (2.1-1) from debian/unstable.
-
- All ub
*** This bug is a duplicate of bug 226808 ***
https://bugs.launchpad.net/bugs/226808
** This bug has been marked a duplicate of bug 226808
Sync request: libapache-mod-random from debian
--
Please sync libapache-mod-random 2.1-1 (universe) from Debian unstable (main).
https://bugs.launchpa
libqt4-dev need updating to 4.4.0~rc1 before the sync can be done.
Missed it while looking through the dependencies; i'll write here again
when it is updated.
--
Please sync qtoctave from debian unstable
https://bugs.launchpad.net/bugs/227099
You received this bug notification because you are a m
Public bug reported:
Binary package hint: qtoctave
Please sync qtoctave 0.7.4+dfsg-1 (universe) from Debian unstable
(main).
Changes in ubuntu since common version listed here. All changes has been
applied in debian version (0.7.1+dfsg-1), and can therefore be dropped
as ubuntu-specific changes.
Also affects kde-guidance-powermanager on certain laptops. Should be
partly fixed in kde-guidance-powermanager.
** Also affects: kde-guidance (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenn
@Daniel
I'll do that. Thanks for pointing me to that page. Searching for it just got me
to a short description with a lot less info about the sync process.
Please sync libapache-mod-random 2.1-1 (universe) from Debian unstable
(main).
Explanation of the Ubuntu delta and why it can be dropped:
T
Public bug reported:
Binary package hint: libapache-mod-random
Please sync libapache-mod-random (2.1-1) from debian/unstable.
All ubuntu-specific changes is also present in the debian package. I've
personally made the changes to the ubuntu package as well as in debian.
** Affects: libapache-mod
Public bug reported:
Binary package hint: libapache-mod-layout
Please sync libapache-mod-layout (5.1-1) from debian/unstable.
All ubuntu-specific changes is also present in the debian package. I've
personally made the changes to the ubuntu package as well as in debian.
** Affects: libapache-mod
ease):
Main release feature is CDR14 format importer (new CorelDRAW X4 format).
** Tags removed: gutsy hardy needs-packaging
** Changed in: ubuntu
Assignee: awen (andreas-wenning) => (unassigned)
--
Import request: python-uniconvertor in debian
https://bugs.launchpad.net/bugs/200
I've prepared both the fix in Ubuntu and the fix in Debian, and I can
confirm, that the we can just make an import from debian unstable.
--
Please sync imapsync 1.249-1 from Debian(Unstable)
https://bugs.launchpad.net/bugs/225717
You received this bug notification because you are a member of Ubun
@Rick
The output indicates that it is a HAL-bug. I don't know if it is related to the
bug you mention; for now i'm just marking this as a hal-bug.
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kde-guidance (Ubuntu)
Status: New => Invalid
--
Gui
Hi Rick
Please check if the command "hal-device `hal-find-by-capability
--capability battery`" shows both your batteries. If it does, just
attach the output. If not, please provide the output of the lshal
command.
--
Guidance-power-manager stopped working after upgrade to Gutsy
https://bugs.lau
New ~ppa4 uploaded. Please test once again, thanks.
You should be able to reproduce stepping double steps:
100 -> 71 -> 42 -> 14 -> 0
0 -> 28 -> 57 -> 85 -> 100
ie. it should be the same seen from your point of view compared to ~ppa2.
--
[hardy] HAL reports multiple button presses when brightnes
Please try starting the attached script in a terminal "./gpmhelper.py",
and do a single press on the brightness-down button. Please attach the
generated output. (Your brightness will seriously misbehave while this
script is running, but that is not interesting, just the output is). You
exit pressin
** Summary changed:
- [hardy] brightness on KDE jumps from 100% -> 42% -> 0%
+ [hardy] HAL reports multiple button presses when brightness keys are pressed
only once
** Description changed:
Binary package hint: kde-guidance-powermanager
- Hello,
+ "lshal -m" output from a single key-press
You will still get multiple output when issueing "lshal -m". I'm trying
to work around this issue, so the interesting is how much your
brightness change each time you press a button; it should drop from
about 100% to around 85% (as you have 8 levels). Does this work, or how
much does it drop with t
Thanks for your feedback.
I've uploaded a new version of the work-around to my PPA. It's named the
same except the version numbering ends in ~ppa2. Please test if this
fixes it. If you reply quickly I might have a chance to get it into
Hardy.
--
[hardy] brightness on KDE jumps from 100% -> 42% -
I've uploaded a test version of a possible work-around to
https://launchpad.net/~andreas-wenning/+archive . Go for the version
0.8.0svn20080103-0ubuntu17~ppa1 of kde-guidance-powermanager. Report
back if this works for you. Remember that you need to restart the
powermanager after installing a new v
It looks like HAL sends us multiple brightness-button events when you
press the button only once. Just to be sure about this, try running
"lshal -m" to see what events is send by HAL. Please attach the output.
--
[hardy] brightness on KDE jumps from 100% -> 42% -> 0%
https://bugs.launchpad.net/bu
Strange. You have the exact same number of brightness levels reported by
HAL as me, so guidance-power-manager should work the same way for both
of us.
Can you please test the attached version. It will report every
brightness change that is done on stdout. Please try to press the
brightness-up or -
13559858/powermanage.py
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: New => Incomplete
--
[hardy] brightness on KDE jumps from 100% -> 42% -> 0%
https://bugs.launchpad.net/bugs/218889
You received this bug notification because you are
That crash has nothing to do with the lock-up of your computer, sorry.
It is probably because the dbus has been restarted, that you received
the above crash. I don't know if a dbus restarting can cause your
computer to freeze (have never heard about that it could); but in any
case you should try t
This is present in an up-to-date Hardy as well. If needed I can provide
a new example of this.
--
Modifies xorg.conf way too heavily on resolution change
https://bugs.launchpad.net/bugs/48008
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber
hunspell-da removed as a depends
** Changed in: language-support-writing-da (Ubuntu)
Status: New => Fix Released
--
language-support-writing-da depends on conflicting packages
https://bugs.launchpad.net/bugs/214969
You received this bug notification because you are a member of Ubuntu
Bugs
Just tested the newest daily live-cd, and it is still present. The
problem occurs, if you do things the opposite way.
You are supposed to open krdc, choose vlc or rdp (by clicking the
button), fill out the connect field and press enter.
If you open krdc, start by filling out the connect field and
If I install amarok-dbgsym and amarok-xine-dbgsym and try again, the
problem is still present, but now the backtrace is totally empty. What
other means can I try to obtain a better backtrace?
--
[hardy] amarok crashes when mp3 player controlled by amarok is plugged in and
automounted
https://bug
It will only work if we are using english, yes.
Using unicode(i18n("Desktop")) is not entirely correctly IIRC at looking
at another similar bug. I can look into this in a few days.
--
wineconfig doesn't work
https://bugs.launchpad.net/bugs/82723
You received this bug notification because you are
g-p-m isn't capable of updating the number of batteries, while it is
running. If you wan't it to show the second battery, you should just
restart it. Close the power manager and start it using the command
guidance-power-manager . This should be marked as wishlist.
--
[Kubuntu Hardy] kde-uidance-p
Public bug reported:
Binary package hint: language-support-writing-da
Package: language-support-writing-da
The package depends on both myspell-da and hunspell-da , but hunspell-da
conflicts with myspell-da and is thereby made uninstallable.
** Affects: language-support-writing-da (Ubuntu)
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: Triaged => In Progress
--
Guidance displayconfig does not automatically detect monitor config on systems
with no xorg.conf
https://bugs.launchpad.net/bugs/203378
You received th
Informational mail has been sent to [EMAIL PROTECTED] and ubuntu-
[EMAIL PROTECTED] . And I'm subscribing ubuntu-release.
Just for info, I can tell that some changes is still pouring in here
closing in on the freeze coming up very soon. So the upload might need
to be coordinated with Scott Kitterm
** Attachment added: "kde-guidance_0.8.0svn20080103-0ubuntu13.debdiff"
http://launchpadlibrarian.net/13297018/kde-guidance_0.8.0svn20080103-0ubuntu13.debdiff
--
U/I FFE: power consumtion monitor
https://bugs.launchpad.net/bugs/214774
You received this bug notification because you are a membe
** Attachment added: "snapshot3.png"
http://launchpadlibrarian.net/13296876/snapshot3.png
--
U/I FFE: power consumtion monitor
https://bugs.launchpad.net/bugs/214774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Public bug reported:
Binary package hint: kde-guidance
kde-guidance-powermanager
I'm requesting a FFE for adding power consumption display to the
guidance-power-manager. This will ultimately bring the guidance-power-
manager feature-wise closer to the power-manager in gnome. For a laptop
user th
@kurosaki
You should be able to install and start the power-manager in kde4 with no
problem. But much too late for inclusion in hardy+kde4 as default.
--
[Hardy - beta ]guidance-power-manager kde4
https://bugs.launchpad.net/bugs/213097
You received this bug notification because you are a member
Guidance power manager heavily uses the dcop interface which is not
avaible in kde4. Some sort of trasition / rewriting is needed to have it
work under kde4.
--
[Hardy - beta ]guidance-power-manager kde4
https://bugs.launchpad.net/bugs/213097
You received this bug notification because you are a
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
--
"Disk&Filesystems" module does not load after plugging in iPod
https://bugs.launchpad.net/bugs/124856
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Found the problem myself; discard the previous message. Tried to do the
diff thing too, and that didn't really show what expected.
>From the lshal.unplugged file:
ac_adapter.present = true (bool)
The problem is, that your AC adapter is reported as present (eg. plugged
in) by HAL even when it is
@Luis
Can I please have you provide the output (if any) of the following command:
"hal-find-by-capability --capability ac_adapter"
Does the above output change whether you are on AC or on battery?
If it exists, please provide the output of the following command when plugged
to AC and when on batt
When changing the sliders (as an admin) and saving, this should IIRC get
saved in the xorg.conf. So the sliders do have a point, even though they
don't change the gamma Live.
If you have a good idea for an ideal solution, feel free to open it as a
wish-list bug.
--
[hardy] sliders for gamma corr
The gamma sliders and the target gamma is two different things. The real
problem is that your video card / driver combination doesn't support the
live gamma changes that is done using the sliders. The fix that has been
made should prevent the displayconfig from crashing (and allowing you to
exit, a
@Sven
I can see that you don't have the new version of displayconfig.py (by comparing
the line numbers in the traceback with the linenumbers in the new file)
If you have touched the file previosly, it will not be overwritten when
it is updated.
The file is located in /usr/share/python-support/kd
@Sven
Can I have you provide a fresh output from trying to set the gamma while
running displayconfig from the terminal?
--
[hardy] sliders for gamma correction don't work in displayconfig
https://bugs.launchpad.net/bugs/201468
You received this bug notification because you are a member of Kubunt
I can confirm that the new version 1:2.4.0-3ubuntu1 of openoffice.org
fixes the problem. Thanks!
** Changed in: openoffice.org (Ubuntu)
Status: Fix Committed => Fix Released
--
[Ubuntu] [hardy] regression: oowriter can't open some documents
https://bugs.launchpad.net/bugs/189206
You recei
@Daniel
AFAIK, no. The two packages containing the same file now conflicts. Until
src:hyphen enters main this is the best we can do.
--
package openoffice.org-hyphenation-en-us None [modified:
/var/lib/dpkg/info/openoffice.org-hyphenation-en-us.list] failed to
install/upgrade: trying to overwr
I've added kde-guidance 0.8.0svn20080103-0ubuntu11~ppa1 to my PPA.
Please test; you should be able to exit it now. See:
https://launchpad.net/~andreas-wenning/+archive
Please test, and report back if it works.
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen
I've added kde-guidance 0.8.0svn20080103-0ubuntu11~ppa1 to my PPA. This
should at least make displayconfig not crash. See: https://launchpad.net
/~andreas-wenning/+archive
Please test, and report back if it works.
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen
Tried to make a new user and starting fram scratch, so no personal
amarok settings was present. This didn't change anything, problem still
present.
As not everybody else can reproduce it, it might be a problem with certain
devices.
I'm using a Denver MP-1021
I don't have an extra mp3 player to t
Public bug reported:
Binary package hint: amarok
amarok 2:1.4.8-0ubuntu5
How to reproduce:
1. Be sure that the mp3-player is set to be handled by amarok (as generic audio
player)
2. Plug in mp3-player
3. KDE pops up, choose to view/open (eg. automount)
4. Amarok crashes.
If you choose not to h
@Sven
Which video-driver are you using? I remember hearing some problems regarding
gamma (changing) problems with the nvidia driver.
--
[hardy] sliders for gamma correction don't work in displayconfig
https://bugs.launchpad.net/bugs/201468
You received this bug notification because you are a mem
I'm marking this as fix released, as the problem looks to be fixed in
the changelog. If the problem is indeed still present please reopen the
bug report, and don't hesitate to submit bug reports in the future. To
reopen the bug report you can click on the current status, under the
Status column, an
@ktulu
A new version of the kde-guidance package has been released, so this will
override the onw from my PPA in any case. After todays update, if the problem
isn't fixed, not even with a new user, please report back.
--
Modify and New in userconfig don't work due to unicode errors
https://bugs
@ktulu
Did you remember to uninstall the version of kde-guidance that you downloaded
from my PPA. As the versions are numbered the same, you wouldn't get this new
one.
Check that my PPA is not in your sources.list. Then uninstall kde-
guidance, use apt-get autoclean, and reinstall kde-guidance.
@Zem
You should report it as a seperate bug (probably already exists in launchpad)
regarding the problem in the nvidia driver.
--
Fn-Keys for adjusting brightness of the display does not work anymore in Gutsy
on my Dell Inspiron 9400
https://bugs.launchpad.net/bugs/151444
You received this bug
@Zem
Try running this:
"/usr/share/python-support/kde-guidance-powermanager/powermanage.py"
This will try to adjust the brightness; does this work?
Also try to attach the output of this command:
"for i in `hal-find-by-capability --capability laptop_panel`; do hal-device $i;
done"
--
Fn-Keys fo
@Zem
Run the attached python script in a terminal.
1. Download
2. "chmod +x buttontest.py"
3. "./buttontest.py"
4. Test your brightness buttons, and see what is output in the terminal. Does
the events appear? Does the next line say ".. ok"?
If the events appear, but the next line is not "ok", ple
Check which version of kde-guidance you are using. (This can be doing by
issuing the following command in a terminal "dpkg -l kde-guidance"
without the quotes).
Run the user configuration utility from the terminal. Can be done with
the command "userconfig", again without the quotes. What happens,
It works perfectly now. Thank you.
** Changed in: kipi-plugins (Ubuntu)
Status: Confirmed => Fix Released
--
[hardy] batch resize generates "error"
https://bugs.launchpad.net/bugs/178356
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@pukyxd
Your brightness buttons isn't recognized by HAL. You should file this as a
seperate bug against hal about your particular laptop model.
Preferably also look at helping to get your laptop into upstream HAL:
http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-index.html
--
Fn-Keys
@pukyxd
Check that "dpkg -l kde-guidance-powermanager" shows that you have version
0.8.0svn20080103-0ubuntu8 installed.
If that is the case issue the command:
"for i in `hal-find-by-capability --capability button`; do hal-device $i; done
> button.log"
and attach the generated button.log
--
Fn-
@Mantas
I'm quite sure nothing will happen until we have the python-uniconvertor
package in Ubuntu. I'll doubt a FeatureFreezeException is possible now; but you
are welcome to try: https://wiki.ubuntu.com/FreezeExceptionProcess
I think the recommends and patching is reasonable to include togethe
Uniconvertor has been packed in Debian. I'll look into having it
included for Intrepid.
--
[needs-packaging] UniConvertor: universal vector graphics translator (needed by
Inkscape for Corel Draw formats support)
https://bugs.launchpad.net/bugs/200730
You received this bug notification because yo
@ktulu77
Yes, it seems fine.
You are running kipi-plugins 0.8.0svn20080103-0ubuntu9 now?
With this version: What do you get when running it from the terminal?
--
Modify and New in userconfig don't work due to unicode errors
https://bugs.launchpad.net/bugs/205487
You received this bug notificati
The attached debdiff is a fix for the problem taken from upstream.
** Attachment added: "kipi-plugins_0.1.5~beta1-3ubuntu2.debdiff"
http://launchpadlibrarian.net/12847614/kipi-plugins_0.1.5%7Ebeta1-3ubuntu2.debdiff
--
[hardy] batch resize generates "error"
https://bugs.launchpad.net/bugs/178
@ktulu77
Can I have you:
1. Go to a terminal
2. Start "python"
3. In the python prompt input these two lines: "import locale" and
"locale.getpreferredencoding()"
What is then outputted?
--
Modify and New in userconfig don't work due to unicode errors
https://bugs.launchpad.net/bugs/205487
You r
) => awen (andreas-wenning)
Status: Incomplete => In Progress
--
Modify and New in userconfig don't work due to unicode errors
https://bugs.launchpad.net/bugs/205487
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-guidanc
Which version of the package kde-guidance are you using, where this
problem exists?
You can use "dpkg -l kde-guidance" in a terminal to get the current
version.
--
kde-guidance user management broken
https://bugs.launchpad.net/bugs/112101
You received this bug notification because you are a memb
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: New => In Progress
--
bright control does not work in gateway laptop display
https://bugs.launchpad.net/bugs/43
You received this bug notification because you are a member of Ubunt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
The problem with suspend not working is already fixed in Hardy, kde-
guidance-powermanager 0.8.0svn20080103-0ubuntu7
Does the problem with not returning to the correct CPU behaviour exist
if you suspend using the guidance-powermanager applet? Or does it only
occur if you suspend from eg. the logou
Thanks for taking the time to report this problem. Please attach the
output from running the following command in a terminal:
hal-device `hal-find-by-capability --capability 'processor'`
** Changed in: kde-guidance (Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
(Ubuntu)
Assignee: (unassigned) => awen (andreas-wenning)
Status: New => Incomplete
--
Power Manager(guidance-power-manager.py) crashed
https://bugs.launchpad.net/bugs/188191
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-guida
*** This bug is a duplicate of bug 123812 ***
https://bugs.launchpad.net/bugs/123812
Then your bug is a duplicate of bug 123812 . I'm marking it as such.
** Changed in: kde-guidance (Ubuntu)
Assignee: awen (andreas-wenning) => (unassigned)
** This bug has been marked a duplicat
You mean, that it was lost at some point, while the packages was
updated?
I know that there has been numerous hal updates the last few days; in
that case the battery will disappear, but restarting g-p-m will bring
the battery back. Is that the case?
--
Battery is "not present" in Hardy on hp6720
: kde-guidance (Ubuntu)
Assignee: awen (andreas-wenning) => (unassigned)
** This bug has been marked a duplicate of bug 151444
Fn-Keys for adjusting brightness of the display does not work anymore in
Gutsy on my Dell Inspiron 9400
--
Brightness Special Buttons doesn't work
@Bernhard
Can you attach the fdi-file that made it work with g-p-m? I'll try taking a
closer look at it.
The "negative logic" is actually what makes the sensible defaults; so
I'm quite sure that will not be included (a very large change so late in
development).
--
Resume from standby works with
Not a good idea to revert that patch it seems. Looks like som pretty
sensible defaults.
Try to have a look in the file
"/usr/share/hal/fdi/information/10freedesktop/". There is some 20* files
that describes different laptops/computers; that's where the patch for
your specific computer should be.
I've also added pm-suspend to the above link. Have a backup of your
originale pm-suspend and replace it with this; your machine will not
suspend but the quirks is logged to /root/pm-suspend.log .
--
Resume from standby works with "pm-suspend" but not with standard ubuntu/gnome
actions (with fglr
I've done a build of the current HAL with
88_change_pm_quirk_policy.patch reverted.
You can find it build for i386 in http://awen.dk/packages/ ... how dows
that one act out?
--
Resume from standby works with "pm-suspend" but not with standard ubuntu/gnome
actions (with fglrx-driver from restric
Okay. If it should resurface, please attach a log. I'll leave this bug
open, for now; and close it, if it doen't resurface in the next few
days.
--
Battery is "not present" in Hardy on hp6720s
https://bugs.launchpad.net/bugs/202867
You received this bug notification because you are a member of Ub
Hi Anton.
Thank you very much for your logs.
I can see, that some info is missing to me in the "not-detected" case.
I've attached a new version of the pmtest.py; can I have you generate a
log from one of the times, that the battery isn't detected.
** Attachment added: "pmtest.tar.gz"
http://l
1 - 100 of 340 matches
Mail list logo
