[Solved]Calibre No longer working

I'm not sure when it started but I just tried loading Calibre and it crashes at startup.
This is what I recieve when running it from a terminal:
[keystone@Archos CyberBasics]$ calibre
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in <module>
sys.exit(calibre())
File "/usr/lib/calibre/calibre/gui_launch.py", line 48, in calibre
main(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 449, in main
app, opts, args = init_qt(args)
File "/usr/lib/calibre/calibre/gui2/main.py", line 100, in init_qt
app = Application(args, override_program_name=override)
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 915, in __init__
self.load_calibre_style()
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 1026, in load_calibre_style
self.pi.load_style(icon_map)
TypeError: a value has type 'unicode' but 'QString' is expected
Since i'm not sure when this issue started, how would you suggest I start troubleshooting it? In my mind it seems like it has something to do with QT being updated after reviewing some bug reports: link
but I'm not exactly sure how to check that, and if it is QT, Downgrading that could have implications on many of the other programs I have running qt... any suggestions?
Last edited by cyberpsych0sis (2014-12-17 00:37:36)

Scimmia wrote:You're out of date. Updating your system should get you calibre 2.12.0-2, which I'm guessing will fix this.
...That's odd... But yeah, it did... weird I'd just updated a couple days prior to posting that question. That's a rolling release for ya I guess.

Similar Messages

[SOLVED] Postgis no longer working after upgrade of postgresql

Dear all,
after yesterdays upgrade of postgresql-server and libs to 9.0.1 the postgis package does no longer work. When trying to import postgis.sql (version 1.5) it always complains about wrong libraries version:
psql:/usr/share/postgresql/contrib/postgis-1.5/postgis.sql:59: FEHLER: inkompatible Bibliothek »/usr/lib/postgresql/postgis-1.5.so«: Version stimmt nicht überein
I have double checked on postgresql and postgis documents that the versions should be compatible:
postgresql 9.0.1-2
postgresql-libs 9.0.1-2
postgis 1.5.1-1
For all databases dump and restore was fine, except for my gis databases. So upgrade from 8.4.4 to 9.0.1 worked in general.
Any ideas?
Last edited by Wauzenplauz (2010-10-31 14:46:20)

"Unfortunately" I did not have enough time to give it a try and rebuild the package.
So today I found that there is already a new version of postgis available which works perfectly fine!

Monitor calibration no longer works -- eye-one display 2

I have been reasonably successfully calibrating monitors for my Mac Pro desktop (Apple monitor) and Macbook Pro laptop for close to 3 years, with an X-rite eye-one display 2 system. I'm using Mac OS 10.6.6 on both computers.
Over the last several days, calibrating on both monitors has yielded widely inaccurate profiles, although I'm calibrating the monitors in the same way I always have. On the MacPro/Apple Cinema, the calibration seems to be proceeding fine, when I've finished the process, "before-after" looks good (i.e., slight change for the better with the new calibration); but when I click "finish calibration" and exit the software, the monitor profile is completely out of whack. On a given image, about half the colors are now out of gamut (where none were before). Similar symptoms on my laptop. I tried downloading the latest software from X-rite on my desktop, and it didn't seem to help. (On the other hand, when I calibrated my Apple monitor using the "Easy" option in the software, it actually worked almost acceptably, except for the luminance.)
The only way I can even use either computer is to go to system preferences and switch to the monitor to the most recent profile I was using before these troubles began. (The laptop is actually unusable without going back to an earlier profile, because the drop-down texts at the top of the display are completely blacked out.)
Since this sort of behavior is happening with two different computers and monitors, and I've downloaded the latest software from X-rite (and reinstalled the software from the original installation disk), I'm assuming that the problem is with the puck (hardware).
I realize it may be hard to provide advice, given my difficulty in describing exactly what's happening. But I'm interested in anyone's advice or thoughts. -- E.g, how to get through to X-Rite for help, altho from other forums, I've gotten the impression they won't be much help; is there any forum specifically devoted to eye-one display 2 (especially if this is the wrong forum). Is there an expected life for the pucks (mine is about 3 years old)? Do they sometimes fail in this way?
Thanks.

It was an extremely frustrating process trying to know if indeed this was the way to calibrate this monitor, and after spending so much time and research was all I could come up with. Did you notice the graphing results of both types of calibration? The red (I believe it was) of the RBG graph line was not lined up at all with the G and B thus the weird color on the monitor, and with the Easy mode, they were at least in line, more or less.

[SOLVED]EasyStroke no longer works after upgrading Xorg....

Hi,
First i would just like to take the time to say, that ArchLinux kicks butt! I just joined the forum, but have been using Arch for about a month. Thus far, i have had very few problems....until tonight
I keep my system really up-to-date (almost everyday i update). Tonight, there was an update for Xorg (1.10? i think).
Anyway, One of the applications that i use is Easystroke - which after the upgrade has stopped working, i even recompiled it (which went fine) but still it doesnt work.
a more detailed explanation;
1. the app starts up fine, and appears to be working.
2. i draw a gesture on the screen, and i can see easystroke drawing them.
3. at this point the usually, i would stop drawing and easystroke would execute my gesture. but now instead, it doesn't properly release the gesture key (second button on my Wacom Bamboo stylus).
4. Easystroke has a "history page" that allows you to see how accurate your gestures are, now it shows absolutely nothing.
I have searched around with google, and no luck. I tried to get a more verbose output from easystroke, but it doesn't tell me anything. So, now i am kind of stuck
After the upgrade (and a reboot), i tested the system to see if there were other problems. So far, i have found zero.
I've tested my tablet, all of my main applications; Maya2011, Mypaint, gimp, Compiz++, Jackd, wine, etc. Everything is fine. I have also went through the log viewer, and nothing caught my eye that would hint to what has gone wrong....
if anyone else is having the same problem, or has a possible solution, please let me know.
I can deal with not using it for now, but not having Easystroke running, seriously hinders my workflow and navigation
on my Arch Desktop.... and now i am wondering whether or not easystroke even runs with the latest X???
jordan
Last edited by triplesquarednine (2011-05-05 06:43:00)

ewaller wrote:
Hello,
Welcome to the forums. Your post is fine in every way. Introduction, problem description, what you have done -- perfect. The package you reference is from the AUR which, as you know, is not in the main stream Arch distribution. These community contributions are essential Arch, but have their own area in the forum to differentiate them.
Moving this thread to AUR issues...
As it turns out. This isn't a bug in AUR/easystroke. It is a bug in the latest xserver 1.10.902 (found in the "extra" repo) Many applications are affected. Opera, chrome (if you are using the mouse gestures features for navigation) and it turns out that while i thought Maya wasn't affected, in reality, it is totally affected. most applications that use a mouse with right-clicks, middle clicks do not work properly.
it's an upstream bug, that affects all distributions using the latest Xorg. I am not filing a bug report, because as i understand it, this bug has already been reported upstream by Ubuntu-devs (on launchpad).
that latest update for Xserver, should have been tested better, before being an update available through pacman.
On my system, i do not use any testing repos, only core, extra, and community. I do this to avoid situations, just like this. lol.
I have work i need to get done today, but unfortunately, the only way that could happen is if i downgrade xserver (which i don't think is a smart idea). So, i guess i must wait for the next xserver update for arch. hopefully this happens in the next 24hours.
I suppose i will have to use OSX for now, until this is properly addressed and fixed.
anyway, i just wanted to point out that this bug has nothing to do (specifically) with Easystroke or AUR, that is just how i first noticed the bug. ( i just wanted to point that out, as you are a moderator ). This bug is in the main repos for Arch, and anyone updating today (or yesterday) will be affected, if they use applications where it's noticable.
jordan

[SOLVED]Sounds no longer works after kernel update (Audigy 4)

Updated kernel along with other updates. I have an audigy 4 (detected as audigy 2, always been that way).
It's detected if I do lspci, if I go in alsaconf it also detects it and says it should work, but if I then go in alsamixer it just comes up with my USB webcam sound mixer.
What am I doing wrong? I can't get any sound anymore and I don't even know how to start fixing it.
I also checked lsmod and the module was loaded (emu10k1), it should work, but it doesn't.
Any ideas?
Edit: Trying to launch MPD:
speng@spengpc ~ $ mpd
output: No "audio_output" defined in config file
output: Attempt to detect audio output device
output: Attempting to detect a alsa audio device
ALSA lib pcm_dmix.c:1008:(snd_pcm_dmix_open) unable to open slave
alsa: Error opening default ALSA device: No such file or directory
output: Attempting to detect a oss audio device
oss: Error opening OSS device "/dev/dsp": Invalid argument
oss: Error opening OSS device "/dev/sound/dsp": No such file or directory
output: Unable to detect an audio device
Aborted
Last edited by speng (2009-08-21 02:10:39)

Speng, perhaps there are two sound devices on your system?.. What are the contents of /dev/snd/?
Efish, your issue is different, you've got a different card, right? And I don't get what the issue is, exactly. /etc/modprobe.d/*sound.conf?

[solved] Password no longer works at tty, but does work elsewhere

Hi,
The other day I could no longer log in to a tty; "Login incorrect", but other users are fine. You're probably thinking I forgot my password, but I can confirm it is correct as I can log in as "user2", "su - jsteel", enter the password and it accepts it! After doing that I can run passwd (it asks for my current password) and it accepts it there too. I have not proceeded to change my password (which may well fix the issue) as I am interested to investigate what the problem is exactly.
Does anyone have any idea what could be wrong?
Thanks
Last edited by jsteel (2013-06-18 22:08:28)

/etc/shells showed /usr/bin/zsh whereas my $SHELL was set to /bin/zsh. Updating my shell to /usr/bin/zsh fixed the issue! I guess it didn't like the symlink, I wonder why.

[solved] checkgmail no longer working

Hi, since a few days checkgmail is not working anymore. It gives a ERROR 200 OK. Any ideas? (I'm using checkgmail from community, have also tried the AUR svn package with no success).
Last edited by rogorido (2013-01-19 15:50:43)

# patching file checkgmail
Reversed (or previously applied) patch detected! Assume -R? [n]
Why is this error appearing?
-R or --reverse
Assume that this patch was created with the old and new files swapped. (Yes, I'm afraid that does happen occasionally, human
nature being what it is.) patch attempts to swap each hunk around before applying it. Rejects come out in the swapped format.
The -R option does not work with ed diff scripts because there is too little information to reconstruct the reverse operation.
If the first hunk of a patch fails, patch reverses the hunk to see if it can be applied that way. If it can, you are asked if you
want to have the -R option set. If it can't, the patch continues to be applied normally. (Note: this method cannot detect a
reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends
always succeed, due to the fact that a null context matches anywhere. Luckily, most patches add or change lines rather than
delete them, so most reversed normal diffs begin with a delete, which fails, triggering the heuristic.)
Assume that this patch was created with the old and new files swapped.
By this I'm assuming the -R switch thinks that it's dealing with a newer version of the executable in which the patch had already been applied versus a version of the executable in which the patch hadn't been applied?
(Yes, I'm afraid that does happen occasionally, human
nature being what it is.) patch attempts to swap each hunk around before applying it. Rejects come out in the swapped format.
I'm not really understanding what's being described here.
The -R option does not work with ed diff scripts because there is too little information to reconstruct the reverse operation.
OK
If the first hunk of a patch fails, patch reverses the hunk to see if it can be applied that way. If it can, you are asked if you
want to have the -R option set.
So I should assume this is exactly what happened and that's why I was prompted if I wanted to apply the -R switch? If so, since it reversed the first hunk and was applied successfully, should I assume that I have a version of the executable in which the patch was already applied?
If it can't, the patch continues to be applied normally. (Note: this method cannot detect a
reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends
always succeed, due to the fact that a null context matches anywhere. Luckily, most patches add or change lines rather than
delete them, so most reversed normal diffs begin with a delete, which fails, triggering the heuristic.)
I don't understand this part, but don't think it really applies to this particular issue.

[SOLVED] Hibernation no longer working

When booting, one of the first things to come up is,
ERROR: resume: no device specified for hibernation
Then it recovers the journal and continues booting.
If I recall correctly I had to add the resume hook when using mkinitcpio. Hibernate was working fine ever since I configured everything, but recently it has been not resuming correctly.
Is there a log to find the information displayed during booting, so I can paste it here?
Any ideas of how to fix this?
Thanks,
Kopkins
Last edited by Kopkins (2012-07-21 13:31:38)

Yes, your boot log should be located in
/var/logs/boot
If not you may find the destination by searching with find
find / -name="boot"
I would check but on my works Win7 comp. Inside /var/logs/ there will also be other logs that might be relevant, for sure there is a suspend log maybe a hibernation one.

[Solved] Pacman no longer works at all!!

Ok, did some searches and found a few hits, but not really sure how to fix this one. Here are 2 links I found.
links:
http://unix.stackexchange.com/questions … -libraries
https://bbs.archlinux.org/viewtopic.php?pid=1232052
In my case, I dont think any pacman option/command works. Cant run 'pacman' with ANY options or with no options??
error:
$ pacman
pacman: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory
I guess I was updating something using curl libraries, but not sure whats the best way to fix this.
ldconfig -p | grep curl
Returns nothing.
Not sure if this was the right thing to do but I also tried this from the first link.
echo /usr/local/lib | sudo tee -a /etc/ld.so.conf.d/local.conf
Here is another one:
$ sudo ldd $(which pacman)
linux-vdso.so.1 (0x00007fff4a3ff000)
libalpm.so.7 => /usr/lib/libalpm.so.7 (0x00007f16be091000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f16bdce4000)
libcurl.so.4 => not found
libgpgme.so.11 => /usr/lib/libgpgme.so.11 (0x00007f16bdab1000)
libarchive.so.12 => /usr/lib/libarchive.so.12 (0x00007f16bd81c000)
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007f16bd412000)
/lib/ld-linux-x86-64.so.2 (0x00007f16be2bd000)
libassuan.so.0 => /usr/lib/libassuan.so.0 (0x00007f16bd202000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f16bcfff000)
libacl.so.1 => /usr/lib/libacl.so.1 (0x00007f16bcdf6000)
libattr.so.1 => /usr/lib/libattr.so.1 (0x00007f16bcbf1000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f16bc9c7000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f16bc7a4000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f16bc594000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f16bc37e000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f16bc17a000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f16bbf5e000)
So looks like thats the issue .. libcurl.so.4 => not found ...
I dont have strace installed and not sure if I need it to continue....I did a quick search and dont see a libcurl installed, so either i need to install it or remove that reference too it? LOL
Any suggestions?
Last edited by banshee28 (2013-02-19 03:28:09)

Army wrote:Show us what you did with pacman which caused this = show us your /var/log/pacman.log. Do you use testing repos?
Never use testing repos.
I dont see anything for libcurl in that log, but I did see this recently for curl. Perhaps this is the culprit. Pacman -Sc ??
[2013-02-07 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-08 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-08 17:19] Running 'pacman -Sy'
[2013-02-08 17:19] synchronizing package lists
[2013-02-08 17:19] starting full system upgrade
[2013-02-08 17:19] Running 'pacman -S -u'
[2013-02-08 17:19] starting full system upgrade
[2013-02-08 17:21] upgraded perl (5.16.2-2 -> 5.16.2-3)
[2013-02-08 17:21] upgraded openssl (1.0.1.c-1 -> 1.0.1.d-1)
***** [2013-02-08 17:21] upgraded curl (7.28.1-1 -> 7.29.0-1) *******
Full log file:
[2012-09-22 09:01] installed filesystem (2012.8-1)
[2013-02-11 20:12] ------------------------------------------------------------------------
[2013-02-11 20:12] upgraded profile-sync-daemon (5.13-1 -> 5.16-1)
[2013-02-12 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-12 18:19] Running 'pacman -Sy'
[2013-02-12 18:19] synchronizing package lists
[2013-02-12 18:19] starting full system upgrade
[2013-02-12 18:19] Running 'pacman -S -u'
[2013-02-12 18:19] starting full system upgrade
[2013-02-12 18:20] upgraded device-mapper (2.02.98-1 -> 2.02.98-3)
[2013-02-12 18:20] upgraded cryptsetup (1.5.1-1 -> 1.6.0-1)
Last edited by banshee28 (2013-02-19 03:29:37)

[SOLVED]qps no longer works after kernel upgrade

I'm not sure if this is right place for this. The error is rather self explanatory.
; qps
Qps: can't determine version, read 3.0-ARCH
please report this bug.
Last edited by whitethorn (2011-08-11 20:13:30)

sounds like qps has not been adapted yet for the switch to linux 3 kernel .
please report this bug
Report it to upstream ?

[SOLVED] Sound no longer working

I'm using alsa in gnome3 and wheen I look at the sound tab in gnome3's settings nothing looks awry.
Thanks in advance,
xrendan
Last edited by xrendan (2011-08-08 05:28:24)

nevermind I just made a stupid mistake i accidentally set my sound to input only instead of input/output but thanks anyway

[SOLVED] Default audio device no longer works after reboot

After today's reboot, the audio device no longer works. E.g., VLC says:
Audio output failed:
The audio device "default" could not be used:
No such file or directory.
This is the console log:
[0x1394138] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
[0x7fac180069c8] pulse audio output error: PulseAudio server connection failure: Connection refused
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
[0x7fac180069c8] alsa audio output error: cannot open ALSA device "default": No such file or directory
[0x7fac180069c8] jack audio output error: failed to connect to JACK server
[0x7fac180069c8] oss audio output error: cannot open audio device (/dev/dsp)
[0x7fac180069c8] main audio output error: no suitable audio output module
[0x7fac40fa4db8] main decoder error: failed to create audio output
[0x7fac180069c8] pulse audio output error: PulseAudio server connection failure: Connection refused
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
[0x7fac180069c8] alsa audio output error: cannot open ALSA device "default": No such file or directory
[0x7fac180069c8] jack audio output error: failed to connect to JACK server
[0x7fac180069c8] oss audio output error: cannot open audio device (/dev/dsp)
[0x7fac180069c8] main audio output error: no suitable audio output module
[0x7fac41055118] main decoder error: failed to create audio output
The strange thing is that the sound card does in fact work; e.g. the sound test for "HDA Intel PCH", the first entry in my KDE Audio Settings, works. But the entry "default" does not and I suppose that is also the device that VLC is complaining about.
I've tried blacklisting the HDMI driver and switched to the other audio output modules in VLC. I've also checked I'm still member of the "audio" group.
Edit:
P.S. Solved this myself. I had a USB-to-MIDI adapter cable plugged in during boot, which seems to have been causing these problems. I suppose systemd thought it was a USB sound card? I was wondering why dmesg said something about USB sound when the computer doesn't have any USB sound devices. Hardware detection epic fail. Although I guess the cable counts as a MIDI device at least, so in a way it's correct.
So it looks like I'll always have to unplug the MIDI cable before rebooting.
Last edited by Morn (2012-11-23 19:24:00)

You might get. Ore assistance in a different forum area. Maybe try Using pad. This is the forum for iPhoto for iOS.

Devilspie no longer working? [solved]

Did configuration change again? Because my xmms script is no longer working for devilspie(then again no scipts are working). Heres my xmms script:
1 (if (is (application_name) "XMMS")
2 (begin
3 (skip_pager)
4 (skip_tasklist)
5 (below)
6 (pin)
7 )
8 )
This simple script used to work, I supposed I did notice this once I switched to pypanel, but I believe the script worked the first couple of times, it's supposed to hide xmms from the pager / tasklist but it isn't doing so.

Global Havok wrote:Still working fine for me... I don't believe there has been a devilspie update recently either. Any major changes in your setup lately?
Other than switching from fbpane to pypanel, no. Altleaste not that I know of
edit
Apparently it's just a pypanel related problem. Guess I'll have to change panels once again ;(
edit
Well, I guess pypanel has it's own option to hide windows fromt he tastklist, so I just did that instead. Problem solved.

Lightroom: Why does auto white balance no longer work after changing the camera calibration profile?

I'm using NEF raw files from Nikon.
Lets say for example I import a NEF file into Lightroom (v4) and click on 'auto' for white balance. The white balance in the image is adjusted correctly (somewhat). However, if I then change the camera profile (in the camera calibration section) from 'adobe standard' to 'camera standard' then the white balance in the image becomes very wrong. I then have to set the white balance back to 'as shot' and correct it manually instead.
Why would 'auto white balance' no longer work just because I change the profile from 'adobe standard' to 'camera standard'?
Any ideas?

Works as expected here...
Which Lr version and what OS??

I have ios 5.1.1. When I sync to iTunes, my purchased apps no longer work. They blink but do not open. The only way I have been able to solve this, is as follows: I delete one of the apps and then re-download and install it. Then, all my apps work.

My new iPod touch 64 Gig has a problem after syncing with iTunes. My purchased apps no longer work. I touch them and they seem to try to open but they do not.
The only way I have found to fix this is as follows:
I delete one of the purchased apps. Then I go to the App Store and re-download and install the same app. After that, all my apps work again.
Please help.

Download/install an app is a know possible solution.
3. Install another app from the App Store
If all user-installed apps are not launching, it could be an Apple ID authorization issue. Download and install an app that isn't already installed on your device to reset this information.
Note: If you have installed apps using multiple Apple ID accounts, you may need to perform this step for each account.
Above from Apple's :
iOS: Troubleshooting applications purchased from the App Store

[Solved]Calibre No longer working

Similar Messages

Maybe you are looking for