[kstars] [Bug 379139] v2.4.0: Upper close/maximize/minimize button and INDI control panel doesn't appear (among other things)
https://bugs.kde.org/show_bug.cgi?id=379139 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jasem Mutlaq --- This is not a bug in KStars, it's due to the Window Manager you're using in Mint. KStars is best run under KDE. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 379140] Kolourpaint4 does not appear on Installed Programs on Ubuntu Software Center
https://bugs.kde.org/show_bug.cgi?id=379140 Martin Koller changed: What|Removed |Added Resolution|--- |INVALID CC||kol...@aon.at Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Koller --- Sorry but this description does not describe a problem with kolourpaint but with your distribution. Please report on a Debian list/forum/bugtracker -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 379145] New: Rectangular region mode can fail to respond to commands and lock out the system!
https://bugs.kde.org/show_bug.cgi?id=379145 Bug ID: 379145 Summary: Rectangular region mode can fail to respond to commands and lock out the system! Product: Spectacle Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: paul.hancock.17041...@live.com Target Milestone: --- The rectangular region mode can fail to respond to keyboard inputs and double-clicking, attempting to escape out of the mode can also be pretty much impossible as it insists on displaying above everything, this is a very bad design flaw! The region mode should allow the user to crop the screenshot that was just taken without taking full control of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379144] [Feature request] Bring back window event sounds
https://bugs.kde.org/show_bug.cgi?id=379144 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Martin Gräßlin --- No the ipc is still required. But one can use KWin scripts to emulate the behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379144] New: [Feature request] Bring back window event sounds
https://bugs.kde.org/show_bug.cgi?id=379144 Bug ID: 379144 Summary: [Feature request] Bring back window event sounds Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: bluescreenaven...@gmail.com Target Milestone: --- Back late in the 4.x cycle, the kwin sound events were removed, I read the justification being that it was causing multiple dbus signals to be sent, causing a power usage penalty. However, with KDE 5, it appears that the knotify4 process is gone, and I am able to suspend the kded5 process, and other knotify sounds still play, and I might be wrong, but it appears there's not as much IPC required now for knotify. (although I might be wrong) Can the events be brought back? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 379143] New: KDE file preview goes by hovered file, not by selected file, when doubleclick-to-open option is enabled
https://bugs.kde.org/show_bug.cgi?id=379143 Bug ID: 379143 Summary: KDE file preview goes by hovered file, not by selected file, when doubleclick-to-open option is enabled Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: bluescreenaven...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- It seems that in Dolphin, and in the open file dialog if you enable "show aside preview", that the preview goes by the hovered file. In Dolphin, you have to hover over the file for a second or two, for it to show in the preview, even if you select the file very quickly. In the Open File Preview, any file that you hover over, changes the preview instantly. When the doubleclick-to-open option is selected, I'd more expect it so that previews are only affected by selected files, not files that are hovered. (but keep that behavior for singleclick-top open mode) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683 --- Comment #4 from David Edmundson --- In what way is it not honoured? What does the config end up being saved as afterwards? Based on your code and system tray code, you will get some additional items added to your "extraItems" list as it will also include anything that has enabledByDefault checked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379032] Plasma still (despite of 346118 is closed) crashes on Connection to WiFi
https://bugs.kde.org/show_bug.cgi?id=379032 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Yes, and you're running Qt 5.7.1 So this new report doesn't change anything. As you're a gentoo user you can probably patch things: Grab these 3: https://github.com/qt/qtbase/commit/3bd0fd8f.patch https://github.com/qt/qtbase/commit/0874861b.patch https://github.com/qt/qtbase/commit/baad82d2.patch *** This bug has been marked as a duplicate of bug 346118 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 David Edmundson changed: What|Removed |Added CC||k...@mva.name --- Comment #175 from David Edmundson --- *** Bug 379032 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.
https://bugs.kde.org/show_bug.cgi?id=376866 David Edmundson changed: What|Removed |Added CC||oc...@ichf.edu.pl --- Comment #17 from David Edmundson --- *** Bug 378887 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378887] Keyboard doesn't work in text fields - some problem with polkit ?
https://bugs.kde.org/show_bug.cgi?id=378887 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from David Edmundson --- *** This bug has been marked as a duplicate of bug 376866 *** -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379142] New: kdoctools fails when linking.
https://bugs.kde.org/show_bug.cgi?id=379142 Bug ID: 379142 Summary: kdoctools fails when linking. Product: kde-windows Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: buildsystem Assignee: kde-wind...@kde.org Reporter: r03...@gmail.com Target Milestone: --- Created attachment 105167 --> https://bugs.kde.org/attachment.cgi?id=105167&action=edit log-C_KDE.txt `[28/28] Linking CXX executable bin\meinproc5.exe FAILED: bin/meinproc5.exe cmd.exe /C "cd . && R:\mingw64\bin\c++.exe -std=c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -W char-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror =return-type -Wvla -Wdate-time -fdiagnostics-color=always -pedantic -Wsuggest-override -O2 -g -DNDEBUG src/CMakeFiles/ meinproc5.dir/meinproc.cpp.obj src/CMakeFiles/meinproc5.dir/meinproc_common.cpp.obj src/CMakeFiles/meinproc5.dir/xslt.cp p.obj src/CMakeFiles/meinproc5.dir/xslt_kde.cpp.obj src/CMakeFiles/meinproc5.dir/loggingcategory.cpp.obj src/CMakeFiles/ meinproc5.dir/meinproc5_automoc.cpp.obj -o bin\meinproc5.exe -Wl,--out-implib,lib\libmeinproc5.dll.a -Wl,--major-image- version,0,--minor-image-version,0 R:/lib/libxml2.dll.a R:/lib/libxslt.dll.a R:/lib/libexslt.dll.a R://lib/libKF5Archive .dll.a R://lib/libQt5Core.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladva pi32 && cd ." src/CMakeFiles/meinproc5.dir/meinproc.cpp.obj: In function `main': Q:/kdoctools/src/meinproc.cpp:134: undefined reference to `__imp__ZN9KDocTools17setupStandardDirsERK7QString' Q:/kdoctools/src/meinproc.cpp:198: undefined reference to `__imp__ZN9KDocTools23locateFileInDtdResourceERK7QString6QFlag sIN14QStandardPaths12LocateOptionEE' Q:/kdoctools/src/meinproc.cpp:213: undefined reference to `__imp__ZN9KDocTools9transformERK7QStringS2_RK7QVectorIPKcE' Q:/kdoctools/src/meinproc.cpp:220: undefined reference to `__imp__ZN9KDocTools11saveToCacheERK7QStringS2_' collect2.exe: error: ld returned 1 exit status ninja: build stopped: subcommand failed. Craft encountered an error: make cmd: ninja Action: compile for frameworks/tier2/kdoctools FAILED *** Craft all failed: all of frameworks/kdoctools failed after 0:00:14 *** fatal error: package frameworks/kdoctools all failed` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Peter Schmidt changed: What|Removed |Added CC||zicrons...@yahoo.com --- Comment #2 from Peter Schmidt --- I too desire this feature. This doesn't appear to be completely broken, though. I noticed any text I select (regardless of source) will middle-click-paste in Xwayland programs. In other words, I can select text from a Wayland-native program and middle-click-paste in a Xwayland program, but not in another Wayland-native program. At the very least, I would like it if there was an implementation not backward compatible with Xwayland. Something is better than nothing. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379141] New: Craft encountered an error: make cmd: jom: No such file or directory (WTF/WTFHeaderDetection.h)
https://bugs.kde.org/show_bug.cgi?id=379141 Bug ID: 379141 Summary: Craft encountered an error: make cmd: jom: No such file or directory (WTF/WTFHeaderDetection.h) Product: kde-windows Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: buildsystem Assignee: kde-wind...@kde.org Reporter: r03...@gmail.com Target Milestone: --- Created attachment 105166 --> https://bugs.kde.org/attachment.cgi?id=105166&action=edit log-C_KDE.txt Encountered in an attempt to build KDevelop. Compilation terminates when unable to find the aforementioned file. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379063] build of win32libs/icu fails when invoking awk in build of kdevelop: error while loading shared libraries: msys-readline7.dll
https://bugs.kde.org/show_bug.cgi?id=379063 --- Comment #7 from r03...@gmail.com --- Unfortunately those instructions did not work. However, the bug has been fixed in by a complete reinstallation of Craft. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379006] When KWallet unlocks automatically and programs re-open on boot, programs open before KWallet gets unlocked
https://bugs.kde.org/show_bug.cgi?id=379006 --- Comment #5 from Nate Graham --- Fair enough. https://bugzilla.mozilla.org/show_bug.cgi?id=1358932 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378950] widgets should all have size constraint property
https://bugs.kde.org/show_bug.cgi?id=378950 --- Comment #3 from Manuel Ramírez --- Hi David. Thank you for the reply. With: - "Applets can already communicate sizes to the containment (min, preffered, max). So most your proposal is already done." You mean that this can be done with some configuration? Regards. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378886] Crash when closing the notification that a panel was just removed
https://bugs.kde.org/show_bug.cgi?id=378886 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 378508 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378508] when remove panel applet plasma crashed
https://bugs.kde.org/show_bug.cgi?id=378508 David Edmundson changed: What|Removed |Added CC||noeero...@gmail.com --- Comment #12 from David Edmundson --- *** Bug 378886 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378508] when remove panel applet plasma crashed
https://bugs.kde.org/show_bug.cgi?id=378508 David Edmundson changed: What|Removed |Added CC||kendos.ken...@gmail.com --- Comment #13 from David Edmundson --- *** Bug 378506 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378506] Plasma crash when applying look and feel
https://bugs.kde.org/show_bug.cgi?id=378506 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 378508 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378508] when remove panel applet plasma crashed
https://bugs.kde.org/show_bug.cgi?id=378508 David Edmundson changed: What|Removed |Added CC||mklape...@kde.org Component|general |Notifications Assignee|k...@davidedmundson.co.uk|k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378735] Firewalld is missing its system tray icon
https://bugs.kde.org/show_bug.cgi?id=378735 David Edmundson changed: What|Removed |Added Component|System Tray |XembedSNIProxy CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Please also file a bug -- You are receiving this mail because: You are watching all bug changes.
[Purpose] [Bug 379093] Spectacle logs user out of the system when user clicks Export image > Share > Save as
https://bugs.kde.org/show_bug.cgi?id=379093 Boudhayan Gupta changed: What|Removed |Added Component|General |general Product|Spectacle |Purpose Assignee|m...@baloneygeek.com |aleix...@kde.org --- Comment #3 from Boudhayan Gupta --- Aleix, Hope you don't mind, I'm reassigning this to you. The GIF gives a clue to the problem - it's apparently setting the whole data uri of the image as the filename. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378950] widgets should all have size constraint property
https://bugs.kde.org/show_bug.cgi?id=378950 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from David Edmundson --- We will try to fix the individual issues Manuel has pointed out. Feel free to list more. Applets can already communicate sizes to the containment (min, preffered, max). So most your proposal is already done. Adding a default to this base class (AppletInterface) won't actually solve the problem; as well as effectively being an API break for 3rd parties. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 47320] [testcase] text and background uses colors from KDE color scheme if not specified in the html style
https://bugs.kde.org/show_bug.cgi?id=47320 Ganton changed: What|Removed |Added CC||ku...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379006] When KWallet unlocks automatically and programs re-open on boot, programs open before KWallet gets unlocked
https://bugs.kde.org/show_bug.cgi?id=379006 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from David Edmundson --- > Firefox thinks there's no network connection and has to be restarted before > pages will load. That's not really anything to do with kwallet. Even if we blocked waiting on kwallet, it still takes network manager a while to connect; during which firefox could load. We cannot block session restore until network manager is ready; it'd break far too many other things. We (Network manager) does broadcast when it does connect, Firefox should detect this and reload itself. Please ask firefox to fix that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371007] Crash in QMetaObject::cast in QtQuickControls
https://bugs.kde.org/show_bug.cgi?id=371007 --- Comment #9 from Tavian Barnes --- > Can someone CC'd here please tell me whether they use the global menu bar? Nope, no global menu bar for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379044] Crash when pressing the "add widget" button on the panel
https://bugs.kde.org/show_bug.cgi?id=379044 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 378376 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378376] plasma crashed when panel changes with screen edge button clicked
https://bugs.kde.org/show_bug.cgi?id=378376 David Edmundson changed: What|Removed |Added CC||keziolio...@gmail.com --- Comment #6 from David Edmundson --- *** Bug 379044 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371007] Crash in QMetaObject::cast in QtQuickControls
https://bugs.kde.org/show_bug.cgi?id=371007 David Edmundson changed: What|Removed |Added CC||r...@bugs.kde.pu.futz.org --- Comment #8 from David Edmundson --- *** Bug 375775 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375775] plasma crash
https://bugs.kde.org/show_bug.cgi?id=375775 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 371007 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371007] Crash in QMetaObject::cast in QtQuickControls
https://bugs.kde.org/show_bug.cgi?id=371007 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from David Edmundson --- Better trace Thread 1 (Thread 0x7f582d8d0940 (LWP 2775)): [KCrash Handler] #6 0x7f583c4ab49b in QMetaObject::cast(QObject const*) const () at /lib64/libQt5Core.so.5 #7 0x7f581810956f in QQuickMenu1::menuBar() () at /usr/lib64/qt5/qml/QtQuick/Controls/libqtquickcontrolsplugin.so #8 0x7f581810e1c1 in QQuickMenuPopupWindow1::shouldForwardEventAfterDismiss(QMouseEvent*) const () at /usr/lib64/qt5/qml/QtQuick/Controls/libqtquickcontrolsplugin.so #9 0x7f581810ed10 in QQuickPopupWindow1::forwardEventToTransientParent(QMouseEvent*) () at /usr/lib64/qt5/qml/QtQuick/Controls/libqtquickcontrolsplugin.so #10 0x7f581810ef7d in QQuickPopupWindow1::mousePressEvent(QMouseEvent*) () at /usr/lib64/qt5/qml/QtQuick/Controls/libqtquickcontrolsplugin.so #11 0x7f583c7e48a5 in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 #12 0x7f583ff9d615 in QQuickWindow::event(QEvent*) () at /lib64 Can someone CC'd here please tell me whether they use the global menu bar? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371007] Crash in QMetaObject::cast in QtQuickControls
https://bugs.kde.org/show_bug.cgi?id=371007 David Edmundson changed: What|Removed |Added CC||taviana...@gmail.com --- Comment #6 from David Edmundson --- *** Bug 379134 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379134] Plasma crashed when switching audio input device for Chromium
https://bugs.kde.org/show_bug.cgi?id=379134 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 371007 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 379140] New: Kolourpaint4 does not appear on Installed Programs on Ubuntu Software Center
https://bugs.kde.org/show_bug.cgi?id=379140 Bug ID: 379140 Summary: Kolourpaint4 does not appear on Installed Programs on Ubuntu Software Center Product: kolourpaint Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: cala...@protonmail.com Target Milestone: --- I want this to be uninstalled -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 379128] Allow remote command: lock, halt, reboot KDE session
https://bugs.kde.org/show_bug.cgi?id=379128 --- Comment #1 from Albert Vaca --- While there is nothing more specific, you can use the "run command" plugin to implement this yourself. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365078] With "Automatically expand groups" enabled, groups are expanded twice or even three times
https://bugs.kde.org/show_bug.cgi?id=365078 --- Comment #4 from kram...@web.de --- KMail 5.5.0 solves this bug for me. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379139] New: v2.4.0: Upper close/maximize/minimize button and INDI control panel doesn't appear (among other things)
https://bugs.kde.org/show_bug.cgi?id=379139 Bug ID: 379139 Summary: v2.4.0: Upper close/maximize/minimize button and INDI control panel doesn't appear (among other things) Product: kstars Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: marinanov...@gmail.com Target Milestone: --- Hi, Close/Max/Min buttons doesn't appear. When the INDI control panel is executed, its window appears behind the main window, and it can't be bring at front. Also the lower Linux Mint control panel disappears. Thanks in advance, Marinanova -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379111] Vertical sync causes flickering on screen capturing
https://bugs.kde.org/show_bug.cgi?id=379111 --- Comment #2 from Michał Dybczak --- Version === KWin version: 5.9.4 Qt Version: 5.8.0 Qt compile version: 5.8.0 XCB compile version: 1.12 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11903000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__Freeze Blur: 1 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 5, 3, 4, 2 decorationButtonsRight: 9, 1 borderSize: 3 gridUnit: 10 font: Noto Sans,11,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 1 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: true killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 20 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: eDP1 Geometry: 0,0,1920x1080 Refresh Rate: 60.0204 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL version string: 4.5 (Core Profile) Mesa 17.0.3 OpenGL platform interface: GLX OpenGL shading language version string: 4.50 Driver: Intel GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 17.0.3 X server version: 1.19.3 Linux kernel version: 4.10.10 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_login wobblywindows screenshot kwin4_effect_translucency magiclamp kwin4_effect_windowaperture desktopgrid cubeslide coverswitch colorpicker kwin4_effect_fade kwin4_effect_morphingpopups kwin4_effect_maximize presentwindows highlightwindow kwin4_effect_dialogparent contrast startupfeedback screenedge kscreen Currently Active Effects: - contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: wobblywindows: stiffness: 0.01 drag: 0.76 moveFactor: 0.25 xTesselation: 20 yTesselation: 20 minVelocity: 0 maxVelocity: 1000 stopVelocity: 0.5 minAcceleration: 0 maxAcceleration: 1000 stopAcceleration: 0.5 moveEffectEnabled: true openEffectEnabled: false closeEffectEnabled: false moveWobble: true resizeWobble: true screenshot: kwin4_effect_translucency: magiclamp: animationDuration: 250 kwin4_effect_windowaperture: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true cubeslide: rotationD
[kde] [Bug 379138] New: Kdenlive 17.04 crash when selecting a composite transititon
https://bugs.kde.org/show_bug.cgi?id=379138 Bug ID: 379138 Summary: Kdenlive 17.04 crash when selecting a composite transititon Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: t...@eilerts1.com Target Milestone: --- Application: kdenlive (17.04.0) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-72-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Loaded project from older version and discovered a error with a affine transition. Deleted the afiine and added a composite. Kdenlive crashed and I'm now unable to delete the composite transition as Kdenlive freezes every time I select the transition. The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f96e730c8c0 (LWP 18397))] Thread 14 (Thread 0x7f967a65c700 (LWP 18455)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f96bdc9195d in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so #2 0x7f96df6bc6ba in start_thread (arg=0x7f967a65c700) at pthread_create.c:333 #3 0x7f96e0dc682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f96a4bb5700 (LWP 18454)): #0 0x7f96d89d9518 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #1 0x7f96d89da458 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7f96d89da789 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #3 0x7f96d89db01a in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #4 0x7f96dbe0b0b7 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f96dbe0b4bc in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f96bda2bfeb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #7 0x7f96bd9fe920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #8 0x7f96bda080b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #9 0x7f96bda47f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #10 0x7f96df6bc6ba in start_thread (arg=0x7f96a4bb5700) at pthread_create.c:333 #11 0x7f96e0dc682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f96937fe700 (LWP 18453)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f96e64d30db in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #2 0x00742eed in RenderThread::run (this=0x7f967c80abb0) at /build/kdenlive-ROJqFx/kdenlive-17.04.0~ubuntu16.04.1/src/monitor/glwidget.cpp:1287 #3 0x7f96e17c1808 in QThreadPrivate::start (arg=0x7f967c80abb0) at thread/qthread_unix.cpp:341 #4 0x7f96df6bc6ba in start_thread (arg=0x7f96937fe700) at pthread_create.c:333 #5 0x7f96e0dc682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f969e03e700 (LWP 18452)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f96bdc9230f in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so #2 0x7f96df6bc6ba in start_thread (arg=0x7f969e03e700) at pthread_create.c:333 #3 0x7f96e0dc682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f96909f9700 (LWP 18414)): #0 0x7f96ddc9c3cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f96ddc9e8bb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f96ddc9f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f96ddc9f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f96e19eb37b in QEventDispatcherGlib::processEvents (this=0x7f966c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f96e1993ffa in QEventLoop::exec (this=this@entry=0x7f96909f8d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f96e17bc9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f96e17c1808 in QThreadPrivate::start (arg=0x7f968014ecc0) at thread/qthread_unix.cpp:341 #8 0x7f96df6bc6ba in start_thread (arg=0x7f96909f9700) at pthread_create.c:333 #9 0x7f96e0dc682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f9691ffb700 (LWP 18412)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f96e17c26bb in QWaitConditionPrivate::wait (time=18446744073709551615, this
[valgrind] [Bug 379039] syscall wrapper for prctl(PR_SET_NAME) must not check more than 16 bytes
https://bugs.kde.org/show_bug.cgi?id=379039 --- Comment #7 from Peter (Stig) Edwards --- Thank you very much for the patch, I built and tested and it works as expected. For the changes in coregrind/m_syswrap/syswrap-linux.c, I was thinking it might be better to use VKI_TASK_COMM_LEN ( as defined in include/vki/vki-linux.h ) and not 16. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379137] Artistic Text Drop Shadows Have Disappeared from a Saved File.
https://bugs.kde.org/show_bug.cgi?id=379137 aacalli...@gmail.com changed: What|Removed |Added Component|Dockers |Text Tool -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379137] Artistic Text Drop Shadows Have Disappeared from a Saved File.
https://bugs.kde.org/show_bug.cgi?id=379137 --- Comment #1 from aacalli...@gmail.com --- I mistakenly marked this as a problem with the dockers. I didn't mean to make that selection. This is a problem with drop shadows on artistic text. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379137] New: Artistic Text Drop Shadows Have Disappeared from a Saved File.
https://bugs.kde.org/show_bug.cgi?id=379137 Bug ID: 379137 Summary: Artistic Text Drop Shadows Have Disappeared from a Saved File. Product: krita Version: 3.0.1 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: aacalli...@gmail.com Target Milestone: --- Created attachment 105165 --> https://bugs.kde.org/attachment.cgi?id=105165&action=edit Layer properties for a layer containing text where the drop shadow has disappeared. Yesterday I used Krita to create artistic text, and I added colored drop shadows to the text. I used custom colors for some of the drop shadows, and default colors like black and white for others. When I was done with my work, I saved my file and closed it. I continued editing other files. When I re-opened the first file, the drop shadows were gone. The other files didn't have this problem so I assumed it was a problem with that one file. I closed the file and restarted Krita, but the problem persisted. I then created a brand new file and started over from scratch (throwing away a couple hours of work), but the same problem occurred. At the end of the day, I saved all of my files and closed Krita. Today I started Krita and opened the same files. The drop shadows have disappeared from all files now - even the ones that were working yesterday. Is there a way to prevent this from happening again? Can I recover my work? I've included a screenshot of the layer properties for one of the layers where the shadow has disappeared. I am using Krita 3.0.1, and I am saving my files using the .kra file type. My computer (laptop) is Toshiba Satellite E45W-C with an Intel(R) Core(TM) i3-5015U CPU @ 2.10GHz running 64-bit Windows 10 Home. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 --- Comment #4 from Anton Latuha --- Open with -> Other... Choose or type, 'digiKam'. Yes, there is no option in the package. Package done right. As in Windows, as in Linux Desktops - file associations in parts is a mess. Like VLC and Firefox, LibreOffice, Inkscape - spam a file associations no one uses in the right state of mind (like open PDF in Inkscape), but sometime they can be used. And it does not mean user cannot chose custom action. All DE has "Open With, choose application", that is why that is legitimate feature to implement. Ok, I have no choice but to agree and put it to rest as is. P.S. ## Question If I get to implement features, such as that to KDE. Does it going to be accepted upstream in KDE community? I love KDE, but I have a list of features lacking, and tried couple of times to get in. But QML + KDE + QT5 + C++ KDE writing standards + C++ itself, was to this time too hard and too layered for me to penetrate it through successfully and to write a good code. If I get to KDE, does my half-quality features get accepted/discussed one and I get in the process. Or probably features not going to be accepted because developers have view and KDE philosophy, way? Thank you. Regards, Anton Latukha -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361598] Alt+Tab does not always work when pressing it quickly
https://bugs.kde.org/show_bug.cgi?id=361598 --- Comment #5 from Martin Gräßlin --- You could run kwin from a konsole and watch the debug output. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 379136] New: www.kde.org missing AAAA record
https://bugs.kde.org/show_bug.cgi?id=379136 Bug ID: 379136 Summary: www.kde.org missing record Product: www.kde.org Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: thomas.bett...@gmail.com Target Milestone: --- www.kde.org has no IPv6 / entry, but is available over IPv6. ... see https://ip6.nl/#!kde.org To be reachable from pure IPv6 systems this record would be necessary... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from caulier.gil...@gmail.com --- And you don't read my previous message... As i said, File manager/context menu/open with.../digiKam as nothing to do here. digiKam is a photo-management program, not an editor/viewer as well. It's not dedicated to open a images by this way. The context menu option to open digiKam is WRONG. It's a customization of desktop file from THE desktop. So it's not a digiKam problem as i said previously. Here under Mageia 5 (KDE4) or MAgeia6 (Plasma), Open with do not contain digiKam entry. Report this problem to ArchLinux team as DOWNSTREAM. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 160110] option for rename: select all on rename
https://bugs.kde.org/show_bug.cgi?id=160110 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Alex Bikadorov --- Fixed a long time ago. The whole filename is selected on rename. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 158159] Missing "Retry" in "Directory not exist" error popup
https://bugs.kde.org/show_bug.cgi?id=158159 Alex Bikadorov changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||alex.bikado...@kdemail.net --- Comment #4 from Alex Bikadorov --- Fixed a long time ago. Error message is shown and "Reload" button is in toolbar. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379135] New: Dolphin crash when closing tab
https://bugs.kde.org/show_bug.cgi?id=379135 Bug ID: 379135 Summary: Dolphin crash when closing tab Product: dolphin Version: 17.04.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: oys...@gmail.com Target Milestone: --- Application: dolphin (17.04.0) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.8.0-46-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: Steps to reproduce: - Perform a baloosearch - Right click one of the results and open in new tab - Switch to that tab and close it On my system this reproduces the crash every time. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f00880938c0 (LWP 7878))] Thread 4 (Thread 0x7f00633b7700 (LWP 7882)): #0 0x7f007c7b3920 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f007c7b42bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f007c7b449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f008283075b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f00827db0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f008260af64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f008260fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f007eabb6ba in start_thread (arg=0x7f00633b7700) at pthread_create.c:333 #8 0x7f0087aac82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f0070a85700 (LWP 7881)): #0 0x7f007c7f8a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f007c7b4381 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f007c7b449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f008283075b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f00827db0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f008260af64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0088182735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f008260fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f007eabb6ba in start_thread (arg=0x7f0070a85700) at pthread_create.c:333 #9 0x7f0087aac82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f0072448700 (LWP 7880)): #0 0x7f0087aa0b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f007bab8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f007baba8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f00749a0d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f008260fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f007eabb6ba in start_thread (arg=0x7f0072448700) at pthread_create.c:333 #6 0x7f0087aac82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f00880938c0 (LWP 7878)): [KCrash Handler] #6 DolphinTabPage::splitViewEnabled (this=this@entry=0x0) at /workspace/build/src/dolphintabpage.cpp:71 #7 0x7f0087db3129 in DolphinMainWindow::updateSplitAction (this=this@entry=0xcc38c0) at /workspace/build/src/dolphinmainwindow.cpp:1472 #8 0x7f0087db3409 in DolphinMainWindow::updateViewActions (this=this@entry=0xcc38c0) at /workspace/build/src/dolphinmainwindow.cpp:1337 #9 0x7f0087dbb157 in DolphinMainWindow::activeViewChanged (this=0xcc38c0, viewContainer=0x158ecb0) at /workspace/build/src/dolphinmainwindow.cpp:942 #10 0x7f00828081f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0087e0bb3f in DolphinTabWidget::activeViewChanged (this=, _t1=0x158ecb0) at /workspace/build/obj-x86_64-linux-gnu/src/moc_dolphintabwidget.cpp:275 #12 0x7f00828081f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0087e0ba8f in DolphinTabPage::activeViewChanged (this=this@entry=0x15300c0, _t1=0x158ecb0) at /workspace/build/obj-x86_64-linux-gnu/src/moc_dolphintabpage.cpp:161 #14 0x7f0087dc64da in DolphinTabPage::slotViewActivated (this=0x15300c0) at /workspace/build/src/dolphintabpage.cpp:316 #15 0x7f00828081f6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00
[kwin] [Bug 376320] Task switcher themes not working under wayland
https://bugs.kde.org/show_bug.cgi?id=376320 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Martin Gräßlin --- This should be fixed in latest KWin master. Relevant commit: https://cgit.kde.org/kwin.git/commit/?id=ac08c5ac9d4532b2506c76e8b69249b32d365aa3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379134] New: Plasma crashed when switching audio input device for Chromium
https://bugs.kde.org/show_bug.cgi?id=379134 Bug ID: 379134 Summary: Plasma crashed when switching audio input device for Chromium Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: taviana...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.10-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Changing the mic device for Chromium in the volume settings -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f109a03c800 (LWP 2350))] Thread 32 (Thread 0x7f0f4effe700 (LWP 28934)): #0 0x7f1092cb3ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f106fd27e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f106e8a2394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f106fd2712c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f0f4f7ff700 (LWP 28933)): #0 0x7f1092cb3756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1093df958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1097b51665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1097b51f72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1093df86d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f0f54ffb700 (LWP 28932)): #0 0x7f1093def8a9 in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7f10940277df in () at /usr/lib/libQt5Core.so.5 #2 0x7f108e4e5c8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f108e4e66cb in () at /usr/lib/libglib-2.0.so.0 #4 0x7f108e4e68bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f109402806b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1093fd189a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1093df3a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1096f2c025 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f1093df86d8 in () at /usr/lib/libQt5Core.so.5 #10 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f0f557fc700 (LWP 28929)): #0 0x7f1092cb3ca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f106fd27e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f106e8a2394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f106fd2712c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f0f69fff700 (LWP 28928)): #0 0x7f1092cb3756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1093df958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1097b51665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7f1097b51f72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1093df86d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f0f848a2700 (LWP 28927)): #0 0x7f108e4e5c8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f108e4e66cb in () at /usr/lib/libglib-2.0.so.0 #2 0x7f108e4e68bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f109402806b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1093fd189a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1093df3a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1096f2c025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1093df86d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1092cad2e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f109370b54f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f0f567fd700 (LWP 28319)): #0 0x7f109370167d in poll () at /usr/lib/libc.so.6 #1 0x7f108e4e67a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f108e4e68bc in g_main_context_iteration () at /usr/lib/libgl
[kde] [Bug 379133] New: kdenlive crashes while adding bass effect
https://bugs.kde.org/show_bug.cgi?id=379133 Bug ID: 379133 Summary: kdenlive crashes while adding bass effect Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: erik.vanzeebro...@gmail.com Target Milestone: --- Application: kdenlive (17.04.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I was messing around with the bass effect and adding more bass to a video. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc9bc81b800 (LWP 8359))] Thread 26 (Thread 0x7fc92d7fa700 (LWP 18113)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fc92dffb700 (LWP 18112)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fc93de63700 (LWP 18111)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fc93e664700 (LWP 18110)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fc93f666700 (LWP 18109)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fc92700 (LWP 18108)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fc92f7fe700 (LWP 18107)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fc92effd700 (LWP 18106)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fc92e7fc700 (LWP 18105)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc97c1310cb in () at /usr/lib/libavfilter.so.6 #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fc8e700 (LWP 11101)): #0 0x7fc9b2c0d756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc968ff06dd in () at /usr/lib/mlt/libmltsdl.so #2 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #3 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fc92cff9700 (LWP 11100)): #0 0x7fc9b4bcc37d in read () at /usr/lib/libc.so.6 #1 0x7fc9a5e9af51 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fc9ac76830e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fc9ac768d80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fc968d8755d in () at /usr/lib/libSDL-1.2.so.0 #5 0x7fc968d5b76b in () at /usr/lib/libSDL-1.2.so.0 #6 0x7fc968d63e18 in () at /usr/lib/libSDL-1.2.so.0 #7 0x7fc968da4d39 in () at /usr/lib/libSDL-1.2.so.0 #8 0x7fc9b2c072e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fc9b4bda54f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fc8f8fe9700 (LWP 11081)): [KCrash Handler] #6 0x in () #7 0x7fc9
[konqueror] [Bug 379132] New: Startup screen does not load icons
https://bugs.kde.org/show_bug.cgi?id=379132 Bug ID: 379132 Summary: Startup screen does not load icons Product: konqueror Version: 4.14.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: klaus-dieter.fie...@bluewin.ch Target Milestone: --- Created attachment 105164 --> https://bugs.kde.org/attachment.cgi?id=105164&action=edit Konqueror Startup Screen When I start Konqueror it does not show the icons that are assigned to the various choices: Home Folder Network Folders Wastebin Bookmarks I have checked the image locations, such as file:///usr/share/icons/breeze/places/32/user-home.svg. They are accessible. I can open the pictures; they show up correctly. Apparently there is no command that causes Konqueror to open the icons. Thank you, Klaus-Dieter Fietze -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 Anton Latuha changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DOWNSTREAM |--- --- Comment #2 from Anton Latuha --- I am not stupid. You probably have not completely understood my description. ## I was looking how to import images. Not from a USB drive. Not from Camera. But, simple. Images from a folder, but so they on import going to be integrated in album structure (date structure). I am not adept of digiKam. And I could not find that simple action for tens of minutes of decisive looking. Trying different variants and searching manuals. Looks like I was doing it somehow before (or maybe I wasn't importing pictures from time I created and album). But I can't find how to do it. And I know, this is what application is for. Application need to have some action on that, I probably can't find it. I have a plethora of image viewers. And image editors. Package is configured right. I thought to fill question, bug-report (suggesting menu/action results to be more understandable). But that seems too stupid to ask, before I find a way or try and fail every path by myself. ## I tried to open images in digiKam deliberately. To see what action is going to happen. Because maybe it going to ask me what to do with them, or import them. And this happens. ## Hanging a system with a couple of hundreds of instances can be considered a usability problem. I have that problem in different applications from time to time, as you probably had also. When working with a lot of files, and hit enter not in that window, by mistake, or choosing to open them in application, inspecting/expecting application to treat them. Action probably needs to be covered with some action processing or a test-case. Or do a popup and point to launch showFoto instead. Or at least hang is a report. It is from my standpoint. Most good applications have that. showFoto, GIMP, Inkscape, Eye of GNOME. I understand, from programmers perspective, digiKam not connected to open photo action. And there is a default stud. But users expect otherwise. ## User thinks: digiKam manages photos, so it have some sort of action with them. If I open photos with it, probably action going to be the most logical one, the most useful one (and it probably is what I think). The way like I experienced with applications before. And it is hard to look at this user logic as wrong. ## Sorry, I open it ones. Because I don't know, do you read massages on resolved, downstream'ed ones. Regards, Anton Latukha. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376320] Task switcher themes not working under wayland
https://bugs.kde.org/show_bug.cgi?id=376320 --- Comment #4 from Martin Vysny --- Also affecting me with Plasma 5.9.4 and the "Large Icons" Visualisation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376320] Task switcher themes not working under wayland
https://bugs.kde.org/show_bug.cgi?id=376320 Martin Vysny changed: What|Removed |Added CC||vy...@baka.sk -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379131] New: Gmail authentication expires after some time
https://bugs.kde.org/show_bug.cgi?id=379131
Bug ID: 379131
Summary: Gmail authentication expires after some time
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: IMAP resource
Assignee: chrig...@fastmail.fm
Reporter: aro...@archlinux.org
CC: kdepim-b...@kde.org, vkra...@kde.org
Target Milestone: ---
This is with kmail/akonadi 5.5 (17.04). After running kmail for a few hours,
the Gmail account stops working. Folders are not synced anymore and messages
are not displayed.
I'm using two different Gmail accounts, in case it makes any difference.
Akonadi terminal output:
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
user=*user*(redacted)auth=Bearer*hash*(redacted)Pass a valid window to
KWallet::Wallet::openWallet().
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
user=**user2**(redacted)auth=Bearer**hash**(redacted)Pass a valid window to
KWallet::Wallet::openWallet().
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::EventFetchJob(0x10898a0) "Autenticación no válida."
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::ContactsGroupFetchJob(0x24d1940) "Autenticación no válida."
org.kde.pim.akonadicore: Deleting items from the akonadi database failed: "No
items found"
org.kde.pim.akonadicore: Error during ItemSync: "Failed to parse stream"
CalendarFetchJob::url()
QUrl("https://www.googleapis.com/calendar/v3/users/me/calendarList";)
org.kde.pim.akonadicore: Received response with a different tag!
QIODevice::write (KTcpSocket): device not open
Pass a valid window to KWallet::Wallet::openWallet().
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.akonadicore: Got a stale 'changed' notification for an item which
was already removed. 2137 ""
org.kde.pim.akonadicore: Got a stale 'changed' notification for an item which
was already removed. 2137 ""
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 379130] New: KDE taskbar randomly crashing when clicking above any application icon.
https://bugs.kde.org/show_bug.cgi?id=379130 Bug ID: 379130 Summary: KDE taskbar randomly crashing when clicking above any application icon. Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ch.mercesmore...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.11.0-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Tried to open some application by its icon located on the KDE taskbar (botton left). Here is one image pointing out where is the location I'm talking about: http://imgur.com/uPAeBsE - Unusual behavior I noticed: The system freezes and the taskbar dissapears. After about 5 seconds the bar reappeares and the system goes back to normal state. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7ea45f6800 (LWP 908))] Thread 18 (Thread 0x7f3d7f70b700 (LWP 13723)): #0 0x7f7e9d260b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a64c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7e9e3a1bc4 in () at /usr/lib/libQt5Core.so.5 #3 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #4 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f7d9cff9700 (LWP 2201)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7de899a249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f7d9d7fa700 (LWP 2200)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f7de899a249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #13 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f7d9dffb700 (LWP 2199)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Th
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 --- Comment #15 from mathoj...@gmail.com --- Thank you, I use a workaround too : I use ftps ;) But using a workaround is not a deal. And I really think that a network protocols should have a high priority in a DE. More and more NAS, multimedia servers ... are making use of : - SMB (bad implementation on KDE) - NFS (not implemented in KDE... incredible, but true) - DLNA/uPnP : there was a kio package for that, but I never successed to use it It's really not serious for a DE. I don't know how all of this is working on Gnome (never tried, because I'm an early fan of KDE, and plasma), but network protocols are a just weak and poor on KDE, and it's a big anomaly. I still hope a developper will fix it (and if he could work on NFS, and DLNA/uPnP would be great) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379129] Duplicate recent document opened
https://bugs.kde.org/show_bug.cgi?id=379129 --- Comment #1 from danjar...@gmail.com --- Created attachment 105163 --> https://bugs.kde.org/attachment.cgi?id=105163&action=edit krunner with recent documents duplicated -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379129] New: Duplicate recent document opened
https://bugs.kde.org/show_bug.cgi?id=379129 Bug ID: 379129 Summary: Duplicate recent document opened Product: plasmashell Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: danjar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105162 --> https://bugs.kde.org/attachment.cgi?id=105162&action=edit application launcher with recent documents duplicated the recent documents opened appear duplicates To reproduce: Open a file many times, and this files appear duplicate many times in krunner and laucher menu. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 379128] New: Allow remote command: lock, halt, reboot KDE session
https://bugs.kde.org/show_bug.cgi?id=379128 Bug ID: 379128 Summary: Allow remote command: lock, halt, reboot KDE session Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: piotr.budny+bugs...@gmail.com Target Milestone: --- Android app could allow one-click session lock, halt or reboot, or, execute custom commands. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 tempel.jul...@gmail.com changed: What|Removed |Added CC||tempel.jul...@gmail.com --- Comment #14 from tempel.jul...@gmail.com --- I have found a workaround: When you login with "*" for both user and password for a share which doesn't require a password, add another "*" to the adress. Example: You have opened a share and the adress looks like this: smb://*@pcname/sharename/ Change it to smb://*:*@pcname/sharename/ and press enter. Voila, you should have write access. Can this please get fixed? It should be so easy and it's really annoying... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 328928] Add text word wrap for all tooltips
https://bugs.kde.org/show_bug.cgi?id=328928 Alex Bikadorov changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kru ||sader/0e661e9fd290fc22f27e4 ||a844e26a4cc0ffd7e1b --- Comment #1 from Alex Bikadorov --- Git commit 0e661e9fd290fc22f27e4a844e26a4cc0ffd7e1b by Alexander Bikadorov. Committed on 18/04/2017 at 14:01. Pushed by abikadorov into branch 'master'. Panel: Added detailed tooltip for filename column in panel; Uses tooltip delay setting. + Merged duplicate code in KrSort and KrVfsModel FIXED: [ 328928 ] Add text word wrap for all tooltips M +21 -0krusader/GUI/krstyleproxy.cpp M +5-0krusader/GUI/krstyleproxy.h M +1-19 krusader/Panel/krinterbriefview.cpp M +0-1krusader/Panel/krinterbriefview.h M +15 -7krusader/Panel/krinterdetailedview.cpp M +3-15 krusader/Panel/krsort.cpp M +0-2krusader/Panel/krsort.h M +43 -25 krusader/Panel/krvfsmodel.cpp M +2-0krusader/Panel/krvfsmodel.h M +18 -2krusader/Panel/krview.cpp M +6-2krusader/Panel/krview.h M +1-1krusader/Panel/krviewitem.cpp https://commits.kde.org/krusader/0e661e9fd290fc22f27e4a844e26a4cc0ffd7e1b -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379127] New: K3B does not show the splashscreen correctly
https://bugs.kde.org/show_bug.cgi?id=379127 Bug ID: 379127 Summary: K3B does not show the splashscreen correctly Product: k3b Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GUI/Usability Assignee: k...@kde.org Reporter: yy...@gmx.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 105161 --> https://bugs.kde.org/attachment.cgi?id=105161&action=edit screencast I'm running K3B 17.04 on Arch. The splashscreen appears quickly, disappears and reappears with some transparency. Watch the screencast please. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Attachment #105159|k3b 2.0.3 and k3b 17.04 |k3b 17.04 screenshot description|| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 --- Comment #4 from Dr. Chapatin --- Created attachment 105160 --> https://bugs.kde.org/attachment.cgi?id=105160&action=edit k3b 2.0.3 screenshot -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 379123] digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 Dennis Nienhüser changed: What|Removed |Added CC||nienhue...@kde.org --- Comment #1 from Dennis Nienhüser --- I just installed latest digikam on arch, which consists of marble-common-17.04.0-1 marble-data-17.04.0-1 digikam-5.5.0-2. This works fine here. Does the crash occur every time you start digikam? The symlink mentioned in the title is not needed anymore after https://mail.kde.org/pipermail/release-team/2017-April/010244.html. It could be a problem even, can you remove it and try with the latest arch packages to see if that makes a difference? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Summary|Disc space bar is broken|Disc space/time bar is ||broken -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- digiKam 5.6.0 pre version do not crash under Wayland using Linux Mageia 6 Cauldron, with Plasma 5 desktop. The backtrace do not show a specific code in digiKam which crash the application. It decent in-deep in Qt5 and the system libraries. Also, if you can install debug symbols this can help to investigate. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 379093] Spectacle logs user out of the system when user clicks Export image > Share > Save as
https://bugs.kde.org/show_bug.cgi?id=379093 ruudolfs.strazd...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from ruudolfs.strazd...@gmail.com --- And it gets even more bizarre because sometimes the SDDM screen is windowed with the system title bar visible. I could resize the window, move it around, etc. And there's a notification in the system tray widget that reads Copying data:[,,,]. Here's the image that I tried to screenshot: http://i.imgur.com/Wv7RqyU.png?1 And here's the very long error window: http://i.imgur.com/GifQhpw.jpg And here's the error itself: http://i.imgur.com/Mw0lEoC.gifv Maybe the option to save the image from Export > Share > Save as should be removed since the image can already be saved. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 --- Comment #3 from Dr. Chapatin --- Created attachment 105159 --> https://bugs.kde.org/attachment.cgi?id=105159&action=edit k3b 2.0.3 and k3b 17.04 This bug is not fixed on k3b 17.04 running on Arch. Compare these two screenshots: K3b 2.0.3 screenshot shows correct disc space/time bar. K3b 17.04 screenshot shows thin disc space/time bar, I cant read used/available disc space/time. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 374563] Device is not accessible when in sleep mode
https://bugs.kde.org/show_bug.cgi?id=374563 pmarget...@gmail.com changed: What|Removed |Added CC||pmarget...@gmail.com --- Comment #1 from pmarget...@gmail.com --- Environment: Phone model: Xiaomi Redmi note 3 pro (MIUI 8.2 global ROM) KDE Connect 1.6 on phone, 1.0.3-1 PC Phone and PC have been paired. Steps to reproduce: -let phone enter standby -reboot PC Result: "No paired devices available" until phone is first activated from standby. As soon as the screen goes on, everything KDE connect related starts working, I don't even need to unlock it. Reproducible: always. Notes: KDE Connect on phone granted every priviledge (auto-start, read SMS, allow notifications on lock screen etc) I'm hereby confirming the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 --- Comment #1 from Anton Latuha --- Created attachment 105158 --> https://bugs.kde.org/attachment.cgi?id=105158&action=edit system log from start of application to finish System log during digiKam start and crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] New: digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 Bug ID: 379126 Summary: digiKam on Wayland Plasma crashes at start Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Application: digikam (5.5.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.10-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Starting digiKam application. (From Application Launcher.) - Custom settings of the application: Plasma on Wayland - Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f034bcc8680 (LWP 23631))] Thread 84 (Thread 0x7f02171d6700 (LWP 23768)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 83 (Thread 0x7f02179d7700 (LWP 23767)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 82 (Thread 0x7f02181d8700 (LWP 23766)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 81 (Thread 0x7f02189d9700 (LWP 23765)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 80 (Thread 0x7f02191da700 (LWP 23764)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 79 (Thread 0x7f02199db700 (LWP 23763)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 78 (Thread 0x7f021a1dc700 (LWP 23762)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Who setup to open image with digiKam. This is not the right way to configure the desktop. The application to use is Showfoto, not digiKam. Showfoto is the digiKam stand alone version of image editor. digiKam is a photo management program which need to setup collection to be used. It do not use image as well in CLI. So report this problem to ArchLinux team. The package is not configured properly. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] New: Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 Bug ID: 379125 Summary: Opening with... in file manager results in for every image digiKam instance spawns Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Workflow Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Thank you, digiKam guys. Steps to reproduce: 1. Use any file manager. (I use Dolphin) 2. In file manager open a folder with number of images. 3. Select a number of images. 4. Open Right click menu -> Open with... and open them with digiKam. 5. digiKam is going to load a new instance for every image. (I had 100 images selected, and my desktop machine gone to almost unresponsive state. So I needed to somehow execute `killall digiKam`) Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) P.S. 1. Severity Effect of bug can be equal to "Crash" severity, because it hangs all system almost completely. I waited for 20 minutes for desktop to sort-out situation. But in the end I needed take another 5 minutes to login to Linux console and kill all digiKam instances. 2. What I wanted to do Basically I was figuring-out how to import images to my album structure. And tried this variant. As a user I expected: Select one image - open import dialog for that image. Or ask me for action. Select bunch of images - open import dialog for that images. Or ask me for action. If images are in albums already - select them there. Or ask me for a custom action. Asking what I want to do. If some images already present - have option to ignore already imported images, report how much of them ignored, how much left to import and view of them (with a button to view what images was ignored, and where they are already in digiKam). Thank you, I appreciate digiKam. Regards, Anton Latukha. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 379124] New: Financial Year issue
https://bugs.kde.org/show_bug.cgi?id=379124 Bug ID: 379124 Summary: Financial Year issue Product: kmymoney4 Version: 4.8.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: nicolas.puir...@gmail.com Target Milestone: --- Hello Before explanation, sorry for my english, I am french (and my KMyMoney is in french mode). In the KMyMoney configuration, in General page, I set the begin of the fiscal year to the 1st July. When I list the operations, I see the "This year" in yellow, but the begin is the 1st January (and not the 1st July as set in configuration). => not critic When I want to set a budget, the fiscal year beginning is not taking into account. Indeed, the 12 months are listed in order (January to December) and not to July to June. The budget seems to use a civil year and not the fiscal year. => critic Perhaps I am the bug :). Thank you a lot for your response Regards Nicolas -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 --- Comment #3 from davidka --- ok -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 379123] digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |general CC||caulier.gil...@gmail.com Version|5.6.0 |unspecified Product|digikam |marble Target Milestone|--- |some future version Assignee|digikam-de...@kde.org |marble-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379123] New: digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 Bug ID: 379123 Summary: digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0 Product: digikam Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: blumensch...@dokom.net Target Milestone: --- Application: digikam (5.6.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: crashes on startup: digikam.geoiface: QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.geoiface: KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43cfc7a640 (LWP 7117))] Thread 42 (Thread 0x7f42753dc700 (LWP 7228)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 41 (Thread 0x7f4275bdd700 (LWP 7227)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 40 (Thread 0x7f42763de700 (LWP 7226)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 39 (Thread 0x7f4276bdf700 (LWP 7225)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 38 (Thread 0x7f42773e0700 (LWP 7224)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 37 (Thread 0x7f4277be1700 (LWP 7223)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wa
[ktouch] [Bug 379122] New: KTouch Empty page on startup
https://bugs.kde.org/show_bug.cgi?id=379122 Bug ID: 379122 Summary: KTouch Empty page on startup Product: ktouch Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: philippe.ques...@gmail.com Target Milestone: --- On Xubuntu 17.04, KTouch opens with an empty page. I can see the following message if I start it from a console: file:///usr/share/ktouch/qml/main.qml:19:1: module "QtQuick" is not installed import QtQuick 2.4 ^ >From what I can see, QtQuick 5.7.1 is installed. I can also see dependencies in the package for libqt5quick5 (>=5.6.1) -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 359537] Calligra Plan Crash every time when try to start a templet
https://bugs.kde.org/show_bug.cgi?id=359537 --- Comment #9 from Andreas Plank --- Thanks for your tip with KGantt2. I feel somewhat ashamed for having reported it here because it turned out I was lax in setting repository priorities, hence the system did install libKGantt2 (5.0.0git-13.1) from another repository but I actually needed version 2.6.0-14.1 of http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ of the same repo from which I obtained calligraplan. In my case this solved the issue: zypper install --oldpackage --details libKGantt2=2.6.0-14.1 libKChart2=2.6.0-14.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379121] "Output destination" uses wrong dialog on GNOME, making choosing destination impossible
https://bugs.kde.org/show_bug.cgi?id=379121 Mike Ironfist changed: What|Removed |Added Severity|minor |normal -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379121] New: "Output destination" uses wrong dialog on GNOME, making choosing destination impossible
https://bugs.kde.org/show_bug.cgi?id=379121 Bug ID: 379121 Summary: "Output destination" uses wrong dialog on GNOME, making choosing destination impossible Product: kdenlive Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: mikekla...@gmail.com Target Milestone: --- Created attachment 105157 --> https://bugs.kde.org/attachment.cgi?id=105157&action=edit Image showing the wrong dialog. This is a simple bug that comes from running Kdenlive on GNOME and not on Plasma. Steps to reproduce the bug: 1. On a GNOME Shell session, click the "render" button or go to "Project - Render" in the menu bar. The render options dialog opens. 2. Click the folder button next to "output destination" to attempt to change the output destination. Expected Result: A "save file" dialog should appear. Actual result: An "open file" dialog appears and picking a file destination is not possible. Is Kdenlive using Zenity for the GNOME file dialogs? If so we could fix this just by adding '--save' as a parameter for the window opened by the "Output Destination" button. If not, I do not expect it should be too hard to fix, since it's only some sort of shell/front-end/toolkit calling the wrong dialog for GNOME. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 379100] generate data from function does nothing
https://bugs.kde.org/show_bug.cgi?id=379100 Stefan Gerlach changed: What|Removed |Added Component|frontend|general Ever confirmed|0 |1 CC||stefan.gerlach@uni-konstanz ||.de Status|UNCONFIRMED |CONFIRMED Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de Severity|normal |major --- Comment #1 from Stefan Gerlach --- * works on Linux * "x" works, "2*x" and "exp(x)" does not -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 359537] Calligra Plan Crash every time when try to start a templet
https://bugs.kde.org/show_bug.cgi?id=359537 --- Comment #8 from Dag Andersen --- This is a different issue. The symbol indicates it's a crash in KGantt. KGantt has been moved out of calligra and is a separate package now. Could you report it there? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361598] Alt+Tab does not always work when pressing it quickly
https://bugs.kde.org/show_bug.cgi?id=361598
Daniel Lichtenberger changed:
What|Removed |Added
CC||daniel.lichtenber...@gmx.ne
||t
--- Comment #4 from Daniel Lichtenberger ---
I also experience this problem with Plasma 5.9.4. I tried disabling/modifying
various desktop effects, reducing or increasing animation speed, as well as
using the compact application switcher.
When the application switcher fails, the Alt+Tab command seems to be
registered. The current window briefly loses focus, but it is re-focused after
a short delay instead of switching to the previous window.
I can kind of reliably reproduce the issue using xdotool, to rule out keyboard
or keypress timing issues:
for i in {1..10}; do echo 'Switching...'; xdotool key 'alt+Tab'; sleep 1; done
Usually this works as expected, toggling between the konsole window and the
previously selected window, but sometimes the same window gets focused multiple
times. I used several applications as the previous window (Dolphin, Firefox, VS
Code, ...), but couldn't notice a pattern. Is there any debug output that could
help diagnose the problem?
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 379120] New: Discover Applications would crash when clicking back button
https://bugs.kde.org/show_bug.cgi?id=379120 Bug ID: 379120 Summary: Discover Applications would crash when clicking back button Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: cruzh...@att.net Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-19-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: When I would view an application then click the back button, the application would crash. I could restart the program and repeat several times in a row. The crash can be reproduced every time. -- 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 0x7fc8342e1440 (LWP 3887))] Thread 10 (Thread 0x7fc790ff9700 (LWP 3927)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc830284b4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc8336ca495 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fc8336cad8a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc82c65e6da in start_thread (arg=0x7fc790ff9700) at pthread_create.c:456 #6 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7fc7ed2fb700 (LWP 3902)): #0 0x7fc82f876cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a553b30 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f042 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc8304a7f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc83045188a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc83027efe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc82c65e6da in start_thread (arg=0x7fc7ed2fb700) at pthread_create.c:456 #10 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7fc7fccd3700 (LWP 3897)): #0 0x7fc82f87b18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a50f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc8304a7f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc83045188a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc83027efe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc82c65e6da in start_thread (arg=0x7fc7fccd3700) at pthread_create.c:456 #8 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7fc7fe9a3700 (LWP 3895)): #0 0x7fc82a50c55f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc82a50ea0b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f902 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc800793476 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7fc82a536f65 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc82c65e6da in start_thread (arg=0x7fc7fe9a3700) at pthread_create.c:456 #7 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7fc7ff1a4700 (LWP 3894)): #0 0x7fc82f87b18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a50f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f6d1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc82a536f65 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc82c65e6da in start_thread (arg=0x7fc7ff1a4700) at pthread_create.c:456 #6 0x7fc82f88717f in clon
[amarok] [Bug 379119] New: Amarok crashes while attempting to "Get Tags from MusicBrainz"
https://bugs.kde.org/show_bug.cgi?id=379119 Bug ID: 379119 Summary: Amarok crashes while attempting to "Get Tags from MusicBrainz" Product: amarok Version: 2.8.0 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: kri...@kristawhipple.com Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.4.38 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: Application: Amarok OS: Slackware 14.2 x64 (4.4.38) WM: Xfce 4.12 Steps to reproduce: Right click on an artist or album - click "Edit Track Details" Click "Get Tags from MusicBrainz" Tracks populate in the "MusicBrainz Tagger" window. When the progress bar reads 100%, Amarok crashes. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fabe422f7c0 (LWP 12621))] Thread 17 (Thread 0x7fab13fff700 (LWP 12641)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabdffa85aa in () at /usr/lib64/qt/lib/libQtScript.so.4 #2 0x7fabdffa85d9 in () at /usr/lib64/qt/lib/libQtScript.so.4 #3 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #4 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fab2914b700 (LWP 12640)): #0 0x7fabda8c7849 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fabda884191 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda8848df in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884a6c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabe16400ce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #5 0x7fabe16105d1 in QEventLoop::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #6 0x7fabe16108e5 in QEventLoop::exec(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #7 0x7fabe1509c39 in QThread::exec() () at /usr/lib64/qt/lib/libQtCore.so.4 #8 0x7fabe150c3bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #9 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #10 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fab2a14d700 (LWP 12637)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe150c8d4 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7fabdea1866c in () at /usr/lib64/libthreadweaver.so.4 #3 0x7fabdea1b0a3 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7fabdea19d7f in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #5 0x7fabe150c3bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #6 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #7 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fab2b18b700 (LWP 12636)): #0 0x7fabe0e34e3d in read () at /lib64/libc.so.6 #1 0x7fabda8c6630 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda884494 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884908 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabda884ce2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7fabd0749986 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7fabda8aa275 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #8 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fab2b98c700 (LWP 12635)): #0 0x7fabe0e3930d in poll () at /lib64/libc.so.6 #1 0x7fabda884964 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda884a6c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884aa9 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabda8aa275 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #6 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fab788ae700 (LWP 12634)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabd8326d9d in () at /usr/lib64/qt/lib/libQtWebKit.so.4 #2 0x7fabd8326df9 in () at /usr/lib64/qt/lib/libQtWebKit.so.4 #3 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #4 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fab89bf2700 (LWP 12633)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe150c8d4 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7fabdea1866c i
[kwin] [Bug 373514] kwin_wayland crashes after Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=373514 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from Martin Gräßlin --- Waiting for response for further investigation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 --- Comment #2 from Christoph Feck --- Just add a comment with your findings. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and widgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Alex changed: What|Removed |Added Attachment #105156|Discover doesn't show |Discover doesn't show description|programs, only plasma |programs, only plasma |vidgets and fonts. |widgets and fonts. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and widgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Alex changed: What|Removed |Added Summary|Discover became useless |Discover became useless |with bug. (He doesn't show |with bug. (He doesn't show |programs, only fonts and|programs, only fonts and |vidgets)|widgets) -- You are receiving this mail because: You are watching all bug changes.
