[digikam] [Bug 481766] New: digikam crashes on startup during "find new items"

2024-02-24 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=481766

Bug ID: 481766
   Summary: digikam crashes on startup during "find new items"
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Application: digikam (8.1.0)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.5.5-1-siduction-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
Happens every time I start digikam.
'digiKam-8.2.0-x86-64.appimage'
digikam 8.1 installed via apt on debian
and also on 'digiKam-8.0.0-beta1-x86-64-debug.appimage'

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#5  0x7f2da40a815f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#6  0x7f2da405a472 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7  0x7f2da40444b2 in __GI_abort () at ./stdlib/abort.c:79
#8  0x7f2da469107d in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2da46902ae in qt_assert_x(char const*, char const*, char const*,
int) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f2da71afcd9 in  () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#11 0x7f2da71afe03 in  () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#12 0x7f2da736a619 in Digikam::AbstractAlbumModel::index(int, int,
QModelIndex const&) const () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#13 0x7f2da739d9b8 in  () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#14 0x7f2da48fb74d in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f2da485c13e in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f2da486501a in QAbstractItemModel::endInsertRows() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f2da4892675 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f2da4896245 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f2da48994dd in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f2da48fb74d in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f2da485c13e in QAbstractItemModel::rowsInserted(QModelIndex const&,
int, int, QAbstractItemModel::QPrivateSignal) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f2da486501a in QAbstractItemModel::endInsertRows() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f2da7369855 in
Digikam::AbstractAlbumModel::slotAlbumAdded(Digikam::Album*) () at
/usr/lib/digikam/libdigikamgui.so.8.1.0
#24 0x7f2da48fba32 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f2da73746b6 in
Digikam::AlbumManager::signalAlbumAdded(Digikam::Album*) () at
/usr/lib/digikam/libdigikamgui.so.8.1.0
#26 0x7f2da73b762a in Digikam::AlbumManager::scanPAlbums() () at
/usr/lib/digikam/libdigikamgui.so.8.1.0
#27 0x7f2da48fb74d in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f2da48ff85a in QTimer::timeout(QTimer::QPrivateSignal) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f2da48ef30b in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f2da5562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#31 0x7f2da48c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f2da491bcc9 in QTimerInfoList::activateTimers() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7f2da491c5ac in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x7f2d953131b4 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x7f2d953162d7 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x7f2d953168f0 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x7f2da491c8d6 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x7f2da48c1b7b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#39 0x7f2da730de00 in
Digikam::ScanController::completeCollectionScanCore(bool, bool, bool) () at
/usr/lib/digikam/libdigikamgui.so.8.1.0
#40 0x7f2da74b4bfa in Digikam::NewItemsFinder::slotStart() () at
/usr/lib/digikam/libdigikamgui.so.8.1.0
#41 0x7f2da48ef400 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#42 0x7f2da5562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#43 0x7f2da48c30d8 in

[krusader] [Bug 448718] New: Crashes if files in an open tab are changed/added

2022-01-18 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=448718

Bug ID: 448718
   Summary: Crashes if files in an open tab are changed/added
   Product: krusader
   Version: 2.7.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY

Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x in ?? ()
#5  0x55bbfe1bc502 in ?? ()
#6  0x55bbfe1bcdfd in ?? ()
#7  0x7f139e74e1b8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f139e75202a in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f139e74404f in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f139f20f6bf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f139e717b1a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f139e76e4fb in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f139e76ed94 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f139cbdecdb in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7f139cbdef88 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7f139cbdf03f in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f139e76f154 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f139e71652b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f139e71e800 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x55bbfe185574 in ?? ()
#21 0x7f139df777ed in __libc_start_main (main=0x55bbfe181ea0, argc=3,
argv=0x7ffd8e146508, init=, fini=,
rtld_fini=, stack_end=0x7ffd8e1464f8) at ../csu/libc-start.c:332
#22 0x55bbfe186dca in _start ()
[Inferior 1 (process 1167002) detached]



STEPS TO REPRODUCE
1. [e.g.] open Download Folder with Krusader
2. use any browser to download a big file (>100 MB) [e.g. appimage]
3. switch to Krusader again and watch it crash
sometimes it also crashes in background
OBSERVED RESULT
Crashes

EXPECTED RESULT
not crashing

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.11-2-siduction-amd64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4720HQ CPU @ 2.60GHz
Memory: 15,6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

ADDITIONAL INFORMATION

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

[digikam] [Bug 431928] New: "Save to original album" does not work in Batch Queue Manager

2021-01-22 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=431928

Bug ID: 431928
   Summary: "Save to original album" does not work in Batch Queue
Manager
   Product: digikam
   Version: 7.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: BatchQueueManager-Renaming
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

SUMMARY
A batch process stores the resulting images not in the original album, but one
level above 

STEPS TO REPRODUCE
1. Create a batch process. In Queue settings chose Tab Target
2. check box labelled "Use original album"
3. go to tab File Renaming; Customize Filename: [file]_c
4. Run the Queue

OBSERVED RESULT
The target files are created in an album one level above the original album.
E.g.
The actual files are in  /album_main/sub_album/my_album
The resulting files are stored in /album_main/sub_album 

EXPECTED RESULT
The resulting files should be stored in /album_main/sub_album/my_album 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: debian 5.10.4
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I have checked this error against digikam 7.10 where the bug does not exist.

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

[digikam] [Bug 431774] New: Search does not work for specific tag and folder

2021-01-18 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=431774

Bug ID: 431774
   Summary: Search does not work for specific tag and folder
   Product: digikam
   Version: 7.2.0
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Searches-Advanced
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Search does not work properly


STEPS TO REPRODUCE
1. Open advanced search
2. check a tag (in my case flora which has sub-tags)
3. check one folder/album (that has lots of images with this tag)
4. hit "try" or "ok"

OBSERVED RESULT
no images

EXPECTED RESULT
all images in the specified folder with the tag "flora" (there are hundreds)


Linux/KDE Plasma: 5.20.4
KDE Framework 5.77.0
Kernel 5.10.4

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

[digikam] [Bug 414902] New: After using the "healing clone" tool only preview is available from other tools

2019-12-06 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=414902

Bug ID: 414902
   Summary: After using the "healing clone" tool only preview is
available from other tools
   Product: digikam
   Version: 6.4.0
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ImageEditor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Edit an Image
2. Use Enhance / Healing Clone
3. Do something and discard it
4. Go to BCR or other
5. You only see the preview (After) and not the last commited version (Before)
when moving the mouse into the image. Reproduced in Windows and Linux 

OBSERVED RESULT
Only preview (After) available


EXPECTED RESULT
PREVIEW should switch when moving the mouse into the image to the latest
commited version

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

ADDITIONAL INFORMATION

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

[gwenview] [Bug 403264] Menu entries shows "No text" instead of file, view, go

2019-01-18 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=403264

m*sh  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |LATER
 Status|NEEDSINFO   |RESOLVED

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

[gwenview] [Bug 403264] Menu entries shows "No text" instead of file, view, go

2019-01-18 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=403264

--- Comment #4 from m*sh  ---
(In reply to Nate Graham from comment #3)
> What distro are you using? Does this persist in a new user account?

Thanks Nate! [I am on debian sid]
After creating a new user I found that the menu is 'normal' for the new user.
Finally I could reset settings in
 /home//.local/share/kxmlgui5/gwenview/gwenviewui.rc
Thanks

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

[gwenview] [Bug 403264] Menu entries shows "No text" instead of file, view, go

2019-01-16 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=403264

--- Comment #2 from m*sh  ---
The Menu-Entries are shown as "No text" instead of "File", "View" ... etc.
Furthermore I can't configure the content of the left sidebar with image
information. I removed gwenview [apt remove --purge gwenview] and reinstalled
it [apt install gwenview], but the Menu is still showing "No Text".

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

[gwenview] [Bug 403264] Menu entries shows "No text" instead of file, view, go

2019-01-16 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=403264

--- Comment #1 from m*sh  ---
Created attachment 117485
  --> https://bugs.kde.org/attachment.cgi?id=117485&action=edit
Menu entries missing - Screenshot

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

[gwenview] [Bug 403264] New: Menu entries shows "No text" instead of file, view, go

2019-01-16 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=403264

Bug ID: 403264
   Summary: Menu entries shows "No text" instead of file, view, go
   Product: gwenview
   Version: 18.04.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[digikam] [Bug 400962] Image editor doesn't display the image

2018-11-12 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=400962

--- Comment #3 from m*sh  ---
I am having Qt 5.11.2

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

[digikam] [Bug 400962] New: Image editor doesn't display the image

2018-11-12 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=400962

Bug ID: 400962
   Summary: Image editor doesn't display the image
   Product: digikam
   Version: 5.9.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: ImageEditor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Created attachment 116260
  --> https://bugs.kde.org/attachment.cgi?id=116260&action=edit
Blank screen in image editor

Image Editor doesn't display the image after first use.
If digikam is started new, the image editor works but is shown without menue.
Can right click and get the main toolbar and edit the image. Editing another
image fails and shows a blank screen.
Tried to repair database without success.
Deleted the database and recreated it. Problem persists with JPG and RAW
images.

OBSERVED RESULT
Blank screen when opening 2nd image in the editor 

EXPECTED RESULT
Showing the image and Menu

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

[digikam] [Bug 396283] missing images in album preview

2018-07-08 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=396283

m*sh  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from m*sh  ---
Thanks Maik I have overseen that option.

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

[digikam] [Bug 396283] missing images in album preview

2018-07-07 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=396283

m*sh  changed:

   What|Removed |Added

   Platform|Other   |Debian unstable

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

[digikam] [Bug 396283] New: missing images in album preview

2018-07-07 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=396283

Bug ID: 396283
   Summary: missing images in album preview
   Product: digikam
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Albums-MainView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Created attachment 113817
  --> https://bugs.kde.org/attachment.cgi?id=113817&action=edit
You can see that there are two images not displayed

As well es version 5.9.0 as 6.0.0 show not all images in the album
I have this with at least two albums.
Album a) There are 3 images in the album and only two are shown
Album b) There are 5 images in the album and only three are shown
The info on the albums-panel is showing the correct number of images (see
screenshots)

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

[digikam] [Bug 387373] digikam does either show no photo in album or all photos of complete database (since Qt 5.9.3)

2018-04-13 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=387373

--- Comment #21 from m*sh  ---
The image works for me (with QT 5.102). Thanks for support.

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

[digikam] [Bug 393069] I do not see images in the file browser, only in calendar

2018-04-13 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=393069

--- Comment #2 from m*sh  ---
Yes I have Qt 5.10.1

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

[digikam] [Bug 393069] New: I do not see images in the file browser, only in calendar

2018-04-12 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=393069

Bug ID: 393069
   Summary: I do not see images in the file browser, only in
calendar
   Product: digikam
   Version: 5.6.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Albums-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Created attachment 111980
  --> https://bugs.kde.org/attachment.cgi?id=111980&action=edit
Screen is blank

File browser doesn't work at all . I can see images only when in calendar mode.
Happened without update or new version
Screen is blank

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

[digikam] [Bug 111591] Tag images browser doesn't show any images

2018-04-12 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=111591

m*sh  changed:

   What|Removed |Added

 CC||h...@sha-mash.de

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

[digikam] [Bug 383280] Panorama tool doesn't find autooptimiser from Hugin 2017.0

2017-08-12 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=383280

--- Comment #4 from m*sh  ---
Hi Gilles,
I downloaded and started 
digikam-5.7.0-01-x86-64.appimage
the problem persists. autooptimizer is in /usr/bin but after selecting it
manually nothing happens.

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

[digikam] [Bug 383280] Panorama tool doesn't find autooptimiser from Hugin 2017.0

2017-08-11 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=383280

--- Comment #2 from m*sh  ---
Hi Gilles, I am using hugin 2017.0
[hugin is already the newest version (2017.0.0~rc2+dfsg-2).]
autooptimiser is in /usr/bin
but nothing happens when I select it manually
Greetings

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

[digikam] [Bug 383280] New: Digikam (panorama creation tool) doesn't find autooptimiser

2017-08-08 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=383280

Bug ID: 383280
   Summary: Digikam (panorama creation tool) doesn't find
autooptimiser
   Product: digikam
   Version: 5.3.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Interroperability
  Assignee: digikam-bugs-n...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

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

The panorama tool doesn't find autooptimiser
Hugin is installed completely (Tried uninstall and reinstalled as well...)

the wizard can't continue (see screenshot attached)

It worked before but I don't use it very often - so I can not exactly describe
What was changed. Actually I did one dist-upgrade between last usage in june
and now.

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

[digikam] [Bug 381586] Crash after tagging ~5 images

2017-06-24 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=381586

--- Comment #2 from m*sh  ---
It xrashed because there was a JPG file in the album with extension DNG. When
Pressing F3 digikam crashes on that.

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

[digikam] [Bug 381586] New: Crash after tagging ~5 images

2017-06-23 Thread m*sh
https://bugs.kde.org/show_bug.cgi?id=381586

Bug ID: 381586
   Summary: Crash after tagging ~5 images
   Product: digikam
   Version: 5.3.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: h...@sha-mash.de
  Target Milestone: ---

Application: digikam (5.3.0)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.10.15-towo.1-siduction-amd64 x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

-- Information about the crash:
I was just about to give a few images a new tag when application crashed.
BEFORE that I was reorganizing the tag tree a little bit.
After reorganizing digikam got very slow. I closed digikam.
After a restart several new tags (images already ad these tags) were missing.
I added them back manually and went on tagging

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c8707ab40 (LWP 11459))]

Thread 17 (Thread 0x7f3bda7fc700 (LWP 26993)):
#0  0x7f3cb088b08d in nanosleep () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f3cb16390ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3cb1593128 in QThread::msleep(unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f3cb1692dd1 in QLockFile::tryLock(int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3cb25821d9 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#5  0x7f3cb256bec0 in KConfig::sync() () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#6  0x7f3cb256c5b5 in KConfig::~KConfig() () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#7  0x7f3cb258b513 in KSharedConfig::~KSharedConfig() () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#8  0x7f3cb258b539 in KSharedConfig::~KSharedConfig() () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#9  0x7f3cb258bc78 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#10 0x7f3cb1592023 in QThreadStorageData::finish(void**) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f3cb1592ecc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f3cb1593db0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f3cad9e9494 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#14 0x7f3cb08bb93f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 16 (Thread 0x7f3bebfff700 (LWP 22395)):
#0  0x7f3cad9ef15f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3cb1594c6b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3cb226c301 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x7f3cb1593da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3cad9e9494 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f3cb08bb93f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 15 (Thread 0x7f3c14fca700 (LWP 22332)):
#0  0x7f3cad9ef15f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3cb1594c6b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3cb226c301 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x7f3cb1593da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3cad9e9494 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f3cb08bb93f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 14 (Thread 0x7f3c17189700 (LWP 15543)):
#0  0x7f3ca7e660e9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3ca7e20404 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3ca7e20994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3ca7e20b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3cb17b806b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3cb17619ca in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3cb3369fda in ?? () from /usr/lib/digikam/libdigikamcore.so.5.3.0
#7  0x7f3cb159014f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3cb1593da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f3cad9e9494 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f3cb08bb93f in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 13 (Thread 0x7f3bff7fe700 (LWP 13294)):
#0  0x7f3ca7e1fe7b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3ca7e20

[krusader] [Bug 360001] connecting to an ftp-server fails

2016-03-02 Thread m*sh via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360001

m*sh  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from m*sh  ---
There was an error on the server-side

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


[krusader] [Bug 360001] New: connecting to an ftp-server fails

2016-03-02 Thread m*sh via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360001

Bug ID: 360001
   Summary: connecting to an ftp-server fails
   Product: krusader
   Version: 2.4.0-beta3 "Single Step"
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: net-connection
  Assignee: m...@fork.pl
  Reporter: h...@sha-mash.de

>From Menu: tools - New Net connection
enter ftp-adress
enter username
enter password hit 
Results in the following errormessages:
Error: The directory
[$currentPath]/ftp:/<$USERNAME>:<$PASS>@:21 does not exist
Where
$currentPath is the path of the last active panel
$USERNAME is the username provided in login screen
$PASS is the password used

Reproducible: Always

Steps to Reproduce:
1. From Menu: tools - New Net connection
2. enter ftp-adress
3. Enter credentials

Actual Results:  
Error: The directory
[$currentPath]/ftp:/<$USERNAME>:<$PASS>@:21 does not exist
Where
$currentPath is the path of the last active panel
$USERNAME is the username provided in login screen
$PASS is the password used

Expected Results:  
a coonnection to the ftp-server

I think the severity is high because the login credentials are shown on the
screen after a failed attempt to establish a connection.

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