Since one of the updates earlier (april, may?) this year, simple-scan is not working correctly anymore: scanning is hectic - sometimes does the job sometimes not - and the theme is so black that the buttons are not readable.
I have read that something was linked with gtk version but I do not know what to do.
Sorry for this late report but I did wait for a correction of this problem with the updates and had no time to risk a computer failure before the northern summer.
Hi @Guirec,
I assume you have cleared your cache in pursuit of an answer? If not, try that first:
rm -fr ~/.cache/*
If that still doesn’t do anything, please provide the output of:
ls -lah ~/.gconf/apps/simple-scan/
Hi Midarthos, thanks for your reaction!
I have done it now, with no effect. Is that a part of a normal cleaning process after update?
This files does not exist, I do find some content in ls -lah ~/.sane/xsane :
batch-lists Brother:_Brother.drc xsane.mdf xsane.rc
I have had some difficulties to install brother printer/scanner originally and may have solved this in an unusual manner.
Not necessarily. But it is a good idea with GUI-type changes, as I understand it.
That is supposed to bee the configuration directory for simple-scan. Let’s see if it is perhaps elsewhere:
find ~ -iname '*scan*' -and -iname '*simp*'
And seeing as there seemed to be configuration(s)/files listed in ~/.sane/xsane, I have to ask, does it work with (X)sane?
As I am on Xfce, I did a test with my scanner : no problem.
You could look into ~/.config/simple-scan/ (and delete content in ~/.cache/simple-scan/ : already done).
Once you start simple-scan, there is a log in ~/.cache/simple-scan/, you could look at it.
1 Like
Found some things in .config and .cache
Output of 'cat ~/.config/simple-scan/state'
[window]
width=1920
height=1080
is-maximized=false
is-fullscreen=false
[scanner]
scan-type=single
There is a log in ~/.cache/simple-scan/simple-scan.log (annex)
Well, @Denis_Pom tested:
And it seems to work. And you mentioned:
However, you only provided the contents of:
So I’d sat completely remove the previous, now obviously incorrect Output of 'cat ~/.config/simple-scan/state:
rm -rf ~/.config/simple-scan
This will force you to have to reconfigure everything.
I’m no expert, but maybe removing that will solve the CRITICAL error in the log as well.
Tip
In the future, when posting terminal output, instead of screenshots, please rather copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
Thanks to you both and sorry for the incorrect quoting sometimes.
I did remove the log and ~/.config/simple-scan and relaunched…
The new CRITICAL log lines are:
[+0,04s] CRITICAL: g_application_set_application_id: assertion 'application_id == NULL || g_application_id_is_valid (application_id)' failed
[+0,04s] CRITICAL: g_variant_new_string: assertion 'string != NULL' failed
[+0,31s] WARNING: scanner.vala:1739: Unknown ScanType: . Please report this error.
[+13,27s] CRITICAL: g_variant_new_string: assertion 'string != NULL' failed
[+122,55s] CRITICAL: g_variant_new_string: assertion 'string != NULL' failed
[+381,12s] CRITICAL: app_window_set_scanning: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_get_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_append_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: app_window_set_selected_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_get_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_append_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: app_window_set_selected_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_get_n_pages: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_get_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: page_get_has_data: assertion 'self != NULL' failed
[+381,12s] CRITICAL: book_delete_page: assertion 'self != NULL' failed
[+381,12s] CRITICAL: app_window_set_scanning: assertion 'self != NULL' failed
Functionning of the scanner is still hectic, after launching the scan takes a long time to generate the image (one or two minutes, never or even sometimes normal and fast…) and the “menu block” (save, quit) is readable until the mouse hovers over it.
Final thought
I did fail to mention that I am using a xfce DARK theme and I did read something about GTK and actualization… This might explain the aspect problem but not the scanning one???
I’m all out of ideas, sorry man!
I use adwaita-dark theme but simple-scan still uses a clear one 
You have a Brother scanner and probably are using a “driver” from AUR. You may need to rebuild it as it may be out of phase with simple-scan and / or sane.
Well, I did try to reinstall il all upgrading from brscan4 to brscan5, with no effect.
I also have gtk2 3 and 4 installed altogether.
I think you are right, simple-scan was clear independently of the dark theme I had chosen. I have the impression that there is some element for the solution there.
Changing to clear is not a solution, the situation is still hectic
I did find now an older thread… simple-scan is not using chosen gtk theme / Applications & Desktop Environments / Arch Linux Forums
I will have a look…
Update, this is correct to have the theme fixed but not the scanner
1 Like
Thanks for the link for the dark theme ! I now have simple-scan using it, but the recipe does not apply to pamac, I probably should use pamac-gtk. But that’s another problem. [Edit : solved by replacing the command for pamac icon in Whisker with : env GTK_THEME=Adwaita:dark pamac-manager %U (no Exec= here)]
For your scanner did you install some AUR stuff ? What does give :
pacman -Qm
Just to rule out that the issue is simple-scan; have you tried a different scanning software?
I am on xfce, Unstable and use gscan2pdf with no issues on a spare HP Printer that has scan capability. gscan2pdf also uses the dark theme that I have set, Matcha-dark-sea.
I’m not sure the word “upgrading” is appropriate here - the two packages are supporting different scanner models, as far as I could see
“upgrading” from 4 to 5 would perhaps even remove the proper driver and leave you with none or a wrong, only partially working one
Thank you all for your ideas. I had a problem with the belgian ID reader also and did leave the scanner’s problem
@jrichard326 : Good option indeed, I am now on gscan2pdf, working fine. XSane did the work but I was not convinced by the GUI and simple-scan was too unpredictable.
@Denis_Pom I think that AUR is necessary, I have at least .
brother-dcp1610w 3.0.1-1
brscan-skey 0.3.2_0-1
brscan4 0.4.11_1-2
@Nachlese It did work but was indeed not adequate; I did come back to brscan4
All this is apparently solved, thanks!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.