[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Erik Zeek changed: What|Removed |Added CC||zee...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407433] New: Visible Area of the Timeline Out of Sync with Keyboard Navigation
https://bugs.kde.org/show_bug.cgi?id=407433 Bug ID: 407433 Summary: Visible Area of the Timeline Out of Sync with Keyboard Navigation Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@michaeltunnell.com Target Milestone: --- SUMMARY The Timeline of 19.04+ is no longer connected to the keyboard navigation shortcuts. I created a video to demonstrate the issue that I am experiencing: https://youtu.be/rblA9vh-0Lw STEPS TO REPRODUCE 1. Have a large enough Timeline to have something extending either side of the visible area. 2. Use Keyboard navigation like Alt+Left or Alt+Right to navigate through the timeline. OBSERVED RESULT Timeline is in a fixed position and does not follow the playhead when using keyboard navigation. EXPECTED RESULT The visible area of the timeline should follow the playhead, the playhead should always be visible in the timeline. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.10 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406786] Appimage doesn't have "breeze" style"
https://bugs.kde.org/show_bug.cgi?id=406786 --- Comment #4 from Jesse DuBord --- (In reply to emohr from comment #3) > Goto: settings -> tick „force breeze icon theme“. Kdenlive restarts and you > should see the icons. When I opened the program, that box was already checked/ticked. I disabled then re-enabled it, but it did not fix the issue: the style of the widgets still were not Breeze. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407312] F3 Find Next sometimes skips the next instance of the search string.
https://bugs.kde.org/show_bug.cgi?id=407312 --- Comment #2 from Ron Cemer --- I'm using plain text search mode. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 401896] freecell getting all system memory
https://bugs.kde.org/show_bug.cgi?id=401896 Wolfgang Bauer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Wolfgang Bauer --- Ok, let's close this report then. Feel free to reopen if it should happen again. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407430] gparted has two icons
https://bugs.kde.org/show_bug.cgi?id=407430 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This is a bug in GParted. It's setting an ugly low-resolution custom window icon, and KWin respects those. It's possible to work around this by forcing KWin to ignore the custom window icon, but it really should be fixed in GParted itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Jeffery Patton changed: What|Removed |Added Summary|KWin 5.15.4 hang regression |KWin 5.15.4+ hang |on Nvidia Optimus |regression on Nvidia ||Optimus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #32 from Jeffery Patton --- (In reply to David Edmundson from comment #28) > From Erik: > > "Alright, I think I see what the issue is. For context, on PRIME systems, > since there isn't actually a display connected to the NVIDIA GPU, we rely on > xf86-video-modeset, which drives the Intel GPU, to call to our driver after > each vblank. However, it will actually only do so if there has been damage > to the screen. So what I think we have here is QtQuick's thread waiting on > this vblank signal before swapping buffers (since we set MaxFramesAllowed to > 1), and KWin's main compositing thread waiting on the QtQuick thread. Since > KWin isn't rendering to the screen while it waits, no damage occurs and > hence this vblank signal is never sent. I think some timeout is what > eventually gets things going again (after about 30 seconds). Does that make > sense?" > > A possible patch is here: https://phabricator.kde.org/P385 could someone try > it? Nice to see that a patch's development is at least being kicked off. Dealing with this bug for more than a month now has been quite annoying. :P Too bad I don't know C++ (I'm learning software development in college though, so that's something I may learn in the future), because I could've helped with this problem as well. :( -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 407434] New: snap crashes: $> qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display.
https://bugs.kde.org/show_bug.cgi?id=407434 Bug ID: 407434 Summary: snap crashes: $> qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display. Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sebastianvjacob...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. ctrl+alt+t 2. $> 3. wait 5 seconds OBSERVED RESULT > qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display. EXPECTED RESULT "opens the snap package" SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu (available in About System) KDE Plasma Version: 5 KDE Frameworks Version: unknown Qt Version: 3.11.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406584] Digikam crashes after scanning for new items
https://bugs.kde.org/show_bug.cgi?id=406584 --- Comment #3 from IWBR --- I think I finally captured the error in a debug console. Here there are the last few lines of the output: Digikam::ActionThreadBase::run: Action Thread run 1 new jobs [New Thread 0x7fff94ff9700 (LWP 6204)] [New Thread 0x7fff957fa700 (LWP 6205)] Digikam::ActionThreadBase::run: Action Thread run 1 new jobs [New Thread 0x7fff7bfff700 (LWP 6206)] Digikam::ActionThreadBase::cancel: Cancel Main Thread [New Thread 0x7fff7b7fe700 (LWP 6207)] [Thread 0x7fff95ffb700 (LWP 6199) exited] [New Thread 0x7fff95ffb700 (LWP 6208)] Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::ActionThreadBase::slotJobFinished: One job is done [Thread 0x7fffacdea700 (LWP 6201) exited] Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fffaedee700 (LWP 6202) exited] [Thread 0x7fff977fe700 (LWP 6200) exited] Digikam::ActionThreadBase::slotJobFinished: One job is done [Thread 0x7fff96877700 (LWP 6203) exited] Digikam::DImg::load: "/home/user2/Documents/FOTOS/whatsapp/IMG-20190418-WA0013.jpg" : JPEG file identified Digikam::DImg::load: "/home/user2/Documents/FOTOS/whatsapp/IMG-20190418-WA0011.jpg" : JPEG file identified Digikam::DImg::load: "/home/user2/Documents/FOTOS/whatsapp/IMG-20190418-WA0010.jpg" : JPEG file identified Digikam::ActionThreadBase::cancel: Cancel Main Thread [Thread 0x7fff94ff9700 (LWP 6204) exited] Digikam::ActionThreadBase::slotJobFinished: One job is done [Thread 0x7fff957fa700 (LWP 6205) exited] [New Thread 0x7fff957fa700 (LWP 6209)] Thread 3 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd7fff700 (LWP 5538)] 0x7fffe8d6e3c1 in _int_malloc (av=av@entry=0x7fffd020, bytes=bytes@entry=28) at malloc.c:3612 3612malloc.c: El fitxer o directori no existeix. (gdb) In this case, Digikam became frozen, instead of just closing, I guess due to the "debug" mode. The output is much much longer. I was only able to copy the last ~5000 lines. I didn't paste the whole thing here because of its length and due to privacy reasons, but I didn't observe anything special in it. However, I could provide it if you deem it necessary. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 407434] snap crashes: $> qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display.
https://bugs.kde.org/show_bug.cgi?id=407434 Unknown changed: What|Removed |Added Platform|Other |Kubuntu Packages --- Comment #1 from Unknown --- if im putting data in the incorrect fields pls. let me know i am still a newbie -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405206] OFX import targets the wrong account
https://bugs.kde.org/show_bug.cgi?id=405206 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Thomas Baumgart --- I fully understand your privacy concerns. Thanks for providing the information in obfuscated form, which is helpful. The problem seems to be that shows up twice. I looks to me that the second occurrence in your output contains to the element of the account in question. Does the second one show up in the context of the account "Cartes de Credits La Poste"? This would explain what is happening. I wonder how it got there, though? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407406] System Settings Crashes when trying to access 'Looks and Feels' Tab
https://bugs.kde.org/show_bug.cgi?id=407406 maxmustermann1...@web.de changed: What|Removed |Added CC||maxmustermann1...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 401896] freecell getting all system memory
https://bugs.kde.org/show_bug.cgi?id=401896 Herman changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #33 from Jeffery Patton --- I changed the title to signify that this still affects 5.14.5, besides 5.14.4. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 402760] Source browse mode activated when saving the document with shortcut
https://bugs.kde.org/show_bug.cgi?id=402760 --- Comment #15 from Simone Gaiarin --- Some thoughts from my debug session: The culprit is in browsemanager.cpp, method eventFilter (Kdevelop at tag 5.3.2) When the Ctrl key is pressed, we enter the first 'if' (line 178) because keyEvent->key() == browseKey and browseMode is activated. m_browsingByKey is set. The event at this point is QKeyEvent(KeyPress, Key_Control, ControlModifier) When Ctrl is released, m_broswingByKey should be unset at line 216, but here we fail to enter the if because we have QKeyEvent(KeyRelease, 0, ControlModifier), so that the condition keyEvent->key() == m_browsingByKey is not satisfied. Given that m_broswingByKey is not unset, as soon we move the mouse we enter eventFilter again and we skip the if at line 233, where we should reset the cursor and return. Instead we proceed to the next if where setHandCursor is called. Basically the problem is that the event we receive when we release Ctrl is QKeyEvent(KeyRelease, 0, ControlModifier) instead of QKeyEvent(KeyPress, Key_Control, ControlModifier) and we miss it. For some reason when the python language plugin is not active we re-enter eventFilter few more times after moving the mouse up to the point where m_browsingByKey is unset and everything goes back to normal. (This interaction is still not clear to me). Nonetheless I think the problem is not in the plugin but in KDevelop itself. It should catch the KeyRelease event correctly. I see if I can think a way to fix this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #17 from David Hurka --- Created attachment 119990 --> https://bugs.kde.org/attachment.cgi?id=119990&action=edit No Text causing shell.rc from David Hurka I didn’t attach my file in the last comment, here it is. Differs from Jan’s shell.rc in the DOCTYPE: kpartgui instead of gui. Is very similar to the shell.rc found in okular’s git repository, but with Open action added to toolbar, some noMerge="1", and SYSTEM "kpartgui.dtd". The shell.rc from the repository works fine, while the attached shell.rc causes No Text. Removing an noMerge="1" from the attached shell.rc file fixed the corresponding No Text entry. Jan’s file, in contrast, looks like the shell.rc files, which are saved by Okular when I put actions into the toolbar. (Okular creates gui files instead of kpartgui files. Why?) Additionally, I observed that No Text menus don’t contain shell actions, but only part actions. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 --- Comment #16 from Laurent Bonnaud --- I have the master flatpak version (konsole 19.07.70), but unfortunately session management does not work with it: $ flatpak run org.kde.konsole//master Qt: Session management error: Could not open network socket and my bug seems to be related to session management because I see this in the backtrace: #42 0x7f3d5641f44b in QProcess::waitForFinished (this=, msecs=1000) at io/qprocess.cpp:1919 #43 0x7f3d57a885f5 in Konsole::Session::closeInNormalWay() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #44 0x7f3d57a889f5 in Konsole::Session::close() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #45 0x7f3d57a9ae08 in Konsole::SessionManager::closeAllSessions() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.18 #46 0x7f3d57d27614 in Konsole::Application::~Application (this=0x7ffc33e2d150, __in_chrg=) at ./src/Application.cpp:158 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 --- Comment #17 from Laurent Bonnaud --- The bug is still in Ubuntu 19.04 with the following versions: konsole 4:18.12.3-0ubuntu2 KF5 5.56.0-0ubuntu1 Qt 5.12.2+dfsg-2ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942
--- Comment #18 from Laurent Bonnaud ---
Here is a backtrace:
#0 0x7f3d57c39729 in __GI___poll (fds=0x7f3d40004e30, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 2
sc_cancel_oldtype = 0
sc_ret =
#1 0x7f3d54716cb6 in g_main_context_poll (priority=,
n_fds=2, fds=0x7f3d40004e30, timeout=, context=0x7f3d4bf0)
at ../../../glib/gmain.c:4228
ret =
errsv =
poll_func = 0x7f3d547264d0
poll_func =
ret =
errsv =
#2 g_main_context_iterate (context=context@entry=0x7f3d4bf0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../../../glib/gmain.c:3922
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 2
allocated_nfds = 2
fds = 0x7f3d40004e30
#3 0x7f3d54716ddc in g_main_context_iteration (context=0x7f3d4bf0,
may_block=may_block@entry=1) at ../../../glib/gmain.c:3988
retval =
#4 0x7f3d564ec047 in QEventDispatcherGlib::processEvents
(this=0x7f3d4b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422
d = 0x7f3d4b40
canWait = true
savedFlags = {i = 0}
result =
#5 0x7f3d564975bb in QEventLoop::exec (this=this@entry=0x7f3d4ec2dd70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
d = 0x7f3d40003800
locker = {val = 94103253173360}
ref = {d = 0x7f3d40003800, locker = @0x7f3d4ec2dcf8, exceptionCaught =
true}
app =
#6 0x7f3d562e22c6 in QThread::exec (this=this@entry=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
d = 0x55961efa4400
locker = {val = 94103253173360}
eventLoop = { = {_vptr.QObject = 0x7f3d567453c8 , static staticMetaObject = {d = {superdata = 0x0, stringdata =
0x7f3d566370c0 , data = 0x7f3d56636fa0
, static_metacall = 0x7f3d564c9470
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x7f3d40003800},
static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7f3d56639fe0
, data = 0x7f3d566371e0 ,
static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = 0x7f3d5673d980
, stringdata = 0x7f3d56631ae0
, data = 0x7f3d56631a80
, static_metacall = 0x7f3d564972e0
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
returnCode =
#7 0x7f3d55a42565 in QDBusConnectionManager::run (this=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
locker =
#8 0x7f3d562e3612 in QThreadPrivate::start (arg=0x7f3d55ac2d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
thr = 0x7f3d55ac2d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>
data =
__clframe = {__cancel_routine = 0x7f3d562e2b40
, __cancel_arg = 0x7f3d55ac2d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __do_it = 1,
__cancel_type = }
#9 0x7f3d54f31182 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139901291128576,
-3784097251147283699, 140721178987678, 140721178987679, 140721178987888,
139901291126528, 3820937170979750669, 3820889216029131533}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
#10 0x7f3d57c45b1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
.
Thread 1 (Thread 0x7f3d517bcd80 (LWP 2236)):
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 17678122487503011840, 0, 139901436319509,
139901436331328, 139901442150508, 94103259618752, 42, 42, 139901436331008,
1256, 0, 0, 0, 0, 0}}
pid =
tid =
ret =
#1 0x7f3d576a62bc in KCrash::defaultCrashHandler(int) () from
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
No symbol table info available.
#2
No locals.
#3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 0, 13827369929818582336, 0, 282042221696779236, 0,
7233170478761014387, 109330211561823, 4621304461106629456, 0,
13827369929818582336, 0, 282042221696779236, 0, 4651831386980745216, 0}}
pid =
tid =
ret =
#4 0x7f3d57b4d535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb, sa_sigaction = 0xb},
sa_mask = {__val = {139901443036800, 3432, 1, 139901443036931, 139901441637425,
14, 139901443036800, 10, 139901177858880, 139901426168304, 8, 139901329313632,
139901441638643, 139901329313632, 139901441583103, 139901443037248}}, sa_flags
= 144379
[konsole] [Bug 389942] konsole crash on logout
https://bugs.kde.org/show_bug.cgi?id=389942 Laurent Bonnaud changed: What|Removed |Added Version|17.12.2 |18.12.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 392806] Lock horizontal scroll
https://bugs.kde.org/show_bug.cgi?id=392806 --- Comment #1 from David Hurka --- I’m currently thinking about horizontal scrolling, but this is probably what Trim Margins / Trim To Selection is good for. (Unfortunately, Trim Margins does not work well yet.) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407435] Any window to open or save a file is empty.
https://bugs.kde.org/show_bug.cgi?id=407435 vitamin307 changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407435] Any window to open or save a file is empty.
https://bugs.kde.org/show_bug.cgi?id=407435 --- Comment #1 from vitamin307 --- So far only in kdenlive is observed the issue. Other applications can open the dialog box for open or save files. Seems the window is just transparent but clicking on it in areas of "Open" or "Cancel" buttons the buttons are activated and window gets closed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407435] New: Any window to open or save a file is empty.
https://bugs.kde.org/show_bug.cgi?id=407435 Bug ID: 407435 Summary: Any window to open or save a file is empty. Product: kdenlive Version: 17.12.3 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: vitamin...@gmail.com Target Milestone: --- Created attachment 119991 --> https://bugs.kde.org/attachment.cgi?id=119991&action=edit Screenshot of KDEnlive with empty window that popup after click on Open in File menu. SUMMARY I am running KDEnlive in LUbuntu 18.04 in VBox on Windows10 host. When I try to open or save any file the winow that popup have only empty frame. But the application is running. If I type blind a filename it will open or saved. I can close the window. Attached is a screenshot taken immediately after starting KDEnlive and click open in File menu. I was moving Shutter winodw and that took capture over the Open window and it left a track. STEPS TO REPRODUCE 1. Open KDEnlive 2. Try to open or save any files. 3. The issue is permannetlt reproduced OBSERVED RESULT The window have only frame and close button on corner but it is transparent (empty). Any other object moved over it leaves a track. EXPECTED RESULT In the window it is expected to appear a file list menu to select path and file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION VBoc 6.0 with installed extention pack on linux. Version 6.0.6 r130049 (Qt5.6.2) -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 407436] New: opensuse leap 15.1 Application: Baloo File Indexing Daemon
https://bugs.kde.org/show_bug.cgi?id=407436 Bug ID: 407436 Summary: opensuse leap 15.1 Application: Baloo File Indexing Daemon Product: BalooWidgets Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: silb...@t-online.de Target Milestone: --- Created attachment 119992 --> https://bugs.kde.org/attachment.cgi?id=119992&action=edit Error immediately after start of kde plasma SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Bernhard Rosenkränzer changed: What|Removed |Added CC||b...@lindev.ch --- Comment #12 from Bernhard Rosenkränzer --- We just fixed this in OpenMandriva. Patch here: https://github.com/OpenMandrivaAssociation/ktorrent/blob/master/ktorrent-5.1.1-geoip.patch -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 --- Comment #13 from Bernhard Rosenkränzer --- https://phabricator.kde.org/D21145 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 319870] Add smooth scrolling
https://bugs.kde.org/show_bug.cgi?id=319870 --- Comment #8 from David Hurka --- I already have per-pixel scrolling with my touchpad. Versions: Computer: Lenovo Ideapad s205 (with Synaptics touchpad) Touchpad settings: Inertial scrolling off (doesn’t matter) KDE Neon 5.15 Plasma 5.15.4 KDE Frameworks 5.57.0 Qt 5.12.0 Kernel 4.18.0-17-generic All applications have per-pixel scrolling, Konsole and Kate have per-line scrolling. Only Firefox does junk. Scrolling with a mouse wheel (simulated with xdotool) gives stepwise scrolling (not animated) in Okular and most other applications. In some widgets, like QAbstractItemView (like in Dolphin), it gives smooth scrolling (stepwise, animated). (Just for info: I don’t like smooth scroling (stepwise, animated), because when I send saccadic scroll commands (what the mouse wheel mechanic enforces), my eyes also want to move saccadic. So, after the saccadic eye movement, I have to wait until the animation is over. Please do not implement smooth scrolling (stepwise, animated) anywhere without an option to turn it off.) So, questions are: How to activate smooth scrolling (mouse wheel stepwise, animated) in Okular? Should this bug be closed, because Okular already supports per-pixel scrolling? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384764] Proxy clips on time line play slower than original clips
https://bugs.kde.org/show_bug.cgi?id=384764 krewetki changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||krewe...@interia.pl Latest Commit|v17.08.1-22-g48db9dad9 |v17.08.1-22-g48db9dad9, v ||19.04.0 MLT 6.14.0-5 --- Comment #11 from krewetki --- Hi, I'm not sure what I'm doing with settings/status of this bug, so please forgive mistakes. I'm changing status to CONFIRMED because it happens to me: Manjaro Stable, Kdenlive 19.04.0, MLT 6.14.0-5. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 269376] Annotations should open with suitable size of the box
https://bugs.kde.org/show_bug.cgi?id=269376 --- Comment #2 from David Hurka --- (In reply to Sumit Sahrawat from comment #1) > This is working as it should [...] On my Okular, this does not work. All popup annotations always open same-sized annotation windows. They also open always in the top left corner, even if they hide the annotation itself then. Did it work in 2015? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407437] New: Unable to run Krita after a successful build from source on KDE
https://bugs.kde.org/show_bug.cgi?id=407437 Bug ID: 407437 Summary: Unable to run Krita after a successful build from source on KDE Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: val.hoff...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Follow the official instructions (https://docs.krita.org/en/untranslatable_pages/building_krita.html) 2. After successful build, the binaries will appear under /path/to/kritadev/install (NOTE /path/to/kritadev is what's actually on disk) 3. Move files from /path/to/kritadev/install to ~/kritadev/install 4. execute ./bin/krita OBSERVED RESULT ./bin/krita: error while loading shared libraries: libkritaui.so.18: cannot open shared object file: No such file or directory EXPECTED RESULT Krita should start SOFTWARE/OS VERSIONS Linux / KDE Neon (basically KDE on Ubuntu) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407417] [4.2 alpha] Moving selection is very laggy
https://bugs.kde.org/show_bug.cgi?id=407417 --- Comment #2 from acc4commissi...@gmail.com --- (In reply to vanyossi from comment #1) > Are you on windwows? What specs is your PC? > > Also, does "Canvas GRaphics Acceleration" is enabled in "Settings > > Display"?? If on windows it is best to set to "ANGLE" Yes, CGA is on, and it's even slower with ANGLE. It's actually much faster when the CGA setting is disabled. Kinda weird. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407417] [4.2 alpha] Moving selection is very laggy
https://bugs.kde.org/show_bug.cgi?id=407417 --- Comment #3 from acc4commissi...@gmail.com --- Spec OS : Windows 7 (x64) CPU : Intel(R) Core(TM) i7-2600 VGA : Radeon RX 560 Series RAM : 16G Tablet : Wacom Intuos Pro -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407438] New: Text hinting causes failure to render some texts
https://bugs.kde.org/show_bug.cgi?id=407438 Bug ID: 407438 Summary: Text hinting causes failure to render some texts Product: okular Version: 1.6.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: lu...@aiken.cz Target Milestone: --- Created attachment 119993 --> https://bugs.kde.org/attachment.cgi?id=119993&action=edit Problematic document SUMMARY When text hinting is enabled, Okular fails to render some texts in some documents. STEPS TO REPRODUCE 1. Enable text hinting 2. Open a document 3. Observe rendered texts in the document OBSERVED RESULT In some documents, some texts are not rendered. EXPECTED RESULT All text are rendered as with text hinting disabled. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Kubuntu 19.04 One problematic document is attached. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407439] New: Multiple errors about timeline clips' length and speed fx due to issues with tags management in project file
https://bugs.kde.org/show_bug.cgi?id=407439 Bug ID: 407439 Summary: Multiple errors about timeline clips' length and speed fx due to issues with tags management in project file Product: kdenlive Version: 19.04.0 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: krewe...@interia.pl Target Milestone: --- It seems that Kdenlive has a generic problem with managing tags inside project file. It might be due to project file syntax. When a project file gets over certain size (on my Dell Inspiron 15R SE 10 GB RAM, Manjaro Stable this is approx. 1.6/2.0 MB), Kdenlive struggles keeping up with updating tags when actual clips are moved. I'm experiencing this problem for good few years of using consecutive versions of Kdenlive, this bug was reported at least 3 times, I think I've also seen it reported on forum(s) few times, and nobody seems to be doing anything about it. Solely for that reason I decided to assign higher severity (grave), please correct if that is wrong. https://bugs.kde.org/show_bug.cgi?id=367984 https://bugs.kde.org/show_bug.cgi?id=386877 https://bugs.kde.org/show_bug.cgi?id=392670 I think the main if not only source of those problems is an action of moving clips on timeline. Depending on variation, different results occur: == STEPS TO REPRODUCE - SPEED FX DEFAULTS TO 100% 1. Put clip on timeline 2. Trim beginning 3. Apply speed fx and change value 4. Move that clip on timeline 5. Play or render OBSERVED RESULT - SPEED FX DEFAULTS TO 100% 1. Speed fx setting remains at set value 2. Clip plays from beginngin (ignoring trim) and at 100% EXPECTED RESULT - SPEED FX DEFAULTS TO 100% 1. As above (speed fx setting remains at set value) 2. Clip plays from the trim point and at speed of set % value == STEPS TO REPRODUCE - CLIPS RANDOM SHORTENING OR DUPLICATION 1. Place many clips on timeline (can't determine whether it's the number of clips in project bin, number of clips on timeline, or project file size (i.e. by having very few clips but with lots of effects)) 2. Mark a large number of clips on timeline (can't determine how many) 3. Move those clips 4. OPTIONALLY if project file is not large enough, continue working with project) 5. Attempt to do with clip anything that is related to it's position and length on timeline (i.e. add marker and then try to edit it, add effect with keyframes and setup some keyframes, try to re-trim the clip or move the clip on timeline) OBSERVED RESULT 1 - CLIPS RANDOMLY SHORTENED 1. All moved clips are trimmed massively, sometimes to only few frames 2. All moved clips play from clip start not the trim set by editor OBSERVED RESULT 1 - CLIPS DUPLICATED 1. All moved clips are duplicated and offset in a specific way: an original clip has it's clone stuck back-to-back to it's end on the same track. If one or more of those clips had speed fx added, there will be various errors related to that clip not found and content of these errors will be something like this: no such marker, clip not found, cannot complete this action, etc. EXPECTED RESULT - CLIPS RANDOM SHORTENING OR DUPLICATION 1. All clips are only moved (they remain their trimming and are not duplicated) == SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: this problem seems to occur on various platforms. Mine is Manjaro Stable 18.0, Kdenlive 19.04.0, MLT 6.14.0-5. KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407439] Multiple errors about timeline clips' length and speed fx due to issues with tags management in project file
https://bugs.kde.org/show_bug.cgi?id=407439 --- Comment #1 from krewetki --- I forgot to add: SPEED FX DEFAULTS TO 100% When this happens, disabling Speed Fx for that clip and re-enabling it, usually brings back the trim point at the beginning of the clip (if applicable) and always restores the actual playing/rendering speed of the clip from the defaulted 100% to the value set by editor before the entire operation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 407393] kdeinit5 Signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=407393 Michael Pyne changed: What|Removed |Added CC||mp...@kde.org --- Comment #3 from Michael Pyne --- Seems to be something with the thumbnailer trying to make previews of a media file somewhere. The backtrace points to taglib (a separate library) but I would also think that a thumbnailer crash shouldn't bring down all of kdeinit5. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 407271] KAboutData crashes when using git svn with KWallet
https://bugs.kde.org/show_bug.cgi?id=407271 --- Comment #1 from Michael Pyne --- I suspect some kind of race condition during shutdown, where the global-static tries to delete an already-deleted KAboutData in the registry. I'm having trouble reproducing but I also don't have git-svn setup for kwallet. Based on the platform plugin message I've tried various settings of the environment variable QT_QPA_PLATFORM (xcb, minimal, eglfs) but that hasn't helped me reproduce either. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407440] New: after export to google photo, metadata are written to sidecar files (and perhaps to picture file too)
https://bugs.kde.org/show_bug.cgi?id=407440 Bug ID: 407440 Summary: after export to google photo, metadata are written to sidecar files (and perhaps to picture file too) Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Google Assignee: digikam-bugs-n...@kde.org Reporter: nicolas.houde...@free.fr Target Milestone: --- SUMMARY after export to google photo it seems that metadata are written again, with presumably no change. (i didn't see any) you can see it by activate "write to sidecar files only" STEPS TO REPRODUCE 1. in configure digikam -> metadata -> activate : * read from sidecar file * write to sidecar file * and write to sidecar files only 2. copy some pictures to export, in a directory there should be no sidecar files 3. export picture to google photo OBSERVED RESULT when all the picture are sent metadata are written, and so.. xmp files appears. EXPECTED RESULT i guess this should not happen except if there should be a medata that tell that this picture has been sent to google photo.. (like in picasa i guess) SOFTWARE/OS VERSIONS Linux Mint 19.1, using digikam appimaga 6.1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384729] __libc_freeres inhibits cross-platform valgrind
https://bugs.kde.org/show_bug.cgi?id=384729 --- Comment #3 from John Reiser --- I hit this again today using valgrind-3.15.0 when the default libc on the target platform is glibc-2.29-12.fc30.aarch64 but the actual libc in the target application is from Android 28. __libc_freeres is not defined for all target app environments; therefore __libc_freeres MUST be a WEAK symbol! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405912] Add support for adaptive sync (FreeSync) in KWin for Wayland and X sessions
https://bugs.kde.org/show_bug.cgi?id=405912 --- Comment #8 from Shmerl --- Wayland applications aren't supposed to be restricted to EGL. They can use WSI too (VK_USE_PLATFORM_WAYLAND_KHR and etc.). -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 407441] New: Tried to enable scripts in Amarok and instantly crashed
https://bugs.kde.org/show_bug.cgi?id=407441 Bug ID: 407441 Summary: Tried to enable scripts in Amarok and instantly crashed Product: amarok Version: 2.9.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: bbrann...@gmail.com Target Milestone: kf5 Application: amarok (2.9.0) KDE Platform Version: 4.14.38 Qt Version: 4.8.7 Operating System: Linux 4.15.0-48-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - Custom settings of the application: Tried to enable scripts in Amarok and instantly crashed. now it will not restart instantly gets crash report. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe4d96bbb80 (LWP 25658))] Thread 19 (Thread 0x7fe406697700 (LWP 25680)): #0 0x7fe4d62af03f in __GI___select (nfds=5, readfds=0x7fe4066969c0, writefds=0x0, exceptfds=0x0, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:41 #1 0x7fe4d6a855cf in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fe4d699ae3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fe4d490f6db in start_thread (arg=0x7fe406697700) at pthread_create.c:463 #4 0x7fe4d62b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fe466f7f700 (LWP 25679)): #0 0x7fe4d49159f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fe48c0804cc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe4d49159f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fe48c080478, cond=0x7fe48c0804a0) at pthread_cond_wait.c:502 #2 0x7fe4d49159f3 in __pthread_cond_wait (cond=0x7fe48c0804a0, mutex=0x7fe48c080478) at pthread_cond_wait.c:655 #3 0x7fe4cbe31321 in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #4 0x7fe4cc140cc6 in () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #5 0x7fe4d490f6db in start_thread (arg=0x7fe466f7f700) at pthread_create.c:463 #6 0x7fe4d62b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fe40794f700 (LWP 25675)): #0 0x7fe4cde1a664 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe4cddd3dc9 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4cddd4547 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4cddd46dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe4d6adb22e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7fe4d6aa912f in QEventLoop::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fe4d6aa9495 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fe4d6998549 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fe4d699ae3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fe4d490f6db in start_thread (arg=0x7fe40794f700) at pthread_create.c:463 #10 0x7fe4d62b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fe4648d6700 (LWP 25674)): #0 0x7fe4d62b3839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fe4d6999672 in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7fe4d6995925 in QMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7fe4d16e75cc in Meta::Tag::readTags(QString const&, bool) () at /usr/lib/libamarokshared.so.1 #4 0x7fe4d8f44f1b in MetaFile::Track::Private::readMetaData() () at /usr/lib/libamaroklib.so.1 #5 0x7fe4d8f46ec4 in MetaFile::Track::Track(KUrl const&) () at /usr/lib/libamaroklib.so.1 #6 0x7fe4d8f4c0e8 in FileTrackProvider::trackForUrl(KUrl const&) () at /usr/lib/libamaroklib.so.1 #7 0x7fe4d8f8b0df in CollectionManager::trackForUrl(KUrl const&) () at /usr/lib/libamaroklib.so.1 #8 0x7fe4d8f586ef in () at /usr/lib/libamaroklib.so.1 #9 0x7fe4d191bc8c in () at /usr/lib/libthreadweaver.so.4 #10 0x7fe4d191bea5 in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () at /usr/lib/libthreadweaver.so.4 #11 0x7fe4d191b533 in ThreadWeaver::Thread::run() () at /usr/lib/libthreadweaver.so.4 #12 0x7fe4d699ae3c in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7fe4d490f6db in start_thread (arg=0x7fe4648d6700) at pthread_create.c:463 #14 0x7fe4d62b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fe4650d7700 (LWP 25673)): #0 0x7fe4d49159f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fe4ccba0698) at ../sysdeps/unix/sysv/linux/futex-internal.h
[dolphin] [Bug 394649] FTP cannot paste into current *empty* folder
https://bugs.kde.org/show_bug.cgi?id=394649 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406458] Krita won't start on mobile station
https://bugs.kde.org/show_bug.cgi?id=406458 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391303] Crash while pasting files from clipboard
https://bugs.kde.org/show_bug.cgi?id=391303 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 394375] Kate crashes when undoing a file restoration
https://bugs.kde.org/show_bug.cgi?id=394375 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403288] Skips animation key frame when using shortcuts
https://bugs.kde.org/show_bug.cgi?id=403288 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406978] Unable to browse filesystem: primary does not exist
https://bugs.kde.org/show_bug.cgi?id=406978 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399618] Mouse forward does not work in Docker images
https://bugs.kde.org/show_bug.cgi?id=399618 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407380] Softness sensor does nothing when using a predefined brush tip
https://bugs.kde.org/show_bug.cgi?id=407380 Brendan changed: What|Removed |Added Summary|Softness sensor does|Softness sensor does |nothing |nothing when using a ||predefined brush tip --- Comment #5 from Brendan --- Well I'll be damned, I'm not sure how I missed that. Updating the bug report now. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406786] Appimage doesn't have "breeze" style"
https://bugs.kde.org/show_bug.cgi?id=406786 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from emohr --- Goto: settings -> tick „force breeze icon theme“. Kdenlive restarts and you should see the icons. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406785] Layout keeps re-sizing after I attempt to adjust it [video example included]
https://bugs.kde.org/show_bug.cgi?id=406785 --- Comment #4 from emohr --- Do you have deleted ~/.config/kdenlive-appimagerc as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406439] plasma shell crashes on startup if using a panel with system tray
https://bugs.kde.org/show_bug.cgi?id=406439 Christoph Feck changed: What|Removed |Added Severity|major |crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407411] color
https://bugs.kde.org/show_bug.cgi?id=407411 Antonio Rojas changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||aro...@archlinux.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher
https://bugs.kde.org/show_bug.cgi?id=391613 Christoph Feck changed: What|Removed |Added CC||mgarze...@hotmail.com --- Comment #41 from Christoph Feck --- *** Bug 406459 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406459] Plasma crashed
https://bugs.kde.org/show_bug.cgi?id=406459 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 391613 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407304] crash scolling through application launcher/menu
https://bugs.kde.org/show_bug.cgi?id=407304 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 391613 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher
https://bugs.kde.org/show_bug.cgi?id=391613 Christoph Feck changed: What|Removed |Added CC||ratrace...@gmail.com --- Comment #42 from Christoph Feck --- *** Bug 407304 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407415] New: Crashed task bar on using search application
https://bugs.kde.org/show_bug.cgi?id=407415 Bug ID: 407415 Summary: Crashed task bar on using search application Product: plasmashell Version: 5.14.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gandrew...@ya.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.4) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.15.0-desktop-47.2rosa-x86_64 x86_64 Distribution: "ROSA Desktop Fresh R11" -- Information about the crash: - What I was doing when the application crashed: I pressed the start button ( with the kde logo ) in the search bar for applications to run started writing clementine. After entering "cl" in the search crashed and lost the task bar - Unusual behavior I noticed: The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc0d319d800 (LWP 5386))] Thread 15 (Thread 0x7fc043fff700 (LWP 19232)): #0 0x7fc0c9e0cb60 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0cd025146 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc094ee4678 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc094ee8418 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc094ee3869 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc094ee61ef in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc0cd024b20 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc0c9e0755a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc0cc942e5f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fc060dea700 (LWP 19231)): #0 0x7fc0c9e0cb60 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0cd025146 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc094ee4678 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc094ee8418 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc094ee3869 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc094ee61ef in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc0cd024b20 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc0c9e0755a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc0cc942e5f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fc0615eb700 (LWP 19230)): #0 0x7fc0c9e0cb60 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0cd025146 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc094ee4678 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc094ee8418 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc094ee3869 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc094ee61ef in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc0cd024b20 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc0c9e0755a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc0cc942e5f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fc061dec700 (LWP 19229)): #0 0x7fc0c9e0cb60 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0cd025146 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc094ee4678 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc094ee8418 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc094ee3869 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc094ee61ef in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc0cd024b20 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc0c9e0755a in start_thread () at /lib64/libpthread.so.0 #8 0x7fc0cc942e5f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fc0625ed700 (LWP 19227)): #0 0x7fc0c9e0cb60 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0cd025146 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.s
[plasmashell] [Bug 407415] Crashed task bar on using search application
https://bugs.kde.org/show_bug.cgi?id=407415 Andrey changed: What|Removed |Added Platform|unspecified |ROSA RPMs -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406975] Split clips aren't saved with the project
https://bugs.kde.org/show_bug.cgi?id=406975 emohr changed: What|Removed |Added Flags||Brainstorm+ Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from emohr --- I opended issue: https://invent.kde.org/kde/kdenlive/issues/184 Do you test this with the AppImage? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407210] Partition manager gets stuck when scanning for partitions on a drive containing a partition with jfs
https://bugs.kde.org/show_bug.cgi?id=407210 mthw0 changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #2 from mthw0 --- sudo jfs_debugfs /dev/sdb1 jfs_debugfs version 1.1.15, 04-Mar-2011 Aggregate Block Size: 4096 > dm Block allocation map control page at block 16 [1] dn_mapsize: 0x074c3e3 [9] dn_agheigth:1 [2] dn_nfree: 0x074c01b [10] dn_agwidth:2 [3] dn_l2nbperpage: 0 [11] dn_agstart:85 [4] dn_numag: 117 [12] dn_agl2size: 16 [5] dn_maxlevel:0 [13] dn_agfree: type 'f' [6] dn_maxag: 0 [14] dn_agsize: 65536 [7] dn_agpref: 0 [15] pad: Not Displayed [8] dn_aglevel: 0 display_dbmap: [m]odify, [f]ree count, [t]ree, e[x]it > x > q On first glance, I can't see anything wrong with this. Program starts normally, operates normally (no slowdowns or anything) and exits normally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406478] Show latest program window thumbnail in taskbar
https://bugs.kde.org/show_bug.cgi?id=406478 Christoph Feck changed: What|Removed |Added Product|frameworks-plasma |kwin Component|components |compositing Assignee|notm...@gmail.com |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407351] i18n ARGUMENT MISSING in task preview window
https://bugs.kde.org/show_bug.cgi?id=407351 --- Comment #4 from Michail Vourlakos --- very strange situation, I thought it would be easily fixable but I must need to investigate the codepath followed in order to find out where it breaks.. it has also one more issue... A. 1. add a second instance of dolphin 2. assign the second dolphin ONLY to the second desktop 3. watch out the dolphin preview, it shows for both Dolphins both Desktops even though it should not B. keeping compatibility with VDs before <= Plasma 5.14 it is going to be a challenge I dont think it wont add clutter and I dont think I will try very hard to succeed keeping compatibility with older plasma versions than 5.15 for this subtext -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407391] Project bin show white squares for some videos in thumbnails
https://bugs.kde.org/show_bug.cgi?id=407391 emohr changed: What|Removed |Added Flags||timeline_corruption+ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407391] Project bin show white squares for some videos in thumbnails
https://bugs.kde.org/show_bug.cgi?id=407391 emohr changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #2 from emohr --- Created attachment 119974 --> https://bugs.kde.org/attachment.cgi?id=119974&action=edit white clip in bin I uploaded your screenshot here. I see you have other clips which are more than 1hour long. - Is your HD full? - Try the AppImage instead of the Flatpack. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work on Gnome Shell using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 Michi changed: What|Removed |Added CC||wosk...@yahoo.de --- Comment #5 from Michi --- this is not limited to gnome! I have the exact same issue with kwin/wayland. With kwin/X11 backend it's working though. bye Michi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 Michi changed: What|Removed |Added Summary|Mouse remote control does |Mouse remote control does |not work on Gnome Shell |not work using Wayland |using Wayland | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407408] krita crash from ubuntu19.04-KDE-AMDGPU
https://bugs.kde.org/show_bug.cgi?id=407408 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||b...@valdyas.org --- Comment #6 from Boudewijn Rempt --- There's nothing strange here. I've been saying for months that using distribution packages with Qt 5.12 means instant crashes if you use a tablet. There's a bug in Qt 5.12 that we've worked around in Krita 4.1.8. Apparently, the Ubuntu people haven't noticed that yet. *** This bug has been marked as a duplicate of bug 401988 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401988] Crash on touching graphic tablet pen on canvas
https://bugs.kde.org/show_bug.cgi?id=401988 Boudewijn Rempt changed: What|Removed |Added CC||folmare.darken@protonmail.c ||om --- Comment #26 from Boudewijn Rempt --- *** Bug 407408 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407412] krita often crashes or has slow load time. will not respond to brush strokes, no lines at all.
https://bugs.kde.org/show_bug.cgi?id=407412 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |NOT A BUG --- Comment #1 from Boudewijn Rempt --- Sorry, as a bug report this is useless. You are not providing any information whatsoever for someting that is specific for your system and the way you work. Next time, report one issue per report. Provide information about the system you're working on (see help/system information for bug reports). Provide information about the images you're working on. Provide the steps to reproduce the issues you report. Provide a screencast if you cannot manage to explain what you're doing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407281] Clips not playing anymore in 19.04.0
https://bugs.kde.org/show_bug.cgi?id=407281 emohr changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||fritzib...@gmx.net --- Comment #2 from emohr --- Thanks for reporting and feedback. Glad to hear it works. It seems it works. We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407270] When I change MLT's "Processing threads" option, Timeline cursor doesn't move.
https://bugs.kde.org/show_bug.cgi?id=407270 emohr changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||fritzib...@gmx.net --- Comment #1 from emohr --- Thanks for reporting. Issue known. Processing thread more than 1 doesn’t work as MLT can’t run in multi-threading. We close this bug as it is a upstream problem (problem inside MLT an not inside Kdenlive). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407347] 4.2 alpha fails to build with -GNinja
https://bugs.kde.org/show_bug.cgi?id=407347 --- Comment #6 from Boudewijn Rempt --- -DBUILD_TESTING=OFF is all that's needed for me to disable the tests. As for the benchmarks, I just checked and they built fine for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 395181] Crash in KCharSelect [assert "index out of range"]
https://bugs.kde.org/show_bug.cgi?id=395181 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|ASSIGNED|RESOLVED --- Comment #5 from Christoph Feck --- Fix accepted upstream. Thanks, David! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 406242] fstab-mounted NFS drive gets two entries in Places panel
https://bugs.kde.org/show_bug.cgi?id=406242 Méven Car changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #6 from Méven Car --- $ cat /etc/fstab 192.168.1.16:/home/meven/ /media/NFS nfs defaults,user,auto,noatime,bg 0 0 $ cat /proc/mounts 192.168.1.16:/home/meven /media/NFS nfs4 rw,nosuid,nodev,noexec,noatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.17,local_lock=none,addr=192.168.1.16 0 0 And to reiterate : $ solid-hardware list [...] udi = '/org/kde/fstab/192.168.1.16:/home/meven/' udi = '/org/kde/fstab/192.168.1.16:/home/meven' Based on reading the code I deduced that Solid::Backends::Fstab::FstabHandling::_k_updateMtabMountPointsCache does not match the device because they end up with different udi. Reviewing my settings I noticed that my remote export folder ends with a slash. And indeed once I removed the slash in my config the issue does not occur anymore. So my previous patch seems irrelevant and what we need would be to strip last slashes out of path read from /etc/fstab. Does it make sense ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407416] New: Timeline 'Remove Layer' option does in fact delete the layer
https://bugs.kde.org/show_bug.cgi?id=407416 Bug ID: 407416 Summary: Timeline 'Remove Layer' option does in fact delete the layer Product: krita Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY When you use the top left icon in the Timeline docker to 'Add Existing Layer' to the timeline then the obvious matching/complementary action is to remove it from the timeline (but not to delete it from the image which is what happens). STEPS TO REPRODUCE 1. In the Timeline docker, right click a layer (or click the small icon next to the audio icon at the top of the layer list) and click the Remove Layer option. OBSERVED RESULT The layer is deleted from the image. EXPECTED RESULT The layer should be removed from the timeline docker but not deleted from the image. SOFTWARE/OS VERSIONS All versions. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406535] plasmashell crashing with freebsd, with kill Xorg and sddm again....
https://bugs.kde.org/show_bug.cgi?id=406535 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Christoph Feck --- Requested information was provided with comment #2; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406596] error to build kwin since commit 6e1655e3cce082b2e7d0daf21dc58bbe3d4524f2
https://bugs.kde.org/show_bug.cgi?id=406596 --- Comment #7 from Christoph Feck --- *** Bug 406686 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360475] Open in file manager for individual images
https://bugs.kde.org/show_bug.cgi?id=360475 vaab changed: What|Removed |Added CC||valentin.lab_kde.org@kalyst ||o.org --- Comment #13 from vaab --- in 6.1.0 it works on Album View, so I don't understand what is the problem to simply do the same action that already works on album context menu. If the trouble is to figure out how to focus properly the file in the file browser, this is really optional and should not delay the implementation of this feature on thumbnail's context menu. This feature is also very essential to any people using other views than Album view. I'm talking about people, date, tags views. To be honest, it makes more sense to me on the photo thumbnail's context menu than lost in the album view's pane, in the album's context menu. To add insult to injury, if your directory path is a little long, you can't even see in one glance where the file is located as you can't display it in tooltip for some reason, and in the left file property pane, because not wide enough, it'll be covered by "..." continuation string. So even access to path information is really cumbersome. File path is an important information for any people caring about independence from the management tool. Independence is the most important feature I'm looking for in any photo manager soft. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406686] The kwin plugin qpa don't build
https://bugs.kde.org/show_bug.cgi?id=406686 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 406596 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405317] Cannot find file just created in home directory
https://bugs.kde.org/show_bug.cgi?id=405317 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #26 from Christoph Feck --- New information was provided with comment #23; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher
https://bugs.kde.org/show_bug.cgi?id=391613 Christoph Feck changed: What|Removed |Added CC||gandrew...@ya.ru --- Comment #43 from Christoph Feck --- *** Bug 407415 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407415] Crashed task bar on using search application
https://bugs.kde.org/show_bug.cgi?id=407415 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 391613 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407417] New: [4.2 alpha~] Moving selection is very laggy
https://bugs.kde.org/show_bug.cgi?id=407417 Bug ID: 407417 Summary: [4.2 alpha~] Moving selection is very laggy Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- Created attachment 119975 --> https://bugs.kde.org/attachment.cgi?id=119975&action=edit gif recording of the problem SUMMARY git 89de24c It's been this way since it was first implememted but I thought it was just a performance problem due to its early stage of development. But I saw the introduction video(https://www.youtube.com/watch?v=gWv--Do9L0E) and it seemed very smoother then it was in my PC. + And is it also a bug that I have to move the cursor to its border to move the selection? It also seems different in the video. Maybe I'm missing something. I wouldn't know. STEPS TO REPRODUCE 1. Make a selection. 2. Try to move it. 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.
[krita] [Bug 407416] Timeline 'Remove Layer' option does in fact delete the layer
https://bugs.kde.org/show_bug.cgi?id=407416 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Yes, this is quite wrong... Remove layer also seems confused about which layer gets removed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407417] [4.2 alpha] Moving selection is very laggy
https://bugs.kde.org/show_bug.cgi?id=407417 acc4commissi...@gmail.com changed: What|Removed |Added Summary|[4.2 alpha~] Moving |[4.2 alpha] Moving |selection is very laggy |selection is very laggy -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407418] New: Rotoscoping interpolation precision
https://bugs.kde.org/show_bug.cgi?id=407418 Bug ID: 407418 Summary: Rotoscoping interpolation precision Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: vincent.lelige...@gmail.com Target Milestone: --- Created attachment 119976 --> https://bugs.kde.org/attachment.cgi?id=119976&action=edit Project file SUMMARY STEPS TO REPRODUCE 1. Create a rotoscoping effect over a short period of time that moves (keyframed) 2. Create a moving effect that do the same OBSERVED RESULT They do not move at the same speed, and the rotoscoping effect has a small jump at the ending keyframe EXPECTED RESULT Rotoscoping should be moving smoothly SOFTWARE/OS VERSIONS Latest Git ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407418] Rotoscoping interpolation precision
https://bugs.kde.org/show_bug.cgi?id=407418 --- Comment #1 from Vincent Le Ligeour --- Created attachment 119977 --> https://bugs.kde.org/attachment.cgi?id=119977&action=edit Rendering video with problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406620] Digital clock calendar does not show PIM events after reboot
https://bugs.kde.org/show_bug.cgi?id=406620 Christoph Feck changed: What|Removed |Added Component|Digital Clock |Calendar -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 406485] KDE forgets my display settings after reboot
https://bugs.kde.org/show_bug.cgi?id=406485 Christoph Feck changed: What|Removed |Added Assignee|plasma-b...@kde.org |se...@kde.org Component|general |common Product|systemsettings |KScreen -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360475] Open in file manager for individual images
https://bugs.kde.org/show_bug.cgi?id=360475 --- Comment #14 from Maik Qualmann --- The problem with tags, search views, is that items with different paths may be present. If you then select 100 items and run "Open in File Manager", then 100 File Manager windows will be opened at once. This possibility should then be limited to a single selection. Maik -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407414] Partition Manager shows no disk information
https://bugs.kde.org/show_bug.cgi?id=407414 --- Comment #1 from Andrius Štikonas --- Might be packaging bug. Can you open Slackware bug and post a link here? It looks like DBus permissions issue. kpmcore installs the following files: /etc/dbus-1/system.d/org.kde.kpmcore.applicationinterface.conf /etc/dbus-1/system.d/org.kde.kpmcore.externalcommand.conf /etc/dbus-1/system.d/org.kde.kpmcore.helperinterface.conf and it seems to work on all other distros. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 406685] KDE Instability of application termination
https://bugs.kde.org/show_bug.cgi?id=406685 --- Comment #1 from Christoph Feck --- If KTorrent is already running, does clicking on its system tray icon show the window? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407419] New: Plasmashell crashes often when copying files from network locations (Wayland)
https://bugs.kde.org/show_bug.cgi?id=407419 Bug ID: 407419 Summary: Plasmashell crashes often when copying files from network locations (Wayland) Product: plasmashell Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: m...@rainer-finke.de Target Milestone: 1.0 Plasmashell is crashing often when copying files from network locations on Wayland. STEPS TO REPRODUCE 1. Copy files from or to network locations OBSERVED RESULT: crash of plasmashell EXPECTED RESULT: plasmashell will just work SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.13-arch1-1-ARCH OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 407315] "Replace All" does not work using keyboard
https://bugs.kde.org/show_bug.cgi?id=407315 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=406592 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 406592] Accelerator conflict with "warnings" and "replace all"
https://bugs.kde.org/show_bug.cgi?id=406592 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=407315 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406478] Show latest program window thumbnail in taskbar
https://bugs.kde.org/show_bug.cgi?id=406478 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Martin Flöser --- I'm sorry but you misunderstood the option and who is involved. KWin is not involved at all in taskbar thumbnails. This is completely handled by Plasma without KWin having anything to do. Furthermore the setting has no influence on Alt+Tab. If you want games to stop playing sounds report a bug against them to stop playing sounds when not active. We cannot control or influence the behavior of games. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407408] krita crash from ubuntu19.04-KDE-AMDGPU
https://bugs.kde.org/show_bug.cgi?id=407408 --- Comment #7 from thikedgatefoxe --- (In reply to Boudewijn Rempt from comment #6) Well, I think that is quite dangerous to KDE users. Because our system is a plasma desktop using ubuntu 19.04 and kubuntu-backport, but the crash is happening. I think that crash report will increase if it is not updated early from 4.1.7 to 4.1.8. but Well that's not something we care about. I will use appimage for now. thanks. -- You are receiving this mail because: You are watching all bug changes.
