Problem with SD card

tempest@de · 06-23-2013, 07:45 AM

Since the beginning I have all my ebooks in the SD card, yesterday I tried to add some more with calibre and I couldn’t.

I disconnected the device and the glo didn’t show any off my books, I ejected the sd card and put it back again with no results. I connected the sd card in to my pc and all the books are there, so I think the problem is not in the SD card.
I formatted the sd card and put it back in the glo, connected calibre and the sd card doesn’t show in calibre.
Since I need to have something to reed I tried to send some books to the main memory of the glo and I couldn’t, calibre shows an error

Code:

Error: Error communicating with device

character mapping must return integer, None or unicode

Traceback (most recent call last):
  File "site-packages\calibre\gui2\device.py", line 85, in run
  File "site-packages\calibre\gui2\device.py", line 557, in _upload_books
  File "calibre_plugins.kobotouch_extended.driver", line 220, in upload_books
  File "calibre_plugins.kobotouch_extended.driver", line 131, in _modify_epub
  File "calibre_plugins.kobotouch_extended.container", line 70, in __init__
  File "zipfile.py", line 1036, in extractall
  File "zipfile.py", line 1024, in extract
  File "zipfile.py", line 1057, in _extract_member
TypeError: character mapping must return integer, None or unicode

I have firmware 2.6.1 (06/06/2013) and calibre version 0.9.36, which was updated yesterday, the same day the problems started.

Any ideas about what could be and what can I do in order to fix this. I'm seeing myself

again in paper, something I haven't done in more that 5 years.

Thank's in advance.

tempest@de · 06-23-2013, 02:11 PM

Problem solved, it seems that the problem was in the latest version off calibre. I uninstalled it and installed the one I had before 0.9.29, connected the glo and it was detected.
I would like to know if this happened to someone else or if it is just me and my bad luck.

PeterT · 06-23-2013, 02:18 PM

Have you opened a bug report with the author of the Extended driver? See his instructions in the first post @ [Device Plugin] Kobo Touch Extended which asks you

Quote:

Submitting Bugs
Found an issue? Have a new feature request? Great, I want to hear from you! Go to the GitHub issue tracker and submit a new bug report. To save us all time, please make sure to include the following details:

What version of calibre are you running? If this is not the latest version, you will likely be asked to upgrade and confirm that the bug still exists.
What version of the plugin are you using? If this is not the latest version, you will likely be asked to upgrade and confirm that the bug still exists.
What Kobo device you're using and what firmware version
- To get the Kobo firmware version, from the Settings page choose Device Information and look for the line beginning with Software Version about two-thirds of the way down the page.
For issues processing books, whether or not you are able to send me a book that demonstrates the problem. Please be aware of your local copyright laws and any legal restrictions which may prevent sending me a book!
The calibre debug log showing the issue, where applicable
- To get the calibre debug log, select Preferences -> Restart in debug mode and reproduce the issue. The calibre debug log will be displayed shortly after closing calibre.

davidfor · 06-23-2013, 10:06 PM

As Peter said, that error comes from the extended driver. It probably means the epub you were transferring has an error in its structure, or at least an unusual structure that the driver doesn't handle yet. Reporting the error to author is needed.

The other issues are with the base calibre and included Kobo driver. The SD card should be visible. Can the OS see the card? If not, then calibre will not see it. The OS also needs to be able to write to the card or calibre won't be able to either.

tempest@de · 06-24-2013, 06:07 PM

I will open a bug report, thanks.

When I conected the card directly on the pc it apeared listed and could delete files, when I conected in the glo it didn't show.

davidfor · 06-24-2013, 11:41 PM

A bug report is good. Can you do a debug log? PeterT's post above includes the instructions.

tempest@de · 06-25-2013, 06:12 PM

I did the bug report, this is what it showed

Quote:

calibre Debug log
calibre 0.9.29 isfrozen: True is64bit: False
Windows-XP-5.1.2600-SP2 Windows ('32bit', 'WindowsPE')
('Windows', 'XP', '5.1.2600')
Python 2.7.3
Windows: ('XP', '5.1.2600', 'SP2', 'Uniprocessor Free')
Starting up...
Started up in 198.53 seconds with 292 books

remember that I made a downgrade for calibre so I no longer have the same version off calibre that created the problem, not sure if that makes diference.

davidfor · 06-25-2013, 08:49 PM

Sorry, I missed something. The instructions above were just for starting in debug mode. I should have added to connect the device and wait for the jobs to finish. That will show a lot more info about what happens, including if the SD card is seen at all.

tempest@de · 06-30-2013, 11:42 AM

After opening a bug report in github Joel told me what the problem was, turns out I didn’t had the plugin up to date

I was convinced I had but I must have seen it wrong in calibre

.
Now that I have the plugin and calibre with the newest versions it is all working.
I really have to pay better attention, so I don’t waste time and more important make others waste time trying to help me, sorry about that.

Ken Maltby · 06-30-2013, 08:01 PM

Quote:

Originally Posted by tempest@de

After opening a bug report in github Joel told me what the problem was, turns out I didn’t had the plugin up to date

I was convinced I had but I must have seen it wrong in calibre

.
Now that I have the plugin and calibre with the newest versions it is all working.
I really have to pay better attention, so I don’t waste time and more important make others waste time trying to help me, sorry about that.

It's an important factor that you came back and let everyone know the situation. All too often posters succumb to the temptation to just say, "nevermind" it's fixed and slink away, leaving us all in the dark.

Luck;
Ken

tempest@de · 07-01-2013, 04:54 PM

@ Ken Maltby

I undestad that it is frustrating when you have a problem and are looking to see if someone has had that same problem and how they fixed it and you find the problem solved but no mention of the solution. Besides it makes sense to let the people that tried to help know the problem is fixed so I always try to give feedback about the situation.

Regards,

AlPe · 07-31-2013, 11:05 AM

Apologies for "reopening" this, but it seems to be a problem with zipfile lib in Python 2.7.4.

Indeed, on my Windows box, running latest Calibre 0.9.41, 32bit, I get:

Code:

character mapping must return integer, None or unicode

Traceback (most recent call last):
  ...
  File "zipfile.py", line 1036, in extractall
  File "zipfile.py", line 1024, in extract
  File "zipfile.py", line 1057, in _extract_member
TypeError: character mapping must return integer, None or unicode

when I call zipfile.extractall() in my code.

In debug mode, Calibre says it is running with Python 2.7.4 (in Windows). I guess this behavior is related to this bug: http://bugs.python.org/issue17656

That's why reverting to a previous version of Calibre, running with Python 2.7.3, seems to fix the issue.

On my Debian machine, running Calibre 0.9.31 with Python 2.7.5+, no exception is raised as well.

I am not familiar with Calibre building, is there a way of "forcing" Calibre to use Python 2.7.5 (installed on system) instead of Python 2.7.4? Or are the libs statically "built-in" the Windows package? Also, "updating" Calibre to Python 2.7.5 should solve the issue altogether.

PeterT · 07-31-2013, 02:12 PM

Quote:

Originally Posted by AlPe

Apologies for "reopening" this, but it seems to be a problem with zipfile lib in Python 2.7.4.

Indeed, on my Windows box, running latest Calibre 0.9.41, 32bit, I get:

Code:

character mapping must return integer, None or unicode

Traceback (most recent call last):
  ...
  File "zipfile.py", line 1036, in extractall
  File "zipfile.py", line 1024, in extract
  File "zipfile.py", line 1057, in _extract_member
TypeError: character mapping must return integer, None or unicode

when I call zipfile.extractall() in my code.

In debug mode, Calibre says it is running with Python 2.7.4 (in Windows). I guess this behavior is related to this bug: http://bugs.python.org/issue17656

That's why reverting to a previous version of Calibre, running with Python 2.7.3, seems to fix the issue.

On my Debian machine, running Calibre 0.9.31 with Python 2.7.5+, no exception is raised as well.

I am not familiar with Calibre building, is there a way of "forcing" Calibre to use Python 2.7.5 (installed on system) instead of Python 2.7.4? Or are the libs statically "built-in" the Windows package? Also, "updating" Calibre to Python 2.7.5 should solve the issue altogether.

I think you'd be better opening a bug report with calibre itself describing the issue; calibre is self contained and uses it's own python build.

davidfor · 07-31-2013, 11:57 PM

Quote:

Originally Posted by AlPe

Apologies for "reopening" this, but it seems to be a problem with zipfile lib in Python 2.7.4.

Indeed, on my Windows box, running latest Calibre 0.9.41, 32bit, I get:

Code:

character mapping must return integer, None or unicode

Traceback (most recent call last):
  ...
  File "zipfile.py", line 1036, in extractall
  File "zipfile.py", line 1024, in extract
  File "zipfile.py", line 1057, in _extract_member
TypeError: character mapping must return integer, None or unicode

when I call zipfile.extractall() in my code.

In debug mode, Calibre says it is running with Python 2.7.4 (in Windows). I guess this behavior is related to this bug: http://bugs.python.org/issue17656

That's why reverting to a previous version of Calibre, running with Python 2.7.3, seems to fix the issue.

On my Debian machine, running Calibre 0.9.31 with Python 2.7.5+, no exception is raised as well.

I am not familiar with Calibre building, is there a way of "forcing" Calibre to use Python 2.7.5 (installed on system) instead of Python 2.7.4? Or are the libs statically "built-in" the Windows package? Also, "updating" Calibre to Python 2.7.5 should solve the issue altogether.

I can't help but wonder what you are up to

If you are running any of the Kobo related plugins, they should just work with calibre. That makes me wonder if your writing something extra and what. Something good?

AlPe · 08-01-2013, 12:32 PM

Quote:

Originally Posted by PeterT

I think you'd be better opening a bug report with calibre itself describing the issue; calibre is self contained and uses it's own python build.

Yeah, eventually I asked in Calibre Development subforum: https://www.mobileread.com/forums/sho...d.php?t=219150

It is not really a Calibre "bug", and I understand that Kovid strongly dislike std zipfile lib. Going with his calibre.utils.zipfile worked for me.

I posted the previous message in this thread because I was googling around to solve a problem with a plugin of mine (not related to Kobo) and I read none mentioned this problem with zipfile, referring it to buggy zipfile in Python 2.7.4, as it seems to me to be the "correct" root of the problem.

06-23-2013, 07:45 AM	#1
tempest@de Fanatic Posts: 525 Karma: 4503161 Join Date: May 2009 Location: Portugal Device: Kobo Glo, kindle	Problem with SD card Since the beginning I have all my ebooks in the SD card, yesterday I tried to add some more with calibre and I couldn’t. I disconnected the device and the glo didn’t show any off my books, I ejected the sd card and put it back again with no results. I connected the sd card in to my pc and all the books are there, so I think the problem is not in the SD card. I formatted the sd card and put it back in the glo, connected calibre and the sd card doesn’t show in calibre. Since I need to have something to reed I tried to send some books to the main memory of the glo and I couldn’t, calibre shows an error Code: Error: Error communicating with device character mapping must return integer, None or unicode Traceback (most recent call last): File "site-packages\calibre\gui2\device.py", line 85, in run File "site-packages\calibre\gui2\device.py", line 557, in _upload_books File "calibre_plugins.kobotouch_extended.driver", line 220, in upload_books File "calibre_plugins.kobotouch_extended.driver", line 131, in _modify_epub File "calibre_plugins.kobotouch_extended.container", line 70, in __init__ File "zipfile.py", line 1036, in extractall File "zipfile.py", line 1024, in extract File "zipfile.py", line 1057, in _extract_member TypeError: character mapping must return integer, None or unicode I have firmware 2.6.1 (06/06/2013) and calibre version 0.9.36, which was updated yesterday, the same day the problems started. Any ideas about what could be and what can I do in order to fix this. I'm seeing myself again in paper, something I haven't done in more that 5 years. Thank's in advance.

07-31-2013, 11:05 AM	#12
AlPe Digital Amanuensis Posts: 727 Karma: 1446357 Join Date: Dec 2011 Location: Turin, Italy Device: Several eReaders and tablets	Apologies for "reopening" this, but it seems to be a problem with zipfile lib in Python 2.7.4. Indeed, on my Windows box, running latest Calibre 0.9.41, 32bit, I get: Code: character mapping must return integer, None or unicode Traceback (most recent call last): ... File "zipfile.py", line 1036, in extractall File "zipfile.py", line 1024, in extract File "zipfile.py", line 1057, in _extract_member TypeError: character mapping must return integer, None or unicode when I call zipfile.extractall() in my code. In debug mode, Calibre says it is running with Python 2.7.4 (in Windows). I guess this behavior is related to this bug: http://bugs.python.org/issue17656 That's why reverting to a previous version of Calibre, running with Python 2.7.3, seems to fix the issue. On my Debian machine, running Calibre 0.9.31 with Python 2.7.5+, no exception is raised as well. I am not familiar with Calibre building, is there a way of "forcing" Calibre to use Python 2.7.5 (installed on system) instead of Python 2.7.4? Or are the libs statically "built-in" the Windows package? Also, "updating" Calibre to Python 2.7.5 should solve the issue altogether.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Touch SD card problem thread	Benjamin Buford	Kobo Reader	25	12-09-2011 02:30 PM
help, SD card problem	witch_moon	Bookeen	4	02-23-2009 06:44 AM
Problem with SD card	Tibor	Calibre	10	01-15-2009 02:23 AM
SD card reader problem	promo	Bookeen	25	11-06-2008 03:26 PM
Visa card problem	ali	iRex	9	06-29-2006 12:57 PM

06-23-2013, 02:11 PM	#2
tempest@de Fanatic Posts: 525 Karma: 4503161 Join Date: May 2009 Location: Portugal Device: Kobo Glo, kindle	Problem solved, it seems that the problem was in the latest version off calibre. I uninstalled it and installed the one I had before 0.9.29, connected the glo and it was detected. I would like to know if this happened to someone else or if it is just me and my bad luck.

06-23-2013, 10:06 PM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	As Peter said, that error comes from the extended driver. It probably means the epub you were transferring has an error in its structure, or at least an unusual structure that the driver doesn't handle yet. Reporting the error to author is needed. The other issues are with the base calibre and included Kobo driver. The SD card should be visible. Can the OS see the card? If not, then calibre will not see it. The OS also needs to be able to write to the card or calibre won't be able to either.

06-24-2013, 06:07 PM	#5
tempest@de Fanatic Posts: 525 Karma: 4503161 Join Date: May 2009 Location: Portugal Device: Kobo Glo, kindle	I will open a bug report, thanks. When I conected the card directly on the pc it apeared listed and could delete files, when I conected in the glo it didn't show.

06-24-2013, 11:41 PM	#6
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	A bug report is good. Can you do a debug log? PeterT's post above includes the instructions.

06-25-2013, 08:49 PM	#8
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Sorry, I missed something. The instructions above were just for starting in debug mode. I should have added to connect the device and wait for the jobs to finish. That will show a lot more info about what happens, including if the SD card is seen at all.

06-30-2013, 11:42 AM	#9
tempest@de Fanatic Posts: 525 Karma: 4503161 Join Date: May 2009 Location: Portugal Device: Kobo Glo, kindle	After opening a bug report in github Joel told me what the problem was, turns out I didn’t had the plugin up to date I was convinced I had but I must have seen it wrong in calibre . Now that I have the plugin and calibre with the newest versions it is all working. I really have to pay better attention, so I don’t waste time and more important make others waste time trying to help me, sorry about that.

07-01-2013, 04:54 PM	#11
tempest@de Fanatic Posts: 525 Karma: 4503161 Join Date: May 2009 Location: Portugal Device: Kobo Glo, kindle	@ Ken Maltby I undestad that it is frustrating when you have a problem and are looking to see if someone has had that same problem and how they fixed it and you find the problem solved but no mention of the solution. Besides it makes sense to let the people that tried to help know the problem is fixed so I always try to give feedback about the situation. Regards,