[ghostwriter] [Bug 492363] New: Ghostwriter crashes with a segment fault on very fresh installed neon after one character is typed.
https://bugs.kde.org/show_bug.cgi?id=492363 Bug ID: 492363 Summary: Ghostwriter crashes with a segment fault on very fresh installed neon after one character is typed. Classification: Applications Product: ghostwriter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: echarr...@gmail.com Target Milestone: --- Ghostwriter crashes on a fresh updated neon Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 7.6 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: LENOVO Product Name: 10SFCTO1WW System Version: ThinkCentre M920t SUMMARY Ghostwriter crashes from beginning, STEPS TO REPRODUCE 1. start ghostwriter 2. Type one characters Then it crashes [31.197 14720 ghostwriter qt.qpa.wayland] WARNING eglSwapBuffers failed with 0x300d, surface: 0x0 [New Thread 0x7fff77e00640 (LWP 14963)] [New Thread 0x7fff77400640 (LWP 14968)] [New Thread 0x7fff76a00640 (LWP 14987)] [New Thread 0x7fff76000640 (LWP 14988)] [New Thread 0x7fff8ec00640 (LWP 14989)] [New Thread 0x7fff8d400640 (LWP 14990)] [New Thread 0x7fff83e00640 (LWP 14991)] [New Thread 0x7fff75600640 (LWP 14992)] [New Thread 0x7fff74c00640 (LWP 14993)] [New Thread 0x7fff6be00640 (LWP 14994)] [New Thread 0x7fff6b400640 (LWP 15007)] [New Thread 0x7fff6aa00640 (LWP 15008)] Thread 80 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff6b400640 (LWP 15007)] 0x555b9b96 in ghostwriter::HtmlPreviewPrivate::exportToHtml (text=..., exporter=0x55c64080) at ./src/preview/htmlpreview.cpp:331 Download failed: Invalid argument. Continuing without source file ./obj-x86_64-linux-gnu/src/./src/preview/htmlpreview.cpp. 331 ./src/preview/htmlpreview.cpp: Inappropriate ioctl for device. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 446848] Gcompris say alphabet letter names instead of actual letter sound.
https://bugs.kde.org/show_bug.cgi?id=446848 --- Comment #4 from Emmanuel Charruau --- We do this type of activity everyday with pupils learning to read, and even before the age of 6 without reading, just asking if pupils hear the sound [a] or do not ear the sound [a] for example. This would be a great activity! One little difficulty I see here is, how good will be the translation teams for this kind of exercises. This is not anymore just a translation task but, they will need to do a real pedagogical work. We have the material to do it (see enrich your vocabulary), and the task is not difficult to program. We need to properly introduce these kind of activities (maybe via youtube videos) to the translation teams and explain how important it is to create the datasets properly and do real tests. Thanks for the suggestion. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 446848] Gcompris say alphabet letter names instead of actual letter sound.
https://bugs.kde.org/show_bug.cgi?id=446848 Emmanuel Charruau changed: What|Removed |Added CC||echarr...@gmail.com --- Comment #1 from Emmanuel Charruau --- Hi, I think you are talking about click_on_letter? The goal of the application is to recognize the letters by their name not to learn to read. I wish your proposition would be easy to do, but it is not, at least in french (I am ground school teacher). In french a single letter can sound totally differently according to where it is in a word. e can sound en é è and even nothing if it is at the end of the word. However you have a point and we would like a day to be able to mimic the following app: http://grapholearn.fr/ Do not hesitate to reply if you think I missed something. Emmanuel -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 433800] Share:dataset "norest", task with rest (task 5 step 4)
https://bugs.kde.org/show_bug.cgi?id=433800 --- Comment #7 from Emmanuel Charruau --- You are right here. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 433800] Share:dataset "norest", task with rest (task 5 step 4)
https://bugs.kde.org/show_bug.cgi?id=433800 Emmanuel Charruau changed: What|Removed |Added CC||echarr...@gmail.com --- Comment #5 from Emmanuel Charruau --- Hi, When we spoke about adding this option, we wanted from a given difficulty level to have always a jar (the rest) present. We want to avoid users to conceive the following idea: 1- these is a jar = there will be a rest, I will try to find a result with a rest 2- no jar, no rest. Hope this can help, Emmanuel -- You are receiving this mail because: You are watching all bug changes.
