[kdenlive] [Bug 456492] Copy and paste Motion Tracker keyframes does not work
https://bugs.kde.org/show_bug.cgi?id=456492 stan changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from stan --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456492] Copy and paste Motion Tracker keyframes does not work
https://bugs.kde.org/show_bug.cgi?id=456492
stan changed:
What|Removed |Added
CC||stanthema...@yandex.com
--- Comment #3 from stan ---
I'm seeing the exact same bug, as shown in the youtube video in previous post
above, but it's consistent, I've never gotten more than one constant point from
my motion tracker, when I try to import keyframes from the motion tracker, to a
transform of an icon that I want to move along an object in the video.
I'm on Arch Linux, (no desktop environment, using clipmenud as clipboard
manager), my Kdenlive version is v. 22.04.2 and I've replicated the bug on the
latest App Image 2022-08-05, build 301.
Interestingly, just now, that I was confirming that the bug is still there, I
first accidentally clicked the wrong effect to import to, namely a "crop scale
tilt" effect (not sure motion tracking makes sense for that effect) on another
track and clip, and then the keyframe import window did show non-constant
graphs, and it looks like it did import keyframes.
This inspired me to confirm (on build 301), that importing key frames from one
motion tracker effect, to another motion tracker effect, on another clip,
works.
For completeness, when I copy the keyframes, I end up with the following in my
clipboard:
v. 22.04.2 & latest App Image 2022-07-18 (282)
[
{
"DisplayName": "Rectangle",
"in": 1523,
"max": 0,
"min": 0,
"name": "results",
"opacity": false,
"out": 1599,
"type": 9,
"value": "1523~=415 107 470 475 0;1528~=402 95 480 480 0;1533~=413 76
480 480 0;1538~=434 33 480 480 0;1543~=472 -19 480 480 0;1548~=542 -45 480 480
0;1553~=596 -54 480 480 0;1558~=650 -54 480 480 0;1563~=703 -36 480 480
0;1568~=726 -42 480 480 0;1573~=756 -52 480 480 0;1578~=772 -29 480 480
0;1583~=780 3 480 480 0;1588~=799 10 480 480 0;1593~=792 15 480 480 0;1598~=763
20 480 480 0;1599~=683 144 480 480 0"
}
]
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 436665] New: Crash after laptop wakeup
https://bugs.kde.org/show_bug.cgi?id=436665 Bug ID: 436665 Summary: Crash after laptop wakeup Product: plasmashell Version: 5.20.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: virap...@gmail.com Target Milestone: 1.0 Application: plasmashell (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.11.15-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: Opened laptop to wake up from sleep. Since the trace contains some sound references, I'm using pipewire 0.3.26-1. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f21e63310a1 in QPulseAudio::server_cb(pa_context*, pa_server_info const*, void*) () at /usr/lib64/qt5/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so #5 0x7f21e62a3549 in context_get_server_info_callback () at /lib64/libpulse.so.0 #6 0x7f21e6246773 in run_action () at /usr/lib64/pulseaudio/libpulsecommon-14.0.so #7 0x7f21e628b8d9 in dispatch_func () at /lib64/libpulse-mainloop-glib.so.0 #8 0x7f222a51ba9f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #9 0x7f222a56da98 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #10 0x7f222a518e73 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #11 0x7f222c0536f3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7f222c00557b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #13 0x7f222c00d1b4 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #14 0x559c4936b7ca in main () [Inferior 1 (process 3447) detached] Possible duplicates by query: bug 381569, bug 363291, bug 353378, bug 345834, bug 344922. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436665] Crash after laptop wakeup
https://bugs.kde.org/show_bug.cgi?id=436665 --- Comment #2 from Stan --- Updated to F34. I'll let you know if/when it happens again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491745] New: Delay after clicking reboot/shutdown button
https://bugs.kde.org/show_bug.cgi?id=491745 Bug ID: 491745 Summary: Delay after clicking reboot/shutdown button Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: stephan.renn...@gmail.com Target Milestone: 1.0 SUMMARY In KDE 5 (Fedora 39) I can click the shutdown button and immediately get a response in the form of a changed screen. Both on shutdown and on restart, both with and without logoff screen. In KDE 6 (Fedora 40) I have a delay on shutdown and reboot, both with and without logoff screen. I have created a video for comparison. Fedora 39 and 40 on the same Proxomox host with identical parameters. This video shows the comparison: https://my.hidrive.com/lnk/SVj4a2AcT In the video it is Fedora 40 (KDE Plasma 6.0.3) after a fresh installation. Even after installing all updates (KDE Plasma 6.1.4), the problem with the delay still exists. If I open a console and enter 'reboot' the system immediately reboots. The delay is about 3 seconds in the Proxmox VMs. On my laptop the delay is about 7 seconds. I hope the video can make it a bit clearer. OBSERVED RESULT dealy after clicking the button until something happens EXPECTED RESULT Instant reaction after clicking the button SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.4 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443882] popup menu of highlighted text does not appear on right click in text selection mode
https://bugs.kde.org/show_bug.cgi?id=443882 Stan changed: What|Removed |Added CC||schym...@gmail.com --- Comment #18 from Stan --- I think it is important that the right-click + delete works in all annotation modes (highlighting, pop-up, etc.), as this is when it is most needed, e.g. after highlighting the wrong part of text or placing a note in the wrong place. It is very tedious to have to switch out of the annotation mode in order to delete the wrong annotation and then switch back into it again to add the annotation in the right place. Therefore, I would consider this missing functionality a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 409448] New: Crash/coredump at logout
https://bugs.kde.org/show_bug.cgi?id=409448 Bug ID: 409448 Summary: Crash/coredump at logout Product: frameworks-kglobalaccel Version: 5.59.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: virap...@gmail.com Target Milestone: --- Created attachment 121299 --> https://bugs.kde.org/attachment.cgi?id=121299&action=edit coredump SUMMARY At logout kglobalaccel crashes with the following: Stack trace of thread 5650: #0 0x7fa264fd8e75 raise (libc.so.6) #1 0x7fa264fc3895 abort (libc.so.6) #2 0x7fa2653e9b05 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #3 0x7fa2659928af _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5) #4 0x7fa265993108 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5) #5 0x7fa2655cd0c5 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5) #6 0x7fa2659948c3 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5) #7 0x7fa265995828 _ZN15QGuiApplicationC2ERiPPci (libQt5Gui.so.5) #8 0x5564bbcdc481 n/a (kglobalaccel5) #9 0x7fa264fc4f33 __libc_start_main (libc.so.6) #10 0x5564bbcdc7de n/a (kglobalaccel5) STEPS TO REPRODUCE 1. Logout in fedora 30 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 422031] New: KPatience Really Likes Dealing 3 of a kind and 3 of another kind.
https://bugs.kde.org/show_bug.cgi?id=422031 Bug ID: 422031 Summary: KPatience Really Likes Dealing 3 of a kind and 3 of another kind. Product: kpat Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: co...@kde.org Reporter: junkm...@stanking.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Initial deal has 3 of a kind (say, 3 queens) and often adds 3 of another kind (say, 3 8's) then the 4th queen will show up within 3 deals (dealing 3 cards). It's just annoying and almost unwinnable. STEPS TO REPRODUCE 1. start klondike 2. start kpatience 3. play OBSERVED RESULT as stated above EXPECTED RESULT a bit more randomness? SOFTWARE/OS VERSIONS Xubuntu ADDITIONAL INFORMATION I'm old. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 419660] New: Crash on window close
https://bugs.kde.org/show_bug.cgi?id=419660 Bug ID: 419660 Summary: Crash on window close Product: dragonplayer Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: virap...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: dragon (19.04.3) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.5.13-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: I was closing the dragon player window. (filler text to minimum length) -- Backtrace: Application: Dragon Player (dragon), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f418ebd3880 (LWP 25894))] Thread 4 (Thread 0x7f416700 (LWP 25899)): #0 0x7f4191ae0d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f41793e919b in util_queue_thread_func () at /usr/lib64/dri/i965_dri.so #2 0x7f41793e8dab in impl_thrd_routine () at /usr/lib64/dri/i965_dri.so #3 0x7f4191ada4e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7f41922bd6d3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f417bfff700 (LWP 25896)): #0 0x7f41922b2a6f in poll () at /lib64/libc.so.6 #1 0x7f419118686e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f41911869a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f4192989843 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f41929331db in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f4192783c45 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f4192c0ff6a in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f4192784d96 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f4191ada4e2 in start_thread () at /lib64/libpthread.so.0 #9 0x7f41922bd6d3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f41818e2700 (LWP 25895)): #0 0x7f41922b2a6f in poll () at /lib64/libc.so.6 #1 0x7f4191a9938a in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f4191a9afea in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f4181aacd48 in QXcbEventQueue::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f4192784d96 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f4191ada4e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f41922bd6d3 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f418ebd3880 (LWP 25894)): [KCrash Handler] #6 0x7f41921f8625 in raise () at /lib64/libc.so.6 #7 0x7f41921e18d9 in abort () at /lib64/libc.so.6 #8 0x7f4190c6f9f9 in pa_fdsem_post () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #9 0x7f4190c87c07 in pa_srbchannel_write () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #10 0x7f4190c85e55 in do_write () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #11 0x7f4190c86f58 in do_pstream_read_write () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #12 0x7f4190c8729a in srb_callback () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #13 0x7f4190c87b2a in srbchannel_rwloop () at /usr/lib64/pulseaudio/libpulsecommon-13.99.so #14 0x7f4191b7e566 in dispatch_func () at /lib64/libpulse-mainloop-glib.so.0 #15 0x7f4191186570 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #16 0x7f4191186900 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #17 0x7f41911869a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #18 0x7f4192989825 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #19 0x7f41929331db in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #20 0x7f419293b0b6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #21 0x55a0d187eaa8 in main () [Inferior 1 (process 25894) detached] Possible duplicates by query: bug 414938, bug 414549, bug 413345, bug 410860, bug 408356. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 185636] More printing options for page control
https://bugs.kde.org/show_bug.cgi?id=185636 Stan changed: What|Removed |Added CC||k...@storespam.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382659] New: KMail crashed on close
https://bugs.kde.org/show_bug.cgi?id=382659 Bug ID: 382659 Summary: KMail crashed on close Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: stabog@gmail.com Target Milestone: --- Application: kmail (5.5.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.11.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I had been closing KMail. Right after pushing 'close' button, it crashed. - Custom settings of the application: I have two separate IMAP accounts with several thousands of emails. The crash does not seem to be reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb3b49c3900 (LWP 9578))] Thread 27 (Thread 0x7fb2fc340700 (LWP 15290)): #0 0x7fb3a762f4ed in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb39bee4992 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fb39bebaba9 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fb39bebb10b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fb39beb39eb in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fb3a7629049 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb3b1b6cf0f in clone () from /usr/lib/libc.so.6 Thread 26 (Thread 0x7fb2f95b2700 (LWP 9802)): #0 0x7fb3a762f1ad in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb39beb60a5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fb39beb6587 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fb39beb7321 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fb39beb39eb in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fb3a7629049 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb3b1b6cf0f in clone () from /usr/lib/libc.so.6 Thread 25 (Thread 0x7fb2f9e33700 (LWP 9801)): #0 0x7fb3a762f1ad in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb39beb60a5 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fb39beb6587 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fb39beb7321 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fb39beb39eb in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fb3a7629049 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb3b1b6cf0f in clone () from /usr/lib/libc.so.6 Thread 24 (Thread 0x7fb2fae66700 (LWP 9800)): #0 0x7fb3a762f1ad in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fb397de8b04 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7fb397de8b49 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7fb3a7629049 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fb3b1b6cf0f in clone () from /usr/lib/libc.so.6 Thread 23 (Thread 0x7fb2f700 (LWP 9797)): #0 0x7fb3b1b62e9d in poll () from /usr/lib/libc.so.6 #1 0x7fb3a5825c09 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fb3a5825d1c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fb3b2497084 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb3b243affb in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb3b225440e in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb3b225915b in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fb3a7629049 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fb3b1b6cf0f in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7fb3297fa700 (LWP 9611)): #0 0x7fb3b1b5ec0d in write () from /usr/lib/libc.so.6 #1 0x7fb3b1af393d in _IO_new_file_write () from /usr/lib/libc.so.6 #2 0x7fb3b1af2c1f in new_do_write () from /usr/lib/libc.so.6 #3 0x7fb3b1af40fe in __GI__IO_file_xsputn () from /usr/lib/libc.so.6 #4 0x7fb3b1acadfb in buffered_vfprintf () from /usr/lib/libc.so.6 #5 0x7fb3b1ac815e in vfprintf () from /usr/lib/libc.so.6 #6 0x7fb3b1b7bb06 in __fprintf_chk () from /usr/lib/libc.so.6 #7 0x7fb3916fb17d in event_logv_ () from /usr/lib/libevent-2.1.so.6 #8 0x7fb3916fb314 in event_warn () from /usr/lib/libevent-2.1.so.6 #9 0x7fb3916fcc3c in ?? () from /usr/lib/libevent-2.1.so.6 #10 0x7fb3916f28f4 in event_base_loop () from /usr/lib/libevent-2.1.so.6 #11 0x7fb39be86eed in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fb39be83168 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #13 0x7fb39be9fd5b in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #14 0x7fb39beb78e6 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #15
[kdenlive] [Bug 496054] New: Disable tutorial info in Statusbar
https://bugs.kde.org/show_bug.cgi?id=496054 Bug ID: 496054 Summary: Disable tutorial info in Statusbar Classification: Applications Product: kdenlive Version: 24.08.2 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface & Miscellaneous Assignee: j...@kdenlive.org Reporter: stanthema...@yandex.com Target Milestone: --- SUMMARY When selecting and/or hovering over a clip, the status bar shows useful information of the clip, such as the length of the clip and start/stop time position. However, often it's not possible to see the full information, since most of the status bar is obscured by tutorial information "Shift drag for rubber-band selection, Shift click for 2" STEPS TO REPRODUCE 1. load a project, ensure status-bar is activated (menu -> settings) 2. select a clip e.g. on that is cut from a longer source clip 3. hover over the clip, e.g. to see how long the clip is. OBSERVED RESULT Most of status bar is taken up by introductory tutorial info. EXPECTED RESULT Possibility to disable tutorial / intro info in status bar, by settings -> configure kdenlive SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441509] Dolphin crash every time I view the properties of a folder
https://bugs.kde.org/show_bug.cgi?id=441509 Stan Morris changed: What|Removed |Added CC||pixelgre...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441509] Dolphin crash every time I view the properties of a folder
https://bugs.kde.org/show_bug.cgi?id=441509 --- Comment #5 from Stan Morris --- Created attachment 150171 --> https://bugs.kde.org/attachment.cgi?id=150171&action=edit New crash information added by DrKonqi dolphin (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: I wanted to see what file system my USB drive uses. I right-click the drive name that appeared under "Removeable Devices" in Dolphin's left pane and selected "Properties" from the context menu. A window appeared that looked like the correct information and disappeared before I could read the contents... perhaps 1 second. I crash dialog popped up, I discarded it. I tried performing the exact same procedure and got the same result. I think the third time I was able to read "VFAT" and got the answer I needed, but I decided that the defect behavior was reproducible and worth entering a bug report. I read through the list of similar bug reports and the crash report for "view properties of a folder" has enough similarities that I decided to test it and I verified that choosing any folder results in a crash. This I cannot think of any modification that I've done that would destabliize Kubuntu -- I'm a novice when it comes to Linux. I have Kubuntu 21.10 and I prefer to use automatic updates instead of tweaking Linux myself; I don't think I did something to break Dolphin. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140642270800320) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140642270800320) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140642270800320, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fe9d94e5476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fe9d94cb7b7 in __GI_abort () at abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423694] New: Prints the square of the quantity requested: ask for 2,get 4; ask for 3, get 9, ask for 4,get 16 sheets.
https://bugs.kde.org/show_bug.cgi?id=423694 Bug ID: 423694 Summary: Prints the square of the quantity requested: ask for 2,get 4; ask for 3, get 9, ask for 4,get 16 sheets. Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: stan7...@gmail.com Target Milestone: --- SUMMARY Prints the square of quantity requested. STEPS TO REPRODUCE 1. Bring up a document 2. File > Print 3. Ask for more than just one copy OBSERVED RESULT: When printing a document, if I ask for quantity of 2, I get 4 sheets. If ask for 3, get 9 sheets etc, etc If ask for 20, get 400 sheets printed per page!! EXPECTED RESULT: Want exact quantity of print-outs requested. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.12.9 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 (build against 5.9.5) ADDITIONAL INFORMATION: The xcb windowing system Kubuntu 18.04 kernel version: 5.3.0-61-generic OS Type: 64-bit Hardware: Processors: 12 x Intel Core i7-8700 CPU @ 3.20 GHz Memory: 31.2 GiB of RAM Note: issue isolated to Okular by testing in LibreOffice Writer, which prints exactly the quantity requested. No other application, whether an email or a web page results in this behavior either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387961] Device action disappears from device notifier when its description is edited
https://bugs.kde.org/show_bug.cgi?id=387961 Stan Towianski changed: What|Removed |Added CC||stashu@gmail.com --- Comment #4 from Stan Towianski --- same on newer mageia 7: KDE Plasma version 5.15.4 KDE Frameworks 5.57.0 Qt 5.12.2 Also in Manjaro current/up-to-date 18.0.4 I think it is Alt-space go to Device actions choose "Open with File Manager" the one with all the Storage stuff change kde-open5 "%f" to whatever : myscript.sh "%f" plug in usb stick missing option to "open with file manager" go edit again and change back to kde-open5 "%f" it is still missing. I am not taking anything out. this is a minor change. I am guessing it is not writing out some config file properly. also, if /usr/share/solid/actions/ is where it writes files, there are now 17 files in there and they are like gwenview, dragonplayer, digikam, vlc, but nothing about file-manager or dolphin... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387961] Device action disappears from device notifier when its description is edited
https://bugs.kde.org/show_bug.cgi?id=387961 --- Comment #5 from Stan Towianski --- I at least figured out how to make it work by creating my own device action file. don't know if it matters but only version diff seems to be Qt Version 5.12.6 I did one "no change" edit and it did not mess up my file but I do not know if editting works yet. so I think default files must be at: /usr/share/solid/actions per skierpage I copied one : test-predicate-openinwindow.desktop to: /home/myuser/.local/share/solid/actions as: test-predicate-openinwindow-jfp.desktop (jfp file manager) test-predicate-openinwindow-jfp.desktop - [Desktop Entry] X-KDE-Solid-Predicate=[ [ [ StorageVolume.ignored == false AND StorageVolume.usage == 'FileSystem' ] OR [ IS StorageAccess AND StorageDrive.driveType == 'Floppy' ] ] OR StorageAccess.ignored == false ] Type=Service Actions=open; [Desktop Action open] Name=Open with JFileProcessor Exec=/mypath/programs/jfp-to-use/run.sh "%f" Icon=/mypath/github/jfileprocessorRest/src/main/resources/icons/jfp.png --- jfp-to-use/run.sh -- #!/bin/bash cd /mypath/programs/jfp-to-use java -jar JFileProcessor-1.8.9.war $1 at least this works and the device action file does not get mangled or disappear. When I pop in a usb stick It does show my name, my icon and opens my program for the usb stick path. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 340670] JJ: Document list recent files highlight is hard to see with dark theme
https://bugs.kde.org/show_bug.cgi?id=340670 --- Comment #4 from Alexandru Stan --- This seems to have been fixed a while ago. I guess the fixer never discovered this bug to link it against. Thank you regardless. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 340670] JJ: Document list recent files highlight is hard to see with dark theme
https://bugs.kde.org/show_bug.cgi?id=340670 Alexandru Stan changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] New: asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 Bug ID: 388088 Summary: asi1600mm Product: kstars Version: 2.8.9 Platform: Other OS: OS X Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: s...@darkskyastro.com Target Milestone: --- Attempting to use zwo asi1600mm camera with kstars/ekos. Camera connects fine and allows configuration but will not download an image. I believe the latest version of kstars for Mac has been compiled with an old version of the zwo driver that lacks the usb issue resolution. Newer version is used in Astroimager and it downloads from the camera. If I use Indi server to connect to the asi camera instead of the native zwo driver in astroimager, it will not download as well. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 --- Comment #2 from stan smith --- I was using nebulosity for acquisition and had a similar download issue. Craig Stark said there was a usb issue and zwo had updated their driver to resolve it. On connection I get this: 2017-12-21T11:33:01: [INFO] Device configuration applied. 2017-12-21T11:33:01: [ERROR] ASISetROIFormat (0x0 @ 1) error (9) 2017-12-21T11:33:01: [INFO] Upload settings set to client only. 2017-12-21T11:33:01: [INFO] Loading device configuration... 2017-12-21T11:33:01: [INFO] CCD is online. Retrieving basic data. 2017-12-21T11:33:01: [INFO] Setting intital bandwidth to AUTO on connection. When I attempt to acquire an image I get this: [ERROR] ASIGetDataAfterExp (1x1 #1 channels) error (13) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 --- Comment #3 from stan smith --- Created attachment 109472 --> https://bugs.kde.org/attachment.cgi?id=109472&action=edit crash report -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 --- Comment #4 from stan smith --- After I sent the errors in the previous post and exited kstars it refuses to reopen. I have restarted, uninstalled and removed every reference to kstars I could find. Reinstalled with fresh download of kstars and it still will not open. I hope you can help. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 --- Comment #5 from stan smith --- It is definitely something wrong with my MacBook. I just installed everything on my matchbook air as a test and it all works just like it should. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 388088] asi1600mm
https://bugs.kde.org/show_bug.cgi?id=388088 --- Comment #8 from stan smith --- Yes. My problem is on my laptop and not an issue with your software. Sorry for the bother. It appears I may have to reload the machine to resolve it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385668] New: git: revision graph gets confused when head is detached
https://bugs.kde.org/show_bug.cgi?id=385668 Bug ID: 385668 Summary: git: revision graph gets confused when head is detached Product: kdevelop Version: 5.0.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: VCS: Git Assignee: kdevelop-bugs-n...@kde.org Reporter: a...@hypertriangle.com Target Milestone: --- The git vcs plugin seems to be parsing the string "(HEAD detached at origin/master)" as an actual branch name, this seems wrong. Steps to reproduce: bash$ git --version git version 2.15.0.rc0.271.g36b669edcc bash$ git checkout origin/master # i do this often, without creating a local branch ... bash$ git branch * (HEAD detached at origin/master) other branches here Right click file, Git > Revision Graph... > git rev-list remotes/origin/some-branch '^(HEAD detached at origin/master)' fatal: bad revision '^(HEAD detached at origin/master)' Command finished with error UnknownError. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 359296] New: No "Recurrence Rule" for Hourly/Minutely
https://bugs.kde.org/show_bug.cgi?id=359296 Bug ID: 359296 Summary: No "Recurrence Rule" for Hourly/Minutely Product: kalarm Version: unspecified Platform: openSUSE RPMs URL: https://www.dropbox.com/s/tubtlrpfmd52lvi/kalarm.png?r aw=1 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Akonadi Assignee: djar...@kde.org Reporter: stangoesag...@gmail.com This is for Version 2.11.3-5ak that in openSUSE packages appears as kalarm5 version 15.12.1-12.2 There are no options to set recurrence rule to 1 or 2 hours, or 10 minutes. In the screenshot it's an old alarm set with previous kalarm (4.14.10-3.10). The recurrence used to be set to 5 min and it shows in the Recurrence tab title but there's no way to change it. For new alarms recurrence is automatically reported at 1 min (in the tab title). Daily/Weekly/Monthly/Yearly choices show relevant editing options as expected. Reproducible: Always Steps to Reproduce: 1. Launch Kalarm 2. Select New and choose any type of alarm 3. Click on Recurrence tab 4. Select Hourly/Minutely Actual Results: No options to edit recurrence Expected Results: Options for setting hours and minutes for recurrence, more or less like in KDE Task Scheduler (where it works). -- You are receiving this mail because: You are watching all bug changes.
