[kwin] [Bug 409565] kwin crashes after reinstall
https://bugs.kde.org/show_bug.cgi?id=409565 --- Comment #2 from yashsorathiy...@gmail.com --- (In reply to Martin Flöser from comment #1) > Unfortunately the backtrace is lacking debug symbols. If you are able to > reproduce please install debug packages and attach a new backtrace. I'm sorry but I don't know what you're talking about, as I mentioned, I'm quite new to this and this is the first time I'm reporting a bug. Can you please help me out a bit with what I need to do? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406866] Windows rearranged when coming back from power save
https://bugs.kde.org/show_bug.cgi?id=406866
--- Comment #2 from Jules RANDOLPH ---
I can reproduce this bug with a two screens setup. One panel disappear after
power save.
System:
██ jsamr@jsamr-nuc
██ ---
██ OS: Manjaro Linux x86_64
██ Host: NUC8i7HVK J71485-504
Kernel: 5.1.15-1-MANJARO
Uptime: 33 mins
Packages: 1447 (pacman)
Shell: zsh 5.7.1
Resolution: 1920x1080, 1920x1080
DE: KDE
WM: KWin
WM Theme: Breeze
Theme: Breath [KDE], Adwaita [GTK2], Breath
[GTK3]
Icons: Papirus [KDE], Adwaita [GTK2], maia
[GTK3]
Terminal: konsole
Terminal Font: Noto Mono 10
CPU: Intel i7-8809G (8) @ 4.200GHz
GPU: Intel HD Graphics 630
GPU: AMD ATI Radeon RX Vega M GH
Memory: 3940MiB / 32085MiB
plasma-desktop 5.16.2-1
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 409565] kwin crashes after reinstall
https://bugs.kde.org/show_bug.cgi?id=409565 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 409566] New: Expected quite after trying to connect to Indi
https://bugs.kde.org/show_bug.cgi?id=409566 Bug ID: 409566 Summary: Expected quite after trying to connect to Indi Product: kstars Version: 3.3.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: mbalk...@gmail.com Target Milestone: --- Created attachment 121361 --> https://bugs.kde.org/attachment.cgi?id=121361&action=edit unexpected quit report SUMMARY Quits every time I try to connect to Indi (after it starts to connect) STEPS TO REPRODUCE 1. restart stars 2. Connect to scope 3. OBSERVED RESULT unexpected quit EXPECTED RESULT connect to telecope SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406866] Windows rearranged when coming back from power save
https://bugs.kde.org/show_bug.cgi?id=406866 Jules RANDOLPH changed: What|Removed |Added CC||theswan...@gmail.com Flags||X11+ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 Gianluca Pettinello changed: What|Removed |Added CC||gianluca.pettinello@gmail.c ||om --- Comment #1 from Gianluca Pettinello --- Same for me -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 403965] 'Kstart5 [something]' doesn't work on wayland
https://bugs.kde.org/show_bug.cgi?id=403965 Igor Kovalenko changed: What|Removed |Added CC||igor.v.kovale...@gmail.com --- Comment #6 from Igor Kovalenko --- Created attachment 121360 --> https://bugs.kde.org/attachment.cgi?id=121360&action=edit kstart5 fix wayland crash I confirm this issue exists with kde-cli-tools-5.16.2 Running on gentoo under plasma wayland 'kstart5 plasmashell' does crash with the same backtrace. I did a change following porting guide, patch attached, please have a look. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 --- Comment #22 from Laurent Montel --- What is you command line that you use for sending sms ? When I look at source code I can't understand the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401634] Brush Disappears from Presets Filtered by a Tag After Override Brush
https://bugs.kde.org/show_bug.cgi?id=401634 Eri changed: What|Removed |Added CC||ender101...@gmail.com --- Comment #8 from Eri --- I was just about to report this exact issue. I have this exact same problem. I'm not sure if I should make a report for 4.2.2 since this is the version I was using. In order to create a convenient environment, I like to make use of the tagging system and create a custom tag for all my most frequently used brush presets, as well as duplicate and customize my own brushes presets. 1. I would select an existing brush preset, and change the parameters. In this case, I modified the settings of Basic 5 size, and did "Save as new preset" and named it Basic 5 custom. The box at the bottom of the brush options is normally checked, "Temporarily save tweaks to presets" but I have found that this is irrelevant to the bug. 2. I would add it to a new tag that I simply called "use" 3. I save and restart Krita 4. I open a new canvas, and select the custom brush preset. I tweak the settings a bit, and hit "overwrite brush". Result: At this point the brush preset disappears from every tag, and will only show up in the All tag, and can't be added or re-added to any tag until Krita is restarted. I also attempted to save a new brush custom off of my existing brush custom preset; I saved it as a new brush preset called Basic 5 custom2. Whenever I try to modify and save this brush, it will display the same behavior and remove itself from all tags, as well as occasionally renaming itself to a very long backup file string it looks like. Inconsistent. (Modification in this context meaning, changing any settings or sliders and saving) >From the looks of it, it only seems to affect a small minority of users, but for folks like myself who frequently experiment with brush settings, it can be very disruptive. I am using a fresh new 4.2.2 install, but this was a problem on all older versions I had used before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409565] New: kwin crashes after reinstall
https://bugs.kde.org/show_bug.cgi?id=409565 Bug ID: 409565 Summary: kwin crashes after reinstall Product: kwin Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: yashsorathiy...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.15-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I installed a ShapeCorners fork known as KDE-rounded-corners and was trying to get round corners but didn't suceed in exactly what I wanted. So I tried removing it and apparently I removed wrong folder (/usr/share/kwin/shaders). So after restarting I am greeted by a black screen. I figured reinstalling kwin would do the job for anything missing and went forward with it. After reinstalling it, Everything works but kwin instantly crashes when the display compositor is set to either opengl 3.1 or opengl 2.0. Right now I'm living off of xrender but this isn't really doing it for me. I'm not really experienced in this so I'll help with the best of my capacity. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a10c54880 (LWP 2400))] Thread 4 (Thread 0x7f99f700 (LWP 2411)): #0 0x7f9a16dc9415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9a178d2edc in () at /usr/lib/libQt5Script.so.5 #2 0x7f9a178d2ef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f9a16dc357f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9a1952f0e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f9a0d74a700 (LWP 2410)): #0 0x7f9a19524756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f9a1806b913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f9a1806cfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f9a180165ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9a17e492f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f9a165538f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f9a17e4a520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f9a16dc357f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9a1952f0e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f9a0f5e2700 (LWP 2404)): #0 0x7f9a19524756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f9a1806b913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f9a1806cfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f9a180165ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9a17e492f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f9a15f84b37 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f9a17e4a520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f9a16dc357f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9a1952f0e3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f9a10c54880 (LWP 2400)): [KCrash Handler] #6 0x7f9a18289c70 in typeinfo for QObject () at /usr/lib/libQt5Core.so.5 #7 0x7f9a192b6926 in KWin::EffectsHandlerImpl::startPaint() () at /usr/lib/libkwin.so.5 #8 0x7f9a192a464f in KWin::Scene::paintScreen(int*, QRegion const&, QRegion const&, QRegion*, QRegion*, QMatrix4x4 const&, QRect const&) () at /usr/lib/libkwin.so.5 #9 0x7f9a0d82bb1f in KWin::SceneOpenGL::paint(QRegion, QList) () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x7f9a19295f33 in KWin::Compositor::performCompositing() () at /usr/lib/libkwin.so.5 #11 0x7f9a180443e5 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f9a189cf4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f9a189d8a21 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f9a180179c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f9a1806ed3d in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #16 0x7f9a1806d109 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7f9a107c839f in () at /usr/lib/libQt5XcbQpa.so.5 #18 0x7f9a180165ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f9a1801e326 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #20 0x7f9a195ff588 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so #21 0x7f9a19459ee3 in __libc_start_main () at
[okular] [Bug 408743] Typewriter tool not showing in okular annotations.
https://bugs.kde.org/show_bug.cgi?id=408743 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409373] Krita crashes when Background and Layer 1 are present in Timeline box at the same time
https://bugs.kde.org/show_bug.cgi?id=409373 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #18 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408404] sometimes shortcuts do not function if altered especially in CANVAS OUTPUT SETTINGS. example popup palette does not show up and brush size does not work.
https://bugs.kde.org/show_bug.cgi?id=408404 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405921] Plasma crashes when dragging task from taskmanager to a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=405921 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 --- Comment #3 from Anders Lund --- søndag den 7. juli 2019 00.41.10 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=408974 > > unlogic changed: > >What|Removed |Added > > CC||un_lo...@rambler.ru > > --- Comment #2 from unlogic --- > Have you tried to filter out notifications from your Android SMS app? It's > under Plug-ins settings Notifications sync. Unflag your SMS app of choice. No, but of cause that could be a workaround. However, seeing SMS messages in notifications is a valuable feature - when it works :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409564] New: Filter wave cut off on high amplitudes
https://bugs.kde.org/show_bug.cgi?id=409564 Bug ID: 409564 Summary: Filter wave cut off on high amplitudes Product: krita Version: 4.2.2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: ghe...@gmail.com Target Milestone: --- Created attachment 121359 --> https://bugs.kde.org/attachment.cgi?id=121359&action=edit Wave filter cut off A reddit user reported this Bounding box is smaller than needed by wave filter on high amplitudes STEPS TO REPRODUCE 1. Draw Circle 2. Filter > Other > Wave... 3. Set amplitude over 40 Deformation will start to go beyond bounding box cutting of the visible pixels -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387759] Konsole Lacks the "Ambiguous-width characters" Option
https://bugs.kde.org/show_bug.cgi?id=387759 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409564] Filter wave cut off on high amplitudes
https://bugs.kde.org/show_bug.cgi?id=409564 vanyossi changed: What|Removed |Added Status|REPORTED|CONFIRMED Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 357698] Reproducible “mergeResultSaved: m_pMFI=0”.
https://bugs.kde.org/show_bug.cgi?id=357698 michael changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from michael --- Is this still an issue in the latest 1.8.1 release? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409561] kdevelop crashes while using the menu item Commit...
https://bugs.kde.org/show_bug.cgi?id=409561 Arthur Gruzauskas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Arthur Gruzauskas --- a kdevelop update just minutes ago, which included a patchreview update, seems to have resolved this issue. Thank you, Arthur -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409563] New: Konsole does not send shift+tab (backtab) to terminal
https://bugs.kde.org/show_bug.cgi?id=409563 Bug ID: 409563 Summary: Konsole does not send shift+tab (backtab) to terminal Product: konsole Version: 19.04.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: radon.n...@gmail.com Target Milestone: --- SUMMARY When I type shift+tab in Konsole, nothing happens. The terminal does not receive any key sequence (verify in Zsh by typing M-x describe-key-briefly and then shift+tab). This contradicts the default keyboard configuration, which says that Backtab+Ansi should generate the sequence I would expect, namely \E[Z. (I use this for cycling backwards through completion candidates in Zsh, as per https://stackoverflow.com/a/842370/3538165.) STEPS TO REPRODUCE 1. Open Konsole 2. Run Zsh 3. Type M-x describe-key-briefly and then shift+tab. OBSERVED RESULT Nothing happens. EXPECTED RESULT I should at least see "undefined-key" from Zsh, indicating that a key sequence was sent to the terminal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro, kernel 4.19.49 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Zsh: 5.7.1 Konsole: 19.04.2 Related but unhelpful bugs: - https://bugs.kde.org/show_bug.cgi?id=284000 - https://bugs.kde.org/show_bug.cgi?id=402161 - https://bugs.kde.org/show_bug.cgi?id=175476 - https://forum.kde.org/viewtopic.php?f=225&t=141829 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 408991] Kdiff3 1.8.1 hangs on comparing two large directories
https://bugs.kde.org/show_bug.cgi?id=408991 --- Comment #1 from michael --- https://phabricator.kde.org/D22294 looks like it should fix your problem. This address an issue with files not being closed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409561] kdevelop crashes while using the menu item Commit...
https://bugs.kde.org/show_bug.cgi?id=409561 --- Comment #1 from Arthur Gruzauskas --- running kdevelop from git master. this crash is consistently happening the last few weeks. Im on debian buster. tried recompiling from a fresh git master, same crash. Previous crashes generated ~300k files, so couldn't send due to the 65K limit for a bug report. Crash seems to be in the same place in those larger files. doing a commit via gitk works, so may not be a git issue directly. Happy to help with more info. Arthur -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409562] New: Build: d649293; DEBUG assert ASSERT: "w > 0" in file when pressing control-c soon after control-r
https://bugs.kde.org/show_bug.cgi?id=409562 Bug ID: 409562 Summary: Build: d649293; DEBUG assert ASSERT: "w > 0" in file when pressing control-c soon after control-r Product: krita Version: nightly build (please specify the git hash!) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: epicwraths...@yandex.ru Target Milestone: --- Created attachment 121358 --> https://bugs.kde.org/attachment.cgi?id=121358&action=edit bt full and thread apply all bt SUMMARY Crash when pressing control-c immediately after selecting an area with control-r. STEPS TO REPRODUCE 1. Create a modest sized image (2048x2048 16-integer) 2. Press control-r to select an area 3. Immediately after releasing mouse/tablet, press control-c 4. If timing is right, krita will crash immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.0-20-generic 64-bit (Ubuntu) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This is a DEBUG build. Version d649293. A core dump is available if requested. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409561] New: kdevelop crashes while using the menu item Commit...
https://bugs.kde.org/show_bug.cgi?id=409561 Bug ID: 409561 Summary: kdevelop crashes while using the menu item Commit... Product: kdevelop Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: deb...@gruz.net Target Milestone: --- Application: kdevelop (5.3.40) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: start up kdevelop, wait for any parsing to finish, attempt Commit..., and it crashes -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6ba3471c0 (LWP 57624))] Thread 44 (Thread 0x7fe5f97fa700 (LWP 57805)): #0 0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502 #2 0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48, mutex=0x55979c647f20) at pthread_cond_wait.c:655 #3 0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe6d1305d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fe6d1309ae8 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fe6d1304e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fe6ce8b7aa7 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe6cd663fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fe6ce40a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 43 (Thread 0x7fe5f9ffb700 (LWP 57804)): #0 0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502 #2 0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48, mutex=0x55979c647f20) at pthread_cond_wait.c:655 #3 0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe6d1305d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fe6d1309ae8 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fe6d1304e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fe6ce8b7aa7 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe6cd663fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fe6ce40a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 42 (Thread 0x7fe5fa7fc700 (LWP 57803)): #0 0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502 #2 0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48, mutex=0x55979c647f20) at pthread_cond_wait.c:655 #3 0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe6d1305d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fe6d1309ae8 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fe6d1304e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fe6ce8b7aa7 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe6cd663fa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fe6ce40a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 41 (Thread 0x7fe5faffd700 (LWP 57802)): #0 0x7fe
[telepathy] [Bug 406676] ktp-call-ui depends on unmaintained qt-gstreamer
https://bugs.kde.org/show_bug.cgi?id=406676
--- Comment #2 from Alexandr Akulich ---
Created attachment 121357
--> https://bugs.kde.org/attachment.cgi?id=121357&action=edit
Patch for qt-gstreamer
Hi folks. I just found out this issue.
Recently I became a KDE Telepathy maintainer and though I'm not active here
(I'm busy with the underlying stuff), I'm kindly asking you to keep the project
in your repos for a bit longer.
The compilation error is caused by commit
https://gitlab.freedesktop.org/gstreamer/gstreamer/commit/b27ee943c2a44a5437a5343d21a9d2be918a1279
This commit introduces a brute C-style cast that prevents a compiler from
proper C++ casting. The workaround is trivial:
src/QGst/caps.cpp:57
void Caps::append(const CapsPtr & caps2)
{
-gst_caps_append(object(), gst_caps_copy(caps2));
+const GstCaps * caps2ptr = caps2;
+gst_caps_append(object(), gst_caps_copy(caps2ptr));
}
I'll try to reach the last qt-gstreamer maintainer to upstream the fix.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #22 from S --- (In reply to Gerson from comment #20) > In my case, actually, it seems that the db only corrupts after I restart the > computer. I've noticed this too. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409473] Computer shutdown gets cancelled
https://bugs.kde.org/show_bug.cgi?id=409473 --- Comment #4 from Darafei Praliaskouski --- Yes, I use Katepart / F4 Editor. If I enable warn on exit and try to logout, no warning is produced, only "Shutdown canceled by Krusader". File-Quit shows it, clicking Quit closes it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 409560] New: riot.im/app
https://bugs.kde.org/show_bug.cgi?id=409560 Bug ID: 409560 Summary: riot.im/app Product: Falkon Version: 3.1.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rs41...@pm.me Target Milestone: --- SUMMARY Cannot access riot.im/app STEPS TO REPRODUCE 1. Deleted local .config files, reinstalled Falkon, disabled AdBlock 2. Attempt to navigate to riot.im/app 3. OBSERVED RESULT blank page EXPECTED RESULT a not blank page SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409559] New: Systemsettings' minimum window size is too large: 1032x733
https://bugs.kde.org/show_bug.cgi?id=409559 Bug ID: 409559 Summary: Systemsettings' minimum window size is too large: 1032x733 Product: systemsettings Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- SUMMARY Systemsettings' minimum window size is too large: 1032x733. This makes it hard to use in a virtual machine when I want to make its emulated screen size for example half the width of host machine's screen. STEPS TO REPRODUCE 1. Change Virtualbox window width to about 900 px. 2. Run systemsettings inside. 3. Maximize the systemsettings window. OBSERVED RESULT Window size is larger than screen size. EXPECTED RESULT Systemsettings window fits in Virtualbox screen, should probably target at least resolutions 1024x768 or may be 1024x600. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409558] New: Tranform tools (perspective, warp, cage, liquify) - all results pixelated and grainy
https://bugs.kde.org/show_bug.cgi?id=409558 Bug ID: 409558 Summary: Tranform tools (perspective, warp, cage, liquify) - all results pixelated and grainy Product: krita Version: unspecified Platform: MS Windows OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: bullshitma...@yahoo.com Target Milestone: --- Created attachment 121356 --> https://bugs.kde.org/attachment.cgi?id=121356&action=edit Example of transformed layers (lines) SUMMARY Only free transform tool works as it should. All other options produce very bad results. Lines of the transformed layer get jigged, pixelated (squarish). It doesn't get better by changing the brush, or working on the higher DPI image... STEPS TO REPRODUCE 1. Take any layer 2. Try to transform it using any transform tool or brush (except free one) 3. Do it again? OBSERVED RESULT badly transformed object EXPECTED RESULT Transformed object, perhaps more blurry but smooth SOFTWARE/OS VERSIONS Windows: 7 - ultimate,10 - home macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 409351] Task bar is going to crashed after print or scan
https://bugs.kde.org/show_bug.cgi?id=409351 Christian Pubanz changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from Christian Pubanz --- I dont know why, but the bug is fixed. I ve print something and the task bar is running. Its verry courius... Thank you for the solution whatever -and a specical thanks go to Kai-Uwe! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409041] KDevelop shows wrong data type in tooltip
https://bugs.kde.org/show_bug.cgi?id=409041
Aaron Puchert changed:
What|Removed |Added
Ever confirmed|0 |1
CC||aaronpuch...@alice-dsl.net
Status|REPORTED|CONFIRMED
--- Comment #2 from Aaron Puchert ---
I can reproduce this. When I hover over either of the bitmask members, it also
highlights the bitmask in u.bitmask. The tool tips show no "Container:",
probably because these are unnamed structs/unions. When I give them names,
everything is fine. So I assume something is wrong with our handling of unnamed
structs, probably because they seem to be represented by empty strings.
For example, `typedef struct {} tp;` is
|-RecordDecl 0x101d5e8 <:1:9, col:17> col:9 struct definition
`-TypedefDecl 0x107a5f8 col:19 tp 'struct tp':'tp'
`-ElaboratedType 0x107a5a0 'struct tp' sugar
`-RecordType 0x101d660 'tp'
`-Record 0x101d5e8 ''
while `typedef struct X {} tp;` is
|-RecordDecl 0x109b5e8 <:1:9, col:19> col:16 struct X definition
`-TypedefDecl 0x10f85b8 col:21 tp 'struct X':'struct X'
`-ElaboratedType 0x10f8560 'struct X' sugar
`-RecordType 0x109b660 'struct X'
`-Record 0x109b5e8 'X'
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 unlogic changed: What|Removed |Added CC||un_lo...@rambler.ru --- Comment #2 from unlogic --- (In reply to Anders Lund from comment #1) > KInfoCecnter says: > KDE-Plasma: 5.16.1 > KDE-Frameworks: 5.59.0 > Qt: 5.12.4 > Linux-kernel: 5.1.12-arch1-1-ARCH > Have you tried to filter out notifications from your Android SMS app? It's under Plug-ins settings Notifications sync. Unflag your SMS app of choice. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 409553] App not starter
https://bugs.kde.org/show_bug.cgi?id=409553 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Antonio Rojas --- As the message says, it needs to be recompiled. Please report this to your distribution. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 345235] Text is hidden when form fields are hidden, text does not export or print
https://bugs.kde.org/show_bug.cgi?id=345235 Doug changed: What|Removed |Added CC||dougjsha...@gmail.com --- Comment #12 from Doug --- Created attachment 121355 --> https://bugs.kde.org/attachment.cgi?id=121355&action=edit I am having this issue on this document -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 --- Comment #4 from Michael Weghorn --- (In reply to avlas from comment #3) > Not sure I understand. I don't see much of a problem, in other words, where > the conflict is. Opening a dialog makes no action, right? The action occurs > when the button (e.g. save) is clicked and this cannot happen at once with > another action, can it? I guess you're right (clicking the "Save" button should trigger the QFileDialog::fileSelected signal), at least if one can assume that edit actions aren't long-running, e.g. you click a button and it takes several seconds until the action is completed (which may not be an issue, and could probably still be dealt with by using proper synchronisation between the processes...). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 409557] New: Bank OFX Files getting Slower to process
https://bugs.kde.org/show_bug.cgi?id=409557 Bug ID: 409557 Summary: Bank OFX Files getting Slower to process Product: kmymoney Version: 4.8.3 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: ralph.godd...@outlook.com Target Milestone: --- SUMMARY I have been using Kmymoney for about a year and I notice the OFX files from the bank are taking longer & longer to process. I assume Kmymoney is checking its entire database to validate entries. Not sure this platform will be useful to me in a few more years unless there is some improvement in this regard. EXPECTED RESULT Quicken never seemed to have this problem, to this degree, with 7+ years of data. SOFTWARE/OS VERSIONS Windows: 10pro 64bit latest updates ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #21 from Gerson --- since the upload limit is 4MB, I'll attach the file with an online system: https://ufile.io/60gkivz8 The file (index.tgz) will be available for 30 days starting now. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #17 from Michael Weghorn --- (In reply to Matthew Trescott from comment #16) > Created attachment 121353 [details] > CUPS error log when printing with LibreOffice > > No, neither of those files exist. And as I said, LibreOffice doesn't have > this problem. Here's the CUPS error log when printing with LibreOffice (I > included a bit more at the beginning this time) Indeed, this log has "PageSize=Letter" as expected. > > I noticed that LibreOffice sends CUPS a PDF, while Okular sends CUPS a > PostScript file. Maybe something goes wrong in the PDF -> PostScript > conversion in Okular/Poppler? I think the problem is earlier already, since the wrong value of the option is used, so I'd expect that Poppler is passed A4 already and thus generates A4 (as it's told). What happens with other Qt/KDE applications, like e.g. Kate? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #20 from Gerson --- Indeed... baloo is working properly in my wife's computer, which runs Manjaro KDE as well. The problem is that since there's no error message... we have do dig manually for the corrupted file. But since it takes a while for the db to get corrupted, this search is probably quite cumbersome. In my case, actually, it seems that the db only corrupts after I restart the computer. I'll attach here the index file before and after I restart the computer. I'll name them index.good (before restart) and index.bad (after restart). It contains only file names, so there's nothing personal or secret that I care about there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 409556] New: Weird notification appearance change when using Synaptics input driver
https://bugs.kde.org/show_bug.cgi?id=409556 Bug ID: 409556 Summary: Weird notification appearance change when using Synaptics input driver Product: frameworks-knotifications Version: 5.16.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ossn...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Weird notification appearance change when using Synaptics input driver STEPS TO REPRODUCE 1. Install Synaptic input driver 2. In "Input" -> "Touchpad" options go to "Enable/Disable Touchpad" and check "Disable touchpad when mouse is plugged in" 3. Log out and back in OBSERVED RESULT Notification becomes a blue bar on top of the screen with white text EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409528] unable to select default email client / outlook for sending by email
https://bugs.kde.org/show_bug.cgi?id=409528 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- It is possible to call the default email client via a "mailto:"; URL, but most email programs no longer support attachments for security reasons. Unfortunately, Outlook also supports only one "/a" parameter via the command line and thus accepts only one attachment/image. There may be a possibility with native Windows code, but this will happen later. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409528] unable to select default email client / outlook for sending by email
https://bugs.kde.org/show_bug.cgi?id=409528 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/b9039f9e42a3 ||67e6337c4211ce19c8b5c27f55f ||b Version Fixed In||6.2.0 Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit b9039f9e42a367e6337c4211ce19c8b5c27f55fb by Maik Qualmann. Committed on 06/07/2019 at 19:24. Pushed by mqualmann into branch 'master'. add outlook as email client FIXED-IN: 6.2.0 M +2-1NEWS M +22 -0core/dplugins/generic/tools/sendbymail/manager/mailprocess.cpp M +1-0core/dplugins/generic/tools/sendbymail/manager/mailsettings.cpp M +1-0core/dplugins/generic/tools/sendbymail/manager/mailsettings.h A +58 -0core/dplugins/generic/tools/sendbymail/tools/outlookbinary.h [License: GPL (v2+)] M +6-0core/dplugins/generic/tools/sendbymail/wizard/mailintropage.cpp M +39 -23 core/libs/widgets/files/dbinaryiface.cpp https://invent.kde.org/kde/digikam/commit/b9039f9e42a367e6337c4211ce19c8b5c27f55fb -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409555] New: Discover crashed when clicking on app or install button
https://bugs.kde.org/show_bug.cgi?id=409555 Bug ID: 409555 Summary: Discover crashed when clicking on app or install button Product: Discover Version: 5.16.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: connorrfi...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.16.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I opened discover and clicked on FreeCIV, and then Discover suddenly crashed. I recieved a crash notification. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa8d4deee00 (LWP 5195))] Thread 11 (Thread 0x7fa85f7fe700 (LWP 5289)): #0 0x7fa8c9f13394 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa8c9ecc3b7 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8c9ecd385 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8c9ecd5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa8d035cdcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8d02fe03a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8d01254ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa8d0126c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8cc7ae6db in start_thread (arg=0x7fa85f7fe700) at pthread_create.c:463 #9 0x7fa8cfa2688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fa85700 (LWP 5286)): #0 0x7fa8cfa150b4 in __GI___libc_read (fd=41, buf=0x7fa85fffea50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fa8c9f12000 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8c9eccfb7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8c9ecd470 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa8c9ecd5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa8d035cdcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8d02fe03a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa8d01254ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8d0126c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa8cc7ae6db in start_thread (arg=0x7fa85700) at pthread_create.c:463 #10 0x7fa8cfa2688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fa86cfce700 (LWP 5285)): #0 0x7fa8cfa19bf9 in __GI___poll (fds=0x7fa858011070, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa8c9ecd4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8c9ecd5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8d035cdcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8d02fe03a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8d01254ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8d373e926 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa8d0126c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8cc7ae6db in start_thread (arg=0x7fa86cfce700) at pthread_create.c:463 #9 0x7fa8cfa2688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fa86f29c700 (LWP 5241)): #0 0x7fa8cc7b49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560838b1b430) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560838b1b3e0, cond=0x560838b1b408) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560838b1b408, mutex=0x560838b1b3e0) at pthread_cond_wait.c:655 #3 0x7fa8d012ddbb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8d012e0c9 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8d37c46f8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa8d37c4b2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qu
[krusader] [Bug 409364] Apparmor disallows opening of multimedia files on LAN (i.e. opening of temporary file in ~/.cache/kioexec/krun/*/ is disallowed)
https://bugs.kde.org/show_bug.cgi?id=409364 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED CC||alex.bikado...@kdemail.net Resolution|--- |NOT A BUG --- Comment #2 from Alex Bikadorov --- This is not related to Krusader. It may be something related to KIO but more likely to Apparmor. >From the error message I would simply say you need to allow read access for VLC for the ~/.cache/kioexec/krun/ path by Apparmor. What is the file path of the original file you have on "LAN" here in Krusader? Is this the "file://" protocol or something else? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409554] New: build d649293 Deadlock when pasting into another application
https://bugs.kde.org/show_bug.cgi?id=409554 Bug ID: 409554 Summary: build d649293 Deadlock when pasting into another application Product: krita Version: nightly build (please specify the git hash!) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: epicwraths...@yandex.ru Target Milestone: --- Created attachment 121354 --> https://bugs.kde.org/attachment.cgi?id=121354&action=edit bt full and thread apply all bt SUMMARY I was doing something that was like this: take screenshot, create new image, paste screenshot, go to original image with very large canvas (2048x4096 16-float RGB/alpha; 130MB size according to tab) and multiple layers, control-r and select, press control-c, and then alt-tabbed to an application where I pasted, and nothing was pasted...krita used 0% cpu and wasn't useful -- I think the UI responded, but nobody was home. STEPS TO REPRODUCE 1. I wish I knew. I tried a bit... I summarized what I was doing in the summary. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.0-20-generic 64-bit (Ubuntu) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Krita version is d649293. Attached is the output of 'bt full' and 'thread apply all bt'. A core dump is available if requested. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409473] Computer shutdown gets cancelled
https://bugs.kde.org/show_bug.cgi?id=409473 --- Comment #3 from Alex Bikadorov --- There seems to be a difference between the quitting by the session manager and quitting by the mainwindow->quit() call. Just one question because i cannot test this myself (I don't use KDE): If you activate the "Warn on exit" setting in Settings->Configure Krusader->General, do you see the warning dialog of Krusader asking to quit when you try to logout in KDE? And you use the inbuilt editor in Krusader i guess? There is another report of this: https://forum.kde.org/viewtopic.php?f=289&t=153379 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407902] KMyMoney crashes in LEAP15.1
https://bugs.kde.org/show_bug.cgi?id=407902 --- Comment #31 from Thomas Baumgart --- Bingo: compiled with ENABLE_WEBENGINE=ON and there is the crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 --- Comment #7 from Bence Mihaly --- Thanks for the help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |b...@valdyas.org Status|REPORTED|ASSIGNED --- Comment #6 from Boudewijn Rempt --- Thanks, I got the file now. Other applications can still show it, but Krita asserts on it. Backtrace: ASSERT (krita): "layerName == layer->name()" in file /home/boud/dev/krita/plugins/impex/libkra/kis_kra_savexml_visitor.cpp, line 293 Thread 1 (Thread 0x7f74045af000 (LWP 6262)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f73fef7d801 in __GI_abort () at abort.c:79 #8 0x7f73ff952f2b in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f74012ad91e in kis_assert_common (assertion=assertion@entry=0x7f73a8139978 "layerName == layer->name()", file=file@entry=0x7f73a8139900 "/home/boud/dev/krita/plugins/impex/libkra/kis_kra_savexml_visitor.cpp", line=line@entry=293, throwException=throwException@entry=false, isIgnorable=isIgnorable@entry=false) at /home/boud/dev/krita/libs/global/kis_assert.cpp:90 #10 0x7f74012ada3a in kis_assert_recoverable (assertion=assertion@entry=0x7f73a8139978 "layerName == layer->name()", file=file@entry=0x7f73a8139900 "/home/boud/dev/krita/plugins/impex/libkra/kis_kra_savexml_visitor.cpp", line=line@entry=293) at /home/boud/dev/krita/libs/global/kis_assert.cpp:103 #11 0x7f73a8130d5d in KisSaveXmlVisitor::loadLayerAttributes (el=..., layer=layer@entry=0x55be0180a7d0) at /home/boud/dev/krita/plugins/impex/libkra/kis_kra_savexml_visitor.cpp:293 #12 0x7f73a8131595 in KisSaveXmlVisitor::loadPaintLayerAttributes (el=..., layer=0x55be0180a7d0) at /home/boud/dev/krita/plugins/impex/libkra/kis_kra_savexml_visitor.cpp:132 #13 0x7f73a836f2eb in KisExrLayersSorter::Private::processLayers (this=this@entry=0x7f73d8004f20, root=...) at /home/boud/dev/krita/plugins/impex/exr/kis_exr_layers_sorter.cpp:109 #14 0x7f73a836f33b in KisExrLayersSorter::Private::processLayers (this=this@entry=0x7f73d8004f20, root=...) at /home/boud/dev/krita/plugins/impex/exr/kis_exr_layers_sorter.cpp:115 #15 0x7f73a836fc1f in KisExrLayersSorter::KisExrLayersSorter (this=0x7fff7f9d0a70, extraData=..., image=...) at /home/boud/dev/krita/plugins/impex/exr/kis_exr_layers_sorter.cpp:170 #16 0x7f73a835b98f in EXRConverter::decode (this=this@entry=0x7fff7f9d0bf0, filename=...) at /home/boud/dev/krita/plugins/impex/exr/exr_converter.cc:909 #17 0x7f73a835c7ad in EXRConverter::buildImage (this=this@entry=0x7fff7f9d0bf0, filename=...) at /home/boud/dev/krita/plugins/impex/exr/exr_converter.cc:931 #18 0x7f73a8354497 in exrImport::convert (this=0x55bdfdb65cb0, document=0x55bdf814e370) at /home/boud/dev/krita/plugins/impex/exr/exr_import.cc:45 #19 0x7f740329a02d in KisImportExportManager::doImport (this=this@entry=0x55bdfee48100, location=..., filter=...) at /home/boud/dev/krita/libs/ui/KisImportExportManager.cpp:601 #20 0x7f740329b851 in KisImportExportManager::convert (this=this@entry=0x55bdfee48100, direction=direction@entry=KisImportExportManager::Import, location=..., realLocation=..., mimeType=..., showWarnings=, exportConfiguration=..., isAsync=) at /home/boud/dev/krita/libs/ui/KisImportExportManager.cpp:361 #21 0x7f740329c15b in KisImportExportManager::importDocument (this=this@entry=0x55bdfee48100, location=..., mimeType=...) at /home/boud/dev/krita/libs/ui/KisImportExportManager.cpp:136 #22 0x7f740328650a in KisDocument::openFile (this=this@entry=0x55bdf814e370) at /home/boud/dev/krita/libs/ui/KisDocument.cpp:1431 #23 0x7f7403286efb in KisDocument::openUrlInternal (this=this@entry=0x55bdf814e370, url=...) at /home/boud/dev/krita/libs/ui/KisDocument.cpp:1873 #24 0x7f74032873bf in KisDocument::openUrl (this=0x55bdf814e370, _url=..., flags=...) at /home/boud/dev/krita/libs/ui/KisDocument.cpp:1330 #25 0x7f74032a4a4d in KisMainWindow::openDocumentInternal (this=this@entry=0x55bdfbe87ab0, url=..., flags=flags@entry=...) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:909 #26 0x7f74032aa87e in KisMainWindow::openDocument (this=this@entry=0x55bdfbe87ab0, url=..., flags=flags@entry=...) at /home/boud/dev/krita/libs/ui/KisMainWindow.cpp:884 #27 0x7f74032738b8 in KisApplication::start (this=, args=...) at /home/boud/dev/krita/libs/ui/KisApplication.cpp:601 #28 0x55bdf2322d7b in main (argc=, argv=0x7fff7f9d1918) at /home/boud/dev/krita/krita/main.cc:513 This is really weird because the the assert happens when saving to .kra... Thanks for you report, and I'll try to figure out what's going on. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 409553] New: App not starter
https://bugs.kde.org/show_bug.cgi?id=409553 Bug ID: 409553 Summary: App not starter Product: ktouch Version: 19.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: jac...@yahoo.es Target Milestone: --- SUMMARY App not starter STEPS TO REPRODUCE 1. Search in menu 2. click icon 3. No starter OBSERVED RESULT Open windows with messages: "qrc:/qml/main.qml: File was compiled ahead of time with an incompatible version of Qt and the original file cannot be found. Please recompile" EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumbleweed 20190704 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404133] Artifacts when painting in RGB 32-bit float/channel
https://bugs.kde.org/show_bug.cgi?id=404133 Tymond changed: What|Removed |Added Status|ASSIGNED|CONFIRMED Assignee|tamtamy.tym...@gmail.com|krita-bugs-n...@kde.org --- Comment #10 from Tymond --- The optimization never worked. They are disabled on master will be disabled on the stable branch as well, so users won't see it/won't have a problem. I unassign myself from this bug report since I couldn't find a cause and I won't be working on it for now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407251] Converting animation color space from 16bit to 8bit creates artifacts in onion skin
https://bugs.kde.org/show_bug.cgi?id=407251 Tymond changed: What|Removed |Added Assignee|tamtamy.tym...@gmail.com|krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404133] Artifacts when painting in RGB 32-bit float/channel
https://bugs.kde.org/show_bug.cgi?id=404133 --- Comment #9 from Tymond --- Git commit cd5450a851ed2183fbb7ea479365efc114e94c26 by Agata Cacko, on behalf of Dmitry Kazakov. Committed on 06/07/2019 at 17:03. Pushed by tymond into branch 'master'. Disable AVX optimizations for 32-bit composite ops They cause artifacts and we don't have a fix yet :( Note from the committer: This commit was initially made on krita/4.2 branch. However between 4.2.1 and 4.2.2 the stable branch was reconstructed, which caused all commits that were exclusively on the previous krita/4.2 (and not on master) to be missing. The previous commit hash: d3e4c3aa299cf10a3ef167213f50799baba9c782 Also regarding the artifacts: it never worked, optimization were enabled during the creamy flow implementation, but they never should be enabled until someone fix them properly. M +14 -3libs/pigment/compositeops/KoCompositeOps.h https://invent.kde.org/kde/krita/commit/cd5450a851ed2183fbb7ea479365efc114e94c26 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407902] KMyMoney crashes in LEAP15.1
https://bugs.kde.org/show_bug.cgi?id=407902 --- Comment #30 from Wolfgang Bauer --- (In reply to Thomas Baumgart from comment #29) > Then I built the software myself from the 5.0.4 tarball and installed it. > Works without a problem. If I remove it and install the RPM version again it > crashes. Did you build with QtWebEngine? The original package is, and one affected user confirmed that the crash is gone when building it with QtWebKit instead. Other than that, I have no idea what could be causing this either. And I cannot even reproduce the crash (I did try with a Leap 15.1 LiveCD). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 --- Comment #3 from avlas --- (In reply to Michael Weghorn from comment #2) > As far as I understand, this would require the Qt file dialog to be > non-modal here. > Don't know whether that's easily possible, but even if it was, I see this > issue: Okular can not only show but also edit documents (e.g. insert > annotations into PDF documents). If the user could interact with the > document and edit it while the save dialog is open, what version of the > document would be saved? > > I'm currently not aware of any program/editor that does have a non-modal > save dialog (at least kate, gedit, libreoffice also have modal ones). Not sure I understand. I don't see much of a problem, in other words, where the conflict is. Opening a dialog makes no action, right? The action occurs when the button (e.g. save) is clicked and this cannot happen at once with another action, can it? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #16 from Matthew Trescott --- Created attachment 121353 --> https://bugs.kde.org/attachment.cgi?id=121353&action=edit CUPS error log when printing with LibreOffice No, neither of those files exist. And as I said, LibreOffice doesn't have this problem. Here's the CUPS error log when printing with LibreOffice (I included a bit more at the beginning this time) I noticed that LibreOffice sends CUPS a PDF, while Okular sends CUPS a PostScript file. Maybe something goes wrong in the PDF -> PostScript conversion in Okular/Poppler? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Michael Weghorn changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #15 from Michael Weghorn --- (In reply to Matthew Trescott from comment #13) > Created attachment 121352 [details] > CUPS log when printing This log (s. the 'argv[5]' line) shows that A4 is explicitly set for the page size. This shouldn't happen if you have Letter selected in the print dialog, and as mentioned, I couldn't reproduce with the same PPD. Is there any file /etc/cups/lpoptions or $HOME/.cups/lpoptions present, and if so, can you attach them here (or try to delete them and see what happens then)? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409541] Sort by toolbar icon not changing properly
https://bugs.kde.org/show_bug.cgi?id=409541 --- Comment #1 from Gabriel Fernandes --- It also affects right click context menu, window main menu and when main menu not shown control menu, it's not a toolbar restricted problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408160] Workspace saves docker positions but not docker sizes (width, height) on restart.
https://bugs.kde.org/show_bug.cgi?id=408160 Boudewijn Rempt changed: What|Removed |Added CC||lozmacdesi...@hotmail.com --- Comment #1 from Boudewijn Rempt --- *** Bug 409535 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409535] Unable to remember workspace last used on program exit
https://bugs.kde.org/show_bug.cgi?id=409535 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |DUPLICATE --- Comment #9 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 408160 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407802] Invalid File
https://bugs.kde.org/show_bug.cgi?id=407802 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from Boudewijn Rempt --- I'm sorry, but there isn't much we can do here -- things like this are a system failure, not a bug in krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 --- Comment #5 from Boudewijn Rempt --- Hm, that might make it harder. It's generally best to work in .kra files, and only export to exr or other formats when needed. I still don't have access to the link, though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 --- Comment #4 from Bence Mihaly --- Yes it should be, I’ve saved everything related to the file as .exr. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409447] Krusader crashes while starting
https://bugs.kde.org/show_bug.cgi?id=409447 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED CC||alex.bikado...@kdemail.net Resolution|--- |FIXED --- Comment #1 from Alex Bikadorov --- In the commit 262a96c7 a line got accidentally deleted when picking commits from master. I recreated the line in stable. @Benjamin Thanks for testing the stable branch and reporting! @Nikita Please try to cherry-pick the commits from master into stable separately and without changing the author information. Otherwise it gets confusing for me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Boudewijn Rempt --- Okay, I've requested access as vur...@gmail.com . Is this ifile also an exr file? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 --- Comment #2 from Bence Mihaly --- (In reply to Boudewijn Rempt from comment #1) > Please provide the file so we can take a look at it -- a dropbox link or > google drive link or something like that. > > For recovery, check whether there are backup files for this file that do > load (they end in .kra~, and you might have to tell Windows Explorer to show > file extensions to see this.) > > Please also consider the save incremental version feature for important work. I attempted to open the backup file but it crashed Explorer. I am not sure if the issue has anything to do with the fact that I saved the image as a .EXR file but this has not caused any sort of problems with previous works. The link to the file: https://drive.google.com/file/d/12q1chNJDl8PbfOzDnXWIgGsuSNOAWw-H/view?usp=sharing_eil&ts=5d20b637 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 403670] Add support for Team Drives
https://bugs.kde.org/show_bug.cgi?id=403670 David Barchiesi changed: What|Removed |Added CC||da...@barchie.si --- Comment #2 from David Barchiesi --- Work on this feature has started https://phabricator.kde.org/T10630 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409473] Computer shutdown gets cancelled
https://bugs.kde.org/show_bug.cgi?id=409473 --- Comment #2 from Darafei Praliaskouski --- Reproducer: - open Krusader - edit file, don't save - try to shut down computer - press "cancel" on pop up asking you to save your work - see the notification "shutdown canceled by Krusader" - close the edited document, don't save - File-Quit does not work anymore, nor shutdown - always cancelled by Krusader. I believe first time I got there somehow without pressing Cancel on the request to save my work, but can't figure that way for now. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #14 from Matthew Trescott --- Sorry for the spam, it's actually poppler 0.76.1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 --- Comment #13 from Matthew Trescott --- Created attachment 121352 --> https://bugs.kde.org/attachment.cgi?id=121352&action=edit CUPS log when printing -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Matthew Trescott changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #12 from Matthew Trescott --- I have Poppler 0.76. I'll attach the relevant CUPS log shortly. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409473] Computer shutdown gets cancelled
https://bugs.kde.org/show_bug.cgi?id=409473 Alex Bikadorov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||alex.bikado...@kdemail.net Status|REPORTED|NEEDSINFO --- Comment #1 from Alex Bikadorov --- >File - Exit does nothing either You mean you cannot close krusader in general? Can you figure out what is preventing this - is Krusader running some process like file copy action or something? What functionality have you used in Krusader - just starting/closing Krusader does not work? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 409489] Can't change permissions and ownership of remote files/folders
https://bugs.kde.org/show_bug.cgi?id=409489 --- Comment #1 from Alex Bikadorov --- This is not related to Krusader. You want to get and set users/groups for remote files via KIO's fish protocol. Support for this new feature must probably not only be build in fish (which is part of KIO extras) but also in KIO itself. I don't know about KRename but i assume it is simply using KIO as well (like Krusader). -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 409489] Can't change permissions and ownership of remote files/folders
https://bugs.kde.org/show_bug.cgi?id=409489 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Assignee|krusader-bugs-n...@kde.org |plasma-b...@kde.org Component|net-connection |FISH Product|krusader|kio-extras Version|2.7.1 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Konsole switch profile from gui only change termial theme but not excute the customed command
https://bugs.kde.org/show_bug.cgi?id=408217 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com --- Comment #3 from Darin McBride --- (In reply to Achim Bohnet from comment #2) > Hi, > AFAIR this behaviour is not new. That's the way konsole treated the > switch-profile as long as I can remember. Prior to https://bugs.kde.org/show_bug.cgi?id=405930, if I used the keyboard shortcut, it would properly create a new tab. Switching an existing tab to a new process makes no sense to me. Also, if I use the switch-profile like the way it is now, whether keyboard or menu, and then restart KDE such that that konsole gets restarted, then that tab has the theme AND runs the command, which is different behaviour. I'd say that it's far more broken now than it was before that "fix". The only way I can see to salvage the difference between "switch profile" and "new tab -> profile" is to separate out *theme* from command/profile. That is, everything under "Settings" changes from "profile" to "theme". There is no command or current directory associated with a theme. The entire "General" tab in profiles would be removed. And then a new configuration, say "template", would exist that would have that "General" tab that just got removed, plus a link to an existing "theme". (Perhaps the ability to create a new theme at the same time would be there, doesn't matter to me.) Both themes and templates can have keyboard shortcuts. I would personally never use the shortcut for the theme, but that doesn't mean others wouldn't. On re-startup, konsole would have to know what template and theme each tab had, and apply as appropriate. That's the salvage. Otherwise, I would simply move the whole profile thing to be starting new tabs. Because as long as a command exists there, which is the sole reason why I use profiles in the first place, switching a tab to a profile without running the command specified is inherently broken. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Please provide the file so we can take a look at it -- a dropbox link or google drive link or something like that. For recovery, check whether there are backup files for this file that do load (they end in .kra~, and you might have to tell Windows Explorer to show file extensions to see this.) Please also consider the save incremental version feature for important work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409552] New: An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image.
https://bugs.kde.org/show_bug.cgi?id=409552 Bug ID: 409552 Summary: An image I was working on fails to load and crashes the application when I attempt to open the aforementioned image. Product: krita Version: 4.2.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: se.wra...@gmail.com Target Milestone: --- SUMMARY An image I was working on has begun failing to load entirely and crashes Krita whenever I attempt to open the aforementioned image file. The issue does not carry over to any other images I have worked on in the past. Reproducible: Always STEPS TO REPRODUCE 1. Load Krita up 2. select image OBSERVED RESULT A window appears stating that the image has been modified so that the pixels have some alpha values (this is normal and happened before the issue) then the application seemingly loads before closing entirely. EXPECTED RESULT The mentioned window about the alpha values appears and the image loads and allows additional changes to be made. Request: Should the issue not be a direct bug or is otherwise not fixable (e.g: the file itself is corrupted), I would like to know if there is any way to restore the file or recover any past saves of the file. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 352029] Tag not shown in ledger if only an category is set
https://bugs.kde.org/show_bug.cgi?id=352029 Thomas Baumgart changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/00bf04711d001bf6885de ||8fda7d99b4058d1c964 Version Fixed In||5.0.5 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Thomas Baumgart --- Git commit 00bf04711d001bf6885de8fda7d99b4058d1c964 by Thomas Baumgart. Committed on 02/07/2019 at 18:27. Pushed by tbaumgart into branch '5.0'. Show tags in ledger if payee is empty FIXED-IN: 5.0.5 M +8-0kmymoney/widgets/stdtransaction.cpp https://commits.kde.org/kmymoney/00bf04711d001bf6885de8fda7d99b4058d1c964 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407282] fade to black move clip by some pixels
https://bugs.kde.org/show_bug.cgi?id=407282 --- Comment #3 from Davy Bartoloni --- issue still present on 19.04.2-6 (July 2019) just place a PNG and apply the fade... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405206] OFX import targets the wrong account
https://bugs.kde.org/show_bug.cgi?id=405206 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #20 from Thomas Baumgart --- Clear out the BANKID field as well. Only if both fields are empty you will be asked for a manual account assignment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- As far as I understand, this would require the Qt file dialog to be non-modal here. Don't know whether that's easily possible, but even if it was, I see this issue: Okular can not only show but also edit documents (e.g. insert annotations into PDF documents). If the user could interact with the document and edit it while the save dialog is open, what version of the document would be saved? I'm currently not aware of any program/editor that does have a non-modal save dialog (at least kate, gedit, libreoffice also have modal ones). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 409551] Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 20l8kxxl8...@opayq.com changed: What|Removed |Added Component|general |Open/save dialogs CC||kdelibs-b...@kde.org Product|okular |frameworks-kio Assignee|okular-de...@kde.org|fa...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from 20l8kxxl8...@opayq.com --- I can confirm that this bug also affects other applications such as KWrite. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407902] KMyMoney crashes in LEAP15.1
https://bugs.kde.org/show_bug.cgi?id=407902 --- Comment #29 from Thomas Baumgart --- This is very strange. I installed the debuginfo packages to get some more information about the cause. This enhanced the backtrace with the following: Thread 1 "kmymoney" received signal SIGSEGV, Segmentation fault. 0x72f2595a in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 (gdb) bt #0 0x72f2595a in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #1 0x72f25a8f in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #2 0x72f2878b in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #3 0x72f259e0 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #4 0x72f25a8f in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #5 0x72f2878b in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #6 0x555f0edc in runKMyMoney (splash=..., file=..., noFile=, a=...) at /usr/src/debug/kmymoney-5.0.4-lp151.1.1.x86_64/kmymoney/main.cpp:332 #7 0x555efb93 in main (argc=, argv=) at /usr/src/debug/kmymoney-5.0.4-lp151.1.1.x86_64/kmymoney/main.cpp:243 Then I built the software myself from the 5.0.4 tarball and installed it. Works without a problem. If I remove it and install the RPM version again it crashes. The next thing I tried was to build with Release instead of RelWithDebugInfo. Still working. Next I stripped all debug symbols. Still working. Then I strippped all symbols. Still working. So I have no idea what could be causing this and would throw it in the ball park of the installable package. Any objections? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409551] New: Usability bug: make "Save/Save As" dialogs use their own process
https://bugs.kde.org/show_bug.cgi?id=409551 Bug ID: 409551 Summary: Usability bug: make "Save/Save As" dialogs use their own process Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Let me give a bit of context on the use case. For research I frequently open PDF articles from the browser, take a look to them and decide (or not) saving them for further reading and/or later consultation and reference. Near 100% of the times that decision happens when I am not at page 1, so details of authors and title are not accessible (information I need to organize the bunch of PDFs I have). Therefore I need to close the Save/Save As dialog opened by intuition, go back to page 1, and proceed to save (again). If this would happen once, I would not care, but when this happens tens of times every day, it feels a bit unpleasant and breaks the flow. I am not sure about the technicalities, but I think this could be solved if the "Save/Save As" dialog would be in its own process, so even if open, I would still be able to scroll up the main window that appears behind. This is how it works in PDFs opened in the embedded viewer in Chromium for instance, and that is the feature request here. This may be a bug against kio instead of okular, not sure. Perhaps other use cases (other applications such as Kate, and other dialogs such as Open) might also benefit from this feature as well if extended to them. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409373] Krita crashes when Background and Layer 1 are present in Timeline box at the same time
https://bugs.kde.org/show_bug.cgi?id=409373 --- Comment #17 from Ahab Greybeard --- It's looking good so far. Can you render the animation out to an animated .gif and a .mp4 file with the 4.2.2.zip portable version? After you do that (assuming you can), make a copy of the kritarc file, rename the copy as kritarc-good-C and attach it to a comment. The details of the kritarc files so far may be useful for figuring out what went wrong. At the moment, you seem to have a working arrangement with the 4.2.2.zip portable. There's no reason why you shouldn't continue to use that and work it hard over the next few days to stress it and check that there are no further problems. At this stage you may as well change the theme, settings, etc to suit your personal preferences. If it goes wrong after you do that, then provide a copy of the kritarc file as an attachment for examination. You should first make a copy for backup of your current working kritarc file so you can restore it to a know good state if and after any problems arise. Later, if all goes well for a while, you can make another copy of the kritarc file for restoration in case of future problems. It's always a good idea to have a copy of a known good configuration file as a backup for restoration in case of problems. If you do that and all is well for a while, you can then try the 4.2.2 installed version that you already have to see if that has any problems. It shouldn't have but strange things can happen. If it does then you can try uninstalling followed by a fresh installation. (You can use the 4.2.2.zip and future portable .zips as an alternative to an installed version of course.) I hope we can assume that the kritarc problem was some strange random bad luck or corruption thing and that you'll have no more problems. If you do, then please report them. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 Philippe ROUBACH changed: What|Removed |Added Version|unspecified |5.11.2 --- Comment #21 from Philippe ROUBACH --- kde apps 19.04.2 plasma 5.16.2 kde frameworks 5.59.0 qt 5.13.0 Problem still there. Here is trace. Application: KAddressBook (kaddressbook), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc698305940 (LWP 5512))] Thread 5 (Thread 0x7fc65c8b4700 (LWP 5519)): #0 0x7fc6947b619b in poll () from /lib64/libc.so.6 #1 0x7fc68c2701a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc68c2702bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc69531c56b in QEventDispatcherGlib::processEvents (this=0x7fc658000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc6952bcb6a in QEventLoop::exec (this=this@entry=0x7fc65c8b3c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc6950d8d6a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc6950da512 in QThreadPrivate::start (arg=0x5581be563940) at thread/qthread_unix.cpp:360 #7 0x7fc68e3a0569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fc6947c09ef in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fc66989c700 (LWP 5517)): #0 0x7fc6947b1c98 in read () from /lib64/libc.so.6 #1 0x7fc68c2b4ca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc68c26fcb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc68c270150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fc68c2702bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fc69531c56b in QEventDispatcherGlib::processEvents (this=0x7fc66b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fc6952bcb6a in QEventLoop::exec (this=this@entry=0x7fc66989bc70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fc6950d8d6a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7fc6950da512 in QThreadPrivate::start (arg=0x5581be43aba0) at thread/qthread_unix.cpp:360 #9 0x7fc68e3a0569 in start_thread () from /lib64/libpthread.so.0 #10 0x7fc6947c09ef in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fc670bc4700 (LWP 5516)): #0 0x7fc68c2b5ff4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fc68c27019e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc68c2702bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc69531c56b in QEventDispatcherGlib::processEvents (this=0x7fc664000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc6952bcb6a in QEventLoop::exec (this=this@entry=0x7fc670bc3c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc6950d8d6a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc6937d3db5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fc6950da512 in QThreadPrivate::start (arg=0x7fc693a4bd80) at thread/qthread_unix.cpp:360 #8 0x7fc68e3a0569 in start_thread () from /lib64/libpthread.so.0 #9 0x7fc6947c09ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fc672e3a700 (LWP 5515)): #0 0x7fc68e3a68ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc673ae092b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fc673ae0637 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fc68e3a0569 in start_thread () from /lib64/libpthread.so.0 #4 0x7fc6947c09ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc698305940 (LWP 5512)): [KCrash Handler] #6 0x7fc69482283f in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #7 0x7fc6951604c1 in memcpy (__len=, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 replaceArgEscapes (s=..., d=..., field_width=field_width@entry=0, arg=..., larg=..., fillChar=...) at tools/qstring.cpp:8323 #9 0x7fc695168a98 in QString::arg (this=this@entry=0x7fff5a27cd38, a=..., fieldWidth=fieldWidth@entry=0, fillChar=...) at tools/qstring.cpp:8422 #10 0x7fc695168bc4 in QString::arg (this=this@entry=0x7fff5a27cd38, a=..., fieldWidth=fieldWidth@entry=0, fillChar=..., fillChar@entry=...) at tools/qstring.cpp:8377 #11 0x7fc6931109b4 in SendSmsAction::sendSms (this=this@entry=0x7fff5a27cdb7, phoneNumber=...) at /usr/src/debug/akonadi-contact-19.04.2-lp151.105.3.x86_64/src/akonadi-contacts/actions/sendsmsaction.cpp:91 #12 0x7fc6930d1cfe in Akonadi::ContactDefaultActions::sendSms (this=, number=...) at /usr/src/debug/akonadi-contact-19.04.2-lp151.105.3.x86_64/src/akonadi-contacts/contactdefaultactions.cpp:100 #13 0x7fc6952ef335 in QMetaObject::activate (sender=0x5581be439a90, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=, argv@entry=0x7fff5a27ced0) at kernel/qobject.cpp:3807 #14 0x7fc6952e
[plasmashell] [Bug 409550] New: Plasma Desktop Crash
https://bugs.kde.org/show_bug.cgi?id=409550 Bug ID: 409550 Summary: Plasma Desktop Crash Product: plasmashell Version: 5.16.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: eisi.eisgru...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Computer startup, opended firefox, closed it again, desktop crashed - Unusual behavior I noticed: Flickering of whole Desktop. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa977c14940 (LWP 3523))] Thread 35 (Thread 0x7fa8cd7fa700 (LWP 4682)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa979ecdfbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa979ece0a9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa97bd26d49 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fa97bd26fed in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fa979ec8112 in () at /usr/lib64/libQt5Core.so.5 #6 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #7 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fa8cdffb700 (LWP 4681)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa96e5d893b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fa96e5d8557 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fa8ce7fc700 (LWP 4680)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa96e5d893b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fa96e5d8557 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fa8ceffd700 (LWP 4654)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa979ecdfbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fa979ece0a9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7fa97bd26d49 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fa97bd26fed in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fa979ec8112 in () at /usr/lib64/libQt5Core.so.5 #6 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #7 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fa8cf7fe700 (LWP 4653)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa96e5d893b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fa96e5d8557 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7fa8c700 (LWP 4652)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa96e5d893b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fa96e5d8557 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #4 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fa8f0f90700 (LWP 4642)): [KCrash Handler] #6 0x7fa97998d2c6 in wl_proxy_marshal_constructor () at /usr/lib64/libwayland-client.so.0 #7 0x7fa975e07817 in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib64/libQt5WaylandClient.so.5 #8 0x7fa9740fc458 in () at /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7fa97a4cfaed in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib64/libQt5Gui.so.5 #10 0x7fa97bd233d6 in () at /usr/lib64/libQt5Quick.so.5 #11 0x7fa97bd26f58 in () at /usr/lib64/libQt5Quick.so.5 #12 0x7fa979ec8112 in () at /usr/lib64/libQt5Core.so.5 #13 0x7fa97937efaa in start_thread () at /lib64/libpthread.so.0 #14 0x7fa979b5371f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fa8f37fe700 (LWP 4641)): #0 0x7fa979384e05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa96e5d893b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fa96e5d8557 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fa97937efa
[kwin] [Bug 409549] With the smart placement policy, window size grows every time I open an application
https://bugs.kde.org/show_bug.cgi?id=409549 --- Comment #2 from David Edmundson --- Edit, not 5.17, Qt 5.13 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409549] With the smart placement policy, window size grows every time I open an application
https://bugs.kde.org/show_bug.cgi?id=409549 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Fixed in 5.17 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409549] New: With the smart placement policy, window size grows every time I open an application
https://bugs.kde.org/show_bug.cgi?id=409549 Bug ID: 409549 Summary: With the smart placement policy, window size grows every time I open an application Product: kwin Version: 5.16.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: b...@ubhofmann.de Target Milestone: --- I use KDE plasma in Wayland mode (kwin is the Wayland compositor) on Gentoo Linux. I use - kde-plasma 5.16.2 - kde-frameworks 5.59.0 - kde-apps 19.04.2 I start konsole (or kate or any other program) and resize the window so that there's some space between the konsole window and the KDE task bar at the bottom of my screen. I close konsole with File / Close window. I restart konsole and the window is bigger than before. Every time I start konsole, the window grows bigger and bigger. After I opened konsole 3 or 4 times, the Konsole window is so large, that its tab bar at the bottom is hidden behind the KDE taskbar at the bottom of my screen. That's annoying. Reproducible: Always SOFTWARE/OS VERSIONS - Gentoo Linux: default/linux/amd64/17.1/no-multilib - Linux Kernel: 4.19.50 - GCC: 8.3.0 - KDE Plasma Version: 5.16.2 - KDE Frameworks Version: 5.59.0 - KDE Apps: 19.04.2 - Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user
https://bugs.kde.org/show_bug.cgi?id=384485 e.ger...@gmx.de changed: What|Removed |Added CC||e.ger...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 409522] Two seperate donate pages on kde.org
https://bugs.kde.org/show_bug.cgi?id=409522 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||aa...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 376296 *** -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376296] Kde.org has two diferent donation pages
https://bugs.kde.org/show_bug.cgi?id=376296 Albert Astals Cid changed: What|Removed |Added CC||ke...@kde.org --- Comment #3 from Albert Astals Cid --- *** Bug 409522 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409547] crash when creating directory.
https://bugs.kde.org/show_bug.cgi?id=409547 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #3 from Friedrich W. H. Kossebau --- Thanks, so seems indeed the same cause. *** This bug has been marked as a duplicate of bug 408801 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 408801] Crash while creating folders in the save as dialog
https://bugs.kde.org/show_bug.cgi?id=408801 Friedrich W. H. Kossebau changed: What|Removed |Added CC||jaap.geu...@fontys.nl --- Comment #2 from Friedrich W. H. Kossebau --- *** Bug 409547 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409373] Krita crashes when Background and Layer 1 are present in Timeline box at the same time
https://bugs.kde.org/show_bug.cgi?id=409373 --- Comment #16 from starlightlovestod...@outlook.com --- (In reply to Ahab Greybeard from comment #14) > The kritarc file isn't very big so it's ok to attach it to a comment here. > The contents may (or may not) be useful for finding out what went wrong. > > The next stage is to establish if your laptop has problems with 4.2.2 (or > not) and then if your tablet is giving problems. (You previously said that > removing the tablet still resulted in a problem but it may be that the > presence of the tablet sets up some kind of faulty configuration, either in > krita or in your operating system.) > > Rename your current (fault giving) kritarc file as kritarc-faulty-A and > attach it to a comment here. > > Still with no tablet attached, download the 4.2.2.zip portable version as > noted in my previous comment, do the extraction process as before, then run > it from inside the resulting folder. It will recreate a fresh kritarc file > as you'll notice. > > You should be able to play/create an animation. If not, there is a strange > incompatibility between your laptop and krita 4.2.2. Either way, close krita > then make a copy of the kritarc file and rename the copy as kritarc-fresh-B, > keeping it for later if needed for examination. > > If the 4.2.2 portable seems to be working well with no tablet, close down > the laptop, connect the display-tablet, power up the laptop and tablet, then > run the 4.2.2 portable again to see if all is still ok when using the stylus > to draw for an animation. > > If adding the tablet and using the stylus causes problems then it's a > difficult situation so I hope it doesn't come to that. I was able to create and play an animation using the 4.2.2.zip portable version with both mouse and display-tablet. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409547] crash when creating directory.
https://bugs.kde.org/show_bug.cgi?id=409547 --- Comment #2 from Jaap Geurts --- Created attachment 121351 --> https://bugs.kde.org/attachment.cgi?id=121351&action=edit Additional backtrace with debug symbols loaded. -- You are receiving this mail because: You are watching all bug changes.
