[krusader] [Bug 445549] kioslave5 blocking umount

2024-03-27 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=445549

--- Comment #13 from Jim  ---
Given the lack of response, I'm assuming that this bug is not going to be
addressed, so I began searching for a workaround on my own.  It failed, but I
wanted to document what I did and the results for anyone following this bug
report or finding it in the future.

I found that the kio packages are not flagged as being built for a specific
version of ubuntu and that
https://repo.miserver.it.umich.edu/ubuntu/pool/universe/ has the older (5.68)
versions.

First, I installed qml-module-org-kde-kio_5.92.0-0ubuntu1_amd64.deb in the hope
that this behavior was simply due to a missing dependency not being installed. 
Unfortunately, the problem still existed, so I removed the package.

I then installed kio-extras_19.12.3a-0ubuntu2_amd64.deb &
kio-extras-data_19.12.3a-0ubuntu2_all.deb - dpkg complained of missing
libopenexr24_2.3.0-6ubuntu0.5_amd64.deb so I downloaded & installed it.  It
then complained of missing libilmbase24_2.3.0-6build1_amd64.deb so I did the
same for that package too.  The problem still existed.

I installed libkf5kiowidgets5_5.68.0-0ubuntu1_amd64.deb over version 5.92 that
was on my system (installed by apt when the laptop was first set up).  Krusader
would not start - krusader: symbol lookup error:
/lib/x86_64-linux-gnu/libKF5Parts.so.5: undefined symbol:
_ZN3KIO13JobUiDelegateC1E6QFlagsIN14KJobUiDelegate4FlagEEP7QWidget when run
from a command line.

Figuring it needed the rest of the kio libraries, I installed these one at a
time, testing between each:
   libkf5kiontlm5_5.68.0-0ubuntu1_amd64.deb - same error
   libkf5kiofilewidgets5_5.68.0-0ubuntu1_amd64.deb - same error
   libkf5kiogui5_5.68.0-0ubuntu1_amd64.deb - same error
   libkf5kiocore5_5.68.0-0ubuntu1_amd64.deb - different error this time -
krusader: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Parts.so.5:
undefined symbol: _ZN3KIO11TransferJob13mimeTypeFoundEPNS_3JobERK7QString
   kio_5.68.0-0ubuntu1_amd64.deb - second error repeated itself

Since krusader would still not start, I got to thinking that there are probably
other dependencies out there, so queried apt & found that there are 104 (!!!)
libkf5* packages on my system.  Decided that I do not have the patience to go
through the list, manually download each, and chase dependencies for every one
of them.

Removed libilmbase24 libopenexr24 kio-extras kio-extras-data with dpkg, then
installed kio kio-extras kio-extras-data libkf5kiocore5 libkf5kiofilewidgets5
libkf5kiogui5 libkf5kiontml5 libkf5kiowidgets5 via apt to put my system back
how it was, defect and all. :( 

---

Does anyone know of any programs that look / feel / behave like krusader that
may not be affected by this flaw in the underlying KDE system?  Or know of a
viable workaround to fix the file locking issues introduced between 5.68 &
5.92?  Love the program, but it's just plain broken at this point, especially
with my using flash drives every single day.

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

[kdenlive] [Bug 471555] Preview not playing, hangs

2024-01-16 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471555

Jim Henderson  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |NOT A BUG
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Jim Henderson  ---
I don't know if I can update the driver for the video card, as this is a
Macbook Pro.
Sorry I left this sitting for so long -- I don't think it has been a problem
lately.
Since then I have ugraded the operating system to Sonoma 14.2.1.
If it happens again, I'll report again. I'll close the issue now.

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

[krita] [Bug 478588] Show Colors from the image combines all canvas colors into one for Color Selectors

2023-12-15 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=478588

--- Comment #2 from Jim  ---
This bug behavior seems to happen with Pixel Art brushes and tools.

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

[krita] [Bug 478588] Show Colors from the image combines all canvas colors into one for Color Selectors

2023-12-15 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=478588

--- Comment #1 from Jim  ---
Created attachment 164215
  --> https://bugs.kde.org/attachment.cgi?id=164215=edit
Screenshot showing Colors from Image patch combining all canvas colors into one

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

[krita] [Bug 478588] New: Show Colors from the image combines all canvas colors into one for Color Selectors

2023-12-15 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=478588

Bug ID: 478588
   Summary: Show Colors from the image combines all canvas colors
into one for Color Selectors
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: snopm...@yahoo.com
  Target Milestone: ---

Created attachment 164214
  --> https://bugs.kde.org/attachment.cgi?id=164214=edit
Krita Usage Log

SUMMARY
Show Colors from the image combines all canvas colors into one for Color
Selectors.

STEPS TO REPRODUCE
1. paint various colors on the canvas and observe the color patches from image.

OBSERVED RESULT
The various colors painted on the canvas gets combined into one patch for the
"Colors from Image" for both Advanced Color Selector and Wide Gamut Color
Selector.

EXPECTED RESULT
Painting different colors on the canvas will have them show up in their own
color patch on the Color Selectors.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Home Version: 10.0.19045 Build 19045

ADDITIONAL INFORMATION
krita-nightly-x64-5.3.0-prealpha-f7fbb6bc57.zip
Git Hash: Revision: f7fbb6bc573645d69b617228880b2002cdbb60d4

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

[gwenview] [Bug 442103] Gwenview crashes when started by clicking on .png file in Dolphin

2023-11-26 Thread Jim Cunning
https://bugs.kde.org/show_bug.cgi?id=442103

--- Comment #4 from Jim Cunning  ---
I did not retain the file(s) causing the crash behavior, or more
   likely cannot find them now, as my original bug report was more than
   two years ago. If I can find a file that demonstrates the problem, I
   will update the bug report.

   On 11/26/23 06:08, Méven Car wrote:

 https://bugs.kde.org/show_bug.cgi?id=442103  
 Méven Car   [1]  changed:

What|Removed |Added


  CC|| meve...@gmail.com
[1] 
 --- Comment #3 from Méven Car   [1]  ---
 Thread 1 (Thread 0x7f4260141440 (LWP 226577)):
 [KCrash Handler]
 [...]
 #14 0x7f426557c60f in Exiv2::Xmpdatum::write(std::ostream&,
Exiv2::ExifData
 const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27
 #15 0x7f4267a72fd9 in ?? () from
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
 #16 0x7f4267a6ef23 in
 Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from
 /lib/x86_64-linux-gnu/libgwenviewlib.so.5
 #17 0x7f4267a2b470 in
 Gwenview::Document::setExiv2Image(std::unique_ptr >) () from
 /lib/x86_64-linux-gnu/libgwenviewlib.so.5

 [...]

 It seems to be due to the exiv data of the file, could you send the file ?





   1. mailto:meve...@gmail.com

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

[plasmashell] [Bug 477279] New: Plasma crashed at startup when dismissing notification about updates being available

2023-11-20 Thread Jim Winchester
https://bugs.kde.org/show_bug.cgi?id=477279

Bug ID: 477279
   Summary: Plasma crashed at startup when dismissing notification
about updates being available
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: winchester_...@hotmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-11-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Title is self-explanatory and pretty much tells the whole story. 
Initialization seemed to be otherwise finished.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 2299 (plasmashell)
   UID: 1000 (jimbo)
   GID: 100 (users)
Signal: 11 (SEGV)
 Timestamp: Mon 2023-11-20 07:22:19 EST (1min 21s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (jimbo)
   Boot ID: 996940141074452dabf1a1b24ce0a278
Machine ID: 1701a12dde5b4203b603c660b9f49179
  Hostname: xw8200a
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.996940141074452dabf1a1b24ce0a278.2299.170048293900.zst
(present)
  Size on Disk: 20.6M
   Message: Process 2299 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64
Stack trace of thread 2299:
#0  0x7f768b6aec24 __GI___pthread_sigmask (libc.so.6 +
0x8fc24)
#1  0x7f768b65b1b9 __GI___sigprocmask (libc.so.6 + 0x3c1b9)
#2  0x7f768dc0ce9b _ZN6KCrash15setCrashHandlerEPFviE
(libKF5Crash.so.5 + 0x4e9b)
#3  0x7f768dc0db3e _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b3e)
#4  0x7f768b65afd0 __restore_rt (libc.so.6 + 0x3bfd0)
#5  0x7f768d077c86 _ZN5QtQml18qmlExecuteDeferredEP7QObject
(libQt5Qml.so.5 + 0x277c86)
#6  0x7f768d549059
_ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject
(libQt5Quick.so.5 + 0x149059)
#7  0x7f768d53e997
_ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject
(libQt5Quick.so.5 + 0x13e997)
#8  0x7f768badd50d _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x2dd50d)
#9  0x7f768c762fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#10 0x7f768bab16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#11 0x7f768bb08c31 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5 + 0x308c31)
#12 0x7f768bb094c4 n/a (libQt5Core.so.5 + 0x3094c4)
#13 0x7f768a4287a9 g_main_context_dispatch
(libglib-2.0.so.0 + 0x547a9)
#14 0x7f768a428a38 n/a (libglib-2.0.so.0 + 0x54a38)
#15 0x7f768a428acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#16 0x7f768bb09836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#17 0x7f768bab017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#18 0x7f768bab82d6 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2b82d6)
#19 0x55f8023cedc3 n/a (plasmashell + 0x26dc3)
#20 0x7f768b6461ca __libc_start_call_main (libc.so.6 +
0x271ca)
#21 0x7f768b646285 __libc_start_main_impl (libc.so.6 +
0x27285)
#22 0x55f8023ceee1 n/a (plasmashell + 0x26ee1)

Stack trace of thread 2306:
#0  0x7f768a426695 g_source_ref (libglib-2.0.so.0 +
0x52695)
#1  0x7f768a426770 n/a (libglib-2.0.so.0 + 0x52770)
#2  0x7f768a428303 g_main_context_check (libglib-2.0.so.0 +
0x54303)
#3  0x7f768a428958 n/a (libglib-2.0.so.0 + 0x54958)
#4  0x7f768a428acc g_main_context_iteration
(libglib-2.0.so.0 + 

[kdenlive] [Bug 476386] Grayed Out 'Shutdown computer after renderings'

2023-11-10 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=476386

Jim  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|MOVED   |---

--- Comment #2 from Jim  ---
I don't think this is a solution for Windows users.

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

[kdenlive] [Bug 476386] New: Grayed Out 'Shutdown computer after renderings'

2023-10-31 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=476386

Bug ID: 476386
   Summary: Grayed Out 'Shutdown computer after renderings'
Classification: Applications
   Product: kdenlive
   Version: 23.08.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jamesichrist...@hotmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Under 'Rendering' -> 'Job Queue'
2. 
3. 

OBSERVED RESULT
No longer enabled

EXPECTED RESULT
to be able to check box to shutdown the system automatically when rendering is
done.

SOFTWARE/OS VERSIONS
Windows: Windows 11 Pro and Home
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.

[kdenlive] [Bug 476371] Video Resolution and fps change when working on different pc

2023-10-31 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=476371

--- Comment #1 from Jim  ---
Created attachment 162777
  --> https://bugs.kde.org/attachment.cgi?id=162777=edit
Repeating issue with resolution and fps

This is the file I removed to continue loading of project. 

Attempted once again and still same result:
Manage to repeat error by fixing project on NBA moving .kdenlive file to NBB
making some changes and copying back to NBA and have same issue of 1920x1080/30
-> 1832x964/20

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

[kdenlive] [Bug 476371] New: Video Resolution and fps change when working on different pc

2023-10-31 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=476371

Bug ID: 476371
   Summary: Video Resolution and fps change when working on
different pc
Classification: Applications
   Product: kdenlive
   Version: 23.08.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: jamesichrist...@hotmail.com
  Target Milestone: ---

SUMMARY

Created Project on Notebook A (NBA) and did some work on it.
Moved Project to Notebook B (NBB) and did some more work on it.
Finished up work on NBB and moved Project back to NBA.
Project was setup as 1920x1080 30.00fps on NBA
When working on NBB it took it in as the same.
But when reading the *.kdelive file back to NBA it changed it to 1832x964
20.00fps and flagged a point in the file it did not like. 
Removed the flagged area and reloaded still not reading the correct  Res or fps

File header reads:
 

NBA is a HP ZBook Workstation Notebook; NBB is a HP ENVY Notebook. Both are
setup exactly the same drive wise. to be able to do this. NBA has 4k
Capabilities , running 4k on main screen 1080 on two dual monitors, NBB is
running 1080 single display 

NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Repeated several times and different revision of my project file.
2. 
3. 

OBSERVED RESULT
in correct resolution and frame per second

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: NBA is 11 Pro, NBB is 11 Home
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 23.08.1
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 391427] Kdenlive crashes after rendering throwing an error: Missing reference picture

2023-10-17 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=391427

--- Comment #16 from Jim Henderson  ---
kdenlive 23.08.2 on macos Ventura (13.5.2) crashed in rendering. The display in
the error dialog contains "missing reference picture" like this bug report, so
I have added an attachment "log file from render crash kdenlive 23.08.2". The
brief display is:
Rendering of /Users/jim . . . meeting.mp4 crashed

QObject::startTimer: Timers can only be used with threads started with QThread
[h264 @ 0x7fb00089e640] Missing reference picture, default is 2147483647 [h264
@ 0x7fb0008a32c0]
reference picture missing during reorder [h264 @ 0x7fb0008a32c0] Missing
reference picture, default is
2147483647

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

[kdenlive] [Bug 391427] Kdenlive crashes after rendering throwing an error: Missing reference picture

2023-10-17 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=391427

Jim Henderson  changed:

   What|Removed |Added

 CC||j...@sydney.dialix.com.au

--- Comment #15 from Jim Henderson  ---
Created attachment 162386
  --> https://bugs.kde.org/attachment.cgi?id=162386=edit
log file from render crash kdenlive 23.08.2

See my comment in the thread about this render crash.

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

[gwenview] [Bug 452842] create preview of files instantly when the user scrolls through folders with a lot of files

2023-10-02 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452842

--- Comment #1 from Jim Jones  ---
any updates?

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

[kwin] [Bug 475090] ExposeClass method selects the next window class when the window with the current focus is closed and the next window in line is from a different class

2023-10-01 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=475090

--- Comment #1 from Jim Jones  ---
i found a more reproducible way:

1. open 3 terminal windows and one dolphin window
2. focus aka click on the dolphin window
3. click on one of the terminal windows
4. call ExposeClass
5. close the terminal window that got clicked/focused in "3."
6. now the dolphin windows only is shown instead of the 2 still open terminal
instances

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

[kwin] [Bug 475090] New: ExposeClass method selects the next window class when the window with the current focus is closed and the next window in line is from a different class

2023-10-01 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=475090

Bug ID: 475090
   Summary: ExposeClass method selects the next window class when
the window with the current focus is closed and the
next window in line is from a different class
Classification: Plasma
   Product: kwin
   Version: git-stable-Plasma/5.27
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
  Target Milestone: ---

SUMMARY

ExposeClass method selects the next window class when the window with the
current focus is closed and the next window in line is from a different class


STEPS TO REPRODUCE
1. open 3 terminal windows and one dolphin window
2. select terminal (current focus) and call ExposeClass
3. close terminal window
4. if the next window in line is dolphin, ExposeClass switches to dolphin (and
only shows dolphin windows) instead of staying in the konsole window class
until all konsole windows are closed

OBSERVED RESULT
ExposeClass switches to new windows class (if in line) when windows gets closed

EXPECTED RESULT
ExposeClass stays in the same class until all open window class windows are
closed

SOFTWARE/OS VERSIONS
Operating System: Linux
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.5 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 38.8 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 461862] KDE daemon crashes

2023-08-22 Thread Jim James
https://bugs.kde.org/show_bug.cgi?id=461862

Jim James  changed:

   What|Removed |Added

 CC||kdeb...@jimjam.es

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

[kdeconnect] [Bug 461862] KDE daemon crashes

2023-08-22 Thread Jim James
https://bugs.kde.org/show_bug.cgi?id=461862

--- Comment #1 from Jim James  ---
Created attachment 161128
  --> https://bugs.kde.org/attachment.cgi?id=161128=edit
New crash information added by DrKonqi

kdeconnectd (23.04.3) using Qt 5.15.10

KDE Connect crashes upon disconnecting my bluetooth headphones from the system.

-- Backtrace (Reduced):
#4  0x7f9ba07a8e17 in PulseAudioQt::CardPrivate::update(pa_card_info
const*) () from /lib64/libKF5PulseAudioQt.so.3
#5  0x7f9ba0662d8f in context_get_card_info_callback () from
/lib64/libpulse.so.0
#6  0x7f9ba05fb5d8 in run_action () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#7  0x7f9ba05ffbcc in pa_pdispatch_run () from
/usr/lib64/pulseaudio/libpulsecommon-16.1.so
#8  0x7f9ba06511ab in pstream_packet_callback () from /lib64/libpulse.so.0

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

[kdenlive] [Bug 471551] Rendering crashed. Could not update timestamps for skipped samples.

2023-07-02 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471551

--- Comment #4 from Jim Henderson  ---
I run a Windows 10 compter in a virtual machine on my Mac (Host on the Mac is
VirtualBox Version 7.0.8 r156879 (Qt5.15.2)). The folder on the Mac where my
kdenlive project is located is shared to the client machine, where it appears
as drive letter P:.
I installed the latest Windows version of kdenlive on the virtual machine
(23.04.2) and opened the project file. The program remade the proxy files and I
started Rendering to an MP4 file.
It ran more slowly than on the Mac, probably because the virtual machine is not
given as many resources as the Mac has (eg. memory and processors) but it ran
fully to completion without any crash :-)

So it seems the problem is in the Mac version of kdenlive, or with how it
interacts with the Mac function calls.
Still hoping you developers, so generous with your time, can have some ideas
for fixing this problem in the Mac version of kdenlive.

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

[kdenlive] [Bug 467262] Effect names, letters missing

2023-06-29 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467262

Jim Henderson  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from Jim Henderson  ---
Thanks developers, we can close this issue now.

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

[kdenlive] [Bug 467262] Effect names, letters missing

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467262

--- Comment #4 from Jim Henderson  ---
(In reply to HymanZXC from comment #1)
> Created attachment 157759 [details]
> broken timeline and footages with missing letters in timestamps and titles
> 
> Not only is the Effect tab showing missing letters. The timeline (and
> several other places I can't remember) also lacks letters. This happens with
> the AppImage version running on Fedora 36. However, the UI of the Flatpak
> version is fine.

Hi HymanZXC -- has any recent update resolved this issue for you? I have just
added a comment that the display is now good for me, with new versions of
kdenlive and the macos OS. Jim Henderson

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

[kdenlive] [Bug 467262] Effect names, letters missing

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467262

--- Comment #3 from Jim Henderson  ---
I am now using the latest normal release, 23.04.2, on an updated macos OS,
Ventura 13.4.1, and the problem has gone away. Thanks Apple, or thanks kdenlive
developers :-)

@HymanZXC, has an update resolved the issue for you?

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

[kdenlive] [Bug 471555] Preview not playing, hangs

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471555

--- Comment #1 from Jim Henderson  ---
Created attachment 159966
  --> https://bugs.kde.org/attachment.cgi?id=159966=edit
Report that goes to Apple after a Force-quit

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

[kdenlive] [Bug 471555] New: Preview not playing, hangs

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471555

Bug ID: 471555
   Summary: Preview not playing, hangs
Classification: Applications
   Product: kdenlive
   Version: 23.04.2
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Keywords: usability
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Editing videos of a speaker, with slides, nearly an hour, many cuts, using
transform and alpha mask effects.
2. When I go away to do other things and come back, quite often the preview
won't play. (The play icon changes to the pause icon, but the video preview
doesn't play.)
3. Open the Kdenlive menu and select Quit Kdenlive.

OBSERVED RESULT
Program doesn't quit, and after a short time the cursor changes to Waiting
circle going round and round.
I can open Application Manager, select kdenlive (which is shown as Not
Responding) and Force Quit. I'll attach a file of the report that goes to Apple

EXPECTED RESULT
The video should play in the Preview window pane, and when I try to quit the
application it should quit.

SOFTWARE/OS VERSIONS
macOS: Ventura 13.4.1

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 471551] Rendering crashed. Could not update timestamps for skipped samples.

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471551

--- Comment #3 from Jim Henderson  ---
Created attachment 159965
  --> https://bugs.kde.org/attachment.cgi?id=159965=edit
log of render crash after reinstall

I removed the previous versions of kdenlive and installed the latest. This time
the render job crashed much earlier.

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

[kdenlive] [Bug 471551] Rendering crashed. Could not update timestamps for skipped samples.

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471551

Jim Henderson  changed:

   What|Removed |Added

 CC||j...@sydney.dialix.com.au

--- Comment #2 from Jim Henderson  ---
Created attachment 159964
  --> https://bugs.kde.org/attachment.cgi?id=159964=edit
crash log before I reinstalled kdenlive

This crash happened when I was using kdenlive that had been installed over the
previous version.

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

[kdenlive] [Bug 471551] Rendering crashed. Could not update timestamps for skipped samples.

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471551

--- Comment #1 from Jim Henderson  ---
I read somewhere that this problem was fixed on a Windows machine by completely
removing the previous version of kdenlive and reinstalling, so I did the same.
Then I tried to render just the first part of the project, and the crash
happened much sooner. I'll try to upload two log files, named with before and
after the reinstall.

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

[kdenlive] [Bug 471551] New: Rendering crashed. Could not update timestamps for skipped samples.

2023-06-28 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=471551

Bug ID: 471551
   Summary: Rendering crashed. Could not update timestamps for
skipped samples.
Classification: Applications
   Product: kdenlive
   Version: 23.04.2
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Make a video using audio preprocessed by Audacity.
2. Render to MP4
3. Rendering crashes with message: [mp3float @ 0x7faa8fe45f80] Could not update
timestamps for skipped samples.

OBSERVED RESULT
Rendering crashes with message: [mp3float @ 0x7faa8fe45f80] Could not update
timestamps for skipped samples.

EXPECTED RESULT
a nicely rendered MP4 file

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

ADDITIONAL INFORMATION
An online search for "Could not update timestamps for skipped samples."
produced these hits:
https://github.com/angelcam/rust-ac-ffmpeg/issues/30
kdenlive bugs 451508 and 447854

Hoping one of you generous developers can find a solution

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

[Discover] [Bug 470910] Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-direc

2023-06-11 Thread Jim Maguire
https://bugs.kde.org/show_bug.cgi?id=470910

--- Comment #6 from Jim Maguire  ---
(In reply to Nicolas Fella from comment #1)
> "no metadata URIs for vendor-directory" and "could not open
> appstream://org.kde.kdeconnect.app" are entirely unrelated. For the former
> see https://bugs.kde.org/show_bug.cgi?id=462931

Ok so I followed that thread to it's conclusion and removing the check in the
vendor directory checkbox does prevent the issue occurring, however (and this
is an arch newbie question) does that not limit the content that discover can
now provide me? 

if no, then I'm happy this is resolved. If yes then it's not really a perfect
solution. Just curious

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

[Discover] [Bug 470910] Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-direc

2023-06-11 Thread Jim Maguire
https://bugs.kde.org/show_bug.cgi?id=470910

--- Comment #5 from Jim Maguire  ---
Hey guys, 

thank you for chipping in on this.
A-lot of googling and experimenting later I've managed to resolve this
partially.

by default KDE Plasma on Arch Linux doesn't install packagekit-qt5 or
appstream-qt it seems. So I manually installed both and the list of
applications available in discover is now listed. Outside of that I still get
the meta data error however if I close it now I can access the stuff in the
list and install KDE Connect. I haven't set it up and used it yet but it does
install.

in answer to your statement Nicolas that it was weird it opened at all. The
welcoming wizard actually points you to it and says you can use KDE Connect
etc, etc... so I presume it's actually meant to be there?? I'm not sure, that's
just conjecture but it's odd they'd mention it and it not be there. 

Anyway I have it working for now, but I would like to find a resolution to the
popup message re: metadata and to remove that if you guys have ideas?

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

[Discover] [Bug 470910] New: Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-

2023-06-11 Thread Jim Maguire
https://bugs.kde.org/show_bug.cgi?id=470910

Bug ID: 470910
   Summary: Trying to open applications or get applications
through discover or even other applications outside of
Discover, all come up with the error: "no metadata
URIs for vendor-directory"
Classification: Applications
   Product: Discover
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: neodreadl...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Search KDE Connect in the start menu
2. Select GET KDE CONNECT

Separately try downloading and installing PyCharm, When finished the pkg
install in terminal, go to the start menu to run the installed application.
Same error

OBSERVED RESULT

When trying to run either of the above, I receive a pop up error stating "no
metadata URIs for vendor-directory"
behind this when I click off the error, within the Discover application I see
the following:

could not open appstream://org.kde.kdeconnect.app  because it was not found in
any available software repositories.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
KDE Plasma: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.7-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 425271] XembedSNIProxy causes "high" cpu usage with certain screen arrangements

2023-05-20 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=425271

Jim  changed:

   What|Removed |Added

 CC||hardlo...@gmx.de

--- Comment #53 from Jim  ---
This is probably caused by the fix to
https://bugs.kde.org/show_bug.cgi?id=357443.

There's this bit in fdoselectionmanager.cpp

> else if (responseType == XCB_VISIBILITY_NOTIFY) {
>   const auto event = reinterpret_cast *>(ev);
>// it's possible that something showed our container window, we have 
> to hide it
>// workaround for BUG 357443: when KWin is restarted, container window 
> is shown on top
>if (event->state == XCB_VISIBILITY_UNOBSCURED) {
>for (auto sniProxy : m_proxies.values()) {
>sniProxy->hideContainerWindow(event->window);
>}
>}
>}

Where does the XCB_VISIBILITY_UNOBSCURED event originate? Is it a bug that a
window is reported as unobscured if it's located on an offscreen position? Or
is it the responsibility of the client to check if the window is unobscured and
on-screen?

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

[kdenlive] [Bug 469944] File--Save As crashes without saving after a source image is changed

2023-05-18 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=469944

--- Comment #2 from Jim Henderson  ---
Created attachment 159075
  --> https://bugs.kde.org/attachment.cgi?id=159075=edit
The tag that mentioned the image that I had changed, "Slide15"

After I removed that section of the newest .kdenlive file, I was able to load
the project and save it with a new name.

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

[kdenlive] [Bug 469944] File--Save As crashes without saving after a source image is changed

2023-05-18 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=469944

Jim Henderson  changed:

   What|Removed |Added

 CC||j...@sydney.dialix.com.au

--- Comment #1 from Jim Henderson  ---
Created attachment 159073
  --> https://bugs.kde.org/attachment.cgi?id=159073=edit
crash report sent to Apple. See highlighted "CRASH GUARD"

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

[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves

2023-05-18 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467114

Jim Henderson  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=469944

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

[kdenlive] [Bug 469944] New: File--Save As crashes without saving after a source image is changed

2023-05-18 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=469944

Bug ID: 469944
   Summary: File--Save As crashes without saving after a source
image is changed
Classification: Applications
   Product: kdenlive
   Version: 23.04.1
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Keywords: usability
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---
 Flags: timeline_corruption-

Created attachment 159071
  --> https://bugs.kde.org/attachment.cgi?id=159071=edit
Screenshot of dialog for approval to import the new image

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
That site says this doesn't work for Macs

STEPS TO REPRODUCE
1. Add videos and still images, saving the project XML file after each one,
successfuly.
2. Notice that one of the images is inadequate.
3. Save the project and close kdenlive.
4. Replace the image with a better one, in the same folder and with the same
filename.
5. Start kdenlive and load the .kdenlive file. Approve importing again the new
version of the image. (see screenshot)
6. Do some more editing.
7. Do File->Save As with a new name.

OBSERVED RESULT
Program crashes with error report to Apple. (see uploaded file) Project is not
saved.

EXPECTED RESULT
I expected the program to save the project in the .kdenlive file and let me
continue working.

SOFTWARE/OS VERSIONS
Windows: 
macOS:  Ventura 13.3.1 (a) (Intel)
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The crash information highlights STACK GUARD, so it seems something was trying
to access memory that it shouldn't.
I edited the latest-saved .kdenlive file and deleted the tag that gave the
details of the image that I had changed. I'll upload what I deleted.
I then reloaded that project file and I can now save the project again.

I reported similar behaviour at https://bugs.kde.org/show_bug.cgi?id=467114

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

[digikam] [Bug 469595] New: digikam 8.0.0 from fedora repository and also local build crash on startup

2023-05-10 Thread Jim Shipman
https://bugs.kde.org/show_bug.cgi?id=469595

Bug ID: 469595
   Summary: digikam 8.0.0 from fedora repository and also local
build crash on startup
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Bundle-Tarball
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jims...@sbcglobal.net
  Target Milestone: ---

SUMMARY
Back trace starting just before the crash:

digikam.widgets: Paths to color scheme :  ("/usr/share/digikam/colorschemes")
digikam.widgets: ""  ::  ""
digikam.widgets: ""  ::  ""
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
0x00020032 in ?? ()
Missing separate debuginfos, use: dnf debuginfo-install
xorg-x11-drv-nvidia-libs-530.41.03-1.fc38.x86_64
(gdb) bt
#0  0x00020032 in  ()
#1  0x75ce16cb in
Digikam::DPluginLoader::registerGenericPlugins(QObject*)
(this=0x768b8250 , parent=0x10575f0)
at
/home/shipman/dk/digikam-8.0.0/core/libs/dplugins/setup/dpluginloader.cpp:288
#2  0x75e79bdd in Digikam::DXmlGuiWindow::registerPluginsActions()
(this=0x10575f0)
at
/home/shipman/dk/digikam-8.0.0/core/libs/widgets/mainview/dxmlguiwindow_actions.cpp:25
#3  0x775c61c5 in Digikam::DigikamApp::setupActions() (this=0x10575f0)
at /home/shipman/dk/digikam-8.0.0/core/app/main/digikamapp_setup.cpp:859
#4  0x775a5d72 in Digikam::DigikamApp::DigikamApp() (this=0x10575f0,
__in_chrg=, __vtt_parm=)
at /home/shipman/dk/digikam-8.0.0/core/app/main/digikamapp.cpp:144
#5  0x004066b4 in main(int, char**) (argc=1, argv=0x7fffda18) at
/home/shipman/dk/digikam-8.0.0/core/app/main/main.cpp:409
(gdb) 


STEPS TO REPRODUCE
1. Start digikam

OBSERVED RESULT
core dump

EXPECTED RESULT
digikam should start up

SOFTWARE/OS VERSIONS
Linux laurie.family.net 6.2.14-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon May 
1 00:55:28 UTC 2023 x86_64 GNU/Linux

Linux/Gnome

KDE Plasma Version: 
Gnome desktop

KDE Frameworks Version: 
5.105.0 (determined by running k3b)

Qt Version:  
[root@laurie shipman]# qmake --version
QMake version 3.1
Using Qt version 6.5.0 in /usr/lib64
[root@laurie shipman]# qmake-qt5 --version
QMake version 3.1
Using Qt version 5.15.9 in /usr/lib64

dnf Installed Packages
Name : qt
Epoch: 1
Version  : 4.8.7
Release  : 71.fc38
Architecture : x86_64
Size : 18 M
Source   : qt-4.8.7-71.fc38.src.rpm
Repository   : @System
>From repo: fedora

ADDITIONAL INFORMATION
Gnome desktop with x-windows system and nvidea (530.41.02) drivers.
digikam version 7.10 works perfectly both local build and dnf installed.
digikam 8.0.0 appimage also works Ok

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

[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read

2023-04-26 Thread Jim Ladino
https://bugs.kde.org/show_bug.cgi?id=468936

Jim Ladino  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from Jim Ladino  ---
(In reply to Jack from comment #3)
> That seems truncated - I usually see a lot longer output.  Is a data file
> open?
> Also - what distribution are you using, and do the Views other than Home and
> Reports look OK or not?

Hi Jack.  

I'm not sure why my last response got lost or something.  Thanks for looking at
my output file.
I am using linux on a distribution called PCLinuxOS - Kernel (6.1.20-pclos1)
2023.  The output file I sent in was from opening KmyMoney from the console. 
It opens right into my datafile.  Is there a log file I can send you for
further information?

All other screens appear to be working correctly.  It's just the Home Screen
and the Reports that are having this problem.

Please let me know what further information I can provide.  Thank you.
Jim Ladino

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

[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read

2023-04-25 Thread Jim Ladino
https://bugs.kde.org/show_bug.cgi?id=468936

--- Comment #2 from Jim Ladino  ---
Created attachment 158425
  --> https://bugs.kde.org/attachment.cgi?id=158425=edit
Output from Console when starting KMyMoney

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

[kmymoney] [Bug 468936] New: Home Page and Reports display completely black - Cannot Read

2023-04-24 Thread Jim Ladino
https://bugs.kde.org/show_bug.cgi?id=468936

Bug ID: 468936
   Summary: Home Page and Reports display completely black -
Cannot Read
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: jlst...@verizon.net
  Target Milestone: ---

Created attachment 158408
  --> https://bugs.kde.org/attachment.cgi?id=158408=edit
Screen Shots of Black Pages

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Since an upgrade, when I open Kmymoney Home Page or when I run a report, the
display is completely blackened out

STEPS TO REPRODUCE
1. Choose the "Home" Icon to go to home page
2. Section under the "KmyMoney" Title Bar is black - nothing can be seen.
3. For Reports:  Access "Reports" Icon
4. Select Report to run and run it by double-clicking on the report name
5. The report comes up with a black page with action buttons on the top.  (It
is possible to export the report and read it in another program such as Libre
Calc.)
OBSERVED RESULT
Black Screen

EXPECTED RESULT
Home Page:  Expect to see the Home Screen with account balances, etc
Reports:  Expect to see the produced report.

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.

[kio-extras] [Bug 325574] Unable to modify file on Android device using kio-mtp

2023-04-10 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=325574

Jim Jones  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #19 from Jim Jones  ---
i applied the patch on 22.12.3 and it's still not possible to move files
between folders, as i get the following error before the operation would
finish:

"Changing the attributes of files is not supported with protocol mtp."

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

[kdenlive] [Bug 467262] New: Effect names, letters missing

2023-03-12 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467262

Bug ID: 467262
   Summary: Effect names, letters missing
Classification: Applications
   Product: kdenlive
   Version: git-master
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

Created attachment 157226
  --> https://bugs.kde.org/attachment.cgi?id=157226=edit
Screenshot showing incorrect names for Effects

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open the Effects pane
2. Notice strange display of the names of effects
3. 

OBSERVED RESULT
In the names of effects, some letters are replaced by spaces, as in the
screenshot that I uploaded.

EXPECTED RESULT
Effect names would appear properly, as in the Stable release.

SOFTWARE/OS VERSIONS
macOS: Ventura 13.2.1

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves

2023-03-09 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467114

Jim Henderson  changed:

   What|Removed |Added

URL|http://@4iron   |http://

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

[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves

2023-03-09 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467114

Jim Henderson  changed:

   What|Removed |Added

 CC||j...@sydney.dialix.com.au

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

[kdenlive] [Bug 467114] New: kdenlive crashes on File->Save As after some successful saves

2023-03-09 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=467114

Bug ID: 467114
   Summary: kdenlive crashes on File->Save As after some
successful saves
Classification: Applications
   Product: kdenlive
   Version: git-master
  Platform: macOS (DMG)
   URL: http://@4iron
OS: macOS
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

Created attachment 157145
  --> https://bugs.kde.org/attachment.cgi?id=157145=edit
error details from kdenlive crash on Save As

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Sorry, that link says it is not relevant to Mac computers.

STEPS TO REPRODUCE
1. Start a new project, basing details on first clip imported, accepting
suggested transcode. 16x9 ratio, variable framerate transcoded to 30 fps.
2. Add another video clip, accepting suggested transcode.
3. Do File->Save As and successfully save a .kdenlive file.
4. Drag the first clip to the timeline.
5. Replace the audio of that clip with an improved version made with Audacity.
6. Insert an image as a background video track below the main image, so the
main image can be transformed and moved partly off the screen without leaving a
slice of black.
7. Add a 3x4 image in a video track above the main track, transform it to move
it to the left margin. This leaves the speaker on the right-hand side of the
screen, and the slide she is talking about covering most of the screen.
8. Stretch the image to cover the duration of the talk about the image in the
main track.
9. Transform the main track to move it left and right as the speaker moves a
bit, to keep her on the right-hand side of the screen and not obscured by the
slide she is talking about.
10. Do File->Save As to a modified filename in the same folder as the video
clips. Successful save.
11. Repeat steps 7 to 10 several times, copying the transform effect from an
old image to the new image each time. Save As works properly.
12. Do File->Save As and the program crashes, displaying a lot of details that
it says will be sent to Apple. I'll attach a file of those.


OBSERVED RESULT

When the program crashes, the file I was trying to save is not written.
When I relaunch the program and load the last-saved .kdenlive file, it offers
to recover unsaved changes.
For some images, the program reports an error dialog when I import the image,
and the detail is that the image is too small to make a proxy file. (Setting
was for 700 px.) Version 22 of kdenlive just said it was unable to make a proxy
file from that image.
I changed the default settings and the settings for the project so that it did
not try to make proxies for any images, and after a crash this change was
remembered.

EXPECTED RESULT
File->Save As would work properly as has been the case for several videos I
have made with earlier versions on my Mac

SOFTWARE/OS VERSIONS
macOS:  Ventura 13.2.1

ADDITIONAL INFORMATION
kdenlive version is the nightly build from 
https://binary-factory.kde.org/job/Kdenlive_Nightly_macos/
Number 1410 of 2023-03-09. 
I moved to this version because the normal stable release, 22.12.1, was
crashing the same way.
I have attached the debug information that I could find, and have uploaded the
.kdenlive files that I was able to save to a folder in Google Drive, along with
a rendering of the video, so you can see what the transform effects do. Here's
the link:
https://drive.google.com/drive/folders/1ibi-iRBUtBnS_wRr7Ro1SzHF27p6QVWR?usp=sharing

There is a bug report that seems similar at
https://bugs.kde.org/show_bug.cgi?id=466561
In that one, 4ironm...@gmail.com changed the save location, which I did not do.

I hope someone can suggest some work-around for me, and the developers, so
generous with their time, can work out what is going wrong and fix it :-)
(Thanks, developers, for a wonderful program!)

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

[gwenview] [Bug 463586] drag and drop files from gwenview into a folder in dolphin is broken (only works the first time)

2023-01-18 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

--- Comment #9 from Jim Jones  ---
reverting the commit b6e8d6a9786937602e76d3ed26ca2ba4043b2336 fixes the bug for
me too

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

[gwenview] [Bug 463586] drag and drop files from gwenview into a folder in dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

--- Comment #5 from Jim Jones  ---
the bug also happens when copying files between two gwenview windows.

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

[gwenview] [Bug 463586] drag and drop files from gwenview into a folder in dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

Summary|drag and drop from gwenview |drag and drop files from
   |to dolphin is broken (only  |gwenview into a folder in
   |works the first time)   |dolphin is broken (only
   ||works the first time)

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

[gwenview] [Bug 463586] drag and drop from gwenview to dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

Summary|drag and drop from gwenview |drag and drop from gwenview
   |into dolphin is broken  |to dolphin is broken (only
   |(only works the first time) |works the first time)

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

[gwenview] [Bug 463586] drag and drop from gwenview into dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

  Component|general |general
Product|dolphin |gwenview

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

[dolphin] [Bug 463586] drag and drop from gwenview into dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

  Component|general |general
 CC||kfm-de...@kde.org
Product|gwenview|dolphin

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

[gwenview] [Bug 463586] drag and drop from gwenview into dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

--- Comment #2 from Jim Jones  ---
Better way to reproduce, show the bug:

STEPS TO REPRODUCE
1. drag multiple files (A) from gwenview into a folder in dolphin (it works)
2. drag file (B) from gwenview into a folder in dolphin (it tries to
copy/overwrite the files (A) selected in step (1.) again, although only one
file (B) is dragged)

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

[gwenview] [Bug 463586] drag and drop from gwenview into dolphin is broken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

Summary|drag and drop from gwenview |drag and drop from gwenview
   |is borken (only works the   |into dolphin is broken
   |first time) |(only works the first time)

--- Comment #1 from Jim Jones  ---
dragging files into other apps like konsole seems normally.

Restarting dolphin fixes the problem and it works one time again (so it could
be that the problem is also dolpin related)

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

[gwenview] [Bug 463586] drag and drop from gwenview is borken (only works the first time)

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Jim Jones  changed:

   What|Removed |Added

Summary|drag and drop from gwenview |drag and drop from gwenview
   |is borken   |is borken (only works the
   ||first time)

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

[gwenview] [Bug 463586] New: drag and drop from gwenview is borken

2022-12-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=463586

Bug ID: 463586
   Summary: drag and drop from gwenview is borken
Classification: Applications
   Product: gwenview
   Version: 22.12.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
  Target Milestone: ---

SUMMARY
Drag and drop operation from qenview into dolphin is broken, it works for the
first time, but doing it a second time with different files, always tries to
copy the files from the first drap and drop operation

STEPS TO REPRODUCE
1. drag file A from gwenview into a folder in dolphin (it works)
2. drag file B from gwenview into a folder in dolphin (it tries to copy the
file A again, although file B is dragged)

OBSERVED RESULT
tries to copy the file A from the first drag operation,when doing a second
opeartion with file B

EXPECTED RESULT
file B gets copied

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Graphics Platform: X11

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

[kalendar] [Bug 460640] Kalendar crash on 1/3 days button push

2022-12-02 Thread Jim James
https://bugs.kde.org/show_bug.cgi?id=460640

--- Comment #1 from Jim James  ---
Created attachment 154259
  --> https://bugs.kde.org/attachment.cgi?id=154259=edit
New crash information added by DrKonqi

kalendar (22.08.3) using Qt 5.15.7

Seemingly randomly, Kalendar crashes at launch. This occurs both when Kalendar
is launched via the kalendar command and when it is opened via kickoff.

-- Backtrace (Reduced):
#5  0x7fe137290c7c in
QQuickItemPrivate::removeItemChangeListener(QQuickItemChangeListener*,
QFlags) () from /lib64/libQt5Quick.so.5
#6  0x7fe13416dc5b in
QQuickScrollBarAttachedPrivate::setFlickable(QQuickFlickable*) () from
/lib64/libQt5QuickTemplates2.so.5
#7  0x7fe13416def1 in QQuickScrollBarAttached::~QQuickScrollBarAttached()
() from /lib64/libQt5QuickTemplates2.so.5
#8  0x7fe13416df0d in QQuickScrollBarAttached::~QQuickScrollBarAttached()
() from /lib64/libQt5QuickTemplates2.so.5
#9  0x7fe1356d164a in QObjectPrivate::deleteChildren() () from
/lib64/libQt5Core.so.5

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

[kalendar] [Bug 460640] Kalendar crash on 1/3 days button push

2022-12-02 Thread Jim James
https://bugs.kde.org/show_bug.cgi?id=460640

Jim James  changed:

   What|Removed |Added

 CC||kdeb...@jimjam.es

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

[kde-windows] [Bug 396804] Cannot load any of the sample puzzles

2022-11-29 Thread Jim Miller
https://bugs.kde.org/show_bug.cgi?id=396804

--- Comment #2 from Jim Miller  ---
HI,

The problem has disapeared.  I use Linex all the time.  I get updates to it
almost everyday.  I suspect some bug in an update since it suddenly
appeared and recently disappered.  Thanks.

Jim

On Tue, Nov 29, 2022 at 12:06 AM Justin Zobel 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=396804
>
> Justin Zobel  changed:
>
>What|Removed |Added
>
> 
>  Status|REPORTED|NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>
> --- Comment #1 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 reported the bug.

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

[korganizer] [Bug 460569] KOrganizer crashed on creating a new task

2022-11-02 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=460569

Jim  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REOPENED
 Ever confirmed|0   |1

--- Comment #4 from Jim  ---
see my other comment for info

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

[krusader] [Bug 409725] Krusader crashed after starting Disk Usage

2022-10-30 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=409725

--- Comment #5 from Jim  ---
I don't have access to the original system that had the issue any more.

I have installed Krusader on two other systems and it seems to be working
properly.

On Sat, Oct 29, 2022 at 7:40 PM Justin Zobel 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=409725
>
> Justin Zobel  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #4 from Justin Zobel  ---
> Thank you for reporting this crash 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 crash 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 reported the bug.

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

[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered

2022-10-26 Thread Jim Kuhn
https://bugs.kde.org/show_bug.cgi?id=458212

--- Comment #5 from Jim Kuhn  ---
> Is using %p in the filename a satisfactory workaround?

That's probably fine for cases where the multiple xml files can be easily
post-processed, but I suspect there are a lot of consumers of this data that
expect it to be in one file (Jenkins plugins, for one).

Perhaps both options could be provided (legacy [single-file] and new
[multi-file]) with a push to getting downstream consumers to use the new
multi-file output.

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

[korganizer] [Bug 460569] KOrganizer crashed on creating a new task

2022-10-18 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=460569

--- Comment #2 from Jim  ---
(In reply to gjditchfield from comment #1)
> Can you install debugging symbols, to get line numbers where the crash
> happens?
> 
> Does KOrganizer print anything useful to stderr when it crashes?
> 
> Is Akonadi running?
> 
> What calendar did you create the event in?
> 
> If you launch akonadiconsole, does it show the events?

Alright, I'll build korganizer w/ debug symbols once I have some spare time.
Weirdly enough, this crash only happens if I launch KOrganizer through the
plasma application launcher (which provides a single parameter "%U"). If I
start KOrganizer from the console, it works perfectly fine (although previously
created repeating events through CalDAV still don't show up)

Akonadi is running. I created the event in a Nextcloud calendar which syncs
through the WebDAV resource feature to KOrganizer. The events are nowhere to be
found in akonaid console, and they don't sync w/ nextcloud's web-based
calendar.

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

[korganizer] [Bug 460569] New: KOrganizer crashed on creating a new task

2022-10-17 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=460569

Bug ID: 460569
   Summary: KOrganizer crashed on creating a new task
Classification: Applications
   Product: korganizer
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: compos...@compositr.dev
  Target Milestone: ---

Application: korganizer (5.21.2 (22.08.2))

Qt Version: 5.15.6
Frameworks Version: 5.99.0
Operating System: Linux 5.19.13-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.26.0 [KCrashBackend]

-- Information about the crash:
KOrganizer refuses to create a repeating event and crashes when creating a
repeating event.
If I create a repeating event in another app and sync it with KOrganizer
through CalDAV, the event does not show up, and I am unable to create
subsequent events without it crashing.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault

[KCrash Handler]
#4  0x7fe0c5148aaf in ?? () from /usr/lib/libKF5AkonadiCalendar.so.5
#5  0x7fe0c5149c77 in ?? () from /usr/lib/libKF5AkonadiCalendar.so.5
#6  0x7fe0c5d8a520 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7fe0c67dab1c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#8  0x7fe0c5d66b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#9  0x7fe0c5d67693 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#10 0x7fe0c5dad728 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x7fe0c35ad81b in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#12 0x7fe0c3603ec9 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x7fe0c35ac0d2 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#14 0x7fe0c5db150c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#15 0x7fe0c5d5f32c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#16 0x7fe0c5d69e59 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#17 0x55c218d42be8 in ?? ()
#18 0x7fe0c56bd290 in ?? () from /usr/lib/libc.so.6
#19 0x7fe0c56bd34a in __libc_start_main () from /usr/lib/libc.so.6
#20 0x55c218d43065 in ?? ()
[Inferior 1 (process 1988820) detached]

Reported using DrKonqi

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

[kdenlive] [Bug 459684] New: Transcode options hard to understand in clip import

2022-09-25 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=459684

Bug ID: 459684
   Summary: Transcode options hard to understand in clip import
Classification: Applications
   Product: kdenlive
   Version: 22.08.1
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

Created attachment 152427
  --> https://bugs.kde.org/attachment.cgi?id=152427=edit
kdenlive import transcode options

SUMMARY
***
I love kdenlive, and I am so grateful to the developers giving their time, but
I find the transcode options hard to understand. (This is when I click Project
and select Add Clip or Folder).

STEPS TO REPRODUCE
1. Take a video on a mobile phone that saves it with variable frame rate. Copy
the clip to the computer.
2. Start kdenlive, click Project and select Add Clip or Folder. The Transcode
dialog pops up, because we can't edit clips with variable frame rate.
3. Open the drop-down list of transcode Options.

OBSERVED RESULT
The first 3 options are easy to understand, but the last 4 I found confusing:
1. Lossy x264 I frame only
2. Lossy x264 I frame only (NVidia GPU Video only)
3. Lossy x264 I frame only (NVidia GPU)
4. Lossy x264 I frame only (Video only)
I looked in the documentation for help, but couldn't find any. I hope someone
can find time to provide help there.
The "I frame only" looked like a vertical bar separating the option into two
parts. I didn't want to get only frames -- I wanted to get the audio as well. I
asked for help in the Forum
(https://forum.kde.org/viewtopic.php?f=265=176125=458018#p458018), and
@bartoloni pointed me to a description of "i-frame" compression. I can now see
that this refers to "i-frames only", not B-frames or P-frames. 

Here are some ways I could misunderstand these options:
1. Lossy x264 I frame only # ie. video frames only, no
audio
2. Lossy x264 I frame only (NVidia GPU Video only) # Only videos made on a
machine with an NVideo GPU or for processing only on a machine with an NVidia
GPU 
3. Lossy x264 I frame only (NVidia GPU) # Only videos made on a machine with an
NVideo GPU or for processing only on a machine with an NVidia GPU
4. Lossy x264 I frame only (Video only)

Since all 4 options only support "i-frame" compression, could we leave that bit
out, and have a note in the dialog that kdenlive wants to make the new x264
video with "i-frame" compression, not "B-frame" nor "P-frame". Then there would
be less to read in each option.

If the NVidia GPU refers to the machine on which the editing will be done,
could there be a checkbox for that instead of two options containing "NVidia
GPU"? (It is easier to put an explanatory comment beside a checkbox than in an
option in a drop-down list.) 

Similarly, if the GPU option refers to the machine on which the video we are
importing was made, again I think a checkbox would be better. (But how would
the user know what machine the clip was made on?)

Finally, if "Video only" means that the transcode should drop the audio, I
think it would be easier to understand if there were a checkbox labelled
"Remove audio from output".

DESIRED RESULT
Taking a few guesses at what these options actually mean, I would find
something like this easier to understand:
=
The following clips are not usable for editing. This will transcode them in an
edit-friendly format and replace the original ones in your project.
Note: the "x264" options will produce compressed files for us to edit, with
some loss of video quality, using "i-frame" compression. (B-frame and P-frame
are not available. For more information, see
https://en.wikipedia.org/wiki/Video_compression_picture_types)


[ ] The transcoded video will be processed on a machine with an NVidia GPU (if
that's what the option means :-)
[ ] Output video only, not audio

AAC (output audio only)
Intermediate DNxHR HQ (Large files)
Lossless (Huge files)
Lossy x264 compressed video (Small files)
=

SOFTWARE/OS VERSIONS
Windows: 
macOS: Big Sur (11.7)
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

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

[dolphin] [Bug 459598] New: clicking with the mouse in an unfocused window shouldn't trigger an action aka open a file/folder

2022-09-24 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=459598

Bug ID: 459598
   Summary: clicking with the mouse in an unfocused window
shouldn't trigger an action aka open a file/folder
Classification: Applications
   Product: dolphin
   Version: 22.08.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***
clicking with the mouse in an unfocused window shouldn't trigger an action aka
open a file/folder

STEPS TO REPRODUCE
1. open 2 dolphin instances A + B
2. give focus to dolphin instance A
3. click on a file/folder in instance B
4. file/folder gets opened

OBSERVED RESULT
the file/folder gets opened in the previously unfocused window

EXPECTED RESULT
the window without focus gets selection, at best the file/folder gets selected
(if there is one below the mouse pointer)

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.8
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Kernel Version: 5.19.11 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

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

[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered

2022-08-30 Thread Jim Kuhn
https://bugs.kde.org/show_bug.cgi?id=458212

--- Comment #2 from Jim Kuhn  ---

(In reply to Paul Floyd from comment #1)
[...]
> Can you provide a small testcase to reproduce?

#include 
#include 

int main(int argc, char** argv) {
  if (!fork()) {
abort();
  }
  malloc(10); // something for memcheck
}

$ valgrind --trace-children=yes --xml=yes --xml-file=test.memcheck ./a.out
$ grep valgrindoutput test.memcheck



```

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

[valgrind] [Bug 458212] Bad XML produced when a fatal_signal is encountered

2022-08-23 Thread Jim Kuhn
https://bugs.kde.org/show_bug.cgi?id=458212

Jim Kuhn  changed:

   What|Removed |Added

 OS|Other   |Linux
   Platform|Other   |Compiled Sources

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

[valgrind] [Bug 458212] New: Bad XML produced when a fatal_signal is encountered

2022-08-23 Thread Jim Kuhn
https://bugs.kde.org/show_bug.cgi?id=458212

Bug ID: 458212
   Summary: Bad XML produced when a fatal_signal is encountered
   Product: valgrind
   Version: 3.19.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: jim.k...@gmail.com
  Target Milestone: ---

When running valgrind on an executable that generates aborts (google test
"death" tests), the resulting xml output contains redundant ``
closing tags.  This breaks downstream tools that ingest this xml.

OBSERVED RESULT

$ grep valgrindoutput exec.memcheck






EXPECTED RESULT

$ grep valgrindoutput exec.memcheck



SOFTWARE/OS VERSIONS
Ubuntu 20.04

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

[dolphin] [Bug 457045] New: [REGRESSION] dolphin: allow to drag files into the current folder when the folder only consists of sub-folders (drop in column != "Name")

2022-07-23 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=457045

Bug ID: 457045
   Summary: [REGRESSION] dolphin: allow to drag files into the
current folder when the folder only consists of
sub-folders (drop in column != "Name")
   Product: dolphin
   Version: 22.04.3
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
when trying to drag files folders to a dolphin window which shows a folder
which only consists of sub-folders, the files get copies/moved into a
sub-folder, instead of the current folder

STEPS TO REPRODUCE
1. drag file into dolphin window (which only consists of sub-foulders)
2. drop file

OBSERVED RESULT
files get copied into the sub-folder

EXPECTED RESULT
files get copied into the current folder when dropped in an area != "Name"

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Graphics Platform: X11

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

[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open

2022-07-15 Thread Jim James
https://bugs.kde.org/show_bug.cgi?id=455575

Jim James  changed:

   What|Removed |Added

 CC||kdeb...@jimjam.es

--- Comment #19 from Jim James  ---
I have the same issue on Fedora 36. I only get it when using my NVIDIA eGPU as
primary. When I use my Intel iGPU as primary, this issue doesn't happen. I have
not tested this with X11.

OS: Fedora 36 KDE
Kernel: 5.18.11-200
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.3
Graphics platform: Wayland
NVIDIA Driver Version: 515.48.07 from the NVIDIA CUDA repo (not RPMFusion)

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

[lattedock] [Bug 455955] New: Latte Dock freezes when moving icons

2022-06-26 Thread Jim M
https://bugs.kde.org/show_bug.cgi?id=455955

Bug ID: 455955
   Summary: Latte Dock freezes when moving icons
   Product: lattedock
   Version: 0.10.8
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: k...@xheonin.com
  Target Milestone: ---

Created attachment 150162
  --> https://bugs.kde.org/attachment.cgi?id=150162=edit
The freeze

SUMMARY
The program freezes when I try to move any icon. The outline stays after I
release the icon and I am not able to make any changes until I restart Latte
(after the restart, my changes are gone). While it is "frozen" I can still open
programs and right click on icons, but the dock does not auto-hide and the
"zoom on hover" does not work.

STEPS TO REPRODUCE
1. Move any icon within the dock

OBSERVED RESULT
The dock freezes as described above.

EXPECTED RESULT
The dock would not freeze and my changes would be saved.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux 5.18.6
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
I will attach a video from the time this happens.

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

[kwin] [Bug 455546] [FEATURE] present windows - allow to set the functionality of the right mouse button

2022-06-18 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=455546

Jim Jones  changed:

   What|Removed |Added

Summary|[FEATURE] allow to set the  |[FEATURE] present windows -
   |functionality of the right  |allow to set the
   |mouse button|functionality of the right
   ||mouse button

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

[kwin] [Bug 455546] New: [FEATURE] allow to set the functionality of the right mouse button

2022-06-18 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=455546

Bug ID: 455546
   Summary: [FEATURE] allow to set the functionality of the right
mouse button
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
  Target Milestone: ---

the current present windows effect only handles the left and the middle mouse
button, while the effect is active.

allow an user to defined the functionality of the right button

like:
 * close all windows
 * only show current window class
 * ...

STEPS TO REPRODUCE
1. activate the present windows effect
2. press the right mouse button

OBSERVED RESULT
nothing happens

EXPECTED RESULT
user can define the action of the right mouse button

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Graphics Platform: X11

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

[dolphin] [Bug 409574] Dolphin startup is sometimes delayed by up to 10 seconds

2022-06-18 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=409574

Jim Jones  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Jim Jones  ---
fixed some time ago

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

[frameworks-kio] [Bug 453289] Dolphin doesn't mark the parent folder when Up button is being used

2022-06-05 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=453289

--- Comment #17 from Jim Jones  ---
(In reply to Bug Janitor Service from comment #16)
> A possibly relevant merge request was started @
> https://invent.kde.org/frameworks/kio/-/merge_requests/862

the patch fixes the bug for me

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

[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share

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

--- Comment #2 from JIm  ---
Created attachment 149181
  --> https://bugs.kde.org/attachment.cgi?id=149181=edit
New crash information added by DrKonqi

dolphin (21.12.2) using Qt 5.15.3

- What I was doing when the application crashed:
COnnecting to an SMB share. It asked if I wanted to accept the SSH key, then
crashed when I clicked Yes.

-- Backtrace (Reduced):
#4  0x7fc6bc1afcae in KIO::SlaveInterface::sendMessageBoxAnswer(int) ()
from /lib64/libKF5KIOCore.so.5
#6  0x7fc6ba854182 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc6bb3bfc22 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#8  0x7fc6ba82a118 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#9  0x7fc6ba82d474 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5

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

[dolphin] [Bug 451050] Dolphin crashing when connecting SMB share

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

JIm  changed:

   What|Removed |Added

 CC||not.md.anym...@gmail.com

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

[kdenlive] [Bug 452466] Preview window doen't play video longer than a frame or two

2022-05-07 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=452466

--- Comment #4 from Jim Henderson  ---
(In reply to emohr from comment #2)
> Thank you for reporting. This playback issue on Mac should be solved with
> version 22.04. Please try to see if it's fixed.

Yes, version 22.04 has fixed this issue :-)
I have just used my Mac to edit a video over half an hour long with two clips,
a sound file and several frame stills, all without this problem appearing at
all :-) Thankyou @emohr

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

[kdenlive] [Bug 452466] Preview window doen't play video longer than a frame or two

2022-05-07 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=452466

--- Comment #3 from Jim Henderson  ---


 (In reply to GO from comment #1)
> If I had well understood the description of the bug (see after), I have
> noticed the same problem on a Linux based platform (instead a MacOS one).
> More precisely: MANJARO-Linux 21.2.6, Linux kernel 5.15.32-1, Kdenlive
> version 21.12.3, MLT Version 7.6.0, KDE Version 5.92.0, Qt Version 5.15.3.
> Do we speak about the same bug ?
> As I’m not sure to have well understood the depicted bug, I give my own
> description under:
> The bug appears when I want to load a video clip or a sound clip in my
> project: A finder window is opened, I have enabled the preview panel inside
> (F11) in order to have a look on the clip before loading it (or not). But,
> the clip is not played, only the first frame, apparently, is displayed. No
> player controller is displayed. Nevertheless, loading of the clip proceeds
> normally.
> With an audio clip, no sound is played.

The issue I described applies when I have loaded some clips into a project and
dragged some of them to the timeline. It's during editing that I noticed that
display in the Preview window would stop after just a couple of frames. Happy
to say it is now fixed :-)

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

[dolphin] [Bug 453176] New: when leaving a folder with ALT + UP KEY, dolphin always selects the first folder instead of the folder, the user is coming from

2022-04-29 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=453176

Bug ID: 453176
   Summary: when leaving a folder with ALT + UP KEY, dolphin
always selects the first folder instead of the folder,
the user is coming from
   Product: dolphin
   Version: 22.04.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
entering a folder and leaving it again with (ALT + UP) doesn't select the
folder which currently was 


STEPS TO REPRODUCE
1. enter a folder in dolphin
2. press ALT + UP KEY
3. dolphin selects the first folder instead of folder the user is coming from

OBSERVED RESULT
the first folder is selected

EXPECTED RESULT
the folder the user is coming from, should get selected

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Graphics Platform: X11

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

[konsole] [Bug 427610] Konsole manages its own window position even when forcing KWin to manage window placement

2022-04-22 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=427610

--- Comment #51 from Jim Jones  ---
ping

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

[kwin] [Bug 450315] Application Menu in titlebar doesn't show checkboxes in claws-mail on first click

2022-04-22 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=450315

--- Comment #3 from Jim Jones  ---
ping

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

[gwenview] [Bug 452842] New: create preview of files instantly when the user scrolls through folders with a lot of files

2022-04-22 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452842

Bug ID: 452842
   Summary: create preview of files instantly when the user
scrolls through folders with a lot of files
   Product: gwenview
   Version: 22.04.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: rauchwo...@gmx.net
  Target Milestone: ---

SUMMARY
when gwenview is used to show folders with hundreds/thousands of files the time
to create a preview of files can take a long time. If the user scrolls down to
pictures without an existing preview, gwenview should not create previews in a
linear way and should instead prioritize the creation of preview for the
pictures that are currently in "focus"


STEPS TO REPRODUCE
1. open folder with massive amounts of pictures
2. scroll down some pages
3. wait for a long time until the preview of the focused pictures is created

OBSERVED RESULT
wait for a long time until the preview of the focused pictures is created, when
the user scrolls down


EXPECTED RESULT
the preview of the focused pictures is created instantly, when the user scrolls
down

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Graphics Platform: X11

ADDITIONAL INFORMATION

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-20 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #21 from Jim Jones  ---
finished -
https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/509

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-20 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #20 from Jim Jones  ---
how do i create a merge request? I can only find a new button to create a new
issue, checking out the source creating a new branch and trying to push the new
branch leads to a

You are not allowed to push code to this project.

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-19 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #18 from Jim Jones  ---
if someone can answer this, i can create a the invite stuff

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-19 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #17 from Jim Jones  ---
to be honest, i just payed around with the patch and i'm not quite sure if it
would be a better idea to just revert the whole commit

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-19 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #15 from Jim Jones  ---
shouldn't the guy that pushed this broken commit fix it? based on git it was
Aleix Pol 

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

[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-19 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

--- Comment #13 from Jim Jones  ---
Created attachment 148232
  --> https://bugs.kde.org/attachment.cgi?id=148232=edit
dialog patch

this patch fixes the problem for me, it reverts a part of
29d31c159503e454b3c483b0b7eb180ce0ee926a

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

[kmix] [Bug 452648] New: the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen

2022-04-15 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=452648

Bug ID: 452648
   Summary: the osd volume indicator is displayed in the top left
corner of the screen instead of being displayed in the
center of the screen
   Product: kmix
   Version: 21.12.3
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: On-Screen-Display (OSD)
  Assignee: es...@kde.org
  Reporter: rauchwo...@gmx.net
  Target Milestone: ---

SUMMARY
after the upgrade to kde-frameworks-5.93 the osd volume indicator is displayed
in the top left corner of the screen instead of being displayed in the center
of the screen


STEPS TO REPRODUCE
1. start kmix
2. press the volume button on the keyboard

OBSERVED RESULT
the osd volume indicator is displayed in the top left corner of the screen

EXPECTED RESULT
the osd volume indicator is displayed in the center of the screen

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Graphics Platform: X11

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 452466] New: Preview window doen't play video longer than a frame or two

2022-04-10 Thread Jim Henderson
https://bugs.kde.org/show_bug.cgi?id=452466

Bug ID: 452466
   Summary: Preview window doen't play video longer than a frame
or two
   Product: kdenlive
   Version: 21.12.3
  Platform: Other
OS: macOS
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: j...@sydney.dialix.com.au
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install the latest kdenlive 21.12.3 on macos 11 (Big Sur) on a MacBook Pro
with 64 Gigs of memory, large SSD drive
2. Start a project with a video clip.
3. Start to play the video in order to edit it.

OBSERVED RESULT
The Preview window doesn't play the video longer than just a few frames.

EXPECTED RESULT
I expected the video to play nicely in the Preview window as it does in the
Linux version.

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

ADDITIONAL INFORMATION

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

[Breeze] [Bug 450315] Application Menu in titlebar doesn't show checkboxes in claws-mail on first click

2022-02-15 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=450315

--- Comment #2 from Jim Jones  ---
SUMMARY

when the  "application menu" is in the titlebar and the option menu is shown in
claws-mails new mail windows, the check boxes are missing, the first time the
window is shown

*) removing the application menu from the titlebar fixes the problem
*) closing the menu and re-opening it again, shows the missing check boxes

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

[Breeze] [Bug 450315] Application Menu in titlebar doesn't show checkboxes in claws-mail on first click

2022-02-15 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=450315

--- Comment #1 from Jim Jones  ---
Created attachment 146776
  --> https://bugs.kde.org/attachment.cgi?id=146776=edit
menu, after opening it the second time

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

[Breeze] [Bug 450315] New: Application Menu in titlebar doesn't show checkboxes in claws-mail on first click

2022-02-15 Thread Jim Jones
https://bugs.kde.org/show_bug.cgi?id=450315

Bug ID: 450315
   Summary: Application Menu in titlebar doesn't show checkboxes
in claws-mail on first click
   Product: Breeze
   Version: 5.24.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: window decoration
  Assignee: plasma-b...@kde.org
  Reporter: rauchwo...@gmx.net
CC: kwin-bugs-n...@kde.org
  Target Milestone: ---

Created attachment 146775
  --> https://bugs.kde.org/attachment.cgi?id=146775=edit
menu after opening it the first time

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. open new mail window
2. open options menu
3. check boxes are missing the first time the menu is opened

OBSERVED RESULT
check boxes are missing

EXPECTED RESULT
check boxes are shown

SOFTWARE/OS VERSIONS
Operating System: Linux
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.9-gentoo (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
*) removing the application menu from the titlebar fixes the problem
*) closing the menu and re-opening it again, shows the missing check boxes

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

[valgrind] [Bug 446401] unhandled series of rr-specific syscalls

2021-12-04 Thread Jim Garrison
https://bugs.kde.org/show_bug.cgi?id=446401

--- Comment #1 from Jim Garrison  ---
I found a more descriptive list of the rr-specific syscalls.  It seems it
should be safe to ignore 1008, specifically, under Valgrind.

https://github.com/rr-debugger/rr/blob/878f756966c660a6e838cbf3516f953e586b9edc/src/preload/rrcalls.h#L68-L75

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

[valgrind] [Bug 446401] New: unhandled series of rr-specific syscalls

2021-12-02 Thread Jim Garrison
https://bugs.kde.org/show_bug.cgi?id=446401

Bug ID: 446401
   Summary: unhandled series of rr-specific syscalls
   Product: valgrind
   Version: 3.18.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: j...@garrison.cc
  Target Milestone: ---

SUMMARY

Valgrind complains about unimplemented syscalls when it encounters system calls
specific to rr (the record and replay framework)

STEPS TO REPRODUCE
1. I'm running portions of the Julia test suite under valgrind, following the
instructions at
https://docs.julialang.org/en/v1/devdocs/valgrind/#Running-the-Julia-test-suite-under-Valgrind
(for the purposes here, `all` can be replaced by a much simpler set of tests,
such as `tuple`).

OBSERVED RESULT

valgrind succeeds, but emits the following warning:

--114742-- WARNING: unhandled amd64-linux syscall: 1008
--114742-- You may be able to write your own handler.
--114742-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--114742-- Nevertheless we consider this a bug.  Please report
--114742-- it at http://valgrind.org/support/bug_reports.html.

The README_MISSING_SYSCALL_OR_IOCTL document instructs me to run `grep 1008
/usr/include/asm/unistd*.h`, but this turns up nothing.

Turns out, julia is making this syscall to determine whether it is running
under rr:
https://github.com/JuliaLang/julia/blob/ed9ad60f0ce7cad38870b2bf9eede5dd7a4b706f/test/runtests.jl#L17-L20

There are a number of rr-specific syscalls that valgrind might want to either
handle, ignore, or display a *different*, more informative warning about:
https://github.com/rr-debugger/rr/blob/b8566d29a78d798d547e520fcaaa217a241430e0/src/syscalls.py#L1736-L1747

EXPECTED RESULT

No warning emitted would be ideal.

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

[Discover] [Bug 443745] discover segmentation fault in FlatpakBackend::findSource

2021-11-24 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=443745

--- Comment #13 from Jim  ---
The bug is still present in 5.23.3 on my Fedora 35 Workstation x86_64 kernel
5.14.18-300. Here is the output of plasma-discover:

[jim@localhost ~]$ plasma-discover
adding empty sources model QStandardItemModel(0x564bffc4ae40)
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
**
flatpak:ERROR:common/flatpak-variant-impl-private.h:3570:var_summary_index_get_subsummaries:
assertion failed: (end <= v.size)
Bail out!
flatpak:ERROR:common/flatpak-variant-impl-private.h:3570:var_summary_index_get_subsummaries:
assertion failed: (end <= v.size)
KCrash: Application 'plasma-discover' crashing...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 43 and type 'Read', disabling...
QSocketNotifier: Invalid socket 46 and type 'Read', disabling...
QSocketNotifier: Invalid socket 47 and type 'Read', disabling...
QSocketNotifier: Invalid socket 50 and type 'Read', disabling...
QSocketNotifier: Invalid socket 54 and type 'Read', disabling...
QSocketNotifier: Invalid socket 55 and type 'Read', disabling...
QSocketNotifier: Invalid socket 56 and type 'Read', disabling...
QSocketNotifier: Invalid socket 58 and type 'Read', disabling...
QSocketNotifier: Invalid socket 60 and type 'Read', disabling...
QSocketNotifier: Invalid socket 61 and type 'Read', disabling...
QSocketNotifier: Invalid socket 62 and type 'Read', disabling...
QSocketNotifier: Invalid socket 63 and type 'Read', disabling...
QSocketNotifier: Invalid socket 64 and type 'Read', disabling...
QSocketNotifier: Invalid socket 65 and type 'Read', disabling...
QSocketNotifier: Invalid socket 66 and type 'Read', disabling...
QSocketNotifier: Invalid socket 67 and type 'Read', disabling...
QSocketNotifier: Invalid socket 68 and type 'Read', disabling...
QSocketNotifier: Invalid socket 69 and type 'Read', disabling...
QSocketNotifier: Invalid socket 70 and type 'Read', disabling...
QSocketNotifier: Invalid socket 71 and type 'Read', disabling...
QSocketNotifier: Invalid socket 72 and type 'Read', disabling...
QSocketNotifier: Invalid socket 73 and type 'Read', disabling...
QSocketNotifier: Invalid socket 74 and type 'Read', disabling...
QSocketNotifier: Invalid socket 75 and type 'Read', disabling...
QSocketNotifier: Invalid socket 76 and type 'Read', disabling...
QSocketNotifier: Invalid socket 77 and type 'Read', disabling...
QSocketNotifier: Invalid socket 78 and type 'Read', disabling...
QSocketNotifier: Invalid socket 79 and type 'Read', disabling...
QSocketNotifier: Invalid socket 80 and type 'Read', disabling...
QSocketNotifier: Invalid socket 81 and type 'Read', disabling...
QSocketNotifier: Invalid socket 82 and type 'Read', disabling...
QSocketNotifier: Invalid socket 83 and type 'Read', disabling...
QSocketNotifier: Invalid socket 84 and type 'Read', disabling...
QSocketNotifier: Invalid socket 85 and type 'Read', disabling...
QSocketNotifier: Invalid socket 86 and type 'Read', disabling...
QSocketNotifier: Invalid socket 133 and type 'Write', disabling...
QSocketNotifier: Invalid socket 53 and type 'Read', disabling...
QSocketNotifier: Invalid socket 52 and type 'Read', disabling...
QSocketNotifier: Invalid socket 59 and type 'Read', disabling...
QSocketNotifier: Invalid socket 53 and type 'Write', disabling...
**
OSTree:ERROR:./libglnx/glnx-local-alloc.h:73:glnx_close_fd: assertion failed:
(errno != EBADF)
Bail out! OSTree:ERROR:./libglnx/glnx-local-alloc.h:73:glnx_close_fd: assertion
failed: (errno != EBADF)
Unable to start Dr. Konqi
kf.kio.slaves.file: readData() returned -1
[jim@localhost ~]$

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

[kdenlive] [Bug 443920] Fade Transition leaving after burn

2021-11-09 Thread Jim
https://bugs.kde.org/show_bug.cgi?id=443920

--- Comment #4 from Jim  ---
Resolved by deleting fade out and adding back in. Seem like existing projects
will need Fade Out reload. 
This is not a fix just a work around.

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

[tellico] [Bug 443845] Database won't load after update to Kubuntu 21.10/Tellico 3.4.1

2021-10-21 Thread Jim Sanderson
https://bugs.kde.org/show_bug.cgi?id=443845

--- Comment #9 from Jim Sanderson  ---
Robby,

Thank you!  Look forward to the new version.

Jim

On Wed, Oct 20, 2021 at 7:58 PM Robby Stephenson 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=443845
>
> Robby Stephenson  changed:
>
>What|Removed |Added
>
> 
>Version Fixed In||3.4.2
>   Latest Commit||
> https://invent.kde.org/offi
>|
> |ce/tellico/commit/3824db1ba
>|
> |a75a2b6fdb1806198bdf7582ea4
>||bf2c
>  Resolution|--- |FIXED
>  Status|REPORTED|RESOLVED
>
> --- Comment #8 from Robby Stephenson  ---
> Git commit 3824db1baa75a2b6fdb1806198bdf7582ea4bf2c by Robby Stephenson.
> Committed on 21/10/2021 at 02:54.
> Pushed by rstephenson into branch '3.4'.
>
> Avoid saving invalid XML characters while stripping them during loading
>
> Using QXmlDefaultHandler in Tellico 3.3 silently allowed loading of
> invalid XML characters, while the switch to QXmlStreamReader in 3.4
> resulted in a data file failing to load. In the event of a parsing
> error, strip invalid characters and attempt to reload.
>
> In addition, change the DOM implementation policy to NOT save the
> invalid characters in the fil to begin with.
> FIXED-IN: 3.4.2
>
> A  +14   -0src/tests/data/bug443845.xml
> M  +26   -0src/tests/tellicoreadtest.cpp
> M  +1-0src/tests/tellicoreadtest.h
> M  +15   -0src/translators/tellico_xml.cpp
> M  +1-0src/translators/tellico_xml.h
> M  +5-1src/translators/tellicoimporter.cpp
> M  +5-0src/translators/tellicoxmlexporter.cpp
>
>
> https://invent.kde.org/office/tellico/commit/3824db1baa75a2b6fdb1806198bdf7582ea4bf2c
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[tellico] [Bug 443845] Database won't load after update to Kubuntu 21.10/Tellico 3.4.1

2021-10-19 Thread Jim Sanderson
https://bugs.kde.org/show_bug.cgi?id=443845

--- Comment #7 from Jim Sanderson  ---
(In reply to Robby Stephenson from comment #6)
> (In reply to Jim Sanderson from comment #4)
> > (In reply to Robby Stephenson from comment #2)
> > > Could you email me the data file privately (or attach it here if you're ok
> > > with that)? I'd like to figure out why the difference myself and fix it.
> > 
> > The file is 9.6 MB (compressed).  Will your e-mail accept that?  Or would
> > you just like the offending record?
> 
> I guess the images are included in the file? The offending record would be
> enough, I think. I can copy it into a Tellico 3.3 file and then see what
> happens in the 3.4 load.

Full file sent.

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

  1   2   3   4   >