[Closed] Please help beta test calibre 7

[JSWolf]

Originally Posted by kovidgoyal

It hasnt, its just some breakage with some windows computers on an update. Uninstall and re-install calibre 7 and you will be fine.

Not fine. calibre-debug is still broken.

[un_pogaz]

Oh, in this case that normal.
calibre-debug.exe without any arguments lauch a python interpreter (it's always been like that)
To realy lauch calibre in debug mode you need to add the "-g" or "--gui" arguments

calibre-debug.exe --gui

[DNSB]

Originally Posted by JSWolf

Windows 11 here and calibre-debug won't work. I get some sort of calibre interactive shell. Going to the calibre directory doesn't help. I have uninstalled calibre 7 and reinstalled. calibre-debug is still broken.

Attachment 204826

Perhaps running calibre-debug -g would do what you seem to want? BTW, this behaviour has not changed since at least calibre 4.23

D:\Calibre Portable\Calibre>calibre-debug --version
calibre-debug.exe (calibre 4.23)

D:\Calibre Portable\Calibre>calibre-debug
Module readline not available.
Welcome to the interactive calibre shell!
Use exit to quit
>>>

To quote from calibre-debug's --help screen:

Various command line interfaces useful for debugging calibre. With no options,
this command starts an embedded Python interpreter. You can also run the main
calibre GUI, the calibre E-book viewer and the calibre editor in debug mode.

It also contains interfaces to various bits of calibre that do not have
dedicated command line tools, such as font subsetting, the E-book diff tool and so on.

And for the options:

Options:
--version show program's version number and exit

-h, --help show this help message and exit

-c COMMAND, --command=COMMAND
Run Python code.

-e EXEC_FILE, --exec-file=EXEC_FILE
Run the Python code in file.

-f, --subset-font Subset the specified font. Use -- after this option to
pass option to the font subsetting program.

-d, --debug-device-driver
Debug device detection

-g, --gui Run the GUI with debugging enabled. Debug output is
printed to stdout and stderr.

--gui-debug=GUI_DEBUG
Run the GUI with a debug console, logging to the
specified path. For internal use only, use the -g
option to run the GUI in debug mode

--run-without-debug Don't run with the DEBUG flag set

-w, --viewer Run the E-book viewer in debug mode

--paths Output the paths necessary to setup the calibre
environment

--add-simple-plugin=ADD_SIMPLE_PLUGIN
Add a simple plugin (i.e. a plugin that consists of
only a .py file), by specifying the path to the py
file containing the plugin code.

-m, --inspect-mobi Inspect the MOBI file(s) at the specified path(s)

--edit-book Launch the calibre "Edit book" tool in debug mode.

-x, --explode-book Explode the book into the specified folder.
Usage: -x file.epub output_dir
Exports the book as a collection of HTML files and
metadata, which you can edit using standard HTML
editing tools. Works with EPUB, AZW3, HTMLZ and DOCX
files.

-i, --implode-book Implode a previously exploded book.
Usage: -i output_dir file.epub
Imports the book from the files in output_dir which
must have been created by a previous call to
--explode-book. Be sure to specify the same file type
as was used when exploding.

--export-all-calibre-data
Export all calibre data (books/settings/plugins).
Normally, you will be asked for the export folder and
the libraries to export. You can also specify them as
command line arguments to skip the questions. Use
absolute paths for the export folder and libraries.
The special keyword "all" can be used to export all
libraries. Examples:
calibre-debug --export-all-calibre-data # for
interactive use
calibre-debug --export-all-calibre-data
/path/to/empty/export/folder /path/to/library/folder1
/path/to/library2
calibre-debug --export-all-calibre-data
/export/folder all # export all known libraries

--import-calibre-data
Import previously exported calibre data

-s, --shutdown-running-calibre
Cause a running calibre instance, if any, to be
shutdown. Note that if there are running jobs, they
will be silently aborted, so use with care.

--test-build Test binary modules in build

-r RUN_PLUGIN, --run-plugin=RUN_PLUGIN
Run a plugin that provides a command line interface.
For example:
calibre-debug -r "Plugin name" -- file1 --option1
Everything after the -- will be passed to the plugin
as arguments.

-t RUN_TEST, --run-test=RUN_TEST
Run the named test(s). Use the special value "all" to
run all tests. If the test name starts with a period
it is assumed to be a module name. If the test name
starts with @ it is assumed to be a category name.

--diff Run the calibre diff tool. For example:
calibre-debug --diff file1 file2

--default-programs=DEFAULT_PROGRAMS
(Un)register calibre from Windows Default Programs.
--default-programs=(register|unregister)

--fix-multiprocessing
For internal use

[Terisa de morgan]

Originally Posted by kovidgoyal

It hasnt, its just some breakage with some windows computers on an update. Uninstall and re-install calibre 7 and you will be fine.

Easier... I've edited the environment variable..

[BetterRed]

Originally Posted by JSWolf

Not fine. calibre-debug is still broken.

Moderator Notice
Please but out of this thread, your red herring contributions are not needed.

Approximately 80% of calibre installs are on Windows, and less than 5% of users have installed calibre 7, so far only a handful have had issues.

I'm wondering how many of those who've had install issues run a Windows development environment, pretty sure that Terisa de Morgan and un_pogaz do. I don't run a development environment and I've not experienced problems.

BR

[Terisa de morgan]

Originally Posted by BetterRed

I'm wondering how many of those who've had install issues run a Windows development environment, pretty sure that Terisa de Morgan and un_pogaz do. I don't run a development environment and I've not experienced problems.

BR

Not me, I run it only from time to time, but it's not a normal thing. And it has broken in two different computers. I've go to install in a third one and I'll see if there is the same effect.

[BetterRed]

Originally Posted by Terisa de morgan

Not me, I run it only from time to time, but it's not a normal thing. And it has broken in two different computers. I've go to install in a third one and I'll see if there is the same effect.

Bang goes that theory then, what about Windows clean up gadgets… apart from your plugin

BR

[DNSB]

For what it's worth, I've tested a calibre 7 update and a clean install on 5 different Windows 10/Windows 11 machines (3 virtual, 2 physical). None of the updates or installs removed the calibre executables path from the environmental variables.

Nothing like an erratic bug to make troubleshooting fun (for certain values of fun).

[Apache]

I closed Calibre and rebooted my Surface Pro with Win 11. When I opened the Start Menu the pinned shortcut and folder in All Apps were missing. The Desktop Shortcut was also missing. Calibre was still installed, but I had to open the Calibre folder to open the application. I did a repair install and everything was back where it belonged.
Apache

[kovidgoyal]

Basically, if you suffer from this problem. Uninstall calibre and re-install it and you will stop sufferring from it from then on.

[thiago.eec]

Windows 11 here. I had the problem with missing icons too. I thought something went wrong with the auto update*, so I ran it again and everything was back to normal.

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?


*I use a batch script to keep calibre updated

[JSWolf]

Originally Posted by thiago.eec

Windows 11 here. I had the problem with missing icons too. I thought something went wrong with the auto update*, so I ran it again and everything was back to normal.

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?


*I use a batch script to keep calibre updated

Windows 11 here. I am seeing a white rectangle just before the GUI shows up.

[Uncle Robin]

Originally Posted by thiago.eec

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?

Yes,I am. Windows 10 Pro here.

[theducks]

Originally Posted by Uncle Robin

Yes,I am. Windows 10 Pro here.

Me too. I thought I mentioned it during the beta
Since it appears to be cosmetic, no biggie here.

[chaley]

Originally Posted by theducks

Me too. I thought I mentioned it during the beta
Since it appears to be cosmetic, no biggie here.

Not me, with and without the splash screen. Win 10 pro.