You are not logged in.
Hi folks,
a few days ago, my calibre stopped recognizing my Amazon Kindle 2. This happend after an update, maybe the reason is, that calibre stopped using one particular "bug", as posted in the changelog: http://gpo.zugaina.org/app-text/calibre/ChangeLog.
I tried a few thinks, I even downgraded calibre to 0.8.24, but it still refused to work. I looked at the logs but I must admit, that I'm stuck and clueless what to do.
Here's the calibre debug output:
Version: 0.8.24
USB devices on system:
[['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.2'],
['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.0'],
['0x17ef', '0x4807', '0x3134', 'Chicony Electronics Co., Ltd.', '', ''],
['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.2'],
['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.0'],
['0x1d6b',
'0x2',
'0x301',
'Linux 3.1.5-1-ARCH ehci_hcd',
'EHCI Host Controller',
'0000:00:1d.7'],
['0x9da', '0xe', '0x1', 'A4Tech', 'PS/2+USB Mouse', ''],
['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1a.1'],
['0x1949', '0x4', '0x100', 'Amazon', 'Amazon Kindle', 'B008A0A011250CVC'],
['0x1d6b',
'0x1',
'0x301',
'Linux 3.1.5-1-ARCH uhci_hcd',
'UHCI Host Controller',
'0000:00:1d.1'],
['0x1d6b',
'0x2',
'0x301',
'Linux 3.1.5-1-ARCH ehci_hcd',
'EHCI Host Controller',
'0000:00:1a.7']]
Available plugins: ADAM ALEX ALURATEK_COLOR ANDROID ARCHOS7O AVANT AZBOOKA BAMBOOK
BLACKBERRY BOEYE_BDX BOEYE_BEX BOOQ BOOX COBY COOL_ER CYBOOK DBOOK E52
E71X EB511 EB600 EBK52 ECLICTO EDGE EEEREADER ELONEX ESLICK EX124G
FOLDER_DEVICE_FOR_CONFIG GEMEI GER2 HANLINV3 HANLINV5 ILIAD INVESBOOK
IPAPYRUS IREXDR1000 IREXDR800 IRIVER_STORY ITALICA JETBOOK
JETBOOK_MINI KINDLE KINDLE2 KINDLE_DX KOBO LIBREAIR LUMIREAD MENTOR
MOOVYBOOK N516 N770 N810 NEWSMY NEXTBOOK NOOK NOOK_COLOR NUUT2 ORIZON
PALMPRE PDNOVEL PDNOVEL_KOBO PICO POCKETBOOK301 POCKETBOOK360
POCKETBOOK360P POCKETBOOK602 POCKETBOOK701 PRS505 PRST1 README S60
SHINEBOOK SNE SOVOS SPECTRA STASH SUNSTECH_EB700 SWEEX TECLAST_K3
THEBOOK TREKSTOR USER_DEFINED VELOCITYMICRO WEBOS WEXLER
Looking for devices...
(6473, 4, 256, 'Amazon', 'Amazon Kindle', 'B008A0A011250CVC')
Detected possible device KINDLE2
Devices possibly connected: Kindle 2/3 Device Interface,
Trying to open Kindle 2/3 Device Interface ... failed
Opening of the following devices failed
<calibre.devices.kindle.driver.KINDLE2 object at 0x4166cd0>
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/devices/__init__.py", line 124, in debug
dev.open(None)
File "/usr/lib/calibre/calibre/devices/usbms/device.py", line 864, in open
self.open_linux()
File "/usr/lib/calibre/calibre/devices/usbms/device.py", line 650, in open_linux
_('Unable to mount main memory (Error code: %d)')%ret)
DeviceError: Unable to mount main memory (Error code: 1)So the good news is, my kindle is still found, so the problem might be related to mouting this thing. I start my openbox-session with ck-launch-session dbus-launch, so there should be no problem with that.
Any suggestions would be appreciated...
Greetings, and best regards.
Last edited by scriptkitty (2011-12-23 16:32:06)
Offline
I had the same problem, but instead of openbox and a kindle 2, I use awesome and a kindle (3) keyboard.
Do you use a login manager? Because I use SLiM and that was the problem. To solve it a changed the login_cmd line in /etc/slim.conf to:
login_cmd exec ck-launch-session /bin/bash -login ~/.xinitrc %sessionAnd (this is important) in my .xinitrc file, I removed the ck-launch-session part:
exec dbus-launch awesomeHope this helps!
Offline
Hi,
your hint did not work for me, although it pointed me in the right direction. On my system it does not matter, where (slim.conf or .xinitrc) the ck-launch-session statement is put.
Here are the things I did to get it working again:
-Launch DBus ![]()
-In
/usr/share/polkit-1/actions/org.freedesktop.udisks.policyat "Mount a device", change
<allow_any>no</allow_any> to "yes"
-Profit
Another bonus feature I got from this: Mounting devices via pcmanfm now works again, too. I know this may not be the appropriate or nice way to deal with this problem, but it works and, at least in my single-user setup, it suffices.
Offline