[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 Kuba Orlik changed: What|Removed |Added CC||kont...@kuba-orlik.name --- Comment #4 from Kuba Orlik --- I'm also experiencing this exact issue. I'm on 20.12.2-1 on desktop and 1.16.0 on Android -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429681] The "KDE Connect" option appears twice when trying to share multiple files
https://bugs.kde.org/show_bug.cgi?id=429681 Kuba Orlik changed: What|Removed |Added CC||kont...@kuba-orlik.name -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429681] New: The "KDE Connect" option appears twice when trying to share multiple files
https://bugs.kde.org/show_bug.cgi?id=429681 Bug ID: 429681 Summary: The "KDE Connect" option appears twice when trying to share multiple files Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: kont...@kuba-orlik.name Target Milestone: --- Created attachment 133664 --> https://bugs.kde.org/attachment.cgi?id=133664=edit A screenshot demonstrating the issue. The Android "Share" dialog is visible, presenting two visually identical options introducing themselves as KDE Connect STEPS TO REPRODUCE 1. Open the Gallery on an Android device 2. Select two or more files (this is important, as the issue does not occur when sharing only one file) OBSERVED RESULT In the sharing menu pop-up, the "KDE Connect" option appears twice. They are identical in appearance, but pressing them causes different things. Pressing one causes the device selection to shop up (the desired behavior, selecting a device sends file to that device), the other causes just the main view for KDE Connect to show up and no way to send the files. EXPECTED RESULT Only one option appears - the one that causes the files to be sent. SOFTWARE/OS VERSIONS: Android: 8.1.0 (LineageOS + MicroG) KDE Connect: 1.15.1 (fdroid) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416786] Plasma was crash after trying delete a app from desktop
https://bugs.kde.org/show_bug.cgi?id=416786 Kuba changed: What|Removed |Added Summary|Usterka plazmy przy próbie |Plasma was crash after |usunięcia programu z|trying delete a app from |pulpitu |desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416786] New: Usterka plazmy przy próbie usunięcia programu z pulpitu
https://bugs.kde.org/show_bug.cgi?id=416786 Bug ID: 416786 Summary: Usterka plazmy przy próbie usunięcia programu z pulpitu Product: plasmashell Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kuba.roez...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: After log in into system I was trying delete a application from desktop "live-usb-maker-qt-19.11.02.x86_64.AppImage". When I was click "Del" key, plasma was crashed. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f15072dae40 (LWP 6047))] Thread 23 (Thread 0x7f144e436700 (LWP 14580)): #0 0x7f14fe02a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d3d4f9e424) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d3d4f9e3d0, cond=0x55d3d4f9e3f8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d3d4f9e3f8, mutex=0x55d3d4f9e3d0) at pthread_cond_wait.c:655 #3 0x7f15010fbaeb in QWaitConditionPrivate::wait (deadline=..., this=0x55d3d4f9e3d0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7f14ec019180, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f15010fbdf9 in QWaitCondition::wait (this=0x7f14ec019188, mutex=0x7f14ec019180, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f150511bec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f150511c2fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f15010f4b52 in QThreadPrivate::start (arg=0x7f14ec019100) at thread/qthread_unix.cpp:360 #9 0x7f14fe0246db in start_thread (arg=0x7f144e436700) at pthread_create.c:463 #10 0x7f15009f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f1461255700 (LWP 7926)): #0 0x7f14fe02a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d3d4a31244) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d3d4a311f0, cond=0x55d3d4a31218) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d3d4a31218, mutex=0x55d3d4a311f0) at pthread_cond_wait.c:655 #3 0x7f15010fbaeb in QWaitConditionPrivate::wait (deadline=..., this=0x55d3d4a311f0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55d3d4a2dc80, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f15010fbdf9 in QWaitCondition::wait (this=0x55d3d4a2dc88, mutex=0x55d3d4a2dc80, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f150511bec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f150511c2fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f15010f4b52 in QThreadPrivate::start (arg=0x55d3d4a2dc00) at thread/qthread_unix.cpp:360 #9 0x7f14fe0246db in start_thread (arg=0x7f1461255700) at pthread_create.c:463 #10 0x7f15009f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f1462dd9700 (LWP 6478)): #0 0x7f15009e00b4 in __GI___libc_read (fd=66, buf=0x7f1462dd8b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f14faba22d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f14fab5d0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f14fab5d570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f14fab5d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1501337b9b in QEventDispatcherGlib::processEvents (this=0x7f145b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f15012d806a in QEventLoop::exec (this=this@entry=0x7f1462dd8da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f15010f33aa in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f15010f4b52 in QThreadPrivate::start (arg=0x7f14c401f930) at thread/qthread_unix.cpp:360 #9 0x7f14fe0246db in start_thread (arg=0x7f1462dd9700) at pthread_create.c:463 #10 0x7f15009f188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f1463fff700 (LWP 6239)): #0 0x7f14fe02a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d3d4671140) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0,
[kde] [Bug 413742] New: application crash on KDE startup (OpenBSD)
https://bugs.kde.org/show_bug.cgi?id=413742 Bug ID: 413742 Summary: application crash on KDE startup (OpenBSD) Product: kde Version: unspecified Platform: OpenBSD Packages OS: OpenBSD Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kg...@o2.pl Target Milestone: --- SUMMARY Hello! I lately try to install KDE4 on OpenBSD 6.5 . Unfortunately that was not quite a success. After starting KDE4, Activity Manager crashed and other apps have troubles starting too. What I did to make KDE4 work… (besides installing kde4 package, of course): * configured to start messagebus (rcctl enable messagebus) * added sysctl tweaks (post install messages from kde-runtime package) * added 'exec kdestart4' to ~user/.xsession Like I wrote… efect is that kde4 starts, but Activity Manager crashes at start. I seen a video on youtube (Setting Up OpenBSD 6.1 with KDE4) where a guy demonstrates how it should be configured, so I got virtual machine with OpenBSD 6.1 on my laptop and it worked! Tweaks pointed above appeared enough to start KDE4. So I got another virtual machine with OpenBSD 6.5 and received the same crashes like on my hardware PC. Lately OpenBSD 6.6 was released so I think I would try it and got also Activity Manager crash. Playing with OpenBSD versions I got to conclusion that KDE4 for versions up to 6.4 works fine. What should I do more? Are any additional tweaks necessary to make things work for version 6.5+ ? I tried few more things… Doubled limits from kde-runtime post-install messages - didn't help. Tried to start via kdm (I used xenodm before). #genkdmconf and then #rcctl stop xenodm #rcctl start kdm KDM seems to not start at all for OpenBSD 6.5+, it writes OK, but doesn't start X and #rcctl ls off |grep kdm gives reply (so it's off). I see that /etc/rc.d/kdm changed in latest versions compared to earlier (ie. 6.1), but I don't feel strong enough to analyze it. ...but maybe it's irrelevant to main issue. File ~$user/.xsession-errors contains a lots of errors, most important (to me) seem (multiple)messages like: *Kded:loadModule: Could not load library "kded_keyboard" . [ "Cannot load library /usr/local/lib/kde4/kded_keyboard.so: (File not found)" ] (altrough file exists) and *kdeinit4_wrapper: Warning: connect(/home/$user/.kde4/socket-$hostname/kdeinit4__0) failed: : No such file or directory Could maybe someone more experienced help? STEPS TO REPRODUCE 1. install OpenBSD ver. 6.5+ with kde4 2. tweak kernel limits as per kde-runtime post-install messages 3. start messagebus (rcctl start messagebus) 4. start KDE4 (ie. startkde4 as root) OBSERVED RESULT (on startup) Activity Manager crash KDE Migration Tool crash .xsession-errors (lots of errors logged) EXPECTED RESULT clean start SOFTWARE/OS VERSIONS OS: OpenBSD 6.5, 6.6 KDE SC Version: 4.14.10 Qt Version: 4.8.7p19 ADDITIONAL INFORMATION I found some other apps crashing (Kinfo) and got some troubles with setting locale -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413661] Explain to the user why a clip wasn't inserted to the timeline
https://bugs.kde.org/show_bug.cgi?id=413661 Kuba Orlik changed: What|Removed |Added CC||kont...@jakub-orlik.pl -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413661] Explain to the user why a clip wasn't inserted to the timeline
https://bugs.kde.org/show_bug.cgi?id=413661 --- Comment #1 from Kuba Orlik --- Relates to: https://bugs.kde.org/show_bug.cgi?id=412223#add_comment which demonstrates how confusing the current behavior can be for some users -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413661] New: Explain to the user why a clip wasn't inserted to the timeline
https://bugs.kde.org/show_bug.cgi?id=413661 Bug ID: 413661 Summary: Explain to the user why a clip wasn't inserted to the timeline Product: kdenlive Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kont...@jakub-orlik.pl Target Milestone: --- SUMMARY It might be confusing to some users (especially new ones) when after clicking "Insert clip zone to timeline" nothing happens - because they didn't specify an active timeline. It would be very user-friendly to display a popup that says "Cannot insert the clip, because none of the timelines are activated. Click on the timeline name to activate it" STEPS TO REPRODUCE 1. Try to insert a clip zone to timeline when no timeline is activated OBSERVED RESULT Nothing happens and it looks like a bug to untrained eye EXPECTED RESULT A popup shows up explaining why the clip wasn't inserted. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412223] Clips don't insert to timeline
https://bugs.kde.org/show_bug.cgi?id=412223 --- Comment #6 from Kuba Orlik --- (I've confirmed it's working correctly on my machine) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412223] Clips don't insert to timeline
https://bugs.kde.org/show_bug.cgi?id=412223 --- Comment #5 from Kuba Orlik --- Oooh, I see. Thanks! It must've changed in some more or less recent version, right? And my muscle memory habits suddenly didn't work :D -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412223] Clips don't insert to timeline
https://bugs.kde.org/show_bug.cgi?id=412223 Kuba Orlik changed: What|Removed |Added CC||kont...@jakub-orlik.pl Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Kuba Orlik --- I'm also experiencing this issue. I've tried the kdenlive-19.08.2-x86_64.appimage release and both pressing 'V' or picking "Timeline > Insertion > Insert Clip Zone in Timeline" do not work. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 344302] kmix close on startup
https://bugs.kde.org/show_bug.cgi?id=344302 --- Comment #2 from Kuba --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! Dear Andrew, I'm sorry it was so long ago that I can't even remember details. Currenty, I run latest stable revision and problem doesn't occur. I think you can close the case. BR, Kuba -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388652] frei0r missing as a dependency
https://bugs.kde.org/show_bug.cgi?id=388652 --- Comment #2 from Kuba Orlik <kont...@jakub-orlik.pl> --- I didn't know about the Wizard - it certainly didn't pop up upon first run... Please tell me - if this is a packaging issue, where should I report it? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388653] New: Missing 'movit' dependency
https://bugs.kde.org/show_bug.cgi?id=388653 Bug ID: 388653 Summary: Missing 'movit' dependency Product: kdenlive Version: 17.12.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: kont...@jakub-orlik.pl Target Milestone: --- Movit is necessary to render movies, but it's not listed as a dependency (even optional) in the repository. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388652] frei0r missing as a dependency
https://bugs.kde.org/show_bug.cgi?id=388652 Kuba Orlik <kont...@jakub-orlik.pl> changed: What|Removed |Added CC||kont...@jakub-orlik.pl -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388652] New: frei0r missing as a dependency
https://bugs.kde.org/show_bug.cgi?id=388652 Bug ID: 388652 Summary: frei0r missing as a dependency Product: kdenlive Version: 17.12.0 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: kont...@jakub-orlik.pl Target Milestone: --- After installing kdenlive on Manjaro, a lot of filters that I remember being there were not available. After lots of searching online I found out that installing frei0r resolves this issue. Unfortunately, frei0r is not a dependency, nor is it marked as an optional dependency for kdenlive. -- You are receiving this mail because: You are watching all bug changes.
