Description of problem: after scanning a document, if I try to save it with accented characters in its filename, or if I try to create a folder that contains accented characters in its name, I get an error box saying "invalid filename". Version-Release number of selected component (if applicable): 3.6.0-3.mga3 (but also happens with simple-scan 3.9.90-1.mga4 in cauldron) How reproducible: everytime Steps to Reproduce: 1. scan a document 2. try to save it as "document numérisé.jpg" 3. You'll get an error box "invalid filename" Reproducible: Steps to Reproduce:
what are the output if you run simple-scan in a teminal with "-d" as parameter ?
Here it is, from startup to quit, and between both, one scan with my webcam and attempt to save it as "document nuùmérisé.jpg"
CC: (none) => denis.prost
Created attachment 4336 [details] simple-scan -d output
Attachment 4336 mime type: application/octet-stream => text/plain
no more ideas
Keywords: (none) => TriagedAssignee: bugsquad => mageia
Can you try with 3.9.91 from cauldron please?
sorry, I cannot succeed testing it : when I tried to install simple-scan from cauldron, it claimed for a libcolord2 dependency, so I installed it also from cauldron and then could install simple-scan. But now, when I try to run simple-scan, I get an error : -------- simple-scan: /lib/libudev.so.1: version `LIBUDEV_196' not found (required by /lib/libcolordprivate.so.2) -------- and trying to install libudev1 from cauldron fails : --------- [root@localhost Téléchargements]# rpm -ivh libudev1-206-8.mga4.i586.rpm Preparing... ################################# [100%] file /usr/lib/libudev.so.1 from install of libudev1-206-8.mga4.i586 conflicts with file from package libudev1-195-22.mga3.i586 ------------
I can reproduce for now with 3.6.0 and 3.9.91. Let me investigate more... :-)
I meant, I can't reproduce... Oops.
Status: NEW => ASSIGNED
That's strange. Is there anything I could do that could help debug it ?
I still can't reproduce. Can you give me more information on your Mageia installation if bug still available please?
Sure, what kind of information do you need ?
- If it's still available on your computer. - If your are using KDE or GNOME. - If your système is in French or English or other. - If you have only one locale installed on your computer or more. - If you can make a screenshot of the popup about bad filename. Thanks!
Created attachment 4664 [details] simple-scan error dialog box simple-scan error dialog box when trying to save "document numérisé".jpg
thank you Damien for taking care of that bug. 1) Yes, it is still available 2) I'm using XFCE with KDM login manager 3) My system is in french 4) I don't know how to check installed locales, I tried this : ---------- [denis@localhost ~]$ localectl System Locale: LANG=fr_FR.UTF-8 VC Keymap: n/a X11 Layout: n/a ---------- And localedrake shows that the chosen language is french. I guess there is a finer way to check locales, but I don't know how 5) attached above is the screenshot Regards, Denis
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Resolution: (none) => OLDStatus: ASSIGNED => RESOLVED
The Problem still exists with mageia 5 beta 3
Status: RESOLVED => REOPENEDResolution: OLD => (none)Version: 3 => Cauldron
CC: (none) => sylvainsjc
Hello, The message comes from GtkFileChooser, not from SimpleScan. Thus I suppose that other application could be affected.
CC: (none) => yves.brungard_mageia
(In reply to papoteur from comment #17) > Hello, > The message comes from GtkFileChooser, not from SimpleScan. > Thus I suppose that other application could be affected. reassigning to bugsquad, because simple-scan no longer has a maintainer. also removing "Triaged" because of the above remark. Before we try to find out what is going on: did anybody recently hit this bug in Mageia 5 and/or cauldron?
Assignee: mageia => bugsquadCC: (none) => marja11Keywords: Triaged => NEEDINFO
Yes, I just hit this bug, although I used to use it without problems by now.
I have reported the problem upstream. https://bugs.launchpad.net/simple-scan/+bug/1546523
Assignee: bugsquad => geiger.david68210Hardware: i586 => All
Indication from upstream report: The warning message comes from GTK+, not simple-scan. But I have other GTK application in which I can use "é" in file names. Version : simple-scan-3.14.0-3.mga5 On Mageia 5. lib64gtk+2.0_0-2.24.26 The log file contains only the final file name. The warning box has no title and says exactly : "Nom de fichier non valide" or when launched with LANGUAGE=C prefix: "Invalid file name" The message comes from gtk/gtkfilechooserdefault.c line 1037 https://git.gnome.org/browse/gtk+/tree/gtk/gtkfilechooserdefault.c?h=gtk-2-24#n1037
CC: (none) => hugo.pereira
Hello, I have found a workaround. I had a file ~/.config/gtkfilechooser.ini with this content: [Filechooser Settings] LocationMode=path-bar ShowHidden=true ShowSizeColumn=true GeometryX=2394 GeometryY=170 GeometryWidth=972 GeometryHeight=720 SortColumn=name SortOrder=ascending StartupMode=recent I don't know when or from where it came, and which setting induce the bad behaviour. But by deleting it, the filechooser dialog box works fine now. \o/
CC: (none) => dglent
Does this issue still happens on current Mageia 7?
I'm sorry, I can't tell, I don't have a Mageia 7 install. Regards, Denis
Present in Mageia 7, i have modified manually the translation of 'Scanned Documment.pdf' output to workaround this issue [Greek local]
a patch was added by dtux in Cauldron who should fix this issue, so I added the same for mga7. Please test the upcoming simple-scan-3.32.2.1-2.1.mga7 in Core/Updates_testing repo!
Here on my mga7 for x86_64 I can confirm that now accented characters works now! It properly display "Nom: Document numérisé.pdf"
Hello, Installed simple-scan-3.32.2.1-2.1.mga7 Launched simple-scan Got a scan. Clicked to save. Suggested name is "Document numérisé.pdf". Saved in ~/Documents No error, however nothing is stored :/
And if I select jpeg format, then I get "Invalid file name" for "Document numérisé.jpg"
Added a bug report by Gnome https://gitlab.gnome.org/GNOME/simple-scan/issues/147
Could the GTK2 vs GTK3 problem with the file chooser be due to a wrong dependency when building the RPM? This bug is really painful.
CC: (none) => LpSolitStatus: REOPENED => NEWKeywords: NEEDINFO => (none)
Tried again today with simple-scan-3.32.2.1-2.mga7.x86_64.rpm No more problem, even with saving in JPEG format. Installing simple-scan-3.32.2.1-2.1.mga7 from testing. No problem with accented characters, but JPEG file is not saved. I think we can close this bug without the release in testing.
Came across this bug by chance. Tried it. simple-scan-3.32.2.1-2.mga7 (current latest public) This really hates (refuses) accented characters in output filenames. (In reply to David GEIGER from comment #26) > Please test the upcoming simple-scan-3.32.2.1-2.1.mga7 in > Core/Updates_testing repo! Would love to, but cannot see it there. Could I try with a urpmi --media parameter?
CC: (none) => lewyssmith
Just found and tried this pending update: simple-scan-3.32.2.1-2.1.mga7 (In reply to papoteur from comment #32) > Installing simple-scan-3.32.2.1-2.1.mga7 from testing. > No problem with accented characters, but JPEG file is not saved. > I think we can close this bug without the release in testing. NO! On my system, Welsh/English with AZERTY kb, I tried saving a scan as: - PDF - jpg - png In all cases, certainly, all accented characters in the output filename were accepted; but in *no* case was the file ever actually saved. So the update resolves the bug problem, but introduces a worse one. --------- I found the same problem in a different (alas, forgotten) application; so agree with the surmise about the GTK file picker being the culprit. And trying for comparison Image-Scan for Linux, that simply ignores any typed accented character in the output filename. Neat!
Hi, I think there is something wrong there in my Mageia 8a1 install. Bug seems to be in the filechooser dialog. In facts, in Linux Mint Cinnamon 20 and KDE Neon (Plasma 5.19.2 as MGA8a1), simple-scan can save accented files. In Ubuntu (18.04 and 20.04), you can also save files with accented characters. Why not here? Workaround: Name file with non accented characters and rename in File-manager later. Very time consuming.
CC: (none) => ouaurelien
See bug 26903 for an explanation and fix for the file saving bug introduced in simple-scan-3.32.2.1-2.1.mga7
CC: (none) => mageiaSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=26903
Sorry, in mga7 with updates installed and simple-scan-3.32.2.1-2.mga7 I have NO bug. In mga8 Cauldron today, I have bug with simple-scan-3.37.2-1.mga8. Seeing simple-scan --debug command in console I see this in beginning of output: In mga7: [aurelien@mageia7 ~]$ simple-scan --debug [+0,00s] DEBUG: simple-scan.vala:638: Starting Simple Scan 3.32.2.1, PID=15599 [+0,03s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ [+0,05s] DEBUG: app-window.vala:1651: Loading state from /home/aurelien/.cache/simple-scan/state [+0,05s] DEBUG: app-window.vala:1630: Restoring window to 683x400 pixels In mga8: [aurelien@mageia8 ~]$ simple-scan --debug [+0,00s] DEBUG: simple-scan.vala:2007: Starting simple-scan 3.37.2, PID=48228 [+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created [+0,01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ [+0,26s] DEBUG: _g_io_module_get_default: Found default implementation keyfile (GKeyfileSettingsBackend) for ‘gsettings-backend’ [+0,28s] DEBUG: app-window.vala:1987: Loading state from /home/aurelien/.cache/simple-scan/state [+0,28s] DEBUG: app-window.vala:1966: Restoring window to 651x566 pixels It seems simple-scan in mg8 loads GLocalVfs that in mga7 it does not load. Bug here?
Also, I managed to see my current LinuxMint 20 Cinnamon installation. $ simple-scan --debug is like mga7: aurelien@linuxmint:~$ simple-scan --debug [+0,00s] DEBUG: simple-scan.vala:638: Starting simple-scan 3.36.0, PID=2354 [+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created [+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ [+0,03s] DEBUG: app-window.vala:1908: Loading state from /home/aurelien/.cache/simple-scan/state [+0,03s] DEBUG: app-window.vala:1887: Restoring window to 642x400 pixels It not load "g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’" Bug here?
Hi there, I managed to install a fresh install of Mageia 8 Cauldron via Classic ISO and in GNOME Desktop. Updated it. Install task-scanning via "Configure scanner" in MCC. When I run: $ simple-scan --debug I see: [aurelien@mageia8-gnome ~]$ simple-scan --debug [+0,00s] DEBUG: simple-scan.vala:2007: Starting simple-scan 3.37.2, PID=18245 [+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created [+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ [+0,03s] DEBUG: app-window.vala:1987: Loading state from /home/aurelien/.cache/simple-scan/state [+0,03s] DEBUG: app-window.vala:1966: Restoring window to 688x400 pixels It not use any gio-vfs thing as in mga8 Plasma 5. And I CAN scan documents and save it as PDF with accented character. I don't have skills to know why in Plasma 5 simple-scan loads one more g_io thing which seems to conflicts here with accented characters. I wonder if I install task-plasma5 on this installation and run it after, bug will be still present?
Hi there! Today there is an update for simple-scan in Cauldron: simple-scan-3.37.3-1.mga8 So, after testing both in Gnome and in KDE Plasma 5, accented characters are no longer forbidden in file name. Seems bug resolved here.
Also in mga7 , with today current simple-scan-3.32.2.1-2.mga7 Accented characters are welcomed, both in Plasma 5 desktop and Gnome. Seems fixed.
CC: lewyssmith => (none)
Hi! I have installed Mageia 8 Beta, and I don't find the simple-scan package. It's lost for something?? Have you retired for any problems? It have
CC: (none) => joselp
Please don't use old bug reports to ask unrelated questions. But to answer your question, it's on all the beta1 ISOs, but appears to have been accidentally removed from cauldron: https://ml.mageia.org/l/arc/dev/2020-10/msg00139.html
Ok, Ok, I will report it to the mailing list that you indicate. Greetings!!
Seems to be solved. See bug 27934
Thus closing
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
I don't know if this is related, but the problem is still present in xsane, using Mageia 7 and xsane-0.999-11.mga7.src.rpm.
I tried with simple-scan-3.32.2.1-2.mga7.src.rpm right now and the problem is still present. simple-scan complains that I cannot use e.g. é or à in the file name.
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
That's because the bug has only been fixed in cauldron. If you don't have a scanner that needs it, try uninstalling the sane-backends-iscan package, which should also cure the problem. If you don't have the sane-backends-iscan package installed (and haven't installed any 3rd party packages that support Epson scanners), then there's another bug, but not one I can reproduce.
Version: Cauldron => 7
(In reply to Martin Whitaker from comment #49) > If you don't have a scanner that needs it, try uninstalling the > sane-backends-iscan package, which should also cure the problem. Fun, removing it indeed fixes the problem with both xsane and simple-scan. Nice catch! Thanks!
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: REOPENED => RESOLVEDResolution: (none) => OLD