[Bug 460631] Re: Incorrect warning about eeepc battery
Can confirm on an eeepc 701 with 9.10 netbook remix installed. Happy to report any dumps deemed necessary. -- Incorrect warning about eeepc battery https://bugs.launchpad.net/bugs/460631 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 454301] Re: warning given about disk health due to smart not being enabled
Can also confirm this bug on eeepc 701 4GB SSD. Only happens to me after a resume from suspend. If I restart, the message goes away. No noticeable "damage". Files are fine, performance is top notch. -- warning given about disk health due to smart not being enabled https://bugs.launchpad.net/bugs/454301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
I noticed sometime last week that gpm was not correctly setting the original brightness again after resuming from idle. After looking into it I realized that a new version of gpm had shipped with a round of updates. So I went back to Paulo Silva's patched version and everything is back in order. Why was Paulo's patch not included in this new updated gpm version? -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 254816] [NEW] F-spot rotate photo results in corrupted file
Public bug reported: Binary package hint: f-spot I'm using f-spot with Hardy Heron 8.04. I came across a rather concerning bug. If I rotate an image (either left or right) and do some other action before the rotation has finished, it results in a corrupted file. After the attempted rotate If I try to open the image in GIMP it says that the file ends prematurely. The image will load, but only the pixels through where the rotation had completed now exist. This is not a constant phenomenon, however. Usually the rotate feature happens very quickly. But in some circumstances (i.e with a very large photo and/or heavy system load) the rotation takes longer than expected and if you try to do something else (namely rotate another image) it ends the first rotation prematurely, effectively rotating only half of the image and corrupting the rest. As long as you let the second rotation finish, the second image is fine. F-spot should either not allow another action until the rotation is completed, or should triage the commands it receives more effectively. Finishing a current process before starting another. ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- F-spot rotate photo results in corrupted file https://bugs.launchpad.net/bugs/254816 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
Paulo, I'm sorry. It happened only one day--though consistently that day--and I have not been able to reproduce this bug since. Everything seems to be working fine. Thanks! BandD On Tue, Jul 1, 2008 at 3:51 AM, Paulo J. S. Silva <[EMAIL PROTECTED]> wrote: > Hi BandD, > > The problem after the screen saver resume does not happen to me. Can you > send me a log file that shows this happening? > > Paulo > Em Dom, 2008-06-29 às 14:09 +, BandD escreveu: > > Paulo, > > > > I may have found another 'bug'. I've noticed that when when the > > screensaver (for me blank screen) is activated using your patched > > version of gpm and deactivate the screensaver (through mouse movement or > > keystroke), my screen brightness is stuck at the 'dimmed' screen > > brightness and I have to manually adjust the screen brightness back to > > 100% with the brightness applet. After that dim on and off works fine. > > It is just when resuming from the screensaver. > > > > Also, sometimes when resuming from suspend I get the same behavior, but > > not always. > > > -- > Paulo José da Silva e Silva > Professor Associado, Dep. de Ciência da Computação > (Associate Professor, Computer Science Dept.) > Universidade de São Paulo - Brazil > > e-mail: [EMAIL PROTECTED] Web: > http://www.ime.usp.br/~pjssilva<http://www.ime.usp.br/%7Epjssilva> > > Teoria é o que não entendemos o (Theory is something we don't) > suficiente para chamar de prática. (understand well enough to call > practice) > > -- > g-p-m does not honor its configuration for LCD brightness levels after > multiple unplug-replug from AC > https://bugs.launchpad.net/bugs/215484 > You received this bug notification because you are a direct subscriber > of the bug. > -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
Paulo, I may have found another 'bug'. I've noticed that when when the screensaver (for me blank screen) is activated using your patched version of gpm and deactivate the screensaver (through mouse movement or keystroke), my screen brightness is stuck at the 'dimmed' screen brightness and I have to manually adjust the screen brightness back to 100% with the brightness applet. After that dim on and off works fine. It is just when resuming from the screensaver. Also, sometimes when resuming from suspend I get the same behavior, but not always. -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199522] Re: Dim on idle does not brighten with activity
This issue had been resolved for me using a patched version of gpm found at the end of the following bug report for those interested: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/215484 -- Dim on idle does not brighten with activity https://bugs.launchpad.net/bugs/199522 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
Ok. The new patch works perfectly for me when setting the idle/active brightness! Nice work there! I'm still having problems with the battery/ac though. But it I don't know that it is a problem with YOUR patch--perhaps gpm in general or ACPI. I had this problem with the Ubuntu's version of gpm in Hardy (though not in Gutsy). The problem is that when I unplug the power supply the brightness doesn't change, i.e. it doesn't dim at all. The icon in the system tray changes, though when I put my mouse over it is says: Computer is running on AC power. Laptop battery 1 hour 35 minutes remaining (78%) When the power supply is plugged in it says: Computer is running on AC power. Laptop batter charging (78%) So, although it says that it is on AC power in both cases, the second line tells you which is which, when on battery it give the estimated time remaining. When on AC it says the battery is charging. So it's just the first line that gets confused. This problem is probably not exactly related to this particular bug. But I wanted to give you the full account of what I'm experiencing on my machine. The bottom line is that your patch seems to fix this particular bug. When my screen dims brightness is restored to 100% again. Before this was not the case. So good work! I've also attached a log file that details the dimming/un-dimming cycles and several AC/Battery switches in case you are curious. ** Attachment added: "gpm-log" http://launchpadlibrarian.net/15518072/gpm-log -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
The patch doesn't seem to work on my system, sadly. I get no response when unplugging and plugging in the power cord; the screen brightness doesn't change at all. The screen will dim when idle, but will not restore ANY brightness once the mouse is moved or a key is pressed. I can manually restore brightness, but gpm doesn't react to automatically restore brightness in any way. If you need any logs or other information, let me know. I'd be happy to help out in whatever way I can. Your idea seems to be going to right direction. -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 215484] Re: g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC
I tried to download the package, but I got an error when I tried to open it with Gdebi saying that the package may be corrupted or not being allowed to open the file. It's not a permissions problem (I even tried gksu gdebi-gtk). I'd be happy to test out the script, the logic of it seems to make sense. But I'm not sure about how to apply the patch. Can you give some instructions on how to do so? -- g-p-m does not honor its configuration for LCD brightness levels after multiple unplug-replug from AC https://bugs.launchpad.net/bugs/215484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199522] Re: Dim on idle does not brighten with activity
I have the same issue as pelle.k: "Same here. Everytime it goes back up from "dim", it decreases until it hits some magic bottom. I've got a brightness range of 0-8. I adjust it to 7. then, let me illustrate; idle > 7 dim > 4 idle > 6 dim > 4 idle > 5 dim > 4 idle > 5 dim > 4 idle > 5" I ran a debug script and basically, when it is, boiled down it's the same issue (full version attached for anyone interested). After each dim, the resulting default restore brightness is diminished one level. I can change the brightness to value "7" again (100%) via the brightness applet, but something in gpm is causing the 'restore' brightness level to decrease by "1" level each dim/undim cycle. ** Attachment added: "gnome-power-management log" http://launchpadlibrarian.net/14651115/gpm.debug.log.txt -- Dim on idle does not brighten with activity https://bugs.launchpad.net/bugs/199522 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 180087] Re: Processes tab causes GLib error
Maybe that it the problem then. I pulled this icon out of an icon set I got from gnome-look.org as is with the .svg tag. But after looking at the file in detail, it is indeed a .png. So perhaps the problem is when a file labeled as .svg is actually a .png. Trying to open the .svg one in image viewer doesn't work. But if I rename it to firefox.png it works fine. So perhaps a mislabled icon is to blame. -- Processes tab causes GLib error https://bugs.launchpad.net/bugs/180087 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 180087] Re: Processes tab causes GLib error
Well I was able to fix the problem AND keep my icon set, though the average user isn't going to want to go through the hassle of this VERY ugly fix. It seems that the system monitor doesn't like to use .svg images as icons; rather it likes .png images. So to resolve this issue I had to 'hide' my firefox icon originally found in /home/.icons/custom_set/scalable/apps/firefox.svg in a new folder I created within that same director (named whatever you choose, I choose "firefox". Then I tracked down where the default firefox icons were kept, which was in /usr/lib/firefox-3.0b5/icons/. I think the really important one here is mozicon128.png as /usr/share/pixmaps/firefox-3.0 is linked to mozicon128.png. So I opened up Gimp and saved my original firefox.svg icon as a 128px x 128px .png (and as a 16x16 and 48x48, just to be safe as files of these sizes also exist in /usr/lib/firefox-3.0b5/icons/) named mozicon128.png (and mozicon16.png and mozicon50.png) to a convenient folder. Then I replaced the files in /usr/lib/firefox-3.0b5/icons/ with my newly created files--you need root privileges for this. The last thing I had to do was change the path for my firefox panel launcher. For this I choose my original .svg icon in it's newly created folder in /home/.icons.../firefox/. So now firefox and the system monitor work together in harmony. But it took me an hour of looking for the various icons and testing different situations out. If someone follows my instructions here, then they will probably be ready to go in 15-20 minutes, maybe less. But it is an awful lot of work and if other icons cause similar issues then the whole process will start over again. So with that said, the System Monitor should be programmed to find more suitable icons if it doesn't like the one that is set as the user's preference. If it comes across a .svg then if should skip it and move on to the next directory until it finds a suitable .png file instead--as the panel, nautilus, and all other programs do. A .svg icon should not keep the system monitor from running. So I agree with Frank. I've attached the icon causing the issue. The original path was /home/.icons/CURRENT ICON SET/scalable/apps/firefox.png ** Attachment added: "firefox.svg" http://launchpadlibrarian.net/14248577/firefox.svg -- Processes tab causes GLib error https://bugs.launchpad.net/bugs/180087 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 180087] Re: Processes tab causes GLib error
I have this same exact problem with an Icon set I made by combining icons from Crashbit and NouveXT2.2. I had this same icon set working fine under Gutsy. I too think this is a bug in the gnome-system-monitor. No other programs crash because of icon discrepancies. The program should be worked to ignore or inherit different icons when it encounters something different than it expects. It's going to be very difficult to find the faulty icon, and we shouldn't have to use 'standard' icons just to get the system-monitor to work. If all else fails, maybe the system monitor should just force use the icons from /usr/share/icons/gnome rather than using the user's defined icon set. At least then the program would work. -- Processes tab causes GLib error https://bugs.launchpad.net/bugs/180087 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
