[Desktop-packages] [Bug 467654] Re: Wrong yellowish colors printing with Epson Stylus Photo R220
I don't have the printer anymore... marking as invalid. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/467654 Title: Wrong yellowish colors printing with Epson Stylus Photo R220 Status in “cups” package in Ubuntu: Invalid Bug description: Binary package hint: cups I am using Ubuntu 9.10 updated as of today from beta 6. With Ubuntu 9.04 I had no problems at all using my Epson Stylus Photo R220. Now I am unable to have a decent print from Ubuntu. I tried printing a black and white file made with inkscape, but it became black and yellow. Tried saving it as a pdf and printing with evince: same problem. Tried doing a png and printing with GIMP: same yellow print. Today I saved an Inkscape page (with colors) as pdf and tried printing with acroread (from Canonical partners' repository): the green becames yellow with stripes, a blue gradient goes from yellow to pink and violet, and a blue square becames dark grey. I tried printing the ubuntu test page and the automatic test page, and they both come out perfectly. I am at your disposal for any other information you may need to find out the problem. I don't want to reboot every now and open windows just to print a page! ProblemType: Bug Architecture: amd64 Date: Sun Nov 1 00:34:34 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Stylus-Photo-R220: usb://EPSON/Stylus%20Photo%20R220 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cups 1.4.1-5ubuntu2 Papersize: a4 PpdFiles: Stylus-Photo-R220: Epson Stylus Photo R220 - CUPS+Gutenprint v5.2.4 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=f181aa04-927a-4c25-8859-38d95eb55d8b ro quiet splash ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: cups Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 02/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: 4Core1333-FullHD dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd02/19/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-FullHD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/467654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
@Alberto: I did a few tests, and it looks like my accounts are going completely crazy. Maybe it's my home folder's fault, with files dating back to the old dapper drake :D However, the login request appears with at least one between evolution contacts, evolution gmail, evolution calendar, empathy, shotwell enabled. If I enable one of them, the request appears immediately. Obviuosly I always gave access before logging out. The login request is in the form illustrated by the attached screenshot: a new window appears, and usually I have to enter my credentials in the main window; every now and then the main window appears black, and the form is in the secondary window. I use the two-step authentication from google, and the first time I added the account it opened a google page in the main window and I had to enter the token from the google auth app. ** Attachment added: "Funny login screen" https://bugs.launchpad.net/account-plugins/+bug/1029289/+attachment/3779398/+files/Bug%20google%20account%20-%20screen1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
Here is the output of account-console show ** Attachment added: "account-console show" https://bugs.launchpad.net/account-plugins/+bug/1029289/+attachment/3779237/+files/account-console%20show -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
I am attaching the syslog from my saucy system: the bug is still here. However, I encounter it at every login, even if not rebooting. Follows the account-console show. ** Attachment added: "syslog" https://bugs.launchpad.net/account-plugins/+bug/1029289/+attachment/3779236/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch
usb-modeswitch-data 20130610-1 has been pulled automatically from debian repositories, but depends from usb-modeswitch >= 1.2.6, while we still have 1.2.3. So, we have to pull the last version of usb-modeswitch or change the dependency to >= 1.2.3... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1182814 Title: [saucy] usb-modeswitch-data bad packaging forces removal of usb- modeswitch Status in “usb-modeswitch-data” package in Ubuntu: Confirmed Bug description: Ubuntu saucy has usb-modeswitch-data-20120815-1. Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is impossible because of bad packaging which forces removal of usb-modeswitch!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch-data/+bug/1182814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167128] Re: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Still here, from raring to saucy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1167128 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: Confirmed Bug description: I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CrashCounter: 1 Date: Tue Apr 9 12:08:05 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2013-02-02 (66 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SegvAnalysis: Segfault happened at: 0xb71ce912 :mov (%edi),%edx PC (0xb71ce912) ok source "(%edi)" (0x0001) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1167128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%
Retried also the $ sudo killall upowerd; sudo /usr/lib/upower/upowerd -v 2>&1 | tee /tmp/upowerd.log as it did not list any keyboard. ** Attachment added: "$ sudo killall upowerd; sudo /usr/lib/upower/upowerd -v 2>&1 | tee /tmp/upowerd.log (again)" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1103064/+attachment/3776224/+files/upowerd.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Confirmed Status in “indicator-power” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Incomplete Status in “indicator-power” source package in Raring: Invalid Status in “upower” source package in Raring: Won't Fix Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%
Sorry for the double posting: tried another $ upower --dump > /tmp/upower.txt as the first one did not list any keyboard. Looks like the other keyboard listed is my old one, K520, turned off and hidden months ago in its box, but still living in the loving memory of its usb receiver :) ** Attachment added: "$ upower --dump > /tmp/upower.txt (again)" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1103064/+attachment/3776222/+files/upower.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Confirmed Status in “indicator-power” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Incomplete Status in “indicator-power” source package in Raring: Invalid Status in “upower” source package in Raring: Won't Fix Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%
** Attachment added: "sudo killall upowerd; sudo /usr/lib/upower/upowerd -v 2>&1 | tee /tmp/upowerd.log" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1103064/+attachment/3776220/+files/upowerd.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Confirmed Status in “indicator-power” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Incomplete Status in “indicator-power” source package in Raring: Invalid Status in “upower” source package in Raring: Won't Fix Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%
I am using a Logitech K800 wireless keyboard and a M310 wireless mouse, and I found this bug waiting for me after the upgrade to saucy. I did not have any battery indicator from my desktop pc with raring and with precise. I attach, as pitti asked, my upower.txt ($ upower --dump > /tmp/upower.txt ) and upowerd.log ($ sudo killall upowerd; sudo /usr/lib/upower/upowerd -v 2>&1 | tee /tmp/upowerd.log) created using my saucy x64 system. I obviously am at your disposal for any other log you'd need :) ** Attachment added: "$ upower --dump > /tmp/upower.txt" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1103064/+attachment/3776219/+files/upower.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Confirmed Status in “indicator-power” package in Ubuntu: Invalid Status in “upower” package in Ubuntu: Incomplete Status in “indicator-power” source package in Raring: Invalid Status in “upower” source package in Raring: Won't Fix Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
