[parley] [Bug 361947] vocabularies don't get promoted when answered correctly

2022-10-20 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=361947

Juergen  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Juergen  ---
Bug is 6 years old!

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 454318] New: Save as Version in Imageeditor not accessible when using external raw editor (rawtherapee)

2022-05-24 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=454318

Bug ID: 454318
   Summary: Save as Version in Imageeditor not accessible when
using external raw editor (rawtherapee)
   Product: digikam
   Version: 7.6.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: ImageEditor-Versioning
  Assignee: digikam-bugs-n...@kde.org
  Reporter: j.z...@online.de
  Target Milestone: ---

SUMMARY
Save as Version in Imageeditor not accessible when using external raw editor
(rawtherapee)
***
If rawtherapee is set as an external raw processor, this will also be started.
When rawtherapee is closed, the edited result is displayed in the image editor.
However, only the "Export" option is available for saving. It would be good if
the "Save as Version" option was also available. However, this only becomes
active if additional processing has been carried out with one of the original
digikam tools.
***
STEPS TO REPRODUCE
1. Start/End edit a raw file with digikam using rawtherapee as raw editor 

OBSERVED RESULT
In Imageedit View only the export button is activ

EXPECTED RESULT
In Imageedit the save as Verion button is also activ

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Win/digikam/rawtherapee run in language de

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 278437] incorrect number of verbs displayed when in conjugation mode

2022-12-21 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=278437

Juergen  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Juergen  ---
This bug is too old.

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 317993] It is not possible to mark 2 vocabularies in 2 different lesson as synonyms.

2023-01-11 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=317993

--- Comment #5 from Juergen  ---
Dear Justin,

all these issues have been reported 10 years or so ago and are obsolate. 
Please close them. I have moved on with my life and don't use Parley at 
the moment.

Thank you and have a nice day

Juergen


Justin Zobel wrote on 12/01/2023 07:27:
> https://bugs.kde.org/show_bug.cgi?id=317993
>
> Justin Zobel  changed:
>
> What|Removed |Added
> 
>   Status|REPORTED|NEEDSINFO
>   Resolution|--- |WAITINGFORINFO
>
> --- Comment #4 from Justin Zobel  ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 255165] Loose Editor toolbar on incorrect shut-down

2023-01-11 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=255165

--- Comment #6 from Juergen  ---
Dear Justin,

all these issues have been reported 10 years or so ago and are obsolate. 
Please close them. I have moved on with my life and don't use Parley at 
the moment.

Thank you and have a nice day

Juergen

Justin Zobel wrote on 12/01/2023 07:27:
> https://bugs.kde.org/show_bug.cgi?id=255165
>
> Justin Zobel  changed:
>
> What|Removed |Added
> 
>   Status|REPORTED|NEEDSINFO
>   Resolution|--- |WAITINGFORINFO
>
> --- Comment #5 from Justin Zobel  ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 321867] Editor toolbar disappears after restart

2023-01-11 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=321867

--- Comment #6 from Juergen  ---
Dear Justin,

all these issues have been reported 10 years or so ago and are obsolate. 
Please close them. I have moved on with my life and don't use Parley at 
the moment.

Thank you and have a nice day

Juergen

Justin Zobel wrote on 12/01/2023 07:28:
> https://bugs.kde.org/show_bug.cgi?id=321867
>
> Justin Zobel  changed:
>
> What|Removed |Added
> 
>   Resolution|--- |WAITINGFORINFO
>   Status|REPORTED|NEEDSINFO
>
> --- Comment #5 from Justin Zobel  ---
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
>
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 376963] New: Printout like a poststamp

2017-02-26 Thread juergen
https://bugs.kde.org/show_bug.cgi?id=376963

Bug ID: 376963
   Summary: Printout like a poststamp
   Product: digikam
   Version: 4.12.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ImageEditor-Print
  Assignee: digikam-de...@kde.org
  Reporter: juergen...@t-online.de
  Target Milestone: ---

Created attachment 104237
  --> https://bugs.kde.org/attachment.cgi?id=104237&action=edit
printermenu

Hello
Printouts are very small , like a post stamp.
If I print from Digikam to an Adobe PDF file, then I can print 4x6 borderless
in a good quality.
It will make not a difference , if I scale the Picture in the printermenu or
not.



Thank you

-- 
You are receiving this mail because:
You are watching all bug changes.

[kcalc] [Bug 496412] New: Entering large numbers, unexpected behaviour

2024-11-18 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=496412

Bug ID: 496412
   Summary: Entering large numbers, unexpected behaviour
Classification: Applications
   Product: kcalc
   Version: 24.08.2
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: evan.te...@gmail.com
  Reporter: kde-...@huppertz.org
CC: gabriel.barrantes@outlook.com
  Target Milestone: ---

Created attachment 175907
  --> https://bugs.kde.org/attachment.cgi?id=175907&action=edit
screenshot of the calculator

SUMMARY

I expected the x*10^y button works like in other calculators the EXP Button to
enter the exponent of a number like
2e6. Without am EXP button or an equvalent it is error prone to enter big or
small numbers like 2e-7. 
Using the kcalc x*10^y button I get something like this 2*10^6, typically a
calculator uses 2e6 which is (2*10^6). The display of the number in kcalc (see
screenshot) suggests that it is an alternative to the 2e6 representation. If
this number ends up in a divisor one gets a huge error. 
Kcalc uses anyhow this kind of number representation for its results.

In kcalc it works like this:
1/2 * 10^6 = 50

I would like to have 
1/2e6 = 2e-7

STEPS TO REPRODUCE
1. Enter: 1
2. /
3. 2
4. Press the button: x*10^y
5. 6
6. =

OBSERVED RESULT
50

EXPECTED RESULT
5e-7

SOFTWARE/OS VERSIONS
Linux 6.11.5-2-default (64-bit)
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kcalc] [Bug 496412] Entering large numbers, unexpected behaviour

2024-11-18 Thread Juergen
https://bugs.kde.org/show_bug.cgi?id=496412

Juergen  changed:

   What|Removed |Added

 CC||kde-...@huppertz.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 371593] Sort valuelist combo

2016-11-06 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=371593

--- Comment #6 from Juergen Spitzmueller  ---
Created attachment 102068
  --> https://bugs.kde.org/attachment.cgi?id=102068&action=edit
Addon fix

There is a small glitch in the commit. Customized text is set too early and
then overwritten. This patch fixes the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 449725] Black Writing in blue annotation box not readable

2024-03-09 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=449725

Juergen Spitzmueller  changed:

   What|Removed |Added

   Keywords||accessibility

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 449725] Black Writing in blue annotation box not readable

2023-11-06 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=449725

Juergen Spitzmueller  changed:

   What|Removed |Added

 CC||juer...@spitzmueller.org

--- Comment #8 from Juergen Spitzmueller  ---
Created attachment 162903
  --> https://bugs.kde.org/attachment.cgi?id=162903&action=edit
Comparison of Okular, Evince, and Master PDF Editor

I think a rather straighforward way to address this is to make the text widget
part of the annotation use a lighter color or even white, as is the case in
many other PDF viewers (see evince and Master PDF Editor here for comparison;
Acrobat also has a white text field).

I agree with the OP that the text in the blue notes (and also in some other of
the darker colors) is hardly readable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 389306] QxtSpanSlider w/ mouse does not work with KF5

2018-02-11 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=389306

--- Comment #7 from Juergen Spitzmueller  ---
Seems to work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 371558] Dynamic crossref resolution and mapping

2018-01-20 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=371558

--- Comment #3 from Juergen Spitzmueller  ---
There seems to be no interest in this, but for the record, a working
implementation (including proper support for XData fields) can be found at
https://github.com/jspitz/kbibtex

Note that this depends on a reversion of the hardcoding of bibtex field
information done upstream (in other words, I have re-introduced the *.kbstyle
files. I think with hardcoded fields, proper biblatex support can never be
fully achieved, since biblatex itself allows for adding new fields for specific
purposes, a feature that is often used by specific biblatex styles; so we need
the possibility to add custom styles in the bibtex editor)

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 389306] New: QxtSpanSlider w/ mouse does not work with KF5

2018-01-22 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=389306

Bug ID: 389306
   Summary: QxtSpanSlider w/ mouse does not work with KF5
   Product: KBibTeX
   Version: git (master)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User interface
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: juer...@spitzmueller.org
  Target Milestone: ---

With recent master/KF5 on OpenSuse Tumbleweed, the QxtSpanSlider used in the ID
Suggestion Editor does not work anymore with the mouse. Whenever I touch the
upper handle, it snaps to position 0 and cannot be moved anymore (the slider
initially shows the correct settings, though; it just seems impossible to use
it to change range settings). The lower handle cannot be moved at all with the
mouse.

Note that I can successfully move both handles with the keyboard (left/right
arrows for lower handle, up/down arrows for upper handle).

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 389306] QxtSpanSlider w/ mouse does not work with KF5

2018-01-29 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=389306

--- Comment #3 from Juergen Spitzmueller  ---
Yes, the problem is fixed. I find the combo solution a bit awkward, though. I'd
rather go for two spin boxes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 389306] QxtSpanSlider w/ mouse does not work with KF5

2018-01-29 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=389306

--- Comment #5 from Juergen Spitzmueller  ---
You could setWrapping(true), then the special ValueText would be at the edge of
minimum/maximum.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 378828] New: KWIN chrashes everey 5min (not exactly, but...)

2017-04-15 Thread Juergen Grete
https://bugs.kde.org/show_bug.cgi?id=378828

Bug ID: 378828
   Summary: KWIN chrashes everey 5min (not exactly, but...)
   Product: kwin
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: juer...@jgrete.de
  Target Milestone: ---

Application: kwin_x11 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-19-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
- What I was doing when the application crashed:
Normaly working with some programs (librteoffice, handbrake,this assistent,
etc...)

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9abbc4f900 (LWP 19419))]

Thread 4 (Thread 0x7f9a7a6e3700 (LWP 19436)):
#0  0x7f9ab4d81510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9ab80ac2c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f9ab80ac309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f9ab4d7b6da in start_thread (arg=0x7f9a7a6e3700) at
pthread_create.c:456
#4  0x7f9abb68717f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f9a92456700 (LWP 19432)):
#0  0x7f9abb67b251 in __GI_ppoll (fds=0x7f9a84000ac8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f9ab8f42251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9ab8f43b4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9ab8ef088a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9ab8d1dfe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ab3ae8df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f9ab8d22c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9ab4d7b6da in start_thread (arg=0x7f9a92456700) at
pthread_create.c:456
#8  0x7f9abb68717f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f9aa4c54700 (LWP 19422)):
#0  0x7f9abb67b251 in __GI_ppoll (fds=0x7f9aa000d708, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f9ab8f42251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9ab8f43b4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9ab8ef088a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9ab8d1dfe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9ab2cc15c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x7f9ab8d22c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9ab4d7b6da in start_thread (arg=0x7f9aa4c54700) at
pthread_create.c:456
#8  0x7f9abb68717f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f9abbc4f900 (LWP 19419)):
[KCrash Handler]
#6  0x7f9a832d0ee6 in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#7  0x7f9a832d1437 in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#8  0x7f9a8333eee6 in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#9  0x7f9a83343b16 in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#10 0x7f9a832ff1ca in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#11 0x7f9a833233e8 in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#12 0x7f9a8332380d in  () at /usr/lib/nvidia-375/libnvidia-glcore.so.375.39
#13 0x7f9a908e8e46 in  () at /usr/lib/nvidia-375/libGLX_nvidia.so.0
#14 0x7f9a94630f9c in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#15 0x7f9a946295a9 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#16 0x7f9abb20f18b in KWin::SceneOpenGL::paint(QRegion,
QList) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5
#17 0x7f9abb1e99ce in KWin::Compositor::performCompositing() () at
/usr/lib/x86_64-linux-gnu/libkwin.so.5
#18 0x7f9ab8f1f313 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f9ab9bca35c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f9ab9bd1b11 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f9ab8ef28a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_6

[KBibTeX] [Bug 371558] Dynamic crossref resolution and mapping

2017-08-31 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=371558

--- Comment #2 from Juergen Spitzmueller  ---
Time to reconsider?

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 379315] KBibTex crashed when aborting duplicate removal

2017-06-27 Thread Juergen Spitzmueller
https://bugs.kde.org/show_bug.cgi?id=379315

Juergen Spitzmueller  changed:

   What|Removed |Added

 CC||juer...@spitzmueller.org

--- Comment #3 from Juergen Spitzmueller  ---
I was struck by the same crash (100% reproducible).

With the patch, kbibtex does not crash anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 479728] New: DarkTable does not open when trying to edit a Raw formatted picture (DNG) in digiKam

2024-01-13 Thread Juergen RA Barnert
https://bugs.kde.org/show_bug.cgi?id=479728

Bug ID: 479728
   Summary: DarkTable does not open when trying to edit a Raw
formatted picture (DNG) in digiKam
Classification: Applications
   Product: digikam
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plugin-RawImport-Darktable
  Assignee: digikam-bugs-n...@kde.org
  Reporter: juergen.barn...@gmail.com
  Target Milestone: ---

SUMMARY
***
I can not import RAW formatted images by using darkTable. 
***


STEPS TO REPRODUCE
1. In the settings > RAW behaviour I set 'always open the Raw Import Tool to
customize settings' to 'Raw Import using DarkTable'
2. When trying to edit a Raw formatted picture (DNG) only a embedded jpeg
preview is opening
3. 

OBSERVED RESULT
When opening / editing a Raw formatted picture DarkTable does not open

EXPECTED RESULT
I would expect that when trying to edit a Raw formatted picture in digiKam,
Darktable should open

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kubuntu (22.04), Plasma (5.24.7)

(available in About System)
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.02.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 479728] DarkTable does not open when trying to edit a Raw formatted picture (DNG) in digiKam

2024-01-14 Thread Juergen RA Barnert
https://bugs.kde.org/show_bug.cgi?id=479728

--- Comment #2 from Juergen RA Barnert  ---
Thank You very for this reply

Am 13.01.2024 um 12:51 schrieb Maik Qualmann:
> https://bugs.kde.org/show_bug.cgi?id=479728
>
> Maik Qualmann  changed:
>
> What|Removed |Added
> 
>   CC||metzping...@gmail.com
>
> --- Comment #1 from Maik Qualmann  ---
> If you use both digiKam and darktable as a snap package on Ubuntu, this will
> not work. Programs in a Snap package are separated from the system by a
> sandbox. We won't be able to help there.
>
> Maik
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 498017] New: KDE3, KMail

2024-12-29 Thread Hans-Juergen Hipp
https://bugs.kde.org/show_bug.cgi?id=498017

Bug ID: 498017
   Summary: KDE3, KMail
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: juergen-h...@t-online.de
  Target Milestone: ---

I have installed OpenSuse Leap 15.6 with KDE3 Vers.3.5.10 and cannot establish
a connection to the T-Online server via KMail. It works without any problems
under OpenSuse Leap 15.5. I have the OpenSuse Repro: KDE3, 15.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 362799] can't write export file

2016-07-02 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362799

--- Comment #2 from Juergen  ---
I practise in this case multiple choice. After the practise is finish I get the
results. Then I press the "export result" button. A new window appears in which
I chose the location and name in html format and when I press save I get an
error like this "Could not write to /home/user/test"

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] Parley can write lock file

2016-07-27 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

--- Comment #7 from Juergen  ---
Thank you for this comment. I will wait until Unbuntu upgrades :)

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 357385] Cannot edit existing collection

2016-09-10 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357385

--- Comment #9 from Juergen  ---
The status of this bug is not resolved. I have no idea how to implement the
above changes. The vocabulary file still can not be saved excepts by manually
overwriting it. I consider this a bug that needs attention. If it is already
fixed like mentioned above why can't one get a deb package to fix this bug.
Any suggestion what to do?

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] Parley can write lock file

2016-06-22 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

--- Comment #5 from Juergen  ---
Created attachment 99657
  --> https://bugs.kde.org/attachment.cgi?id=99657&action=edit
next version up

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] Parley can write lock file

2016-05-17 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

--- Comment #4 from Juergen  ---
bug continues in version   4:16.04.0-0u amd64

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 363567] New: improved design of multiple choice test

2016-05-26 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363567

Bug ID: 363567
   Summary: improved design of multiple choice test
   Product: parley
   Version: 1.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

Version 2.1.0 4:15.12.3-0ubuntu1 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built
against 5.5.1) The xcb windowing system 64 bit Ubuntu 16.04

I suggest to shift the "Continue" button in the present interface from the
bottom of the box to the right (see screen shot). It saves a lot of mouse
movement when one for example goes through 100 vocabularies.

Reproducible: Always

Steps to Reproduce:
see screen shot

Actual Results:  
see screen shot

Expected Results:  
see screen shot

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 363567] improved design of multiple choice test

2016-05-26 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363567

--- Comment #1 from Juergen  ---
Created attachment 99211
  --> https://bugs.kde.org/attachment.cgi?id=99211&action=edit
screenshot multiple choise window

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 361947] New: vocabularies don't get promoted when answered correctly

2016-04-18 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361947

Bug ID: 361947
   Summary: vocabularies don't  get promoted when answered
correctly
   Product: parley
   Version: 1.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

Parley 1.1.1 , KDE 4.14.13 ubuntu 14.04 64 bit

A number of vocabularies don't  get promoted when answered correctly. They are
stuck on level 2.

Reproducible: Always

Steps to Reproduce:
1. go to practise mode
2. answer correctly. first time the words get promoted from level 1 to 2, then
get stuck forever on level 2



Expected Results:  
All words should be promoted. In my vocabulary file presently it is about 20
words out of 1000

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 361947] vocabularies don't get promoted when answered correctly

2016-04-18 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361947

--- Comment #1 from Juergen  ---
Here are some of the stuck words:
=

  
world
  
  
el mundo

  0
  4
  7
  1
  2016-04-18T21:49:21
  0

  
===

  
seat
  
  
el asiento

  0
  4
  12
  1
  2016-04-12T04:32:26
  0


  la silla

  



  
partner/mate
  
  
el compañero

  0
  4
  12
  1
  2016-04-18T17:04:49
  0


  acompañante

  

===

  
finger, toe
  
  
el dedo

  0
  3
  11
  1
  2016-04-15T19:17:17
  0


  la uña

  

-- 
You are receiving this mail because:
You are watching all bug changes.

[parley] [Bug 357385] Cannot edit existing collection

2016-04-23 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357385

Juergen  changed:

   What|Removed |Added

 CC||b4tas...@auroville.org.in

--- Comment #7 from Juergen  ---
Ubuntu 16.04 64bit after upgrade from 14.04
Writing file "..." resulted in an error: The lock file can't be created.

The vocabulary collection is locked by another process.  You can open the file
if you take over the lock, but you will lose any changes from the other
process.

Version 2.1.0
Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

This bug has rendered my Parley unusable. Can somebody explain in English :)
how to solve this problem.
Thanks for any help

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 357385] Cannot edit existing collection

2016-04-23 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357385

--- Comment #8 from Juergen  ---
using 4:15.12.3-0ubuntu1

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] New: Parley can write lock file

2016-04-23 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

Bug ID: 362176
   Summary: Parley can write lock file
   Product: parley
   Version: 1.1.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

This is a duplicate report of https://bugs.kde.org/show_bug.cgi?id=357385 which
is marked as "resolved" which is not the case for the latest ubuntu 16.04 64bit
on my computer. Before the upgrade all worked fine.

now I get this error:
Writing file "..." resulted in an error: The lock file can't be created.

The vocabulary collection is locked by another process.  You can open the file
if you take over the lock, but you will lose any changes from the other
process.

Do you want to take over the lock?

Version 2.1.0
4:15.12.3-0ubuntu1
Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system



Reproducible: Always

Steps to Reproduce:
1. open parley 
2. get message "Writing file "..." resulted in an error: The lock file can't be
created."
3. 

Actual Results:  
parley can't save any lock or any data 

Expected Results:  
parley can save lock files and data

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] Parley can write lock file

2016-04-25 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

--- Comment #1 from Juergen  ---
QFile::copy: Empty or null file name
"Cannot lock file "
Save failed trying save as for  "/home//parley-en-es-0.4.2.kvtml"
QFile::copy: Empty or null file name
"Cannot lock file "
Save failed trying save as for  "/home//parley-en-es-0.4.2.kvtml"
QFile::copy: Empty or null file name
"Cannot lock file "
Save failed trying save as for  "/home//parley-en-es-0.4.2.kvtml"
Clear summary widget
Set invalid document
Clear summary widget
QCoreApplication::postEvent: Unexpected null receiver

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362176] Parley can write lock file

2016-04-25 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362176

--- Comment #2 from Juergen  ---
as a temporary work around:
when trying to save the file and getting the message 

Writing file "/home/./parley-en-es-0.4.2.kvtml" resulted in an error: The
lock file can't be created.

the "Save as" dialogue window opens and I choose the same file name.
whne asked "parley-en-es-0.4.2.kvtml already exists.
Do you want to replace it?" I say yes.

then a warming window pops up:

The file
/home/.../parley-en-es-0.4.2.kvtml
already exists. Do you want to overwrite it?

I say yes. File is saved. However the automatic backup and the save on exit and
quit needs to be disabled. 

I hope this can be fixed soon

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362565] New: "conjugations" training mode gives error message

2016-05-01 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362565

Bug ID: 362565
   Summary: "conjugations" training mode gives error message
   Product: parley
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

I am trying to use parley practice in the "conjugations" mode but I always get
the error following error:
The vocabulary document contains no entries that can be used for the chosen
type of practice.

I tried to troubleshoot the problem and created a new unit with only one verb
in it and entered the right conjugation form for the present tense Spanish.

Then I tried it again but I am still getting the same error. I am not sure
what/if I am doing something wrong. Is anyone using that mode in parley? Any
insights or hints would be greatly appreciated.
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
parley version 4:15.12.3-0ubuntu1

I am using Parley several years now and I never got the conjugation training
working. I always get this error. Find the one verb file attached.
Thank you! 



Reproducible: Always

Steps to Reproduce:
1. got to training mode
2. choose conjugations
3.

Actual Results:  
Error: The vocabulary document contains no entries that can be used for the
chosen type of practice.


Expected Results:  
I can learn conjugations

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362565] "conjugations" training mode gives error message

2016-05-01 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362565

--- Comment #1 from Juergen  ---
Created attachment 98740
  --> https://bugs.kde.org/attachment.cgi?id=98740&action=edit
one verb test file

-- 
You are receiving this mail because:
You are watching all bug changes.


[parley] [Bug 362799] New: can't write export file

2016-05-07 Thread Juergen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362799

Bug ID: 362799
   Summary: can't write export file
   Product: parley
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

Version 2.1.0 4:15.12.3-0ubuntu1 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built
against 5.5.1) The xcb windowing system, ubuntu 16.04 64 bit

When trying to export practise results Parley gives an error message:

Could not write to /home/user/practice_export


Parley can't write export file

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371515] New: Adding new entry is slow

2016-10-23 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371515

Bug ID: 371515
   Summary: Adding new entry is slow
   Product: KBibTeX
   Version: 0.6
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User interface
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: juer...@spitzmueller.org

Created attachment 101714
  --> https://bugs.kde.org/attachment.cgi?id=101714&action=edit
Proposed fix

Especially with the biblatex style, adding a new entry to a database can be
extremely slow. It takes up to ~10 seconds until the widget edit dialog finally
pops up.

Debugging revealed that the culprit is FileView::setSelectedElement, more
precisely the loop over all columns added in
https://quickgit.kde.org/?p=kbibtex.git&a=commit&h=4f529a8444e4c

In my case, this loops over all (130!) columns just for the sake of selecting
the whole row after the new entry has been added.

I'll attach a patch which uses the QItemSelectionModel::Rows flag instead,
which has the same effect but is _much_ faster (the editing window now pops up
almost instantaneously).

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371515] Adding new entry is slow

2016-10-23 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371515

--- Comment #1 from Juergen Spitzmueller  ---
BTW, independent of my patch, the selection of the new entry fails if (1.) the
database has comments or macros and (2.) if "Show comments" or "Show macros" is
disabled in the prefs. Presumably due to a mismatch of the rows in the file
model and the QAbstractItemModel. I had a look but did not find a solution how
these can be synchronized.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371515] Adding new entry is slow

2016-10-23 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371515

Juergen Spitzmueller  changed:

   What|Removed |Added

 Attachment #101714|0   |1
is obsolete||

--- Comment #2 from Juergen Spitzmueller  ---
Created attachment 101718
  --> https://bugs.kde.org/attachment.cgi?id=101718&action=edit
Updated patch (addressing the mentioned additional issue)

I found the solution to the index mismatching problem: We have to use
sortFilterProxyModel()->mapFromSource.

The updated patch does this.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371558] New: Dynamic crossref resolution and mapping

2016-10-24 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371558

Bug ID: 371558
   Summary: Dynamic crossref resolution and mapping
   Product: KBibTeX
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User interface
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: juer...@spitzmueller.org

Created attachment 101735
  --> https://bugs.kde.org/attachment.cgi?id=101735&action=edit
Implement dynamic crossref resolution and mapping

(Transfered from https://gna.org/bugs/?20407, since GNA does not seem to get
attention anymore)

Currently, the crossref resolution is hardcoded to the "crossref" field.
However, biblatex also has the field "xdata" which is used in a similar way
(note that biblatex's xref field must not be resolved, since it does not
inherit fields from the target.). Furthermore, biblatex does not do a
1:1-mapping, but maps fields more cleverly (author > bookauthor etc.).

The attached patch (against branch/0.6) implements this function.

* It dynamically resolves xdata entries (also multiple and nested ones)

* It implements proper crossref field mapping (via the kbstyle file; the syntax
should be self-explaining, but is also documented in the source).

I think this patch is a significant improvement for biblatex users.

The patch is the last version I posted over at GNA. I have tested it now in
real work for several weeks.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371593] New: Sort valuelist combo

2016-10-24 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371593

Bug ID: 371593
   Summary: Sort valuelist combo
   Product: KBibTeX
   Version: 0.6
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User interface
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: juer...@spitzmueller.org

Created attachment 101748
  --> https://bugs.kde.org/attachment.cgi?id=101748&action=edit
Sort the valuelist combo locale-aware

The valuelist combo box does not seem to have a transparent sorting order,
which makes its use (especially with many fields as in biblatex) rather clumsy.
I propose to sort it alphabetically (locale-aware). Patch attached.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371593] Sort valuelist combo

2016-10-24 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371593

--- Comment #1 from Juergen Spitzmueller  ---
BTW the same should be done for the entry type combo in the entry edit dialog.
I can provide a separate path if you like.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371593] Sort valuelist combo

2016-10-24 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371593

--- Comment #2 from Juergen Spitzmueller  ---
(In reply to Juergen Spitzmueller from comment #1)
> BTW the same should be done for the entry type combo in the entry edit
> dialog. I can provide a separate path if you like.

... and the "Field" combobox in the filter bar.

Updated patch that considers all three cases follows.

-- 
You are receiving this mail because:
You are watching all bug changes.


[KBibTeX] [Bug 371593] Sort valuelist combo

2016-10-24 Thread Juergen Spitzmueller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371593

Juergen Spitzmueller  changed:

   What|Removed |Added

 Attachment #101748|0   |1
is obsolete||

--- Comment #3 from Juergen Spitzmueller  ---
Created attachment 101765
  --> https://bugs.kde.org/attachment.cgi?id=101765&action=edit
Updated patch that considers two more combo boxes

-- 
You are receiving this mail because:
You are watching all bug changes.