[kdev-python] [Bug 379961] Wrong type for 'or' operator expression
https://bugs.kde.org/show_bug.cgi?id=379961 Nicolás Alvarez changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|m...@svenbrauch.de |nicolas.alva...@gmail.com --- Comment #1 from Nicolás Alvarez --- Bah. Replace 'b' with 'x' in the explanation. Also, I almost fixed this myself. Will submit patch tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379963] Play button crashes in macOS
https://bugs.kde.org/show_bug.cgi?id=379963 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Please check the 3.1.4 alpha; I think we just fixed this issue. https://download.kde.org/unstable/krita/3.1.4-alpha.1/ -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368605] RTL Lang - the range line reversed
https://bugs.kde.org/show_bug.cgi?id=368605 --- Comment #7 from Hugo Pereira Da Costa --- It is related to Quick controls. Does not happen with standard widgets. What seems to happen is that the input to the widgets properly handle r-to-l layout, but not the rendering. I can change breeze to make the widget look r-to-l oriented so that the handle stays below the mouse, and the blue area appear on the right (as opposed to the left), although the issue is really inside Qt (QCommonStyle). Andd then, still, the guy continues to behave incorrectly: 0% is on the left, 100% is on the right -> not inverted. So the issue is further upstream. And not in breeze. In QtCurve (just checked), the bug does not seem present, but here it seems to be because the widget is not right-to-left inverted at all (though I'm unclear as to why it behaves differently from breeze) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379658] Widget location in panel not saving on logout
https://bugs.kde.org/show_bug.cgi?id=379658 --- Comment #1 from Joshua Dodd --- Fixed it by adding a spacer. Not really too obvious to do though, since you would think the widgets would stay where you put them. Not sure if this is even a bug or not, I will keep this as unconfirmed for now. If it's not a bug you can close this. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] New: Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 Bug ID: 379964 Summary: Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails Product: ark Version: 17.04.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: sun...@hotmail.ru CC: rthoms...@gmail.com Target Milestone: --- Here https://bugs.kde.org/show_bug.cgi?id=353266 it says it was fixed downstream long ago. Its not fixed nowadays, i can still reproduce this bug in Ark Version 17.04.1 with the same file. Ubuntu patches had nothing to do with it, i am using Manjaro to open archive you can see here https://bugs.kde.org/show_bug.cgi?id=353266 in attachments -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 --- Comment #1 from sun...@hotmail.ru --- Also i can unzip file using unzip tool (unzip test.zip) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379965] New: Plasnashell crash on applications switch
https://bugs.kde.org/show_bug.cgi?id=379965 Bug ID: 379965 Summary: Plasnashell crash on applications switch Product: plasmashell Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mich...@bertuccioli.me CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.8.0-52-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: randomly on application switch, clicking on the taskbar, plasmashell crashed and than restart. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f00a7c138c0 (LWP 2361))] Thread 13 (Thread 0x7effc569f700 (LWP 4563)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f00a2c5a9fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x28f4010) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x2a6fd58, mutex=mutex@entry=0x2a6fd50, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f00a5c7c47d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x2a6fd48) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2a6fcd0) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f00a5c7cd55 in QSGRenderThread::run (this=0x2a6fcd0) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f00a2c59b48 in QThreadPrivate::start (arg=0x2a6fcd0) at thread/qthread_unix.cpp:368 #7 0x7f00a1aff6ba in start_thread (arg=0x7effc569f700) at pthread_create.c:333 #8 0x7f00a256682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7effc73ef700 (LWP 4245)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f00a2c5a9fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x296a800) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x29aa738, mutex=mutex@entry=0x29aa730, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f00a5c7c47d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x29aa728) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x29aa6b0) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f00a5c7cd55 in QSGRenderThread::run (this=0x29aa6b0) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f00a2c59b48 in QThreadPrivate::start (arg=0x29aa6b0) at thread/qthread_unix.cpp:368 #7 0x7f00a1aff6ba in start_thread (arg=0x7effc73ef700) at pthread_create.c:333 #8 0x7f00a256682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7effc6bee700 (LWP 3159)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f00a2c5a9fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1f5dc50) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x28f0a08, mutex=mutex@entry=0x28f0a00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f00a5c7c47d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x28f09f8) at scenegraph/qsgthreadedrenderloop.cpp:242 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x28f0980) at scenegraph/qsgthreadedrenderloop.cpp:690 #5 0x7f00a5c7cd55 in QSGRenderThread::run (this=0x28f0980) at scenegraph/qsgthreadedrenderloop.cpp:719 #6 0x7f00a2c59b48 in QThreadPrivate::start (arg=0x28f0980) at thread/qthread_unix.cpp:368 #7 0x7f00a1aff6ba in start_thread (arg=0x7effc6bee700) at pthread_create.c:333 #8 0x7f00a256682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7effcd4f0700 (LWP 2830)): [KCrash Handler] #6 0x7efffad9eaa4 in ?? () from /usr/lib/nvidia-381/libnvidia-glcore.so.381.22 #7 0x7f00a5c3bc58 in QOpenGLFunctions::glVertexAttribPointer (ptr=, stride=0, normalized=0 '\000', type=5126, size=1, indx=, this=0x7effc013f058) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qopenglfunctions.h:2166 #8 QSGBatchRenderer::Renderer::renderMergedBatch (this=0x7effc013ef80, batch=0x7effc02367f0) at scenegraph/coreapi/qsgbatchrenderer.cpp:2336 #9 0x7f00a5c3c645 in QSGBatchRender
[frameworks-kio] [Bug 371278] Dolphin crashed when opening smb location
https://bugs.kde.org/show_bug.cgi?id=371278 Elvis Angelaccio changed: What|Removed |Added CC||e.walker@clansmandynamics.c ||om --- Comment #4 from Elvis Angelaccio --- *** Bug 379953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379953] Dolphin crash when Adding Windows 2008 R2 SMB share
https://bugs.kde.org/show_bug.cgi?id=379953 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||elvis.angelac...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 371278 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 371278] Dolphin crashed when opening smb location
https://bugs.kde.org/show_bug.cgi?id=371278 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Component|general |default Product|frameworks-kio |kio-extras Version|5.29.0 |unspecified Assignee|fa...@kde.org |plasma-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] New: WARNING: unhandled syscall: 313
https://bugs.kde.org/show_bug.cgi?id=379966
Bug ID: 379966
Summary: WARNING: unhandled syscall: 313
Product: valgrind
Version: unspecified
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: bartekg...@gmail.com
Target Milestone: ---
There's no such syscall on x86_64. Seems to be triggered when the process tries
to check the state of a loadable kernel module:
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
open("/sys/module/gpio_mockup/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 6324
read(65530, "Z", 1) = 1
stat("/sys/module/gpio_mockup", 0xffefff220) = -1 ENOENT (No such file or
directory)
getpid()= 6324
write(65529, "--6324-- WARNING: unhandled sysc"..., 41--6324-- WARNING:
unhandled syscall: 313
) = 41
In order to reproduce:
1. Clone https://github.com/brgl/libgpiod
2. Build the test suite (refer to README)
3. Run the test suite under memcheck (must run tests/.libs/gpiod-test, not the
libtool wrapper in tests/)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled syscall: 313
https://bugs.kde.org/show_bug.cgi?id=379966 Bartosz Golaszewski changed: What|Removed |Added CC||bartekg...@gmail.com Version|unspecified |3.13 SVN -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled syscall: 313
https://bugs.kde.org/show_bug.cgi?id=379966 Bartosz Golaszewski changed: What|Removed |Added Latest Commit||r16395 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] [libzip] Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 Elvis Angelaccio changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|rthoms...@gmail.com Component|general |plugins Summary|Opening zip archives with |[libzip] Opening zip |streaming (general purpose |archives with streaming |bit 3) and/or zip64 enabled |(general purpose bit 3) |fails |and/or zip64 enabled fails Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||elvis.angelac...@kde.org --- Comment #2 from Elvis Angelaccio --- Thanks for the report, it seems libzip cannot open the file. Workaround: disable the libzip plugin in Settings -> Configure Ark -> Plugin Settings -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379172] Craft installation instructions should not modify global execution policy.
https://bugs.kde.org/show_bug.cgi?id=379172 Thomas Friedrichsmeier changed: What|Removed |Added Resolution|--- |FIXED CC||thomas.friedrichsmeier@ruhr ||-uni-bochum.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Thomas Friedrichsmeier --- Good suggestion. I've changed this. -- Did you try "Login with Phabricator" in the "Personal Tools" sidebar? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379967] New: Chrash after searching in start menu
https://bugs.kde.org/show_bug.cgi?id=379967 Bug ID: 379967 Summary: Chrash after searching in start menu Product: plasmashell Version: 5.9.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: fab...@web2.0-apps.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.95) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.10.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Every time I search in the start menu, no matter for what, plasma shell crashes and restarts. Im using the cascading menu. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ba3b1b8c0 (LWP 17677))] Thread 18 (Thread 0x7f4a7700 (LWP 20309)): #0 0x7f4b9c7979a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4b9d8e137b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f4ac5ace07b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) (this=, th=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:594 #3 0x7f4ac5acee60 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) (this=0x5527c20, th=, th@entry=0x7f4a88002b90, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:554 #4 0x7f4ac5ad3018 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) (this=0x6735480, th=0x7f4a88002b90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/workinghardstate.cpp:66 #5 0x7f4ac5acdfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) (this=, th=0x7f4a88002b90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:568 #6 0x7f4ac5ad3072 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) (this=0x6735480, th=0x7f4a88002b90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/workinghardstate.cpp:73 #7 0x7f4ac5acdfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) (this=, th=0x7f4a88002b90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:568 #8 0x7f4ac5ad0ea9 in ThreadWeaver::Thread::run() (this=0x7f4a88002b90) at /usr/src/debug/threadweaver-5.34.0/src/thread.cpp:103 #9 0x7f4b9d8e04c8 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f4b9c791537 in start_thread () at /lib64/libpthread.so.0 #11 0x7f4b9d1eb04f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f4a9cff9700 (LWP 20308)): #0 0x7f4b9c7979a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4b9d8e137b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f4ac5ace07b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*) (this=, th=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:594 #3 0x7f4ac5acee60 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) (this=0x5527c20, th=, th@entry=0x7f4a94002f90, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:554 #4 0x7f4ac5ad3018 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) (this=0x6735480, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/workinghardstate.cpp:66 #5 0x7f4ac5acdfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) (this=, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:568 #6 0x7f4ac5ad3072 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) (this=0x6735480, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/workinghardstate.cpp:73 #7 0x7f4ac5acdfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) (this=, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:568 #8 0x7f4ac5ad3072 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) (this=0x6735480, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/workinghardstate.cpp:73 #9 0x7f4ac5acdfdd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) (this=, th=0x7f4a94002f90, wasBusy=) at /usr/src/debug/threadweaver-5.34.0/src/weaver.cpp:568 #10 0x7f4ac5ad0e
[frameworks-baloo] [Bug 375780] Krunner crashes after search
https://bugs.kde.org/show_bug.cgi?id=375780 --- Comment #4 from Fabian --- For me it seems like the problem got resolved. Krunner didn't crash while search for quite some time. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 181145] Lokalize cannot create the mo files
https://bugs.kde.org/show_bug.cgi?id=181145 --- Comment #26 from Daniele Scasciafratte --- Thank you so much! I modified based on my new needs and I shared on https://github.com/Mte90/Script/tree/master/lokalize Actually is not running on save of the po file but is better now than before without this script. Also I saw on debian that the folder inside my home folder is not reconize but only the root one on Debian. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339752] enable max protocol SMB3
https://bugs.kde.org/show_bug.cgi?id=339752 Per Pomsel changed: What|Removed |Added CC||phant...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 341514] Dolphin fails to mount CIFS 3 share
https://bugs.kde.org/show_bug.cgi?id=341514 Per Pomsel changed: What|Removed |Added CC||phant...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 --- Comment #4 from Eike Hein --- Basically the reason is that the data round trip is broken between the model and the applet. The launcherList() getter returns a list built from d->launchersOrder, but the setLauncherList() setter builds a new d->launchersOrder from what's passed in, and on a move(), the applet passes in a new list based on what it sees after filtering by activity. The result is that the launchers specific to activities other than the current activity get dropped. The change signal is emitted, and a new list from the getter sans them is written to the config. To sum it up, if you have activity-specific launchers on an activity different from the current one, reordering launchers in the currenty activity will remove them. This is not a regression in this dev cycle, this bug was introduced with per-activity launchers in 5.9.0 and is a design oversight in the code. We can't make setLauncherList() implicitly activity-specific because we need a setter for the full list to reload it from config. We need a setLauncherListCurrentActivity() that's smart enough to do a merge. Ivan, can you write this? You solved the same problem for Kicker-based launchers so you presumably have a preferred way now. I'd like to see consistent behavior between the interfaces, if possible/desirable, and I'm not exactly sure what policy decisions you made on the launcher menus side for this case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 --- Comment #5 from Eike Hein --- BTW: Keep in mind 5.10 final tagging is soon; while this is not a regression it is serious and I'd like to see it addressed it in that release still, if possible. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 --- Comment #19 from Ivo Raisr --- And follow up VEX commit in SVN r3376. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Hugo Pereira Da Costa changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/bre ||eze/760cc2b71d544c8084f278b ||c2d6eb7cfa576b864 Resolution|--- |FIXED --- Comment #15 from Hugo Pereira Da Costa --- Git commit 760cc2b71d544c8084f278bc2d6eb7cfa576b864 by Hugo Pereira Da Costa. Committed on 18/05/2017 at 10:03. Pushed by hpereiradacosta into branch 'master'. set a mask to shadow widget to make sure that it does not overlap with the mdi window. M +10 -2kstyle/breezemdiwindowshadow.cpp https://commits.kde.org/breeze/760cc2b71d544c8084f278bc2d6eb7cfa576b864 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 --- Comment #16 from Hugo Pereira Da Costa --- Previous commit fixes the issue for me. I will backport to plasma 5.10. Don't hesitate to reopen if the problem reappears after that. best, Hugo -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 Mark Wielaard changed: What|Removed |Added Summary|WARNING: unhandled syscall: |WARNING: unhandled syscall: |313 |313 (finit_module) CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- That is the finit_module which loads a kernel module from a file descriptor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379968] New: plasmashell crashes if adding cpu usage monitor to control panel
https://bugs.kde.org/show_bug.cgi?id=379968 Bug ID: 379968 Summary: plasmashell crashes if adding cpu usage monitor to control panel Product: plasmashell Version: 5.9.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: michv...@gmx.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.9.27-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Add cpu usage monitor plasmaoid (not sure if the correct english name) to the control panel after if was added to desktop Does not occur if added straight to control panel after reproduced this 2 or 3 times, plasmashell wont recover. Screen stays black The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39dc890800 (LWP 14426))] Thread 29 (Thread 0x7f38ccba6700 (LWP 4535)): #0 0x7f39d5504756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39d664a58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f39da3a2665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f39da3a2f72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f39d66496d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f39d54fe2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f39d5f5c54f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f38937fe700 (LWP 3847)): #0 0x7f39d5504756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39d664a58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f391ac351d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f391ac399d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f391ac39a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f391ac37249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f39d66496d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f39d54fe2e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f39d5f5c54f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f3893fff700 (LWP 3846)): #0 0x7f39d5504756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39d664a58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f391ac351d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f391ac399d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f391ac39a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f391ac37249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f39d66496d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f39d54fe2e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f39d5f5c54f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f38a8d7e700 (LWP 3845)): #0 0x7f39d5504756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f39d664a58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f391ac351d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f391ac399d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f391ac39a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f391ac39a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f391ac34263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9
[krita] [Bug 379969] New: Transparancy Mask Disappear
https://bugs.kde.org/show_bug.cgi?id=379969 Bug ID: 379969 Summary: Transparancy Mask Disappear Product: krita Version: 3.1.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: mifuk...@gmail.com Target Milestone: --- When saves file with .ora, transparancy mask disappear in the next file open, completely delete any area with "black-painted" part inside the "marked" layer. *englsih isn't my primary language* -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 346139] add "local or outdated packages"
https://bugs.kde.org/show_bug.cgi?id=346139 林博仁 changed: What|Removed |Added CC||buo.ren@gmail.com --- Comment #1 from 林博仁 --- Probably duplicate of #335884 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 Ｖ字龍(Vdragon) changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Ｖ字龍(Vdragon) --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 --- Comment #2 from Bartosz Golaszewski --- Right, I checked the wrong file. It's in /usr/include/x86_64-linux-gnu/asm/unistd_64.h on Debian. I'll try to create a wrapper for this syscall. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361943] systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed
https://bugs.kde.org/show_bug.cgi?id=361943 --- Comment #3 from Cristiano Guadagnino --- Just a little addition: when I say "Same here on openSUSE..." I mean that I have the same behavior of the original poster (i.e. James), not as the previous commenter (Creitom de Souza Oliveira). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #3 from Tom Hughes --- Sure there is - it's finit_module. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 Tom Hughes changed: What|Removed |Added Summary|WARNING: unhandled syscall: |WARNING: unhandled |313 (finit_module) |amd64-linux syscall: 313 ||(finit_module) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 --- Comment #4 from Bartosz Golaszewski --- Hmm... it's already there in ./coregrind/m_syswrap/syswrap-amd64-linux.c but it's commented out: 835 // LIN__(__NR_finit_module, sys_ni_syscall), // 313 Does it mean that it just doesn't have a wrapper in valgrind or some other reason? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Hugo Pereira Da Costa changed: What|Removed |Added Latest Commit|https://commits.kde.org/bre |https://commits.kde.org/oxy |eze/760cc2b71d544c8084f278b |gen/ac3136236da1854262387d2 |c2d6eb7cfa576b864 |f24409b3bf6aeaca9 --- Comment #17 from Hugo Pereira Da Costa --- Git commit ac3136236da1854262387d2f24409b3bf6aeaca9 by Hugo Pereira Da Costa. Committed on 18/05/2017 at 10:39. Pushed by hpereiradacosta into branch 'master'. Set a mask to shadow widget to make sure that it does not overlap with the mdi window. M +22 -3kstyle/oxygenmdiwindowshadow.cpp M +29 -41 kstyle/oxygenmdiwindowshadow.h https://commits.kde.org/oxygen/ac3136236da1854262387d2f24409b3bf6aeaca9 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Hugo Pereira Da Costa changed: What|Removed |Added Latest Commit|https://commits.kde.org/oxy |https://commits.kde.org/oxy |gen/ac3136236da1854262387d2 |gen/21f4e6ec82f1faef06cc31f |f24409b3bf6aeaca9 |0c14dbfcbbcac78f7 --- Comment #18 from Hugo Pereira Da Costa --- Git commit 21f4e6ec82f1faef06cc31f0c14dbfcbbcac78f7 by Hugo Pereira Da Costa. Committed on 18/05/2017 at 10:41. Pushed by hpereiradacosta into branch 'Plasma/5.10'. Set a mask to shadow widget to make sure that it does not overlap with the mdi window. M +22 -3kstyle/oxygenmdiwindowshadow.cpp M +29 -41 kstyle/oxygenmdiwindowshadow.h https://commits.kde.org/oxygen/21f4e6ec82f1faef06cc31f0c14dbfcbbcac78f7 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379790] MDI SubWindows are frozen (non-responsive) with Breeze and Oxygen
https://bugs.kde.org/show_bug.cgi?id=379790 Hugo Pereira Da Costa changed: What|Removed |Added Latest Commit|https://commits.kde.org/oxy |https://commits.kde.org/bre |gen/21f4e6ec82f1faef06cc31f |eze/71ac59a3b571e5bcf8f75b6 |0c14dbfcbbcac78f7 |02951ae73069b34bf --- Comment #19 from Hugo Pereira Da Costa --- Git commit 71ac59a3b571e5bcf8f75b602951ae73069b34bf by Hugo Pereira Da Costa. Committed on 18/05/2017 at 10:41. Pushed by hpereiradacosta into branch 'Plasma/5.10'. set a mask to shadow widget to make sure that it does not overlap with the mdi window. M +10 -2kstyle/breezemdiwindowshadow.cpp https://commits.kde.org/breeze/71ac59a3b571e5bcf8f75b602951ae73069b34bf -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] [libzip] Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 --- Comment #3 from sun...@hotmail.ru --- Hi, workaround worked. Also it gives notification that an archive will be opened as Read Only and gives you an option to quit. IMO its better to simply create a new line under toolbar in a different colour(how kate does it) that says its Read Only mode. And if toolbar is moved elsewhere then show it under menu. Also i've tried to find any libzip bug trackers it appears there is none. How important is this libzip? Is there a need to write authors to email? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)
https://bugs.kde.org/show_bug.cgi?id=379966 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Ivo Raisr --- It means the syscall wrapper needs a careful review w.r.t. kernel sources and ideally also a test case. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] [libzip] Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 --- Comment #4 from sun...@hotmail.ru --- Now i see, atleast character encodings is handled better with libzip. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 372343] search stops working after muon is first used to install a package
https://bugs.kde.org/show_bug.cgi?id=372343 Joe changed: What|Removed |Added CC||jose...@main.nc.us --- Comment #1 from Joe --- Duplicate of 369301 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 355234] add "local" to status or source tab (similar to synaptic)
https://bugs.kde.org/show_bug.cgi?id=355234 Ｖ字龍(Vdragon) changed: What|Removed |Added CC||vdragon.tai...@gmail.com --- Comment #1 from Ｖ字龍(Vdragon) --- Possible duplicate of #335884 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379970] New: When manually adding digital camera on Windows 10, camera is not detected and photos cannot be imported
https://bugs.kde.org/show_bug.cgi?id=379970 Bug ID: 379970 Summary: When manually adding digital camera on Windows 10, camera is not detected and photos cannot be imported Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: wpvk...@gmail.com Target Milestone: --- I am trying to import photos from digital camera on Windows 10. The feature does not work due to the fact that the camera is not detected by digiKam. I see it works with gPhoto2, which is a Linux application. Will it be possible to do this in MS Windows? If not, it would be better to only have this feature available when the OS is Linux based. Rather hide it in MS Windows than "creating futile hope". -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 379964] [libzip] Opening zip archives with streaming (general purpose bit 3) and/or zip64 enabled fails
https://bugs.kde.org/show_bug.cgi?id=379964 --- Comment #5 from Elvis Angelaccio --- Yes, that's one of the reasons why we are switching to libzip. There is a libzip mailing list, feel free to reach the libzip developers there and send them the link to the this report. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 Joe changed: What|Removed |Added CC||jose...@main.nc.us --- Comment #6 from Joe --- 372343 is a duplicate of this -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379849] Rip fails to start when using clone mode and target exsists
https://bugs.kde.org/show_bug.cgi?id=379849 --- Comment #8 from Chris --- It does fix the problem of the rip not starting, however I do think k3b should prompt if the target exists for clone opperations. This is what happens for non clone opperations and this behavior should be consistant throuh out the application. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 --- Comment #7 from pop...@online.de --- It's happening not only when a package is installed, but sometimes even when you start muon and just wait a while. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379571] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=379571 --- Comment #3 from Shane --- Running plasmashell from console: 524 [shane@neocontrol] ~ $ /usr/bin/plasmashell Service started, version: org.kde.plasma: requesting config for "Desktop" without a containment! KActivities: FATAL ERROR: Failed to contact the activity manager daemon Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/Notifications.qml:147: TypeError: Cannot read property 'IdleTime' of undefined file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null Both point size and pixel size set. Using pixel size. trying to show an empty dialog KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0). And whether your filesystem supports shared memory KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type '
[krusader] [Bug 377268] 2.5.1 - Preserve directory structure checkbox missing in "Copy..."
https://bugs.kde.org/show_bug.cgi?id=377268 --- Comment #1 from Alex Bikadorov --- If I understood you right: You are comparing the content of two folders and want to copy the resulting difference of one side to another location - as backup. If this is correct, would adding an option to specify another folder in the Synchronize dialog (the one with "Right to left, "Left to right",... checkboxes) as sync target be sufficient for your needs? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 300211] Timestamps are not preserved with Syncronizer and SFTP
https://bugs.kde.org/show_bug.cgi?id=300211 Alex Bikadorov changed: What|Removed |Added Version|2.4.0-beta3 "Single Step" |2.6.0 CC||alex.bikado...@kdemail.net Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Alex Bikadorov --- Confirmed. After a quick look I could not figure out why files are considered equal although the have different timestamps (which is actually good, otherwise files folders would not be equal after a sync). Note for myself: with KIO::FileCopyJob::setModificationTime() this can probably be easily fixed. https://api.kde.org/frameworks/kio/html/classKIO_1_1FileCopyJob.html#a28f12603e4db5e7adc1aff5b2acc0f9f -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379971] New: kmail asserts whenever I drop a mail into composer
https://bugs.kde.org/show_bug.cgi?id=379971 Bug ID: 379971 Summary: kmail asserts whenever I drop a mail into composer Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: kol...@aon.at Target Milestone: --- I think this is a regression. When creating a new mail and I'd like to drag&drop another email (e.g. from the sent-folder) into the composer, kmail asserts: 20170518 15:47:49.280 CEST kmail2 unknown line:0: ASSERT failure in FolderSettings::fallBackIdentity: "No resource found in collection", file /home/KDE5/source/kde/pim/mailcommon/src/folder/foldersettings.cpp, line 326 In the debugger I see that the resource string is an empty string. I'm pretty sure that worked in some earlier version. I'm using KDE-PIM master from yesterday -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379972] New: Crash after removing hdmi external monitor
https://bugs.kde.org/show_bug.cgi?id=379972 Bug ID: 379972 Summary: Crash after removing hdmi external monitor Product: plasmashell Version: 5.8.6 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: alexandre.nu...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.6) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.20 x86_64 Distribution: Debian GNU/Linux 9.0 (stretch) -- Information about the crash: - What I was doing when the application crashed: Removed hdmi external monitor, was copying files as well. The crash happened after copying was done. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc92781940 (LWP 2555))] Thread 7 (Thread 0x7fdbdfa2d700 (LWP 2745)): #0 0x7fdc8ce5955d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc8860db30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc885c9042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc885c9514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdc885c968c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc8d77006b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc8d7199ca in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdc8d5470f3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc90762406 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fdc8d54bda8 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdc8c660494 in start_thread (arg=0x7fdbdfa2d700) at pthread_create.c:333 #11 0x7fdc8ce6693f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 6 (Thread 0x7fdc6e5a9700 (LWP 2743)): #0 0x7fdc8c66615f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdc921da2c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fdc921da309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fdc8c660494 in start_thread (arg=0x7fdc6e5a9700) at pthread_create.c:333 #4 0x7fdc8ce6693f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 5 (Thread 0x7fdc6700 (LWP 2732)): #0 0x7fdc8ce5d4ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc885c9576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc885c968c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc8d77006b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdc8d7199ca in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdc8d5470f3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc8fdd86a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fdc8d54bda8 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc8c660494 in start_thread (arg=0x7fdc6700) at pthread_create.c:333 #9 0x7fdc8ce6693f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 4 (Thread 0x7fdc76127700 (LWP 2636)): #0 0x7fdc8ce5955d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc8860db30 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc885c9042 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc885c9514 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdc885c968c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc8d77006b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc8d7199ca in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdc8d5470f3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc8fdd86a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fdc8d54bda8 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdc8c660494 in start_thread (arg=0x7fdc76127700) at pthread_create.c:333 #11 0x7fdc8ce6693f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7fdc77b6c700 (LWP 2572)): #0 0x7fdc8ce5d4ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc885c9576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc885c968c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0
[kmail2] [Bug 379973] New: Quote misparses '|' character
https://bugs.kde.org/show_bug.cgi?id=379973 Bug ID: 379973 Summary: Quote misparses '|' character Product: kmail2 Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: chandanrm...@gmail.com Target Milestone: --- Created attachment 105613 --> https://bugs.kde.org/attachment.cgi?id=105613&action=edit screenshot displaying bad rendering '|' character inside quoted part of an email is misparsed. Hence ASCII diagrams are rendered badly. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376506] Problem at least when synchronizing zip files
https://bugs.kde.org/show_bug.cgi?id=376506 Alex Bikadorov changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Alex Bikadorov --- Syncing archive content seems not to be supported at all right now. Solutions: 1. Check if user wants to do it and abort with error message 2. Make it working (2) is more complicated, of course. But maybe it will be be a fortunate side effect after I simplify the code base... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379973] Quote misparses '|' character
https://bugs.kde.org/show_bug.cgi?id=379973 --- Comment #1 from chandan --- Created attachment 105614 --> https://bugs.kde.org/attachment.cgi?id=105614&action=edit screenshot displaying the same text using "Message as plain text" window -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379973] Quote misparses '|' character
https://bugs.kde.org/show_bug.cgi?id=379973 chandan changed: What|Removed |Added CC||chandanrm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379974] New: Freezing no matter what
https://bugs.kde.org/show_bug.cgi?id=379974 Bug ID: 379974 Summary: Freezing no matter what Product: krita Version: 3.1.2 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: Instant Preview Assignee: krita-bugs-n...@kde.org Reporter: gray.stephanie1...@gmail.com Target Milestone: --- Created attachment 105615 --> https://bugs.kde.org/attachment.cgi?id=105615&action=edit Image of the freezing document I was applying the dark blue color to my image, when the preview quit displaying anything. The brush freezes on the image, nothing disappears when I tell it to not show the layers, and I can't make changes. I restarted everything and opened a new document. The same issues occurred, but I could click the hide button twice to make any changes appear. The same is going on with pre-existing images. I'm not sure what's going on. There was a JPEG at the bottom of the image before, but I deleted it when the freezing started, and the layers are masked to the image at the bottom of the group. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 379194] Ambiguous Shortcuts - gwenview Cut and Remove -> Shift+Del
https://bugs.kde.org/show_bug.cgi?id=379194 Twisted Lucidity changed: What|Removed |Added CC||lucidlytwis...@gmail.com --- Comment #4 from Twisted Lucidity --- Seeing this now on two separate Kubuntu 16.04.2 LTS systems which were fully updated in the last few days. Gwenview: 16.04.3 KDE Plasma: 5.8.6 KDE Frameworks: 5.33.0 Qt Version: 5.6.1 Kernel: 4.4.0-77-generic OS Type: 64bit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379971] kmail asserts whenever I drop a mail into composer
https://bugs.kde.org/show_bug.cgi?id=379971 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kma ||il/e8dbbd11b388bc3449a5adfb ||9987b2498d40dbdd --- Comment #1 from Laurent Montel --- Git commit e8dbbd11b388bc3449a5adfb9987b2498d40dbdd by Montel Laurent. Committed on 18/05/2017 at 14:41. Pushed by mlaurent into branch 'master'. Fix Bug 379971 - kmail asserts whenever I drop a mail into composer M +10 -4src/editor/kmcomposerwin.cpp https://commits.kde.org/kmail/e8dbbd11b388bc3449a5adfb9987b2498d40dbdd -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 379003] Wallpaper "Picture of the Day" from National Geographics only changing after reboot or not at all.
https://bugs.kde.org/show_bug.cgi?id=379003 Patrick Hanft changed: What|Removed |Added CC||m...@patrick-hanft.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379925] PPC64, mtffs does not set the FPCC and C bits in the FPSCR register
https://bugs.kde.org/show_bug.cgi?id=379925 Carl Love changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Carl Love --- No issues seen in the nightly regression test. Closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 --- Comment #6 from Ivan Čukić --- I'll see what can be done. The sad part is that the pinned tasks is a completely different beast to kicker favs. (here we chose to have different per-applet pinned things, not global, so it does not use activity linking at all) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 Ivan Čukić changed: What|Removed |Added Assignee|h...@kde.org|ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379975] New: PNG transparency not available with multiple layers
https://bugs.kde.org/show_bug.cgi?id=379975 Bug ID: 379975 Summary: PNG transparency not available with multiple layers Product: krita Version: 3.1.3-beta Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: cvoisinead...@gmail.com Target Milestone: --- Created attachment 105616 --> https://bugs.kde.org/attachment.cgi?id=105616&action=edit screenshot of issue Not sure if bug. When trying to export (or save) as png, option to store transparency is greyed out if image has multiple layers. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 181145] Lokalize cannot create the mo files
https://bugs.kde.org/show_bug.cgi?id=181145 --- Comment #27 from Dimitrios Glentadakis --- Ok great, is better in github, You mean that you removed the ts support because it doesn't work ? For me it works the po and ts version without any problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379972] Crash after removing hdmi external monitor
https://bugs.kde.org/show_bug.cgi?id=379972 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 375388 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379921] Plasma Crash After Changing Widget Configurations and Arrangements
https://bugs.kde.org/show_bug.cgi?id=379921 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 375388 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 David Edmundson changed: What|Removed |Added CC||alexandre.nu...@gmail.com --- Comment #45 from David Edmundson --- *** Bug 379972 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 David Edmundson changed: What|Removed |Added CC||alexandre.nu...@gmail.com CC||2020cmitch...@gmail.com --- Comment #45 from David Edmundson --- *** Bug 379972 has been marked as a duplicate of this bug. *** --- Comment #46 from David Edmundson --- *** Bug 379921 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379750] menu bar sometimes screws up royally, requiring restart to fix
https://bugs.kde.org/show_bug.cgi?id=379750 --- Comment #1 from Ian Haber --- Created attachment 105617 --> https://bugs.kde.org/attachment.cgi?id=105617&action=edit picture of menu bar incorrect menus this one doesnt have the correct menus. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379969] Transparancy Mask Disappear
https://bugs.kde.org/show_bug.cgi?id=379969 mvowada changed: What|Removed |Added CC||freebo...@tiscali.it Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from mvowada --- Yes, I can confirm the same issue on Ubuntu 14.04 as well with Krita 3.1.4 Alpha appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379974] Freezing no matter what
https://bugs.kde.org/show_bug.cgi?id=379974 sol changed: What|Removed |Added CC||solcitolarri...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379974] Freezing no matter what
https://bugs.kde.org/show_bug.cgi?id=379974 --- Comment #1 from sol --- (In reply to Felicity Swan from comment #0) > Created attachment 105615 [details] > Image of the freezing document > > I was applying the dark blue color to my image, when the preview quit > displaying anything. The brush freezes on the image, nothing disappears when > I tell it to not show the layers, and I can't make changes. > I restarted everything and opened a new document. The same issues occurred, > but I could click the hide button twice to make any changes appear. The same > is going on with pre-existing images. I'm not sure what's going on. > There was a JPEG at the bottom of the image before, but I deleted it when > the freezing started, and the layers are masked to the image at the bottom > of the group. > Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378315] KMail crash on logout
https://bugs.kde.org/show_bug.cgi?id=378315 FabioLima changed: What|Removed |Added CC||fhe...@gmail.com --- Comment #3 from FabioLima --- It also happens to me. I am using Arch Linux stable repositories. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379976] New: Artifacts by adding Transparency Mask to the Background First Layer (Krita 3.1.4 Alpha appimage)
https://bugs.kde.org/show_bug.cgi?id=379976 Bug ID: 379976 Summary: Artifacts by adding Transparency Mask to the Background First Layer (Krita 3.1.4 Alpha appimage) Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: freebo...@tiscali.it Target Milestone: --- Created attachment 105618 --> https://bugs.kde.org/attachment.cgi?id=105618&action=edit (Video example) (Ubuntu 14.04 - Krita 3.1.4 Alpha appimage) I get artifacts on canvas by adding a Transparency mask to the Background First Layer (please, see the video example). Steps to reproduce: 1. create a new document with only 1 layer, 2. add a transparency mask. Expected Results: no artifacts. Actual Results: artifacts on canvas. -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 379831] Could not find a suitable SoundController plugin
https://bugs.kde.org/show_bug.cgi?id=379831 SP changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from SP --- Ran strace and discovered that the program was expecting the minuet plugin folder to be in /usr/lib64/qt5/plugins/minuet whereas the build had installed it in /usr/lib64/plugins/minuet. Made a symlink and now the program works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379974] Freezing no matter what
https://bugs.kde.org/show_bug.cgi?id=379974 Felicity Swan changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Felicity Swan --- I fixed it. I uninstalled and reinstalled the program. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 379977] New: hang in context browser popup
https://bugs.kde.org/show_bug.cgi?id=379977 Bug ID: 379977 Summary: hang in context browser popup Product: kdevplatform Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: language Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- I just had my 2nd hang in a context browser popup, this time one I triggered myself in order to jump to a variable definition in some header file. The (partial) backtrace: #0 0x7fc4df38b93d in nanosleep () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fc4dfc8488d in qt_nanosleep (amount=...) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qelapsedtimer_unix.cpp:195 #2 0x7fc4dfa67134 in QThread::usleep (usecs=usecs@entry=500) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/thread/qthread_unix.cpp:511 #3 0x7fc4dd52babe in KDevelop::DUChainLock::lockForWrite ( this=0x7fc4ddcc8ce0 , timeout=0) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevplatform-5/language/duchain/duchainlock.cpp:155 #4 0x7fc4dd52bcdc in KDevelop::DUChainWriteLocker::lock (this=0x7ffe666ff340) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevplatform-5/language/duchain/duchainlock.cpp:249 #5 0x7fc4dd4d3526 in KDevelop::DUChain::documentLoadedPrepare (this=0x17dbc60, doc=0x947bb80) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevplatform-5/language/duchain/duchain.cpp:1504 #6 0x7fc4dfc5e32e in call (a=0x7ffe666ff4c0, r=0x17dbc60, this=) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #7 QMetaObject::activate (sender=0x1624d10, signalOffset=, local_signal_index=local_signal_index@entry=9, argv=argv@entry=0x7ffe666ff4c0) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qobject.cpp:3723 #8 0x7fc4dfc5e8c7 in QMetaObject::activate (sender=, m=m@entry=0x7fc4e1ca76a0 , local_signal_index=local_signal_index@entry=9, argv=argv@entry=0x7ffe666ff4c0) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qobject.cpp:3602 #9 0x7fc4e1a93c52 in KDevelop::IDocumentController::documentLoadedPrepare (this=, _t1=, _t1@entry=0x947bb80) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/build/interfaces/KDevPlatformInterfaces_automoc.dir/moc_idocumentcontr_BKHINBC3JP6LAY.cpp:565 #10 0x7fc4e1a85960 in KDevelop::IDocument::notifyLoaded (this=0x947bb80) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevplatform-5/interfaces/idocument.cpp:130 #11 0x7fc4dfc5e32e in call (a=0x7ffe666ff600, r=0x947bb60, this=) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #12 QMetaObject::activate (sender=sender@entry=0xa20c060, signalOffset=, local_signal_index=local_signal_index@entry=15, argv=argv@entry=0x7ffe666ff600) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qobject.cpp:3723 #13 0x7fc4dfc5e8c7 in QMetaObject::activate (sender=sender@entry=0xa20c060, m=, local_signal_index=local_signal_index@entry=15, argv=argv@entry=0x7ffe666ff600) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/kernel/qobject.cpp:3602 #14 0x7fc4dc2c4272 in KTextEditor::Document::textChanged(KTextEditor::Document*) (this=this@entry=0xa20c060, _t1=, _t1@entry=0xa20c060) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-ktexteditor/work/build/src/KF5TextEditor_automoc.dir/moc_document_G7ZZNPEZ2BAWZM.cpp:577 ---Type to continue, or q to quit---q Quit (gdb) f 3 #3 0x7fc4dd52babe in KDevelop::DUChainLock::lockForWrite ( this=0x7fc4ddcc8ce0 , timeout=0) at /opt/local/var/lnxports/build/_opt_local_site-ports_kf5_kdevplatform5/kf5-kdevplatform-devel/work/kf5-kdevpla
[krusader] [Bug 377268] 2.5.1 - Preserve directory structure checkbox missing in "Copy..."
https://bugs.kde.org/show_bug.cgi?id=377268 --- Comment #2 from fred frazelle --- Thank you very much, Alex, for personally replying. Here's the situation: Once i get the list of file and folders (folders being the other, very important part here), all i want to be able to do is to copy those to another folder, with the files once again appearing in their respective folders. So, we would do the sync, then send to List Box and from there, select just the files and then from the mouse i think, select Copy. When the Copy window appeared, it would include a Check Box to Preserve Original Structure or something to that effect so that when the files were copied into the other pane/folder, they would arrive, each in its original folder. i suspect that what you are suggesting would only copy the files to the new folder, but would leave out their folders. i don't know if you are familiar with Areca Backup, but it seems to do the same thing, but it creates a folder which contains the files, each in folder in which they originally appeared. i hope this clarifies the situation a little. Thank you again very much for replying and asking the question. i suspect that getting the program to make this "copy and maintain folder structure" is not as easy as it sounds. Have a wonderful day and keep up the great work! :) fred:-) // /"Every imperfect soul is self-centred and thinketh only of his own good. But as his thoughts expand a little he will begin to think of the welfare and comfort of his family. If his ideas still more widen, his concern will be the felicity of his fellow citizens; and if still they widen, he will be thinking of the glory of his land and of his race. But when ideas and views reach the utmost degree of expansion and attain the stage of perfection, then will he be interested in the exaltation of humankind. He will then be the well-wisher of all men and the seeker of the weal and prosperity of all lands. This is indicative of perfection."/ / (´Abdu'l-Bahá, Selections from the Writings of ´Abdu'l-Bahá, p. 68)/ On 05/18/2017 06:09 AM, Alex Bikadorov wrote: > https://bugs.kde.org/show_bug.cgi?id=377268 > > --- Comment #1 from Alex Bikadorov --- > If I understood you right: You are comparing the content of two folders and > want to copy the resulting difference of one side to another location - as > backup. > > If this is correct, would adding an option to specify another folder in the > Synchronize dialog (the one with "Right to left, "Left to right",... > checkboxes) as sync target be sufficient for your needs? > -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377268] 2.5.1 - Preserve directory structure checkbox missing in "Copy..."
https://bugs.kde.org/show_bug.cgi?id=377268 --- Comment #3 from Alex Bikadorov --- >i suspect that what you are suggesting would only copy the files to the new folder, but would leave out their folders. No, I plan to preserver the folder structure. But when doing the sync its possible that changes are made on both sides: copy some files from left to right AND copy files from right to left. But when doing a backup, this doesn't make sense. So I assume you only want to copy the different files/folders of one side to some other location. And I still don't get what two sides you are comparing. One side is the folder containing your current original data. But with what are you comparing it? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379978] New: Runtime error
https://bugs.kde.org/show_bug.cgi?id=379978 Bug ID: 379978 Summary: Runtime error Product: krita Version: 3.0.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ray.ro...@gmail.com Target Milestone: --- have been using Krita for about 6 months. Last few days very slow and crashes often. when trying to save final drawing as jpeg program closes automatically. Saw a pop up saying runtime error. Ray -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 181145] Lokalize cannot create the mo files
https://bugs.kde.org/show_bug.cgi?id=181145 --- Comment #28 from Daniele Scasciafratte --- the script is working very good only that today I need only the po support. I want also that will be execute on save of the po file (the .rc file) but actually this not happen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379979] New: kwin crash
https://bugs.kde.org/show_bug.cgi?id=379979 Bug ID: 379979 Summary: kwin crash Product: kwin Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gh...@vivaldi.net Target Milestone: --- Application: kwin_x11 (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.9.28-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Nothing yet, just booted into OS. Not using a login manager. Start KDE with "exec startkde" in "~/.xinitrc" In "~/.config/autostart/" I have "steam.desktop" and "org.kde.yakuake.desktop" -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50785bc840 (LWP 2562))] Thread 10 (Thread 0x7f503b60d700 (LWP 2816)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f50745a4234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f50745a4279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f503c60f700 (LWP 2814)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5042bd85eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f5042bd8317 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f503ce10700 (LWP 2813)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5042bd85eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f5042bd8317 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f503d611700 (LWP 2812)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5042bd85eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f5042bd8317 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f503de12700 (LWP 2811)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5042bd85eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f5042bd8317 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f503e81a700 (LWP 2810)): #0 0x7f50711e8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5042bd85eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f5042bd8317 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f50562c2700 (LWP 2798)): #0 0x7f507801d76b in ppoll () at /usr/lib/libc.so.6 #1 0x7f507566b329 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f507566c99a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f50756198ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f507543ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f506fef8025 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f50754406d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f505c9ca700 (LWP 2679)): #0 0x7f507801d76b in ppoll () at /usr/lib/libc.so.6 #1 0x7f507566b329 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f507566c99a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f50756198ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f507543ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f506f089125 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f50754406d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f50711e22e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f507802754f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f505eb42700 (LWP 2597)): #0 0x
[plasmashell] [Bug 379980] New: Crash on docking
https://bugs.kde.org/show_bug.cgi?id=379980 Bug ID: 379980 Summary: Crash on docking Product: plasmashell Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gis...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing before the crash: Laptop was being used on battery without any external peripherals. - What I was doing when the application crashed: Had just plugged in 2 monitors and then the USB 3 dock with Ethernet. Laptop was still powered on. Monitors flashed and activated as usual. After the monitors were activated, I noticed the KDE crash dialog saying plasma had crashed, which is how this report was generated. - Notable information: I have KDE configured to have 2 taskbar panels - one on the bottom of the laptop's internal display, and another one configured vertically on the left edge of the first external monitor. I have had issues with panel positioning and resizing in the past with multi-monitor configurations, so maybe this is a related problem. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa43a5a5800 (LWP 971))] Thread 12 (Thread 0x7fa32700 (LWP 4011)): #0 0x7fa4281c044f in pa_pstream_unref () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7fa4281c0989 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fa4281c120a in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #3 0x7fa42883299c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #4 0x7fa428832d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #5 0x7fa428832e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #6 0x7fa428840e29 in () at /usr/lib/libpulse.so.0 #7 0x7fa4281d0fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #8 0x7fa4332102e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa433c6e54f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa3393b0700 (LWP 4010)): #0 0x7fa42ea811c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fa42ea3a9b4 in g_main_context_release () at /usr/lib/libglib-2.0.so.0 #2 0x7fa42ea3b96a in () at /usr/lib/libglib-2.0.so.0 #3 0x7fa42ea3bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fa43458b09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa4345348ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa434356a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fa43748f025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fa43435b6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fa4332102e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fa433c6e54f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa34fbec700 (LWP 1373)): #0 0x7fa42ea3adf2 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7fa42ea3b8db in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa42ea3bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa43458b09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa4345348ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa434356a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa43435b6d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa4332102e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa433c6e54f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fa3553f4700 (LWP 1362)): #0 0x7fa42ea811c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fa42ea3a870 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7fa42ea3b865 in () at /usr/lib/libglib-2.0.so.0 #3 0x7fa42ea3bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fa43458b09b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa4345348ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa434356a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fa356a780a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7fa43435b6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fa4332102e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fa433c6e54f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fa35d56d700 (LWP 1361)): #0 0x7fa42ea80da9 in g_private_get () at /usr/lib/lib
[plasmashell] [Bug 379980] Crash on docking
https://bugs.kde.org/show_bug.cgi?id=379980 Brian G. changed: What|Removed |Added CC||gis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 379899] unable to save work
https://bugs.kde.org/show_bug.cgi?id=379899 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- see https://userbase.kde.org/Umbrello/FAQ#How_to_fix_the_error_message_.27There_was_a_problem_saving_file.27_.3F -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 --- Comment #71 from Martin Flöser --- Git commit 55f169d1c34491f0d97c8b7a162f4ba60f6849e2 by Martin Flöser, on behalf of Luboš Luňák. Committed on 18/05/2017 at 17:30. Pushed by graesslin into branch 'Plasma/5.8'. fix occassional crash caused by needlessly delayed signals (bko#363224) As pointed out by the Valgrind trace in #363224, delaying the signal causes the EffectWindow* argument to become invalid before the connected slot is called (this is because Qt discards only delayed signal->slot calls where the receiver gets deleted meanwhile, not the sender and definitely not a random argument. If the supposed glitches really happen, they should get fixed correctly, and for all cases (I doubt only desktop number would be involved but not e.g. shaded or minimized states). https://phabricator.kde.org/D5164 M +1-5effects.cpp https://commits.kde.org/kwin/55f169d1c34491f0d97c8b7a162f4ba60f6849e2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Martin Flöser changed: What|Removed |Added CC||gh...@vivaldi.net --- Comment #72 from Martin Flöser --- *** Bug 379979 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379979] kwin crash
https://bugs.kde.org/show_bug.cgi?id=379979 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 363224 *** -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 379981] New: Add control for delete wallet
https://bugs.kde.org/show_bug.cgi?id=379981 Bug ID: 379981 Summary: Add control for delete wallet Product: kwalletmanager Version: 17.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: lucho.fuen...@gmail.com Target Milestone: --- The KDE Wallet Manager crash when try delete a wallet that not exisist. To fix it , is necesary add a control, if the variable walletName is not null, in line 374 of https://github.com/KDE/kwalletmanager/blob/master/src/manager/kwalletmanager.cpp -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379982] New: Dolphin crashed when attempting to move file(s) inside wastebin
https://bugs.kde.org/show_bug.cgi?id=379982 Bug ID: 379982 Summary: Dolphin crashed when attempting to move file(s) inside wastebin Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: daederp1...@gmail.com Target Milestone: --- Application: dolphin (17.04.1) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.10.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: The action of using the cursor to move a file from one folder to another (which should show the context menu: Copy Here, Link Here, Cancel), inside the wastebin. - Custom settings of the application: Previews must be shown for the bug to consistently occur. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59acc20400 (LWP 11595))] Thread 8 (Thread 0x7f59811a2700 (LWP 11604)): #0 0x7f59ac56d67d in poll () at /usr/lib/libc.so.6 #1 0x7f599f3559b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f599f355acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f59a668009b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f59a66298ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f59a644ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f59a64506d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f598243f700 (LWP 11603)): #0 0x7f59a1728756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f598ca800cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f598ca7fdf7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5982c40700 (LWP 11602)): #0 0x7f59a1728756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f598ca800cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f598ca7fdf7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f5983441700 (LWP 11601)): #0 0x7f59a1728756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f598ca800cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f598ca7fdf7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f5983c42700 (LWP 11600)): #0 0x7f59a1728756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f598ca800cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f598ca7fdf7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f598464a700 (LWP 11599)): #0 0x7f59a1728756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f598ca800cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f598ca7fdf7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f598f94a700 (LWP 11598)): #0 0x7f59ac56d67d in poll () at /usr/lib/libc.so.6 #1 0x7f599f3559b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f599f355acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f59a668009b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f59a66298ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f59a644ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f59a6a99125 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f59a64506d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f59a17222e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f59ac57754f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f59acc20400 (LWP 11595)): [KCrash Handler] #6 0x7f59aa5f0f7b in KIO::UDSEntry::UDSEntry(KIO::UDSEntry const&) () at /usr/lib/libKF5KIOCore.so.5 #7 0x7f59aa54dbe5 in KFileItem::entry()
[akregator] [Bug 379983] New: Viewer doesn't scale under HiDPI
https://bugs.kde.org/show_bug.cgi?id=379983 Bug ID: 379983 Summary: Viewer doesn't scale under HiDPI Product: akregator Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: hla...@hlavki.eu Target Milestone: --- Created attachment 105620 --> https://bugs.kde.org/attachment.cgi?id=105620&action=edit Akregator screenshot Using 4K display with scale. Feed browser doesn't scale. Screenshot attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379978] Runtime error
https://bugs.kde.org/show_bug.cgi?id=379978 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Ray, Please update to 3.1.3. 3.0.1.1 is pretty old by now! Also, run a memory checker. If things suddenly start getting unstable, it's probably not that the application suddenly develops bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379969] Transparancy Mask Disappear
https://bugs.kde.org/show_bug.cgi?id=379969 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WONTFIX CC||b...@valdyas.org Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- OpenRaster doesn't support masks. If you want to save masks, save to .kra. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379984] New: ASSERT failure in Q_GLOBAL_STATIC: "The global static was used after being destroyed", file /usr/include/qt5/QtCore/qglobalstatic.h, line 138
https://bugs.kde.org/show_bug.cgi?id=379984 Bug ID: 379984 Summary: ASSERT failure in Q_GLOBAL_STATIC: "The global static was used after being destroyed", file /usr/include/qt5/QtCore/qglobalstatic.h, line 138 Product: digikam Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Searches-Fuzzy Assignee: digikam-de...@kde.org Reporter: kdeb...@i-pi.com Target Milestone: --- In Tools->find duplicates, click on Update Fingerprints causes a crash (after some run time) with the message: ASSERT failure in Q_GLOBAL_STATIC: "The global static was used after being destroyed", file /usr/include/qt5/QtCore/qglobalstatic.h, line 138 Unfortunately, OpenSUSE Tumbleweed has no debug packages for digikam, so I have no backtrace info. Linux localhost.localdomain 4.11.0-1-default #1 SMP PREEMPT Tue May 2 05:35:51 UTC 2017 (1b516a5) x86_64 x86_64 x86_64 GNU/Linux digikam-5.5.0-1.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379448] MATSHITA BD-MLT UJ240AS 1.02 - There is no information
https://bugs.kde.org/show_bug.cgi?id=379448 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 305123] Using Synchronizer to compare content with ftp server generates errors for files with the length of 0 bytes.
https://bugs.kde.org/show_bug.cgi?id=305123 Alex Bikadorov changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||alex.bikado...@kdemail.net --- Comment #2 from Alex Bikadorov --- It's a bug in KIO. *** This bug has been marked as a duplicate of bug 379787 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 379787] KIO::TransferJob cannot handle empty files over FTP
https://bugs.kde.org/show_bug.cgi?id=379787 Alex Bikadorov changed: What|Removed |Added CC||bugs.kde@mentat.net.pl --- Comment #2 from Alex Bikadorov --- *** Bug 305123 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 301514] Enormous amount of memory used when synchronising with sftp
https://bugs.kde.org/show_bug.cgi?id=301514 Alex Bikadorov changed: What|Removed |Added CC||shlom...@gmail.com --- Comment #1 from Alex Bikadorov --- *** Bug 321863 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
