Bug 871147

Summary: Ups is not detected
Product: [Fedora] Fedora Reporter: Juan Urroa <observer1>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, neko.shippo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-07 23:11:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
snipet of my lsusb -v none

Description Juan Urroa 2012-10-29 18:12:57 UTC 
Description of problem:
The ups connected to the system is not detected


Version-Release number of selected component (if applicable):
kernel-3.6.2-4.fc17.x86_64
kernel-3.6.3-1.fc17.x86_64


How reproducible:
Always happens


Steps to Reproduce:
1. Turn on the system
  
Actual results:
The ups icon is not in the gnome dock


Expected results:
The ups icon is in the gnome dock


Additional info:
It seems the device connects and disconnects every few seconds, This is a an extract of /var/log/messages:

Oct 28 15:40:59 Maia kernel: [   80.454226] usb 3-2: USB disconnect, device number 9
Oct 28 15:41:00 Maia kernel: [   80.663135] usb 3-2: new low-speed USB device number 10 using uhci_hcd
Oct 28 15:41:00 Maia kernel: [   80.830771] usb 3-2: New USB device found, idVendor=09ae, idProduct=2010
Oct 28 15:41:00 Maia kernel: [   80.830783] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 28 15:41:00 Maia kernel: [   80.830792] usb 3-2: Product: Tripp Lite UPS
Oct 28 15:41:00 Maia kernel: [   80.830799] usb 3-2: Manufacturer: Tripp Lite
Oct 28 15:41:00 Maia kernel: [   81.104980] hid-generic 0003:09AE:2010.0009: hiddev0,hidraw0: USB HID v1.10 Device [Tripp Lite  Tripp Lite UPS] on usb-0000:00:1d.1-2/input0
Oct 28 15:41:00 Maia mtp-probe: checking bus 3, device 10: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Oct 28 15:41:00 Maia mtp-probe: bus: 3, device: 10 was not an MTP device

As I said this occurs every few seconds
Comment 1 Johnathan 2012-11-04 17:31:08 UTC 
I started having a similar issue with the 3.6 series of kernels. My ups is detected fine in 3.5.x, but in 3.6.x its not detected by Gnome. Nut can detect it, but I was happy just using Gnome's basic power functions. Dmesg output when I connect it in the two kernels are pretty much the same.

dmesg when connected in 3.5.x
[  200.802575] usb 4-3: >new low-speed USB device number 4 using ohci_hcd
[  200.960929] usb 4-3: >New USB device found, idVendor=0764, idProduct=0501
[  200.960941] usb 4-3: >New USB device strings: Mfr=3, Product=1, SerialNumber=0
[  200.960948] usb 4-3: >Product:  CP 1350C
[  200.960953] usb 4-3: >Manufacturer: CPS
[  201.029318] hid-generic 0003:0764:0501.0006: >hiddev0,hidraw2: USB HID v1.10 Device [CPS  CP 1350C] on usb-0000:00:12.0-3/input0

dmesg when connected in 3.6.x
[  100.932977] usb 4-3: new low-speed USB device number 4 using ohci_hcd
[  101.090392] usb 4-3: New USB device found, idVendor=0764, idProduct=0501
[  101.090403] usb 4-3: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[  101.090410] usb 4-3: Product:  CP 1350C
[  101.090415] usb 4-3: Manufacturer: CPS
[  101.160753] hid-generic 0003:0764:0501.0006: hiddev0,hidraw2: USB HID v1.10 Device [CPS  CP 1350C] on usb-0000:00:12.0-3/input0
Comment 2 Frank Jacobberger 2012-11-27 22:24:44 UTC 
Created attachment 653166 [details]
snipet of my lsusb -v
Comment 3 Josh Boyer 2013-01-07 22:05:29 UTC 
There was a recent update to upower to fix issues detecting USPs.  If you update upower and reboot, does it appear as you'd expect?
Comment 4 Johnathan 2013-01-07 22:47:49 UTC 
My ups seems to be detected normally again using upower 0.9.19.
Comment 5 Josh Boyer 2013-01-07 23:11:51 UTC 
Great, thanks for letting us know.

*** This bug has been marked as a duplicate of bug 848521 ***